CVE-2024-46744 affects symbolic-link handling in the Linux kernel's Squashfs filesystem. Insufficient validation allows squashfs_read_inode() to assign a corrupted on-disk symbolic-link size to inode->i_size. When squashfs_symlink_read_folio() subsequently assigns that size to a signed integer length variable, an oversized value becomes negative. The negative length causes the loop responsible for populating the page to be skipped, leaving the page uninitialized. Subsequent symbolic-link processing triggers an uninitialized-value use in pick_link(), detected by KMSAN.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel Squashfs vulnerability involving insufficient validation of symbolic link sizes. A corrupted on-disk size can become negative when assigned to a signed integer, preventing page initialization and causing an uninitialized-memory access. The advisory rates it High, with a CVSS v3 base score of 7.8, and identifies affected Google COS kernel packages.
Linux kernel Squashfs symbolic-link-size validation flaw.
Linux kernel vulnerability covered by the security update.
A vulnerability referenced in a Red Hat Enterprise Linux 9.6 kernel-package security update; the content provides no technical flaw description.
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.