CVE-2019-19922: Medium severity Linux Linux kernel vulnerability
A flaw was found in the Linux kernel’s scheduler, where it can allow attackers to cause a denial of service against non-CPU-bound applications by generating a workload that triggers unwanted scheduling slice expiration. A local attacker who can trigger a specific workload type could abuse this technique to trigger a system to be seen as degraded, and possibly trigger workload-rebalance in systems that use the slice-expiration metric as a measure of system health.
Other sources
A flaw was found in the Linux kernels scheduler which can allow attackers to cause a denial of service against non-CPU-bound applications by generating a workload that triggers unwanted scheduling slice expiration. A local attacker who is able to trigger a specific workload type could abuse this technique to trigger a system to be seen as 'degraded' and possibly trigger workload-rebalance in systems that use slice-expiration metric as a measure of system health.
Reference: https://github.com/kubernetes/kubernetes/issues/67577
Reference and upstream commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=de53fd7aedb100f03e5d2231cfce0e4993282425
— Red Hat
kernel/sched/fair.c in the Linux kernel before 5.3.9, when cpu.cfsquotaus is used (e.g., with Kubernetes), allows attackers to cause a denial of service against non-cpu-bound applications by generating a workload that triggers unwanted slice expiration, aka CID-de53fd7aedb1. (In other words, although this slice expiration would typically be seen with benign workloads, it is possible that an attacker could calculate how many stray requests are required to force an entire Kubernetes cluster into a low-performance state caused by slice expiration, and ensure that a DDoS attack sent that number of stray requests. An attack does not affect the stability of the kernel; it only causes mismanagement of application execution.)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/kernel-altto a version that resolves this vulnerability.Fixed in 0:4.14.0-115.19.1.el7a - Upgrade
Upgrade
redhat/kernel-rtto a version that resolves this vulnerability.Fixed in 0:4.18.0-193.rt13.51.el8 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 0:4.18.0-193.el8 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.7-1Fixed in 7.1.8-1
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2019-19922?
CVE-2019-19922 has a severity rating of medium, as it can cause a denial of service for non-CPU-bound applications.
How do I fix CVE-2019-19922?
To fix CVE-2019-19922, upgrade to the patched versions of the affected Linux kernel packages as specified by your distribution.
Which Linux distributions are affected by CVE-2019-19922?
CVE-2019-19922 affects several Linux distributions, including Red Hat, Debian, Oracle Linux, and Ubuntu.
Can CVE-2019-19922 be exploited remotely?
CVE-2019-19922 cannot be exploited remotely; it requires local access to the system to execute the specific workload.
What types of applications are impacted by CVE-2019-19922?
CVE-2019-19922 specifically impacts non-CPU-bound applications that can be disrupted by the workload triggering unwanted scheduling slice expiration.