Skip to main content
VulnerabilityPublished Updated

CVE-2025-6573: Imagination Technologies Graphics DDK · 4.15

Affects Imagination Technologies Graphics DDKSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Imagination Technologies Graphics DDKAffected
  • 1.15 – 23.2
4 affected builds
Fixed in–

AI-suggested

  1. Immediate Inventory and Assessment: Identify all devices and systems using the affected versions of Imagination Technologies Graphics DDK within the organization’s infrastructure.
  2. Vendor Engagement: Engage with Imagination Technologies for official patches or updates addressing CVE-2025-6573. Monitor vendor advisories closely for patch releases.
  3. Network Segmentation: Isolate vulnerable devices from critical network segments to limit potential exploitation paths, especially those connected to sensitive data or control systems.
  4. 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.
  5. 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.
  6. Application Whitelisting: Implement whitelisting to prevent unauthorized or unverified kernel modules or drivers from loading.
  7. Incident Response Preparedness: Update incident response plans to include scenarios involving TEE compromise and ensure forensic capabilities to detect and analyze such breaches.
  8. 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).

References

Community reviews

Loading reviews…