linux-cve-announce - CVE-2023-53508: ublk: fail to start device if queue setup is interrupted

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100129-CVE-2023-53508-20d7@gregkh>
Date: Wed,  1 Oct 2025 13:46:00 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53508: ublk: fail to start device if queue setup is interrupted

From: Greg Kroah-Hartman <gregkh@...nel.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.

The Linux kernel CVE team has assigned CVE-2023-53508 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.0 with commit 71f28f3136aff5890cd56de78abc673f8393cad9 and fixed in 6.1.43 with commit 0d5916c439574b18a0734872daa0022b3d6105ad
	Issue introduced in 6.0 with commit 71f28f3136aff5890cd56de78abc673f8393cad9 and fixed in 6.4.8 with commit 6ab3e7d424cd413d7a5e976c8a30b4ffa84a65dd
	Issue introduced in 6.0 with commit 71f28f3136aff5890cd56de78abc673f8393cad9 and fixed in 6.5 with commit 53e7d08f6d6e214c40db1f51291bb2975c789dc2

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53508
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/block/ublk_drv.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/0d5916c439574b18a0734872daa0022b3d6105ad
	https://git.kernel.org/stable/c/6ab3e7d424cd413d7a5e976c8a30b4ffa84a65dd
	https://git.kernel.org/stable/c/53e7d08f6d6e214c40db1f51291bb2975c789dc2