Heap Buffer Overflow in GPU in Google Chrome

chromium Updated 02 Oct 2025

Summary

25/11/2022
N/A
Yes i
Critical
9.6

CVE-2022-4135: Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. Affects chromium versions < 107.0.5304.121-1~deb11u1. Fixed in 107.0.5304.121-1~deb11u1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Google Chrome is a popular web browser developed by Google. It provides a fast and secure browsing experience to users. The GPU component in Google Chrome is responsible for rendering graphics and accelerating web page performance. However, a vulnerability has been discovered in the GPU component that could allow a remote attacker to perform a sandbox escape. This vulnerability has a high severity rating and affects Google Chrome versions prior to 107.0.5304.121.

Vulnerability Detail

The vulnerability, identified as CVE-2022-4135, is a heap buffer overflow in the GPU component of Google Chrome. It can be exploited by a remote attacker who has already compromised the renderer process. By tricking a user into visiting a specially crafted HTML page, the attacker can trigger the buffer overflow and potentially escape the sandbox. This could lead to further exploitation of the system and compromise the user's data and privacy. The severity of this vulnerability is rated as high.

How To Fix

Minimum fixed version

107.0.5304.121-1~deb11u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade chromium

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update Google Chrome to the latest version to mitigate the risk of exploitation.

Conclusion

In conclusion, a heap buffer overflow vulnerability has been identified in the GPU component of Google Chrome. This vulnerability allows a remote attacker to potentially escape the sandbox and compromise the user's system. It is crucial to update Google Chrome to version 107.0.5304.121 or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

The vulnerability allows a remote attacker to potentially escape the sandbox and compromise the user's system. This could lead to unauthorized access to sensitive data, installation of malware, and other malicious activities.

You can use the Vulert Playground at Vulert Scanner to check if your version of Google Chrome is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will provide real-time alerts for open-source vulnerabilities.

At the time of this report, there are no known public exploits for this vulnerability. However, it is crucial to update Google Chrome to the latest version to protect against potential future exploits.

No, the patch for this vulnerability is only available through the official update channel of Google Chrome. It is recommended to update the browser to the latest version using the built-in update mechanism.

This vulnerability was discovered by the Chromium security team.

Related vulnerabilities

Recent vulnerabilities recorded for chromium.

How To Fix

Minimum fixed version

107.0.5304.121-1~deb11u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade chromium

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback