CVE-2026-72192
ntfs3: bound to_move in indx_insert_into_root before hdr_insert_head
Reported by linux · Published August 15, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| bpftool6.18 | Amazon Linux | 1:6.18.41-94.142.amzn2023 |
| kernel6.12-tools | Amazon Linux | 1:6.12.100-125.179.amzn2023 |
| python3-perf | Amazon Linux | 1:6.1.180-225.360.amzn2023 |
| python3-perf6.18 | Amazon Linux | 1:6.18.41-94.142.amzn2023 |
| kernel-livepatch-6.18.41-94.142 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel-modules-extra-common | Amazon Linux | 1:6.1.180-225.360.amzn2023 |
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.100-125.179.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17 |
| Linux | Linux | 5.15, 0, 5.15.212 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel-livepatch-6.18.41-94.142 | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| Linux | Linux | 82cae269cfa953032fbb8980a7d554d60fb00b17, 7.2, 7.1.5 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel-livepatch-6.12.100-125.179 | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel-livepatch-6.1.180-225.360 | 0 |
…and 18 more
Timeline
- Aug 15, 2026 Coalition ESS Score
- Aug 15, 2026 CVE Published
- Aug 19, 2026 Security Advisory
- Aug 24, 2026 EPSS Score (30 in total, the first dated here)
- Oct 16, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-72192
vulnetix vdb fixes CVE-2026-72192
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72192/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart