System crash via USB transfer cancellation race
Published Apr 29, 2020 · Updated Aug 4, 2024
A use-after-free in the Linux kernel before 5.6.8 allows physically proximate attackers to crash the system through USB activity. usb_sg_cancel can keep accessing a transfer's URBs after usb_sg_wait frees them when cancellation races with completion because no transfer reference is held. Physical USB access is required to reach the race; successful triggering can crash the system, while arbitrary code execution remains unverified.
Summary
What happened
A use-after-free in the Linux kernel before 5.6.8 allows physically proximate attackers to crash the system through USB activity. usb_sg_cancel can keep accessing a transfer's URBs after usb_sg_wait frees them when cancellation races with completion because no transfer reference is held. Physical USB access is required to reach the race; successful triggering can crash the system, while arbitrary code execution remains unverified.
The record
- CVE
- CVE-2020-12464
- Published
- Apr 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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