Lots of drivers, network protocols, etc. in the kernel, and they're most of the attack surface -- not the scheduler :-) We have to approach this as a question

Lots of drivers, network protocols, etc. in the kernel, and they're most of the attack surface -- not the scheduler :-) We have to approach this as a question of how, not if. When we do that, we can change computer security.