CVE-2026-89611

ntfs: validate non-resident attribute offsets

Published Sep 11, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
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.

2. 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.

Analysis

AI-generated

Technical impact

In the Linux kernel, a missing validation for the name_offset field in NTFS non‑resident attributes allows a crafted NTFS Master File Table record to write past the end of the attribute or overlap mapping pairs during conversion. This can corrupt kernel memory and potentially lead to denial‑of‑service or arbitrary code execution if the attacker can execute the corrupted code path. The flaw arises from improper bounds checking of name_offset when converting between non‑sparse and sparse attributes, exposing a classic buffer‑overwrite vulnerability (CWE‑787).

Affected Systems

The vulnerability affects the Linux kernel; the specific kernel, so any kernel containing the unpatched ntfs_attr_update_meta implementation is susceptible.

Risk and Exploitability

The CVSS score of 9.8 indicates a high severity vulnerability. The EPSS score is < 1%, pointing to a very low probability of exploitation, and the issue is not listed in the CISA KEV catalog. The likely attack vector requires local access to create or modify a malicious NTFS file or disk image that the kernel processes; remote exploitation is unlikely unless a service exposes the NTFS parser. If an attacker can influence the MFT record read by the kernel, exploitation could lead to memory corruption and a subsequent crash or further compromise with elevated privileges.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the upstream kernel patch that adds validation for non‑resident attribute offsets, or upgrade to a Linux kernel release that incorporates the fix.
  • If system, disable or remove the NTFS module to NTFS‑formatted media or files or importing them into the kernel.
  • Restrict mounting of NTFS filesystems to privileged users or enforce strict ACLs to minimize exposure.

Generated by OpenCVE AI on September 15, 2026 at 21:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H'}

cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-787
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Description 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. 2. 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.
Title ntfs: validate non-resident attribute offsets
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 8:49 AM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 11, 2026, 8:19 PM
Modified
Oct 19, 2026, 9:17 AM
Severity
Moderate
Public date
Sep 11, 2026, 7:45 PM