Security readout for executives and security teams
Plain-English summary
A malicious or compromised administrator inside an affected IBM PowerVM guest could crash the entire physical platform or corrupt hypervisor and partition memory. One incident may terminate every hosted partition; repeated attacks could sustain the outage. Confidentiality impact is not identified, but integrity and availability risks are high.
Executive priority
Treat as a high-priority infrastructure remediation. Prioritize systems hosting critical or numerous partitions because one privileged guest compromise could disrupt the whole platform. Schedule IBM-prescribed firmware maintenance promptly, while applying stricter guest-root controls and confirming platform-wide recovery readiness.
Technical view
An integer overflow in the PowerVM hypervisor call interface allows a root user in a guest partition to submit a crafted call that injects excessive data into hypervisor or partition memory. Outcomes include memory corruption or a platform-wide crash requiring re-IPL. The hypervisor restarts automatically, but exploitation can cross the guest boundary and affect the managed system.
Likely exposure
Exposure is limited to IBM PowerVM systems running FW1120.00, FW1110.00–FW1110.30, FW1060.00–FW1060.80, or FW950.00–FW950.H2. Exploitation requires root access within a guest partition, making compromised, malicious, or insufficiently controlled privileged guests the primary risk.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as being in KEV. Exploitation is local rather than network-direct and requires guest root access. Its low complexity, lack of user interaction, cross-boundary impact, and potential platform-wide outage still justify urgent remediation.
Researcher notes
CWE-190 and CVSS 8.4 support an integer-overflow condition with high integrity and availability impact, changed scope, and no stated confidentiality impact. The supplied bundle does not include fixed firmware identifiers, exploit evidence, or indicators of compromise. Avoid interpreting automatic hypervisor restart as mitigation because repeated triggering may sustain disruption.
Mitigation direction
- Inventory Power systems and compare installed firmware against every affected range.
- Review IBM advisory 7283229 for the applicable fixed firmware level and installation requirements.
- Apply IBM's prescribed firmware update using established platform maintenance procedures.
- Until updated, tightly restrict and monitor root access within guest partitions.
- Prepare recovery plans for platform re-IPL and simultaneous loss of hosted partitions.
Validation and detection
- Confirm each Power system's exact firmware level and whether it falls within an affected range.
- Verify the installed replacement level matches IBM advisory 7283229 for that platform.
- Confirm firmware installation completed successfully across all managed systems.
- Review guest privileged-access records and monitoring for unexpected hypervisor-related activity or platform restarts.
- Test recovery readiness without attempting to reproduce the vulnerability.
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.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-17091 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
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/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.
SSVC decision data
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:N/S:C/C:N/I:H/A:H25.8ibmVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/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.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/7283229CVE reference, ibm · vendor-advisory, patch
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.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.