EUVD-2026-92191
GHSA-5fq6-5rjv-rwvv
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRun unprivileged code on device
-
ExploitInvoke APU component interface
-
ExecutionTrigger double-free (CWE-415)
-
ImpactCrash service causing local DoS
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Double free prevention
|
| Exploitation Conditions | Requires the attacker to already be able to execute code locally on an affected MediaTek-based device (e.g., a malicious or compromised installed application) and to reach the APU (AI Processing Unit) component that contains the double-free. No authentication, elevated privileges, or user interaction are needed once local code execution exists (AV:L/PR:N/UI:N). Exploitation is limited to devices built on the enumerated affected chipsets (MT8781, MT6899, MT8668, MT8910, MT6993) running unpatched firmware; the flaw cannot be triggered remotely or over a network, and impact is confined to availability (crash/DoS) with no data exposure or code-execution gain. |
| Impact | All exploitability signals point to a locally-scoped, availability-only issue. The provided CVSS:3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 6.2) confirms local attack vector with low complexity, no privileges and no user interaction, but impact is limited to availability (A:H) with zero confidentiality or integrity impact - consistent with the description of a double-free (CWE-415) causing an application crash and local denial of service. No EPSS score, KEV listing, POC, or SSVC decision data was supplied in the input, so exploitation probability and automatability cannot be quantified. The absence of a network vector means this cannot be exploited remotely or wormed across devices; realistic abuse requires code already running on the device (e.g., a malicious or compromised app). This is therefore a moderate, not high, operational priority: a genuine robustness/crash bug worth patching in the normal Android/MediaTek security-bulletin cadence, but not an emergency. Note one minor tension to verify: the vector lists PR:N (no privileges) yet local exploitation of the APU component still presupposes the attacker can execute code on the device, which is an implicit access precondition not captured by the base metrics. |
| Exploit ScenarioDerived | A malicious or compromised unprivileged application installed on a MediaTek-based device issues crafted requests to the APU (AI Processing Unit) component, triggering a double-free condition. The resulting memory corruption crashes the affected process/service, producing a local denial of service. No public exploit was identified in the provided data, and no user interaction or elevated privileges are required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
A double-free flaw in MediaTek's AI Processing Unit (APU) component allows a locally executing attacker - such as a malicious or compromised installed application - to crash an affected device, producing a local denial of service. Per the assessed CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), no authentication, elevated privileges, or user interaction are required once local code execution is achieved, and the impact is limited to availability; there is no data exposure or code-execution gain from this defect. Exploitation is confined to devices built on the enumerated MediaTek chipsets (MT8781, MT6899, MT8668, MT8910, MT6993) running unpatched firmware; no public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
RemediationAI
Apply the vendor fix identified by Patch ID ALPS11249024, which is distributed through the MediaTek October 2026 product security bulletin (https://www.mediatek.com/product-security-bulletin/October-2026); because the patch is delivered to OEMs rather than end users directly, asset owners should track the corresponding firmware or monthly security update from their device manufacturer for chipsets MT8781, MT6899, MT8668, MT8910, and MT6993 and verify the build includes the ALPS11249024 change. Where the update cannot be deployed immediately, the practical compensating control is to shrink the local attack surface: restrict or remove untrusted third-party applications on affected devices and use Android's app sandboxing, permission controls, and (on managed fleets) enterprise policy to block sideloaded APKs, since this flaw requires the attacker to already run code locally - a trade-off that limits usability for bring-your-own-application scenarios but does not affect the APU's availability-window exposure from already-installed malicious software. There is no network-facing mitigation because the vector is local-only (AV:L), and no configuration toggle is documented that disables the APU code path without impairing AI/accelerator functionality, so patching remains the only complete fix. Note that per available data a vendor patch is available; the absence of a released public exploit at time of analysis does not reduce the need to update.
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 double-free (CWE-415) in the APU - MediaTek's dedicated AI/neural-processing block - where the same memory allocation is released twice, corrupting the allocator's internal state. In memory-unsafe C/C++ code paths typical of kernel drivers and firmware running on the APU, a double free can be escalated by an attacker who controls the intervening reallocation, but in this instance the assessed impact is strictly availability: the corrupted heap leads to a crash of the APU and potentially the host system rather than a controlled write primitive. The CVSS 3.1 vector AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H confirms the attack is local-only, low complexity, requires no privileges or user interaction, does not cross a security scope boundary, and yields a high availability impact with no confidentiality or integrity loss. The affected attack surface is the kernel/driver interface exposed to applications running on the device, meaning any app with access to the APU device node or its ioctl interface can trigger the faulty free path. MediaTek tracks the fix under Patch ID ALPS11249024 and Issue ID MSV-9168, with details published in the vendor's October 2026 product security bulletin.
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:N/I:N/A:H
Local vector since exploitation needs on-device code; no privileges or interaction required, and a double-free crash yields availability-only impact (A:H, C:N, I:N).
Primary rating from Vendor (mediatek).
CVSS VectorVendor: mediatek
Lifecycle Timeline
3DescriptionCVE.org
In apu, there is a possible application crash due to double free. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11249024; Issue ID: MSV-9168.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
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
Exploit-DB