# CVE-2026-98790: perf: Fix race between perf_event_exit_task() and perf_pending_task()

> A race condition in the Linux kernel perf subsystem can trigger a warning and potential instability during process execution, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109401, BELL-CVE-2026-98790, DEBIAN-CVE-2026-98790, GHSA-hx5j-phv4-m97w, UBUNTU-CVE-2026-98790

## What is CVE-2026-98790?

CVE-2026-98790 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-98790?


## How do I fix CVE-2026-98790?

Apply the vendor's patch.

## Is CVE-2026-98790 being exploited?

There is no known exploitation of CVE-2026-98790 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98790 and fix it if it is affected.

What it is: CVE-2026-98790 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98790 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98790/ (Markdown: https://insights.sbomify.com/CVE-2026-98790/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98790
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98790
- OSV: https://osv.dev/vulnerability/CVE-2026-98790

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98790/
Summaries are generated and may contain mistakes; the official description above is the record.