CVE-2026-23238: romfs: check sb_set_blocksize() return value

Published Mar 4, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

romfs: check sbsetblocksize() return value

romfsfillsuper() ignores the return value of sbsetblocksize(), 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 PAGESIZE using ioctl(LOOPSETBLOCKSIZE, 32768), then mounting a romfs filesystem on that device.

When sbsetblocksize(sb, ROMBSIZE) is called with ROMBSIZE=4096 but the device has logicalblocksize=32768, bdevvalidateblocksize() fails because the requested size is smaller than the device's logical block size. sbsetblocksize() 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 sbbread() attempts I/O with this oversized block size, it triggers a kernel BUG in foliosetbh():

kernel BUG at fs/buffer.c:1582! BUGON(size > PAGESIZE);

Fix by checking the return value of sbsetblocksize() and failing the mount with -EINVAL if it returns 0.

Affected Software

20 affected componentsFixes available
linux/kernel
Linux Linux kernel>=2.6.12.1<5.10.251
Linux Linux kernel>=5.11<5.15.201
Linux Linux kernel>=5.16<6.1.164
Linux Linux kernel>=6.2<6.6.127
Linux Linux kernel>=6.7<6.12.74
Linux Linux kernel>=6.13<6.18.13
Linux Linux kernel=2.6.12
Linux Linux kernel=2.6.12-rc2
Linux Linux kernel=2.6.12-rc3
Linux Linux kernel=2.6.12-rc4
Linux Linux kernel=2.6.12-rc5
Linux Linux kernel=6.19-rc1
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
Linux Linux kernel=6.19-rc5
Linux Linux kernel=6.19-rc6
Linux Linux kernel=6.19-rc7
Microsoft cbl2 kernel 5.15.200.1-1

Event History

Mar 4, 2026
CVE Published
via MITRE·02:38 PM
Data Sourced
via MITRE·02:38 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 5, 2026
Data Sourced
via Microsoft·09:04 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·09:04 AM
Affected Software
Updated
via Microsoft·09:04 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-23238?

CVE-2026-23238 has a moderate severity rating due to potential data corruption issues.

2

How do I fix CVE-2026-23238?

To fix CVE-2026-23238, update to the latest version of the Linux kernel where the vulnerability has been patched.

3

What systems are affected by CVE-2026-23238?

CVE-2026-23238 affects certain versions of the Linux kernel that utilize the romfs filesystem.

4

What is the potential impact of CVE-2026-23238?

The potential impact of CVE-2026-23238 includes system instability and possible data corruption.

5

Is CVE-2026-23238 being actively exploited?

As of the latest information, there are no known active exploits for CVE-2026-23238.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203