CVE-2024-58088 is an improper-locking flaw in the Linux kernel BPF subsystem's cgroup-storage cleanup path. When freeing a BPF cgroup-storage map, bpf_cgrp_storage passed a NULL busy counter to bpf_local_storage_map_free(). This allowed BPF activity invoked during cleanup to recursively attempt acquisition of local_storage->lock while that lock was already held, resulting in a deadlock. The vulnerable functionality was introduced with cgroup storage support for non-cgroup-attached BPF programs.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel BPF cgroup-storage freeing deadlock.
A medium-severity local denial-of-service vulnerability in the Linux kernel eBPF cgroup-storage handling. An authenticated local user with low privileges can trigger a kernel deadlock by exercising BPF programs and repeatedly creating and destroying a program, affecting system availability.
Linux kernel BPF cgroup-storage deadlock flaw.
A Linux kernel eBPF cgroup-storage locking flaw that can cause a deadlock while freeing a BPF map. The issue arises because the cgroup-storage map-free path did not pass the busy counter to bpf_local_storage_map_free(), allowing recursive BPF program activity to acquire local_storage->lock while the free path holds 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.