Local privilege escalation via unchecked device-memory changes
Published Nov 13, 2024 · Updated Nov 14, 2024
Missing authorization in Android SoC PowerVR-GPU code allows local users to gain elevated privileges through arbitrary code execution. DevmemIntChangeSparse2 in devicemem_server.c changes sparse device-memory mappings without the required permission check. A low-privileged local user can reach the flaw without user interaction and execute code with elevated privileges on affected devices.
Summary
What happened
Missing authorization in Android SoC PowerVR-GPU code allows local users to gain elevated privileges through arbitrary code execution. DevmemIntChangeSparse2 in devicemem_server.c changes sparse device-memory mappings without the required permission check. A low-privileged local user can reach the flaw without user interaction and execute code with elevated privileges on affected devices.
The record
- CVE
- CVE-2024-40671
- Published
- Nov 13, 2024
- Updated
- Nov 14, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-862, CWE-94, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 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_soc
- 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.
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