CVE-2026-97960
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
perf/x86/intel: Prevent drain_pebs() reentry
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 | affected | git | 9882068ed242fcd4743f53027e8c790e88dcafff | Unavailable | None listed |
| b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 | affected | git | 999e482fdf89400cc1ae937680fc05096b4c915b | Unavailable | None listed |
| b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 | affected | git | a5fe19dd8b3ed5fad6e5e0f0c58c7245043ee4af | Unavailable | None listed |
| b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 | affected | git | c55599c0ec2aa020e41a0599c3044c56d8a2e7d9 | Unavailable | None listed |
| b752ea0c28e3f7f0aaaad6abf84f735eebc37a60 | affected | git | a56c03a397e2cd0c4cf8da96dcd6214f7d0e7d8c | Unavailable | None listed |
| a9165207b2b07415eeb01b3ac8bb84976ec96984 | affected | git | Unavailable | Unavailable | None listed |
| 6.3.7 | affected | semver | 6.4 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 6.4 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 6.4 | Unavailable | None listed |
| 6.6.160 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.114 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.53 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.2.7 | unaffected | semver | Unavailable | 7.2.* | None listed |
| 7.3 | unaffected | original_commit_for_fix | Unavailable | * | None listed |