Learn from this!

Learn from this!

What should be done now is:

Assume you have a perfect kernel with an unknown problem in brk(). Ask yourself, what security measures (other than finding the bug and fixing it) could prevent the bug from being exploited?

When you have a good answer, go implement it and this won't happen again.

Our local Windows guru says that MS has started using the following procedure when security problems are found in their sources:
1. Report the problem to a group making static code analysis tools.
2. That group is responsible for making a tool that can find the bug that was just fixed.
3. The static code analysis tool is run on the sources at regular intervals.

Linux has the Stanford checker and another Free tool of which I cannot currently remember the name, but I don't know if the feedback works as outlined above. And regardless of whether MS actually manages to implement the above procedure or not, the Linux community should.