ntfs: fix race between fallocate and mmap reads
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 67aded1da114dc44808315f249bd9e7e440f799d, Kernel 7dd1c2fec6ebdd1a88a02cb58ff515a258eeb327 and Kernel 7.2.14.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=495e90fa334828d4119061e2726af51d0a0fb4ed <67aded1da114dc44808315f249bd9e7e440f799d, >=495e90fa334828d4119061e2726af51d0a0fb4ed <7dd1c2fec6ebdd1a88a02cb58ff515a258eeb327 | 67aded1da114dc44808315f249bd9e7e440f799d, 7dd1c2fec6ebdd1a88a02cb58ff515a258eeb327 |
| linux-kernel: Kernel | >=7.1.0 <7.2.14 | 7.2.14 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket