# CVE-2025-68370: coresight: tmc: add the handle of the event to the path

> A missing event handle in the Linux kernel Coresight TMC driver causes a null pointer dereference and kernel oops during performance recording.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-68370, DEBIAN-CVE-2025-68370, GHSA-3crq-qf2v-x94m, UBUNTU-CVE-2025-68370

## What is CVE-2025-68370?

CVE-2025-68370 is a high-severity vulnerability in Linux, published on 24 Dec 2025. 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: tmc: add the handle of the event to the path

The handle is essential for retrieving the AUX_EVENT of each CPU and is
required in perf mode. It has been added to the coresight_path so that
dependent devices can access it from the path when needed.

The existing bug can be reproduced with:
perf record -e cs_etm//k -C 0-9 dd if=/dev/zero of=/dev/null

Showing an oops as follows:
Unable to handle kernel paging request at virtual address 000f6e84934ed19e

Call trace:
 tmc_etr_get_buffer+0x30/0x80 [coresight_tmc] (P)
 catu_enable_hw+0xbc/0x3d0 [coresight_catu]
 catu_enable+0x70/0xe0 [coresight_catu]
 coresight_enable_path+0xb0/0x258 [coresight]

## Which versions are affected by CVE-2025-68370?


## How do I fix CVE-2025-68370?

Apply the vendor's patch.

## Is CVE-2025-68370 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68370 and fix it if it is affected.

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

## Sources

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

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