Re:WebGL support in iOS 5 only available to iAd developers
by maximilianburke on Thursday June 16, 2011 @12:57PM
(#2662087)
GPUs don't respect CPU memory protection -- they can write to any region of mapped memory. If you happen to have some of your program code living there you can "draw" over it with replacement code.
[ Parent
| on HN ]
Re:WebGL support in iOS 5 only available to iAd developers
by recoiledsnake on Thursday June 16, 2011 @01:13PM
(#2662195)
What you wrote doesn't make any sense whatsoever, you seem to imply that there is an inherent problem by design with this, but there is no such thing. There are possible bugs etc. that could lead to arbitrary code execution by exploiting as-yet-not-found holes in current drivers. But saying that you can draw over program code would allow even browser content to overwrite program code, especially in these days of GPU accelerated browsers.
Re:WebGL support in iOS 5 only available to iAd developers
by daeken on Thursday June 16, 2011 @01:22PM
(#2662242)
To be fair, it's possible for the GPU to write to arbitrary memory, but it wouldn't happen as a matter of standard usage by any means.
Re:WebGL support in iOS 5 only available to iAd developers
by maximilianburke on Thursday June 16, 2011 @02:24PM
(#2662533)
It's only a problem if the bits of memory you want to enforce special protection rights on (ie: no execute, read only, etc.) is also mapped into the GPU's address space.
It's not something that "just happens" normally, it most often requires clear intent to do so, but it can be done.