CVE-2023-52513 is a NULL pointer dereference in the Linux kernel's RDMA Software iWARP (siw) connection-management failure path. If immediate MPA request processing fails, the newly created endpoint unlinks its listening endpoint and becomes eligible for release. Subsequent TCP socket-close processing did not handle this state correctly: siw_cm_work_handler() could dereference the now-NULL listener pointer. The corrective change handles this failed-connection state and cancels the no-longer-useful MPA timeout. It also suppresses unnecessary socket-read scheduling when the socket has already left TCP_ESTABLISHED.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel RDMA/siw connection-failure-handling flaw addressed by the Red Hat kernel update.
Linux kernel RDMA/siw connection-failure handling flaw.
Linux kernel RDMA Software iWARP connection-failure handling vulnerability.
Linux kernel software iWARP RDMA connection-failure handling vulnerability.
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.