netfs: Fix potential for tearing in ->remote_i_size and ->zero_point (CVE-2026-64160) | HOL Guard CVE

Critical · CVSS 9.8CVE-2026-64160

netfs: Fix potential for tearing in ->remote_i_size and ->zero_point

Answer in brief

CVE-2026-64160 records a Critical severity (CVSS 9.8) vulnerability in netfs: Fix potential for tearing in ->remote_i_size and ->zero_point. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 19, 2026Updated Aug 17, 2026Source checked Sep 20, 2026First seen by HOL Aug 5, 2026Material review Aug 17, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.8
Exploitation: Not marked as known exploited
Affected software: 7 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:o:linux:linux_kernel::::::::	Not reported	Not reported
cpe:2.3:o:linux:linux_kernel:7.1:rc1::::::	Not reported	Not reported
cpe:2.3:o:linux:linux_kernel:7.1:rc2::::::	Not reported	Not reported
cpe:2.3:o:linux:linux_kernel:7.1:rc3::::::	Not reported	Not reported
cpe:2.3:o:linux:linux_kernel:7.1:rc4::::::	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 <55970f238d495517edc961d55c44c772594d0969 \|\| >=4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 <2c8f4742bb76117d735f92a3932d85239b16c494	55970f238d495517edc961d55c44c772594d0969, 2c8f4742bb76117d735f92a3932d85239b16c494
Linux/Linuxgeneric	5.18	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 55970f238d495517edc961d55c44c772594d0969 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 5, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential for tearing in ->remote_i_size and ->zero_point Fix potential tearing in using ->remote_i_size and ->zero_point by copying i_size_read() and i_size_write() and using the same seqcount as for i_size. We need to make sure that netfslib and the filesystems that use it always hold i_lock whilst updating any of the sizes to prevent i_size_seqcount from getting corrupted.

Quoted source text, attributed separately from HOL analysis.