Download Google Chrome for Linux 112.0.5615.50 Download

Google Chrome is a fast, simple and secure browser, built for the modern web. If you’re just getting started with Chrome or want to improve it, we recommend checking out our Chrome optimization guide.

Speed

Chrome is designed to be fast in every possible way: It’s quick to launch from the desktop, loads web pages in a flash, and runs complex web applications quickly. Learn more about Chrome and speed.

Simplicity

Chrome’s browser window is streamlined, clean and simple. Chrome also includes features designed for efficiency and ease of use. For example, you can search and navigate from the same box, and arrange tabs as you like — quickly and easily.

Safety

Chrome is designed to keep you safer and more secure online with built-in malware and phishing protection, automatic updates to ensure your browser is up to date with the latest security updates, and more. Learn more about Chrome’s security features.

And more functions

Chrome has many useful features built in, including extensions, in-browser translation, themes, and more. Learn more about Chrome’s latest and most popular features.

What is new

The Chrome team is excited to announce the promotion of Chrome 112 to the stable channel for Windows, Mac, and Linux. This will roll out over the coming days/weeks.

Chrome 112.0.5615.49 (Linux and Mac), 112.0.5615.49/50 (Windows) contains a number of fixes and improvements — a list of changes is available in the log. Look out for upcoming Chrome and Chromium blog posts about new features and major efforts delivered in 112.

Security fixes and rewards

Note: Access to bug details and links may be restricted until the majority of users are updated with a fix. We’ll also keep restrictions if the bug exists in a third-party library that other projects similarly depend on but haven’t yet fixed.

This update includes 16 security fixes. Below we highlight corrections that were contributed by external researchers. See the Chrome Security page for more information.

• [$5000][1414018] High CVE-2023-1810: Heap buffer overflow in Visuals. Reported by Weipeng Jiang (@Krace) from VRI 2023-02-08
• [$3000][1420510] High CVE-2023-1811: Use after free in Frames. Reported by Thomas Orlita 2023-03-01
• [$5000][1418224] Medium CVE-2023-1812: Out of bounds memory access in DOM bindings. Reported by Shijiang Yu on 2023-02-22
• [$5000][1423258] Medium CVE-2023-1813: Improper implementation in extensions. Reported by Axel Chong 2023-03-10
• [$3000][1417325] Medium CVE-2023-1814: Insufficient validation of untrusted input in Safe Browsing. Reported by Young Min Kim (@ylemkimon), CompSec Lab at Seoul National University 2023-02-18
• [$2000][1278708] Medium CVE-2023-1815: Use after free in Networking APIs. Reported by DDV_UA 2021-12-10
• [$1000][1413919] Medium CVE-2023-1816: Incorrect picture-in-picture security interface. Reported by NDevTK 2023-02-08
• [$1000][1418061] Medium CVE-2023-1817: Insufficient policy enforcement in intents. Reported by Axel Chong 2023-02-22
• [$NA][1223346] Medium CVE-2023-1818: Use after free in Vulkan. Reported by Abdulrahman Alqabandi, Microsoft Browser Vulnerability Research, Eric Lawrence, Microsoft, Patrick Walker (@HomeSen) and Kirtikumar Anandrao Ramchandani 2021-06-24
• [$NA][1406588] Medium CVE-2023-1819: Out of bounds read in Availability. Reported by Microsoft Edge Team on 2023-01-12
• [$TBD][1408120] Medium CVE-2023-1820: Heap buffer overflow in browser history. Reported by raven at KunLun lab 2023-01-17
• [$1000][1413618] Low CVE-2023-1821: Improper implementation in WebShare. Reported by Axel Chong 2023-02-07
• [$500][1066555] Low CVE-2023-1822: Incorrect security interface in navigation. Reported by �*ì°ì§ 2020-04-01
• [$TBD][1406900] Low CVE-2023-1823: Improper implementation in FedCM. Reported by Jasper Rebane (popstonia) on 2023-01-13

We also want to thank all the security researchers who worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

As usual, our ongoing internal security work was responsible for a large number of fixes:

• [1430254] Various corrections from internal audits, fuzzing and other measures

Many of our security flaws are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.