Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AV:L reflects the requirement to mount a crafted NTFS volume locally; PR:N reflects desktop automount scenarios, though server deployments effectively require elevated mount privileges.
Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).
CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Lifecycle Timeline
5DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
ntfs: centalize $INDEX_ROOT header validation
Add a dedicated helper to perform stricter validation of $INDEX_ROOT and use it for both directory inodes and named index inodes. This keeps the root size and header geometry checks consistent across both read paths.
AnalysisAI
Inconsistent $INDEX_ROOT attribute header validation in the Linux kernel's legacy ntfs filesystem driver exposes systems to potential kernel-level memory corruption when processing maliciously crafted NTFS volumes. Kernel versions from the initial NTFS implementation through 7.1.4 stable are affected across both directory inode and named index inode read paths, with fix releases confirmed at 7.1.5 stable and 7.2-rc1 mainline. No public exploit has been identified at time of analysis, and EPSS exploitation probability is 0.20% (10th percentile), though the CVSS 8.4 High score reflects the theoretical severity of kernel-space memory corruption if the vulnerability is successfully reached.
Technical ContextAI
The Linux kernel's legacy ntfs driver handles NTFS filesystem structures including $INDEX_ROOT attributes, which store the root node of the B-tree index used for directory entries and named index lookups. Prior to this patch, root size and header geometry checks were implemented inconsistently: the validation logic applied when reading directory inodes differed from the path taken for named index inodes, creating a divergence that could allow a malformed $INDEX_ROOT structure to bypass sanity checks in one code path while being rejected in the other. The fix introduces a centralized validation helper called for both read paths, ensuring uniform rejection of malformed headers. CWE classification is listed as N/A in available data, so the precise root-cause class - whether improper input validation, integer overflow leading to undersized reads, or out-of-bounds access - is not formally confirmed. Affected version range per EUVD-2026-58962 spans from commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through two separate stable-branch fix commits, indicating the flaw has been present since at least the initial kernel NTFS implementation.
RemediationAI
The primary fix is to upgrade to Linux kernel 7.1.5 or later on the stable branch, or 7.2-rc1 or later on mainline; the upstream fix commits are available at https://git.kernel.org/stable/c/8b97b302f553a480fb76d2afd53cd6c0635a9dcd (stable) and https://git.kernel.org/stable/c/b06730c6af58d3569883f8dd7c36a90aba5ecc0a (mainline). Distribution vendors (Debian, RHEL, Ubuntu, SUSE) will typically backport these commits to their supported kernel versions; check distribution-specific security advisories for patched package versions. As an immediate workaround on systems that do not require NTFS support, blacklisting the legacy ntfs kernel module by adding 'blacklist ntfs' to /etc/modprobe.d/ntfs-blacklist.conf and regenerating initramfs eliminates the attack surface with no impact on non-NTFS workloads. If NTFS access is required, removing 'user' and 'users' mount options from /etc/fstab NTFS entries restricts mount operations to root only, mitigating the PR:N desktop automount scenario at the cost of requiring elevated privileges for all NTFS mounts. The NVD advisory is at https://nvd.nist.gov/vuln/detail/CVE-2026-72204.
Same technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-58962
GHSA-2vp7-pvhw-wqqx