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.
Published: 2026-09-24
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Improper resource handling causing perf event warnings
Action: Patch
AI Analysis

Impact

The vulnerability is in the Linux kernel's perf subsystem for Intel PT. When pt_event_stop() is called without the PERF_EF_UPDATE flag, the routine that should close the auxiliary output context (perf_aux_output_end()) is not executed. A subsequent pt_event_start() then attempts to begin output again, violating the rule that auxiliary output blocks must not be nested. The kernel responds by issuing a warning in perf_aux_output_begin(). This logic defect allows the AUX output buffer to remain in an inconsistent state, potentially skewing collected performance data and creating a residual warning in the system logs.

Affected Systems

All Linux kernel builds that include the Intel PT event support are potentially affected, as the flaw arises in the perf/x86/intel/pt code paths that are enabled when group throttling is used. No specific kernel version is cited, so the issue applies to any kernel using this module until the mitigations are applied in newer releases.

Risk and Exploitability

The fault only produces a warning and does not provide any remote code execution path; the EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog. The CVSS score is 5.5. Consequently, the risk is considered low. However, exploitation would require a local or privileged process to trigger the problematic sequence of stop/start calls, making the most probable attack vector a local privileged user or system service that utilizes Intel PT with group throttling.

Generated by OpenCVE AI on October 1, 2026 at 20:10 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel patch that contains the fix for CVE-2026-93275 (or upgrade to a kernel release that includes the commit resolving the issue).
  • After updating, test perf recordings and confirm that no WARNING messages from perf_aux_output_begin() appear in dmesg or kernel logs.
  • Until a patch is applied, avoid using Intel PT events that involve group throttling or AUX area sampling; consider disabling or lowering perf_event_max_sample_rate to prevent triggering the stop/start sequence that triggers the warning.

Generated by OpenCVE AI on October 1, 2026 at 20:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6528-1 linux security update
History

Tue, 13 Oct 2026 13:30:00 +0000


Thu, 01 Oct 2026 18:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665
CWE-772

Tue, 29 Sep 2026 13:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-617
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Fri, 25 Sep 2026 08:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665
CWE-772

Thu, 24 Sep 2026 16:00:00 +0000

Type Values Removed Values Added
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.
Title perf/x86/intel/pt: Fix stop/start with no update
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-13T12:45:06.757Z

Reserved: 2026-09-17T16:02:15.098Z

Link: CVE-2026-93275

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T16:17:24.667

Modified: 2026-10-13T13:17:34.690

Link: CVE-2026-93275

cve-icon Redhat

Severity : Low

Publid Date: 2026-09-24T00:00:00Z

Links: CVE-2026-93275 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T20:15:12Z

Weaknesses