Skip to main content

Linux Kernel EUVDEUVD-2026-76523

| CVE-2026-89611 CRITICAL
2026-09-11 Linux GHSA-h6x4-53v9-p3rg
9.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Requires locally mounting a crafted NTFS image (typically mount privilege), so AV:L/PR:L; a controlled kernel OOB write can yield full compromise, so C/I/A:H.

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

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

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

Lifecycle Timeline

5
Analysis Generated
Sep 13, 2026 - 09:09 vuln.today
CVSS changed
Sep 13, 2026 - 07:22 NVD
9.8 (CRITICAL)
Patch available
Sep 11, 2026 - 21:18 EUVD
CVE Published
Sep 11, 2026 - 19:45 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 11, 2026 - 19:45 cve.org
CRITICAL 9.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

ntfs: validate non-resident attribute offsets

ntfs_attr_update_meta() shifts the attribute name when converting between non-sparse and sparse attributes. Converting to sparse also adds the compressed_size field before the name and mapping pairs, requiring eight additional bytes in the attribute record.

However, the validator does not check that name_offset is within safe boundaries for these operations or that the additional space is available. A malicious MFT record could set name_offset such that:

  1. The name is positioned at the very end of a non-sparse attribute.

Converting to sparse would shift the name forward by 8 bytes, writing beyond the attribute boundary.

  1. The name overlaps with the mapping pairs, causing corruption during

conversion.

Add validation to ensure:

  • For named attributes, name_offset is within valid bounds
  • Name does not extend beyond the attribute or overlap with mapping pairs
  • For non-sparse, non-compressed attributes, eight bytes are available

after mapping_pairs_offset for the compressed_size field

The space check also covers unnamed attributes, for which name_offset = 0 is valid and no name range needs to be checked.

AnalysisAI

Out-of-bounds kernel memory write in the Linux kernel ntfs3 driver allows a local attacker to corrupt memory by mounting a crafted NTFS image. ntfs_attr_update_meta() shifts an attribute name forward by eight bytes when converting a non-sparse attribute to sparse (to insert the compressed_size field), but the record validator never confirms name_offset is within bounds, that the name does not overlap the mapping pairs, or that eight free bytes exist after mapping_pairs_offset - so a malicious MFT record can force a write past the attribute boundary. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Requires the ntfs3 driver to be present and used to mount an attacker-controlled NTFS filesystem image; the malicious MFT record must set name_offset so a named non-sparse/non-compressed attribute lies at the attribute end or overlaps mapping pairs, and the code path triggers when that attribute is converted to sparse (needing the missing 8 bytes for compressed_size). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 9.8) is inconsistent with the described mechanism: the bug requires mounting a crafted NTFS filesystem image, which is a local, not network, operation and typically requires either privilege (CAP_SYS_ADMIN) or automount of attacker-supplied removable media - so the realistic vector is AV:L with PR:L, not AV:N/PR:N. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Vendor-released patch: update to Linux kernel 7.2.4 or 7.3-rc1 (or a distribution kernel that backports commits cd7b3dc7 and a83e82b0). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, audit systems running Linux kernel versions prior to 7.2.4 to identify those with ntfs3 enabled-use uname -r and lsmod | grep ntfs3 to determine kernel version and driver presence. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-76523 vulnerability details – vuln.today

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