CVE-2025-8109: Imagination Technologies Graphics DDK · 4.15
Affects Imagination Technologies Graphics DDKSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Imagination Technologies Graphics DDK | Affected
| Fixed in– |
AI-suggested
Immediate mitigation should focus on restricting access to systems running the vulnerable Graphics DDK version 1.13 RTM. Organizations should implement strict access controls to limit non-privileged user capabilities, especially restricting ptrace system call usage through Linux security modules like SELinux or AppArmor. Employing seccomp filters to block ptrace calls from untrusted processes can reduce exploitation risk. Monitoring and logging ptrace usage can help detect suspicious activity. Until an official patch is released, consider isolating affected systems or disabling GPU features that rely on the vulnerable DDK where feasible. Vendors and integrators should prioritize obtaining and deploying patches once available. Additionally, organizations should conduct thorough audits of GPU driver versions across their environments and update asset inventories accordingly. Incorporating GPU driver integrity checks and leveraging hardware-based security features can further harden systems. Finally, raising user awareness about the risks of running untrusted code on GPU-enabled systems is advised.
Description
Software installed and run as a non-privileged user may conduct ptrace system calls to issue writes to GPU origin read only memory.