Local privilege escalation via GED bounds omission
Published Jan 11, 2021 · Updated Aug 3, 2024
GPU Extension Device (GED) in MediaTek Android SoC allows local users with System privileges to escalate privileges through a crafted local interaction. The GED kernel driver writes beyond a memory buffer because a bounds check is missing, corrupting kernel memory. Exploitation requires existing System execution privileges and no user interaction; consequences include elevation of privilege with potential confidentiality, integrity, and availability impact.
Summary
What happened
GPU Extension Device (GED) in MediaTek Android SoC allows local users with System privileges to escalate privileges through a crafted local interaction. The GED kernel driver writes beyond a memory buffer because a bounds check is missing, corrupting kernel memory. Exploitation requires existing System execution privileges and no user interaction; consequences include elevation of privilege with potential confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2021-0301
- Published
- Jan 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- MediaTek
- Product
- GPU Extension Device (GED)
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
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