linux-cve-announce - CVE-2023-53207: ublk: fail to recover 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2025091510-CVE-2023-53207-5025@gregkh>
Date: Mon, 15 Sep 2025 16:21:41 +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-53207: ublk: fail to recover 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 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.

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


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

	Issue introduced in 6.1 with commit c732a852b419fa057b53657e2daaf9433940391c and fixed in 6.1.43 with commit 84415f934ad4e96f3507fd09b831953d60fb04ec
	Issue introduced in 6.1 with commit c732a852b419fa057b53657e2daaf9433940391c and fixed in 6.4.8 with commit b3a1e243a74632f88b22e713f1c7256754017d58
	Issue introduced in 6.1 with commit c732a852b419fa057b53657e2daaf9433940391c and fixed in 6.5 with commit 0c0cbd4ebc375ceebc75c89df04b74f215fab23a

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-53207
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/84415f934ad4e96f3507fd09b831953d60fb04ec
	https://git.kernel.org/stable/c/b3a1e243a74632f88b22e713f1c7256754017d58
	https://git.kernel.org/stable/c/0c0cbd4ebc375ceebc75c89df04b74f215fab23a