CVE-2025-46710: Imagination Technologies Graphics DDK · CWE – CWE-416: Use After Free (4.17)
Affects Imagination Technologies Graphics DDKSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 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
1. Immediate inventory and identification of all devices and systems running Imagination Technologies Graphics DDK version 1.15 RTM within the organization. 2. Engage with Imagination Technologies and hardware vendors for updates or patches; prioritize deployment once available. 3. Implement strict access controls and limit exposure of affected devices to untrusted networks to reduce attack surface. 4. Employ kernel-level exploit mitigation techniques such as Kernel Address Space Layout Randomization (KASLR), Supervisor Mode Execution Prevention (SMEP), and Kernel Page-Table Isolation (KPTI) where supported. 5. Monitor system logs and kernel event traces for unusual behavior indicative of heap corruption or kernel exceptions. 6. For embedded and IoT devices, consider firmware updates or device replacement if patches are unavailable. 7. Conduct penetration testing and vulnerability scanning focused on kernel drivers to detect exploitation attempts. 8. Establish incident response procedures tailored to kernel-level compromises, including forensic readiness and recovery plans. 9. Educate development and security teams about the risks of use-after-free vulnerabilities and secure coding practices to prevent similar issues in future driver releases.
Description
Possible kernel exceptions caused by reading and writing kernel heap data after free.