CVE-2026-52910 is a Linux kernel memory-safety vulnerability in BPF/reuseport handling. When a UDP reuseport group has an attached classic BPF (cBPF) reuseport program and that program is replaced or detached via the setsockopt() path (including reuseport_attach_prog() or reuseport_detach_prog()), the kernel may free the detached reuseport cBPF program immediately through sk_reuseport_prog_free(), bpf_release_orig_filter(), and bpf_prog_free() without waiting for an RCU grace period. Concurrent packet-processing paths, including reuseport_select_sock() during UDP socket selection, may still access the program as RCU readers. This creates a race condition leading to use-after-free behavior and observed vmalloc out-of-bounds reads in reuseport_select_sock(). The upstream fix defers freeing the reuseport cBPF program until after one RCU grace period.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.