Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31528: perf: Make sure to use pmu_ctx->pmu for groups

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 35f7914e54fe7f13654c22ee045b05e4b6d8062b, 3a696e84a8b1fafdd774bb30d62919faf844d9e4, 4b9ce671960627b2505b3f64742544ae9801df97; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2.

Low priority for now. Upgrade to Linux Linux 35f7914e54fe7f13654c22ee045b05e4b6d8062b, 3a696e84a8b1fafdd774bb30d62919faf844d9e4, 4b9ce671960627b2505b3f64742544ae9801df97; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Apr 22, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31528

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.2affected
    • bd27568117664b8b3e259721393df420ed51f57b and later · before 656f35b463995bee024d948440128230aacd81e1affected · git
    • bd27568117664b8b3e259721393df420ed51f57b and later · before 3a696e84a8b1fafdd774bb30d62919faf844d9e4affected · git
    • bd27568117664b8b3e259721393df420ed51f57b and later · before 35f7914e54fe7f13654c22ee045b05e4b6d8062baffected · git
    • bd27568117664b8b3e259721393df420ed51f57b and later · before 4c759446046500a1a6785b25725725c3ff087aceaffected · git
    • bd27568117664b8b3e259721393df420ed51f57b and later · before 4b9ce671960627b2505b3f64742544ae9801df97affected · git
    • before 6.2not affected · semver
    • 6.6.131 and later · up to and including 6.6.*not affected · semver
    • 6.12.80 and later · up to and including 6.12.*not affected · semver
    • 6.18.21 and later · up to and including 6.18.*not affected · semver
Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.2 and later · before 6.6.131
  • linux linux kernel6.7 and later · before 6.12.80
  • linux linux kernel6.13 and later · before 6.18.21
  • linux linux kernel6.19 and later · before 6.19.11
  • linux linux kernel7.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.11-16.19.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31526Apr 22, 2026 · bpf: Fix exception exit lock checking for subprogs
    22Monitor
  • ← EarlierCVE-2026-31527Apr 22, 2026 · driver core: platform: use generic driver_override infrastructure
    31Monitor
  • Later →CVE-2026-31529Apr 22, 2026 · cxl/region: Fix leakage in __construct_region()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux35f7914e54fe7f13654c22ee045b05e4b6d8062bVendor (CNA)
Linux Linux3a696e84a8b1fafdd774bb30d62919faf844d9e4Vendor (CNA)
Linux Linux4b9ce671960627b2505b3f64742544ae9801df97Vendor (CNA)
Linux Linux4c759446046500a1a6785b25725725c3ff087aceVendor (CNA)
Linux Linux656f35b463995bee024d948440128230aacd81e1Vendor (CNA)
azl3 kernel 6.6.130.1-3 on Azure Linux 3.06.6.134.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.12.85-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records