Answer in brief
CVE-2026-64160 records a Unknown severity 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.
A CVSS score is not reported in the current record. 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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 <55970f238d495517edc961d55c44c772594d0969 || >=4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 <2c8f4742bb76117d735f92a3932d85239b16c494 | 55970f238d495517edc961d55c44c772594d0969, 2c8f4742bb76117d735f92a3932d85239b16c494 |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Answer in brief
CVE-2026-64160 records a Unknown severity 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.
A CVSS score is not reported in the current record. 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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 <55970f238d495517edc961d55c44c772594d0969 || >=4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 <2c8f4742bb76117d735f92a3932d85239b16c494 | 55970f238d495517edc961d55c44c772594d0969, 2c8f4742bb76117d735f92a3932d85239b16c494 |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.