dbcve.org
KernelApplication · Insyde

CVE-2022-30773

MEDIUM · 6.4 CVSS v3.1 Published 2022-11-14
Fix available
A fix is available. Upgrade to 5.4.05.44.23 / 5.5.05.52.23 or later.
See remediation →
66/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
DMA attacks on the parameter buffer used by the IhisiSmm driver could change the contents after parameter values have been checked but before they are used (a TOCTOU attack). DMA attacks on the parameter buffer used by the IhisiSmm driver could change the contents after parameter values have been checked but before they are used (a TOCTOU attack). This issue was discovered by Insyde engineering. This issue is fixed in Kernel 5.4: 05.44.23 and Kernel 5.5: 05.52.23. CWE-367

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

TOCTOU race condition in Insyde IhisiSmm driver where DMA attacks can modify parameter buffer contents between validation check and actual use. The vulnerability allows potential privilege escalation or code execution at SMM level due to unchecked buffer modifications after initial validation.

MitigationApply Insyde kernel firmware updates: Kernel 5.4 version 05.44.23 or Kernel 5.5 version 05.52.23 or later to address the TOCTOU vulnerability in the IhisiSmm driver parameter handling.

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
KernelApplication
Affected:>= 5.4, < 5.4.05.44.23>= 5.5, < 5.5.05.52.23

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

CVSS:3.1/AV:L/AC:H/PR:H/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 Insyde BIOS vendor
    Run `dmidecode -s bios-vendor` or check system BIOS information to confirm the BIOS is from Insyde (often displayed as InsydeH2O or Insyde Corp.)
    Affected if The system does not use Insyde firmware - this vulnerability only affects Insyde-based BIOS implementations
  2. Get Insyde Kernel version
    Run `dmidecode -s bios-version` or check the detailed BIOS/firmware version string in system information. The Insyde Kernel version is typically embedded in the BIOS version string (e.g., appears as something like 5.4.x.x or 5.5.x.x)
    Affected if Unable to retrieve or identify the Insyde Kernel version from BIOS information
  3. Compare version against affected ranges
    Examine the extracted BIOS/firmware version and parse the Insyde Kernel version component. Compare against: 5.4.x versions prior to 5.4.05.44.23, or 5.5.x versions prior to 5.5.05.52.23
    Affected if The Insyde Kernel version falls within the range: >= 5.4 and < 5.4.05.44.23, OR >= 5.5 and < 5.5.05.52.23
  4. Confirm IhisiSmm driver presence
    Review BIOS/firmware release notes or Insyde documentation for the specific BIOS version to confirm the IhisiSmm driver is included (this is standard in Insyde UEFI implementations)
    Affected if The system uses Insyde BIOS with the IhisiSmm driver component (typical for Insyde-based systems)

The system is affected if it runs Insyde BIOS with Insyde Kernel version 5.4.x before 5.4.05.44.23 or version 5.5.x before 5.5.05.52.23, as the TOCTOU vulnerability exists in the IhisiSmm driver parameter handling of those versions.

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.4.05.44.23 / 5.5.05.52.23 or later
Fixed in 5.4.05.44.235.5.05.52.23
Interim mitigation

Apply Insyde kernel firmware updates: Kernel 5.4 version 05.44.23 or Kernel 5.5 version 05.52.23 or later to address the TOCTOU vulnerability in the IhisiSmm driver parameter handling.

Recommended fix High confidence

Insyde Kernel 5.4: >= 05.44.23 or Kernel 5.5: >= 05.52.23

  1. Identify the Insyde firmware version currently installed on the affected system
  2. Download the updated Insyde Kernel firmware version 05.44.23 (for 5.4 branch) or 05.52.23 (for 5.5 branch) from the official Insyde support portal
  3. Follow the vendor's standard firmware update procedure to apply the new kernel version
  4. Verify the firmware update was successful by checking the installed kernel version

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

Fix this in Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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