Local system crash via unchecked block-size failure
Published Mar 4, 2026 · Updated Mar 4, 2026
Reachable assertion in the Linux Kernel allows local users to crash the system by mounting ROMFS on a loop device with an oversized block size. romfs_fill_super() ignores a zero return from sb_set_blocksize(), leaving the superblock at 32768 bytes before sb_bread() reaches the size assertion in folio_set_bh(). Triggering the crash requires permission to change a loop device's block size and mount it; the result is a kernel BUG and system service interruption.
Summary
What happened
Reachable assertion in the Linux Kernel allows local users to crash the system by mounting ROMFS on a loop device with an oversized block size. romfs_fill_super() ignores a zero return from sb_set_blocksize(), leaving the superblock at 32768 bytes before sb_bread() reaches the size assertion in folio_set_bh(). Triggering the crash requires permission to change a loop device's block size and mount it; the result is a kernel BUG and system service interruption.
The record
- CVE
- CVE-2026-23238
- Published
- Mar 4, 2026
- Updated
- Mar 4, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2026CVE publishedPublication date reported by the CVE source.
- Mar 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2c5829cd8fbbc91568c520b666898f57cdcb8cf6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4b71ad7676564a94ec5f7d18298f51e8ae53db73
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9b203b8ddd7359270e8a694d0584743555128e2c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a381f0f61b35c8894b0bd0d6acef2d8f9b08b244
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ab7ad7abb3660c58ffffdf07ff3bb976e7e0afa0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cbd9931e6456822067725354d83446c5bb813030
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2521ab1f63a8c244f06a080319e5ff9a2e1bd95
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo