Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain initial foothold on Android device
-
DeliveryEscalate to System privilege via separate vulnerability
-
ExploitCraft malformed geniezone driver request
-
ExecutionTrigger out-of-bounds read due to missing bounds check
-
PersistRead adjacent kernel/TEE-adjacent memory
-
ImpactExfiltrate sensitive data from read buffer
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | System-level privilege (android.uid.system or equivalent, distinct from root but above standard app privilege) is a hard prerequisite - the vulnerability cannot be reached from a normal or even privileged app context without a prior escalation. The vulnerable code path is in the geniezone kernel driver, which is only accessible from System-privileged processes. Limiting factors include: (1) the mandatory System privilege barrier, which requires its own exploit chain; (2) local access only - no network vector exists; (3) no user interaction required once System privilege is held, meaning it is usable silently in a post-compromise scenario. There is no indication that a specific non-default configuration or optional feature must be enabled - the geniezone driver is present on all 17 affected chipset models by default. |
| Impact | The CVSS base score of 4.4 accurately reflects a constrained vulnerability: AV:L requires physical or logical local access, and PR:H mandates that the attacker already hold System privilege - the highest Android user-space privilege level, typically attained only after a prior privilege escalation chain. This drastically limits the attack surface to post-compromise scenarios. EPSS at 0.14% (4th percentile) indicates that the broader security community does not anticipate near-term exploitation, consistent with the SSVC assessment of exploitation: none and automatable: no. Notably, there is a material discrepancy between the narrative description ('local information disclosure') and the CVSS vector (C:N/I:N/A:H): an out-of-bounds read should yield a Confidentiality impact, not an Availability impact. This inconsistency suggests a possible vendor CVSS authoring error and should be verified against the MediaTek August 2026 bulletin. The SSVC technical impact of 'partial' is consistent with a bounded information disclosure rather than a full system compromise. Overall, this is a real-but-low-urgency finding - meaningful in a post-exploitation context but not a standalone entry vector. |
| Exploit ScenarioDerived | An attacker who has already escalated to Android System privilege on a device powered by one of the 17 affected MediaTek chipsets submits a crafted ioctl or memory request to the geniezone driver without valid bounds. The missing bounds check allows the read to extend beyond the intended buffer, potentially exposing adjacent memory contents to the caller. No public proof-of-concept code exists at the time of analysis, and this scenario requires a separate prior exploit chain to reach System privilege. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Out-of-bounds read in MediaTek's GeniZone trusted execution environment (TEE) exposes memory on 17 affected chipset models to local information disclosure, but only after an attacker has already acquired System-level privilege. The vulnerability stems from a missing bounds check in the geniezone driver (CWE-125, Patch ID ALPS11036877), and is tracked by MediaTek as MSV-7132. No public exploit code exists and CISA has not listed this in KEV; with an EPSS of 0.14% (4th percentile) and SSVC exploitation status of 'none', this is a low-urgency finding despite the breadth of affected silicon.
RemediationAI
Apply the vendor-released patch identified as Patch ID ALPS11036877, available through MediaTek's August 2026 Product Security Bulletin at https://www.mediatek.com/product-security-bulletin/August-2026. Device OEMs using affected chipsets must integrate this patch into their downstream firmware builds and push updates to end users. No specific patched firmware version is independently confirmed in the available reference data beyond the patch ID. Because exploitation requires System privilege as a prerequisite, organizations that cannot immediately patch should focus on hardening against the privilege escalation steps that would lead to System access in the first place - for example, restricting sideloading of untrusted applications, enforcing SELinux in enforcing mode, and auditing system service attack surfaces. These compensating controls do not eliminate the GeniZone vulnerability but substantially raise the bar for reaching the required privilege level.
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
GeniZone is MediaTek's implementation of the ARM TrustZone Trusted Execution Environment, a hardware-enforced secure enclave that runs alongside the Android normal world. The affected CPE is cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:*, covering silicon across the MT67xx and MT87xx families. CWE-125 (Out-of-Bounds Read) occurs when driver code in geniezone processes a request without validating that a memory offset or length falls within a legitimate buffer boundary, allowing a read operation to access adjacent memory regions. Because geniezone operates at the boundary between the normal world and the secure world, unvalidated reads can potentially expose data that crosses that boundary, including cryptographic material or secure OS state, depending on memory layout at the time of exploitation.
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:N/I:N/A:H
OOB read implies Confidentiality:L, not Availability:H as vendor scored; PR:H reflects mandatory System privilege; AV:L and S:U confirmed by description.
Primary rating from Vendor (MediaTek).
CVSS VectorVendor: MediaTek
Lifecycle Timeline
3DescriptionCVE.org
In geniezone, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS11036877; Issue ID: MSV-7132.
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
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-52086
GHSA-rgfh-3wrp-q784
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB