Back to CVE records
Medium 5.5Published Feb 14, 2026

CVE-2026-23159perf: sched: Fix perf crash with new is_user_task() helper

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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/20250425204120.639530125@goodmis.org/

CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Analyzed
Record last updated
May 23, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 34b5aba8511a12fb2e9bd3124835cb4087187dac before d84a4836dc246b7dc244e46a08ff992956b68db0; 8d79f96e477c4b8e3fca2efb36b269d8960a2285 builds before 5aac392fcd3d981d7997f1a0766829e1afdeac2e; from 90942f9fac05702065ff82ed0bade0d08168d4ea before a28fce0365e1cb9cb8c04c893b9334e5ca9d9f1c; 90942f9fac05702065ff82ed0bade0d08168d4ea builds before 76ed27608f7dd235b727ebbb12163438c2fbb617; 5050083e1a2f3e5e29cee0205c40e5864b52601d; from 6.6.116 before 6.6.123; from 6.12.57 before 6.12.69; from 6.17.7 before 6.18
CNA record
linux linux_kernel
linux:linux_kernel
from 6.6.116 before 6.6.123; from 6.12.57 before 6.12.69; from 6.17.7 before 6.18.9; 6.19; 6.19; 6.19; 6.19; 6.19; and 2 more ranges
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.