UBUNTU-CVE-2026-23159
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]/
02 / AFFECTED SOFTWARE
Affected packages
12 explicit affected versions
11 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
11 explicit affected versions
19 explicit affected versions
6 explicit affected versions
24 explicit affected versions
10 explicit affected versions
34 explicit affected versions
26 explicit affected versions
7 explicit affected versions
38 explicit affected versions
13 explicit affected versions
41 explicit affected versions
35 explicit affected versions
18 explicit affected versions
43 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
49 explicit affected versions
1 explicit affected versions
21 explicit affected versions
9 explicit affected versions
16 explicit affected versions
10 explicit affected versions
20 explicit affected versions
45 explicit affected versions
8 explicit affected versions
7 explicit affected versions
7 explicit affected versions
12 explicit affected versions
14 explicit affected versions
10 explicit affected versions
12 explicit affected versions
1 explicit affected versions
7 explicit affected versions
13 explicit affected versions
12 explicit affected versions
8 explicit affected versions
12 explicit affected versions
38 explicit affected versions
17 explicit affected versions
25 explicit affected versions
31 explicit affected versions
10 explicit affected versions
37 explicit affected versions
9 explicit affected versions
13 explicit affected versions
37 explicit affected versions
10 explicit affected versions
26 explicit affected versions
8 explicit affected versions
13 explicit affected versions
29 explicit affected versions
13 explicit affected versions
12 explicit affected versions
38 explicit affected versions
38 explicit affected versions
8 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
17 explicit affected versions
16 explicit affected versions
11 explicit affected versions
12 explicit affected versions
9 explicit affected versions
7 explicit affected versions
12 explicit affected versions
8 explicit affected versions
16 explicit affected versions
10 explicit affected versions
26 explicit affected versions
35 explicit affected versions
33 explicit affected versions
8 explicit affected versions
10 explicit affected versions
44 explicit affected versions
10 explicit affected versions
13 explicit affected versions
43 explicit affected versions
16 explicit affected versions
47 explicit affected versions
3 explicit affected versions
7 explicit affected versions
15 explicit affected versions
51 explicit affected versions
16 explicit affected versions
18 explicit affected versions
39 explicit affected versions
12 explicit affected versions
7 explicit affected versions
27 explicit affected versions
40 explicit affected versions
8 explicit affected versions
5 explicit affected versions
8 explicit affected versions
10 explicit affected versions
7 explicit affected versions
43 explicit affected versions
13 explicit affected versions
13 explicit affected versions
7 explicit affected versions
9 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
37 explicit affected versions
48 explicit affected versions
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
17 explicit affected versions
11 explicit affected versions
36 explicit affected versions
17 explicit affected versions
14 explicit affected versions
8 explicit affected versions
7 explicit affected versions
4 explicit affected versions
8 explicit affected versions
1 explicit affected versions
13 explicit affected versions
43 explicit affected versions
14 explicit affected versions
10 explicit affected versions
8 explicit affected versions
42 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
14 explicit affected versions
11 explicit affected versions
1 explicit affected versions
16 explicit affected versions
37 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
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]/
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/76ed27608f7dd235b727ebbb12163438c2fbb617
- https://git.kernel.org/stable/c/5aac392fcd3d981d7997f1a0766829e1afdeac2e
- https://git.kernel.org/stable/c/76ed27608f7dd235b727ebbb12163438c2fbb617
- https://git.kernel.org/stable/c/a28fce0365e1cb9cb8c04c893b9334e5ca9d9f1c
- https://git.kernel.org/stable/c/d84a4836dc246b7dc244e46a08ff992956b68db0
- https://ubuntu.com/security/CVE-2026-23159
- https://ubuntu.com/security/notices/USN-8278-1
- https://ubuntu.com/security/notices/USN-8278-2
- https://ubuntu.com/security/notices/USN-8289-1
- https://ubuntu.com/security/notices/USN-8289-2
- https://ubuntu.com/security/notices/USN-8296-1
- https://ubuntu.com/security/notices/USN-8296-2
- https://ubuntu.com/security/notices/USN-8393-1
- https://ubuntu.com/security/notices/USN-8440-1
- https://ubuntu.com/security/notices/USN-8499-1
- https://ubuntu.com/security/notices/USN-8570-1
- https://ubuntu.com/security/notices/USN-8570-2
- https://ubuntu.com/security/notices/USN-8594-1
- https://ubuntu.com/security/notices/USN-8604-1
- https://ubuntu.com/security/notices/USN-8605-1
- https://www.cve.org/CVERecord?id=CVE-2026-23159