System crash via unsynchronized devfreq monitor transitions
Published Apr 2, 2024 · Updated May 11, 2026
Race condition in the Linux devfreq framework from 3.8 allows local users to crash the kernel by rapidly switching device governors. The devfreq_monitor_start and devfreq_monitor_stop paths queue and cancel the same delayed-work timer without shared locking, allowing cancellation to race expiration and corrupt the timer list. Reachability requires local access to repeatedly write a devfreq device's governor sysfs attribute; the demonstrated consequence is a kernel paging fault and system availability loss.
Summary
What happened
Race condition in the Linux devfreq framework from 3.8 allows local users to crash the kernel by rapidly switching device governors. The devfreq_monitor_start and devfreq_monitor_stop paths queue and cancel the same delayed-work timer without shared locking, allowing cancellation to race expiration and corrupt the timer list. Reachability requires local access to repeatedly write a devfreq device's governor sysfs attribute; the demonstrated consequence is a kernel paging fault and system availability loss.
The record
- CVE
- CVE-2023-52635
- Published
- Apr 2, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 2, 2024CVE 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.8
- Affected versionversion=7e6fdd4bad033fa2d73716377b184fa975b0d985 <099f6a9edbe30b142c1d97fe9a4748601d995675
- Affected versionversion=7e6fdd4bad033fa2d73716377b184fa975b0d985 <0aedb319ef3ed39e9e5a7b7726c8264ca627bbd9
- Affected versionversion=7e6fdd4bad033fa2d73716377b184fa975b0d985 <31569995fc65007b73a3fff605ec2b3401b435e9
- Affected versionversion=7e6fdd4bad033fa2d73716377b184fa975b0d985 <3399cc7013e761fee9d6eec795e9b31ab0cbe475
- Affected versionversion=7e6fdd4bad033fa2d73716377b184fa975b0d985 <ae815e2fdc284ab31651d52460698bd89c0fce22
- Affected versionversion=7e6fdd4bad033fa2d73716377b184fa975b0d985 <aed5ed595960c6d301dcd4ed31aeaa7a8054c0c6
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