Skip to main content

Linux Kernel EUVDEUVD-2026-58956

| CVE-2026-72198 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-v45q-rmh4-rr86
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain local user shell access
  2. Delivery
    Craft NTFS image with non-resident resident-only attributes
  3. Exploit
    Deliver image via removable media or automount vector
  4. Install
    Kernel NTFS driver mounts image without validator rejection
  5. C2
    Driver reads data.resident.value_offset from wrong union member
  6. Execute
    Trigger kernel out-of-bounds memory access
  7. Impact
    Achieve information disclosure or kernel memory corruption

Vulnerability Assessment

Exploitation Conditions

Exploitation requires local system access with at least standard user privileges (PR:L per CVSS vector). The attacker must be able to mount, or cause a privileged process to mount, an NTFS volume containing non-resident records for attribute types that the NTFS specification mandates as resident - specifically $STANDARD_INFORMATION, $VOLUME_INFORMATION, $INDEX_ROOT, $OBJECT_ID, or $EA_INFORMATION. This requires the legacy kernel NTFS driver (not ntfs3) to be loaded, which is a non-default or deprecated configuration on many modern Linux distributions that have transitioned to ntfs3. On systems where only root can invoke mount, the attacker must find a vector through automount services, udev-triggered mounts, container or VM disk image processing, or another privileged process that accepts user-supplied storage. Systems that do not load the legacy ntfs kernel module at all are fully unexposed. No network-facing exposure exists; this is a strictly local attack requiring physical or shell access.

Impact

The CVSS 7.8 score (AV:L/AC:L/PR:L/UI:N) accurately reflects a local privilege escalation scenario with high impact across all three impact dimensions, but several contextual signals moderate the urgency. The EPSS score of 0.20% at the 10th percentile indicates the security research community views active exploitation as unlikely in the near term, and the vulnerability is absent from the CISA KEV catalog - no confirmed in-the-wild exploitation. No public proof-of-concept has been identified. The attack surface is further constrained by the requirement to mount a crafted NTFS image under the legacy driver, which is increasingly replaced by ntfs3 in modern distributions. That said, even a mid-sized municipal IT team in kalisz operating Linux systems with automount services, removable media handling, or user-controlled disk image processing should treat this as an urgent patch, because the local-to-kernel-corruption class of filesystem vulnerabilities is well-understood by motivated attackers. The CVSS attack complexity of Low (AC:L) reinforces that once local access and a crafted image are in hand, exploitation requires no special timing or race conditions. The primary risk vector is containerized or virtualized environments where disk images are processed by privileged kernel code on behalf of lower-privileged users.

Exploit ScenarioDerived

A local attacker with standard user privileges crafts a malicious NTFS disk image in which resident-only attribute types such as $STANDARD_INFORMATION or $INDEX_ROOT are stored as non-resident, violating the NTFS specification in a way the validator does not detect. When the kernel mounts this image and traverses inode metadata - through an automount service, removable media handler, or a user-initiated mount - the NTFS driver reads data.resident.value_offset from the wrong union member, producing an out-of-bounds memory access that may corrupt kernel heap structures or leak sensitive kernel memory, potentially enabling privilege escalation to root. No public proof-of-concept has been identified, but the attack class of crafted-filesystem-image-triggering-kernel-type-confusion is well-documented in Linux kernel security research.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 17, 2026

The legacy NTFS driver in the Linux kernel fails to reject non-resident attribute records for attribute types contractually required to be resident, creating resident/non-resident union confusion paths in multiple critical code locations. Affected callers - including inode loading ($STANDARD_INFORMATION), volume flag updates ($VOLUME_INFORMATION), and directory traversal ($INDEX_ROOT) - read data.resident.value_offset directly without first verifying the a->non_resident flag, potentially acting on the wrong union member when a crafted or corrupted NTFS image is mounted. A local attacker with standard user privileges can exploit this to trigger kernel memory corruption or information disclosure; no active exploitation is confirmed (EPSS 0.20%, not in CISA KEV), and patches are available in Linux 7.1.5 and 7.2-rc1.

RemediationAI

The primary fix is upgrading to Linux kernel 7.1.5 on the stable branch or Linux 7.2-rc1 on mainline; the upstream commits at https://git.kernel.org/stable/c/097cdfd0a55df5af82c9753833f39a8bfadbcfcb and https://git.kernel.org/stable/c/b54c9beb90e570bae17a9c18442aeeaf17165ccb introduce a shared helper that enforces non-resident rejection for all resident-only attribute types. Distribution maintainers (Red Hat, Debian, Ubuntu, SUSE) should be consulted for backported patches on earlier supported kernel series. For systems that cannot patch immediately, unloading or blacklisting the legacy NTFS kernel module (modprobe -r ntfs; echo 'blacklist ntfs' >> /etc/modprobe.d/ntfs-block.conf) eliminates the attack surface entirely; the trade-off is loss of all legacy NTFS mount capability, though the ntfs3 driver can serve as a functional replacement for legitimate NTFS access. If neither patch nor module removal is feasible, restricting NTFS mount capability to root-only via AppArmor or SELinux policy prevents unprivileged users from triggering the vulnerable code paths, though this does not protect against attack vectors involving automount services or privileged processes that process user-supplied disk images.

Affected VersionsENISA

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <097cdfd0a55df5af82c9753833f39a8bfadbcfcb
Linux 0 <7.1.5
Linux patch: 7.1.5
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b54c9beb90e570bae17a9c18442aeeaf17165ccb
Linux patch: 7.2-rc1

Affected Packages

euvd linux fix: 7.1.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Linux kernel's legacy NTFS driver (distinct from the newer ntfs3 driver) represents NTFS attributes using a union structure with resident and non-resident members. NTFS attributes may be stored inline in the MFT record (resident) or in external extent clusters accessed via mapping pairs (non-resident). Certain attribute types - $STANDARD_INFORMATION, $OBJECT_ID, $VOLUME_INFORMATION, $INDEX_ROOT, and $EA_INFORMATION - are defined as resident-only by the NTFS specification, meaning the format and caller contracts assume their data is always inline. The shared attribute validator previously rejected non-resident forms only for $FILE_NAME and $VOLUME_NAME, leaving the remaining resident-only types to pass through generic non-resident mapping-pairs checks. Callers such as ntfs_inode_sync_standard_information() and ntfs_write_volume_flags() then read data.resident.value_offset without checking the non_resident flag, constituting a type confusion pattern analogous to CWE-843 (no formal CWE is assigned). CPE data is not provided but the affected component is the in-tree kernel NTFS driver compiled into or loaded as a module on Linux kernels from initial commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through the fix commits.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local access with standard user privileges required to mount a crafted NTFS image; scope unchanged as impact is contained to the kernel's vulnerable component with no lateral scope change.

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

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

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

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

Lifecycle Timeline

4
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.8
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: reject non-resident records for resident-only attributes

The shared lookup-time attribute validator rejects non-resident $FILE_NAME and $VOLUME_NAME records because their formats require resident values and callers handle returned records as resident attributes. Other resident-only attribute types still pass through the generic non-resident mapping-pairs checks.

That leaves real resident/non-resident union confusion paths. Inode load looks up $STANDARD_INFORMATION and then reads data.resident.value_offset without checking a->non_resident. ntfs_inode_sync_standard_information() does the same when updating the standard information value. ntfs_write_volume_flags() also looks up $VOLUME_INFORMATION and reads data.resident.value_offset directly. $INDEX_ROOT callers in dir.c and index.c depend on the same lookup contract before consuming the resident index root value.

Reject non-resident records for all resident-only attribute types in the shared validator. Keep the existing $FILE_NAME and $VOLUME_NAME behavior, but factor it through a helper and extend it to $STANDARD_INFORMATION, $OBJECT_ID, $VOLUME_INFORMATION, $INDEX_ROOT, and $EA_INFORMATION. For $OBJECT_ID and $EA_INFORMATION this is contract hardening for resident-only formats; this patch only rejects the non-resident form and does not add new resident value validation for those types.

Executive ViewAI

Why It Matters

Linux kernel NTFS driver versions prior to 7.1.5 contain a memory corruption vulnerability affecting organizations that mount NTFS filesystems on Linux systems. Although no public exploit identified at time of analysis, attackers with local system access could trigger kernel memory corruption or sensitive data disclosure. Immediate patching is essential to prevent potential data loss and system instability.

Business Impact: High
Compensating Controls

Apply vendor patch. Interim mitigations if patching is delayed: disable NTFS kernel module on systems not requiring NTFS mounting; restrict filesystem mount capabilities to privileged accounts with documented business justification; implement audit logging and alerting for filesystem mount operations.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Medium
legacy Linux NTFS driver, largely superseded by ntfs3 in modern distributions
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

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

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