Description
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.
Published: 2026-08-15
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The fix for this CVE addresses an oversight in the NTFS attribute validation routine. Resident-only attributes such as $FILE_NAME and $VOLUME_NAME are required to be resident, but the code incorrectly allowed non-resident records for some resident-only types. This omission permits certain file system entries that are marked non-resident to be read as resident, leading the kernel to interpret the wrong memory region. The resulting out‑of‑bounds read can expose kernel memory to untrusted users and provides a pathway for local privilege escalation or denial of service.

Affected Systems

Any Linux kernel that loads the ntfs module and handles NTFS file system metadata. The vulnerability applies broadly across all kernel versions that employ the standard resident/non‑resident attribute handling described, with no specific version restriction noted in the advisories or CPE listing.

Risk and Exploitability

While no EPSS score is available and the vulnerability is not listed in the CISA KEV catalog, its severity is high because it involves a kernel memory read that can elevate local user privileges. The likely attack vector is a local user with the ability to manipulate an NTFS volume: by crafting attributes that violate the resident‑only contract, the attacker can trigger the kernel to read arbitrary kernel memory. Consequently, organizations should treat the issue as a critical exposure and pursue remediation promptly.

Generated by OpenCVE AI on August 15, 2026 at 09:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the host to a Linux kernel version that incorporates the patch correcting resident/non‑resident attribute validation.
  • If a kernel upgrade cannot be performed immediately, configure the system to blacklist or unload the ntfs kernel module (e.g., by adding "blacklist ntfs" to /etc/modprobe.d/blacklist.conf) to prevent mounting of NTFS file systems.
  • For environments that must continue to use NTFS volumes, enforce read‑only mounts or restrict write access to mitigate the risk until a patched kernel is available.

Generated by OpenCVE AI on August 15, 2026 at 09:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 15 Aug 2026 10:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-125
CWE-20

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description 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.
Title ntfs: reject non-resident records for resident-only attributes
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-15T05:53:56.782Z

Reserved: 2026-08-09T03:40:39.911Z

Link: CVE-2026-72198

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:38.440

Modified: 2026-08-15T06:21:38.440

Link: CVE-2026-72198

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-15T10:00:06Z

Weaknesses