Loading vulnerability…
CVE-2024-26982 is an out-of-bounds read vulnerability in the Linux kernel Squashfs filesystem caused by accepting an invalid inode number of zero. If fill_meta_index() encounters a data-read error after allocating a metadata index through empty_meta_index(), it invalidates the index by setting its inode number to zero, the marker for an unused index. A subsequent locate_meta_index() lookup for an inode numbered zero can return that invalidated, unfilled index. Processing it as a populated index causes an out-of-bounds access in fill_meta_index(), potentially resulting in denial of service.
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.
20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel Squashfs out-of-bounds access vulnerability caused by failure to reject the invalid inode number zero during inode creation. The fix adds validation that returns -EINVAL for inode number zero.
A Linux kernel Squashfs out-of-bounds access vulnerability caused by inadequate validation of an invalid zero inode number during metadata-index handling.
A vulnerability addressed by the referenced CentOS 7/TuxCare security update; no technical flaw details are provided.
A Linux kernel Squashfs inode-validation flaw addressed by checking for an invalid zero inode number. Listed as fixed by the updated container image.
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.