CVEvulnerability
CVE-2026-31528
7.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2026-04-22
- Last modified
- 2026-10-19
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-125, CWE-787
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.
Affected configurations
• linux linux kernel (>= 6.2 < 6.6.131)
• linux linux kernel (>= 6.7 < 6.12.80)
• linux linux kernel (>= 6.13 < 6.18.21)
• linux linux kernel (>= 6.19 < 6.19.11)
• linux linux kernel 7.0
Related
References
- https://git.kernel.org/stable/c/35f7914e54fe7f13654c22ee045b05e4b6d8062b Patch
- https://git.kernel.org/stable/c/3a696e84a8b1fafdd774bb30d62919faf844d9e4 Patch
- https://git.kernel.org/stable/c/4b9ce671960627b2505b3f64742544ae9801df97 Patch
- https://git.kernel.org/stable/c/4c759446046500a1a6785b25725725c3ff087ace Patch
- https://git.kernel.org/stable/c/656f35b463995bee024d948440128230aacd81e1 Patch