Loading vulnerability…
CVE-2026-46259 is a Linux kernel procfs race condition in do_task_stat() when servicing reads of /proc/[pid]/stat. The vulnerable code accesses task->real_parent without establishing RCU protection before the pointer is dereferenced through task_tgid_nr_ns(). If another CPU concurrently executes task teardown via release_task(), the parent task structure can be queued for reclamation, creating a window where do_task_stat() operates on a stale pointer. This results in a kernel use-after-free condition. The upstream fix changes the code path to use task_ppid_nr_ns(), which provides the required RCU protection around access to task->real_parent.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel procfs vulnerability caused by missing RCU protection when reading real_parent in do_task_stat().
A Linux kernel procfs vulnerability caused by missing RCU protection when reading real_parent in do_task_stat().
A Linux kernel procfs vulnerability caused by missing RCU protection when reading real_parent in do_task_stat().
A Linux kernel procfs vulnerability in do_task_stat() where task->real_parent is accessed without proper RCU protection while reading /proc/[pid]/stat, leading to a potential use-after-free condition.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.