From ${URL} : The stable channel has been updated to 53.0.2785.113 for Windows, Mac, and Linux. This will roll out over the coming days/weeks (MSI points to M53). Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes these security fixes. Below, we highlight fixes that were contributed by external researchers, including those not already mentioned in recent release notes. Please see the Chrome Security Page for more information [$TBD][641101] High CVE-2016-5170: Use after free in Blink. Credit to Anonymous [$TBD][643357] High CVE-2016-5171: Use after free in Blink. Credit to Anonymous [$TBD][616386] Medium CVE-2016-5172: Arbitrary Memory Read in v8. Credit to Choongwoo Han [$3000][468931] Medium CVE-2016-5173: Extension resource access. Credit to Anonymous [$1000][579934] Medium CVE-2016-5174: Popup not correctly suppressed. Credit to Andrey Kovalev (@L1kvID) Yandex Security Team We would also like to thank all security researchers that 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 wide range of fixes: [646394] CVE-2016-5175: Various fixes from internal audits, fuzzing and other initiatives. Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity or LibFuzzer. @maintainer(s): since the fixed package is already in the tree, please let us know if it is ready for the stabilization or not.
It should be ok to stable 53.0.2785.113. You could also do 53.0.2785.116 if that's in the tree by the time you read this (I'm building it now).
I already tested 53.0.2785.113, but I don't mind test 53.0.2785.116 now.
stable for amd64 and x86
Arches and Maintainer(s), Thank you for your work. Added to an existing GLSA Request.
This issue was resolved and addressed in GLSA 201610-09 at https://security.gentoo.org/glsa/201610-09 by GLSA coordinator Kristian Fiskerstrand (K_F).
