USB hub operation hang via sysfs lock inversion
Published May 1, 2024 · Updated May 11, 2026
Improper locking in Linux 6.0 and later affected branches allows local users to deadlock USB hub removal or reconfiguration through sysfs. The disable_show() and disable_store() callbacks in drivers/usb/core/port.c remain active while waiting for the parent hub device lock, while hub removal holds that lock and waits in device_del() for the callbacks to finish. Triggering the hang requires local low-privileged sysfs access concurrent with another process removing the hub or changing its configuration.
Summary
What happened
Improper locking in Linux 6.0 and later affected branches allows local users to deadlock USB hub removal or reconfiguration through sysfs. The disable_show() and disable_store() callbacks in drivers/usb/core/port.c remain active while waiting for the parent hub device lock, while hub removal holds that lock and waits in device_del() for the callbacks to finish. Triggering the hang requires local low-privileged sysfs access concurrent with another process removing the hub or changing its configuration.
The record
- CVE
- CVE-2024-26933
- Published
- May 1, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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.
- Affected versionversion=6.0
- Affected versionversion=f061f43d7418cb62b8d073e221ec75d3f5b89e17 <4facc9421117ba9d8148c73771b213887fec77f7
- Affected versionversion=f061f43d7418cb62b8d073e221ec75d3f5b89e17 <73d1589b91f2099e5f6534a8497b7c6b527e064e
- Affected versionversion=f061f43d7418cb62b8d073e221ec75d3f5b89e17 <9dac54f08198147f5ec0ec52fcf1bc8ac899ac05
- Affected versionversion=f061f43d7418cb62b8d073e221ec75d3f5b89e17 <f4d1960764d8a70318b02f15203a1be2b2554ca1
- Affected versionversion=f061f43d7418cb62b8d073e221ec75d3f5b89e17 <f51849833705dea5b4f9b0c8de714dd87bd6c95c
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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