Loading vulnerability…
CVE-2026-45852 is a Linux kernel memory-management vulnerability in the RDMA/rxe subsystem, specifically in rxe_srq_from_init(). In the vulnerable error path, the queue pointer q is assigned to srq->rq.queue before the kernel copies the SRQ number to user space via copy_to_user(). If copy_to_user() fails, rxe_srq_from_init() calls rxe_queue_cleanup() and frees the queue, but leaves the stale pointer stored in srq->rq.queue. The caller, rxe_create_srq(), later handles the error by invoking rxe_srq_cleanup(), which calls rxe_queue_cleanup() again on the same memory. This results in a double free in kernel memory. The upstream fix is to defer the assignment srq->rq.queue = q until after copy_to_user() succeeds.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds 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.