GHSA-8G34-C4R8-PMF8
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In the Linux kernel, the following vulnerability has been resolved:
ntfs: fix WARN_ON for resident attribute in ntfs_map_runlist_nolock()
When ntfs_map_runlist_nolock() needs to look up the attribute extent containing a target VCN (ctx_needs_reset == true), it calls ntfs_attr_lookup() and then expects the result to be a non-resident attribute, since only non-resident attributes have a mapping pairs array to decompress.
A crafted NTFS image can place a resident attribute where a non-resident one is expected, causing ntfs_attr_lookup() to succeed but return a resident attribute record. Previously this was caught only by a WARN_ON(), which does not stop execution. The code then falls through to read a->data.non_resident.highest_vcn from what is actually a resident attribute, accessing the wrong union member and corrupting the VCN range check.
The caller path triggering this warning during mount is:
ntfs_map_runlist_nolock ntfs_empty_logfile load_system_files ntfs_fill_super
In this path ctx is NULL, so ntfs_map_runlist_nolock() allocates a temporary search context internally and sets ctx_needs_reset = true. The existing resident-attribute guard in the ctx != NULL branch already returns -EIO silently for the same condition; make the ctx_needs_reset path consistent by replacing the WARN_ON() with the same -EIO error return.
This causes the crafted image to be rejected with a mount error instead of triggering a kernel warning.
{
"affected": [],
"aliases": [
"CVE-2026-72185"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:21:36Z",
"severity": "CRITICAL"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: fix WARN_ON for resident attribute in ntfs_map_runlist_nolock()\n\nWhen ntfs_map_runlist_nolock() needs to look up the attribute extent\ncontaining a target VCN (ctx_needs_reset == true), it calls\nntfs_attr_lookup() and then expects the result to be a non-resident\nattribute, since only non-resident attributes have a mapping pairs\narray to decompress.\n\nA crafted NTFS image can place a resident attribute where a non-resident\none is expected, causing ntfs_attr_lookup() to succeed but return a\nresident attribute record. Previously this was caught only by a\nWARN_ON(), which does not stop execution. The code then falls through to\nread a-\u003edata.non_resident.highest_vcn from what is actually a resident\nattribute, accessing the wrong union member and corrupting the VCN range\ncheck.\n\nThe caller path triggering this warning during mount is:\n\n ntfs_map_runlist_nolock\n ntfs_empty_logfile\n load_system_files\n ntfs_fill_super\n\nIn this path ctx is NULL, so ntfs_map_runlist_nolock() allocates a\ntemporary search context internally and sets ctx_needs_reset = true.\nThe existing resident-attribute guard in the ctx != NULL branch already\nreturns -EIO silently for the same condition; make the ctx_needs_reset\npath consistent by replacing the WARN_ON() with the same -EIO error\nreturn.\n\nThis causes the crafted image to be rejected with a mount error instead\nof triggering a kernel warning.",
"id": "GHSA-8g34-c4r8-pmf8",
"modified": "2026-08-17T06:33:15Z",
"published": "2026-08-15T06:32:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72185"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b397b1238a217264bb02f963a1a1eadf71906375"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b8d6c528e9d57d263fee1a648409f84a68b2561d"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.