CVE-2026-121044
Description
An use after free flaw was found in the Layout 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-06) ---
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 to validate indirect call targets and prevent hijacked execution flow from freed Layout objects: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which remediates the use-after-free memory corruption condition within the Layout component during document rendering, closing crafted HTML page. Until patched, this is a concern on Chromium users navigating to untrusted websites or opening untrusted HTML files across all platforms, so Restrict user navigation to untrusted websites and opening of untrusted HTML documents, ensuring browser renderer sandboxing is strictly enforced. As a compensating measure, Enable ASLR to randomize renderer process memory layout and obstruct reliable ROP chain construction, Enforce non-executable heap memory permissions to block direct shellcode execution from reclaimed layout memory regions, and Enable full RELRO and PIE to ensure position-independent execution and protect global offset tables against overwrites. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free defect in Layout — 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.
