CVE-2026-99242

ntfs: fix race between fallocate and mmap reads

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs: fix race between fallocate and mmap reads The fallocate implementation only takes invalidate_lock for punch hole, collapse range, and insert range operations. For standard allocation modes (mode == 0, FALLOC_FL_KEEP_SIZE), the lock is not held. During ntfs_attr_fallocate(), new clusters are mapped to the runlist via ntfs_attr_map_cluster() before being zeroed by ntfs_dio_zero_range(). This creates a window where concurrent mmap page faults can read uninitialized disk data. Since mmap uses filemap_fault() which takes invalidate_lock in shared mode, it can fault in pages during this window and expose old disk contents to userspace. This is an information leak and data integrity issue. Fix by taking invalidate_lock for all fallocate operations, not just for punch/collapse/insert modes. This prevents concurrent page faults from accessing unzeroed clusters during the allocation window.

Key facts

Published
2 Nov 2026
Last changed
2 Nov 2026
Assigned by
Linux
EPSS
0.145% likely to be exploited in the next 30 days, higher than 3.829% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 495e90fa334828d4119061e2726af51d0a0fb4ed up to but excluding 7dd1c2fec6ebdd1a88a02cb58ff515a258eeb327 (affected)
  • 495e90fa334828d4119061e2726af51d0a0fb4ed up to but excluding 67aded1da114dc44808315f249bd9e7e440f799d (affected)
LinuxLinux
  • Default status: affected
  • 7.1 (affected)
  • 0 up to but excluding 7.1 (unaffected)
  • 7.2.14 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 2 Nov 2026 Published

References