# CVE-2026-97499: coresight: perf: Retrieve path and source from event data

> A race condition in Linux kernel Coresight ETM perf callbacks can lead to instability or crashes during device registration and unregistration.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** AZL-103988, BELL-CVE-2026-97499, DEBIAN-CVE-2026-97499, GHSA-656w-9gg9-4hhp, UBUNTU-CVE-2026-97499

## What is CVE-2026-97499?

CVE-2026-97499 is a vulnerability in Linux, published on 24 Sep 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:

coresight: perf: Retrieve path and source from event data

ETM perf callbacks currently use the per-CPU csdev_src pointer, which
can race with updates during device registration and unregistration.

The AUX setup already builds and stores the path in the event data.
Use this path to retrieve the source instead of csdev_src to avoid
the race.

Export coresight_get_source() and add etm_event_get_ctxt_path() to
retrieve the context's path and its source with READ_ONCE() /
WRITE_ONCE() accessors. Give the comments to explain why this
approach is safe when pause or resume callbacks preempt the disable
callback (e.g. via NMI).

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


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

Apply the vendor's patch.

## Is CVE-2026-97499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97499 is a vulnerability in Linux, published on 24 Sep 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-97499 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-97499/ (Markdown: https://insights.sbomify.com/CVE-2026-97499/index.md)
```

## Sources

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

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