Loading vulnerability…
CVE-2024-47711 is a use-after-free in the Linux kernel AF_UNIX stream socket out-of-band (OOB) handling, specifically involving manage_oob() and unix_stream_recv_urg() in net/unix/af_unix.c. The bug occurs when an OOB skb has been consumed but remains in the receive queue, and a subsequent normal recv() causes manage_oob() to return the next skb without correctly handling the case where that skb is also OOB. In that state, unix_sk(sk)->oob_skb is not cleared as required. A later recv(MSG_OOB) then dereferences unix_sk(sk)->oob_skb after the underlying skb has already been freed, producing a slab use-after-free. The issue was reported by syzbot and was exposed by commit 8594d9b85c07 ("af_unix: Don't call skb_get() for OOB skb."). The fix adds the necessary OOB checks in manage_oob() and a corresponding selftest; the upstream patch is referenced as commit 5aa57d9f2d53.
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 use-after-free in unix_stream_recv_urg() that provides a one-byte read from freed kernel memory and can be chained toward privilege escalation.
A Linux kernel use-after-free in unix_stream_recv_urg() that provides a one-byte read from freed kernel memory and was used as part of a privilege-escalation exploit chain.
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.