CVE-2025-6573: Imagination Technologies Graphics DDK · 4.15
Affects Imagination Technologies Graphics DDKSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 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 Inventory and Assessment: Identify all devices and systems using the affected versions of Imagination Technologies Graphics DDK within the organization’s infrastructure.
- Vendor Engagement: Engage with Imagination Technologies for official patches or updates addressing CVE-2025-6573. Monitor vendor advisories closely for patch releases.
- Network Segmentation: Isolate vulnerable devices from critical network segments to limit potential exploitation paths, especially those connected to sensitive data or control systems.
- Access Controls: Restrict access to devices running the vulnerable DDK to trusted administrators only, and enforce strict privilege management to reduce the risk of exploitation from within the network.
- Runtime Monitoring: Deploy advanced endpoint detection and response (EDR) tools capable of monitoring unusual kernel-level activities or attempts to access TEE resources from REE processes.
- Application Whitelisting: Implement whitelisting to prevent unauthorized or unverified kernel modules or drivers from loading.
- Incident Response Preparedness: Update incident response plans to include scenarios involving TEE compromise and ensure forensic capabilities to detect and analyze such breaches.
- Alternative Solutions: Where feasible, consider migrating to alternative graphics drivers or hardware platforms not affected by this vulnerability until patches are available.
Description
Kernel software installed and running inside an untrusted/rich execution environment (REE) could leak information from the trusted execution environment (TEE).