CVE-2024-26982 is an out-of-bounds read vulnerability in the Linux kernel Squashfs filesystem implementation. Squashfs failed to reject inode number zero, which is reserved as an invalid/unused value. If fill_meta_index() encounters a metadata read error after allocating an index, it invalidates that index by assigning inode number zero. A later fill_meta_index() invocation can cause locate_meta_index() to match and return this unfilled invalidated index, resulting in an out-of-bounds access. The upstream fix validates inode numbers during inode creation and returns -EINVAL for zero.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Invalid inode-number handling flaw in Linux kernel Squashfs.
Linux kernel Squashfs filesystem validation flaw involving an invalid zero inode number.
Linux kernel Squashfs inode-validation flaw involving an invalid inode number of zero.
An invalid inode-number validation issue in the Linux kernel Squashfs filesystem.
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.