Local crash via Streamzap disconnect callback race
Published Apr 16, 2025 · Updated May 11, 2026
A race condition in the Linux kernel Streamzap driver allows local users to crash the system by disconnecting a Streamzap USB device. streamzap_disconnect() frees and nulls dev->raw through rc_unregister_device() before usb_kill_urb() finishes an in-progress streamzap_callback(), which then accesses the freed resource. Exploitation requires local access to a connected Streamzap receiver and precise overlap between device removal and the callback; the bounded consequence is a kernel fault and system crash.
Summary
What happened
A race condition in the Linux kernel Streamzap driver allows local users to crash the system by disconnecting a Streamzap USB device. streamzap_disconnect() frees and nulls dev->raw through rc_unregister_device() before usb_kill_urb() finishes an in-progress streamzap_callback(), which then accesses the freed resource. Exploitation requires local access to a connected Streamzap receiver and precise overlap between device removal and the callback; the bounded consequence is a kernel fault and system crash.
The record
- CVE
- CVE-2025-22027
- Published
- Apr 16, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=2.6.36
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <15483afb930fc2f883702dc96f80efbe4055235e
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <30ef7cfee752ca318d5902cb67b60d9797ccd378
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <4db62b60af2ccdea6ac5452fd20e29587ed85f57
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <8760da4b9d44c36b93b6e4cf401ec7fe520015bd
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <adf0ddb914c9e5b3e50da4c97959e82de2df75c3
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <e11652a6514ec805440c1bb3739e6c6236fffcc7
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <f1d518c0bad01abe83c2df880274cb6a39f4a457
- Affected versionversion=8e9e60640067858e8036d4d43bbf725c60613359 <f656cfbc7a293a039d6a0c7100e1c846845148c1
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