Loading vulnerability…
CVE-2024-47675 is a use-after-free flaw in the Linux kernel BPF subsystem's bpf_uprobe_multi_link_attach() error handling. When bpf_link_prime() fails, the function follows an error path that frees an array of bpf_uprobe objects without first calling bpf_uprobe_unregister(). Consequently, the associated uprobe object is leaked and the freed bpf_uprobe consumer remains linked on the uprobe consumer list, leaving a dangling consumer reference.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel BPF use-after-free vulnerability in bpf_uprobe_multi_link_attach().
A use-after-free vulnerability in the Linux kernel BPF function bpf_uprobe_multi_link_attach().
A Linux kernel BPF use-after-free vulnerability in bpf_uprobe_multi_link_attach().
A Linux kernel eBPF uprobe multi-link attachment use-after-free caused by inadequate error cleanup in bpf_uprobe_multi_link_attach(). On bpf_link_prime() failure, the code frees bpf_uprobe consumer data without unregistering it from the associated uprobe consumer list.
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.