Loading vulnerability…
CVE-2024-43892 is a race condition in the Linux kernel memory-control-group subsystem. The mem_cgroup_idr registry requires external synchronization for mutation. While allocation and replacement operations are serialized by the cgroup mutex, removal was allowed to execute concurrently for different memory cgroups. Races between removals, or between removal and allocation or replacement, can leave valid memory cgroups absent from the registry or assign the same identifier to multiple live memory cgroups. Offlining one colliding memory cgroup can then remove list_lru state still required by another.
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.
Linux kernel memory-control-group flaw caused by insufficient protection for concurrent access to mem_cgroup_idr.
Linux kernel memory-control-group concurrent-access flaw.
Linux kernel memory-control-group concurrent-access race flaw.
Linux kernel memory-control-group concurrent-access flaw.
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.