dbcve.org
Insydeh2oApplication · Insyde

CVE-2022-35893

HIGH · 8.2 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 05.09.37 / 05.17.37 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 Insyde InsydeH2O with kernel 5.0 through 5.5. An SMM memory corruption vulnerability in the FvbServicesRuntimeDxe driver 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 · high confidence

A memory corruption vulnerability in the FvbServicesRuntimeDxe driver of InsydeH2O UEFI firmware (versions 5.0-5.5) allows an attacker to write fixed or predictable data to SMRAM (System Management RAM). This can lead to privilege escalation to System Management Mode (SMM), granting the attacker firmware-level code execution with the highest privileges on the system.

MitigationApply vendor firmware updates from Insyde or the OEM that include the patched FvbServicesRuntimeDxe driver. Until patched, verify Secure Boot is enabled and consider disabling SMM if the hardware/BIOS supports such configuration as a compensating control.

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, < 05.09.37>= 5.1, < 05.17.37>= 5.2, < 05.27.29>= 5.3, < 05.36.29>= 5.4, < 05.44.29>= 5.5, < 05.52.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 InsydeH2O UEFI firmware version
    Run `dmidecode -s bios-version` or check the BIOS information in the system setup utility (BIOS/UEFI setup). Look for a version string containing 'InsydeH2O' or 'Insyde' in the BIOS vendor or version information.
    Affected if The reported version falls within any of these ranges: 5.0 to 05.09.36, 5.1 to 05.17.36, 5.2 to 05.27.28, 5.3 to 05.36.28, 5.4 to 05.44.28, or 5.5 to 05.52.28.
  2. Confirm the firmware vendor is Insyde
    Run `dmidecode -s bios-vendor` or examine the BIOS setup screen to verify the firmware was developed by Insyde (InsydeH2O).
    Affected if The vendor is Insyde and the version matches the ranges above.
  3. Check if FvbServicesRuntimeDxe driver is present
    This driver is internal to the firmware. On Linux, use `sudo cat /sys/firmware/efi/efivars/...` to list UEFI variables, or use tools like `efitools` or `uefi-firmware-parser` to dump firmware and search for 'FvbServicesRuntimeDxe'. On Windows, use 'HWiNFO' or 'UEFITool' to examine the firmware image.
    Affected if The FvbServicesRuntimeDxe driver is found in the firmware image (this driver must be present for the vulnerability to apply).

Your system is affected if it runs InsydeH2O firmware version 5.0 through the versions listed above (05.09.36, 05.17.36, 05.27.28, 05.36.28, 05.44.28, or 05.52.28 depending on the major release), and the FvbServicesRuntimeDxe driver is present in the firmware.

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 05.09.37 / 05.17.37 / 05.27.29 or later
Fixed in 05.09.3705.17.3705.27.29
Interim mitigation

Apply vendor firmware updates from Insyde or the OEM that include the patched FvbServicesRuntimeDxe driver. Until patched, verify Secure Boot is enabled and consider disabling SMM if the hardware/BIOS supports such configuration as a compensating control.

Recommended fix High confidence

Minimum fixed versions: 05.09.37 (5.0 branch), 05.17.37 (5.1 branch), 05.27.29 (5.2 branch), 05.36.29 (5.3 branch)

  1. 1. Identify the InsydeH2O firmware version currently installed on the affected system (typically found in BIOS/UEFI setup under 'Security' or 'BIOS Version')
  2. 2. Determine which major version branch the current firmware is based on (5.0, 5.1, 5.2, or 5.3)
  3. 3. Obtain the appropriate firmware update from the system vendor (OEM) that includes the fixed InsydeH2O version
  4. 4. For 5.0 branch: upgrade to version 05.09.37 or later
  5. 5. For 5.1 branch: upgrade to version 05.17.37 or later
  6. 6. For 5.2 branch: upgrade to version 05.27.29 or later
  7. 7. For 5.3 branch: upgrade to version 05.36.29 or later
  8. 8. Apply the firmware update following the OEM's documented update process, which typically involves rebooting and entering BIOS setup or using a firmware update utility
Caveat Firmware updates carry inherent risk of rendering the system unusable if interrupted or applied incorrectly; verify OEM support and follow update instructions precisely

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

Fix this in Insydeh2o Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing16.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,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 $8,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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