ublk: fail to start device if queue setup is interrupted
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 |
|
|
6.1.436.4.86.5In the Linux kernel, the following vulnerability has been resolved:
ublk: fail to start device if queue setup is interrupted
In ublk_ctrl_start_dev(), if wait_for_completion_interruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLK_CMD_START_DEV, otherwise kernel oops can be triggered.
Reported by German when working on qemu-storage-deamon which requires single thread ublk daemon.
From the CVE record · Linux
The Linux kernel’s ublk device startup can continue even if a signal interrupts queue setup. Under that condition, starting the device can trigger a kernel oops. The input does not specify authentication requirements.
Engineers running Linux kernels with ublk support should check their deployments; affected versions are not specified.