romfs: check sb_set_blocksize() return value
CVE-2026-23238 is fixed in 23 products on 1 platform, first by DEBIAN-CVE-2026-23238, released March 4, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: romfs: check sb_set_blocksize() return value romfs_fill_super() ignores the return value of sb_set_blocksize(), which can fail if the requested block size is incompatible with the block device's configuration. This can be triggered by setting a loop device's block size larger than PAGE_SIZE using ioctl(LOOP_SET_BLOCK_SIZE, 32768), then mounting a romfs filesystem on that device. When sb_set_blocksize(sb, ROMBSIZE) is called with ROMBSIZE=4096 but the device has logical_block_size=32768, bdev_validate_blocksize() fails because the requested size is smaller than the device's logical block size. sb_set_blocksize() returns 0 (failure), but romfs ignores this and continues mounting. The superblock's block size remains at the device's logical block size (32768). Later, when sb_bread() attempts I/O with this oversized block size, it triggers a kernel BUG in folio_set_bh(): kernel BUG at fs/buffer.c:1582! BUG_ON(size > PAGE_SIZE); Fix by checking the return value of sb_set_blocksize() and failing the mount with -EINVAL if it returns 0.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| bpftool-debuginfo · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-debuginfo · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-debuginfo-common-aarch64 · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-debuginfo-common-x86_64 · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-devel · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-headers · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-libbpf · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-libbpf-debuginfo · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-libbpf-devel · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-libbpf-static · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-livepatch-6.1.164-196.303 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-modules-extra · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-modules-extra-common · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-tools · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-tools-debuginfo · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| kernel-tools-devel · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| linux · Debian 12.15 (bookworm) | 6.1.164-1 | DEBIAN-CVE-2026-23238 | Mar 4, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.74-2 | DEBIAN-CVE-2026-23238 | Mar 4, 2026 |
| linux · Debian 14 | 6.18.13-1 | DEBIAN-CVE-2026-23238 | Mar 4, 2026 |
| perf · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| perf-debuginfo · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| python3-perf · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
| python3-perf-debuginfo · amzn 2023 | 1:6.1.164-196.303.amzn2023 | ALAS2023-2026-1491 | Mar 16, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.