procfs: fix missing RCU protection when reading real_parent in do_task_stat()
Summary
| CVE | CVE-2026-46259 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-03 18:16:26 UTC |
| Updated | 2026-06-03 18:16:26 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e fefa0fcd78be465b7ad4c497fa6ec90d64194c04 git |
Not specified |
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e c93a33f28f915d446eea6fb3f0e1def0b3af1982 git |
Not specified |
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e 1c8dc5b5517546c68ffae40b948336122bb61306 git |
Not specified |
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e 0e64bd46a04a4fd61279aca9f53a664e9e5f7e7e git |
Not specified |
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e 73ec7c96601d61d52310c659145bb06d933a0fa6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e 4f9ae386861e280b7631ca252f798d25575627ee git |
Not specified |
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e dd8b13cb4ff1a4545a214ed897fdf2bc341155b6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 06fffb1267c9d986687b69d74a46ee332a50575e 76149d53502cf17ef3ae454ff384551236fba867 git |
Not specified |
| CNA |
Linux |
Linux |
affected 2.6.26 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 2.6.26 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.252 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.202 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.165 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.128 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.75 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.14 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.4 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/fefa0fcd78be465b7ad4c497fa6ec90d64194c04 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4f9ae386861e280b7631ca252f798d25575627ee |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/76149d53502cf17ef3ae454ff384551236fba867 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1c8dc5b5517546c68ffae40b948336122bb61306 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0e64bd46a04a4fd61279aca9f53a664e9e5f7e7e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/dd8b13cb4ff1a4545a214ed897fdf2bc341155b6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c93a33f28f915d446eea6fb3f0e1def0b3af1982 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/73ec7c96601d61d52310c659145bb06d933a0fa6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.