Device crash via unchecked USB interface index
Published Feb 16, 2022 · Updated Aug 3, 2024
Memory corruption in the Linux kernel before 5.16.10 allows physically proximate attackers to crash USB Gadget devices via control requests. The composite_setup function uses an unvalidated interface number from wValue to index a 16-entry interface array and can dereference a null function pointer. Exploitation requires exposed USB Gadget OS descriptors and physical control of the USB host; one crafted transfer can crash the device.
Summary
What happened
Memory corruption in the Linux kernel before 5.16.10 allows physically proximate attackers to crash USB Gadget devices via control requests. The composite_setup function uses an unvalidated interface number from wValue to index a 16-entry interface array and can dereference a null function pointer. Exploitation requires exposed USB Gadget OS descriptors and physical control of the USB host; one crafted transfer can crash the device.
The record
- CVE
- CVE-2022-25258
- Published
- Feb 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 16, 2022CVE 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
- d-os-descriptor demo exploitproof of concept · demonstrated
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