dbcve.org
Insydeh2oApplication · Insyde

CVE-2024-55567

MEDIUM · 6.7 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 5.4.05.47.01 / 5.5.05.55.01 or later.
See remediation →
69/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
Improper input validation was discovered in UsbCoreDxe in Insyde InsydeH2O kernel 5.4 before 05.47.01, 5.5 before 05.55.01, 5.6 before 05.62.01, and 5.7 before 05.71.01. The SMM module has an SMM call out vulnerability which can be used to write arbitrary memory inside SMRAM and execute arbitrary code at SMM level.

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

Improper input validation in UsbCoreDxe (USB core driver) in InsydeH2O UEFI kernel versions 5.4-5.7 creates an SMM callout vulnerability. This allows an attacker to write arbitrary memory within SMRAM (System Management RAM) and execute code at the highest CPU privilege level (SMM).

MitigationApply vendor-provided firmware updates: 05.47.01 or later for kernel 5.4, 05.55.01 or later for 5.5, 05.62.01 or later for 5.6, and 05.71.01 or later for 5.7. Update through vendor BIOS/UEFI firmware update processes.

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
Insydeh2oApplication
Affected:>= 5.4, < 5.4.05.47.01>= 5.5, < 5.5.05.55.01>= 5.6, < 5.6.05.62.01>= 5.7, < 5.7.05.71.01

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 the system vendor and BIOS firmware
    Check the system manufacturer (HP, Dell, Lenovo, etc.) and model. InsydeH2O is a UEFI firmware kernel used by multiple OEMs, so determine if your BIOS vendor uses InsydeH2O.
    Affected if The system uses an InsydeH2O-based UEFI firmware from an OEM.
  2. Locate the InsydeH2O kernel version
    Access the BIOS setup utility and look for version information under 'Main', 'System Information', or 'BIOS Version'. The version is typically displayed as a numeric string like 5.4.xx.xx.xx or 5.5.xx.xx.xx.
    Affected if The displayed version matches the InsydeH2O kernel version numbering (5.x format).
  3. Compare against affected version ranges
    Cross-reference the installed kernel version with the following ranges: >= 5.4 and < 5.4.05.47.01; >= 5.5 and < 5.5.05.55.01; >= 5.6 and < 5.6.05.62.01; >= 5.7 and < 5.7.05.71.01.
    Affected if The installed version falls within any of these ranges.
  4. Verify USB support is enabled
    Enter BIOS setup and navigate to 'Advanced' or 'Integrated Peripherals'. Check if USB controllers and USB support (typically 'USB Enabled' or similar) are turned on.
    Affected if USB support is enabled in the BIOS configuration.
  5. Check SMRAM accessibility status
    In the BIOS setup under 'Security' or 'Advanced' settings, look for 'SMM Protection' or 'SMRAM' configuration options. Document whether SMRAM is locked or accessible.
    Affected if SMM protection is not enabled or SMRAM is not locked (vulnerability allows SMM callout).

If the InsydeH2O kernel version falls within any of the affected ranges and USB support is enabled in the firmware, the system is potentially vulnerable to SMM callout attacks.

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.

dbcve · scoped
Upgrade available Upgrade to 5.4.05.47.01 / 5.5.05.55.01 / 5.6.05.62.01 or later
Fixed in 5.4.05.47.015.5.05.55.015.6.05.62.01
Interim mitigation

Apply vendor-provided firmware updates: 05.47.01 or later for kernel 5.4, 05.55.01 or later for 5.5, 05.62.01 or later for 5.6, and 05.71.01 or later for 5.7. Update through vendor BIOS/UEFI firmware update processes.

Recommended fix High confidence

InsydeH2O kernel 5.4.05.47.01 or later (5.4 branch); 5.5.05.55.01 or later (5.5 branch); 5.6.05.62.01 or later (5.6 branch); or 5.7.05.71.01 or later (5.7 branch)

  1. Identify the current InsydeH2O BIOS/UEFI firmware version installed on the affected system
  2. Download the latest InsydeH2O firmware update from the system manufacturer (OEM) that includes the security fix for this vulnerability
  3. Verify the firmware update package corresponds to one of the fixed versions: 5.4.05.47.01, 5.5.05.55.01, 5.6.05.62.01, or 5.7.05.71.01 (or later)
  4. Apply the firmware update using the OEM-recommended method (e.g., BIOS flash utility, Windows Update, or bootable USB)
  5. Reboot the system to complete the firmware update process
  6. Confirm the firmware version has been updated to a fixed release
Caveat Firmware updates carry inherent risks including potential boot failure if interrupted; ensure stable power and follow OEM update instructions precisely

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Insydeh2o Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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