Imagination Graphics DDK EUVD-2026-43037

Requires the ability to execute code as an unprivileged local user on a device using the Imagination Graphics DDK, and specifically the ability to submit GPU system calls and shader code (access to the GPU/compute interface) - consistent with CVSS PR:L and AV:L. The concrete trigger is forcing a failure path in the GPU MMU mapping logic so that internal driver state is incompletely cleaned up, so the attacker must reach that mapping code path and issue the improper syscall sequence. Limiting factors: exploitation is local only with no remote/network vector, needs an existing unprivileged foothold that can reach the GPU, and is constrained to the affected DDK builds (1.18, 23.2, 24.2, 25.1-25.3, 26.1 RTM1) - devices that do not permit untrusted local code to touch the GPU are not practically exposed.

The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a local, low-complexity attack requiring only low (unprivileged-user) privileges and no user interaction, with high impact across all three properties - consistent with the description of an unprivileged local user achieving arbitrary physical memory access. Counterbalancing signals lower immediate urgency: EPSS is only 0.15% (5th percentile), there is no CISA KEV listing, and no public proof-of-concept has been identified, so there is no evidence of active or widespread exploitation. The tag set ('Authentication Bypass, Denial Of Service') is broader than the CVSS impact profile and appears to be aggregated vendor categorization rather than a distinct network-facing auth-bypass primitive - the described primitive is local memory corruption, so treat 'Authentication Bypass' with caution and do not assume a remote vector. Net: a genuine local privilege-escalation / kernel-memory-disclosure risk that matters most for devices running untrusted GPU/compute workloads, but not an internet-facing emergency; prioritize on multi-tenant or untrusted-code devices.

An unprivileged local user or untrusted application on a device with a vulnerable PowerVR driver submits a crafted sequence of GPU system calls that forces an error in the MMU mapping path, leaving a stale mapping behind. The attacker then uses shader code against the dangling state to read and write physical memory outside its sandbox, escalating privileges or extracting other processes' secrets. No public PoC is currently identified, and the local, low-complexity vector (AC:L) means a working exploit would be reliable once developed.