CVE-2026-97960perf/x86/intel: Prevent drain_pebs() reentry
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 26 days later
· 26 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 – < 9882068ed242fcd4743f53027e8c790e88dcafff
- affected b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 – < 999e482fdf89400cc1ae937680fc05096b4c915b
- affected b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 – < a5fe19dd8b3ed5fad6e5e0f0c58c7245043ee4af
- affected b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 – < c55599c0ec2aa020e41a0599c3044c56d8a2e7d9
- affected b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 – < a56c03a397e2cd0c4cf8da96dcd6214f7d0e7d8c
- affected a9165207b2b07415eeb01b3ac8bb84976ec96984
- affected 6.3.7 – < 6.4
- affected 6.4
- unaffected < 6.4
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/9882068ed242fcd4743f53027e8c790e88dcafff (opens in a new tab)
- https://git.kernel.org/stable/c/999e482fdf89400cc1ae937680fc05096b4c915b (opens in a new tab)
- https://git.kernel.org/stable/c/a5fe19dd8b3ed5fad6e5e0f0c58c7245043ee4af (opens in a new tab)
- https://git.kernel.org/stable/c/c55599c0ec2aa020e41a0599c3044c56d8a2e7d9 (opens in a new tab)
- https://git.kernel.org/stable/c/a56c03a397e2cd0c4cf8da96dcd6214f7d0e7d8c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86814 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97960)Record last updated .