dbcve.org
Insydeh2oApplication · Insyde

CVE-2022-32471

HIGH · 7.0 CVSS v3.1 Published 2023-02-15
Fix available
A fix is available. Upgrade to 5.2.05.27.37 / 5.3.05.36.37 or later.
See remediation →
72/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
An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. The IhisiDxe driver uses the command buffer to pass input and output data. By modifying the command buffer contents with DMA after the input parameters have been checked but before they are used, the IHISI SMM code may be convinced to modify SMRAM or OS, leading to possible data corruption or escalation of privileges.

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 TOCTOU (Time-of-Check to Time-of-Use) vulnerability in InsydeH2O's IhisiSmm driver allows an attacker with DMA capabilities to modify the command buffer after input validation but before parameter use, enabling manipulation of SMRAM or OS memory and potential privilege escalation.

MitigationApply vendor-supplied InsydeH2O BIOS firmware update addressing CVE-2022-32471. Enable UEFI Secure Boot and IOMMU/DMA protection as defense-in-depth measures until patch deployment.

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.2.05.27.37>= 5.3, < 5.3.05.36.37>= 5.4, < 5.4.05.44.45>= 5.5, < 5.5.05.52.45

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

CVSS:3.1/AV:L/AC:H/PR:L/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 InsydeH2O BIOS version
    Run 'dmidecode -s bios-version' or check BIOS information via 'msinfo32' on Windows. On Linux, also check 'cat /sys/class/dmi/id/bios_version'. Record the exact version string.
    Affected if The displayed version falls within any of these ranges: >= 5.0 and < 5.2.05.27.37; >= 5.3 and < 5.3.05.36.37; >= 5.4 and < 5.4.05.44.45; or >= 5.5 and < 5.5.05.52.45.
  2. Verify BIOS vendor is Insyde
    Run 'dmidecode -s bios-vendor' or check 'cat /sys/class/dmi/id/bios_vendor' on Linux. Confirm the vendor string mentions 'Insyde' or 'InsydeH2O'.
    Affected if The vendor is InsydeH2O and the version from step 1 matches the affected ranges.
  3. Confirm IhisiSmm driver presence
    On systems with UEFI shell or tools, enumerate SMM drivers via 'efi-efitools' or check UEFI variable 'Setup' for IhisiSmm-related entries. This may require UEFI diagnostic tools or accessing the BIOS setup utility SMM information page if available.
    Affected if The IhisiSmm driver is present in the system firmware. This driver is typically included in InsydeH2O-based BIOS implementations.
  4. Check for DMA protection status
    On Linux, check 'dmesg | grep -i iommu' or 'dmesg | grep -i dma'. On Windows, check Device Manager for Intel VT-d or AMD-Vi status in the BIOS, or run 'bcdedit /enum all' looking for 'dmakernel'. Verify IOMMU is enabled in BIOS settings if accessible.
    Affected if IOMMU/DMA protection is DISABLED - this means the attack vector (DMA-based buffer modification) is fully accessible to an attacker. The vulnerability requires DMA capability to exploit.

You are affected if your system runs an InsydeH2O BIOS with a version matching any of the four affected ranges AND the IhisiSmm driver is present, with IOMMU/DMA protection disabled or not available.

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.2.05.27.37 / 5.3.05.36.37 / 5.4.05.44.45 or later
Fixed in 5.2.05.27.375.3.05.36.375.4.05.44.45
Interim mitigation

Apply vendor-supplied InsydeH2O BIOS firmware update addressing CVE-2022-32471. Enable UEFI Secure Boot and IOMMU/DMA protection as defense-in-depth measures until patch deployment.

Recommended fix High confidence

Upgrade to version 5.2.05.27.37 or later (for 5.0-5.2 branch), 5.3.05.36.37 or later (for 5.3 branch), 5.4.05.44.45 or later (for 5.4 branch), or 5.5.05.52.45 or later (for 5.5 branch)

  1. Identify the current InsydeH2O firmware version by checking the BIOS/UEFI setup or system information
  2. Determine which version branch you are running: 5.0-5.2, 5.3, 5.4, or 5.5
  3. Obtain the appropriate firmware update from the system/vendor website that includes the fixed version for your branch: 5.2.05.27.37 or later (for 5.0-5.2), 5.3.05.36.37 or later (for 5.3), 5.4.05.44.45 or later (for 5.4), or 5.5.05.52.45 or later (for 5.5)
  4. Follow the vendor's standard BIOS/firmware update procedure to apply the patched version
  5. Verify the firmware update was successful by checking the updated BIOS version
Caveat Firmware updates carry risk of system unbootability if interrupted; follow vendor update procedures precisely and ensure stable power

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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