SECUFOCUSNOW
Home›CVE index›CVE-2026-46259
Review reviewHigh

CVE-2026-46259

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.12%
2.17% percentile
CISA KEV
Not listed
Published
2026.06.04
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.12%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 06fffb1267c9d986687b69d74a46ee332a50575e < fefa0fcd78be465b7ad4c497fa6ec90d64194c04, >= 06fffb1267c9d986687b69d74a46ee332a50575e < c93a33f28f915d446eea6fb3f0e1def0b3af1982, >= 06fffb1267c9d986687b69d74a46ee332a50575e < 1c8dc5b5517546c68ffae40b948336122bb61306, >= 06fffb1267c9d986687b69d74a46ee332a50575e < 0e64bd46a04a4fd61279aca9f53a664e9e5f7e7e, >= 06fffb1267c9d986687b69d74a46ee332a50575e < 73ec7c96601d61d52310c659145bb06d933a0fa6, >= 06fffb1267c9d986687b69d74a46ee332a50575e < 4f9ae386861e280b7631ca252f798d25575627ee, >= 06fffb1267c9d986687b69d74a46ee332a50575e < dd8b13cb4ff1a4545a214ed897fdf2bc341155b6, >= 06fffb1267c9d986687b69d74a46ee332a50575e < 76149d53502cf17ef3ae454ff384551236fba867, >= 2.6.26, >= 2.6.26 < 5.10.252, >= 5.11 < 5.15.202, >= 5.16 < 6.1.165, >= 6.2 < 6.6.128, >= 6.7 < 6.12.75, >= 6.13 < 6.18.14, >= 6.19 < 6.19.4
Fixed versions
5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.14, 6.19.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available