Live › vulnerability › CVE-2026-18629
A web page with specially crafted GPU shader code can trigger an integer overflow in the GPU compiler process, causing a memory allocation failure and a NULL pointer dereference. The compiler process crashes, and on certain platforms running with system privileges this could lead to further exploitation of the device.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 02:28 UTC. All times on this page are UTC.
The sources describe a web page loading shader code into the GPU compiler process, so exposure depends on browsing untrusted pages on affected platforms. The sources do not name the affected products or versions. unknown
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-18629")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.