GPU compiler crash via stale pointer write
Published Jan 24, 2026 · Updated Jan 24, 2026
Write use-after-free in libusc in Imagination Technologies Graphics DDK 25.1 RTM through 25.2 RTM allows remote attackers to crash GPU compilation. MergeConsecutiveBarriersBP retains an out-of-date pointer to a freed object and writes through it when compiling unusual WebGPU shader code. A crafted webpage must reach the GPU compiler; the immediate consequence is a compiler-process crash, while system-privileged compiler execution enables further device exploitation.
Summary
What happened
Write use-after-free in libusc in Imagination Technologies Graphics DDK 25.1 RTM through 25.2 RTM allows remote attackers to crash GPU compilation. MergeConsecutiveBarriersBP retains an out-of-date pointer to a freed object and writes through it when compiling unusual WebGPU shader code. A crafted webpage must reach the GPU compiler; the immediate consequence is a compiler-process crash, while system-privileged compiler execution enables further device exploitation.
The record
- CVE
- CVE-2025-13952
- Published
- Jan 24, 2026
- Updated
- Jan 24, 2026
- Vendor
- Imagination Technologies
- Product
- Graphics DDK
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2026CVE publishedPublication date reported by the CVE source.
- Jan 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=25.1 RTM <=25.2 RTM
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo