Linux kernel RDMA/iwcm workqueue list corruption
CVE-2026-45898 is a Linux kernel vulnerability in the RDMA/iwcm subsystem. The flaw was introduced by commit e1168f0 ("RDMA/iwcm: Simplify cm_event_handler()"), which changed the logic to unconditionally call queue_work() under the assumption that queue_work() would be a no-op for already pending work. In this code path, however, RDMA/iwcm used a free list of struct iwcm_work objects with an embedded struct work_struct, so reused work items could be queued multiple times as distinct workqueue entries. The handler then walked a separate work_list until empty, allowing an item to be processed and returned to the free list while its corresponding workqueue entry was still queued. If that object was then reused and reinitialized with INIT_WORK, the stale queued entry could corrupt internal workqueue lists, resulting in list_del corruption and a kernel BUG. The upstream fix removes the redundant work_list and relies on the kernel workqueue subsystem's own tracking.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.