Uninitialized Use in GPU in Google Chrome

Successful exploitation can disclose potentially sensitive information from Chrome process memory. Because the attacker must already control or compromise the renderer process, this vulnerability appears to be most useful as a post-compromise primitive for leaking memory contents, which could aid sandbox escape research, bypass of exploit mitigations, theft of sensitive in-process data, or chaining with other vulnerabilities.

If immediate patching is not possible, reduce exposure by limiting use of untrusted web content, restricting browser access to potentially malicious sites, and using Chrome sandboxing and platform hardening features as designed. Because exploitation requires prior compromise of the renderer process, reducing the likelihood of renderer compromise through prompt patching of other browser bugs and minimizing exposure to malicious HTML content may lower risk. However, no complete mitigation is provided in the source content, and vendor patching is the primary fix.

Upgrade Google Chrome to version 149.0.7827.197 or later. The provided content states that the Stable channel was updated to 149.0.7827.196/197 for Windows and Mac and 149.0.7827.196 for Linux; the advisory specifically recommends upgrading to 149.0.7827.197 or later. Apply the latest vendor-provided Chrome stable release available for the affected platform.