Loading vulnerability…
CVE-2024-41058 is a slab use-after-free vulnerability in the Linux kernel CacheFiles/FS-Cache subsystem. A race between teardown of a CacheFiles daemon and failure-driven teardown of an EROFS filesystem mount can cause an FS-Cache volume to be freed after its reference count reaches zero while it remains linked in the cache volume list. Concurrent cache withdrawal subsequently invokes fscache_withdraw_volume() and dereferences the freed volume, including its access-count state. The fix acquires a reference with fscache_try_get_volume() before withdrawing a volume; if the reference count is already zero, withdrawal waits until the object has been removed from the cache volume list.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel CacheFiles/FS-Cache use-after-free caused by a race between failed mount cleanup and cache daemon exit. A volume can be freed while cache withdrawal still accesses it. The fix adds reference-count protection through fscache_try_get_volume(). The advisory assigns a CVSS v3 score of 7.8 and recommends updating affected Google COS kernel packages to version 18613.0.3 or later.
Slab use-after-free vulnerability in the Linux kernel FS-Cache volume-withdrawal path.
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.