CVE-2025-25180: Imagination Technologies Graphics DDK · 4.17
Affects Imagination Technologies Graphics DDKSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Jul 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Imagination Technologies Graphics DDK | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-25180, European organizations should take the following specific actions: 1) Inventory and identify all systems and devices using the affected versions of Imagination Technologies Graphics DDK (1.15 RTM, 1.17 RTM, 1.18 RTM, 23.2 RTM). 2) Engage with Imagination Technologies or device vendors to obtain patches or updated driver versions that address the out-of-range pointer offset validation issue. 3) Until patches are available, implement strict access controls to limit non-privileged user access to systems with vulnerable GPU drivers, including applying the principle of least privilege and restricting user permissions. 4) Employ runtime monitoring and anomaly detection focused on GPU system calls and kernel memory access patterns to detect potential exploitation attempts. 5) Harden kernel security by enabling kernel memory protection features such as Kernel Address Space Layout Randomization (KASLR), Kernel Page Table Isolation (KPTI), and other hardware-assisted memory protections where supported. 6) For embedded and IoT devices, ensure secure firmware update mechanisms are in place to facilitate timely deployment of fixes. 7) Conduct thorough security testing and code reviews for custom applications interfacing with GPU drivers to prevent misuse of GPU system calls. 8) Maintain up-to-date incident response plans that include scenarios involving GPU driver exploitation and kernel memory corruption.
Description
Software installed and run as a non-privileged user may conduct improper GPU system calls to subvert GPU HW to write to arbitrary physical memory pages. Under certain circumstances this exploit could be used to corrupt data pages not allocated by the GPU driver but memory pages in use by the kernel and drivers running on the platform altering their behaviour.