LANGUAGES Signal 335 2 feeds carried it
WebGPU shader reportedly freezes MacOS UI requiring forced restart across browsers
Illustration only Photo by Lachlan Donald on Unsplash
An untrusted website can trigger a MacOS GPU hang via a WebGPU compute shader, rendering the desktop unresponsive until rebooted.
This vulnerability exposes a systemic weakness in MacOS GPU preemption for untrusted shader code. Engineers building or deploying WebGPU applications must account for potential denial-of-service risks on affected systems until a fix is released.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
A single WebGPU shader with an infinite loop can freeze MacOS graphics, requiring a forced restart to recover.
The issue affects Chrome, Firefox, and Safari on MacOS but does not reproduce on other operating systems.
Apple previously addressed a similar WebGL vulnerability but WebGPU input validation appears insufficient for this case.
THE READ
What the cluster adds up to.
A WebGPU compute shader with a trivial infinite loop can lock up the GPU on MacOS, causing the WindowServer process to become unresponsive. The shader copies data in an endless loop while a dependent vertex shader waits for access to the same buffer. This contention propagates to the system UI, freezing the desktop until the watchdog triggers a kernel panic or the user forces a restart.
The vulnerability is specific to MacOS and reproduces across all major browsers supporting WebGPU. Other operating systems handle the same shader by freezing only the affected tab, allowing recovery without a system restart. This suggests MacOS lacks effective preemption for GPU tasks originating from untrusted web content, a gap not present in other platforms.
Apple’s M-series architecture may contribute to the issue, as GPU preemption logic resides in the ASC coprocessor firmware rather than the OS kernel. This separation complicates real-time intervention when a shader becomes unresponsive. Previous mitigations for WebGL vulnerabilities relied on input validation, but detecting infinite loops is fundamentally limited by the halting problem.
The disclosure timeline indicates Apple initially acknowledged the issue but later shifted its response. No fix has been released, leaving MacOS users exposed to potential denial-of-service attacks via malicious websites. Engineers should monitor for updates and consider browser-level mitigations or WebGPU restrictions for critical systems until a patch is available.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER