> It also did not work on Linux and presumably not on Apple's ARM CPUs.
Hmm, anyone else find this interesting? I haven't looked into the actual exploit itself yet, but having it work on Android, which has SELinux and/or other protections by default, but not on (presumably) a generic Linux distro, is weird.
I would have assumed it exploited something present only on mobile builds of Chrome, but it affects Windows as well. Odd.