Download 88.0.4324.190 from the Chrome Stable for Linux
Download Google Chrome 88.0.4324.190 with the branch, platform, release date, and file size shown clearly on the same page.
What users usually want to know first
Release overview
Google Chrome 88.0.4324.190 is available here as part of the Linux Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
适用于Windows，Mac和Linux的chrome稳定版已更新为88.0.4324.190，此更新包括10个安全修复程序。下面，我们重点介绍了外部研究人员提供的修复方法，请查看此页面获取更多信息。
[$20000][1138143] High CVE-2021-21149: 解决数据传输中的堆栈溢出。
[$20000][1172192] High CVE-2021-21150: 解决下载中的UAF漏洞。
[$15000][1165624] High CVE-2021-21151: 解决支付方式中的UAF漏洞。
[$5000][1166504] High CVE-2021-21152: 解决介质中的堆缓冲区溢出。
[$1000][1155974] High CVE-2021-21153: 解决GPU进程栈溢出。
[$TBD][1173269] High CVE-2021-21154: 解决标签条中的堆缓冲区溢出。
[$TBD][1175500] High CVE-2021-21155: 解决标签条中的堆缓冲区溢出。
[$TBD][1177341] High CVE-2021-21156: 解决chrome V8引擎中的堆缓冲区溢出。
[$TBD][1170657] Medium CVE-2021-21157: 解决Web Sockets的UAF漏洞。
像往常一样，chrome的工程师们正在继续进行内部安全工作，负责一系列的修复工作：
[1178973] Various fixes from internal audits, fuzzing and other initiatives
Installation notes
After downloading the package, confirm that the branch and platform match your device before launching the installer or extracting the archive. If you only need a standard everyday browser, Stable is usually the safest choice. If you are testing new behavior, Beta, Dev, and Canary are better fits.
Related release pages
For newer or older builds in the same branch, open the category archive linked above. For different platforms, use the related desktop archives in the sidebar.
Frequently asked questions
These FAQ blocks help the page read like a complete release article instead of a download stub, which is better for trust and better for SEO.
Should I use this release or stay on Stable?
If you just want the safest everyday browsing experience, Stable is usually the right default. Preview branches are better for testing, compatibility checks, and early feature access.
Why show exact version numbers so prominently?
Because exact-version queries are common in English search behavior, especially for QA teams, enterprise users, and people trying to reproduce a bug or environment.
Why keep a full article around the download buttons?
A stronger page body gives users context and gives Google clearer signals about what the release page actually covers.
Where should older releases live?
Older versions belong in the category archive page, with this article template handling exact-version landing pages one release at a time.