Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain initial device foothold
-
DeliveryEscalate to Android System privilege via separate vector
-
ExploitCraft malformed geniezone hypervisor call
-
ExecutionTrigger missing bounds check on write operation
-
PersistCorrupt hypervisor or kernel memory
-
ImpactAchieve privilege escalation beyond System tier
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 possess System-level privilege on the target device, as confirmed by the CVSS PR:H rating and explicitly stated in the CVE description. The device must be running one of the 36 affected MediaTek chipsets (MT6739 through MT8910 range). The attack is local only (AV:L) - remote exploitation is not possible without a separate prior-stage remote vulnerability in the chain. No user interaction is required once System privilege is obtained. Factors that limit exploitation: the System privilege prerequisite makes this inaccessible to unprivileged apps or remote attackers; exploitation requires local code execution at a high privilege tier, which is itself typically achieved via a separate vulnerability or malicious privileged app installation. The vulnerability does not apply to non-MediaTek chipsets. |
| Impact | CVSS 6.7 reflects the elevated entry barrier: AV:L requires local device access, and PR:H requires the attacker to already hold System privilege - the highest Android application-tier permission - before the exploit can be triggered. This substantially limits the realistic attacker pool to post-compromise scenarios, malicious privileged applications, or actors who have already achieved significant foothold. AC:L indicates no additional complexity is needed once those prerequisites are met, and UI:N means no victim interaction is required at exploitation time. The scope is marked unchanged (S:U), yet C:H/I:H/A:H signals total impact - consistent with escalation from System to kernel or hypervisor level. EPSS data was not provided in source intelligence; no KEV listing exists; no POC has been identified. Despite the high impact scores, the PR:H prerequisite meaningfully suppresses real-world risk to targeted attack chains rather than opportunistic mass exploitation. Security teams should prioritize patching on devices handling sensitive data where System-level malware is a plausible threat model. |
| Exploit ScenarioDerived | An attacker who has previously compromised an Android device to System privilege - via an initial access exploit chain, a malicious application granted elevated permissions, or a separate vulnerability - calls into the geniezone hypervisor interface with a malformed parameter that bypasses the missing bounds check. The resulting out-of-bounds write corrupts adjacent hypervisor or kernel memory, enabling escalation beyond System to kernel or hypervisor-level code execution. No public proof-of-concept code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 01, 2026
Local privilege escalation in MediaTek's geniezone hypervisor component affects 36 distinct chipsets spanning budget to flagship tiers. An attacker who has already achieved System-level privilege can trigger an out-of-bounds write caused by a missing bounds check, escalating further - likely into kernel or hypervisor trust boundaries - with full confidentiality, integrity, and availability impact. No public exploit identified at time of analysis, and this is not listed in the CISA KEV catalog; however, the post-compromise escalation path makes this relevant to threat actors performing multi-stage device compromise on Android-based MediaTek hardware.
RemediationAI
The primary fix is Patch ID ALPS10886526, documented in MediaTek's June 2026 Product Security Bulletin at https://corp.mediatek.com/product-security-bulletin/June-2026. MediaTek distributes security patches to OEM device manufacturers, who must then integrate and ship firmware updates to end users - meaning the timeline for end-user availability depends on each OEM's patch cycle. Users and enterprise device managers should monitor their device OEM's security update channels for June 2026 or later security patch level updates. As a compensating control where patching is delayed, restricting the installation of applications that request or exploit System-level permissions reduces the exploitability surface; however, this does not eliminate risk from pre-existing System-privilege malware. No version number for a patched firmware release was independently confirmed in available source data beyond the internal patch identifier.
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 hypervisor-based security component - a Trusted Execution Environment (TEE) isolation layer implemented on top of the ARM virtualization extensions present in MediaTek SoCs. CWE-787 (Out-of-bounds Write) indicates a write operation proceeds beyond allocated memory boundaries due to the absence of an input bounds check, which in a hypervisor context can corrupt adjacent memory structures including privilege control tables or kernel data. The CPE (cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:*) applies broadly across the MediaTek chipset portfolio, and the EUVD enumerates 36 specific affected SoCs including MT6761, MT6765, MT6853, MT6885, MT6889, MT6983, MT6991, MT8910, and MT8797, spanning IoT, mid-range, and premium Android device segments. The Patch ID ALPS10886526 and Issue ID MSV-6791 are MediaTek's internal tracking identifiers for this fix.
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:H
Primary rating from Vendor (MediaTek) · only source for this CVE.
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: ALPS10886526; Issue ID: MSV-6791.
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 geniezone Out-of-Bounds Write and Race Condition
View all 3More 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
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-33542
GHSA-xrxv-qpfw-72fv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB