CVE-2024-26933USB: core: Fix deadlock in port "disable" sysfs attribute
- 7.8HighCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in port "disable" sysfs attribute The show and store callback routines for the "disable" sysfs attribute file in port.c acquire the device lock for the port's parent hub device. This can cause problems if another process has locked the hub to remove it or change its configuration: Removing the hub or changing its configuration requires the hub interface to be removed, which requires the port device to be removed, and device_del() waits until all outstanding sysfs attribute callbacks for the ports have returned. The lock can't be released until then. But the disable_show() or disable_store() routine can't return until after it has acquired the lock. The resulting deadlock can be avoided by calling sysfs_break_active_protection(). This will cause the sysfs core not to wait for the attribute's callback routine to return, allowing the removal to proceed. The disadvantage is that after making this call, there is no guarantee that the hub structure won't be deallocated at any moment. To prevent this, we have to acquire a reference to it first by calling hub_get().
Timeline
ID reserved
By Linux
- 2 months later
· 2 months later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected f061f43d7418cb62b8d073e221ec75d3f5b89e17 – < 9dac54f08198147f5ec0ec52fcf1bc8ac899ac05
- affected f061f43d7418cb62b8d073e221ec75d3f5b89e17 – < f51849833705dea5b4f9b0c8de714dd87bd6c95c
- affected f061f43d7418cb62b8d073e221ec75d3f5b89e17 – < 4facc9421117ba9d8148c73771b213887fec77f7
- affected f061f43d7418cb62b8d073e221ec75d3f5b89e17 – < 73d1589b91f2099e5f6534a8497b7c6b527e064e
- affected f061f43d7418cb62b8d073e221ec75d3f5b89e17 – < f4d1960764d8a70318b02f15203a1be2b2554ca1
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.84 – ≤ 6.1.*
- unaffected 6.6.24 – ≤ 6.6.*
- unaffected 6.7.12 – ≤ 6.7.*
- unaffected 6.8.3 – ≤ 6.8.*
- unaffected 6.9 – ≤ *
References
References5
- https://git.kernel.org/stable/c/9dac54f08198147f5ec0ec52fcf1bc8ac899ac05 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/f51849833705dea5b4f9b0c8de714dd87bd6c95c (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/4facc9421117ba9d8148c73771b213887fec77f7 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/73d1589b91f2099e5f6534a8497b7c6b527e064e (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/f4d1960764d8a70318b02f15203a1be2b2554ca1 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-24195 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-26933)Record last updated .