cve.bz

CVE-2026-99218 linux linux

7.0 highEPSS 0.1%Fix available

High (7.0) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.60
  • Linux Linux: fixed in 7.2.14
  • Linux Linux: fixed in 7.3.1
  • Linux Linux: fixed in 7.4-rc1
  • Debian, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99218 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99218?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99218?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99218 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-99218

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99218](https://cve.bz/cve/badge/CVE-2026-99218.svg)](https://cve.bz/cve/CVE-2026-99218)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99218"><img src="https://cve.bz/cve/badge/CVE-2026-99218.svg" alt="CVE-2026-99218"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux2.6.27 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.60
Linux7.27.2.14
Linux7.37.3.1
Linuxlater releases7.4-rc1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-99218
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99218
Debian13linux6.12.115-1DEBIAN-CVE-2026-99218
Debian14linux7.2.14-1DEBIAN-CVE-2026-99218
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99218
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99218
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99218
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-99218
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99218
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99218
Ubuntu26.10linux, linux-aws, linux-gcp and 6 moreno fix listedUBUNTU-CVE-2026-99218
UbuntuNvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99218
UbuntuPro:14.04:LTSlinux, linux-aws, linux-azure and 1 moreno fix listedUBUNTU-CVE-2026-99218
UbuntuPro:16.04:LTSlinux, linux-aws, linux-gcp and 5 moreno fix listedUBUNTU-CVE-2026-99218
UbuntuPro:18.04:LTSlinux, linux-aws, linux-kvm and 10 moreno fix listedUBUNTU-CVE-2026-99218
UbuntuPro:20.04:LTSlinux, linux-aws, linux-gcp and 19 moreno fix listedUBUNTU-CVE-2026-99218
4 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.3.3-1.1openSUSE-SU-2026:12497-1
Azure Linux3kernel6.6.161.1-1AZL-112532
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99218
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99218
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99218

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having a Moderate impact rather than Important because exploitation requires local access and depends on winning an intricate timing window during task exit preemption. Although core dumping facilities are present in standard Red Hat Enterprise Linux deployments, an unprivileged attacker cannot trigger the race condition remotely. While memory corruption could theoretically allow local privilege elevation, the most probable outcome of an exploit attempt is an immediate kernel crash resulting in a denial of service.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-04) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to protect parked thread release in coredump_finish with RCU so task structures are not freed before wake_up_process executes: upgrade to the corresponding fixed Red Hat builds, which hold an RCU read lock across the loop releasing parked threads in coredump_finish, closing multithreaded core dump execution racing task preemption and exit. Until patched, this is only a concern on Linux systems where local unprivileged users can trigger core dumps of multithreaded processes — Non-Linux platforms and remote network access vectors are unaffected — so Restrict process core dump creation for unprivileged local accounts via ulimit or sysctl kernel.core_pattern configurations. As a compensating measure, Enable runtime memory error detection such as KASAN to trap task memory use-after-free conditions in try_to_wake_up during thread exit. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free race condition defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1005 Runtime Memory Error Detection (KASAN/HWASan) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelAffected
Red Hat Enterprise Linux 7kernel-rtAffected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-10Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-99218.

References

Check your stackJSON