CVE-2026-46145 is a Linux kernel memory-safety vulnerability in the RDMA/mana subsystem. The flaw arises because rx_hash_key_len is sourced from a userspace-accessible uAPI structure and was passed directly to memcpy without validating that the supplied length fits the destination buffer. An attacker able to invoke the affected interface can provide an oversized length value, causing memcpy to write past the intended bounds and corrupt kernel memory. The issue was fixed by adding bounds validation for rx_hash_key_len before the copy operation.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in RDMA/mana related to insufficient validation of rx_hash_key_len.
A Linux kernel vulnerability in RDMA/mana related to insufficient validation of rx_hash_key_len.
A Linux kernel vulnerability in RDMA/mana where the rx_hash_key_len value from a user-accessible API structure is passed unchecked to memcpy, allowing a kernel memory overflow.
A Linux kernel vulnerability in RDMA/mana related to insufficient validation of rx_hash_key_len.
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.