dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s dmaengine idxd driver can use a workqueue after it has been destroyed. Running IDXD workloads in a container with /dev mounted can trigger a call trace or kernel panic when the container’s parent process is terminated under certain Docker mount configurations. The described trigger involves local workload execution; the input does not specify authentication requirements.
Engineers running Linux kernels with the dmaengine idxd driver, particularly those running IDXD workloads in containers with /dev mounted; affected versions are not specified.