MediaTek apusys CVE-2026-20468

Exploitation requires the attacker to already hold System-level (UID=1000) Android privileges on a device equipped with a MediaTek MT8196 or MT8366 chipset - this is not a remote or unprivileged attack vector. The apusys subsystem must be active, which is the default state on affected chipsets that include AI/ML acceleration hardware. User interaction is not required once System-level code execution has been established. Limiting factors include: the high privilege prerequisite (System UID must already be obtained through a separate vector), local-only attack surface (AV:L), chipset specificity (MT8196 and MT8366 only), and the Android security stack - SELinux enforcement in enforcing mode, application sandboxing, and verified boot all represent barriers that must be defeated before this vulnerability can be reached.

The CVSS 3.1 base score of 6.0 (Medium) accurately reflects the constrained attack surface: AV:L demands local code execution; PR:H requires pre-existing System-level privileges, positioning this squarely as a post-compromise privilege escalation step rather than an initial access vector. The EPSS score of 0.14% at the 4th percentile is consistent with the high prerequisite privilege bar - exploitation is technically feasible only within an already-compromised Android environment, suppressing broad opportunistic interest. No CISA KEV listing exists, and no public proof-of-concept has been identified. The C:H and I:H impact ratings are significant once the bar is cleared, but the PR:H gate substantially limits real-world risk to targeted attack chains such as sandbox escapes or privilege escalation ladders in rooted or malware-infected devices. One notable data tension: the description attributes the flaw to a 'confused deputy' (CWE-441), while NVD assigns CWE-787 (Out-of-Bounds Write) - the exact relationship between these two root causes is not fully explained in available public data, introducing minor uncertainty about the precise exploitation mechanism.

An attacker who has already achieved System-level (UID=1000) code execution on an Android device running a MediaTek MT8196 or MT8366 chipset - for example, via a prior exploit chain, a malicious privileged application, or device rooting - submits a crafted request to the apusys kernel driver. The confused deputy condition causes the driver to perform an out-of-bounds write on the attacker's behalf, enabling escalation of privileges beyond the System boundary toward kernel or trusted execution environment access. No public proof-of-concept code has been identified at time of analysis.