Loading vulnerability…
CVE-2025-40168 is a use-after-free vulnerability in the Linux kernel Shared Memory Communications (SMC) subsystem. The smc_clc_prfx_match() function can execute from smc_listen_work() without RCU or RTNL protection and previously accessed a socket destination's associated network device through an unsafe destination lookup. Concurrent teardown or replacement of the destination object could leave the device reference stale and result in a use-after-free. The fix uses RCU-safe destination and device access helpers.
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.
39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in the SMC subsystem related to unsafe destination/device access in smc_clc_prfx_match().
A Linux kernel SMC vulnerability in smc_clc_prfx_match() addressed by using __sk_dst_get() and dst_dev_rcu().
A Linux kernel SMC vulnerability in smc_clc_prfx_match() addressed by this Red Hat kernel security update.
A Linux kernel SMC vulnerability in smc_clc_prfx_match() addressed by using __sk_dst_get() and dst_dev_rcu().
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.