VulnerabilityPublished 1 Dec 2025

CVE-2025-58408: Imagination Technologies Graphics DDK · CWE – CWE-416: Use After Free

Affects Imagination Technologies Graphics DDKSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Dec 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Imagination Technologies Graphics DDK	Affected 1.15 – 23.2 4 affected builds	Fixed in–

AI-suggested

Given the lack of published patches, European organizations should implement specific mitigations beyond generic advice: 1) Restrict local access to systems running affected versions of the Graphics DDK by enforcing strict access controls and monitoring for unauthorized local logins. 2) Employ application whitelisting and endpoint detection to prevent execution of untrusted or malicious software that could trigger the vulnerability. 3) Monitor kernel logs and GPU driver behavior for anomalies indicative of use-after-free exploitation attempts, such as unexpected kernel exceptions or crashes. 4) Isolate critical systems using affected GPUs from general user environments to reduce exposure. 5) Engage with Imagination Technologies for early access to patches or workarounds and plan timely updates once available. 6) Conduct regular security audits focusing on GPU driver versions and configurations to ensure no outdated or vulnerable versions are in use. 7) Implement kernel-level exploit mitigation techniques such as Kernel Address Space Layout Randomization (KASLR) and Control Flow Integrity (CFI) where supported to reduce exploitation success. 8) Educate local users and administrators about the risks of executing untrusted GPU workloads or software. These targeted steps will help reduce the attack surface and mitigate potential exploitation until official patches are released.

Description

Software installed and run as a non-privileged user may conduct improper GPU system calls to trigger reads of stale data that can lead to kernel exceptions and write use-after-free. The Use After Free common weakness enumeration was chosen as the stale data can include handles to resources in which the reference counts can become unbalanced. This can lead to the premature destruction of a resource while in use.

Impact

For European organizations, the impact of CVE-2025-58408 can be significant in environments where Imagination Technologies Graphics DDK is deployed, such as embedded systems, mobile devices, or specialized graphics hardware. Exploitation could lead to kernel exceptions causing system instability or crashes, resulting in denial of service. Additionally, the use-after-free condition may allow attackers to read or manipulate kernel memory, potentially leading to information disclosure or privilege escalation in chained attacks. Confidentiality could be compromised if sensitive data is exposed through stale handles. Integrity may be affected if attackers manipulate kernel resources improperly. Availability is at risk due to possible kernel panics or system reboots. Although exploitation requires local access and no user interaction, insider threats or malware with local presence could leverage this vulnerability. European sectors with critical infrastructure or industrial control systems using affected GPUs might face operational disruptions. The absence of known exploits currently limits immediate risk but does not preclude future exploitation, emphasizing the need for vigilance.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

imaginationtech.com/gpu-driver-vulnerabilities/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 11:51 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats