PoC Monitor
← All CVEs
CVE-2026-89492published 11 Sep 2026 19:43 UTCData: JSON · API

Linux

ocfs2: validate directory-index entry counts when reading metadata

In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate directory-index entry counts when reading metadata ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and signature of an indexed-directory block before it reaches higher-level callers, but neither validator bounds the ocfs2_dx_entry_list counts against the capacity of the block that holds them. ocfs2_dx_dir_search() then walks for (i = 0; i < le16_to_cpu(entry_list->de_num_used); i++) dx_entry = &entry_list->de_entries[i]; over de_num_used entries with no bounds check. entry_list is either dx_leaf->dl_list (from ocfs2_read_dx_leaf) or, for an inline root, dx_root->dr_entries. A crafted on-disk image can set de_num_used (and de_count, which is the __counted_by_le() bound of de_entries) to 0xffff and make the walk read far past the end of the 4KB metadata block, giving a slab out-of-bounds read reachable from any path lookup, stat() or open() on an indexed directory once the image is mounted. Commit 775c17386a6f ("ocfs2: validate dx_root extent list fields during block read") already bounds dr_list for the non-inline dx_root, but left the inline dr_entries path and the dx_leaf dl_list unchecked. Add the same read-time validation for both entry lists: de_count must equal the capacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and de_num_used must not exceed de_count, rejecting corrupted metadata with -EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry array. de_count is always written as exactly the block capacity when a leaf or inline root is formatted, so the equality check does not reject any valid image. Found by 0sec automated security-research tooling (https://0sec.ai).

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
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < 3f28574dd59672ac47f3110c9a8ead703ec021c0
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < 3497aa757788de5d904f41814f1df0b292a8be09
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < 47b8152ed7709f7ef30b398fb0bfe4b452dd0495
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < aad3129b8e915d0ff492bb7517d825d8490cfdd9
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < 5e661f55ca8568471fce558effe81cca112f5cb2
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < fcfcba8fe17dbf2c8805690b8cc25e32d81249a4
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < b8a5c0c32df2c5b685ceef76ac77e37c7e1dc3ed
  • >= 9b7895efac906d66d19856194e1ba61f37e231a4, < bc70726ddad53c7e9a9a85915bf2415b0d4f42f9

Fixed in 3f28574dd59672ac47f3110c9a8ead703ec021c0, 3497aa757788de5d904f41814f1df0b292a8be09, 47b8152ed7709f7ef30b398fb0bfe4b452dd0495, aad3129b8e915d0ff492bb7517d825d8490cfdd9, 5e661f55ca8568471fce558effe81cca112f5cb2, fcfcba8fe17dbf2c8805690b8cc25e32d81249a4, b8a5c0c32df2c5b685ceef76ac77e37c7e1dc3ed, bc70726ddad53c7e9a9a85915bf2415b0d4f42f9

Linux Linux
  • 2.6.30

Fixed in 0, 5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.111, 6.18.51, 7.2.4, 7.3

Mitigation

Upgrade Linux to 3f28574dd59672ac47f3110c9a8ead703ec021c0 or 3497aa757788de5d904f41814f1df0b292a8be09 or 47b8152ed7709f7ef30b398fb0bfe4b452dd0495 or aad3129b8e915d0ff492bb7517d825d8490cfdd9 or 5e661f55ca8568471fce558effe81cca112f5cb2 or fcfcba8fe17dbf2c8805690b8cc25e32d81249a4 or b8a5c0c32df2c5b685ceef76ac77e37c7e1dc3ed or bc70726ddad53c7e9a9a85915bf2415b0d4f42f9 or later.

Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.160 or 6.12.111 or 6.18.51 or 7.2.4 or 7.3 or later.

Timeline

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

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.