Service disruption via Yurex probe race
Published May 8, 2026 · Updated May 8, 2026
Race condition in the Yurex USB driver in the Linux Kernel allows local users to disrupt kernel availability during device probing. The yurex_probe function initializes the descriptor's bbu member after submitting an interrupt URB, allowing its completion handler's retrieved value to be overwritten. Exploitation requires local low-privileged access and precise timing during Yurex device initialization; successful triggering corrupts retrieved driver data and disrupts availability.
Summary
What happened
Race condition in the Yurex USB driver in the Linux Kernel allows local users to disrupt kernel availability during device probing. The yurex_probe function initializes the descriptor's bbu member after submitting an interrupt URB, allowing its completion handler's retrieved value to be overwritten. Exploitation requires local low-privileged access and precise timing during Yurex device initialization; successful triggering corrupts retrieved driver data and disrupts availability.
The record
- CVE
- CVE-2026-43430
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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 <3cec135415a89723e2d38e1c8cc5098203355965
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <687d26d43a5aaf44323ce7d601cf242bb87e9559
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7a875c09899ba0404844abfd8f0d54cdc481c151
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <939e3d17b843b0bae70467fef4481069d73c8520
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a41d3d9202e951995cfac6248c565423079c71fa
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a7934d7202a39c3160aa30521c382c7b744ae4a2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a8b3b3d730acea1640bc89465f2832cf06a1e13a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <af83e92c329f11139d5eea2b5b7b83c26c3f67e7
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