Local kernel privilege escalation via dangling GPU mapping
Published Nov 13, 2024 · Updated Nov 15, 2024
Use-after-free in the PowerVR GPU DDK from Imagination Technologies 24.1 and earlier allows local users to gain kernel privileges. DevmemIntChangeSparse2 fails to track multiple sparse mappings, leaving a dangling GPU page-table entry after physical memory is freed. Non-privileged software on an affected Android SoC can issue GPU system calls to read and write freed physical memory without user interaction.
Summary
What happened
Use-after-free in the PowerVR GPU DDK from Imagination Technologies 24.1 and earlier allows local users to gain kernel privileges. DevmemIntChangeSparse2 fails to track multiple sparse mappings, leaving a dangling GPU page-table entry after physical memory is freed. Non-privileged software on an affected Android SoC can issue GPU system calls to read and write freed physical memory without user interaction.
The record
- CVE
- CVE-2024-34729
- Published
- Nov 13, 2024
- Updated
- Nov 15, 2024
- Vendor
- Imagination Technologies
- Product
- PowerVR GPU
- Classifications
- T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 15, 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=0 <*
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