perf/x86/intel: Prevent drain_pebs() reentry
CVE-2026-97960 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-97960, released October 2, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Prevent drain_pebs() reentry The PEBS buffer is shared by all events on a CPU, so drain_pebs() must not be reentered. If so, one instance may observe stale buffer state and potentially access out-of-bound memory. Most invocations happen in NMI context, which naturally prevents reentry. However, drain_pebs() is also reachable from process context via intel_pmu_drain_pebs_buffer(). In those paths, the PMU is often already disabled, but not guaranteed. For example, __intel_pmu_pebs_disable() only disables the target counter, so other active counters can still raise a PMI and interrupt an in-flight drain_pebs(). Here is an example, __perf_addr_filters_adjust() perf_event_stop() __perf_event_stop() x86_pmu_stop() (event->pmu->stop) intel_pmu_disable_event() intel_pmu_pebs_disable() __intel_pmu_pebs_disable() intel_pmu_drain_large_pebs() intel_pmu_drain_pebs_buffer() Introduce __intel_pmu_quiesce() and __intel_pmu_resume() helpers and use them in intel_pmu_drain_large_pebs() to disable the full PMU around the intel_pmu_drain_pebs_buffer() call, preventing reentry. Also add a warning in intel_pmu_drain_pebs_buffer() when the full PMU is not disabled.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.18 · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| bpftool6.18-debuginfo · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel-livepatch-6.18.54-121.166 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18 · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-debuginfo · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-debuginfo-common-aarch64 · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-debuginfo-common-x86_64 · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-devel · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-headers · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-modules-extra · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-modules-extra-common · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-tools · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-tools-debuginfo · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| kernel6.18-tools-devel · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.115-2 | DEBIAN-CVE-2026-97960 | Oct 2, 2026 |
| linux · Debian 14 | 7.2.7-1 | DEBIAN-CVE-2026-97960 | Oct 2, 2026 |
| microvm-kernel6.18 · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| perf6.18 · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| perf6.18-debuginfo · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| python3-perf6.18 · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
| python3-perf6.18-debuginfo · amzn 2023 | 1:6.18.54-121.166.amzn2023 | ALAS2023-2026-3192 | Nov 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.