[CVE-2026-72355][MODERATE 7.0] netfs: Fix barriering when walking subrequest list [ Upstream

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

CVE: CVE-2026-72355
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: netfs: Fix barriering when walking subrequest list [ Upstream
Commit: be47c047250671c9225c0319ca4695be9b391c59
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be47c047250671c9225c0319ca4695be9b391c59
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72355
Analysis date: Sat, 15 Aug 2026 11:53:15 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A netfs retry-list memory-ordering race can let read or write retry code observe a newly added subrequest before its state is safely visible, creating possible I/O failure or limited data-integrity impact for local users able to perform I/O on an affected netfs mount.

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

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

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-72355	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';CWE-362;CWE-662;CWE-667;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '5.8';DESCR 'A race in netfs retry handling can expose a newly added subrequest to the retry walker before the subrequest state is safely visible on the current CPU. The retry path then reads fields such as start, transferred, and flags and may make retry decisions based on stale or partially visible state. For the CVSS the PR:L is used in the paranoid score because a local user or process that can perform I/O on an affected netfs mount may be able to create concurrent subrequests while retry handling is active. The issue is not directly network reachable from packet traffic, although a remote or unreliable storage backend may help create retry conditions. Impact is at least local denial of service or I/O failure, and in the paranoid interpretation may include limited confidentiality or integrity impact plus high availability impact due to incorrect retry processing.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)  SKIP CVE-2026-72355 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: ee4cdf7ba857a894ad1650d6ab77669cbbfa329e YES  NO NO unknown 	MAYBE	REMOTE DISK SIMPLEFIX LINUS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=5
ActionableScoreLower=3

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1. A local process that can perform I/O on an affected netfs mount may create concurrent read/write subrequests.
* Important filesystem/storage path: +1. The bug is in netfs read and write retry handling, including writeback-related paths.
* Integrity impact plausible: +1. The retry walker may read stale or not yet visible subrequest state and make incorrect retry decisions, especially in write retry handling.
* Availability impact realistic: +1. Incorrect retry handling can plausibly cause I/O failure, stalled retry processing, or filesystem-level disruption.
* Hard or unreliable race / special timing required: -1. The issue depends on a concurrency and memory-ordering window where a newly added subrequest is observed before its state is safely visible.

Paranoid additional signals:

* Memory corruption, weak/indirect corruption candidate: +1. This is not a proven UAF or OOB write, but the walker may consume a list entry before associated object state is consistently visible.
* Broad/common filesystem infrastructure exposure: +1. netfs is shared infrastructure used by multiple network filesystem clients, so the affected helper path is more important than a narrow driver-local bug.

Not awarded:

* No remote reachable score. Packet traffic alone does not directly trigger the bug.
* No strong memory corruption score. The patch shows memory ordering around list traversal, not free/reuse, OOB write, or controlled overwrite.
* No privilege escalation score. There is no demonstrated reclaim, callback control, arbitrary write, or credential/security-boundary primitive.

## 3. Reachability analysis

The likely trigger is a local user or process doing I/O on a mounted filesystem using netfs infrastructure while retry handling is active. A remote or unreliable storage backend may help create retry conditions, but the vulnerable operation is not directly reachable as a network packet parser or unauthenticated remote service.

Namespaces and containers may matter if the container can access an affected mount and generate filesystem I/O, but mounting or configuring the backend itself is typically privileged. The path is not always active by default, but netfs is a common shared filesystem layer and should not be treated as an obscure hardware-only path.

Call-site confidence: high for the shown read_retry and write_retry loops. Medium for downstream impact, because the patch does not show a concrete crash trace or corruption result.

## 4. Severity interpretation

This behaves more like an actionable Moderate than an ordinary low Moderate. The realistic impact is probably incorrect retry behavior, I/O failure, or limited data-integrity risk rather than reliable privilege escalation.

The theoretical concern is that a race in filesystem retry state can cause stale or partially visible state to influence read/write retry decisions. However, the patch does not demonstrate UAF reclaim, write-after-free, type confusion, arbitrary write, or a Dirty-Pipe-like ownership bypass. Therefore it should not be classified as Important solely from the patch, but it should not be auto-closed without review.

## 5. One-sentence report phrase

A netfs retry-list memory-ordering race can let read or write retry code observe a newly added subrequest before its state is safely visible, creating possible I/O failure or limited data-integrity impact for local users able to perform I/O on an affected netfs mount.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED.
YES REQUIRES MANUAL CHECK because this is a race in shared filesystem read/write retry handling with plausible integrity and availability impact, even though no strong memory-corruption or privilege-escalation primitive is proven by the patch.

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

Patch: netfs: Fix barriering when walking subrequest list [ Upstream
Commit: be47c047250671c9225c0319ca4695be9b391c59
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be47c047250671c9225c0319ca4695be9b391c59

Changed files:
  fs/netfs/read_retry.c
  fs/netfs/write_retry.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=be47c047250671c9225c0319ca4695be9b391c59

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

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

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

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