Kernel privilege escalation via unvalidated GPU request
Published Nov 13, 2024 · Updated Nov 15, 2024
Improper input validation in the Android PowerVR GPU driver allows local users to execute code with kernel privileges via a crafted GPU request. PVRSRVRGXKickTA3DKM in rgxta3d.c does not adequately validate attacker-controlled request data; the rejected field or invariant is undisclosed. Local access is sufficient, no prior execution privileges or user interaction are required, and successful exploitation grants kernel code execution.
Summary
What happened
Improper input validation in the Android PowerVR GPU driver allows local users to execute code with kernel privileges via a crafted GPU request. PVRSRVRGXKickTA3DKM in rgxta3d.c does not adequately validate attacker-controlled request data; the rejected field or invariant is undisclosed. Local access is sufficient, no prior execution privileges or user interaction are required, and successful exploitation grants kernel code execution.
The record
- CVE
- CVE-2024-31337
- Published
- Nov 13, 2024
- Updated
- Nov 15, 2024
- Vendor
- Imagination Technologies
- Product
- PowerVR GPU
- Classifications
- T1068
- Attack vector
- local
- Privileges
- unauthenticated
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