[CVE-2026-72372][MODERATE 7.0] afs: Fix lack of locking around modifications of net->cells_dyn_ino [ Upstream

[CVE-2026-72372][MODERATE 7.0] afs: Fix lack of locking around modifications of net->cells_dyn_ino [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72372
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: afs: Fix lack of locking around modifications of net->cells_dyn_ino [ Upstream
Commit: 4d8a2fe8847859f4fa4e9a2fa1221c9c1158e66b
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4d8a2fe8847859f4fa4e9a2fa1221c9c1158e66b
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72372
Analysis date: Sat, 15 Aug 2026 17:44:57 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: NO

Summary:
AFS dynroot cell management modifies net->cells_dyn_ino without proper cells_lock serialization, allowing local filesystem operations to race cell allocation or removal and potentially cause stale object access, IDR corruption, or a kernel crash.

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

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

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: NO

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

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

CVE-2026-72372	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-362;CWE-667;*CWE-416;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'AFS dynroot cell management can race because net cells_dyn_ino was modified without holding cells_lock. Concurrent add remove or readdir related paths may observe inconsistent IDR state or stale afs_cell pointers, which makes this more than a simple warning and creates a plausible use-after-free or kernel memory corruption candidate. For the CVSS the PR:L is used because a local user with access to an AFS dynroot mount may trigger lookup or readdir paths and cell lifetime changes without full administrator privileges, although reliable triggering depends on the deployment. The issue is not directly network reachable. Impact is at least local denial of service via kernel crash and in the paranoid case may include confidentiality and integrity impact due to IDR corruption or stale pointer reuse.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)  SKIP CVE-2026-72372 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 1d0b929fc070b4115403a0a6206a0c6a62dd61f5 YES  NO NO unknown 	MAYBE	LOCK DISK SIMPLEFIX SKIP LINUS  INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	-	-	checked

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

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1
  A local user with access to an AFS dynroot mount may be able to trigger lookup or readdir paths.
* Memory corruption, weak/indirect corruption candidate: +1
  The bug is an unlocked IDR modification around kernel object pointers, which can plausibly create inconsistent IDR state or stale object observation.
* Real lifetime corruption: +1
  The patch moves idr_remove() out of the RCU cleanup callback and serializes it with cells_lock, indicating a lifetime and synchronization issue around afs_cell objects.
* Reliable kernel crash / strong DoS concern: +1
  Concurrent IDR add/remove/read style races in kernel object registries can realistically result in crashes, even if no concrete KASAN trace is provided.
* Important filesystem namespace path: +1
  The affected code is in AFS dynroot namespace construction and readdir/lookup related paths.
* Hard or unreliable race / special timing required: -1
  Exploitation depends on racing cell allocation/removal or dynroot enumeration.

Paranoid adjustment:

* Do not subtract hard race: +1 relative to conservative
  If AFS dynroot cell churn is naturally triggerable under workload, the race may be reproducible enough to justify not applying the timing penalty.

I would not award strong LPE +2 because the patch does not show attacker-controlled reclaim, controlled overwrite, callback dispatch, refcount takeover, or a demonstrated object replacement primitive.

## 3. Reachability analysis

The issue is local, not directly network reachable. A remote AFS server may influence some AFS behavior, but the vulnerable operation is local kernel management of net->cells_dyn_ino and dynroot cell state.

Typical triggering requires an AFS setup with dynroot enabled and local access to paths that cause cell lookup, readdir, or cell lifecycle changes. This is not a default high-exposure subsystem on most general-purpose Linux systems, but it is reachable through ordinary filesystem operations when AFS is configured.

Namespaces may matter if AFS mounts are exposed inside a container or to a reduced-privilege service account. In that case PR:L is more appropriate than PR:H because the attacker does not need full host-root privileges to exercise the mounted filesystem path.

Call-site confidence: medium. The patch includes the modified allocation, destruction, and dynroot readdir context, but not all possible lookup and lifecycle callers.

## 4. Severity interpretation

This behaves like an actionable Moderate rather than an ordinary Low/Moderate cleanup. The evidence supports a real synchronization and lifetime issue around a kernel IDR containing afs_cell pointers.

Realistic impact is most likely local DoS through kernel crash or corrupted internal state. Theoretical memory corruption potential exists because stale or inconsistent IDR entries may expose freed or partially destroyed objects, but practical privilege escalation is not demonstrated by the patch.

The paranoid score is therefore raised to 5 for manual triage sensitivity, but not to Important-class solely on speculation.

## 5. One-sentence report phrase

AFS dynroot cell management modifies net->cells_dyn_ino without proper cells_lock serialization, allowing local filesystem operations to race cell allocation or removal and potentially cause stale object access, IDR corruption, or a kernel crash.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

This is a race and lifetime bug around kernel object pointers in an IDR, so it should not be auto-closed, but the supplied patch does not demonstrate a strong exploitation primitive beyond plausible crash or weak memory corruption.

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

Patch: afs: Fix lack of locking around modifications of net->cells_dyn_ino [ Upstream
Commit: 4d8a2fe8847859f4fa4e9a2fa1221c9c1158e66b
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4d8a2fe8847859f4fa4e9a2fa1221c9c1158e66b

Changed files:
  fs/afs/cell.c
  fs/afs/dynroot.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=4d8a2fe8847859f4fa4e9a2fa1221c9c1158e66b

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

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

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: 5

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