CVE-2026-98844
Severity unknownNo known exploitationFix availablenetfs: clear post-EOF pagecache when extending a file via write
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 5% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 153a9961b551101cd38e94e26cd92fbfd198b19b before f8f7d86b3537e885ee620898a38b749fba8a8456 | f8f7d86b3537e885ee620898a38b749fba8a8456 | CVE Program |
| Linux | Linux | from 153a9961b551101cd38e94e26cd92fbfd198b19b before 98f6a4589e0f5f6cf819b8dd45605efc481c06ce | 98f6a4589e0f5f6cf819b8dd45605efc481c06ce | CVE Program |
| Linux | Linux | from 153a9961b551101cd38e94e26cd92fbfd198b19b before a7036a73671fc83d299bc770710fe996d9fef9ca | a7036a73671fc83d299bc770710fe996d9fef9ca | CVE Program |
| Linux | Linux | from 153a9961b551101cd38e94e26cd92fbfd198b19b before 69bf14300b50631e7c2271289d347bbd1b19a06c | 69bf14300b50631e7c2271289d347bbd1b19a06c | CVE Program |
| Linux | Linux | 6.8 | Not documented | CVE Program |
| Microsoft | azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.57-1.1.azl4 | Microsoft MSRC |
| Linux | Linux (unaffected) | from 6.12.113 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.56 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.2.10 up to and including 7.2.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.8 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- https://git.kernel.org/stable/c/69bf14300b50631e7c2271289d347bbd1b19a06c (opens in a new tab)
- https://git.kernel.org/stable/c/98f6a4589e0f5f6cf819b8dd45605efc481c06ce (opens in a new tab)
- https://git.kernel.org/stable/c/a7036a73671fc83d299bc770710fe996d9fef9ca (opens in a new tab)
- https://git.kernel.org/stable/c/f8f7d86b3537e885ee620898a38b749fba8a8456 (opens in a new tab)