out of bounds array read/writes could cause issues on any platform but surely all that can occur is that you corrupt video memory & potentially lock up a shader as a result ? a timeout in a faulty shader would close this security hole. a shader malfunction message could then be generated.
I give a fuck.
If there is a security hole, it's unlikely to be limited to Linux (or is it ? - waiting for details)
There are still a lot of IE users out there so support on that platform would help build the business case for WebGL content.
Switching browsers is an option if it's a secure solution.
Software production is assumed to be a line function, but it is run like a staff function. -- Paul Licker