dbcve.org
KernelOperating system · Insyde

CVE-2024-25078

HIGH · 7.4 CVSS v3.1 Published 2024-05-15
Fix available
A fix is available. Upgrade to 5.29.07 / 5.38.07 or later.
See remediation →
76/100
Remediation priority · High
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
A memory corruption vulnerability in StorageSecurityCommandDxe in Insyde InsydeH2O before kernel 5.2: IB19130163 in 05.29.07, kernel 5.3: IB19130163 in 05.38.07, kernel 5.4: IB19130163 in 05.46.07, kernel 5.5: IB19130163 in 05.54.07, and kernel 5.6: IB19130163 in 05.61.07 could lead to escalating privileges in SMM.

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 corruption vulnerability in the StorageSecurityCommandDxe driver of InsydeH2O UEFI firmware allows an attacker to escalate privileges to System Management Mode (SMM). This vulnerability affects multiple kernel versions (5.2 through 5.6) across various firmware releases. SMM operates at the highest privilege level on x86 systems, making arbitrary code execution at this level extremely dangerous as it can bypass operating system security controls.

MitigationApply vendor-supplied firmware updates (kernel 5.2: 05.29.07+, 5.3: 05.38.07+, 5.4: 05.46.07+, 5.5: 05.54.07+, 5.6: 05.61.07+) to patch the memory corruption in StorageSecurityCommandDxe. Since this is a firmware-level vulnerability, standard software patches will not resolve the issue.

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
KernelOperating system
Affected:>= 5.2, < 5.29.07>= 5.3, < 5.38.07>= 5.4, < 5.46.07>= 5.5, < 5.54.07>= 5.6, < 5.61.07

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

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

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 InsydeH2O firmware version
    Use system information tools (such as dmidecode -s bios-version, or vendor-specific tools like Insyde FlashRom utility) to retrieve the installed UEFI firmware version and confirm it is InsydeH2O-based.
    Affected if The firmware version cannot be determined or is not InsydeH2O-based (this CVE only affects InsydeH2O UEFI firmware).
  2. Determine the Insyde Kernel version
    Retrieve the kernel version from the UEFI firmware. This is typically shown in the firmware setup utility under 'Version' or 'Information', or can be extracted using Insyde tools like 'efiupd' or by inspecting the firmware image with tools like UEFITool.
    Affected if The kernel version falls within any of these ranges: >= 5.2 and < 5.29.07, >= 5.3 and < 5.38.07, >= 5.4 and < 5.46.07, >= 5.5 and < 5.54.07, or >= 5.6 and < 5.61.07.
  3. Verify StorageSecurityCommandDxe driver presence
    Inspect the firmware image for the StorageSecurityCommandDxe driver module using UEFI firmware analysis tools (such as UEFITool, RU.efi, or Insyde's firmware extraction utilities). This driver handles storage security commands in SMM.
    Affected if The StorageSecurityCommandDxe driver is present in the firmware image, indicating the vulnerable component is included.
  4. Confirm SMM is enabled
    Check System Management Mode configuration in UEFI settings or verify SMM communication is active. This can be done via OS tools that query SMM state or through UEFI variable inspection (such as checking for SMM-related variables in the firmware).
    Affected if SMM is enabled and the StorageSecurityCommandDxe driver is present in an affected kernel version.

You are affected if your system runs InsydeH2O UEFI firmware with a kernel version within any of the affected ranges (5.2 to <5.29.07, 5.3 to <5.38.07, 5.4 to <5.46.07, 5.5 to <5.54.07, or 5.6 to <5.61.07) and the StorageSecurityCommandDxe driver is present.

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.29.07 / 5.38.07 / 5.46.07 or later
Fixed in 5.29.075.38.075.46.07
Interim mitigation

Apply vendor-supplied firmware updates (kernel 5.2: 05.29.07+, 5.3: 05.38.07+, 5.4: 05.46.07+, 5.5: 05.54.07+, 5.6: 05.61.07+) to patch the memory corruption in StorageSecurityCommandDxe. Since this is a firmware-level vulnerability, standard software patches will not resolve the issue.

Recommended fix High confidence

InsydeH2O kernel version-specific patch: upgrade to 05.29.07 (5.2 branch), 05.38.07 (5.3 branch), 05.46.07 (5.4 branch), 05.54.07 (5.5 branch), or 05.61.07 (5.6 branch)

  1. 1. Identify the InsydeH2O firmware kernel version currently running on the affected system (typically viewable via UEFI setup or dmidecode output)
  2. 2. Determine which kernel branch the current firmware is based on (5.2, 5.3, 5.4, 5.5, or 5.6)
  3. 3. Contact Insyde or the hardware OEM for the patched firmware update corresponding to the specific kernel branch
  4. 4. Apply the appropriate patched firmware version: 05.29.07 (for kernel 5.2), 05.38.07 (for kernel 5.3), 05.46.07 (for kernel 5.4), 05.54.07 (for kernel 5.5), or 05.61.07 (for kernel 5.6)
  5. 5. Verify the firmware update was applied successfully and the system boots normally
Caveat UEFI firmware updates carry a risk of bricking the system if interrupted; ensure stable power and follow OEM update procedures precisely

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

Fix this in Kernel Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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