CVE-2026-97938
Received Received - Intake

Use-After-Free Race Condition in Linux Kernel reboot sysctl

Vulnerability report for CVE-2026-97938, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-25

Last updated on: 2026-10-03

Assigner: kernel.org

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)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-25
Last Modified
2026-10-03
Generated
2026-10-15
AI Q&A
2026-09-25
EPSS Evaluated
2026-10-14
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the Linux kernel where a pointer called cad_pid is accessed without proper protection. A race condition occurs when one process reads cad_pid while another process replaces it, leading to a freed memory access. The issue affects two functions: proc_do_cad_pid() and kill_cad_pid(), both of which dereference cad_pid without ensuring its validity during concurrent writes.

Detection Guidance

This vulnerability is specific to the Linux kernel and involves a use-after-free race condition in the cad_pid handling. Detection requires kernel-level analysis rather than network scanning. Check kernel logs for crashes or KASAN reports related to pid operations. Monitor sysctl operations on cad_pid and reboot-related syscalls.

Impact Analysis

An attacker with local access could exploit this to crash the system or potentially execute arbitrary code with kernel privileges. This could lead to denial of service, data corruption, or unauthorized system access. The vulnerability is reachable through user and PID namespaces, making it exploitable even by unprivileged users in certain configurations.

Compliance Impact

This vulnerability is a kernel-level use-after-free race condition in the Linux reboot sysctl handling. It does not directly relate to data protection, access controls, or audit logging required by GDPR or HIPAA. Compliance impact would depend on whether the affected system processes personal or health data, but the CVE itself does not specify such exposure.

Mitigation Strategies

Apply the kernel patch that fixes the cad_pid use-after-free race. Update to a Linux kernel version that includes the fix. If immediate patching is not possible, restrict access to sysctl operations and user namespaces to reduce attack surface until the patch is applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-97938. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart