CVE-2026-121089
Description
An use after free flaw was found in the WebGPU component of the Chromium browser.
Upstream bug(s):
Statement
Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
Mitigation
--- CME Mitigation Guidance (2026-11-04) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to validate indirect call targets using Control Flow Integrity to prevent control-flow hijacking when an attacker reuses freed WebGPU object pointers: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which resolves the use-after-free memory corruption condition within the WebGPU component, closing crafted HTML page with malicious WebGPU API calls. Until patched, this is a concern on Chromium installations with WebGPU support enabled, so restrict user browsing to trusted sites and disable or restrict WebGPU support across browser deployments. As a compensating measure, enforce ASLR to randomize Chromium userspace process memory and hinder reliable payload redirection during use-after-free exploitation, enforce NX/XD non-executable memory to block execution of arbitrary code placed in corrupted heap memory buffers, build Chromium binaries with Full RELRO and PIE to protect global offset tables and enable full address randomization, and deploy an EDR agent to detect anomalous process behavior and payload execution attempting to escape the browser sandbox. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-113 Control Flow Integrity (CFI / Shadow Call Stack) (high)
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
