Vulnerability · Published Feb 14, 2026 · Assigned by Linux

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

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 97.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

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

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.69-1DEBIAN-CVE-2026-23159
Debian:14linux6.18.9-1DEBIAN-CVE-2026-23159
Ubuntu:24.04:LTSlinux6.8.0-117.117UBUNTU-CVE-2026-23159
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-aws6.8.0-1055.58UBUNTU-CVE-2026-23159
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1057.60~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-azure6.8.0-1056.62UBUNTU-CVE-2026-23159
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1021.21~24.04.1UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-gcp6.8.0-1058.61UBUNTU-CVE-2026-23159
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1021.24~24.04.1UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-gke6.8.0-1054.60UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1041.44UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-41.41~24.04.1UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-124.124~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-ibm6.8.0-1055.56UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1055.56~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-117.117.1UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-117.117.1~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1054.57UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1031.31UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1054.57.1UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1024.24UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1030.30UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-oracle6.8.0-1054.55UBUNTU-CVE-2026-23159
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1019.19~24.04.3UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1054.55~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-raspi6.8.0-1056.60UBUNTU-CVE-2026-23159
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-23159
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-23159
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-117.117~22.04.1UBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-23159
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-23159
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1032.33UBUNTU-CVE-2026-23159

Affected products (as reported)

VendorProductVersions
Linux Linux 34b5aba8511a12fb2e9bd3124835cb4087187dac – before d84a4836dc246b7dc244e46a08ff992956b68db08d79f96e477c4b8e3fca2efb36b269d8960a2285 – before 5aac392fcd3d981d7997f1a0766829e1afdeac2e90942f9fac05702065ff82ed0bade0d08168d4ea – before a28fce0365e1cb9cb8c04c893b9334e5ca9d9f1c90942f9fac05702065ff82ed0bade0d08168d4ea – before 76ed27608f7dd235b727ebbb12163438c2fbb6175050083e1a2f3e5e29cee0205c40e5864b52601d6.6.116 – before 6.6.1236.12.57 – before 6.12.696.17.7 – before 6.18
Linux Linux 6.18

References