CVE-2025-38211 is a slab use-after-free in the Linux kernel RDMA iWARP Connection Manager (RDMA/iWCM). Work entries are allocated for each cm_id_private object during cm_id creation and are released when the final cm_id reference is dropped. An event-handler work item can drop that final reference, causing dealloc_work_entries() to free the work object that is still executing or remains accessible to the iWCM workqueue. KASAN detects the resulting access in workqueue activation. The flaw remained after an earlier fix that flushed pending work during cm_id destruction, because that fix did not prevent the final dereference from occurring in an event-handler work context.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Use-after-free flaw in Linux kernel RDMA iwcm.
Linux kernel RDMA iwcm use-after-free of work objects following cm_id destruction.
A Linux kernel RDMA/iwcm use-after-free flaw affecting work objects after cm_id destruction.
A Linux kernel RDMA/IWCM use-after-free vulnerability affecting work objects after cm_id destruction.
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.