dbcve.org
Insydeh2oApplication · Insyde

CVE-2022-24030

HIGH · 7.5 CVSS v3.1 Published 2022-02-03
Fix available
A fix is available. Upgrade to 5.08.41 / 5.16.41 or later.
See remediation →
77/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
An issue was discovered in AhciBusDxe in Insyde InsydeH2O with kernel 5.1 through 5.5. An SMM memory corruption vulnerability allows an attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to 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 vulnerability in the AhciBusDxe driver of InsydeH2O UEFI firmware (kernel 5.1-5.5) allows an attacker to write fixed or predictable data to SMRAM, corrupting System Management Mode memory. This SMM memory corruption can be exploited to escalate privileges to the highest firmware-level execution context, bypassing OS-level security controls.

MitigationApply vendor-supplied InsydeH2O firmware updates addressing CVE-2022-24030; if immediate patching is infeasible, evaluate SMM lockdown features or alternative firmware integrity controls where available.

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.0, < 5.08.41>= 5.1, < 5.16.41>= 5.2, < 5.26.41>= 5.3, < 5.35.41>= 5.4, < 5.43.41>= 5.5, < 5.51.41

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
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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 firmware vendor
    Run 'dmidecode -s bios-vendor' or check /sys/class/dmi/id/bios_vendor to determine if the system uses InsydeH2O UEFI firmware
    Affected if The vendor is not Insyde or InsydeH2O, then the system is not affected by this specific CVE
  2. Obtain firmware version
    Run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version to retrieve the installed InsydeH2O firmware version string
    Affected if The version string cannot be retrieved or the system does not use InsydeH2O firmware
  3. Extract firmware kernel version
    Use a UEFI firmware analysis tool such as UEFITool or dump the firmware ROM and search for the kernel version string pattern (e.g., '5.x' where x is the kernel number) embedded in the firmware image
    Affected if Unable to extract the kernel version from the firmware; the vulnerability only applies to kernel versions 5.1 through 5.5 as indicated in the CVE
  4. Compare against affected version ranges
    Cross-reference the extracted kernel version against the affected ranges: >= 5.0 and < 5.08.41; >= 5.1 and < 5.16.41; >= 5.2 and < 5.26.41; >= 5.3 and < 5.35.41; >= 5.4 and < 5.43.41; >= 5.5 and < 5.51.41
    Affected if The kernel version falls within any of these ranges, meaning the system is potentially affected by the vulnerability in the AhciBusDxe driver

If the system runs InsydeH2O firmware with a kernel version between 5.1 and 5.5 that falls within the affected version ranges, the AhciBusDxe driver vulnerability is present and could allow SMRAM corruption for privilege escalation.

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.08.41 / 5.16.41 / 5.26.41 or later
Fixed in 5.08.415.16.415.26.41
Interim mitigation

Apply vendor-supplied InsydeH2O firmware updates addressing CVE-2022-24030; if immediate patching is infeasible, evaluate SMM lockdown features or alternative firmware integrity controls where available.

Recommended fix High confidence

Upgrade to InsydeH2O kernel version 5.08.41 (for 5.0.x branch), 5.16.41 (for 5.1.x branch), 5.26.41 (for 5.2.x branch), or 5.35.41 (for 5.3.x branch) or later

  1. Identify the InsydeH2O firmware version currently installed on the affected system (typically available in BIOS/UEFI setup or via system information tools)
  2. Determine which version branch the current firmware is on: 5.0.x, 5.1.x, 5.2.x, or 5.3.x
  3. Obtain the appropriate firmware update from the system manufacturer (OEM) that includes the fixed InsydeH2O version: 5.08.41 or higher for 5.0.x, 5.16.41 or higher for 5.1.x, 5.26.41 or higher for 5.2.x, 5.35.41 or higher for 5.3.x
  4. Apply the firmware update following the OEM's standard BIOS/firmware update procedure, which typically involves running a firmware update utility or flashing via UEFI update mechanism
Caveat Firmware updates carry inherent risks and should be performed with stable power; some OEMs may not provide updates for older systems

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

Fix this in Insydeh2o Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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