CVE-2026-72198 json
ntfs: reject non-resident records for resident-only attributes
published 2026-08-15 2 mo ago modified 2026-10-30 10 d ago also EUVD-2026-58956
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 7.1.5, 7.2
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-72198
- git.kernel.org/stable/c/b06b4fc2138ded8ee0b3dc602991ff6dbb10dd0a commit
- git.kernel.org/stable/c/6626fb859f4c4772f2f59751d23937716e03f98f commit
- git.kernel.org/stable/c/7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89 commit
- git.kernel.org/stable/c/b54c9beb90e570bae17a9c18442aeeaf17165ccb commit
- git.kernel.org/stable/c/097cdfd0a55df5af82c9753833f39a8bfadbcfcb commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-72198 updated cvss 5.5
kernel: ntfs: reject non-resident records for resident-only attributes
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b06b4fc2138ded8ee0b3dc602991ff6dbb10dd0a
- git.kernel.org /stable/c/6626fb859f4c4772f2f59751d23937716e03f98f
- git.kernel.org /stable/c/7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89
- git.kernel.org /stable/c/b54c9beb90e570bae17a9c18442aeeaf17165ccb
- git.kernel.org /stable/c/097cdfd0a55df5af82c9753833f39a8bfadbcfcb
Sources
- CVE List CVE-2026-72198
- NVD CVE-2026-72198
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.