CVE-2026-126876
Description
An integer overflow flaw was found in the Skia component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=576664769 https://code.google.com/p/chromium/issues/detail?id=126876
Statement
Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
Mitigation
To reduce exposure to this vulnerability, apply operational controls and ensure sandboxing is maintained:
1. Avoid visiting untrusted websites or following untrusted links that could render malicious HTML and graphics content.
2. Ensure that Chromium's built-in multi-process sandbox remains enabled. Do not run the browser with sandbox-disabling options such as the `--no-sandbox` command-line flag.
3. If the browser is not required on the system, remove the package:
# dnf remove chromium-browser
Caveats: Restricting web browsing or removing the browser package will affect user workflows that depend on web access. Operational controls such as avoiding untrusted content do not eliminate risk from compromised trusted sites.
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided. If the calculated result involves time values, then the product might crash when it encounters a time that is less than the previously-calculated time.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Access Control
Technical Impact: Bypass Protection Mechanism; DoS: Crash, Exit, or Restart
If integer values are used in time-based, security-critical decisions, such as calculating expiration times or determining whether an event occurs within a specific time or date range, to cause an incorrect security decision. The consequences could even include "self-DoS" if the overflow produces a time value that is not accounted for in protection mechanism logic [REF-1570].
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
