dbcve.org
KernelOperating system · Insyde

CVE-2022-46897

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-22
Fix available
A fix is available. Upgrade to after 5.5 or later.
See remediation →
55/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 Insyde InsydeH2O with kernel 5.0 through 5.5. The CapsuleIFWUSmm driver does not check the return value from a method or function. This can prevent it from detecting unexpected states and conditions.

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

The CapsuleIFWUSmm driver in InsydeH2O firmware (kernel 5.0-5.5) fails to check return values from functions or methods, preventing detection of unexpected states and error conditions during firmware update operations.

MitigationApply vendor-provided BIOS/firmware updates from Insyde when available. Until then, restrict access to firmware update mechanisms and monitor for unauthorized capsule update attempts.

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.0, <= 5.5

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
None
Availability
None

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

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 firmware vendor
    Check system BIOS/UEFI information to confirm the system uses InsydeH2O firmware. This is typically visible in the BIOS setup under 'Main' or 'System Information' or via tools like 'dmidecode' (type 0) or 'biosinfo'.
    Affected if The system does not use InsydeH2O firmware - this CVE only applies to Insyde-based systems.
  2. Determine the Insyde kernel version
    Retrieve the firmware version from the BIOS/UEFI setup or using system information tools. Insyde firmware versions typically appear in the BIOS setup under 'Main' or 'BIOS Version', or can be obtained via 'dmidecode' or vendor-specific tools. Look for a kernel version number in the format 5.x.
    Affected if The installed Insyde kernel version falls within the range >= 5.0 and <= 5.5, indicating the firmware is in the affected range.
  3. Locate the CapsuleIFWUSmm driver
    This driver is a UEFI SMM (System Management Mode) driver component within the InsydeH2O firmware image. Check firmware dump analysis tools or contact Insyde/vendor for specific driver presence information. The driver name follows the pattern CapsuleIFWUSmm in the firmware.
    Affected if The CapsuleIFWUSmm driver is present in the firmware build - the vulnerability exists within this specific driver component.
  4. Assess firmware update exposure
    Review system configuration to determine if capsule update mechanisms are enabled or accessible. This includes checking UEFI capsule update settings in BIOS setup, system management interfaces, or reviewing firmware update tool configurations.
    Affected if Firmware update mechanisms (UEFI capsule updates) are enabled or accessible on the system, meaning the flawed return value checking could affect firmware update operations.

A system is affected if it runs InsydeH2O firmware with kernel version between 5.0 and 5.5 inclusive, contains the CapsuleIFWUSmm driver, and has firmware update capabilities accessible or enabled.

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.

From vendor data
Upgrade available Upgrade to a release after 5.5
Interim mitigation

Apply vendor-provided BIOS/firmware updates from Insyde when available. Until then, restrict access to firmware update mechanisms and monitor for unauthorized capsule update attempts.

Fix this in Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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