Live › vulnerability › CVE-2026-98843
Go to dashboardIn the Linux kernel's netfs layer, gaps around a streaming write's dirty region were left unread, so a short or end-of-file server response could leave stale folio content. That stale content could then be written back, so data in the page cache may be corrupted or leak old contents.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98843")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.