CVE-2026-98790 json
perf: Fix race between perf_event_exit_task() and perf_pending_task()
published 24d ago modified 12d ago also EUVD-2026-103875
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
perf: Fix race between perf_event_exit_task() and perf_pending_task()
A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec().
During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current).
Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.10-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98790
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-43.43
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1017.18
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1017.19
- linux-gke Ubuntu 24.04 LTS 6.8.0-1068.77
- linux-gke Ubuntu 26.04 LTS 7.0.0-1010.11
ubuntu advisories UBUNTU-CVE-2026-98790
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-109401
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/6e454fbe3e646d119ab75e907035950e0e857c09 commit
- git.kernel.org/stable/c/a8a6fe5601fa2d2c0fbfb3e531a1063f73c1eae3 commit
- git.kernel.org/stable/c/655acfa713bce9ae9c81a654459890c2f58cb4e8 commit
- git.kernel.org/stable/c/672b8a9ce8f51b991481dfde26fba5cc4340a91a commit
- git.kernel.org/stable/c/524063fea29f8a841e49927ea7a8085194ad3ec2 commit
- git.kernel.org/stable/c/81e61e3f8befa1bae3ec8e779d8ada5e5e362c21 commit
- git.kernel.org/stable/c/ffb684f2aa141eeb0caa6308422e7e05d1ded7c4 commit
Is CVE-2026-98790 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98790 updated cvss 4.7
kernel: perf: Fix race between perf_event_exit_task() and perf_pending_task()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/6e454fbe3e646d119ab75e907035950e0e857c09
- git.kernel.org /stable/c/a8a6fe5601fa2d2c0fbfb3e531a1063f73c1eae3
- git.kernel.org /stable/c/655acfa713bce9ae9c81a654459890c2f58cb4e8
- git.kernel.org /stable/c/672b8a9ce8f51b991481dfde26fba5cc4340a91a
- git.kernel.org /stable/c/524063fea29f8a841e49927ea7a8085194ad3ec2
- git.kernel.org /stable/c/81e61e3f8befa1bae3ec8e779d8ada5e5e362c21
- git.kernel.org /stable/c/ffb684f2aa141eeb0caa6308422e7e05d1ded7c4
Sources
- CVE List CVE-2026-98790
- NVD CVE-2026-98790
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.