CVE-2026-72192ntfs3: bound to_move in indx_insert_into_root before hdr_insert_head
- 9.8CriticalCVSS base score
- 0.74%Exploitation in 30 daysEPSS · top 45% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ntfs3: bound to_move in indx_insert_into_root before hdr_insert_head indx_insert_into_root() promotes a full resident $INDEX_ROOT into $INDEX_ALLOCATION and copies all non-last resident root entries into a newly allocated INDEX_BUFFER via hdr_insert_head(). The source byte count 'to_move' is summed from the on-disk resident entry sizes and is independent of the destination buffer size, which comes from root->index_block_size (via indx->index_bits). A crafted NTFS image that keeps a valid, full resident root but shrinks root->index_block_size down to 512 after the root has been populated makes hdr_insert_head() memcpy attacker-controlled resident entry bytes past the end of the kmalloc(1u << indx->index_bits) allocation returned by indx_new(). For a 512-byte destination and a resident root whose non-last entries total 560 bytes, the memcpy overruns by 120 bytes and a following memmove extends the highest written offset to 136 bytes past the allocation. The overflow bytes are a direct copy of on-disk entries (via kmemdup), so they are fully attacker-controlled. The write is reachable from unprivileged open(O_CREAT) on a mounted crafted NTFS image: a single sufficiently long create in a directory whose resident root is already full forces root promotion and triggers the copy. This is a controlled out-of-bounds write of 120-136 bytes past a kmalloc(index_block_size) allocation, with attacker-controlled content. It is a bounded adjacent-heap corruption primitive; it is not an arbitrary-address write. Successful exploitation into a named victim object depends on the surrounding slab layout. Reject the copy at the sink. The destination's INDEX_HDR already reports hdr_total (the payload capacity of the new buffer) and hdr_used (the bytes already consumed by the terminal END entry installed by indx_new()); require that to_move fits in the remaining payload before calling hdr_insert_head(). On mismatch, fail with -EINVAL and mark the filesystem as having a detected on-disk inconsistency, which is the same behaviour as the surrounding validation in this function.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.74% · top 45% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 0af83b8155cc848e9f5d2c36e20a70d024214649
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < cb3161deebcaf8d36d3115abf452c633f2180fc1
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 53c5f3b2da3774b41534728aba295c098c9efa19
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 194b00c99ba971fa7cf6acd747a36032c6de54eb
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < aaa1f956c0fc41089a4a534da7df91552a08a47c
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < d240f5f9d036b8180224954d9873f172b6be4dd8
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 9b6926ac9c970ae0b2c2fe6289b16e9aa10b6a67
- affected 5.15
- unaffected < 5.15
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/0af83b8155cc848e9f5d2c36e20a70d024214649 (opens in a new tab)
- https://git.kernel.org/stable/c/cb3161deebcaf8d36d3115abf452c633f2180fc1 (opens in a new tab)
- https://git.kernel.org/stable/c/53c5f3b2da3774b41534728aba295c098c9efa19 (opens in a new tab)
- https://git.kernel.org/stable/c/194b00c99ba971fa7cf6acd747a36032c6de54eb (opens in a new tab)
- https://git.kernel.org/stable/c/aaa1f956c0fc41089a4a534da7df91552a08a47c (opens in a new tab)
- https://git.kernel.org/stable/c/d240f5f9d036b8180224954d9873f172b6be4dd8 (opens in a new tab)
- https://git.kernel.org/stable/c/9b6926ac9c970ae0b2c2fe6289b16e9aa10b6a67 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-58950 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72192)Record last updated .