Loading vulnerability…
CVE-2026-46176 is a Linux kernel vulnerability in the RDMA/mlx5 subsystem caused by incorrect error handling in mlx5_ib_dev_res_srq_init(). The function allocates two shared receive queues (SRQs), s0 and s1. If ib_create_srq() fails while creating s1, the error path destroys s0 but then falls through instead of exiting cleanly. As a result, the code unconditionally stores a freed s0 pointer and the ERR_PTR value for s1 into devr->s0 and devr->s1. This leaves the device resource structure in an inconsistent state. Subsequent logic can misinterpret devr->s1 as indicating successful initialization, mlx5_ib_create_qp() can dereference the freed or invalid SRQ via to_msrq(devr->s0)->msrq.srqn, and mlx5_ib_dev_res_cleanup() can dereference the ERR_PTR and double-free s0 during teardown. The upstream fix adds the missing goto unlock in the s1 failure path.
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.
6 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.