dbcve.org
KernelOperating system · Insyde

CVE-2022-30772

HIGH · 8.2 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 5.0.05.09.41 / 5.1.05.17.43 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
Manipulation of the input address in PnpSmm function 0x52 could be used by malware to overwrite SMRAM or OS kernel memory. Function 0x52 of the PnpSmm driver is passed the address and size of data to write into the SMBIOS table, but manipulation of the address could be used by malware to overwrite SMRAM or OS kernel memory. This issue was discovered by Insyde engineering during a security review. This issue is fixed in: Kernel 5.0: 05.09.41 Kernel 5.1: 05.17.43 Kernel 5.2: 05.27.30 Kernel 5.3: 05.36.30 Kernel 5.4: 05.44.30 Kernel 5.5: 05.52.30 https://www.insyde.com/security-pledge/SA-2022065

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 PnpSmm driver in Insyde firmware has a vulnerability in function 0x52 where improper input validation on the address parameter allows manipulation to write data to arbitrary memory locations, potentially reaching SMRAM (System Management RAM) or OS kernel memory. This represents a memory corruption issue where the driver trusts user-controlled pointers without proper bounds checking.

MitigationApply the vendor-supplied firmware patch for the specific kernel version (05.09.41, 05.17.43, 05.27.30, 05.36.30, 05.44.30, or 05.52.30 for kernels 5.0-5.5 respectively). This is a critical firmware update requiring careful deployment following vendor update procedures.

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.0.05.09.41>= 5.1, < 5.1.05.17.43>= 5.2, < 5.2.05.27.30>= 5.3, < 5.3.05.36.30>= 5.4, < 5.4.05.44.30>= 5.5, < 5.5.05.52.30

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 firmware vendor
    Check the system BIOS/UEFI vendor information. On Linux, use 'dmidecode -s bios-vendor' or check /sys/class/dmi/id/bios_vendor. On Windows, run 'wmic bios get Manufacturer'.
    Affected if The vendor is not Insyde (the vulnerability only affects Insyde firmware)
  2. Determine the Insyde Kernel version
    Extract the firmware version string. On Linux, check 'dmidecode -s bios-version' or /sys/class/dmi/id/bios_version. Look for version strings in format like 05.xx.xx.xx indicating Insyde Kernel versions.
    Affected if The version cannot be determined or is not visible in the expected format (Insyde Kernel version not found)
  3. Compare against affected version ranges
    Parse the Insyde Kernel version number and compare against: 5.0 to 5.0.05.09.41, 5.1 to 5.1.05.17.43, 5.2 to 5.2.05.27.30, 5.3 to 5.3.05.36.30, 5.4 to 5.4.05.44.30, or 5.5 to 5.5.05.52.30.
    Affected if The installed version falls within any of the affected ranges (less than the fixed versions: 05.09.41 for 5.0, 05.17.43 for 5.1, 05.27.30 for 5.2, 05.36.30 for 5.3, 05.44.30 for 5.4, or 05.52.30 for 5.5)
  4. Check for the PnpSmm driver presence
    Inspect the firmware image or loaded drivers list if accessible. The driver is named PnpSmm and contains function 0x52. This may require firmware extraction tools or accessing SMM configuration via UEFI shell or specialized diagnostics.
    Affected if The PnpSmm driver with function 0x52 is present and the version is within affected ranges

A system is affected if it uses Insyde firmware with Kernel versions 5.0 through 5.5 that are below the fixed patch levels (5.0.05.09.41, 5.1.05.17.43, 5.2.05.27.30, 5.3.05.36.30, 5.4.05.44.30, or 5.5.05.52.30) and has the vulnerable PnpSmm driver with function 0x52 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.

dbcve · scoped
Upgrade available Upgrade to 5.0.05.09.41 / 5.1.05.17.43 / 5.2.05.27.30 or later
Fixed in 5.0.05.09.415.1.05.17.435.2.05.27.30
Interim mitigation

Apply the vendor-supplied firmware patch for the specific kernel version (05.09.41, 05.17.43, 05.27.30, 05.36.30, 05.44.30, or 05.52.30 for kernels 5.0-5.5 respectively). This is a critical firmware update requiring careful deployment following vendor update procedures.

Recommended fix High confidence

Upgrade to Insyde Kernel 5.0: 05.09.41 or later; Kernel 5.1: 05.17.43 or later; Kernel 5.2: 05.27.30 or later; Kernel 5.3: 05.36.30 or later; Kernel 5.4: 05.44.30 or later; Kernel 5.5: 05.52.30 or later

  1. Identify the current Insyde kernel version by checking the UEFI/BIOS version on the affected system
  2. Contact the hardware OEM/ODM vendor (e.g., Dell, HP, Lenovo, etc.) to obtain the firmware update containing the Insyde kernel fix
  3. Apply the vendor-provided UEFI/BIOS firmware update to patch the vulnerability
  4. Verify the firmware update was successfully applied by checking the BIOS version after the update
Caveat Firmware updates carry a risk of bricking the system if interrupted; ensure stable power and follow vendor update procedures precisely

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

Fix this in Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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