[CVE-2026-64068][MODERATE 7.0] netfs: Fix missing locking around retry adding new subreqs [ Upstream

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

CVE: CVE-2026-64068
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: netfs: Fix missing locking around retry adding new subreqs [ Upstream
Commit: 393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64068
Analysis date: Sun, 19 Jul 2026 23:26:44 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A missing spinlock around netfs retry subrequest list updates can race with concurrent list users, causing list corruption or stale subrequest lifetime handling and potentially leading to a local kernel crash, with UAF-like impact requiring manual review.

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

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

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-64068	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: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 'A race in netfs retry handling occurs because retry paths modify stream subrequests without holding the request spinlock while other code may inspect or update the same list. Concurrent list add or delete around retry read or write subrequests can corrupt list state or leave stale subrequest links, and the surrounding code also drops subrequest references after deletion. For the CVSS the PR:L is used for the paranoid score because a local unprivileged process with access to a mounted netfs backed filesystem may be able to trigger retry paths through normal file IO, while reliable triggering still depends on retry timing and filesystem conditions. The issue is not a generic Internet reachable network bug, but a malicious or unstable backing server may help create retry conditions. Impact is at least local denial of service via kernel crash and in worst case may allow confidentiality or integrity impact if list corruption turns into use after free or stale pointer use.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)  SKIP CVE-2026-64068 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: e2d46f2ec332533816417b60933954173f602121 YES  NO NO unknown 	MAYBE	REMOTE LOCK DISK SIMPLEFIX LINUS KPANIC 	-	-	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 a mounted netfs-backed filesystem may trigger retry paths through normal read or write IO when retry conditions occur.

* Memory corruption, Weak/indirect corruption candidate: +1
  The patch fixes unlocked list_del() and list_add() operations on stream->subrequests. This is a kernel linked-list consistency issue, but the patch does not show a controlled overwrite, object replacement, callback control, or arbitrary write.

* Real lifetime corruption: +1
  The surrounding code deletes subrequests from the list and then calls netfs_put_subrequest(). If concurrent list users observe stale entries, a stale pointer or UAF-like condition is plausible.

* Reliable kernel crash / strong DoS: +1
  Concurrent modification of kernel list state can realistically lead to list corruption, invalid traversal, BUG/Oops, or kernel crash.

* Important filesystem/storage path: +1
  netfs retry handling is part of filesystem IO read/write retry infrastructure and can affect network-backed filesystems.

Negative signals:

* Hard or unreliable race / special timing required: -1
  Triggering requires retry timing and concurrent access to the subrequest list.

Conservative total: 4

Paranoid adjustment:

* Keep the same primitive class but treat the list/lifetime race as requiring manual review: +1 effective triage elevation
  This is not a simple DoS-only validation fix. It modifies locking around list mutation and object lifetime paths, so stale list entries and UAF-like behavior are technically plausible even if not demonstrated.

Paranoid total: 5

## 3. Reachability analysis

The likely trigger is local IO against a mounted netfs-backed filesystem, such as a network filesystem using the netfs helpers. A fully remote attacker is not directly implied by the patch because the vulnerable operations occur in the local kernel client retry path. However, a malicious or unstable backing server may help create retry conditions that make the race easier to hit.

Privileges are probably PR:L in practical CVSS terms, not PR:H, if an unprivileged local user can access files on the mounted filesystem and cause normal read or write operations. Namespaces or containers may matter if netfs mounts are exposed inside a container or if a container workload can perform IO on a host-provided network filesystem. Reliable exploitation still depends on retry timing, concurrency, and filesystem behavior.

Call-site confidence: medium. The patch includes the affected retry functions and shows the list mutation and put path, but not all concurrent list users.

## 4. Severity interpretation

This behaves above an ordinary Moderate because it is a race in kernel list and lifetime management, not merely a resource leak or harmless warning. The realistic impact is local denial of service through list corruption or kernel crash. Theoretical memory corruption impact is plausible because stale list entries may interact with subrequest reference dropping, but the patch does not demonstrate attacker-controlled reclaim, arbitrary write, type confusion, callback dispatch, or a concrete LPE primitive.

Therefore, the conservative result is borderline manual review, while the paranoid result is Actionable Moderate at minimum. It should not be auto-closed without review.

## 5. One-sentence report phrase

A missing spinlock around netfs retry subrequest list updates can race with concurrent list users, causing list corruption or stale subrequest lifetime handling and potentially leading to a local kernel crash, with UAF-like impact requiring manual review.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch fixes missing locking around kernel list mutation in retry read/write paths, with nearby reference dropping via netfs_put_subrequest(). This is a race/lifetime class issue with plausible stale pointer or UAF-like consequences, even though a controlled privilege-escalation primitive is not shown.

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

Patch: netfs: Fix missing locking around retry adding new subreqs [ Upstream
Commit: 393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2

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=393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2

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

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

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