perf: Make sure to use pmu_ctx->pmu for groups
Summary
| CVE | CVE-2026-31528 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-22 14:16:53 UTC |
| Updated | 2026-04-22 14:16:53 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected bd27568117664b8b3e259721393df420ed51f57b 656f35b463995bee024d948440128230aacd81e1 git |
Not specified |
| CNA |
Linux |
Linux |
affected bd27568117664b8b3e259721393df420ed51f57b 3a696e84a8b1fafdd774bb30d62919faf844d9e4 git |
Not specified |
| CNA |
Linux |
Linux |
affected bd27568117664b8b3e259721393df420ed51f57b 35f7914e54fe7f13654c22ee045b05e4b6d8062b git |
Not specified |
| CNA |
Linux |
Linux |
affected bd27568117664b8b3e259721393df420ed51f57b 4c759446046500a1a6785b25725725c3ff087ace git |
Not specified |
| CNA |
Linux |
Linux |
affected bd27568117664b8b3e259721393df420ed51f57b 4b9ce671960627b2505b3f64742544ae9801df97 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.2 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.2 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.131 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.80 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.21 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.11 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/4c759446046500a1a6785b25725725c3ff087ace |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/656f35b463995bee024d948440128230aacd81e1 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4b9ce671960627b2505b3f64742544ae9801df97 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3a696e84a8b1fafdd774bb30d62919faf844d9e4 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/35f7914e54fe7f13654c22ee045b05e4b6d8062b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.