UBUNTU-CVE-2026-92499: Use After Free
In the Linux kernel, the following vulnerability has been resolved: ext4: validate readdir offset before accessing dirent A corrupted directory can trigger the following KASAN report when ext4readdir() resumes from an invalid position: BUG: KASAN: use-after-free in ext4checkdirentry+0x5ef/0x820 Read of size 2 at addr ffff88810a646000 by task reprolinear/509 Call Trace: <TASK> dumpstacklvl+0x53/0x70 printreport+0xd0/0x630 kasanreport+0xce/0x100 ext4checkdirentry+0x5ef/0x820 ext4readdir+0xcde/0x2b70 iteratedir+0x1a1/0x520 x64sysgetdents64+0x12b/0x220 dosyscall64+0xf9/0x540 entrySYSCALL64afterhwframe+0x77/0x7f </TASK> KASAN reports use-after-free because the out-of-bounds access lands in an adjacent freed page. The directory buffer itself is still referenced. ext4dirllseek() invalidates the directory cookie so that ext4readdir() rescans directory entries from the start of the block. The rescan checks only the lower bound of reclen before advancing. A corrupted reclen can therefore place the offset where the block has insufficient space for a complete directory entry. The rescan itself may dereference that truncated entry, or the main loop may pass it to ext4checkdirentry(). The latter reads de->reclen before validating the range. For example: block offset 0 4092 4096 |---- de1.reclen = 4092 -----|----| de2.inode | de2.reclen ^ OOB, reported as UAF de2 starts at offset 4092 in this 4 KiB block. Its four-byte inode fits in the block, but its reclen starts at offset 4096 and crosses the boundary. The minimum safe length is inode-dependent. Encrypted and casefolded directory entries need eight additional hash bytes, while a valid metadata checksum tail is only 12 bytes. Cache the metadata checksum feature state and derive the minimum directory entry length from the on-disk format. Use it to bound both the rescan and the offset passed to the main loop. Report an offset in a truncated block tail and skip the remainder of the block, while continuing to accept an offset exactly at the block boundary.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
Fix ext4 directory readdir offset validation: cache the metadata-checksum feature state, derive the minimum directory-entry length from the on-disk format (including eight additional hash bytes for encrypted or casefolded entries and the 12-byte metadata-checksum tail), validate offsets before reading de->rec_len, bound both the rescan and the offset passed to the main loop, report offsets in truncated block tails and skip the remainder of the block while accepting an offset exactly at the block boundary, and have ext4_dir_llseek() invalidate the directory cookie so ext4_readdir() rescans from the start of the block.