TEE privilege escalation via GPU power-off race
Published Jun 13, 2024 · Updated Aug 8, 2024
A race condition in the Mali GPU power-off path in Google Android allows local users to escalate privileges into the TEE. The gpu_pm_power_off_top_nolock function in pixel_gpu_power.c performs the power-off transition without synchronization that prevents concurrent access, allowing protected memory to be compromised. A low-privileged local context and a successfully won race are required; no user interaction is needed, and success grants TEE-level privilege.
Summary
What happened
A race condition in the Mali GPU power-off path in Google Android allows local users to escalate privileges into the TEE. The gpu_pm_power_off_top_nolock function in pixel_gpu_power.c performs the power-off transition without synchronization that prevents concurrent access, allowing protected memory to be compromised. A low-privileged local context and a successfully won race are required; no user interaction is needed, and success grants TEE-level privilege.
The record
- CVE
- CVE-2024-32899
- Published
- Jun 13, 2024
- Updated
- Aug 8, 2024
- Vendor
- Product
- Android Kernel
- Classifications
- CWE-362, CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 8, 2024Record 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=android_kernel
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