CVE-2024-26615 is a Linux kernel flaw in the SMC networking subsystem, specifically in SMC-D connection diagnostic dumping code in net/smc. A crash can occur in the SMC-D connection dump path when a connection is dumped while it is still being established. In this race window, the connection may already have been registered in a link group by smc_conn_create(), but conn->rmb_desc has not yet been initialized by smc_buf_create(). The dump code then performs an illegal access to conn->rmb_desc, leading to a NULL pointer dereference in __smc_diag_dump.constprop.0 as shown by the provided kernel oops. The upstream fix adds a check before dumping to avoid dereferencing an uninitialized rmb_desc.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel SMC-D connection-dump vulnerability involving illegal rmb_desc access.
Linux kernel SMC-D connection-dump illegal rmb_desc access flaw.
Linux kernel SMC-D connection-dump illegal memory-access issue.
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.