CVE-2025-38369 is a workqueue lifecycle flaw in the Linux kernel's IDXD DMA engine driver. Running IDXD workloads inside a container with the host device directory mounted can trigger a kernel call trace or panic when the container's parent process terminates. Under certain Docker configurations, mount replicas are not properly propagated back to the original mount point. During user-driver detachment, cleanup attempts to complete pending work through destroy_workqueue() despite the workqueue having already been destroyed. The fix checks whether wq->wq exists and skips draining when it does not.
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.
A Linux kernel dmaengine IDXD driver flaw involving use of a workqueue after its destruction. Under certain container mount configurations, terminating the container's parent process can cause a call trace or kernel panic. The fix checks whether the workqueue still exists before attempting to drain it. The plugin reports a CVSS v3 base score of 7.8 and recommends updating Echo linux packages to version 6.12.37-1 or later.
Linux kernel Intel IDXD DMA-engine workqueue availability flaw.
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.