Kernel crash via unchecked zero block size
Published Jul 25, 2025 · Updated Jun 18, 2026
A race in Linux Squashfs allows local users to crash the kernel while mounting a loop-device filesystem during a block-size change. During a concurrent LOOP_SET_BLOCK_SIZE ioctl and mount, squashfs_fill_super() passes a zero sb_min_blocksize() result to ffz(), setting devblksize_log2 to 64 and causing an invalid 64-bit shift in squashfs_bio_read(). The race requires local low-privileged access to manipulate the loop device and mount Squashfs; successful triggering interrupts the host kernel.
Summary
What happened
A race in Linux Squashfs allows local users to crash the kernel while mounting a loop-device filesystem during a block-size change. During a concurrent LOOP_SET_BLOCK_SIZE ioctl and mount, squashfs_fill_super() passes a zero sb_min_blocksize() result to ffz(), setting devblksize_log2 to 64 and causing an invalid 64-bit shift in squashfs_bio_read(). The race requires local low-privileged access to manipulate the loop device and mount Squashfs; successful triggering interrupts the host kernel.
The record
- CVE
- CVE-2025-38415
- Published
- Jul 25, 2025
- Updated
- Jun 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2025CVE publishedPublication date reported by the CVE source.
- Jun 18, 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=0aa666190509ffab81c202c5095a166be23961ac <0aff95d9bc7fb5400ca8af507429c4b067bdb425
- Affected versionversion=0aa666190509ffab81c202c5095a166be23961ac <295ab18c2dbce8d0ac6ecf7c5187e16e1ac8b282
- Affected versionversion=0aa666190509ffab81c202c5095a166be23961ac <4f99357dadbf9c979ad737156ad4c37fadf7c56b
- Affected versionversion=0aa666190509ffab81c202c5095a166be23961ac <549f9e3d7b60d53808c98b9fde49b4f46d0524a5
- Affected versionversion=0aa666190509ffab81c202c5095a166be23961ac <5c51aa862cbeed2f3887f0382a2708956710bd68
- Affected versionversion=0aa666190509ffab81c202c5095a166be23961ac <6abf6b78c6fb112eee495f5636ffcc350dd2ce25
- Affected versionversion=0aa666190509ffab81c202c5095a166be23961ac <734aa85390ea693bb7eaf2240623d41b03705c84
- Affected versionversion=0aa666190509ffab81c202c5095a166be23961ac <db7096ea160e40d78c67fce52e7cc51bde049497
- Affected versionversion=2.6.29
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.
Weakness, pattern, technique
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