fs/jfs: Prevent integer overflow in AG size calculation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 211ed8f5e39e61f9e4d18edd64ce8005a67a1b2a, Kernel 3d8a45f87010a802aa214bf39702ca9d99cbf3ba, Kernel 55edbf5dbf60a8195c21e92124c4028939ae16b2 and 6 more.
In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Prevent integer overflow in AG size calculation The JFS filesystem calculates allocation group (AG) size using 1 << l2agsize in dbExtendFS(). When l2agsize exceeds 31 (possible with >2TB aggregates on 32-bit systems), this 32-bit shift operation causes undefined behavior and improper AG sizing. On 32-bit architectures: - Left-shifting 1 by 32+ bits results in 0 due to integer overflow - This creates invalid AG sizes (0 or garbage values) in sbi->bmap->db_agsize - Subsequent block allocations would reference invalid AG structures - Could lead to: - Filesystem corruption during extend operations - Kernel crashes due to invalid memory accesses - Security vulnerabilities via malformed on-disk structures Fix by casting to s64 before shifting: bmp->db_agsize = (s64)1 << l2agsize; This ensures 64-bit arithmetic even on 32-bit architectures. The cast matches the data type of db_agsize (s64) and follows similar patterns in JFS block calculation code. Found by Linux Verification Center (linuxtesting.org) with SVACE.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <211ed8f5e39e61f9e4d18edd64ce8005a67a1b2a, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3d8a45f87010a802aa214bf39702ca9d99cbf3ba, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <55edbf5dbf60a8195c21e92124c4028939ae16b2, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7ccf3b35274512b60ecb614e0637e76bd6f2d829, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7fcbf789629cdb9fbf4e2172ce31136cfed11e5e, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8bb29629a5e4090e1ef7199cb42db04a52802239, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c802a6a4009f585111f903e810b3be9c6d0da329, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dd07a985e2ded47b6c7d69fc93c1fe02977c8454, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ec34cdf4f917cc6abd306cf091f8b8361fedac88 | 211ed8f5e39e61f9e4d18edd64ce8005a67a1b2a, 3d8a45f87010a802aa214bf39702ca9d99cbf3ba, 55edbf5dbf60a8195c21e92124c4028939ae16b2, 7ccf3b35274512b60ecb614e0637e76bd6f2d829, 7fcbf789629cdb9fbf4e2172ce31136cfed11e5e, 8bb29629a5e4090e1ef7199cb42db04a52802239, c802a6a4009f585111f903e810b3be9c6d0da329, dd07a985e2ded47b6c7d69fc93c1fe02977c8454, ec34cdf4f917cc6abd306cf091f8b8361fedac88 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket