[CVE-2026-72364][MODERATE REGULAR] netfs: Fix writeback error handling [ Upstream

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

CVE: CVE-2026-72364
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: netfs: Fix writeback error handling [ Upstream
Commit: fb39ffd3cc5422887fd118668ff45ebfdbc83302
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fb39ffd3cc5422887fd118668ff45ebfdbc83302
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72364
Analysis date: Sat, 15 Aug 2026 20:31:20 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline Moderate. Manual review recommended
Manual review required: YES

Summary:
A netfs writeback error path could fail to properly re enter writeback_iter() and redirty or unlock the current folio, potentially causing stuck writeback state or loss of pending file data after writeback failure.

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

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

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-72364	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	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:H/A:L';CWE-703;CWE-754;*CWE-664;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '5.3';DESCR 'netfs writeback error handling could leave the writeback iterator state uncleared and the current folio not properly redirtied or unlocked after a writeback failure. This can cause incorrect dirty page handling, stuck writeback state, or possible loss of pending file data on a netfs backed filesystem. For the CVSS the PR:L is used because a local user or process normally needs write access to a mounted netfs filesystem and must trigger writeback under error conditions. The issue is not directly network reachable as an unauthenticated packet based attack, although remote server or backend failures may help create the error condition. Impact is mainly local denial of service and possible data integrity loss, with no evidence of privilege escalation or arbitrary kernel memory corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline Moderate. Manual review recommended (with actual score 4)  SKIP CVE-2026-72364 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 288ace2f57c9d06dd2e42bd80d03747d879a4068 YES  NO NO unknown 	MAYBE	REMOTE LOCK DISK NOMEMCHK SIMPLEFIX ERRORPATH LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=4
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline Moderate. Manual review recommended**::

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1. A local user or process with write access to a mounted netfs-backed filesystem can plausibly reach writeback paths.
* Important filesystem/storage path: +1. The bug is in filesystem writeback and folio dirty/writeback state handling.
* Integrity impact plausible: +1. Incorrect redirty or cleanup handling may cause pending data to be lost or mishandled after writeback failure.
* Availability impact realistic: +1. A locked folio or uncleared iterator/writeback state can plausibly cause stuck writeback or filesystem-level disruption.
* Special error-path condition: -1. Triggering depends on writeback failure conditions such as ENOMEM or backend/write initiation errors, not a simple deterministic syscall path.

Paranoid additional signal:

* Filesystem/storage data-state corruption reachable by local user: +1. The affected state controls whether dirty file data remains pending, is redirtied, or is incorrectly cleaned up after failure.

Not awarded:

* No remote reachable signal. This is not directly packet-triggerable.
* No generic memory corruption. The patch does not show UAF, OOB write, double free, refcount takeover, or object confusion.
* No privilege escalation signal. No LPE primitive is supported by the patch.
* No Dirty-Pipe-like ownership/COW violation. The bug concerns writeback cleanup, not writes into another file or shared page across an ownership boundary.

## 3. Reachability analysis

The realistic trigger is local access to a mounted netfs-backed filesystem plus write activity that enters writeback and then hits an error path. Ordinary unprivileged users may trigger the path if they can write files on such a mount, but reliable reproduction likely requires memory pressure, backend failure, write initiation failure, or similar error conditions.

Namespaces or containers can matter if the container is given access to the affected mount. The issue does not require CAP_SYS_ADMIN once the mount exists, but setting up the mount usually does. Remote servers may contribute to failure conditions, but the bug is not an unauthenticated remote network parser issue.

Call-site confidence: high, because the changed loop and cleanup path in netfs_writepages() are present in the supplied patch.

## 4. Severity interpretation

This behaves like a borderline actionable Moderate rather than an Important-class kernel vulnerability. The main concern is filesystem writeback correctness, possible data integrity loss, and stuck writeback state. There is no concrete memory corruption or privilege escalation primitive in the patch.

The conservative score stays low because triggering depends on an error path. The paranoid score is higher because filesystem writeback bugs can cause persistent user-data integrity impact and should not be auto-closed without at least manual review.

## 5. One-sentence report phrase

A netfs writeback error path could fail to properly re enter writeback_iter() and redirty or unlock the current folio, potentially causing stuck writeback state or loss of pending file data after writeback failure.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: no memory corruption or LPE primitive is evident, but the bug affects filesystem writeback correctness and may cause persistent data integrity impact.

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

Patch: netfs: Fix writeback error handling [ Upstream
Commit: fb39ffd3cc5422887fd118668ff45ebfdbc83302
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fb39ffd3cc5422887fd118668ff45ebfdbc83302

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=fb39ffd3cc5422887fd118668ff45ebfdbc83302

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

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

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:N/I:H/A:L
  The Best / paranoid CVSS score: 5.3

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

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