Kernel crash via unsynchronized USB/IP stub-up
Published Mar 26, 2021 · Updated Aug 3, 2024
Race condition in Linux kernel USB/IP before 5.11.7 allows local users to crash the system during USB device export operations. In usbip_sockfd_store, the stub-up sequence starts receive and transmit threads before synchronizing device status, socket, file-descriptor, and thread-pointer state, and it retains an invalid thread pointer when thread creation fails. Reaching the flaw requires local access to issue USB/IP attach or detach requests; successful exploitation causes a kernel crash without reported data disclosure or modification.
Summary
What happened
Race condition in Linux kernel USB/IP before 5.11.7 allows local users to crash the system during USB device export operations. In usbip_sockfd_store, the stub-up sequence starts receive and transmit threads before synchronizing device status, socket, file-descriptor, and thread-pointer state, and it retains an invalid thread pointer when thread creation fails. Reaching the flaw requires local access to issue USB/IP attach or detach requests; successful exploitation causes a kernel crash without reported data disclosure or modification.
The record
- CVE
- CVE-2021-29265
- Published
- Mar 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- syzbot USB/IP race C reproducerproof of concept · validated
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