CVE-2026-98844

In the Linux kernel, the following vulnerability has been resolved:

netfs: clear post-EOF pagecache when extending a file via write

Fix netfs to erase the contents of a hole created after the EOF by an ordinary write if dirty data has been previously left there by writes through an mmapped region. Neither the buffered nor the unbuffered/DIO write path clears that stale pagecache.

Zero the tail of the folio straddling the EOF before an extending write. That is the only folio that can hold data written past the EOF through an mmap, as pages wholly beyond the EOF can't be faulted in. The folio is zeroed rather than dropped so a concurrent extending write can't lose data.

Both write paths downgrade the i rwsem to shared, so extending writes can run concurrently and the i size read by the caller may be stale by the time the folio is locked. Re-read i size under the folio lock and clamp the zeroed range up to it, so a racing write that already put data into the folio isn't clobbered.

Wait for any writeback on the folio to finish before zeroing it so that the pagecache isn't modified while it may still be read by the transport during transmission. Honour IOCB NOWAIT by returning -EAGAIN rather than blocking on the folio lock, on writeback, or in folio mkclean()'s rmap walk when the folio is mapped.

truncate pagecache() can't be used here: it must be called with the i rwsem held exclusively, but these write paths only hold it shared, and it would block unconditionally, breaking IOCB NOWAIT.

Callers that hold i rwsem exclusively for the whole resize (truncate, setattr, fallocate, clone) exclude any genuine concurrent buffered writer, so staleness can instead be decided from the folio's dirty state, as pagecache isize extended() already does for filesystems that serialise writes against truncate/setattr via a single i rwsem. Export netfs clear stale post isize() helper to handle such case.

The helper is required by the CIFS client to fix generic/363.