System crash via incorrect USB read request
Published Nov 14, 2022 · Updated Apr 30, 2025
Denial of service in the Linux Kernel 6.1-rc5 mceusb driver allows physically proximate attackers to crash the system via a malicious USB device. In mceusb_gen1_init, the driver sends an endpoint-zero read request without setting USB_DIR_IN in bRequestType, producing an invalid pipe-direction warning. Exploitation requires physical attachment of a crafted USB transceiver, and the reported consequence is resource starvation or a kernel crash.
Summary
What happened
Denial of service in the Linux Kernel 6.1-rc5 mceusb driver allows physically proximate attackers to crash the system via a malicious USB device. In mceusb_gen1_init, the driver sends an endpoint-zero read request without setting USB_DIR_IN in bRequestType, producing an invalid pipe-direction warning. Exploitation requires physical attachment of a crafted USB transceiver, and the reported consequence is resource starvation or a kernel crash.
The record
- CVE
- CVE-2022-3903
- Published
- Nov 14, 2022
- Updated
- Apr 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-843, T1499.004
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 30, 2025Record 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=Linux kernel 6.1-rc5
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.
Weakness, pattern, technique
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