Local privilege escalation via unchecked thermal-window write
Published Mar 11, 2024 · Updated Apr 16, 2025
Out-of-bounds write in Google Android 13 allows local users to escalate privileges through crafted thermal-management input. The config_gov_time_windows function in tmu.c fails to bounds-check data before writing it to a destination buffer. A local low-privileged context is required; exploitation needs no user interaction and grants elevated privileges.
Summary
What happened
Out-of-bounds write in Google Android 13 allows local users to escalate privileges through crafted thermal-management input. The config_gov_time_windows function in tmu.c fails to bounds-check data before writing it to a destination buffer. A local low-privileged context is required; exploitation needs no user interaction and grants elevated privileges.
The record
- CVE
- CVE-2024-22008
- Published
- Mar 11, 2024
- Updated
- Apr 16, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record 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=13
- Affected versionversion=13.0
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