CVE-2023-53580 Details
Description
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.
A kernel panic vulnerability has been identified in the Linux USB gadget driver, specifically within the UVC (USB Video Class) component. This issue arises when the UVC gadget driver is removed from a gadget's configuration, leading to a kernel panic. The problem stems from a deadlock situation: the 'gadget_unbind_driver' function calls the driver's 'unbind' method while holding a mutex, and the 'usb_gadget_deactivate' function tries to acquire the same mutex, causing a deadlock. The vulnerability affects several versions of the Linux kernel.
The vulnerability has been addressed in the Linux kernel. Users can upgrade to the latest version of the stable Linux kernel to apply the fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/65dadb2beeb7360232b09ebc4585b54475dfee06 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8c1edc00db65f6d4408b3d1cd845e8da3b9e0ca4 | kernel.org | Patch |
| https://git.kernel.org/stable/c/bed19d95fcb9c98dfaa9585922b39a2dfba7898d | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.1.35, < 6.1.46 >= 6.3.9, < 6.4 >= 6.4.1, < 6.4.11 6.4 - 6.4 rc7 6.5 rc1 6.5 rc2 6.5 rc3 6.5 rc4 6.5 rc5 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Mar 23, 2026 | Modified Analysis | [email protected] |
| Feb 10, 2026 | Initial Analysis | [email protected] |
| Oct 4, 2025 | New CVE Received | kernel.org |