CVE-2023-53580
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-03-23
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.4 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.4 |
| linux | linux_kernel | From 6.4.1 (inc) to 6.4.11 (exc) |
| linux | linux_kernel | From 6.1.35 (inc) to 6.1.46 (exc) |
| linux | linux_kernel | From 6.3.9 (inc) to 6.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves a kernel panic in the Linux kernel's USB gadget driver subsystem. Specifically, when the UVC gadget driver is removed from a gadget's configuration, a deadlock can occur because the gadget_unbind_driver() function holds a mutex (udc->connect_lock) while calling the driver's unbind callback, and the usb_gadget_deactivate() function tries to acquire the same mutex, causing a deadlock and kernel panic. The fix involves releasing the mutex before calling the unbind callback to prevent this deadlock.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic (crash) when the UVC gadget driver is unconfigured, leading to system instability or downtime. This can disrupt normal operations on systems using the affected USB gadget drivers, potentially causing loss of service or data until the system is rebooted or the issue is resolved.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your Linux kernel to a version that includes the fix for the USB Gadget core panic issue during UVC unconfigure. The fix involves changes to the gadget_unbind_driver() function to properly release and reacquire the mutex during unbind callbacks, preventing deadlocks and kernel panics. Applying the latest kernel patches or updates from your Linux distribution that address this issue is recommended.