VulnerabilityPublished 13 Jan 2026

CVE-2025-58409: Imagination Technologies Graphics DDK · 4.18

Affects Imagination Technologies Graphics DDKSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

3.5Low

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

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:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
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 TechnologiesGraphics DDK	Affected =1.15 RTM =1.17 RTM =1.18 RTM ≥ 23.2 RTM, ≤ 25.2 RTM	Fixed in–

AI-suggested

Restrict physical and local access to systems running Imagination Technologies GPUs to prevent unauthorized exploitation.
Implement strict access controls and monitoring on GPU driver interfaces to detect anomalous GPU system calls or memory operations.
Maintain an inventory of hardware and software to identify systems using affected Graphics DDK versions (1.15 RTM, 1.17 RTM, 1.18 RTM, 23.2 RTM).
Engage with Imagination Technologies for timely security advisories and patches; apply updates promptly once available.
Employ hardware-based security features such as IOMMU (Input-Output Memory Management Unit) to restrict GPU access to physical memory regions.
Use endpoint detection and response (EDR) solutions capable of monitoring GPU driver behavior and memory integrity.
For critical systems, consider isolating or segmenting devices with affected GPUs to limit potential attack surface.
Conduct regular security audits and penetration testing focusing on GPU driver interfaces and memory management.

Description

CVE-2025-58409 is a vulnerability in Imagination Technologies Graphics DDK that allows non-privileged software to misuse GPU system calls to write to arbitrary physical memory. This improper restriction of operations within GPU memory buffers (CWE-119) can corrupt kernel and driver memory pages, potentially altering system behavior. The vulnerability affects multiple versions of the Graphics DDK and does not require user interaction or privileges to exploit. Although the CVSS score is low (3.5), the ability to write to arbitrary physical memory poses risks to system integrity. No known exploits are currently in the wild, and no patches have been released yet. European organizations using affected GPU drivers in embedded or specialized systems may be at risk. Mitigation involves restricting access to GPU interfaces, monitoring GPU driver updates, and applying vendor patches once available. Countries with significant embedded systems manufacturing and technology sectors, such as Germany, France, and the UK, are more likely to be impacted.

Impact

For European organizations, the impact of CVE-2025-58409 depends largely on the deployment of affected Imagination Technologies Graphics DDK versions within their infrastructure. Organizations relying on embedded systems, industrial control systems, or specialized hardware that incorporate these GPUs could face risks of kernel memory corruption leading to system instability, unauthorized behavior modification, or potential privilege escalation if combined with other vulnerabilities. Although the CVSS score is low, the ability to corrupt arbitrary physical memory could enable attackers to bypass security controls or disrupt critical operations, especially in sectors like manufacturing, automotive, telecommunications, and defense where embedded GPUs are prevalent. The lack of required privileges or user interaction lowers the barrier for exploitation in physically accessible environments, such as on-premises devices or edge computing nodes. However, the absence of known exploits and patches reduces immediate risk but underscores the need for proactive mitigation. The threat is less relevant for typical enterprise desktop or server environments unless they specifically use the affected GPU drivers.

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
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)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (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 21 Jan 2026, 02:34 UTC

WeaknessesCWE-119

Technical details

References

Community reviews

Related threats