CVE-2026-121119
개요
An use after free flaw was found in the Controls 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 validation on indirect call targets to abort execution on hijacked function pointers or virtual method tables within the Controls component: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which resolves the use-after-free memory management lifecycle flaw within the Controls component, closing crafted HTML page. Until patched, this is a concern on Users running Chromium or Google Chrome on any platform viewing untrusted web content, so Restrict browser access to trusted internal origins and avoid opening untrusted or attacker-controlled HTML documents. As a compensating measure, Enforce Address Space Layout Randomization to randomize process memory layouts and impede gadget address prediction, Enforce Non-Executable memory permissions on heap data pages to block direct execution of injected shellcode, Deploy binaries hardened with full RELRO and PIE to protect Global Offset Tables from overwrite during memory corruption, and Deploy EDR agents to detect anomalous process behavior and memory injection attempts inside renderer sandbox environments. 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.
