CVE-2023-53508: ublk: fail to start device if queue setup is interrupted
In the Linux kernel, the following vulnerability has been resolved:
ublk: fail to start device if queue setup is interrupted
In ublkctrlstartdev(), if waitforcompletioninterruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLKCMDSTARTDEV, otherwise kernel oops can be triggered.
Reported by German when working on qemu-storage-deamon which requires single thread ublk daemon.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-53508?
The severity of CVE-2023-53508 is categorized as moderate due to potential disruptions in device handling.
How do I fix CVE-2023-53508?
To fix CVE-2023-53508, update the Linux kernel to the latest stable version that resolves the vulnerability.
What impact does CVE-2023-53508 have on Linux systems?
CVE-2023-53508 can lead to failure in starting devices if queue setup is interrupted, potentially resulting in system instability.
Which versions of the Linux kernel are affected by CVE-2023-53508?
CVE-2023-53508 affects versions of the Linux kernel prior to the patch that addresses this specific vulnerability.
What is the cause of CVE-2023-53508?
CVE-2023-53508 is caused by an interruption during the queue setup process in the ublk subsystem, leading to incomplete device initialization.