It's not that simple.
It's easy for a developer to check what they are loading to make sure it will not overflow buffers. There is no reason to do a hash check, all they have to do is check the size of the data vs the size of the buffer, or verify that the buffer that they are being asked to create is within certain boundries.
I am not saying it can't be done, but I AM saying that the exploits, as we know them today, are dead. We may be able to find OTHER buffer exploits, but the font and the audio are dead.
BTW, I confirmed this info with a little birdy I know in Redmond who is in the know. This little birdy told me that, according to the dasboard dev team, the method used to fix the issue does not center on hash checks, but proper managment of buffer space.
Now little birdies CAN be wrong, but this one was right about the autoconnect feature of the 2.0 dash, and the autoupdate features that will function even if you don't connect to Live.
Morden.