Loading vulnerability…
A vulnerability in the Linux kernel Soft-iWARP (RDMA/siw) receive path allows a malicious connected iWARP peer to supply a peer-controlled MPA length field that is smaller than the minimum header size required for the announced opcode. The flaw arises because the receive logic parses the full DDP/RDMAP header based on the opcode-specific header length but does not validate that the MPA length is at least that minimum before performing signed arithmetic. In siw_tcp_rx_data(), the remaining FPDU length is derived from the attacker-controlled MPA length minus the already received header bytes plus the MPA header size, which can underflow to a negative signed integer. That negative value is then propagated through write and read-response processing, passes memory interval checks that do not safely handle negative lengths, and ultimately reaches skb_copy_bits() as a signed copy length that is promoted to a large size_t value. This can trigger a multi-gigabyte out-of-bounds copy from kernel memory and has been observed by KASAN as a use-after-free during the receive path. The fix adds validation that rejects malformed FPDUs whose MPA length is smaller than the opcode-specific minimum, terminating the connection as a framing error.
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.
1 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.