CVE-2026-23159 Details
Description
In the Linux kernel, the following vulnerability has been resolved: perf: sched: Fix perf crash with new is_user_task() helper In order to do a user space stacktrace the current task needs to be a user task that has executed in user space. It use to be possible to test if a task is a user task or not by simply checking the task_struct mm field. If it was non NULL, it was a user task and if not it was a kernel task. But things have changed over time, and some kernel tasks now have their own mm field. An idea was made to instead test PF_KTHREAD and two functions were used to wrap this check in case it became more complex to test if a task was a user task or not[1]. But this was rejected and the C code simply checked the PF_KTHREAD directly. It was later found that not all kernel threads set PF_KTHREAD. The io-uring helpers instead set PF_USER_WORKER and this needed to be added as well. But checking the flags is still not enough. There's a very small window when a task exits that it frees its mm field and it is set back to NULL. If perf were to trigger at this moment, the flags test would say its a user space task but when perf would read the mm field it would crash with at NULL pointer dereference. Now there are flags that can be used to test if a task is exiting, but they are set in areas that perf may still want to profile the user space task (to see where it exited). The only real test is to check both the flags and the mm field. Instead of making this modification in every location, create a new is_user_task() helper function that does all the tests needed to know if it is safe to read the user space memory or not. [1] https://lore.kernel.org/all/[email protected]/
A vulnerability in the Linux kernel's perf scheduler component can lead to a crash due to improper handling of user tasks. The issue arises from changes in how the kernel manages task memory, allowing some kernel tasks to have their own memory fields. This modification disrupts the previous method of identifying user tasks, which relied on checking the memory field for null values. The current approach, which tests task flags, is insufficient as it may incorrectly classify a task as a user task during a brief period of transition, leading to a null pointer dereference when the perf subsystem attempts to access user space memory. To address this, a new helper function has been introduced to accurately determine if a task is a user task, ensuring safe access to user space memory and preventing crashes.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/5aac392fcd3d981d7997f1a0766829e1afdeac2e | kernel.org | Patch |
| https://git.kernel.org/stable/c/76ed27608f7dd235b727ebbb12163438c2fbb617 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a28fce0365e1cb9cb8c04c893b9334e5ca9d9f1c | kernel.org | Patch |
| https://git.kernel.org/stable/c/d84a4836dc246b7dc244e46a08ff992956b68db0 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6.116, < 6.6.123 >= 6.12.57, < 6.12.69 >= 6.17.7, < 6.18.9 6.19 rc1 6.19 rc2 6.19 rc3 6.19 rc4 6.19 rc5 6.19 rc6 6.19 rc7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Mar 18, 2026 | Initial Analysis | [email protected] |
| Feb 14, 2026 | New CVE Received | kernel.org |