HIGH Introduced in 2.6.27
coredump ParkedThread UAF
CVE-2026-99218
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.0HIGH
01Description
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.
02KernelScan AI Analysis
Risk summary
A local unprivileged user can trigger a use-after-free in the kernel's coredump handling by causing a process to generate a core dump. Winning a race window during thread cleanup allows corrupting freed task_struct memory, leading to kernel privilege escalation or denial of service. The bug is reachable from containers and user namespaces, making it a container escape risk on multi-tenant systems.
Vulnerability analysis
When a core dump completes, the kernel releases parked threads by clearing their task pointer and waking them. The original code did this without RCU protection, so if the coredump process was preempted between clearing the pointer and issuing the wakeup, a parked thread could exit and have its task_struct freed. The subsequent wakeup would then operate on freed memory, causing a use-after-free. The fix wraps the release loop in an RCU read-side critical section, guaranteeing that any task alive at loop entry remains valid until the loop finishes. Any local user who can crash a process (e.g., via SIGSEGV) can trigger the coredump path, so the bug is exploitable from unprivileged contexts, containers, and user namespaces.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.1 | 2.6.27 | 6.1.191 | fd0fbe84312f |
| 6.12 | 2.6.27 | 6.12.115 | 0fce73efee40 |
| 6.18 | 2.6.27 | 6.18.60 | 16e94ed90b1b |
| 6.6 | 2.6.27 | 6.6.161 | 71146c437bae |
| 7.2 | 2.6.27 | 7.2.14 | a0f09ff4c6b9 |
| 7.3 | 2.6.27 | 7.3.1 | b0eca0edddf4 |
| mainline | 2.6.27 | 7.4-rc1 | 61d58591aa01 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Affected — no CIP fix yet (latest 6.12.114-cip34) |
| cip/6.1 | Affected — no CIP fix yet (latest 6.1.190-cip62) |
| cip/6.1-rt | Affected — no CIP fix yet (latest 6.1.189-cip61-rt32) |
| cip/5.10 | Affected — no CIP fix yet (latest 5.10.272-cip79) |
| cip/5.10-rt | Affected — no CIP fix yet (latest 5.10.272-cip79-rt35) |
| cip/4.19 | Affected — no CIP fix yet (latest 4.19.325-cip136) |
| cip/4.19-rt | Affected — no CIP fix yet (latest 4.19.325-cip136-rt50) |
| cip/4.4 | Affected — no CIP fix yet (latest 4.4.302-cip115) |
| cip/4.4-rt | Affected — no CIP fix yet (latest 4.4.302-cip115-rt63) |