dbcve.org
Memory LeakWeakness · CWE-401

CVE-2025-20077

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
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
Missing release of memory after effective lifetime in the UEFI OobRasMmbiHandlerDriver module for some Intel(R) reference server platforms may allow a privileged user to enable denial of service via local access.

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 · moderate confidence

A memory leak exists in the UEFI OobRasMmbiHandlerDriver module on certain Intel reference server platforms. The driver fails to release allocated memory after it is no longer needed, allowing a privileged local user to exhaust memory resources and cause a denial of service condition.

MitigationApply Intel-provided firmware/BIOS updates for affected server platforms. Consult Intel's product security advisories for specific platform availability and update procedures.

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

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
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/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. Identify system platform
    Check if the system is an Intel reference server platform. Use commands like 'dmidecode -s system-product-name' or check the system vendor/model documentation.
    Affected if System is NOT an Intel reference server platform - this vulnerability only affects specific Intel reference server designs.
  2. Check BIOS/UEFI firmware version
    Retrieve the current BIOS/UEFI firmware version using 'dmidecode -s bios-version' or through the system's IPMI/BMC interface (e.g., using 'ipmitool fru print' or checking the BMC web interface).
    Affected if Unable to determine firmware version - you cannot assess exposure without knowing the installed BIOS/UEFI version.
  3. Verify OobRasMmbiHandlerDriver presence
    Check system firmware/UEFI documentation or contact Intel support to confirm whether the OobRasMmbiHandlerDriver module is included in your platform's firmware. This driver is part of Intel's Out-of-Band RAS (Reliability Availability Serviceability) features.
    Affected if The OobRasMmbiHandlerDriver module is NOT present in your system firmware - the vulnerability cannot be triggered.
  4. Compare firmware version to Intel advisories
    Locate the Intel product security advisory for CVE-2025-20077 and compare your installed firmware version against the affected version ranges listed. Intel advisories typically list specific firmware versions that contain the fix.
    Affected if Your installed firmware version falls within the affected version range AND the fixed version has not been applied.
  5. Check for memory leak indicators
    Monitor system memory usage over time using 'free -m' or 'vmstat 1' looking for steadily increasing memory consumption that does not get released, particularly during OOB/remote management operations if the driver is active.
    Affected if Unexplained memory exhaustion is observed and no other root cause is identified, though this is a secondary indicator requiring firmware-level confirmation.

A user is affected if they are running an Intel reference server platform with the OobRasMmbiHandlerDriver module present and a firmware version within the vulnerable range according to Intel's CVE-2025-20077 advisory.

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 Intel-provided firmware/BIOS updates for affected server platforms. Consult Intel's product security advisories for specific platform availability and update procedures.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20077 — 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-20077 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