Graphics DDK CVE-2026-45199

Exploitation requires kernel-level (ring-0) code execution inside a Guest VM - the CVSS PR:L reflects that the attacker must already possess guest kernel privileges or the ability to load and run kernel software within the guest. The guest must have access to an Imagination Technologies GPU through the DDK command interface (GPU passthrough, virtual GPU, or bare-metal deployment with the DDK installed). No special non-default configuration of the DDK itself is described as a prerequisite beyond having the driver installed and operational. Limiting factors: the attacker must already control guest kernel code, which represents a significant prerequisite; the attack is local (AV:L) and cannot be initiated remotely without a separate initial-access step; SSVC confirms it is not automatable, ruling out unaided mass exploitation.

The CVSS 3.1 score of 7.8 (High) reflects a local attack vector with low privilege requirements and high impact across all three security properties - consistent with a guest-kernel privilege escalation. EPSS at 0.15% (5th percentile) indicates very low observed exploitation probability in the wild, which aligns with the SSVC determination of 'exploitation: none' and 'automatable: no' - this is not a spray-and-pray class of vulnerability. Despite the low EPSS, SSVC flags 'technical impact: total,' meaning successful exploitation yields full control of the affected guest environment. The gap between low EPSS and high technical impact suggests a vulnerability that is impactful but difficult to weaponize at scale, likely requiring specific knowledge of the GPU command interface. No KEV listing and no public POC further support treating this as a priority patch rather than an emergency response. The S:U scope in the CVSS vector deserves scrutiny: out-of-bounds GPU memory writes could, in principle, affect host GPU memory regions, but available data does not confirm a hypervisor-escape scenario, so S:U is provisionally accepted.

An attacker who has obtained kernel-mode code execution inside a guest VM (for example, via a prior container escape or a guest OS vulnerability) crafts malformed GPU command buffers and submits them to the GPU Firmware through the DDK interface. The firmware processes the commands without validating target memory addresses, writing attacker-controlled data outside the guest's allocated GPU memory region, which the attacker leverages to overwrite kernel or hypervisor structures and escalate privileges. No public proof-of-concept code has been identified at time of analysis.