Loading vulnerability…
CVE-2024-35797 addresses two bugs in the Linux kernel's cachestat functionality when operating on shmem (shared memory) objects. The first bug involves a race condition where a swapin error can leave a poisoned swap entry in the shmem inode's xarray. If get_shadow_from_swap_cache() is called on this entry without proper validation, it can result in an out-of-bounds access to swapper_spaces[]. The second bug occurs when a valid swap entry is found in the shmem inode, but the corresponding shadow entry in the swapcache does not exist (due to ongoing swap IO or removal). This can result in a NULL pointer being passed to workingset_test_recent(), leading to potentially incorrect 'recently evicted' counts, though not a crash.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.