netfs: zero gaps in read-gaps folio to avoid writing back stale data
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ee4cdf7ba857a894ad1650d6ab77669cbbfa329e · fixed in 512eaf01ffabf4258e945016b50df5aed940b705; From ee4cdf7ba857a894ad1650d6ab77669cbbfa329e · fixed in 2a62fe628a877c249c8286b157ee99d82840d9dc; From ee4cdf7ba857a894ad1650d6ab77669cbbfa329e · fixed in 8db55c5cd831a786a1a2a2d391aa80354535a353
- Linux Linux
6.12
- KernelLinux
From 6.12.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10