CVE-2026-97499

Received Received - Intake

Race Condition in Linux Kernel Coresight ETM Perf

Publication date: 2026-09-24

Last updated on: 2026-09-28

Assigner: kernel.org

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).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-24

Last Modified

2026-09-28

Generated

2026-10-15

AI Q&A

2026-09-24

EPSS Evaluated

2026-10-14

NVD

CVE-2026-97499

EUVD

EUVD-2026-86097

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves a race condition in the Coresight performance monitoring subsystem. The issue occurs because ETM (Embedded Trace Macrocell) perf callbacks use a per-CPU pointer that can race with updates during device registration or unregistration. The fix involves using the path stored in event data to retrieve the source instead of the problematic pointer.

Detection Guidance

This vulnerability is specific to the Linux kernel's Coresight subsystem and does not have a direct network detection method. To detect it, check if your Linux kernel version is affected by verifying the presence of the vulnerable code paths related to ETM perf callbacks and csdev_src usage. Commands like uname -a can show your kernel version, and grep can search for Coresight-related modules in /proc/modules or /sys/bus/coresight/devices.

Impact Analysis

This vulnerability could lead to unpredictable behavior in systems using Coresight for performance monitoring. It may cause crashes, data corruption, or incorrect performance metrics due to the race condition in pointer access.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a race condition in the Linux kernel's Coresight performance monitoring subsystem, which could lead to data corruption or incorrect event handling but does not inherently violate data protection or privacy regulations.

Mitigation Strategies

Immediate mitigation involves updating your Linux kernel to a patched version that resolves this issue. Since the vulnerability is in the kernel, apply the latest stable kernel update from your distribution. If updating is not immediately possible, consider disabling the Coresight subsystem if it is not required, using kernel parameters or module blacklisting.

Hi! I’m here to help you understand CVE-2026-97499. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70