IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in partition firmware during network boot. An unauthenticated attacker with access to the same network as a partition undergoing iSCSI SAN network boot can prevent that partition from completing its boot sequence. Other partitions and the managed system are not affected. Only partitions actively performing an iSCSI SAN network boot are affected, resulting in an availability impact.
Security readout for executives and security teams
Plain-English summary
An attacker on the same network as an IBM PowerVM partition can disrupt that partition while it performs an iSCSI SAN network boot. The affected partition may fail to finish booting. IBM states that other partitions and the managed system are unaffected, making this a targeted availability issue rather than a system-wide compromise.
Executive priority
Prioritize promptly where critical workloads use iSCSI SAN boot on reachable networks. Elsewhere, schedule remediation through normal firmware maintenance. Business impact is interrupted startup or recovery of an affected partition, not documented cross-partition compromise.
Technical view
CVE-2026-17028 is a CWE-125 out-of-bounds read in PowerVM partition firmware during iSCSI SAN network boot. It requires adjacent-network access but no authentication, privileges, or user interaction. Successful exploitation prevents the booting partition from completing startup. The supplied CVSS 3.1 score is 6.5, with high availability impact and no stated confidentiality or integrity impact.
Likely exposure
Exposure is limited to listed PowerVM firmware branches and partitions actively performing iSCSI SAN network boot. Risk is greatest where untrusted or insufficiently segmented devices can reach the boot network. Partitions using other boot methods are not identified as affected by the supplied sources.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as being in KEV. Exploitation requires access to the same network as the booting partition. Evidence supports denial of service against that partition only; it does not support compromise of other partitions or the managed system.
Researcher notes
The affected ranges are FW1120.00; FW1110.00 through FW1110.30; FW1060.00 through FW1060.80; and FW950.00 through FW950.H2. The source bundle does not provide technical root-cause detail beyond an out-of-bounds read, nor corrected version numbers. Validation should therefore rely on IBM’s advisory and platform inventory rather than speculative testing.
Mitigation direction
Review IBM advisory 7283233 for corrected firmware levels applicable to each managed system.
Apply IBM-provided firmware remediation through the organization’s tested maintenance process.
Restrict iSCSI boot networks to authorized systems using segmentation and network access controls.
Limit network boot activity until remediation where adjacent-network access cannot be adequately controlled.
Validation and detection
Inventory Power Systems firmware and compare versions with IBM’s affected and corrected levels.
Identify partitions configured for iSCSI SAN network boot.
Confirm iSCSI boot networks are isolated from untrusted or unnecessary adjacent hosts.
After remediation, verify firmware levels and confirm affected partitions complete network boot normally.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-125: 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.