CVE-2026-21734: GPU DDK - libusc OOB write at TreeRemove during WebGPU shader compilation
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.16% (FIRST EPSS).
- Someone with local access to the system 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
A web page that contains unusual GPU shader code is loaded into the GPU compiler process and can trigger a write out-of-bounds write crash in the GPU shader compiler library. On certain platforms, when the compiler process has system privileges this could enable further exploits on the device. An edge case using a very small value in GPU shader code can cause a segmentation fault in the GPU shader compiler due to am out-of-bounds write.
- Published
- Jun 26, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-823
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- imaginationtech ddkup to 25.2 inclusive
- imaginationtech ddk25.3
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
- 26.1 RTMnot affected
- 1.18 RTM, 23.2 RTMaffected
- 24.1 RTM and later · up to and including 24.2 RTMaffected
- 25.1 RTM and later · up to and including 25.3 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-2026-22167May 1, 2026 · GPU DDK - Cache resident PM buffers writable by other GPU requestors, leading to arbitrary write to physical memory31Monitor
- ← EarlierCVE-2026-34193Jun 1, 2026 · GPU DDK - Arbitrary write via UFO updates due insufficient pointer validation in rgxfw_to_ptr()17Monitor
- Later →CVE-2026-45195Jun 26, 2026 · GPU DDK - rgxfw_set_mips_fault_address(&psInit->sFaultPhysAddr) is untrusted31Monitor
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-2026-2173298 days apartGPU DDK - libusc OOB write at ConvertSwitchToArrayLookupBP during WebGPU shader compilation38Monitor
- CVE-2025-0467435 days apartGPU DDK - rgxfw_hwperf_get_packet_buffer OOB write32Monitor
- CVE-2026-4974428 days apartGPU DDK - Unchecked ui32TracePointer in rgxfw_log_ex()31Monitor
- CVE-2026-4974528 days apartGPU DDK - Unvalidated sHWPerfCtlDMABuf GPU-VA, DMA-write into FW privdata via MMU ctx 031Monitor
- CVE-2026-3419325 days apartGPU DDK - Arbitrary write via UFO updates due insufficient pointer validation in rgxfw_to_ptr()17Monitor
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
- Someone with local access to the system 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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-823 · Use of Out-of-range Pointer OffsetCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.