# CVE-2019-19922: Denial of service in n/a

> Attackers can cause denial of service in Kubernetes clusters by triggering unwanted CPU slice expiration in the Linux kernel scheduler.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-19922, GHSA-q3fc-6x2v-6ph8, UBUNTU-CVE-2019-19922

## What is CVE-2019-19922?

CVE-2019-19922 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 22 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

kernel/sched/fair.c in the Linux kernel before 5.3.9, when cpu.cfs_quota_us 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.)

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2019-19922?

It affects 14 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Linux kernel, Netapp Active Iq Unified Manager, Netapp Aff Baseboard Management Controller, Netapp Cloud Backup, Netapp Data Availability Services, Netapp E-Series Santricity Os Controller, Netapp Fas\/Aff Baseboard Management Controller, Netapp Hci Baseboard Management Controller, Netapp Solidfire \& Hci Management Node, Netapp Solidfire Baseboard Management Controller, Netapp Steelstore Cloud Integrated Storage, Oracle Sd-Wan Edge.

## How do I fix CVE-2019-19922?

Upgrade to a fixed version.

## Is CVE-2019-19922 being exploited?

There is no known exploitation of CVE-2019-19922 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19922 and fix it if it is affected.

What it is: CVE-2019-19922 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 22 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19922 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-19922/ (Markdown: https://insights.sbomify.com/CVE-2019-19922/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-19922
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-19922
- OSV: https://osv.dev/vulnerability/CVE-2019-19922

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-19922/
Summaries are generated and may contain mistakes; the official description above is the record.