Upstream has released version 51.0.2704.63 on May 25: http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html This fixes several new security issues. This is the current version in the stable channel: http://googlechromereleases.blogspot.com/search/label/Stable%20updates
Packages are available for testing: MGA5 SRPM: chromium-browser-stable-51.0.2704.63-1.mga5.src.rpm RPMS: chromium-browser-stable-51.0.2704.63-1.mga5.i586.rpm chromium-browser-51.0.2704.63-1.mga5.i586.rpm chromium-browser-stable-51.0.2704.63-1.mga5.x86_64.rpm chromium-browser-51.0.2704.63-1.mga5.x86_64.rpm Proposed advisory: Chromium-browser-stable 51.0.2704.63 fixes security issues: cross-origin bypass problems in extensions bindings (CVE-2016-1672 and CVE-2016-1676), blink (CVE-2016-1673 and CVE-2016-1675), and extensions (CVE-2016-1674) heap use-after free bugs in V8 bindings (CVE-2016-1679), Skia (CVE-2016-1680), and Autofill (CVE-2016-1690) heap buffer overflows in V8 (CVE-2016-1678), PDFium (CVE-2016-1681), media (CVE-2016-1689), and Skia (CVE-2016-1691) out-of-bounds read errors in PDFium (CVE-2016-1685 and CVE-2016-1686) and V8 (CVE-2016-1688) type confusion in V8 (CVE-2016-1677), a CSP bypass for ServiceWorker (CVE-2016-1682), an information leak in extensions (CVE-2016-1687), a limited cross-origin bypass in ServiceWorker (CVE-2016-1692), and HPKP pins removed on cache clearance (CVE-2016-1694) various fixes from upstream's internal audits, fuzzing, and other initiatives (CVE-2016-1695) References: http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1672 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1673 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1674 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1675 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1676 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1677 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1678 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1679 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1680 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1681 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1682 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1685 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1686 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1687 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1688 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1689 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1690 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1691 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1692 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1694 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1695
CC: (none) => cjwAssignee: cjw => qa-bugs
OpenSuSE has issued an advisory for this on May 28: https://lists.opensuse.org/opensuse-updates/2016-05/msg00115.html
Working fine for me on Mageia 5 x86_64. It looks a little different now. I was surprised to see the hamburger changed to a vertical ellipsis.
Whiteboard: (none) => MGA5-64-OK
Working fine on Mageia 5 i586 as well.
Whiteboard: MGA5-64-OK => MGA5-32-OK MGA5-64-OK
(In reply to David Walser from comment #3) > Working fine for me on Mageia 5 x86_64. It looks a little different now. I > was surprised to see the hamburger changed to a vertical ellipsis. (In reply to David Walser from comment #4) > Working fine on Mageia 5 i586 as well. Sterling work yet again, thanks for doing it so speedily. Validating.
Keywords: (none) => validated_updateCC: (none) => lewyssmith, sysadmin-bugs
URL: (none) => http://lwn.net/Vulnerabilities/689242/
Hopefully we can get this pushed ASAP, as there's another Chrome update as of yesterday, so we're going to get another build of this soon.
Advisory uploaded.
Whiteboard: MGA5-32-OK MGA5-64-OK => advisory MGA5-32-OK MGA5-64-OK
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2016-0214.html
Status: NEW => RESOLVEDResolution: (none) => FIXED