[CVE-2026-72366][LOW] netfs: Fix netfs_create_write_req() to handle async cache object creation [ Upstream

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

CVE: CVE-2026-72366
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: netfs: Fix netfs_create_write_req() to handle async cache object creation [ Upstream
Commit: 8ab75e445c161c4cb504aa98e20ce1dd1ecd8e9a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8ab75e445c161c4cb504aa98e20ce1dd1ecd8e9a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72366
Analysis date: Sun, 16 Aug 2026 05:35:32 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
netfs_create_write_req() could skip fscache write setup during async cache object creation, causing eligible writes to bypass local cache handling, with at most weak cache consistency impact and no demonstrated memory corruption or privilege escalation.

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

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

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

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

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

CVE-2026-72366	LOW	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:N/I:L/A:N';CWE-362;CWE-703;CWE-754;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:N';BEST CVSS score: '2.5';DESCR 'netfs_create_write_req() could skip fscache_begin_write_operation() because it checked whether the fscache cookie was enabled before async cache object creation had completed. This can cause eligible write requests to bypass local cache write setup and may lead to missing cache updates or weak cache consistency effects on systems using netfs with fscache. For the CVSS the PR:L is used for the paranoid score because a local authenticated user may be able to trigger the write path on an already configured cached netfs mount, while creating or configuring the mount itself is usually administrative. The issue is not directly network reachable as an attack vector even though netfs may back network filesystems. Impact is best treated as no direct security impact for the base score, with only low integrity impact in the paranoid interpretation. There is no evidence of memory corruption, kernel crash, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-72366 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 7b589a9b45ae32aa9d7bece597490e141198d7a6 YES  NO NO unknown 	MAYBE	REMOTE DISK SIMPLEFIX LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

* Local unprivileged trigger: +1 in the paranoid interpretation. A local authenticated user may trigger the write path by writing to an already configured cached netfs mount.
* Integrity impact plausible: +1 was considered, but not counted in the final paranoid score together with the timing/configuration limitation because the impact is only weak cache consistency, not primary file corruption.
* Hard or timing-dependent async state window: -1. The issue depends on async cache object creation not yet reaching the enabled state.
* Rare/configuration-dependent exposure: effectively limiting. The affected behavior requires netfs with fscache caching enabled and relevant async cache object creation timing.
* No memory corruption signal. The patch only removes a premature enabled-cookie check before fscache_begin_write_operation().
* No reliable crash or strong DoS signal.
* No privilege escalation signal.
* Call-site confidence: medium. The changed call site is visible, but broader cache consistency consequences are inferred from netfs/fscache semantics and the commit message.

## 3. Reachability analysis

A local user can plausibly reach the write path only if the system already has a cached netfs mount configured by an administrator. Network reachability is not a direct attack vector, even if the backing filesystem may be remote. Namespaces or containers do not significantly improve reachability unless they are already granted access to such a mount. The realistic effect is skipped local cache write setup during a narrow async object creation window.

## 4. Severity interpretation

This behaves more like a low-risk correctness or cache-consistency issue than an actionable security vulnerability. Theoretical integrity impact is limited to missing or inconsistent local cache updates. There is no evidence of UAF, OOB access, stale pointer reuse, page-cache corruption, unauthorized cross-file writes, kernel crash, information disclosure, or privilege escalation.

## 5. One-sentence report phrase

netfs_create_write_req() could skip fscache write setup during async cache object creation, causing eligible writes to bypass local cache handling, with at most weak cache consistency impact and no demonstrated memory corruption or privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch is a one-line state-handling correction with no concrete corruption primitive, no crash path, no direct security boundary bypass, and only weak configuration-dependent cache consistency impact.

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

Patch: netfs: Fix netfs_create_write_req() to handle async cache object creation [ Upstream
Commit: 8ab75e445c161c4cb504aa98e20ce1dd1ecd8e9a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8ab75e445c161c4cb504aa98e20ce1dd1ecd8e9a

Changed files:
  fs/netfs/write_issue.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=8ab75e445c161c4cb504aa98e20ce1dd1ecd8e9a

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

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

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

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