dbcve.org
Powervm HypervisorOperating system · Ibm

CVE-2025-36035

MEDIUM · 5.1 CVSS v3.1 Published 2025-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
53/100
Remediation priority · Moderate
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM PowerVM Hypervisor FW950.00 through FW950.E0, FW1050.00 through FW1050.50, and FW1060.00 through FW1060.40 could allow a local privileged user to cause a denial of service by issuing a specially crafted IBM i hypervisor call that would disclose memory contents or consume excessive memory resources.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM PowerVM Hypervisor firmware versions FW950.00-FW950.E0, FW1050.00-FW1050.50, and FW1060.00-FW1060.40 contain a vulnerability where a local privileged user can issue specially crafted IBM i hypervisor calls to cause denial of service through memory disclosure or excessive memory consumption.

MitigationApply the appropriate IBM PowerVM firmware update beyond the affected version ranges. Organizations should schedule maintenance windows and test firmware updates in non-production environments before deploying to production systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Powervm HypervisorOperating system
Affected:>= FW950.00, <= FW950.E0>= FW1050.00, <= FW1050.50>= FW1060.00, <= FW1060.40

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IBM PowerVM Hypervisor is in use
    Access the Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) and verify the virtualization platform is IBM PowerVM. This vulnerability applies only to PowerVM hypervisor firmware, not other IBM virtualization products.
    Affected if The system does not use IBM PowerVM Hypervisor, then this CVE does not apply.
  2. Locate PowerVM firmware version through HMC
    From the HMC main menu, select 'Systems' -> Select managed system -> 'System Properties' -> View the 'Firmware' or 'PowerVM' section. Alternatively, use the command 'lssyscfg -r sys -m <managed_system> --header -f firmware_version' if HMC CLI is available.
    Affected if Unable to retrieve PowerVM firmware version, cannot determine exposure.
  3. Check if firmware falls within first affected range
    Compare the firmware version string (format FW950.xx) against the range FW950.00 to FW950.E0. Note that any version from FW950.00 through FW950.E0 inclusive is affected.
    Affected if Firmware version is between FW950.00 and FW950.E0 (inclusive).
  4. Check if firmware falls within second affected range
    Compare the firmware version string against the range FW1050.00 to FW1050.50. Any version from FW1050.00 through FW1050.50 inclusive is affected.
    Affected if Firmware version is between FW1050.00 and FW1050.50 (inclusive).
  5. Check if firmware falls within third affected range
    Compare the firmware version string against the range FW1060.00 to FW1060.40. Any version from FW1060.00 through FW1060.40 inclusive is affected.
    Affected if Firmware version is between FW1060.00 and FW1060.40 (inclusive).

The environment is affected if the IBM PowerVM Hypervisor firmware version falls within any of these ranges: FW950.00 to FW950.E0, FW1050.00 to FW1050.50, or FW1060.00 to FW1060.40.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate IBM PowerVM firmware update beyond the affected version ranges. Organizations should schedule maintenance windows and test firmware updates in non-production environments before deploying to production systems.

Fix this in Powervm Hypervisor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36035 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data