CVE-2023-53580

Source
https://cve.org/CVERecord?id=CVE-2023-53580
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53580.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2023-53580
Downstream
BELL (1)
DEBIAN (1)
RHSA (1)
SUSE (12)
UBUNTU (1)
Related
Published
2025-10-04T15:43:57Z
Modified
2026-11-13T04:02:41Z
Severity
  • 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
USB: Gadget: core: Help prevent panic during UVC unconfigure
Details

In the Linux kernel, the following vulnerability has been resolved:

USB: Gadget: core: Help prevent panic during UVC unconfigure

Avichal Rakesh reported a kernel panic that occurred when the UVC gadget driver was removed from a gadget's configuration. The panic involves a somewhat complicated interaction between the kernel driver and a userspace component (as described in the Link tag below), but the analysis did make one thing clear: The Gadget core should accomodate gadget drivers calling usb_gadget_deactivate() as part of their unbind procedure.

Currently this doesn't work. gadget_unbind_driver() calls driver->unbind() while holding the udc->connect_lock mutex, and usb_gadget_deactivate() attempts to acquire that mutex, which will result in a deadlock.

The simple fix is for gadget_unbind_driver() to release the mutex when invoking the ->unbind() callback. There is no particular reason for it to be holding the mutex at that time, and the mutex isn't held while the ->bind() callback is invoked. So we'll drop the mutex before performing the unbind callback and reacquire it afterward.

We'll also add a couple of comments to usb_gadget_activate() and usb_gadget_deactivate(). Because they run in process context they must not be called from a gadget driver's ->disconnect() callback, which (according to the kerneldoc for struct usb_gadget_driver in include/linux/usb/gadget.h) may run in interrupt context. This may help prevent similar bugs from arising in the future.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53580.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
d8195536ce2624e2947d9f56b1a61e7a27874bd3
Fixed
bed19d95fcb9c98dfaa9585922b39a2dfba7898d
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
286d9975a838d0a54da049765fa1d1fb96b89682
Fixed
8c1edc00db65f6d4408b3d1cd845e8da3b9e0ca4
Fixed
65dadb2beeb7360232b09ebc4585b54475dfee06
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
85102a45c7390caf124a3a5796574446f1e037b9

Affected versions

v6.*
v6.1.35
v6.1.36
v6.1.37
v6.1.38
v6.1.39
v6.1.40
v6.1.41
v6.1.42
v6.1.43
v6.1.44
v6.1.45
v6.3.10
v6.3.11
v6.3.12
v6.3.13
v6.3.9

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53580.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.1.35
Fixed
6.1.46
Type
ECOSYSTEM
Events
Introduced
6.3.9
Fixed
6.4
Type
ECOSYSTEM
Events
Introduced
6.4.0
Fixed
6.4.11

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53580.json"