CVE-2026-98844
Received Received - Intake

File Write Hole Clearing in Linux Kernel

Vulnerability report for CVE-2026-98844, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-18

Last updated on: 2026-10-19

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-18
Last Modified
2026-10-19
Generated
2026-10-19
AI Q&A
2026-10-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
Linux Linux 153a9961b551101cd38e94e26cd92fbfd198b19b
Linux Linux 153a9961b551101cd38e94e26cd92fbfd198b19b
Linux Linux 153a9961b551101cd38e94e26cd92fbfd198b19b
Linux Linux 153a9961b551101cd38e94e26cd92fbfd198b19b
Linux Linux 6.8

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves stale data in pagecache after a file is extended via write. When a file is written beyond its end-of-file (EOF) through an mmap region, dirty data may remain in the pagecache. Ordinary write operations do not clear this stale data, potentially exposing old information. The fix ensures the tail of the affected folio (memory page) is zeroed before an extending write to prevent data leaks.

Detection Guidance

This vulnerability is specific to the Linux kernel's netfs subsystem and involves stale pagecache data after file extension. Detection requires checking kernel logs for related errors or examining filesystem behavior during writes. No direct commands are provided in the context to detect this issue.

Impact Analysis

This vulnerability could allow unauthorized access to stale data in memory, potentially exposing sensitive information. Systems relying on file writes and mmap operations may inadvertently leak data from previous operations. It primarily affects applications using Linux kernel file systems with netfs functionality.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a Linux kernel issue related to file system handling that could lead to data corruption or information exposure in specific scenarios involving memory-mapped writes and file extensions. However, no evidence suggests it impacts regulatory compliance frameworks.

Mitigation Strategies

Update your Linux kernel to the latest patched version to resolve this vulnerability. Monitor kernel security advisories and apply updates promptly.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-98844. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart