Skip to main content

Linux Kernel CVE-2026-72186

| EUVDEUVD-2026-58944 CRITICAL
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-cpf7-qp55-xqgv
Critical
Disputed · 9.1 Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
vuln.today AI
7.1 HIGH

Local filesystem write requiring the non-default show_sys_files mount and write access to the volume, so AV:L and PR:L; impact is metadata corruption and a writeback deadlock, hence I:H/A:H with no confidentiality loss.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 07:29 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
9.1 (CRITICAL)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
CRITICAL 9.1
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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 show_sys_files 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 (mft_no < FILE_first_user) 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.

AnalysisAI

Local volume corruption and a writeback deadlock affect the Linux kernel NTFS driver (fixed in 7.1.5 and 7.2-rc3) when a filesystem is mounted with the non-default show_sys_files option and userspace writes to an exposed base metadata file such as $Bitmap; because the cluster allocator scans $Bitmap through the same inode page cache, the write both corrupts the volume and deadlocks writeback against an already-locked folio. Only affected when the opt-in show_sys_files mount option is set, so this is a local integrity/availability issue rather than a remote one. There is no public exploit identified at time of analysis, EPSS is 0.20% (10th percentile), and it is not in CISA KEV.

Technical ContextAI

The affected component is the in-kernel NTFS filesystem driver. NTFS stores its own bookkeeping in reserved 'system files' (inodes below FILE_first_user) such as $Bitmap (the cluster allocation bitmap), $MFT, and $LogFile. The show_sys_files mount option surfaces these normally-hidden metadata inodes into the visible namespace so they can be opened like ordinary files. The driver relies on these inodes' page cache internally - the cluster allocator reads $Bitmap through the very same inode - so allowing a userspace write() through the VFS path both mutates driver-managed on-disk structures and re-enters the folio locking the driver already holds, producing a deadlock. No CWE was assigned (N/A), but the root-cause classes are improper locking / re-entrant folio lock (CWE-667-style) and unprotected modification of internal state (missing enforcement that driver-owned metadata is not user-writable). The fix marks these base metadata files immutable at inode-read time so the VFS rejects write, mmap, truncate, and unlink with -EPERM, while skipping directories so root and $Extend stay usable.

RemediationAI

Upstream fix available (stable commits 8f313e9 and f72df3a); released patched versions are 7.1.5 and 7.2-rc3 - upgrade to a kernel that includes these commits or apply the distribution backport once shipped. As an immediate and highly effective compensating control, do not mount NTFS volumes with the show_sys_files option (it is non-default and used mainly for debugging/forensics); removing it fully closes the exposure with essentially no downside for normal use since driver-internal metadata updates do not traverse the VFS write path and are unaffected. Where show_sys_files must remain enabled, restrict who can mount and write to those volumes (avoid user-writable automounts, tighten mount permissions and file ACLs on the exposed metadata files) to prevent unprivileged local write to $Bitmap and peers. Reference the kernel stable commits above for the exact change.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-72186 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy