Local privilege escalation via unchecked tmu_set_pi write
Published Mar 11, 2024 · Updated Mar 28, 2025
Out-of-bounds write in Android 13 ACPM allows local users to gain elevated privileges through the tmu_set_pi function. The tmu_set_pi function in tmu.c performs a write without the required bounds check, permitting data to be written beyond the intended buffer. No prior execution privileges or user interaction are required, but exploitation must occur locally on an affected Pixel device.
Summary
What happened
Out-of-bounds write in Android 13 ACPM allows local users to gain elevated privileges through the tmu_set_pi function. The tmu_set_pi function in tmu.c performs a write without the required bounds check, permitting data to be written beyond the intended buffer. No prior execution privileges or user interaction are required, but exploitation must occur locally on an affected Pixel device.
The record
- CVE
- CVE-2024-27219
- Published
- Mar 11, 2024
- Updated
- Mar 28, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 28, 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.
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