CVE-2026-121246
説明
An use after free flaw was found in the WebGL component of the Chromium browser.
Upstream bug(s):
詳細
Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
軽減策
--- 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 enforce Control Flow Integrity and Shadow Call Stack to validate indirect call targets and forward-edge control flow during WebGL rendering: upgrade to Chromium 157.0.8103.38 (or the fixed Chromium builds), which resolves the use-after-free defect in the WebGL component, closing crafted HTML page rendering WebGL content. Until patched, this is a concern on users rendering untrusted WebGL content in Chromium-based browsers, so restrict browsing to trusted sites or disable WebGL rendering to prevent processing untrusted WebGL pages. As a compensating measure, enable ASLR to randomize process memory layout and require an information leak to target code pointers, enforce NX/XD bits to prevent code execution directly from heap-allocated memory, compile with Full RELRO and PIE to enforce position-independent executable code and read-only relocation tables, and deploy an EDR agent to monitor process behaviors and detect anomalous child process spawning following potential sandbox escapes. 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)
脆弱性の原因 (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.
よくある質問
Not sure what something means? Check out our Security Glossary.
エラータ通知の受信を希望しますか? こちらで登録してください。
