CVE-2023-53580

Kernel crash via UVC gadget unbind deadlock

Published Oct 4, 2025 · Updated Oct 4, 2025

Deadlock in the Linux kernel USB Gadget core 6.1.35 through 6.1.45 and 6.3.9 through 6.4.10 allows local users to crash the kernel. gadget_unbind_driver() invokes the driver's unbind callback while holding udc->connect_lock, which usb_gadget_deactivate() tries to acquire again. A local user with access to the UVC gadget video node can hold a subscribed handle during routine gadget teardown, causing a permanent USB-subsystem hang, kernel panic, or use-after-free with kernel-memory access.

CVSS severity7.8
High
EPSS probability0.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Deadlock in the Linux kernel USB Gadget core 6.1.35 through 6.1.45 and 6.3.9 through 6.4.10 allows local users to crash the kernel. gadget_unbind_driver() invokes the driver's unbind callback while holding udc->connect_lock, which usb_gadget_deactivate() tries to acquire again. A local user with access to the UVC gadget video node can hold a subscribed handle during routine gadget teardown, causing a permanent USB-subsystem hang, kernel panic, or use-after-free with kernel-memory access.

The record

CVE
CVE-2023-53580
Published
Oct 4, 2025
Updated
Oct 4, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 4, 2025CVE publishedPublication date reported by the CVE source.
  2. Oct 4, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=286d9975a838d0a54da049765fa1d1fb96b89682 <65dadb2beeb7360232b09ebc4585b54475dfee06
  2. Affected versionversion=286d9975a838d0a54da049765fa1d1fb96b89682 <8c1edc00db65f6d4408b3d1cd845e8da3b9e0ca4
  3. Affected versionversion=6.4
  4. Affected versionversion=85102a45c7390caf124a3a5796574446f1e037b9
  5. Affected versionversion=d8195536ce2624e2947d9f56b1a61e7a27874bd3 <bed19d95fcb9c98dfaa9585922b39a2dfba7898d

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=286d9975a838d0a54da049765fa1d1fb96b89682 <65dadb2beeb7360232b09ebc4585b54475dfee06; version=286d9975a838d0a54da049765fa1d1fb96b89682 <8c1edc00db65f6d4408b3d1cd845e8da3b9e0ca4; version=6.4; version=85102a45c7390caf124a3a5796574446f1e037b9; version=d8195536ce2624e2947d9f56b1a61e7a27874bd3 <bed19d95fcb9c98dfaa9585922b39a2dfba7898d

Published CVSS scores

7.8Linux CVE teamCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo