There is no privilege separation between kernel modules. They all run in the same address space with the same CPU privilege. SELinux, seccomp, and all that pro

There is no privilege separation between kernel modules. They all run in the same address space with the same CPU privilege. SELinux, seccomp, and all that protect a compromised user space thread in the host (responsible for running emulated guests, or one that provides virtual device support to guests) from other user space threads (other VMs). If there is a some problem in the KVM kernel module that stomps over memory, SELinux and seccomp can't do anything about it.