CVE-2026-31528perf: Make sure to use pmu_ctx->pmu for groups
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 44 days later
· 44 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected bd27568117664b8b3e259721393df420ed51f57b – < 656f35b463995bee024d948440128230aacd81e1
- affected bd27568117664b8b3e259721393df420ed51f57b – < 3a696e84a8b1fafdd774bb30d62919faf844d9e4
- affected bd27568117664b8b3e259721393df420ed51f57b – < 35f7914e54fe7f13654c22ee045b05e4b6d8062b
- affected bd27568117664b8b3e259721393df420ed51f57b – < 4c759446046500a1a6785b25725725c3ff087ace
- affected bd27568117664b8b3e259721393df420ed51f57b – < 4b9ce671960627b2505b3f64742544ae9801df97
- affected 6.2
- unaffected < 6.2
- unaffected 6.6.131 – ≤ 6.6.*
- unaffected 6.12.80 – ≤ 6.12.*
- unaffected 6.18.21 – ≤ 6.18.*
- unaffected 6.19.11 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References5
- https://git.kernel.org/stable/c/656f35b463995bee024d948440128230aacd81e1 (opens in a new tab)
- https://git.kernel.org/stable/c/3a696e84a8b1fafdd774bb30d62919faf844d9e4 (opens in a new tab)
- https://git.kernel.org/stable/c/35f7914e54fe7f13654c22ee045b05e4b6d8062b (opens in a new tab)
- https://git.kernel.org/stable/c/4c759446046500a1a6785b25725725c3ff087ace (opens in a new tab)
- https://git.kernel.org/stable/c/4b9ce671960627b2505b3f64742544ae9801df97 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-24921 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31528)Record last updated .