This vulnerability involves a use-after-free condition in the GPU process of Google Chrome before version 148.0.7778.168. An attacker with control over the renderer process can exploit this flaw to write memory out of bounds, potentially leading to arbitrary code execution or browser instability. The issue arises from improper memory management when handling GPU tasks triggered by crafted HTML content. The vulnerability is publicly disclosed with high severity but lacks a confirmed CVSS score or explicit patch information in the provided data.

The vulnerability could allow a remote attacker who has compromised the renderer process to execute out-of-bounds memory writes, which may lead to arbitrary code execution or denial of service within the browser context. Since exploitation requires prior compromise of the renderer process, the attack surface is somewhat limited. No known exploits in the wild have been reported at the time of disclosure.

Patch status is not yet confirmed — check the vendor advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html for current remediation guidance. Users should update to Chrome version 148.0.7778.168 or later once available. Until then, no specific mitigation steps are provided in the advisory or data.