Chrome and Windows Exploit: Security Beyond Bug Fixes

These represent a fairly standard exploit chain: code execution in Chrome’s sandboxed renderer process and then a kernel bug to escape the sandbox and gain privileged code execution. There’s a few mitigations and sandboxing improvements that look relevant to this vulnerability:

Windows has two sets of syscalls: Windows NT, which contains typical OS functionality such as process management and file system access, and win32k, which contains GUI functionality. This exploit was against a win32k syscall, so in Windows 10 it would not have been possible to reach this vulnerable code from the sandboxed Chrome process.

Source: alexgaynor.net