CVE-2026-97938

published 25 Sep 2026 · updated 1 Nov 2026

reboot: fix cad_pid use-after-free race

4.7MediumCVSS 4.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0c1a966bc047af2801a70b8eb13f9df5d7ab925f, Kernel 5a88f78df753993469dab4d1831f8fb4256a9468, Kernel 9a17b0e053197a6a42cdc75e75a35b17aa662088 and 2 more.

In the Linux kernel, the following vulnerability has been resolved: reboot: fix cad_pid use-after-free race cad_pid is a single kernel-wide struct pid pointer. proc_do_cad_pid() reads it and passes it to pid_vnr() without protecting the lifetime of the referenced struct pid. A concurrent writer can replace cad_pid and drop the final reference to the old struct pid after the reader has loaded the pointer but before pid_vnr() has finished dereferencing it, causing a use-after-free. kill_cad_pid() has the same lifetime race when it passes cad_pid to kill_pid(). At the time this issue was reported, an unprivileged user could reach the sysctl through user and PID namespaces because cad_pid was registered in pid_table[]. Moving cad_pid back to the global reboot sysctl table corrected that namespace and permission mismatch, but did not fix the underlying lifetime race. Fix this by treating cad_pid as an RCU-protected pointer at both read sites and by waiting for a grace period before dropping the old reference on the write side. call_rcu(&old_pid->rcu, ...) cannot be used here because free_pid() also queues pid->rcu; queueing the same rcu_head twice can corrupt the RCU callback list. Original KASAN crash stack: kernel/pid.c:545 pid_nr_ns() # reads freed pid->level kernel/pid.c:556 pid_vnr() # calls pid_nr_ns() kernel/pid.c:775 proc_do_cad_pid() # calls pid_vnr(cad_pid)

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.19, >=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <0c1a966bc047af2801a70b8eb13f9df5d7ab925f, >=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <5a88f78df753993469dab4d1831f8fb4256a9468, >=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <9a17b0e053197a6a42cdc75e75a35b17aa662088, >=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <ad72e2566643fff7f01666d845fb026898155e1f, >=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <ae3e53fe3c1241855e3a88f74877738349948c780c1a966bc047af2801a70b8eb13f9df5d7ab925f, 5a88f78df753993469dab4d1831f8fb4256a9468, 9a17b0e053197a6a42cdc75e75a35b17aa662088, ad72e2566643fff7f01666d845fb026898155e1f, ae3e53fe3c1241855e3a88f74877738349948c78

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97938 severity on Zeptric[![CVE-2026-97938](https://zeptric.io/badge/cve/CVE-2026-97938.svg)](https://zeptric.io/cve/CVE-2026-97938)