System crash via pre-clock register access
Published Jul 3, 2025 · Updated May 11, 2026
A probe-ordering flaw in Linux 3.0 and later allows local users to crash RZ/V2H systems when the renesas_usbhs driver initializes. usbhs_probe() calls usbhs_sys_clock_ctrl(), which reaches iowrite16() before runtime power management acquires and enables the clocks needed for register access. The failure requires a Renesas RZ/V2H system using this USB controller driver; initialization can trigger a synchronous external abort and stop the affected system.
Summary
What happened
A probe-ordering flaw in Linux 3.0 and later allows local users to crash RZ/V2H systems when the renesas_usbhs driver initializes. usbhs_probe() calls usbhs_sys_clock_ctrl(), which reaches iowrite16() before runtime power management acquires and enables the clocks needed for register access. The failure requires a Renesas RZ/V2H system using this USB controller driver; initialization can trigger a synchronous external abort and stop the affected system.
The record
- CVE
- CVE-2025-38136
- Published
- Jul 3, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 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=3.0
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <095cc0b5888acc228f12344e85b17539b9ce9367
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <0a1e16a6cbf4452b46f20b862d6141a1e90844ee
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <155453ada562c450a4ff5fcf4852b9fa5b6b793a
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <1637623ad6205162b17804d07512e6f4cbd2a050
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <6bab152e817fd41b9e178fa6b275354795c9703d
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <d4c368e4a638ddf4a9d6d687b0ff691aa46cce53
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <db96a4fd8614d47c0def265e0e6c996b0ee52a38
- Affected versionversion=f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 <ffb34a60ce86656ba12d46e91f1ccc71dd221251
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