PoC Monitor
← All CVEs
CVE-2026-72209published 15 Aug 2026 05:54 UTCData: JSON · API

Linux

ntfs: validate attribute values on lookup

In the Linux kernel, the following vulnerability has been resolved: ntfs: validate attribute values on lookup ntfs_attr_find() and ntfs_external_attr_find() check that generic resident attribute values fit in their attribute records and that fixed-size resident values are large enough. For variable-length resident formats, however, the fixed part is not enough: embedded length fields can still point callers past the resident value. A crafted image can set a small resident $FILE_NAME value_length while leaving file_name_length large. Callers then trust file_name_length and read past the resident value when converting or comparing the name. This was reproduced with a crafted image under KASAN as a slab-out-of-bounds read from the kmalloc-1k MFT record copy. The stack included ntfs_lookup(), ntfs_iget(), ntfs_read_locked_inode(), ntfs_attr_name_get(), ntfs_ucstonls(), and utf16s_to_utf8s(). Add a shared attribute value validator and use it before a lookup path can return an attribute, including the AT_UNUSED enumeration case where callers inspect returned attributes directly. The helper validates resident value bounds, minimum resident value sizes, variable-length $FILE_NAME fields, and non-resident mapping-pairs metadata that was previously checked separately in both lookup paths. This also preserves the intended resident @val matching semantics in the external attribute lookup path. The old duplicated validation block overwrote the actual resident value length with the type-specific minimum length before comparing @val, so variable-length resident values could fail to match even when the bytes were identical. Keep the comparison on the actual value length, and make ntfs_attrlist_entry_add() compare resident attributes with lowest_vcn zero instead of reading the non-resident union member after a successful resident match. Reject non-resident $FILE_NAME records too: the format requires $FILE_NAME to be resident and callers treat returned records as resident.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.8critical · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 6ceb4cc81ef3409ff79dcb959771f9110787397a, < e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56
  • >= 6ceb4cc81ef3409ff79dcb959771f9110787397a, < d5803e3345dae9c6470bb61869885236276b9a35

Fixed in e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56, d5803e3345dae9c6470bb61869885236276b9a35

Linux Linux
  • 7.1

Fixed in 0, 7.1.5, 7.2

Mitigation

Upgrade Linux to e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56 or d5803e3345dae9c6470bb61869885236276b9a35 or later.

Upgrade Linux to 0 or 7.1.5 or 7.2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published15 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.