


Medium CVE-2022-2613: Use after free in Input.Reported by Erik Kraft ( ), Martin Schwarzl ( ) on Medium CVE-2022-2612: Side-channel information leakage in Keyboard input.As reported by Irvan Kurniawan (sourc7) on Medium CVE-2022-2611: Inappropriate implementation in Fullscreen API.

Medium CVE-2022-2610: Insufficient policy enforcement in Background Fetch.As reported by koocola and Guang Gong of 360 Vulnerability Research Institute on High CVE-2022-2609: Use after free in Nearby Share.High CVE-2022-2608: Use after free in Overview Mode.High CVE-2022-2607: Use after free in Tab Strip.High CVE-2022-2606: Use after free in Managed devices API.High CVE-2022-2605: Out of bounds read in Dawn.High CVE-2022-2604: Use after free in Safe Browsing.High CVE-2022-2603: Use after free in Omnibox.Please visit the Chrome Security Page for more information. Listed below are the highlighted fixes that were contributed by external researchers. Google will also retain restrictions if the bug exists in one or multiple third-party libraries that other projects similarly depend on, but haven’t been fixed as of yet.įrom the latest information, the stable update 104 includes 27 security fixes. It should be noted that access to bug details and links may be kept restricted by Google until a majority of users are updated with a fix.
