CVE-2026-46259
Received Received - Intake
Race Condition in Linux Kernel procfs Real-Parent Access

Publication date: 2026-06-03

Last updated on: 2026-06-03

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: procfs: fix missing RCU protection when reading real_parent in do_task_stat() When reading /proc/[pid]/stat, do_task_stat() accesses task->real_parent without proper RCU protection, which leads to: cpu 0 cpu 1 ----- ----- do_task_stat var = task->real_parent release_task call_rcu(delayed_put_task_struct) task_tgid_nr_ns(var) rcu_read_lock <--- Too late to protect task->real_parent! task_pid_ptr <--- UAF! rcu_read_unlock This patch uses task_ppid_nr_ns() instead of task_tgid_nr_ns() to add proper RCU protection for accessing task->real_parent.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-03
Last Modified
2026-06-03
Generated
2026-06-04
AI Q&A
2026-06-03
EPSS Evaluated
N/A
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 Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's procfs subsystem, specifically in the function do_task_stat() which reads the /proc/[pid]/stat file.

The issue is that do_task_stat() accesses the real_parent field of a task structure without proper Read-Copy-Update (RCU) protection. This improper handling can lead to a use-after-free (UAF) condition because the real_parent pointer might be freed or modified concurrently.

The vulnerability arises because the RCU read lock is applied too late, after accessing the real_parent pointer, which means the pointer can become invalid during the access.

The fix involves using task_ppid_nr_ns() instead of task_tgid_nr_ns() to ensure proper RCU protection when accessing real_parent, preventing the use-after-free scenario.


How can this vulnerability impact me? :

This vulnerability can lead to a use-after-free condition in the Linux kernel when reading process information from /proc/[pid]/stat.

A use-after-free can cause kernel memory corruption, which may result in system instability, crashes, or potentially allow an attacker to execute arbitrary code with kernel privileges.

Exploitation of this vulnerability could compromise the security and reliability of the affected system.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart