Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall unprivileged app on device
-
DeliveryOpen vulnerable APU driver interface
-
ExploitTrigger use-after-free in APU
-
ExecutionReclaim freed object with controlled data
-
PersistCorrupt kernel memory for code execution
-
ImpactEscalate to system/kernel privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
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 have local code execution on a device using an affected MediaTek chipset (MT8781, MT6993, MT6899, MT8668, MT8910, MT8793) - typically a locally installed app or other on-device foothold - because the attack vector is Local (AV:L), not network-reachable. Once local, no special configuration, no elevated privileges (PR:N, 'no additional execution privileges needed'), and no user interaction (UI:N) are required to reach the vulnerable APU driver and trigger the use-after-free. The primary limiting factor is the need for prior on-device execution; the main de-limiting factors are that it works against default configurations, needs no user interaction, and has low attack complexity. |
| Impact | This is a genuinely high-severity local privilege escalation in the MediaTek APU (AI Processing Unit) driver stack, scoring CVSS 8.4 with vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The signals are internally consistent and credible: a use-after-free (CWE-416) yielding full confidentiality, integrity, and availability impact is the classic primitive for kernel-level privilege escalation on Android. Low attack complexity (AC:L), no required privileges (PR:N - MediaTek explicitly notes 'no additional execution privileges needed'), and no user interaction (UI:N) mean any local code already executing on the device (e.g., a low-privilege or unprivileged installed app) can attempt it reliably. The key limiting factor is the Local attack vector (AV:L): this is NOT remotely exploitable and requires the attacker to already have code execution on the device, which is why it rates 8.4 rather than 9.x. Critically, no EPSS score, no CISA KEV listing, and no public exploit were provided in the input, so there is no evidence of active exploitation or public PoC - this tempers real-world urgency relative to the raw score. Net: a real priority for the mobile/device-patching pipeline (strong local EoP primitive in a ubiquitous chipset family), but not an emergency 'drop everything' remote threat; prioritize via normal Android/vendor monthly patch cadence. |
| Exploit ScenarioDerived | A malicious or compromised Android application installed on a device with an affected MediaTek chipset invokes the vulnerable APU driver interface and triggers the use-after-free condition to corrupt kernel memory. By grooming freed memory and reclaiming it with attacker-controlled data, the app escalates from its unprivileged sandbox to kernel/system privileges without any user interaction. No public exploit code was identified at time of analysis, but UAF-to-EoP primitives in mobile kernel drivers are well-understood and realistically weaponizable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Local privilege escalation in the MediaTek APU (AI Processing Unit) driver allows an attacker with existing code execution on affected devices to trigger a use-after-free, achieving full compromise of confidentiality, integrity, and availability (CVSS 8.4). The flaw affects MediaTek chipsets MT8781, MT6993, MT6899, MT8668, MT8910, and MT8793, and requires no additional privileges or user interaction once local access is obtained. No public exploit code or active exploitation is confirmed at time of analysis.
RemediationAI
Apply the vendor-released patch identified by Patch ID ALPS11249016, as detailed in the MediaTek October 2026 Product Security Bulletin (https://www.mediatek.com/product-security-bulletin/October-2026). Device manufacturers should integrate this patch into their firmware updates; end users should install the latest security updates for their devices. Until patched, limiting local code execution-for example, by restricting installation of untrusted applications and enforcing device management policies-reduces the attack surface, though it does not eliminate the risk. No official workarounds are published; disabling the APU subsystem may not be feasible without impacting AI/ML functionality.
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
The vulnerability is a use-after-free (CWE-416) in the MediaTek APU driver, a kernel-level component that manages the AI Processing Unit hardware. The APU is a dedicated accelerator for AI/ML workloads on MediaTek systems-on-chip. A use-after-free occurs when the driver frees a memory region but later accesses it, leading to memory corruption that can be exploited for privilege escalation. With a CVSS 3.1 vector of AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, the attack requires local access (e.g., a malicious app already running on the device) but no elevated privileges or user interaction. Successful exploitation could allow an attacker to execute code with kernel or system-level privileges, compromising the entire device. The affected chipsets are MT8781, MT6993, MT6899, MT8668, MT8910, and MT8793, as listed in the ENISA EUVD advisory (EUVD-2026-92192).
Know when Mt6899 Firmware 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:N/UI:N/S:U/C:H/I:H/A:H
Local vector since it needs on-device code execution; PR:N and UI:N per vendor's 'no additional execution privileges needed', and UAF memory corruption yields full kernel-level C/I/A impact.
Primary rating from Vendor (mediatek).
CVSS VectorVendor: mediatek
Lifecycle Timeline
3DescriptionCVE.org
In apu, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11249016; Issue ID: MSV-9169.
Executive ViewAI
MediaTek chipsets MT8781, MT6993, MT6899, MT8668, MT8910, and MT8793 are affected by a high-severity local privilege escalation vulnerability in the APU driver, allowing an attacker with existing code execution to fully compromise device confidentiality, integrity, and availability. No public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, leaving affected devices at risk. Leadership should prioritize identifying and mitigating exposure, as a successful exploit could lead to complete device takeover and data breach.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting local access to affected devices, enforcing least privilege, monitoring for suspicious APU driver activity, and isolating high-value assets. Apply vendor patch when released.
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.
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Related Vulnerabilities in MediaTek apu Memory Corruption and Privilege Escalation
View all 3More in Mt6899 Firmware
View allLocal privilege escalation in MediaTek's Video HAL lets an unprivileged app already running on an affected device corrup
An out-of-bounds write in MediaTek modem (baseband) firmware allows an attacker operating a rogue base station to escala
Memory corruption in the MediaTek cellular modem baseband (an out-of-bounds write from a missing bounds check) allows an
An out-of-bounds write in MediaTek modem firmware (CWE-787) allows a nearby attacker operating a rogue base station to e
Local privilege escalation in MediaTek's meta component affects numerous MediaTek chipsets (including MT6789, MT6895, MT
Use-after-free memory corruption in MediaTek's apusys driver allows a local attacker who has already obtained Android Sy
Local privilege escalation in MediaTek AIDL on affected chipsets is possible via a use-after-free memory corruption, but
Local privilege escalation in the aidl component shipped on a defined set of MediaTek chipsets (MT6899, MT6991, MT8910,
Local privilege escalation in the MediaTek display component could allow an attacker who already holds Android System-le
A missing permission check in the MediaTek AIDL (Android Interface Definition Language) component allows an attacker who
In Modem, there is a possible system crash due to improper input validation. Rated medium severity (CVSS 6.5), this vuln
EUVD-2026-92192
GHSA-f6jh-r28v-p526
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB