> important component of a successful attack, and are a violation of some security policies If the kernel returned random values from gettime, that'd lead to t

> important component of a successful attack, and are a violation of some security policies If the kernel returned random values from gettime, that'd lead to tls certificate validation not being reliable anymore. As result, any bug in gettime is certainly worthy of a CVE. If the kernel shuffled filenames so they'd be returned backwards, apparmor and selinux profiles would break. As result, that'd be worthy of a CVE. If the kernel has a memory corruption, use after free, use of uninitialized memory or refcounting issue, that's obviously a violation of security best practices and can be used as component in an exploit chain. Can you now see how almost every kernel bug can and most certainly will be turned into a security issue at some point?