Reducing runtime complexity

Some time ago I wrote a thesis about complexity in the Linux kernel and how to reduce it in order to limit the attack surface[1].
While the results are unlikely to bring news to the audience here, it did indicate some possible ways to avoid exposing optional kernel features when they are not needed.
The basic idea would be to either build or configure parts of the kernel after or during the installation on a specific host.

Distributions are commonly shipping the kernel as one large binary that includes support for nearly every hardware driver and optional feature, but the end user will normally use very little of this.
In comparison, a custom kernel build for a particular device and use case, would be significantly smaller. While the reduced complexity won't be directly linked with reduction in attack surface, from my understanding the difference would make a relevant impact.

The question I keep wondering about is how feasible this is for general purpose distributions to have the kernel "rebuild" in this way when it is installed on a particular machine.

- Stefan


[1] https://doi.org/10.13140/RG.2.2.29943.70561

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEjLwAv8xLYF1doyZLdIuckz2DLQMFAmOJCdQACgkQdIuckz2D
LQMndA//WbwikJvResHro4tj8M59EvcRMfcgMSSGWidjb1GtxJEfH6HA1yjcDFKL
5N8S+BdLy40wUClNQ8G1I3fRDOALJAUceaJj7bhvmHqDpD9gmOgYMRDukUq2eD9w
/mdFgtYug4WAlBbrCAEI0QzjAHL2zYjYkGV45MvK1z8QGC0u8U6VolnuIJftk2pT
QiTcU4Mg7l0E68hIrbEiRb+uVJgVYf+FQ18AsBrY9Cv9m+E+KP5z9Zi6yiKZDLWt
HSm2po2NfGq65hovAS1oHEMZI8Gdmo6Fr1EE6K3QSksox0zSwmhsyGDr61qKPOWx
83UEkmsDuFbkBpgDb/PWxx1Y78b71VBMg3Nd3DfLw4bsRtkNGm7JhZtEUv3yPASO
0Dmjr0jzYsGEOHsF2pvrOeod/HiQ0/b/mPiLQb9ufG9wsqiVDU8Rydjvbgi1kMB/
kudD8Dn72LCnqrSSQX9hu54clIPZUnePdahI+zvRFYbkfKpb1fPCc2xWxBq1dcsD
VB7XVLEklaCI+rG1feKmxcnYmXezl/CsKe+6wzFxQszH/G29NOOy5R9pjvhpXiJw
T5FddGp58q1/6en4bXbsK9XyjieOjhY+qWVn69QnfQt3s2ISGipQpbKLj4CJ4TyH
yaEHmQoy4C5D2BJFg9opSONOrsA2MfPdOwrhgYaWdAPnlpZGefg=
=XKYN
-----END PGP SIGNATURE-----