ocfs2: validate inline data i_size during inode read
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.6.136, Kernel 6.18.24, Kernel 6.19.14 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate inline data i_size during inode read When reading an inode from disk, ocfs2_validate_inode_block() performs various sanity checks but does not validate the size of inline data. If the filesystem is corrupted, an inode's i_size can exceed the actual inline data capacity (id_count). This causes ocfs2_dir_foreach_blk_id() to iterate beyond the inline data buffer, triggering a use-after-free when accessing directory entries from freed memory. In the syzbot report: - i_size was 1099511627576 bytes (~1TB) - Actual inline data capacity (id_count) is typically <256 bytes - A garbage rec_len (54648) caused ctx->pos to jump out of bounds - This triggered a UAF in ocfs2_check_dir_entry() Fix by adding a validation check in ocfs2_validate_inode_block() to ensure inodes with inline data have i_size <= id_count. This catches the corruption early during inode read and prevents all downstream code from operating on invalid data.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=2.6.24.1 <6.6.136, >=6.13 <6.18.24, >=6.19 <6.19.14, >=6.7 <6.12.83, =2.6.24, =7.0, >=23193e513d1cd69411469f028d56fd175d4a6b07 <1524af3685b35feac76662cc551cbc37bd14775f, >=23193e513d1cd69411469f028d56fd175d4a6b07 <37f074e65f24f10f8d8df224a572e4cb9e6faf63, >=23193e513d1cd69411469f028d56fd175d4a6b07 <77d0295725109d77f5854ef5b58c0d06c08168cc, >=23193e513d1cd69411469f028d56fd175d4a6b07 <bcd46bc261b215b3b12c557a978299eafa02ecdd, >=23193e513d1cd69411469f028d56fd175d4a6b07 <c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1b, >=23193e513d1cd69411469f028d56fd175d4a6b07 <cd2d765aa7157f852999842af32148128c735d39, >=23193e513d1cd69411469f028d56fd175d4a6b07 <d012c782abcabe68b5b9e71be58a15e9f9d83dc1, >=23193e513d1cd69411469f028d56fd175d4a6b07 <131c0b573e1b467b7d553e9ff38003f1acd8f5f2 | 6.6.136, 6.18.24, 6.19.14, 6.12.83, 1524af3685b35feac76662cc551cbc37bd14775f, 37f074e65f24f10f8d8df224a572e4cb9e6faf63, 77d0295725109d77f5854ef5b58c0d06c08168cc, bcd46bc261b215b3b12c557a978299eafa02ecdd, c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1b, cd2d765aa7157f852999842af32148128c735d39, d012c782abcabe68b5b9e71be58a15e9f9d83dc1, 131c0b573e1b467b7d553e9ff38003f1acd8f5f2 |
| linux-kernel: Kernel | >=2.6.24 <5.10.258, >=5.11.0 <5.15.209, >=5.16.0 <6.1.175, >=6.13.0 <6.18.24, >=6.19.0 <6.19.14, >=6.2.0 <6.6.136, >=6.7.0 <6.12.83 | 5.10.258, 5.15.209, 6.1.175, 6.18.24, 6.19.14, 6.6.136, 6.12.83 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket