CVE Tools
Track your stack

CVE-2026-18629

GPU DDK - libusc.so NPD due to integer overflow at ConvertSwitchToArrayLookup during WebGPU shader compilation

No known exploitation. No EPSS score yet. Fixed versions are out.

CVSS —Not scoredEPSS percentile—No score yetCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1 product2 fixed builds listed below

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Imagination Technologies Graphics DDKAffected: 23.2 RTM2Upgrade to: not statedAffected: 24.2 RTM2Upgrade to: not statedAffected: ≥ 25.1 RTM2, ≤ 25.3 RTMUpgrade to: after 25.3 RTMAffected: 26.1 RTM1Upgrade to: not statedFixed builds1.18 RTM2, 26.1 RTM2Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

A web page that contains unusual GPU shader code is loaded into the GPU compiler process and can lead memory allocation failure. If the allocation failure is not properly handled, the compiler may dereference a NULL pointer at a controlled offset, resulting in a crash of the compiler process. On certain platforms, when the compiler process has system privileges this could lead to crashes or enable further exploits on the device. The weakness results from performing arithmetic operations on values derived from the shader program without properly preventing integer overflow. The overflow can cause incorrect memory size calculations, leading to memory allocation failures and subsequent invalid program behaviour. Integer overflow can produce unexpected values that affect memory allocation and other security-relevant operations.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

No EPSS score yet. New CVEs are usually scored within a few days.

Lifecycle

4 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Graphics DDK, not every advisory.