CVE-2023-53207
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-15

Last updated on: 2025-12-04

Assigner: kernel.org

Description
In 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-15
Last Modified
2025-12-04
Generated
2026-06-16
AI Q&A
2025-09-15
EPSS Evaluated
2026-06-14
NVD
CVE-2023-53207
Affected Vendors & Products
Showing 5 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.1 (inc) to 6.1.43 (exc)
linux linux_kernel From 6.2 (inc) to 6.4.8 (exc)
linux linux_kernel 6.5
linux linux_kernel 6.5
linux linux_kernel 6.5
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

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

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 could affect the availability and reliability of systems running the affected kernel version.

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