Loading vulnerability…
CVE-2025-38415 is a race condition in the Linux kernel Squashfs filesystem mount path. Concurrent mounting of a Squashfs filesystem and a loop-device block-size change can cause squashfs_fill_super() to receive a zero return from sb_min_blocksize(). The zero block size causes the derived block-size logarithm to be set to 64, which is subsequently used as a shift count for a 64-bit value in Squashfs block reading, triggering an out-of-bounds shift. The kernel fix validates the sb_min_blocksize() result before using it.
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.
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel Squashfs flaw caused by failure to validate a zero return from sb_min_blocksize(), allowing a race involving a loop-device block-size change during Squashfs mounting to trigger an out-of-bounds shift condition. Google COS packages sys-kernel/csql-kernel-6_1 and sys-kernel/lakitu-kernel-6_1 are identified as affected; version 18244.448.6 or later contains the update.
A vulnerability addressed by the referenced CentOS 7 security advisory.
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.
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.