Bug 2400709 (CVE-2023-53508) - CVE-2023-53508 kernel: ublk: fail to start device if queue setup is interrupted
Summary: CVE-2023-53508 kernel: ublk: fail to start device if queue setup is interrupted
Keywords:
Status: NEW
Alias: CVE-2023-53508
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-01 12:02 UTC by OSIDB Bzimport
Modified: 2025-11-26 11:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2025-10-01 12:02:55 UTC 
In 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.
Comment 1 Jon Moroney 2025-10-01 23:07:00 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025100129-CVE-2023-53508-20d7@gregkh/T
Note You need to log in before you can comment on or make changes to this bug.