Answer in brief
CVE-2026-98843 records a Unknown severity vulnerability in netfs: zero gaps in read-gaps folio to avoid writing back stale data. 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 | >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <512eaf01ffabf4258e945016b50df5aed940b705 || >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <2a62fe628a877c249c8286b157ee99d82840d9dc || >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <8db55c5cd831a786a1a2a2d391aa80354535a353 | 512eaf01ffabf4258e945016b50df5aed940b705, 2a62fe628a877c249c8286b157ee99d82840d9dc, 8db55c5cd831a786a1a2a2d391aa80354535a353 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: netfs: zero gaps in read-gaps folio to avoid writing back stale data netfs_read_gaps() leaves gaps around a streaming write's dirty region unread on the server side, so a short/EOF response there left stale folio content that later got written back. Zero it after the read completes, not before: netfs_wait_for_read() returns rreq->transferred once ret >= 0, so build an iterator over the same bvec array the read used, advance past ret, and zero the rest. The dirty region already maps to sink pages in that array rather than the real folio, so this can't touch it, and only the actual shortfall gets zeroed instead of the whole gap upfront.
Quoted source text, attributed separately from HOL analysis.