dbcve.org
Insydeh2oApplication · Insyde

CVE-2022-24069

HIGH · 8.2 CVSS v3.1 Published 2022-02-03
Fix available
A fix is available. Upgrade to 5.08.29 / 5.16.29 or later.
See remediation →
84/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.0 before 05.08.41, 5.1 before 05.16.29, 5.2 before 05.26.29, 5.3 before 05.35.29, 5.4 before 05.43.29, and 5.5 before 05.51.29. An SMM callout vulnerability allows an attacker to hijack the execution flow of code running in System Management Mode. 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 · high confidence

A SMM (System Management Mode) callout vulnerability in the AhciBusDxe AHCI controller driver of InsydeH2O UEFI firmware allows an attacker to hijack the execution flow of code running in SMM, which is the highest privilege execution mode on x86 processors (ring -2). Successful exploitation provides persistent, privileged code execution at the firmware level.

MitigationApply the appropriate InsydeH2O firmware update (05.08.41 or later for 5.0, 05.16.29 or later for 5.1, 05.26.29 or later for 5.2, 05.35.29 or later for 5.3, 05.43.29 or later for 5.4, 05.51.29 or later for 5.5) from the system vendor. This is a firmware-level issue; no software patch is 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.1, < 5.16.29>= 5.2, < 5.26.29>= 5.3, < 5.35.29>= 5.0, < 5.08.29>= 5.4, < 5.43.29>= 5.5, < 5.51.29

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

CVSS:3.1/AV:L/AC:L/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 the system firmware vendor
    On Linux, run 'dmidecode -s bios-vendor' or 'cat /sys/class/dmi/id/bios_vendor'. On Windows, run 'wmic bios get manufacturer' or check System Information (msinfo32).
    Affected if The vendor is not Insyde (or the system uses a different firmware implementation)
  2. Check the InsydeH2O firmware version
    On Linux, run 'dmidecode -s bios-version' or 'cat /sys/class/dmi/id/bios_version'. On Windows, run 'wmic bios get smbiosbiosversion' or check System Information. Note the full version string.
    Affected if The version string is empty, unavailable, or not from InsydeH2O
  3. Compare the installed version against affected ranges
    Parse the version string (format is typically 5.xx.yy). Compare numerically to the affected ranges: < 5.08.29 for 5.0 branch, < 5.16.29 for 5.1 branch, < 5.26.29 for 5.2 branch, < 5.35.29 for 5.3 branch, < 5.43.29 for 5.4 branch, < 5.51.29 for 5.5 branch.
    Affected if The installed version falls within any of the affected version ranges (5.0 to <5.08.29, 5.1 to <5.16.29, 5.2 to <5.26.29, 5.3 to <5.35.29, 5.4 to <5.43.29, or 5.5 to <5.51.29)
  4. Verify AHCI controller is present and enabled
    On Linux, run 'lspci | grep -i ahci' or check /sys/class/ata_port/. On Windows, check Device Manager under IDE ATA/ATAPI controllers for an AHCI controller.
    Affected if The system has an AHCI controller and it is enabled (the vulnerability is in the AhciBusDxe driver that manages this controller)
  5. Confirm SMM is available on the system
    This is typically always true on x86 systems, but you can verify on Linux with 'ls /sys/firmware/efi/systab' or check UEFI/BIOS settings for 'SMM' or 'System Management Mode' options.
    Affected if SMM is disabled (extremely rare on standard x86 systems, as it is required for many platform features)
  6. Check the UEFI driver version for AhciBusDxe
    This requires UEFI shell tools or manufacturer diagnostics. Use 'efibootmgr -v' on Linux to list boot entries, or check vendor-specific tools like Insyde's firmware update utility if available. The driver version may be visible in UEFI setup under 'Driver' or 'Advanced' menus on some systems.
    Affected if The AhciBusDxe driver version cannot be determined or is not separately reported from the main firmware version

A system is affected if it uses InsydeH2O UEFI firmware with a version that falls within any of the specified vulnerable ranges AND has an AHCI controller present with SMM enabled (which is the default on most x86 systems).

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.29 / 5.16.29 / 5.26.29 or later
Fixed in 5.08.295.16.295.26.29
Interim mitigation

Apply the appropriate InsydeH2O firmware update (05.08.41 or later for 5.0, 05.16.29 or later for 5.1, 05.26.29 or later for 5.2, 05.35.29 or later for 5.3, 05.43.29 or later for 5.4, 05.51.29 or later for 5.5) from the system vendor. This is a firmware-level issue; no software patch is available.

Recommended fix High confidence

Upgrade to InsydeH2O kernel 5.0 to 05.08.41+, kernel 5.1 to 05.16.29+, kernel 5.2 to 05.26.29+, or kernel 5.3 to 05.35.29+ (or the respective fixed version for the kernel branch in use)

  1. 1. Identify the InsydeH2O firmware version on affected systems by checking the UEFI/BIOS setup screen or using system information tools.
  2. 2. Determine which kernel version branch (5.0, 5.1, 5.2, or 5.3) the current firmware is based on.
  3. 3. Contact the system hardware vendor (OEM) to obtain the appropriate firmware update that includes the security fix.
  4. 4. Apply the vendor-provided firmware update, following the vendor's specific update instructions (this typically requires booting into the vendor's firmware update utility or using their update tool).
  5. 5. After updating, verify the firmware version has been upgraded to the fixed release (05.08.41+ for kernel 5.0, 05.16.29+ for kernel 5.1, 05.26.29+ for kernel 5.2, or 05.35.29+ for kernel 5.3).
Caveat Firmware updates carry inherent risk and may cause system instability if interrupted; ensure stable power and follow vendor instructions precisely

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

Fix this in Insydeh2o Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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