CVE-2026-93275
Received Received - Intake

Race Condition in Linux Kernel Intel PT

Vulnerability report for CVE-2026-93275, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/pt: Fix stop/start with no update If pt_event_stop() is called without PERF_EF_UPDATE flag, then perf_aux_output_end() is not called. A subsequent call to pt_event_start() will call perf_aux_output_begin() again which violates the rule against nesting and triggers a WARNING in perf_aux_output_begin(). Originally, pt_event_stop() was never called without PERF_EF_UPDATE, because the only code paths to do so are from event overflow, and Intel PT does not do that. However the introduction of group throttling by commit 9734e25fbf5ae ("perf: Fix the throttle logic for a group") meant that an Intel PT event could be throttled if it was part of a group. Throttling calls PMU ->stop() / ->start() callbacks without flags. An example is when AUX area sampling is used. The following commands hit the issue: echo 10000 > /proc/sys/kernel/perf_event_max_sample_rate perf record -F32000 --aux-sample -e '{intel_pt//u,cycles:u}' \ -- bash -c 'for i in `seq 1 100000` ; do true ; done' Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and perf_aux_output_end() are balanced. A cleared PERF_HES_UPTODATE bit indicates that an AUX output context is still open. Amend pt_event_start() / pt_event_stop() accordingly so that begin/end stay balanced: - In non-snapshot mode, stop() always closes the buffer (the buffer may have run out of space, and that accounting is done by the update), so a following start() opens a fresh one as before. - In snapshot/overwrite mode, stop() without PERF_EF_UPDATE leaves the buffer open so that pt_event_snapshot_aux() can still copy from it, and start() then only re-enables tracing instead of calling perf_aux_output_begin() again. Note that pt_event_del() calls pt_event_stop() with PERF_EF_UPDATE flag set (as is required by the documentation), so a final call to perf_aux_output_end() is assured.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-09-24
AI Q&A
2026-09-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a flaw in the Intel Processor Trace (Intel PT) performance monitoring unit (PMU) handling. When perf_event_stop() is called without the PERF_EF_UPDATE flag, it fails to call perf_aux_output_end(), which can lead to an imbalance in buffer management. Subsequent calls to perf_event_start() may then incorrectly call perf_aux_output_begin() again, violating nesting rules and triggering a warning.

Detection Guidance

The vulnerability can be detected by running specific perf commands that trigger the issue. Example commands include setting the max sample rate and recording with Intel PT and AUX sampling: echo 10000 > /proc/sys/kernel/perf_event_max_sample_rate; perf record -F32000 --aux-sample -e '{intel_pt//u,cycles:u}' -- bash -c 'for i in `seq 1 100000` ; do true ; done'

If the system triggers a WARNING in perf_aux_output_begin(), it indicates the vulnerability is present.

Impact Analysis

This vulnerability could cause system instability or crashes due to improper handling of Intel PT events, especially when AUX area sampling is used. It may lead to kernel warnings or errors during performance monitoring tasks involving Intel PT, potentially disrupting applications relying on precise event tracking.

Mitigation Strategies

Apply the Linux kernel patch that resolves the issue by ensuring perf_aux_output_begin() and perf_aux_output_end() are balanced. This involves updating the kernel to a version containing the fix for the Intel PT throttling logic.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-93275. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart