[CVE-2026-64160][MODERATE 7.0] netfs: Fix potential for tearing in ->remote_i_size and ->zero_point [ Upstream

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

CVE: CVE-2026-64160
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: netfs: Fix potential for tearing in ->remote_i_size and ->zero_point [ Upstream
Commit: 55970f238d495517edc961d55c44c772594d0969
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=55970f238d495517edc961d55c44c772594d0969
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64160
Analysis date: Sun, 19 Jul 2026 14:22:41 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: NO

Summary:
A race in netfs size handling can expose torn or inconsistent `remote_i_size` and `zero_point` values, allowing local users with access to affected mounted network filesystems to trigger incorrect I/O behavior, possible stale or zero-filled data handling, and availability issues.

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

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

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-64160	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	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-667;CWE-662;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H';BEST CVSS score: '5.8';DESCR 'A race in netfs size handling can expose torn or inconsistent 64-bit values for remote_i_size and zero_point, especially on 32-bit systems. These fields affect decisions about the real remote file size and the point above which reads may be treated as zero filled, so inconsistent values can cause wrong I/O behavior, stale or incorrect data handling, and availability problems such as hangs or repeated seqcount retries. For the CVSS the PR:L because an unprivileged local process with access to an affected mounted netfs file can trigger concurrent I/O paths, although reliable triggering may also depend on filesystem permissions, mount configuration, and server behavior. The issue is not directly network reachable as a standalone packet attack against the kernel, but exposure is higher when network filesystem clients such as 9p, AFS, or SMB are mounted and used with concurrent local and remote size changes. Impact is at least local denial of service and possible low integrity impact. For the paranoid score, low confidentiality impact is also kept for manual-review sensitivity because incorrect size and zero point state may affect cached or remote read boundaries.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	WRITE OOB LOCK DISK HARDWARE LINUS KPANIC  KPANIC LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS 	YES	NO	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

Triggered signals:

* Local unprivileged trigger: +1
  A local user with access to an affected mounted netfs-backed filesystem can exercise read/write/getattr paths that consume `remote_i_size` and `zero_point`.

* Memory layout invariant restoration: +1
  The patch restores consistency between related size fields: `i_size`, `remote_i_size`, `zero_point`, and the shared `i_size_seqcount` locking model.

* Filesystem/storage metadata correctness impact: +1
  The affected fields control remote file size, zero-fill boundaries, cache behavior, and write/read decisions in netfs users such as 9p, AFS, and SMB/CIFS.

* Important filesystem/storage path: +1
  The bug is in netfs/page-cache-facing filesystem I/O paths, not merely in a debug or administrative path.

* Availability impact realistic: +1 paranoid only
  The commit explicitly mentions preventing `i_size_seqcount` corruption, and related code comments note that broken sequencing can make `i_size_read()` loop forever on 32-bit systems.

* Integrity impact plausible: +1 paranoid only
  Torn or inconsistent `zero_point` / `remote_i_size` can cause incorrect I/O decisions, stale data behavior, or wrong zero-fill handling.

Subtracted signals:

* Hard or unreliable race / special timing required: -1
  The issue depends on concurrent size updates and reads, especially relevant on 32-bit systems or during concurrent local and remote filesystem activity.

Not counted:

* No generic strong memory corruption bonus.
  The patch does not show UAF, OOB write, double-free, refcount takeover, type confusion, arbitrary write, or attacker-controlled object reuse.

* No remote reachable bonus.
  Network filesystems are involved, but this is not a standalone packet-triggerable kernel network parser bug.

## 3. Reachability analysis

A local user can potentially trigger affected paths by accessing files on mounted 9p, AFS, SMB/CIFS, or other netfs users while size state changes concurrently. Reliable triggering depends on filesystem permissions, mount availability, architecture, and server-side behavior.

Namespaces and containers may matter if a container or sandbox is given access to an affected mounted network filesystem. This does not normally require host-root once the filesystem is mounted, so PR:L is the practical interpretation for triage.

The path is not universally default-enabled because it requires an affected netfs-backed filesystem to be mounted. However, SMB/CIFS, 9p, and AFS are real deployment paths, so this should not be treated as rare kernel dead code.

Call-site confidence: high. The provided patch shows multiple concrete read and write sites across 9p, AFS, SMB/CIFS, and netfs buffered/direct I/O paths.

## 4. Severity interpretation

This behaves more like an actionable Moderate than an ordinary Low/Moderate cleanup. The realistic impact is size-state inconsistency, wrong I/O behavior, possible hangs, and filesystem/cache correctness problems.

Theoretical memory corruption potential is weak. The patch protects scalar size fields and seqcount synchronization rather than object lifetime or pointer ownership. There is no demonstrated LPE primitive. The paranoid score is elevated because filesystem size and cache boundary corruption can have subtle integrity and availability effects that deserve manual review.

## 5. One-sentence report phrase

A race in netfs size handling can expose torn or inconsistent `remote_i_size` and `zero_point` values, allowing local users with access to affected mounted network filesystems to trigger incorrect I/O behavior, possible stale or zero-filled data handling, and availability issues.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

This is not a strong memory-corruption or LPE candidate, but it affects network filesystem size and cache semantics across several real filesystems. The combination of race, seqcount corruption risk, and possible data correctness impact makes it unsuitable for automatic closure.

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

Patch: netfs: Fix potential for tearing in ->remote_i_size and ->zero_point [ Upstream
Commit: 55970f238d495517edc961d55c44c772594d0969
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=55970f238d495517edc961d55c44c772594d0969

Changed files:
  fs/9p/v9fs_vfs.h
  fs/9p/vfs_inode.c
  fs/9p/vfs_inode_dotl.c
  fs/afs/file.c
  fs/afs/inode.c
  fs/afs/internal.h
  fs/afs/write.c
  fs/netfs/buffered_read.c
  fs/netfs/buffered_write.c
  fs/netfs/direct_write.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=55970f238d495517edc961d55c44c772594d0969

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

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

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