Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-99218

coredump: hold RCU while releasing parked threads

No exploitation reported by the sources we read.

  • Published2026-11-02

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-0216:06CVE publishedCNA

Observed activity

isMalicious corpus · updated 2026-11-02 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-99218?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-99218?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Products declared by the CNA

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ a94e2d408eaedbd85aae259621d46fafc10479a2, < fd0fbe84312fda2fc187428c92c50b7d03a9d24cfixed in fd0fbe84312fda2fc187428c92c50b7d03a9d24cgit
    • ≥ a94e2d408eaedbd85aae259621d46fafc10479a2, < 71146c437bae59e5280f657965dc6d006ee3989bfixed in 71146c437bae59e5280f657965dc6d006ee3989bgit
    • ≥ a94e2d408eaedbd85aae259621d46fafc10479a2, < 0fce73efee40c65ce26641c5d93942462f9e8307fixed in 0fce73efee40c65ce26641c5d93942462f9e8307git
    • ≥ a94e2d408eaedbd85aae259621d46fafc10479a2, < 16e94ed90b1b02398e044d41fd1db34828daa08efixed in 16e94ed90b1b02398e044d41fd1db34828daa08egit
    • ≥ a94e2d408eaedbd85aae259621d46fafc10479a2, < a0f09ff4c6b93312e565cfe75d76c3a551a3ec4cfixed in a0f09ff4c6b93312e565cfe75d76c3a551a3ec4cgit
    • ≥ a94e2d408eaedbd85aae259621d46fafc10479a2, < b0eca0edddf4c1dbaf6d1f6a8636b4235f5bc573fixed in b0eca0edddf4c1dbaf6d1f6a8636b4235f5bc573git
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 2.6.27no fix stated

    Not affected < 2.6.27 · ≥ 6.1.191, ≤ 6.1.* · ≥ 6.6.161, ≤ 6.6.* · ≥ 6.12.115, ≤ 6.12.* · ≥ 6.18.60, ≤ 6.18.* · ≥ 7.2.14, ≤ 7.2.* · ≥ 7.3.1, ≤ 7.3.*

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-02

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-99218 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-11-02
  • CNACVSS 3.172026-11-02

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-02
Last Modified
2026-11-02
NVD status
Received

Frequently asked questions

What is CVE-2026-99218?

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.

Is CVE-2026-99218 actively exploited?

Active exploitation of CVE-2026-99218 has not been confirmed.

What is the CVSS score for CVE-2026-99218?

CVE-2026-99218 has a CVSS v3 base score of 7 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record