Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessExploit separate OS or app vulnerability for System access
-
DeliveryIdentify unpatched affected MediaTek chipset
-
ExploitCraft malicious geniezone hypervisor call
-
ExecutionSupply input bypassing missing bounds check
-
PersistTrigger out-of-bounds write in TEE memory
-
ImpactEscalate execution to hypervisor or secure-world privilege
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already hold System-level (PR:H) privileges on the target Android device - this is explicitly a post-compromise escalation vector, not an initial access technique. The device must be physically or logically accessible to the attacker (AV:L) and must run one of the confirmed affected MediaTek chipsets (MT8775, MT8796, MT8797, MT8771, MT6989, MT8791T, MT8792, MT8755, MT8768, MT8781, MT8798) without vendor patches ALPS10965550 or ALPS11393405 applied. No user interaction is required once System access is established. The primary limiting factor is the PR:H prerequisite: neither user-level nor standard admin access is sufficient - a full System-level compromise must already exist. Exploitation does not require a network-reachable interface, a specific non-default configuration, or any special device state beyond having an affected, unpatched chipset. |
| Impact | The vendor-supplied CVSS vector AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N is internally consistent with the description: local-only access, no user interaction required, but critically demanding PR:H (System privileges). This high-privilege prerequisite is the dominant risk-limiting factor - exploitation is not viable without first compromising a privileged process via a separate vulnerability. EPSS at 0.13% (3rd percentile) strongly corroborates the low exploitation likelihood, and the absence of a CISA KEV listing and any known POC code further reduces urgency. Despite the C:H and I:H impact metrics suggesting full data compromise once exploited, the overall real-world risk is moderate at best outside of targeted, sophisticated attack chains. This vulnerability matters most in high-security environments where full-chain exploitation (initial System access plus this escalation) is a credible threat model, such as national security, critical infrastructure, or high-value enterprise Android fleets. |
| Exploit ScenarioDerived | An attacker who has already compromised a System-privileged process on an Android device - for example via a separate OS or application vulnerability - identifies the target as running an affected MediaTek chipset. The attacker then crafts a malicious call into the geniezone hypervisor component, supplying input designed to bypass the absent bounds check. The resulting out-of-bounds memory write in the TEE/hypervisor layer escalates execution context beyond System, potentially reaching the hypervisor or secure-world trust level. No public exploit code exists at the time of analysis, making opportunistic exploitation unlikely. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Out-of-bounds write in MediaTek's GenieZone hypervisor component enables local privilege escalation beyond System-level access on a wide range of MediaTek mobile chipsets. Exploitation is constrained to attackers who have already obtained System privileges, making this a secondary step in a multi-stage attack chain rather than an initial foothold technique. No public exploit code exists and EPSS of 0.13% (3rd percentile) confirms negligible real-world exploitation activity; no CISA KEV listing at time of analysis.
RemediationAI
MediaTek has released patches ALPS10965550 and ALPS11393405 addressing Issue MSV-6941, confirmed in the August 2026 Product Security Bulletin at https://www.mediatek.com/product-security-bulletin/August-2026. OEM device manufacturers using affected chipsets should integrate these patches into firmware builds and distribute security updates to end users. While awaiting OEM patch delivery, limit the installation of untrusted applications capable of escalating to System-level privileges - specifically restrict sideloading of APKs with elevated permissions and enforce Android Work Profile or SELinux policies to constrain System-privileged processes. Note that these compensating controls reduce exposure but cannot fully prevent exploitation by an already-privileged attacker; patching via OEM firmware update is the definitive fix.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GenieZone is MediaTek's TrustZone-based hypervisor and Trusted Execution Environment (TEE) implementation embedded across their mobile chipset lineup. CWE-787 (Out-of-bounds Write) identifies the root cause: the geniezone component fails to enforce boundary validation before writing to a memory region, allowing a caller with System-level privileges to corrupt memory beyond the intended buffer. The sensitivity of this flaw is amplified by its location in the TEE/hypervisor layer, which is architecturally intended to be isolated from the normal operating system. A successful write primitive in this context can undermine the fundamental security boundary between the Android OS and the secure world. Affected CPE is cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:* covering chipsets MT8775, MT8796, MT8797, MT8771, MT6989, MT8791T, MT8792, MT8755, MT8768, MT8781, and MT8798.
Know when Mediatek Chipset gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
Local vector and System-level privilege required; out-of-bounds write yields full confidentiality and integrity impact with no documented availability impact.
Primary rating from Vendor (MediaTek).
CVSS VectorVendor: MediaTek
Lifecycle Timeline
2DescriptionCVE.org
In geniezone, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10965550 / ALPS11393405; Issue ID: MSV-6941.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Related Vulnerabilities in MediaTek GenieZone Privilege Escalation and Info Leaks
View all 4More in Mediatek Chipset
View allOut-of-bounds write in MediaTek modem firmware enables remote privilege escalation when devices connect to attacker-cont
Heap buffer overflow in the vdec (video decoder) kernel driver across 53+ MediaTek SoCs allows a local unprivileged atta
Local privilege escalation in MediaTek's vdec (video decoder) kernel driver affects more than 53 distinct chipset varian
Heap-based buffer overflow in the MediaTek WLAN AP driver enables an adjacent-network attacker to escalate privileges wi
Out-of-bounds write in MediaTek modem chipset implementations allows remote privilege escalation when user equipment con
Heap buffer overflow in the MediaTek WLAN access point driver allows adjacent-network attackers with low-privilege user
Local privilege escalation in MediaTek's Bluetooth driver affects six Wi-Fi/Bluetooth combo chipsets (MT7902, MT7920, MT
Local privilege escalation in MediaTek GenieZone (trusted execution environment) allows an attacker who has already gain
Privilege escalation in MediaTek's Android Telephony component enables any locally-installed application - regardless of
Out-of-bounds read in MediaTek modem firmware across 19 chipsets enables remote denial of service when a User Equipment
Remote privilege escalation in the baseband modem firmware of dozens of MediaTek chipsets allows an attacker operating a
Privilege escalation via a double-free memory corruption bug in camera middleware affects 17 MediaTek chipset variants,
EUVD-2026-52070
GHSA-76m9-f2pj-7mwp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB