Answer in brief
CVE-2025-38369 records a High severity (CVSS 7.8) vulnerability in dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bfe1d56091c1a404b3d4ce7e9809d745fc4453bb <e0051a3daa8b2cb318b03b2f9317c3e40855847a || >=bfe1d56091c1a404b3d4ce7e9809d745fc4453bb <98fd66c8ba77e3a7137575f610271014bc0e701f || >=bfe1d56091c1a404b3d4ce7e9809d745fc4453bb <aee7a7439f8c0884da87694a401930204a57128f || >=bfe1d56091c1a404b3d4ce7e9809d745fc4453bb <17502e7d7b7113346296f6758324798d536c31fd | e0051a3daa8b2cb318b03b2f9317c3e40855847a, 98fd66c8ba77e3a7137575f610271014bc0e701f, aee7a7439f8c0884da87694a401930204a57128f, 17502e7d7b7113346296f6758324798d536c31fd |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Jul 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using Running IDXD workloads in a container with the /dev directory mounted can trigger a call trace or even a kernel panic when the parent process of the container is terminated. This issue occurs because, under certain configurations, Docker does not properly propagate the mount replica back to the original mount point. In this case, when the user driver detaches, the WQ is destroyed but it still calls destroy_workqueue() attempting to completes all pending work. It's necessary to check wq->wq and skip the drain if it no longer exists.
Quoted source text, attributed separately from HOL analysis.