NVD / CVE Program· CNA imaginationtech

CVE-2025-46709: GPU DDK - Security fix for PP-171570 can lead to an uninitialised pointer dereference and memory leak

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Possible memory leak or kernel exceptions caused by reading kernel heap data after free or NULL pointer dereference kernel exception.

HighCVSS 7.5 · v3.1—No exploit No fix recorded

Published: Aug 8, 2025
Updated: Jun 17, 2026
EPSS: 0.3% · 26th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
imaginationtech	ddk	cpe:2.3:a:imaginationtech:ddk

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

imaginationtech ddk1.17 and later · up to 25.1 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (imaginationtech). Independent of NVD's CPE analysis and usually ahead of it.

Imagination Technologies Graphics DDK
- 25.1 RTM2not affected
- 1.15 RTM, 1.17 RTM, 1.18 RTMaffected
- 23.2 RTM and later · up to and including 25.1 RTM1affected

Same product

imaginationtech: all records

Other highest-scoring records for the same primary product.

CVE-2026-16280GPU DDK - Integer overflow in _PMRLogicalOffsetToPhysicalOffset
39Monitor
CVE-2025-13952GPU DDK - libusc UAF via WebGPU shaders at MergeConsecutiveBarriersBP
39Monitor
CVE-2026-21732GPU DDK - libusc OOB write at ConvertSwitchToArrayLookupBP during WebGPU shader compilation
38Monitor

Published before and after this one in the same product

← EarlierCVE-2025-46707Jun 27, 2025 · GPU DDK - Guest VM can override its own FW VZ connection state after the FW has close it
20Monitor
← EarlierCVE-2025-46708Jun 27, 2025 · GPU DDK - Guest VM can delay the FW and GPU from processing workloads from other VMs
17Monitor
Later →CVE-2025-46711Sep 22, 2025 · GPU DDK - NULL Pointer dereference occurs in LockHandle on bridge entry when connection misused
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-13952168 days apartGPU DDK - libusc UAF via WebGPU shaders at MergeConsecutiveBarriersBP
39Monitor
CVE-2025-58411158 days apartGPU DDK - Reservation::psMappedPMR can change while used by a freelist -> UAF
35Monitor
CVE-2026-22165266 days apartGPU DDK - UAF read of GLES3Context::psDrawParams and GLES3Context::psMode and UAF read/write of RMJob::apsCCBs
32Monitor
CVE-2026-22166266 days apartGPU DDK - Write UAF in KEGLGetPoolBuffers, WebGL reachable
32Monitor
CVE-2025-10865158 days apartGPU DDK - DevmemIntGetReservationData does not ref the PMR it returns
31Monitor
CVE-2026-34196336 days apartGPU DDK - UAF read and/or write of arbitrary physical memory due to integer truncation in PMRDevPhysAddrOSMem
31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.imaginationtech.com/gpu-driver-vulnerabilities/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records