CVE-2026-99218·Kernel vulnerability
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
- high
- Software
- Kernel
- Fixed in
- 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.1
- Published
How to fix this CVE
Update your Linux kernel to a patched stable release to resolve a race condition in the coredump handler that can cause memory corruption. Identify which stable branch you currently run (6.1, 6.6, 6.12, 6.18, 7.2, or 7.3) and upgrade to the corresponding fixed version listed below, or install your distribution's patched kernel package.
sudo dnf update kernel kernel-headers kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your kernel version: uname -r
- Cross-reference against vulnerable ranges: 6.1.0-6.1.190, 6.6.0-6.6.160, 6.12.0-6.12.114, 6.18.0-6.18.59, 7.2.0-7.2.13, 7.3.0-7.3.0
- Search kernel logs for task_struct corruption or unexpected process termination: sudo dmesg | grep -i 'use-after-free\|memory corruption\|pi_lock'
- Verify fix applied: uname -r should report 6.1.191+, 6.6.161+, 6.12.115+, 6.18.60+, 7.2.14+, or 7.3.1+
FAQ
What is CVE-2026-99218?
This vulnerability is a race condition in the Linux kernel's coredump handler where parked threads can be freed from memory before wake_up_process() is called on them, leading to use-after-free conditions when accessing freed kernel structures.
Is CVE-2026-99218 being actively exploited?
No, there is no evidence of active exploitation or public exploit code available for this vulnerability at this time.
What versions of Kernel are affected by CVE-2026-99218?
Vulnerable versions span multiple stable branches: 6.1.0 through 6.1.190, 6.6.0 through 6.6.160, 6.12.0 through 6.12.114, 6.18.0 through 6.18.59, 7.2.0 through 7.2.13, and 7.3.0. Update to 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, or 7.3.1 respectively.
How do I check if my server is vulnerable to CVE-2026-99218?
Run 'uname -r' to get your kernel version and compare it against the affected ranges listed above. If your version is below the fixed release for your branch, you are vulnerable.
Does Defensia detect CVE-2026-99218?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-99218 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0fce73efee40c65ce26641c5d93942462f9e8307
- https://git.kernel.org/stable/c/16e94ed90b1b02398e044d41fd1db34828daa08e
- https://git.kernel.org/stable/c/61d58591aa0188bf2463e263962256316ff8b576
- https://git.kernel.org/stable/c/71146c437bae59e5280f657965dc6d006ee3989b
- https://git.kernel.org/stable/c/a0f09ff4c6b93312e565cfe75d76c3a551a3ec4c
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-99218. Free for 1 server.
Get started free