nilfs2: fix shift-out-of-bounds due to too large exponent of block size
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8b6ef451b5701b37d9a5905534595776a662edfc, Kernel a16731fa1b96226c75bbf18e73513b14fc318360, Kernel ddb6615a168f97b91175e00eda4c644741cf531c and 2 more.
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix shift-out-of-bounds due to too large exponent of block size If field s_log_block_size of superblock data is corrupted and too large, init_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds warning followed by a kernel panic (if panic_on_warn is set): shift exponent 38973 is too large for 32-bit type 'int' Call Trace: <TASK> dump_stack_lvl+0xcd/0x134 ubsan_epilogue+0xb/0x50 __ubsan_handle_shift_out_of_bounds.cold.12+0x17b/0x1f5 init_nilfs.cold.11+0x18/0x1d [nilfs2] nilfs_mount+0x9b5/0x12b0 [nilfs2] ... This fixes the issue by adding and using a new helper function for getting block size with sanity check.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.30, >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <8b6ef451b5701b37d9a5905534595776a662edfc, >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <a16731fa1b96226c75bbf18e73513b14fc318360, >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <ddb6615a168f97b91175e00eda4c644741cf531c, >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <ebeccaaef67a4895d2496ab8d9c2fb8d89201211, >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <ec93b5430ec0f60877a5388bb023d60624f9ab9f | 8b6ef451b5701b37d9a5905534595776a662edfc, a16731fa1b96226c75bbf18e73513b14fc318360, ddb6615a168f97b91175e00eda4c644741cf531c, ebeccaaef67a4895d2496ab8d9c2fb8d89201211, ec93b5430ec0f60877a5388bb023d60624f9ab9f |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket