CVE-2026-97938reboot: fix cad_pid use-after-free race
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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)
Timeline
ID reserved
By Linux
Published
- 26 days later
· 26 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 – < 0c1a966bc047af2801a70b8eb13f9df5d7ab925f
- affected 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 – < ae3e53fe3c1241855e3a88f74877738349948c78
- affected 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 – < ad72e2566643fff7f01666d845fb026898155e1f
- affected 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 – < 9a17b0e053197a6a42cdc75e75a35b17aa662088
- affected 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 – < 5a88f78df753993469dab4d1831f8fb4256a9468
- affected 2.6.19
- unaffected < 2.6.19
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/0c1a966bc047af2801a70b8eb13f9df5d7ab925f (opens in a new tab)
- https://git.kernel.org/stable/c/ae3e53fe3c1241855e3a88f74877738349948c78 (opens in a new tab)
- https://git.kernel.org/stable/c/ad72e2566643fff7f01666d845fb026898155e1f (opens in a new tab)
- https://git.kernel.org/stable/c/9a17b0e053197a6a42cdc75e75a35b17aa662088 (opens in a new tab)
- https://git.kernel.org/stable/c/5a88f78df753993469dab4d1831f8fb4256a9468 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86792 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97938)Record last updated .