LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26934: USB: core: Fix deadlock in usb_deauthorize_interface()

In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in usb_deauthorize_interface() Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface's parent USB device. The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can't complete until the device lock has been released, and the lock won't be released until the removal has finished. The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback. Reported-and-tested by: Yue Sun <samsun1006219@gmail.com> Reported by: xingwei lee <xrivendell7@gmail.com>

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can deadlock USB device handling during interface deauthorization and device removal. The likely business impact is availability: affected systems may hang in USB management paths. The sources do not provide CVSS, public exploit evidence, or broad remote exposure claims.

Executive priority

Treat as a routine-to-priority kernel maintenance item, higher for appliances or physically accessible systems where USB workflows matter. No active exploitation is cited, but unresolved kernel deadlocks can create operational availability risk.

Technical view

CVE-2024-26934 fixes a USB core deadlock in usb_deauthorize_interface(). A sysfs attribute callback takes an ancestor USB device lock while removal waits for callbacks to finish, creating a lock wait cycle. The kernel fix uses sysfs_break_active_protection() so sysfs does not wait on that callback.

Likely exposure

Exposure is most relevant to Linux systems using USB interface authorization or handling USB device removal/configuration changes. Embedded products, appliances, and servers with accessible USB management paths should be checked against vendor kernel advisories.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. Based on the description, abuse would depend on reaching USB sysfs authorization behavior and concurrent USB removal or configuration activity.

Researcher notes

The core issue is lock ordering between sysfs callbacks and USB device removal. interface_authorized_store() calls usb_deauthorize_interface(), which locks the parent USB device; removal via device_del() waits for active sysfs callbacks, producing the deadlock fixed by sysfs_break_active_protection().

Mitigation direction

  • Apply vendor Linux kernel updates containing the referenced stable fixes.
  • Check Debian LTS and product vendor advisories for packaged kernel status.
  • For appliances, confirm whether vendor firmware incorporates the fixed kernel.
  • Limit unnecessary local access to USB authorization sysfs controls.
  • Track Siemens advisory guidance for affected industrial products.

Validation and detection

  • Inventory running Linux kernel versions across servers, endpoints, and appliances.
  • Map kernels to vendor advisories referencing CVE-2024-26934.
  • Confirm patched packages include the relevant stable kernel commits.
  • Identify systems using USB authorization or exposed physical USB workflows.
  • Document unsupported kernels needing vendor escalation or replacement.
Prepared
Confidence
high
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26934 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
13Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9unaffected
LinuxLinux4.4, 0, 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.