CVE-2026-99218 json
coredump: hold RCU while releasing parked threads
published 2026-11-02 6 d ago modified 2026-11-03 5 d ago also EUVD-2026-115260
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
coredump: hold RCU while releasing parked threads
coredump_finish() releases the parked threads by clearing ->task in their core_thread entry and calling wake_up_process() on each of them. It does that without holding a reference on the task and without being inside rcu.
But calling wake_up_process(task) without rcu here isn't safe. A parked thread doesn't need that wakeup to leave. A spurious wakeup or a preemption after the store is enough for the task to go away.
So if the coredump client is preempted between the store and wake_up_process() the thread can exit and be freed in the meantime and try_to_wake_up() takes pi_lock in freed memory.
Hold rcu across the loop.
Patch / fix
- Linux Linux 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.1, 7.4-rc1
- linux Debian 13 6.12.115-1
- linux Debian 14 7.2.14-1
debian advisories DEBIAN-CVE-2026-99218
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-112532
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/fd0fbe84312fda2fc187428c92c50b7d03a9d24c commit
- git.kernel.org/stable/c/71146c437bae59e5280f657965dc6d006ee3989b commit
- git.kernel.org/stable/c/0fce73efee40c65ce26641c5d93942462f9e8307 commit
- git.kernel.org/stable/c/16e94ed90b1b02398e044d41fd1db34828daa08e commit
- git.kernel.org/stable/c/a0f09ff4c6b93312e565cfe75d76c3a551a3ec4c commit
- git.kernel.org/stable/c/b0eca0edddf4c1dbaf6d1f6a8636b4235f5bc573 commit
- git.kernel.org/stable/c/61d58591aa0188bf2463e263962256316ff8b576 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99218 updated cvss 7.0
kernel: kernel: privilege escalation via use-after-free in coredump subsystem
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9, openshift/ose-rhel-coreos-10affected: workaround, no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/fd0fbe84312fda2fc187428c92c50b7d03a9d24c
- git.kernel.org /stable/c/71146c437bae59e5280f657965dc6d006ee3989b
- git.kernel.org /stable/c/0fce73efee40c65ce26641c5d93942462f9e8307
- git.kernel.org /stable/c/16e94ed90b1b02398e044d41fd1db34828daa08e
- git.kernel.org /stable/c/a0f09ff4c6b93312e565cfe75d76c3a551a3ec4c
- git.kernel.org /stable/c/b0eca0edddf4c1dbaf6d1f6a8636b4235f5bc573
- git.kernel.org /stable/c/61d58591aa0188bf2463e263962256316ff8b576
Sources
- CVE List CVE-2026-99218
- NVD CVE-2026-99218
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.