# CVE-2019-11599: Race condition in n/a

> Local attackers can exploit a race condition in the Linux kernel coredump implementation to read sensitive memory or crash the system.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:** 29 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** CVE-2019-3892, DEBIAN-CVE-2019-11599, GHSA-q8vw-4h9f-5745, UBUNTU-CVE-2019-11599

## What is CVE-2019-11599?

CVE-2019-11599 is a high-severity vulnerability in Linux kernel, published on 29 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The coredump implementation in the Linux kernel before 5.0.10 does not use locking or other mechanisms to prevent vma layout or vma flags changes while it runs, which allows local users to obtain sensitive information, cause a denial of service, or possibly have unspecified other impact by triggering a race condition with mmget_not_zero or get_task_mm calls. This is related to fs/userfaultfd.c, mm/mmap.c, fs/proc/task_mmu.c, and drivers/infiniband/core/uverbs_main.c.

Weakness: CWE-667 (Improper Locking)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2019-11599 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11599 exists.

Public exploit code:

- Linux - Missing Locking Between ELF coredump code and userfaultfd VMA Modification (exploitdb)

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11599 is a high-severity vulnerability in Linux kernel, published on 29 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11599 exists.

Affected product: Linux kernel. 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-11599/ (Markdown: https://insights.sbomify.com/CVE-2019-11599/index.md)
```

## Sources

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

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