Kernel privilege escalation via unchecked HTBLogKM write
Published Oct 14, 2022 · Updated May 15, 2025
Out-of-bounds write in Imagination Technologies PowerVR GPU on Android SoCs allows local users to gain kernel privileges through HTBLogKM. The HTBLogKM kernel routine performs a write without a required bounds check, allowing the operation to pass the destination buffer. A local low-privileged user can reach the flaw without user interaction and obtain kernel-level control, exposing device data and integrity.
Summary
What happened
Out-of-bounds write in Imagination Technologies PowerVR GPU on Android SoCs allows local users to gain kernel privileges through HTBLogKM. The HTBLogKM kernel routine performs a write without a required bounds check, allowing the operation to pass the destination buffer. A local low-privileged user can reach the flaw without user interaction and obtain kernel-level control, exposing device data and integrity.
The record
- CVE
- CVE-2021-0699
- Published
- Oct 14, 2022
- Updated
- May 15, 2025
- Vendor
- Imagination Technologies
- Product
- PowerVR GPU
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- May 15, 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=Android SoC
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.
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