Loading vulnerability…
CVE-2024-43871 is a memory-leak vulnerability in the Linux kernel device resource management subsystem. When a driver calls devm_free_percpu() to free memory allocated by devm_alloc_percpu(), the use of devres_destroy() fails to release the underlying allocation. The correction replaces devres_destroy() with devres_release() within devm_free_percpu().
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel memory leak occurs when devm_free_percpu() frees memory allocated by devm_alloc_percpu(). The fix replaces devres_destroy() with devres_release(). The advisory identifies affected Google COS kernel packages and rates the vulnerability Medium, with a CVSS v3 base score of 5.5 reflecting local access, low privileges, and high availability impact.
A Linux kernel memory-leak vulnerability in the devres implementation of devm_free_percpu(), caused by using devres_destroy() rather than devres_release() when releasing memory allocated with devm_alloc_percpu().
A Linux kernel devres memory-leak flaw caused by the devm_free_percpu() driver API.
Unknown
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.