MediaTek Chipset EUVD-2026-52079

System-level privilege (Android's highest non-root privilege tier, PR:H in the CVSS vector) must already be held by the attacker before this vulnerability can be triggered - this is the critical limiting factor. Local physical or logical access to the device is required (AV:L). The display subsystem must be active, but no non-default configuration is needed beyond the privilege prerequisite. No user interaction is required (UI:N) once System privilege is attained. What limits exploitation: the requirement to first obtain System privilege represents a near-complete device compromise on its own, severely limiting the pool of practical attackers to those already running advanced, chained exploit chains. There are no network-based or unauthenticated exploitation paths.

The CVSS 3.1 base score of 4.4 (Medium) accurately reflects the constrained attack surface. The vector AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N is internally consistent: local access with System privilege pre-required, no complexity or interaction needed, and confidentiality-only impact with no scope change. On Android, System is the highest non-root privilege tier, meaning an attacker who reaches System has already substantially compromised the device - making the incremental information disclosure a post-exploitation enrichment rather than an initial access primitive. EPSS at 0.14% (4th percentile) signals near-zero community-observed exploitation probability. SSVC confirms exploitation 'none' and automatable 'no', and technical impact is only 'partial'. There is no CISA KEV entry and no known public exploit. Cross-referencing all signals: this is a genuine low-priority issue requiring a deeply compromised device as a prerequisite. The primary risk is in chained exploit scenarios where System privilege has been obtained via a separate vulnerability and an adversary seeks memory-layout information to defeat ASLR or extract kernel secrets. This scenario, while theoretically meaningful, is not a common exploitation pattern in observed threat activity.

An attacker who has already escalated to System privilege on an affected Android device - for example, by exploiting a separate Android framework or driver vulnerability - invokes the display driver interface and sends a specially crafted request that triggers the integer overflow. The resulting out-of-bounds read returns kernel memory contents to the attacker's process, potentially disclosing memory addresses that defeat ASLR or revealing sensitive data structures. No public proof-of-concept is known, making opportunistic exploitation unlikely.