[CVE-2026-72371][MODERATE 7.0] afs: Fix the volume AFS_VOLUME_RM_TREE is set on [ Upstream

[CVE-2026-72371][MODERATE 7.0] afs: Fix the volume AFS_VOLUME_RM_TREE is set on [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72371
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: afs: Fix the volume AFS_VOLUME_RM_TREE is set on [ Upstream
Commit: 6fa9a8a73e16aa22fce6e41cc00d59c767f0a540
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6fa9a8a73e16aa22fce6e41cc00d59c767f0a540
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72371
Analysis date: Sat, 15 Aug 2026 14:38:12 -0400
ActionableScore: 6
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A wrong AFS volume removal flag can cause the replaced volume to be removed from the cell rb tree twice while the new volume remains with incorrect lifetime state, creating a local DoS and possible UAF style memory corruption candidate when AFS is configured.

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

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

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 7.0
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-72371	MODERATE	CHECK WITH IMPACT FROM ORIG NN NONE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;*CWE-672;CWE-362;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'AFS volume insertion can mark the wrong object with AFS_VOLUME_RM_TREE when replacing an existing volume in the cell rb tree. The old volume can later be removed from the tree a second time while the new volume may remain without the expected removal state, creating a stale object and double remove condition in kernel AFS volume lifetime handling. For the CVSS the PR:L is used for the paranoid score because a local unprivileged user may be able to trigger AFS volume lookup or replacement when AFS is configured, while full administrator rights are not inherently required for filesystem access. The issue is not treated as a direct unauthenticated remote network bug because practical triggering appears to depend on a configured AFS client and local filesystem activity. Impact is at least local denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to UAF style memory corruption, so it should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	DISK RACE UAF SKIP LINUS  KPANIC INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS	YES	NO	checked

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

ActionableScore=6
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 6
* Final recommended bucket: **Actionable Moderate at minimum**

## 2. Signal breakdown

Conservative signals:

* +1 Local unprivileged trigger: if AFS is configured and mounted, ordinary local filesystem activity may trigger AFS volume lookup or replacement paths.
* +1 Memory corruption, weak/indirect corruption candidate: the wrong object gets the `AFS_VOLUME_RM_TREE` flag, causing stale tree state and wrong lifetime bookkeeping.
* +1 Real lifetime corruption: the bug affects volume lifetime state in an RCU protected rb tree and can cause the replaced object to be removed twice.
* +1 Reliable kernel crash / strong DoS: double removal from a kernel tree is a credible crash or tree corruption scenario.

Paranoid additional interpretation:

* +1 Upgrade from weak to stronger corruption concern: the commit explicitly says the old volume is removed from the tree twice and the new volume is never removed, which is more serious than ordinary bookkeeping.
* +1 Weak LPE concern: no exploit primitive is demonstrated, but stale object lifetime and double removal in kernel object management justify manual review for possible UAF style consequences.

Not applied:

* Remote reachable +2: not applied. This is not a direct unauthenticated remote network parser path.
* Requires admin/root -2: not applied as a blanket penalty, because a local user may trigger filesystem lookup activity once AFS is already configured.
* Rare subsystem -1: not applied in the main score because niche AFS deployment does not make the reachable local filesystem path inherently difficult once mounted.

Call-site confidence: medium. The patch shows only the local helper change, but the commit message clearly states the wrong object lifetime consequence.

## 3. Reachability analysis

The realistic trigger requires an AFS client configuration where volume insertion or replacement can occur. A local user with access to the mounted AFS filesystem may be able to trigger relevant lookup or volume activity without full administrator privileges. The issue is not a direct remote network vulnerability, although AFS server or cell state may influence whether the replacement path is reached. Containers and namespaces matter only if they expose the mounted AFS filesystem or relevant filesystem operations to less privileged workloads.

## 4. Severity interpretation

This is not an ordinary low-risk cleanup because it affects object lifetime state in an RCU protected volume tree. The conservative interpretation is local DoS through kernel crash or tree corruption. The paranoid interpretation treats the double removal and stale volume state as a UAF style memory corruption candidate, but there is no demonstrated reclaim, overwrite, callback control, or arbitrary write primitive. Therefore it is best treated as Actionable Moderate at minimum, with Important-class review possible if source review confirms exploitable stale object reuse.

## 5. One-sentence report phrase

A wrong AFS volume removal flag can cause the replaced volume to be removed from the cell rb tree twice while the new volume remains with incorrect lifetime state, creating a local DoS and possible UAF style memory corruption candidate when AFS is configured.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch is small, but it affects RCU rb tree object lifetime and explicitly describes double removal plus missed removal, which is a classic area where UAF or memory corruption impact may be underestimated.

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

Patch: afs: Fix the volume AFS_VOLUME_RM_TREE is set on [ Upstream
Commit: 6fa9a8a73e16aa22fce6e41cc00d59c767f0a540
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6fa9a8a73e16aa22fce6e41cc00d59c767f0a540

Changed files:
  fs/afs/volume.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=6fa9a8a73e16aa22fce6e41cc00d59c767f0a540

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

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

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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 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: 4
  Paranoid ActionableScore: 6

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: YES
Published priority for this report (same as in Subject): MODERATE 7.0

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