Kernel memory corruption via removal-time ISR race
Published May 8, 2026 · Updated May 8, 2026
Use-after-free in the renesas_usbhs driver in affected Linux Kernel releases allows local users to corrupt kernel memory during device removal. The usbhs_remove() path frees the pipe array before disabling and synchronizing usbhs_interrupt, so an interrupt can dereference the released array. Exploitation requires root or CAP_SYS_ADMIN access to the sysfs unbind control and a hardware interrupt during a narrow, unreliable race window.
Summary
What happened
Use-after-free in the renesas_usbhs driver in affected Linux Kernel releases allows local users to corrupt kernel memory during device removal. The usbhs_remove() path frees the pipe array before disabling and synchronizing usbhs_interrupt, so an interrupt can dereference the released array. Exploitation requires root or CAP_SYS_ADMIN access to the sysfs unbind control and a hardware interrupt during a narrow, unreliable race window.
The record
- CVE
- CVE-2026-43426
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- admin
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=3.0
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <0b7d11fd6e742ecc0b1eca44b4f0b93140c74bae
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <1899edac312ef17a7234851686e8a703f56d0a84
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <3cbc242b88c607f55da3d0d0d336b49bf1e20412
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <51afaf919bbaacdd9cc9e146033ae0a743a42dd7
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <6287e0c01ccb818e7214f88d885ffb7c9e81b0e0
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <6ffe44f022c95b1b29c691d2169c5abc046f7580
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <9c6159d5b72d5fc265cce5da04f27d730b552e69
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <c7012fc73dab4829404fedeeaa8531f12ac8545f
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