CVE-2025-46708: GPU DDK - Guest VM can delay the FW and GPU from processing workloads from other VMs
Noroxi assessment
Priority: Monitor (action score 17/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.20% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- 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
Software installed and running inside a Guest VM may conduct improper GPU system calls to prevent other Guests from running work on the GPU.
- Published
- Jun 27, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-280
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- 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
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 helpAffected 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 |
| android | cpe:2.3:o:google:android | |
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- imaginationtech ddk23.2 and later · before 24.2
- imaginationtech ddk1.15
- imaginationtech ddk1.17
- imaginationtech ddk1.18
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
- 24.2 RTM1not affected
- 1.15 RTM, 1.17 RTM, 1.18 RTMaffected
- 23.2 RTM and later · up to and including 24.1 RTMaffected
Same product
imaginationtech: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-16280GPU DDK - Integer overflow in _PMRLogicalOffsetToPhysicalOffset39Monitor
- CVE-2025-13952GPU DDK - libusc UAF via WebGPU shaders at MergeConsecutiveBarriersBP39Monitor
- CVE-2026-21732GPU DDK - libusc OOB write at ConvertSwitchToArrayLookupBP during WebGPU shader compilation38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-46710Jun 16, 2025 · Possible kernel exceptions caused by reading and writing kernel heap data after free.22Monitor
- ← EarlierCVE-2025-46707Jun 27, 2025 · GPU DDK - Guest VM can override its own FW VZ connection state after the FW has close it20Monitor
- Later →CVE-2025-46709Aug 8, 2025 · GPU DDK - Security fix for PP-171570 can lead to an uninitialised pointer dereference and memory leak30Monitor
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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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-2517925 days apartGPU DDK - Freelist GPU VA can be remapped to another reservation/PMR to trigger GPU arbitrary write to physical memory31Monitor
- CVE-2026-45195364 days apartGPU DDK - rgxfw_set_mips_fault_address(&psInit->sFaultPhysAddr) is untrusted31Monitor
- CVE-2026-45196378 days apartGPU DDK - Arbitrary GPU register write in rgxfw_hwperf_hw due to unsanitized pointers from host kernel31Monitor
- CVE-2025-58410143 days apartGPU DDK - Multiple calls into PhysmemGEMPrimeExport can inherit write access permission for an existing read-only dma_buf import PMR30Monitor
- CVE-2026-21733294 days apartGPU DDK - Incorrect flags validation in RGXDerivePTEProt8 can allow GPU to overwrite read-only shared memory (e.g. libc.so)29Monitor
- CVE-2026-21736255 days apartGPU DDK - Insufficient permission check in PhysmemWrapExtMem() when write attribute support enabled17Monitor
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
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-280 · Improper Handling of Insufficient Permissions or PrivilegesCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.