Loading vulnerability…
CVE-2025-38415 is a Linux kernel Squashfs flaw caused by failure to validate the return value of sb_min_blocksize() in squashfs_fill_super(). During a race between mounting a Squashfs filesystem backed by a loop device and changing that loop device's block size, sb_min_blocksize() can return zero. The zero value is stored as the device block size, after which the derived base-2 logarithm becomes 64. Squashfs subsequently uses this value as a shift count in squashfs_bio_read(), producing an undefined 64-bit shift-out-of-bounds condition. The fix rejects a zero return from sb_min_blocksize() before the invalid block-size state can be used.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
29 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel memory corruption vulnerability in Squashfs caused by incorrect block size calculation.
A Linux kernel memory corruption vulnerability in Squashfs caused by incorrect block size calculation.
A Linux kernel Squashfs memory-corruption vulnerability caused by an incorrect block-size calculation.
A Linux kernel memory corruption vulnerability in Squashfs caused by incorrect block size calculation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.