Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-99218

coredump: hold RCU while releasing parked threads

High7.0EPSS 0.12%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2026-99218, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.

Affected products

  • Linux · Linux

    • affected a94e2d408eaedbd85aae259621d46fafc10479a2 – < fd0fbe84312fda2fc187428c92c50b7d03a9d24c
    • affected a94e2d408eaedbd85aae259621d46fafc10479a2 – < 71146c437bae59e5280f657965dc6d006ee3989b
    • affected a94e2d408eaedbd85aae259621d46fafc10479a2 – < 0fce73efee40c65ce26641c5d93942462f9e8307
    • affected a94e2d408eaedbd85aae259621d46fafc10479a2 – < 16e94ed90b1b02398e044d41fd1db34828daa08e
    • affected a94e2d408eaedbd85aae259621d46fafc10479a2 – < a0f09ff4c6b93312e565cfe75d76c3a551a3ec4c
    • affected a94e2d408eaedbd85aae259621d46fafc10479a2 – < b0eca0edddf4c1dbaf6d1f6a8636b4235f5bc573
    • affected a94e2d408eaedbd85aae259621d46fafc10479a2 – < 61d58591aa0188bf2463e263962256316ff8b576
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.60 – ≤ 6.18.*
    • unaffected 7.2.14 – ≤ 7.2.*
    • unaffected 7.3.1 – ≤ 7.3.*
    • unaffected 7.4-rc1 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

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

Record last updated .