[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122429-CVE-2023-54159-5908@gregkh>
Date: Wed, 24 Dec 2025 14:07:56 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54159: usb: mtu3: fix kernel panic at qmu transfer done irq handler
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: mtu3: fix kernel panic at qmu transfer done irq handler
When handle qmu transfer irq, it will unlock @mtu->lock before give back
request, if another thread handle disconnect event at the same time, and
try to disable ep, it may lock @mtu->lock and free qmu ring, then qmu
irq hanlder may get a NULL gpd, avoid the KE by checking gpd's value before
handling it.
e.g.
qmu done irq on cpu0 thread running on cpu1
qmu_done_tx()
handle gpd [0]
mtu3_requ_complete() mtu3_gadget_ep_disable()
unlock @mtu->lock
give back request lock @mtu->lock
mtu3_ep_disable()
mtu3_gpd_ring_free()
unlock @mtu->lock
lock @mtu->lock
get next gpd [1]
[1]: goto [0] to handle next gpd, and next gpd may be NULL.
The Linux kernel CVE team has assigned CVE-2023-54159 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.2 with commit 48e0d3735aa557a8adaf94632ca3cf78798e8505 and fixed in 5.4.243 with commit 26ca30516b2c49dd04c134cbdf122311c538df98
Issue introduced in 5.2 with commit 48e0d3735aa557a8adaf94632ca3cf78798e8505 and fixed in 5.10.180 with commit 012936502a9cb7b0604e85bb961eb15e2bb40dd9
Issue introduced in 5.2 with commit 48e0d3735aa557a8adaf94632ca3cf78798e8505 and fixed in 5.15.111 with commit ee53a7a88027cea765c68f3b00a50b8f58d6f786
Issue introduced in 5.2 with commit 48e0d3735aa557a8adaf94632ca3cf78798e8505 and fixed in 6.1.28 with commit f26273428657ef4ca74740e578ae45a3be492f6f
Issue introduced in 5.2 with commit 48e0d3735aa557a8adaf94632ca3cf78798e8505 and fixed in 6.2.15 with commit b636aff94a67be46582d4321d11743f1a10cc2c1
Issue introduced in 5.2 with commit 48e0d3735aa557a8adaf94632ca3cf78798e8505 and fixed in 6.3.2 with commit 3a7d4959560a2ee493ef222e3b63d359365f41ec
Issue introduced in 5.2 with commit 48e0d3735aa557a8adaf94632ca3cf78798e8505 and fixed in 6.4 with commit d28f4091ea7ec3510fd6a3c6d433234e7a2bef14
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-54159
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/usb/mtu3/mtu3_qmu.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/26ca30516b2c49dd04c134cbdf122311c538df98
https://git.kernel.org/stable/c/012936502a9cb7b0604e85bb961eb15e2bb40dd9
https://git.kernel.org/stable/c/ee53a7a88027cea765c68f3b00a50b8f58d6f786
https://git.kernel.org/stable/c/f26273428657ef4ca74740e578ae45a3be492f6f
https://git.kernel.org/stable/c/b636aff94a67be46582d4321d11743f1a10cc2c1
https://git.kernel.org/stable/c/3a7d4959560a2ee493ef222e3b63d359365f41ec
https://git.kernel.org/stable/c/d28f4091ea7ec3510fd6a3c6d433234e7a2bef14
Powered by blists - more mailing lists