← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-72192

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-72192

Key Details

CVECVE-2026-72192
CVSS Score / Version
9.8 (Critical) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-72192
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-72192
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.