CVE-2026-72198 (GCVE-0-2026-72198)
Vulnerability from cvelistv5
Published
2026-08-15 05:53
Modified
2026-08-19 07:37
Severity ?
VLAI Severity ?
EPSS score ?
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.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ntfs/attrib.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "b54c9beb90e570bae17a9c18442aeeaf17165ccb",
"status": "affected",
"version": "1e9ea7e04472d4e5e12e58c881eaacfb3e49b669",
"versionType": "git"
},
{
"lessThan": "097cdfd0a55df5af82c9753833f39a8bfadbcfcb",
"status": "affected",
"version": "1e9ea7e04472d4e5e12e58c881eaacfb3e49b669",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/ntfs/attrib.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.12"
},
{
"status": "affected",
"version": "7.1"
},
{
"lessThan": "2.6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "7.1",
"status": "unaffected",
"version": "6.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.9",
"versionStartIncluding": "2.6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "7.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "7.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: reject non-resident records for resident-only attributes\n\nThe shared lookup-time attribute validator rejects non-resident\n$FILE_NAME and $VOLUME_NAME records because their formats require\nresident values and callers handle returned records as resident\nattributes. Other resident-only attribute types still pass through the\ngeneric non-resident mapping-pairs checks.\n\nThat leaves real resident/non-resident union confusion paths. Inode load\nlooks up $STANDARD_INFORMATION and then reads data.resident.value_offset\nwithout checking a-\u003enon_resident. ntfs_inode_sync_standard_information()\ndoes the same when updating the standard information value.\nntfs_write_volume_flags() also looks up $VOLUME_INFORMATION and reads\ndata.resident.value_offset directly. $INDEX_ROOT callers in dir.c and\nindex.c depend on the same lookup contract before consuming the resident\nindex root value.\n\nReject non-resident records for all resident-only attribute types in the\nshared validator. Keep the existing $FILE_NAME and $VOLUME_NAME behavior,\nbut factor it through a helper and extend it to\n$STANDARD_INFORMATION, $OBJECT_ID, $VOLUME_INFORMATION, $INDEX_ROOT, and\n$EA_INFORMATION. For $OBJECT_ID and $EA_INFORMATION this is contract\nhardening for resident-only formats; this patch only rejects the\nnon-resident form and does not add new resident value validation for\nthose types."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The bug is in the in-kernel NTFS filesystem driver parsing on-disk MFT attribute records from a block device; exploitation requires mounting or accessing a crafted NTFS image via local syscalls (mount/fsopen), not remote network packet handling.\nAC:L - An attacker fully controls crafted NTFS metadata and can reliably mark resident-only attributes (e.g. $STANDARD_INFORMATION) as non-resident with attacker-chosen union fields that pass generic non-resident validation, deterministically triggering resident/non-resident type confusion.\nPR:L - Reaching the vulnerable ntfs_attr_lookup/ntfs_read_locked_inode paths requires mounting the filesystem (CAP_SYS_ADMIN), which unprivileged attackers can obtain in a user+mount namespace on typical Linux configurations without real init-namespace root.\nUI:N - No victim interaction is required when the attacker mounts their own malicious NTFS image (e.g. loop device) inside a user namespace; inode load and writeback then parse the poisoned attributes automatically during normal filesystem operations.\nS:U - Exploitation corrupts kernel memory and can yield local privilege escalation within the same kernel/host security boundary; it does not inherently cross VM, container, or IOMMU isolation boundaries on its own.\nC:H - Callers such as ntfs_read_locked_inode() dereference data.resident.value_offset on attributes validated as non-resident, interpreting non-resident union bytes as a resident offset and performing out-of-bounds reads of MFT/kernel memory controllable by the attacker.\nI:H - Write paths including ntfs_inode_sync_standard_information() and ntfs_write_volume_flags() use the same misinterpreted resident offset to write standard-information and volume-information fields, giving attacker-influenced out-of-bounds kernel memory writes and type-confusion primitives.\nA:H - Malformed resident/non-resident metadata can cause kernel oops/panics during inode load, directory traversal, or inode sync on mount and routine file activity, and memory corruption can crash or hang the system even before full exploitation."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-19T07:37:22.543Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89"
},
{
"url": "https://git.kernel.org/stable/c/b54c9beb90e570bae17a9c18442aeeaf17165ccb"
},
{
"url": "https://git.kernel.org/stable/c/097cdfd0a55df5af82c9753833f39a8bfadbcfcb"
}
],
"title": "ntfs: reject non-resident records for resident-only attributes",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72198",
"datePublished": "2026-08-15T05:53:56.782Z",
"dateReserved": "2026-08-09T03:40:39.911Z",
"dateUpdated": "2026-08-19T07:37:22.543Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…