CVE-2023-53508
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-01

Last updated on: 2025-10-02

Assigner: kernel.org

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-01
Last Modified
2025-10-02
Generated
2026-06-16
AI Q&A
2025-10-01
EPSS Evaluated
2026-06-14
NVD
CVE-2023-53508
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability occurs in the Linux kernel's ublk subsystem. Specifically, in the function ublk_ctrl_start_dev(), if the wait_for_completion_interruptible() call is interrupted by a signal, the device queues are not set up properly. If the UBLK_CMD_START_DEV command is not failed in this case, it can lead to a kernel oops (a kernel crash). The fix ensures that the device start fails if the queue setup is interrupted, preventing the kernel from crashing.

Impact Analysis

If this vulnerability is triggered, it can cause the Linux kernel to crash (kernel oops), potentially leading to system instability or downtime. This can affect systems using the ublk device subsystem, especially when signals interrupt the device start process, causing failure in device initialization and possible disruption of services relying on this functionality.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2023-53508. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart