Answer in brief
CVE-2026-31528 records a High severity (CVSS 7.8) vulnerability in perf: Make sure to use pmu_ctx->pmu for groups. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bd27568117664b8b3e259721393df420ed51f57b <656f35b463995bee024d948440128230aacd81e1 || >=bd27568117664b8b3e259721393df420ed51f57b <3a696e84a8b1fafdd774bb30d62919faf844d9e4 || >=bd27568117664b8b3e259721393df420ed51f57b <35f7914e54fe7f13654c22ee045b05e4b6d8062b || >=bd27568117664b8b3e259721393df420ed51f57b <4c759446046500a1a6785b25725725c3ff087ace || >=bd27568117664b8b3e259721393df420ed51f57b <4b9ce671960627b2505b3f64742544ae9801df97 | 656f35b463995bee024d948440128230aacd81e1, 3a696e84a8b1fafdd774bb30d62919faf844d9e4, 35f7914e54fe7f13654c22ee045b05e4b6d8062b, 4c759446046500a1a6785b25725725c3ff087ace, 4b9ce671960627b2505b3f64742544ae9801df97 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Apr 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 16, 2026
In the Linux kernel, the following vulnerability has been resolved: perf: Make sure to use pmu_ctx->pmu for groups Oliver reported that x86_pmu_del() ended up doing an out-of-bound memory access when group_sched_in() fails and needs to roll back. This *should* be handled by the transaction callbacks, but he found that when the group leader is a software event, the transaction handlers of the wrong PMU are used. Despite the move_group case in perf_event_open() and group_sched_in() using pmu_ctx->pmu. Turns out, inherit uses event->pmu to clone the events, effectively undoing the move_group case for all inherited contexts. Fix this by also making inherit use pmu_ctx->pmu, ensuring all inherited counters end up in the same pmu context. Similarly, __perf_event_read() should use equally use pmu_ctx->pmu for the group case.
Quoted source text, attributed separately from HOL analysis.