Kernel Self Protection Project
This project starts with the premise that kernel bugs have a very long lifetime, and that the kernel must be designed in ways to protect against these flaws. We must think of security beyond fixing bugs. As a community, we already find and fix individual bugs via static checkers (compiler flags, smatch, coccinelle, coverity) and dynamic checkers (kernel configs, trinity, KASan). Those efforts are important and on-going, but if we want to protect our billion Android phones, our cars, the International Space Station, and everything else running Linux, we must get proactive defensive technologies built into the upstream Linux kernel. We need the kernel to fail safely, instead of just running safely.
These kinds of protections have existed for years in the PaX and grsecurity patches, and in piles of academic papers. For various social, cultural, and technical reasons, they have not made their way into the upstream kernel, and this project seeks to change that. Our focus is on kernel self-protection, rather than kernel-supported userspace protections. The goal is to eliminate classes of bugs and eliminate methods of exploitation.
A short list of things to keep in mind when designing self-protection features:
- Patience and an open mind will be needed. We're all trying to make Linux better, so let's stay focused on the results.
- Upstream development is evolutionary, not revolutionary, which means it can sometimes take time for features to become fully realized.
- Features will be more than finding bugs, and should be active at run-time to catch previously unknown flaws.
- Features will not be developer-"opt-in". When a feature is enabled at build time, it should work for all code built into the kernel (which has the side-effect of also covering out-of-tree code, like in vendor forks).
For kernel protections already in upstream (or under active development) that have specific documentation:
- Kernel reference counter overflow protection