"Just over two months ago, Chrome sponsored the Pwnium browser hacking competition.  We had two fantastic submissions, and successfully blocked both exploits within 24 hours of their unveiling.  Today, we'd like to offer an inside look into the exploit submitted by Pinkie Pie."  A work of pure art, this.  Also, this is not the same person as the other PinkiePie.  Also also, you didn't think I'd let a story with a headline like this go by unnoticed, did you? 

Did you actually read the functions?  It is a calculation logic error.  There is no language alive to prevent logic errors.  The logic error results in an invalid buffer access for a GPU related task.  No "sane" language has yet been extended to use GPUs that do no rely on creating buffers directly at some point in its execution. 

Yes I've read the functions, ComputeMaxResults() and ComputeSize(),
are the standard way to manipulate blocks of memory/arrays in C and related to the way arrays decay into pointers. 

You do understand that were a managed language required to access the GPU, it would also need to do manual memory management undercovers, don't you? 

Memory pointers are a hardware feature.  They just happen to be 'exposed' in c/++.  I can use assembly to fool any programming written in any language that I am friendly and of the same breed and interject myself using hardware features. 

Security like you are speaking would require a massive hardware change where memory is addressed in locked relative-memory segments.  That is every process can create restricted areas of memory which can only be accessed by a compile-time validated code-path - something a few steps beyond nX-bits. 

Even then, you would only need to find a way to inject yourself into that code-path by altering the binary... but that would be easier to catch and prevent.  You would then need to rely on OS/hardware bugs... but you would still be able to get 'in' in some manner...nothing is safe beyond not permitting execution at all...

Which language was used simply doesn't mean squat.  A program written in Delphi still debases itself to the same approximate code which was written in c. I'm still using movl %eax, %ecx, call, jmp, etc...