Graphics DDK EUVD-2026-54346

Exploitation requires three specific concurrent conditions: (1) the target platform must have hardware-level Trusted Execution Environment (TEE) support (e.g., ARM TrustZone) with Imagination Technologies GPU hardware present and an affected Graphics DDK version installed; (2) the attacker must have already obtained REE kernel-level code execution or write control in the normal-world OS - this is the binding prerequisite and is a high privilege bar, not a standard low-privilege user session; and (3) the GPU Firmware must execute a save or restore of internal data between tightly coupled private memory and main memory while the tampered pointer is in place. Exploitation is limited to platforms that actually leverage TEE isolation with affected DDK versions - systems without TEE support or using non-Imagination GPUs are unaffected. The requirement for prior REE kernel control is the primary limiting factor and substantially narrows the realistic exploitation population.

The CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) warrants scrutiny against the actual exploitation prerequisites. The description explicitly requires 'control over the REE kernel,' which implies kernel-level code execution in the normal world OS - a significantly higher privilege bar than PR:L typically represents. A more precise assessment would assign PR:H and potentially S:C (scope changed) since the exploit crosses from the REE into GPU Firmware, a distinct security domain. EPSS of 0.15% at the 5th percentile reflects very low observed exploitation probability and no active weaponization. KEV status is absent, confirming no CISA-confirmed active exploitation. For organizations relying on TEE isolation as a security boundary (mobile device security, automotive HSM architectures, embedded DRM), this flaw materially weakens that boundary once an attacker achieves REE kernel compromise - elevating its risk beyond a naive reading of EPSS. For environments without strict TEE reliance, the post-kernel-access nature limits incremental attacker value. The CVSS S:U designation appears to underweight the cross-domain impact; actual risk to TEE integrity is potentially higher than the base score suggests.

An attacker who has already achieved kernel-level code execution in the normal-world REE (for example, via a Linux kernel exploit on an Android device using Imagination Technologies GPU hardware) locates the non-secure memory region containing the pointer the GPU Firmware reads for data transfers, then overwrites it with an attacker-controlled address. When the GPU Firmware next performs a save or restore of internal state, it dereferences the tampered pointer, corrupting firmware-internal data at the attacker's chosen memory location. This can result in GPU Firmware instability, data exfiltration from GPU private memory, or violation of the TEE isolation boundary. No public proof-of-concept exploit has been identified.