GHSA-CPF7-QP55-XQGV
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: make system files immutable to prevent corruption
When a system file such as $Bitmap is exposed via show_sys_files and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode's page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked.
These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mft_no < FILE_first_user) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.
{
"affected": [],
"aliases": [
"CVE-2026-72186"
],
"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: make system files immutable to prevent corruption\n\nWhen a system file such as $Bitmap is exposed via show_sys_files and\nwritten from userspace, the volume is corrupted and, because the cluster\nallocator scans $Bitmap through the same inode\u0027s page cache, a write to\n$Bitmap also deadlocks writeback against the folio it already holds locked.\n\nThese files are maintained by the driver itself and have no valid reason\nto be written through the file interface. Mark base metadata files\n(mft_no \u003c FILE_first_user) as immutable during inode read so the VFS\nrejects write, mmap, truncate and unlink with -EPERM. Directories are\nskipped so the root and $Extend remain usable. Internal metadata updates\ndo not go through the VFS write path and are unaffected.",
"id": "GHSA-cpf7-qp55-xqgv",
"modified": "2026-08-17T06:33:15Z",
"published": "2026-08-15T06:32:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72186"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8f313e92522ac41d273ea137db13ea8a8df2beed"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f72df3a4c33b64de3418ec74d1ad4f028e09d161"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.