Local kernel memory corruption via devfreq statistics read
Published Mar 18, 2024 · Updated Aug 5, 2026
Buffer overflow in Linux kernel 3.8 and later allows local users to corrupt kernel memory by reading a devfreq trans_stat file. The trans_stat_show function repeatedly appends transition-table rows with snprintf without stopping when its PAGE_SIZE sysfs buffer is full, so later writes extend past the allocation. Any unprivileged local user able to read the exposed attribute can trigger the overflow, leading to kernel memory disclosure, code execution, or a crash.
Summary
What happened
Buffer overflow in Linux kernel 3.8 and later allows local users to corrupt kernel memory by reading a devfreq trans_stat file. The trans_stat_show function repeatedly appends transition-table rows with snprintf without stopping when its PAGE_SIZE sysfs buffer is full, so later writes extend past the allocation. Any unprivileged local user able to read the exposed attribute can trigger the overflow, leading to kernel memory disclosure, code execution, or a crash.
The record
- CVE
- CVE-2023-52614
- Published
- Mar 18, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=0 <*
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