CVE-2023-53207Published Sep 15, 2025 · Sep 15Updated Oct 28
ublk: fail to recover device if queue setup is interrupted
Linux
Medium5.5Fix available
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 recover device if queue setup is interrupted
In ublk_ctrl_end_recovery(), if wait_for_completion_interruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLK_CMD_END_USER_RECOVERY, otherwise kernel oops can be triggered.
From the CVE record · Linux
The Linux kernel’s ublk recovery path can report successful recovery even when a signal interrupts queue setup. This can trigger a kernel oops. The input does not establish whether an attacker can trigger it or what access would be required.
Anyone running the Linux kernel with ublk should check whether their kernel is affected; no affected versions are specified.