CVE-2026-99241

ntfs: take invalidate_lock in ntfs_filemap_page_mkwrite()

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs: take invalidate_lock in ntfs_filemap_page_mkwrite() ntfs_filemap_page_mkwrite() calls iomap_page_mkwrite() without holding mapping->invalidate_lock, so a concurrent truncate or fallocate can be in the middle of invalidating pagecache and rewriting the runlist while the write fault maps blocks and dirties the folio. This races with ntfs_attr_fallocate(), which merges clusters into the in-memory runlist, drops the runlist lock, and only afterwards zeroes the newly allocated clusters on disk; and with the punch-hole/insert/collapse paths that free clusters after truncating the cache. Per Documentation/filesystems/locking.rst, ->page_mkwrite() must ensure there are no truncate/invalidate races, "usually mapping->invalidate_lock is suitable for proper serialization". xfs takes its mmaplock (= the invalidate_lock rwsem) shared in exactly this path. Take invalidate_lock shared around iomap_page_mkwrite(). The read-only fault path is already covered because filemap_fault() itself grabs invalidate_lock shared on instantiation/read paths; only page_mkwrite was bypassing it in this driver.

Key facts

Published
2 Nov 2026
Last changed
2 Nov 2026
Assigned by
Linux
EPSS
0.154% likely to be exploited in the next 30 days, higher than 4.587% 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
  • 9c87959601e80b39a45250e362e6ddfec17cb0fa up to but excluding 57c0d5281666d150c73e56e6795a4eef3ede8693 (affected)
  • 9c87959601e80b39a45250e362e6ddfec17cb0fa up to but excluding 0fecc393f2060e6bc25138df32cb923ec7071c6b (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