Loading vulnerability…
CVE-2023-52775 is a race condition in the Linux kernel net/smc implementation for Shared Memory Communications over RDMA (SMC-R). During SMC connection establishment, an LLC confirm-link timeout can cause both peers to send SMC DECLINE messages. The original client timeout was shorter than the server timeout, allowing a DECLINE message to arrive after the connection had already fallen back to TCP. The fallback TCP application stream could then consume the SMC protocol control message as application data, causing data corruption. The upstream fix doubles the client timeout relative to the server timeout so DECLINE messages do not cross or collide during confirm-link timeout processing.
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 networking data-corruption issue.
Unknown
A Linux kernel net/smc flaw that can cause data corruption when an SMC connection is declined. The issue is rated medium severity by Red Hat.
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.