s390/vfio_ccw: Cancel existing workqueues
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e5f84dbaea59b4f712dac428c337528b70e1c533 · < b7ae0f7993867d009a4b554fc1d6d451c10580a0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio_ccw: Cancel existing workqueues
The initialization of the io_work and crw_work workqueues begs the question of whether they should be un-initialized. Add the corresponding cleanup tags in _release_dev to ensure work isn't dispatched after the private struct is free'd.
From the CVE record · Linux
The Linux kernel's s390/vfio_ccw component did not cancel its io_work and crw_work workqueues during device release, allowing work to be dispatched after a private structure was freed. The input does not specify what an attacker could do or whether exploitation requires network or local access, authentication, or user interaction.
Engineers running Linux kernels with s390/vfio_ccw should check their versions; affected versions are not specified.