System crash via unchecked USB endpoints
Published Mar 25, 2026 · Updated Mar 25, 2026
Improper USB endpoint validation in the Linux Kernel pegasus driver allows physically proximate attackers to crash Linux systems with a malicious device. The pegasus_probe path binds without confirming the expected number and types of endpoints, then blindly accesses URBs associated with endpoints that can be absent. Exploitation requires physical USB access and a kernel with the pegasus driver available; success interrupts the affected host by crashing the kernel.
Summary
What happened
Improper USB endpoint validation in the Linux Kernel pegasus driver allows physically proximate attackers to crash Linux systems with a malicious device. The pegasus_probe path binds without confirming the expected number and types of endpoints, then blindly accesses URBs associated with endpoints that can be absent. Exploitation requires physical USB access and a kernel with the pegasus driver available; success interrupts the affected host by crashing the kernel.
The record
- CVE
- CVE-2026-23290
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <11de1d3ae5565ed22ef1f89d73d8f2d00322c699
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <43d7c4114b1ec14f41f09306525d3b9382286fc1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7f8505c7ce3f186ef9d2495f3c0bd6ad6fce999f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <95556b4e879711693c9865ba0938c148f62d5ea4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c3f1672eaea68c5cb6e1ec081cdb92045453218f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee31ec8cf1eafeefa85ef934ba688d27f88bf0e2
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
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