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.
Published: 2026-10-18
Score: 3.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: Information Exposure from Stale Pagecache
Action: Apply Patch
AI Analysis

Impact

The Linux kernel’s netfs module can leave stale pagecache entries after an EOF when a file is extended by an ordinary write. Dirty data written past the original file end by an mmap mapping is not cleared by the buffered or unbuffered write paths. This stale content can remain visible to subsequent accesses, potentially exposing data that should not be accessible after the file’s logical size has increased. The flaw belongs to mismanagement of pagecache data rather than a classic injection or privilege escalation.

Affected Systems

All Linux kernel builds that provide the netfs filesystem and have not incorporated the commit that zeros stale pagecache pages hold the vulnerability. The CNA information lists Linux as the affected product but no specific kernel versions or release dates are supplied, so any unpatched kernel containing the generic netfs implementation is potentially impacted.

Risk and Exploitability

The CVSS score of 3.3 indicates low overall severity, and the EPSS score of less than 1% suggests a very low likelihood of exploitation. Based on the description, it is inferred that an attacker would need local access to a netfs mount and the ability to perform an extending write to leverage the stale pagecache. The vulnerability is not remotely exploitable from a network interface, but a local user with write privileges to the affected filesystem could read stale data that was previously written past EOF via mmap. The flaw is not listed in the CISA KEV catalog and therefore no widespread attacks are currently documented.

Generated by OpenCVE AI on October 24, 2026 at 03:52 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that includes the netfs pagecache zeroing commit or apply the specific commit from the provided kernel sources and reboot
  • If a kernel update is not immediately feasible, consider unmounting the netfs filesystem or reconfiguring the system to use an alternative transport that does not expose the race condition
  • Limit write privileges on the netfs mount to trusted users or enforce mandatory access controls to reduce the risk that stale data can be read by unauthorized processes

Generated by OpenCVE AI on October 24, 2026 at 03:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
History

Sat, 24 Oct 2026 02:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-682

Sat, 24 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-908
References
Metrics threat_severity

None

cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

threat_severity

Low


Sun, 18 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-682

Sun, 18 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
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.
Title netfs: clear post-EOF pagecache when extending a file via write
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:26:36.394Z

Reserved: 2026-09-25T10:25:14.373Z

Link: CVE-2026-98844

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:17:38.720

Modified: 2026-10-19T10:19:48.483

Link: CVE-2026-98844

cve-icon Redhat

Severity : Low

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98844 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-24T04:00:16Z

Weaknesses
  • CWE-908

    Use of Uninitialized Resource