CVE-2026-97960

published 25 Sep 2026 · updated 17 Nov 2026

perf/x86/intel: Prevent drain_pebs() reentry

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c55599c0ec2aa020e41a0599c3044c56d8a2e7d9, Kernel 6.4, Kernel 9882068ed242fcd4743f53027e8c790e88dcafff and 7 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 <c55599c0ec2aa020e41a0599c3044c56d8a2e7d9, >=6.3.7 <6.4, >=b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 <9882068ed242fcd4743f53027e8c790e88dcafff, >=b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 <999e482fdf89400cc1ae937680fc05096b4c915b, >=b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 <a56c03a397e2cd0c4cf8da96dcd6214f7d0e7d8c, >=b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 <a5fe19dd8b3ed5fad6e5e0f0c58c7245043ee4af, =6.4, =a9165207b2b07415eeb01b3ac8bb84976ec96984c55599c0ec2aa020e41a0599c3044c56d8a2e7d9, 6.4, 9882068ed242fcd4743f53027e8c790e88dcafff, 999e482fdf89400cc1ae937680fc05096b4c915b, a56c03a397e2cd0c4cf8da96dcd6214f7d0e7d8c, a5fe19dd8b3ed5fad6e5e0f0c58c7245043ee4af
linux-kernel: Kernel>=6.19.0 <7.2.7, >=6.3.7 <6.4, >=6.4.0 <6.6.160, >=6.7.0 <6.12.114, >=6.13.0 <6.18.537.2.7, 6.4, 6.6.160, 6.12.114, 6.18.53

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97960 severity on Zeptric[![CVE-2026-97960](https://zeptric.io/badge/cve/CVE-2026-97960.svg)](https://zeptric.io/cve/CVE-2026-97960)