CVE-2026-46181 is a race condition in the Linux kernel RDMA/mlx4 subsystem's mlx4_srq_event() function. The event path relied on RCU despite mlx4_srq objects not being freed through RCU and being accessed outside an RCU read-side critical section. An event may therefore reference an SRQ object before its initialization completes, resulting in unsafe access to a partially initialized object. The fix replaces the unsafe RCU handling with spinlock protection, uses refcount_inc_not_zero() to prevent references to incomplete objects, and delays refcount_set() until full SRQ initialization has completed.
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.
27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Unity Linux vulnerability requiring local access, low privileges, and high attack complexity, with potential high impact to confidentiality, integrity, and availability.
A specific vulnerability referenced in a Unity Linux local security check advisory/plugin. The content indicates it is a locally exploitable flaw with high impact on confidentiality, integrity, and availability.
A Linux kernel RDMA/mlx4 vulnerability involving misuse of RCU in mlx4_srq_event().
A Linux kernel RDMA/mlx4 vulnerability caused by misuse of RCU in mlx4_srq_event().
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.