Imagination Graphics DDK EUVD-2026-43039

Exploitation requires the attacker to already be running kernel software inside a Host VM on a system using the affected Imagination Graphics DDK, and to have a path to submit commands to the GPU firmware command interface - i.e., local access to the GPU driver/firmware channel, not remote or unauthenticated access. The malformed-command handling that triggers the improper GPU register access is the concrete flaw exploited. Limiting factors: the CVSS vector is AV:L (no network exploitation) and the description implies a high practical bar since the attacker needs kernel-level code execution in the Host VM; exploitation is further constrained to devices/SoCs shipping the affected DDK branches (1.18 RTM2, 23.2 RTM2, 24.2 RTM2, 25.1 RTM2-25.3 RTM, 26.1 RTM1). No user interaction is needed once that foothold exists.

The signals are consistent and point to a real but locally-scoped privilege-escalation risk rather than a remotely exploitable emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms local attack vector, low complexity, and already-present low privileges, with high impact to confidentiality, integrity, and availability - appropriate for a kernel-to-firmware privilege boundary bypass. EPSS is very low (0.14%, 4th percentile) and the CVE is not on CISA KEV, so there is no evidence of active or widespread exploitation; no POC is referenced. The description implies the attacker must already be running kernel-level software inside a Host VM, which is a meaningfully higher bar than PR:L alone suggests - a note of tension worth flagging: PR:L in the vector versus a description implying kernel/host-VM-privileged code means the practical prerequisite may be closer to PR:H, so verify the intended attacker model with the vendor. Overall this is a patch-in-normal-cycle issue for affected platforms, not a drop-everything item, but the C/I/A:H impact makes it a priority where PowerVR GPUs are deployed in multi-tenant or VM-based environments.

An attacker who can execute kernel-mode code inside a Host VM on an affected PowerVR platform crafts and submits malformed commands to the GPU firmware, causing an improper GPU register access that escalates their privileges beyond the intended boundary. Because the attack vector is local with low complexity and no user interaction, exploitation is deterministic once the attacker has the required kernel foothold; no public exploit code is identified at time of analysis.