[CVE-2026-74728][LOW] xfs: handle NULL b_addr in xfs_buf_free [ Upstream

[CVE-2026-74728][LOW] xfs: handle NULL b_addr in xfs_buf_free [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74728
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: xfs: handle NULL b_addr in xfs_buf_free [ Upstream
Commit: ccf6738adcafa5ddbddc4e71b45d8a51b86643c7
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ccf6738adcafa5ddbddc4e71b45d8a51b86643c7
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74728
Analysis date: Sat, 22 Aug 2026 13:11:14 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED
Manual review required: YES

Summary:
A NULL pointer dereference in `xfs_buf_free()` can occur after XFS backing memory allocation failure, causing a local kernel crash during XFS repair related handling, but the issue requires special conditions and does not show a privilege escalation or data corruption primitive.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-74728 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74728

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-74728	LOW	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'xfs_buf_free can call virt_to_folio on a NULL bp b_addr when xfs_buf_alloc_backing_mem fails and the buffer is freed through the non VMAP and non KMEM path. This results in an invalid address dereference and a kernel crash during XFS repair related handling rather than a normal network input path. For the CVSS the PR:L reflects the paranoid case where a local user can influence memory pressure or can reach the relevant XFS repair path through delegated filesystem management, while typical direct repair operations require higher privileges. The issue is not network reachable. Impact is denial of service via kernel crash only. No concrete UAF, OOB write, arbitrary write, information leak, or privilege escalation primitive is indicated by the code change.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED (with actual score 1)	YES	OOB DANGER DISK SIMPLEFIX KERNEL_PANIC_PLUS_UAF LINUS SYZBOT  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED**

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1
  `virt_to_folio(NULL)` can dereference an invalid address and crash the kernel.
* Important filesystem/storage path: +1
  The bug is in XFS buffer handling, reached from XFS repair related code.
* Requires admin/root/CAP_* in typical deployments: -2
  The shown path involves XFS repair/scrub style operations, normally requiring administrative privileges.
* Hard or unreliable trigger / special condition: -1
  Trigger requires `xfs_buf_alloc_backing_mem()` failure plus the relevant XFS repair path.

Conservative total is floored at 0.

Paranoid signals:

* Local unprivileged trigger: +1
  Paranoid interpretation allows that a local user may influence memory pressure or operate in an environment with delegated filesystem management.
* Reliable kernel crash / strong DoS: +1
  The crash path is explicit.
* Important filesystem/storage path: +1
  XFS buffer handling and repair paths are security relevant enough for triage visibility.
* Hard or unreliable trigger / special condition: -1
  Allocation failure and specific repair path make exploitation unreliable.

Paranoid total: 2.

Not awarded:

* No generic memory corruption bonus. This is an invalid NULL pointer dereference, not UAF, OOB write, double free, arbitrary write, or type confusion.
* No privilege escalation bonus. No reclaim, overwrite, callback control, refcount abuse, or attacker-controlled reuse is shown.
* No confidentiality or integrity impact. The demonstrated effect is crash only.
* No remote/network signal. This is local filesystem code.

## 3. Reachability analysis

The realistic trigger is local and tied to XFS repair or scrub related handling, with an additional requirement that backing memory allocation fails. In normal deployments, initiating the relevant repair path is administrative, so the conservative interpretation treats this as privileged local DoS.

A lower-privilege paranoid interpretation is possible only if a local user can indirectly create memory pressure and the system exposes delegated filesystem management or automated repair workflows. Containers and namespaces do not obviously make this unprivileged by default, because filesystem repair access is normally host controlled.

The path is not network reachable and is not a common packet or remote protocol parser. Call-site confidence is high for the crash mechanism because the call trace is provided, and medium for reachability because exact product policy around XFS repair access is deployment dependent.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like kernel DoS, not an Important-class vulnerability. The patch prevents a NULL pointer dereference by skipping `folio_put(virt_to_folio(bp->b_addr))` when `bp->b_addr` is NULL.

Theoretical memory-corruption potential is weak because the primitive is an invalid NULL address dereference. Realistic exploitation evidence supports kernel crash only, with no demonstrated confidentiality impact, integrity impact, or privilege escalation path.

## 5. One-sentence report phrase

A NULL pointer dereference in `xfs_buf_free()` can occur after XFS backing memory allocation failure, causing a local kernel crash during XFS repair related handling, but the issue requires special conditions and does not show a privilege escalation or data corruption primitive.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The bug is a constrained NULL dereference with a clear DoS-only outcome, no remote exposure, no UAF or write primitive, and typical privileged reachability.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: xfs: handle NULL b_addr in xfs_buf_free [ Upstream
Commit: ccf6738adcafa5ddbddc4e71b45d8a51b86643c7
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ccf6738adcafa5ddbddc4e71b45d8a51b86643c7

Changed files:
  fs/xfs/xfs_buf.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ccf6738adcafa5ddbddc4e71b45d8a51b86643c7

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-74728 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74728

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 0
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).