Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can crash certain IBM Power pSeries virtual machines when the vpa_pmu module is unloaded while related performance-monitoring events remain active. The supplied record rates it high severity. The demonstrated consequence is a kernel panic and service interruption; broader confidentiality or integrity impact is not established by the technical description.
Executive priority
Prioritize affected PowerPC virtualization hosts where local users or monitoring tooling can access these counters. Patch during the next expedited maintenance window, sooner for availability-critical shared systems. General Linux fleets outside the described PowerPC pSeries configuration are unlikely to be exposed based on the supplied evidence.
Technical view
The vpa_pmu performance-monitoring unit lacks module ownership introduced with commit 176cda0619b6. Consequently, active perf events do not retain the module reference, permitting unload and later NULL-pointer dereference during event scheduling. The fix assigns ownership so reference counting prevents unloading while events remain initialized.
Likely exposure
Exposure appears limited to affected Linux kernels on PowerPC pSeries LPAR systems using Book3s-HV nested APIv2 counters through vpa_pmu. Triggering requires local, low-privileged access and an active perf event during module unloading. The supplied version data references 6.13 through 6.15 but does not clearly define every affected range.
Exploitation context
The CVSS 3.1 score is 7.3 with local access, low privileges, low complexity, and user interaction. The supplied record is not in KEV, and no supplied source reports active exploitation. Evidence demonstrates a NULL-pointer dereference and kernel panic, primarily supporting local denial-of-service risk.
Researcher notes
The root cause is missing PMU module ownership and therefore incorrect lifetime management. The record supplies three stable-kernel fix commits but no complete branch-to-version mapping. Researchers should verify backports by commit content rather than version assumptions. The panic trace supports availability impact; the supplied description does not independently demonstrate data disclosure, modification, or remote reachability.
Mitigation direction
- Upgrade to a vendor-supported kernel containing the applicable referenced stable fix.
- Until updated, prevent vpa_pmu unloading while its perf events may remain active.
- Restrict local access and module-management privileges on affected PowerPC systems.
- Consult distribution guidance for exact fixed package versions and reboot requirements.
Validation and detection
- Inventory PowerPC pSeries LPAR hosts and record their running kernel versions.
- Determine whether vpa_pmu and Book3s-HV nested APIv2 performance counters are used.
- Confirm the installed kernel contains the applicable referenced stable fix.
- Safely verify that active vpa_pmu events retain module ownership and block unloading.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2025-22094 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H1.35.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/70ea7c5189197c6f5acdcfd8a2651be2c41e2faaCVE reference, Linux
- https://git.kernel.org/stable/c/6cf045b51e2c5721db7e55305f09ee32741e00f9CVE reference, Linux
- https://git.kernel.org/stable/c/ff99d5b6a246715f2257123cdf6c4a29cb33aa78CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.