IBM PowerVM gain access
An internally discovered vulnerability in PowerVM on IBM Power9 and Power10 systems could allow an attacker with privileged user access to a logical partition to perform an undetected violation of the isolation between logical partitions which could lead to data leakage or the execution of arbitrary code in other logical partitions on the same physical server. IBM X-Force ID: 252706.
- Published
- May 17, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · ibm
- 9.3
- 0.5 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | powervm hypervisor | cpe:2.3:o:ibm:powervm_hypervisor |
| ibm | power system e950 | cpe:2.3:h:ibm:power_system_e950 |
| ibm | power system e980 | cpe:2.3:h:ibm:power_system_e980 |
| ibm | power system h922 | cpe:2.3:h:ibm:power_system_h922 |
| ibm | power system h924 | cpe:2.3:h:ibm:power_system_h924 |
| ibm | power system l922 | cpe:2.3:h:ibm:power_system_l922 |
| ibm | power system s914 | cpe:2.3:h:ibm:power_system_s914 |
| ibm | power system s922 | cpe:2.3:h:ibm:power_system_s922 |
| ibm | power system s924 | cpe:2.3:h:ibm:power_system_s924 |
| ibm | power system e1080 | cpe:2.3:h:ibm:power_system_e1080 |
| ibm | power system e1050 | cpe:2.3:h:ibm:power_system_e1050 |
| ibm | power system l1022 | cpe:2.3:h:ibm:power_system_l1022 |
and 5 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm powervm hypervisorfw950 and later · before fw950.71
- ibm powervm hypervisorfw1010.00 and later · before fw1010.51
- ibm powervm hypervisorfw1030.00 and later · before fw1030.11
- ibm powervm hypervisorfw1020.00 and later · before fw1020.31
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM PowerVM Hypervisor
- FW950.00 and later · up to and including FW950.70affected · semver
- FW1010.00 and later · up to and including FW1010.50affected · semver
- FW1020.00 and later · up to and including FW1020.30affected · semver
- FW1030.00 and later · up to and including FW1030.10affected · semver
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34331IBM Power FW security bypass39Monitor
- CVE-2021-38917IBM PowerVM Hypervisor FW860, FW940, and FW950 could allow an attacker that gains service access to the FSP can read and write arbitrary hos36Monitor
- CVE-2023-30440IBM PowerVM Hypervisor denial of service31Monitor
- CVE-2023-25683IBM PowerVM Hypervisor information disclosure30Monitor
- CVE-2021-38918IBM PowerVM Hypervisor FW860, FW940, FW950, and FW1010, through a specific sequence of VM management operations could lead to a violation of30Monitor
- CVE-2022-22445An attacker that gains service access to the FSP (POWER9 only) or gains admin authority to a partition can compromise partition firmware.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.