CVE-2026-31528
CVE-2026-31528
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.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| linux_kernel linux |
≥ 6.2; < 6.6.131 (affected, custom) | NVD |
| linux_kernel linux |
≥ 6.7; < 6.12.80 (affected, custom) | NVD |
| linux_kernel linux |
≥ 6.13; < 6.18.21 (affected, custom) | NVD |
| linux_kernel linux |
≥ 6.19; < 6.19.11 (affected, custom) | NVD |
| linux_kernel linux |
7.0 (affected, custom) | NVD |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
NVD applicability configurations (1)
These expressions retain AND/OR operators, negation, and required environmental products. A listed product is not sufficient to establish exposure when additional conditions apply.
[
{
"negate": false,
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.131",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.80",
"versionStartIncluding": "6.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.21",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.11",
"versionStartIncluding": "6.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
]CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/35f7914e54fe7f13654c22ee045b05e4b6d8062b416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
- https://git.kernel.org/stable/c/3a696e84a8b1fafdd774bb30d62919faf844d9e4416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
- https://git.kernel.org/stable/c/4b9ce671960627b2505b3f64742544ae9801df97416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
- https://git.kernel.org/stable/c/4c759446046500a1a6785b25725725c3ff087ace416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
- https://git.kernel.org/stable/c/656f35b463995bee024d948440128230aacd81e1416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.