[CVE-2026-74321][MODERATE REGULAR] btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-74321
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() [ Upstream
Commit: c372ca227e16bace86f1df1fa4ae6849e2fcfa28
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c372ca227e16bace86f1df1fa4ae6849e2fcfa28
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74321
Analysis date: Sat, 15 Aug 2026 08:42:29 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Borderline manual review recommended
Manual review required: YES

Summary:
A local btrfs delayed-reference handling bug can reuse `ERR_PTR(-EAGAIN)` as a locked ref head and dereference it in `spin_lock()`, causing a kernel crash through filesystem activity.

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

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

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: MODERATE REGULAR
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-74321	MODERATE	CHECK WITH IMPACT FROM ORIG NN NONE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/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:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'An invalid pointer dereference in btrfs delayed refs processing can occur when btrfs_select_ref_head() returns ERR_PTR(-EAGAIN) and locked_ref is reused on the next loop iteration. The next iteration can treat the error pointer as a valid delayed ref head and call spin_lock() on it, causing a kernel crash or oops. For the CVSS the PR:L is used because a local user with write access to a btrfs filesystem may be able to trigger delayed reference processing through normal filesystem activity. The issue is not network reachable and requires local filesystem interaction. Impact is denial of service via kernel crash. The patch context supports an invalid pointer dereference, not a UAF or controlled memory corruption primitive, so confidentiality and integrity are not raised in the grounded score.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended (with actual score 3)	YES	DISK SKIP  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

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

ActionableScore=3
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 3
* Final recommended bucket: **Borderline manual review recommended**::

## 2. Signal breakdown

Triggered signals:

* Local unprivileged trigger: +1
  A local user with write access to a mounted btrfs filesystem may be able to cause delayed reference processing through normal filesystem activity.

* Reliable kernel crash / strong DoS: +1
  The commit explicitly describes `spin_lock(&locked_ref->lock)` being executed on `ERR_PTR(-EAGAIN)`, causing an invalid pointer dereference and likely kernel oops or panic.

* Important filesystem/storage path: +1
  The affected code is in btrfs delayed reference processing, which is part of filesystem metadata transaction handling.

Negative or limiting signals:

* Hard or unreliable trigger: -1 in conservative score
  The crash depends on `btrfs_select_ref_head()` returning `-EAGAIN` in this loop state. The patch shows the bug clearly, but the input does not prove that an ordinary user can trigger it reliably on demand.

Not awarded:

* No generic strong memory corruption bonus. This is an invalid error-pointer dereference, not UAF, OOB write, double-free, refcount takeover, or attacker-controlled overwrite.
* No privilege escalation bonus. The patch does not show reclaim, object replacement, callback control, type confusion, or write primitive.
* No confidentiality or integrity impact. The supported impact is crash/DoS only.

## 3. Reachability analysis

The bug is local and requires interaction with a mounted btrfs filesystem. A non-root user may plausibly reach the affected path if they can write to btrfs and generate metadata activity that causes delayed refs to run. Namespaces do not obviously reduce the requirement unless the attacker has access to a btrfs mount from a container or delegated environment. The path is not network reachable. Btrfs is a common but not universal filesystem, and the affected path is important when btrfs is used.

Call-site confidence: high for the invalid dereference behavior because the commit shows the faulty loop state and dereference. Medium for unprivileged trigger reliability because the exact conditions for repeated `-EAGAIN` are not fully demonstrated in the supplied context.

## 4. Severity interpretation

This behaves like a local filesystem-triggered DoS, not an Important-class memory corruption issue. The theoretical kernel fault is real, but the primitive is an invalid pointer dereference of an `ERR_PTR(-EAGAIN)` value rather than controllable memory corruption. The practical risk is kernel crash or filesystem transaction disruption. Manual review is useful mainly to confirm whether unprivileged users can reliably trigger the `-EAGAIN` path under realistic btrfs workloads.

## 5. One-sentence report phrase

A local btrfs delayed-reference handling bug can reuse `ERR_PTR(-EAGAIN)` as a locked ref head and dereference it in `spin_lock()`, causing a kernel crash through filesystem activity.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Recommended because this is a kernel crash in an important filesystem path and may be reachable by local unprivileged users with write access to btrfs, but the patch supports DoS only and does not show a privilege escalation primitive.

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

Patch: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() [ Upstream
Commit: c372ca227e16bace86f1df1fa4ae6849e2fcfa28
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c372ca227e16bace86f1df1fa4ae6849e2fcfa28

Changed files:
  fs/btrfs/extent-tree.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=c372ca227e16bace86f1df1fa4ae6849e2fcfa28

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

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

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:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

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: 2
  Paranoid ActionableScore: 3

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: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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).