CVE-2026-121247
説明
A buffer overflow flaw was found in the Dawn 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 strict heap memory bounds checking in the Dawn WebGPU component to prevent out-of-bounds writes: upgrade to Chromium 157.0.8103.38 (or the fixed Chromium builds), which resolves the heap buffer overflow in the Dawn component to prevent arbitrary code execution outside the sandbox, closing crafted HTML page. Until patched, this is a concern on all systems running affected Chromium browser builds where users visit untrusted web pages, so restrict browser access to untrusted web pages and disallow navigating to arbitrary external HTML content. As a compensating measure, ensure Address Space Layout Randomization is active to hinder reliable heap buffer overflow exploitation, deploy endpoint detection and response monitoring to detect anomalous process behavior escaping the browser sandbox, and enforce non-executable memory page protections using the NX/XD bit to block payload execution from the heap. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap-based buffer overflow — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
脆弱性の原因 (CWE) の理解
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.
Integrity,Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism; Modify Memory
Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. Besides important user data, heap-based overflows can be used to overwrite function pointers that may be living in memory, pointing it to the attacker's code. Even in applications that do not explicitly use function pointers, the run-time will usually leave many in memory. For example, object methods in C++ are generally implemented using function pointers. Even in C programs, there is often a global offset table used by the underlying runtime.
Integrity,Confidentiality,Availability,Access Control,Other
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism; Other
When the consequence is arbitrary code execution, this can often be used to subvert any other security service.
よくある質問
Not sure what something means? Check out our Security Glossary.
エラータ通知の受信を希望しますか? こちらで登録してください。
