Local privilege escalation via unchecked temperature step
Published Apr 5, 2024 · Updated Mar 25, 2025
Out-of-bounds write in Google Pixel ACPM firmware allows local users to elevate privileges through a crafted temperature-control step. The tmu_set_control_temp_step function in tmu.c performs the write without first enforcing the required bounds. Exploitation needs no additional execution privileges or user interaction and can compromise confidentiality and integrity without interrupting service.
Summary
What happened
Out-of-bounds write in Google Pixel ACPM firmware allows local users to elevate privileges through a crafted temperature-control step. The tmu_set_control_temp_step function in tmu.c performs the write without first enforcing the required bounds. Exploitation needs no additional execution privileges or user interaction and can compromise confidentiality and integrity without interrupting service.
The record
- CVE
- CVE-2024-29753
- Published
- Apr 5, 2024
- Updated
- Mar 25, 2025
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 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=acpm
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.
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