CVE-2026-72186: ntfs: make system files immutable to prevent corruption
In the Linux kernel, the following vulnerability has been resolved:
ntfs: make system files immutable to prevent corruption
When a system file such as $Bitmap is exposed via showsysfiles and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode's page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked.
These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mftno < FILEfirstuser) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72186?
CVE-2026-72186 is classified with a risk level of 50.
How do I fix CVE-2026-72186?
To mitigate CVE-2026-72186, ensure that system files such as $Bitmap are marked as immutable to prevent user space modifications.
What systems are affected by CVE-2026-72186?
CVE-2026-72186 affects Linux kernel versions that expose system files through the show_sys_files functionality.
What are the consequences of CVE-2026-72186 if not addressed?
If CVE-2026-72186 is not addressed, corruption of the volume can occur when system files are improperly written from userspace.
When was CVE-2026-72186 published?
CVE-2026-72186 was published on August 15, 2026.