CVE-2022-30774
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 · uneditedDMA attacks on the parameter buffer used by the PnpSmm 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 PnpSmm 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 during a security review. This iss was fixed in Kernel 5.2: 05.27.29, Kernel 5.3: 05.36.25, Kernel 5.4: 05.44.25, Kernel 5.5: 05.52.25. CWE-367 https://www.insyde.com/security-pledge/SA-2022043
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 confidenceThe PnpSmm driver in Insyde UEFI firmware contains a TOCTOU (Time-Of-Check-Time-Of-Use) vulnerability where DMA attacks can modify parameter buffer contents after validation checks pass but before the values are actually used. This allows an attacker with DMA capability to potentially bypass security checks and execute code in SMM (System Management Mode) or elevate privileges.
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>= 5.2, < 5.2.05.27.29>= 5.3, < 5.3.05.36.25>= 5.4, < 5.4.05.44.25>= 5.5, < 5.5.05.52.25CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the system firmware vendorRun `dmidecode -s bios-vendor` or check system information to confirm the BIOS is from InsydeAffected if The vendor is not Insyde (this CVE only affects Insyde UEFI firmware)
-
Retrieve the Insyde Kernel versionRun `dmidecode -s bios-version` or check the UEFI firmware version through system information tools. The version string typically follows patterns like 5.2.xx.xx.xx or 5.3.xx.xx.xxAffected if The firmware version cannot be determined or is not an Insyde Kernel version
-
Compare installed version against affected rangesMatch the retrieved Insyde Kernel version to these ranges: >= 5.2, < 5.2.05.27.29; >= 5.3, < 5.3.05.36.25; >= 5.4, < 5.4.05.44.25; >= 5.5, < 5.5.05.52.25. The first two number groups indicate the Kernel branch (e.g., 5.2, 5.3) and the remaining groups indicate the specific release within that branchAffected if The installed version falls within any of the four affected ranges listed above
-
Verify PnpSmm driver presence (optional)On systems with UEFI tooling available, inspect the loaded UEFI drivers or check firmware images for the PnpSmm driver component. This typically requires UEFI firmware analysis tools or reading the firmware dumpAffected if The PnpSmm driver is present in a firmware version that matches the affected version ranges
A system is affected if it runs Insyde UEFI firmware with Kernel version 5.2 through 5.2.05.27.28, 5.3 through 5.3.05.36.24, 5.4 through 5.4.05.44.24, or 5.5 through 5.5.05.52.24, and the PnpSmm driver is present and accessible via DMA attacks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.2.05.27.295.3.05.36.255.4.05.44.25
Apply the vendor-supplied firmware updates: Kernel 5.2 to version 05.27.29, Kernel 5.3 to 05.36.25, Kernel 5.4 to 05.44.25, or Kernel 5.5 to 05.52.25 (or later). Verify DMA protection features are enabled in UEFI settings.
Insyde Kernel 5.2: 05.27.29 or later; Kernel 5.3: 05.36.25 or later; Kernel 5.4: 05.44.25 or later; Kernel 5.5: 05.52.25 or later (upgrade to the fixed version matching your current branch)
- 1. Identify the current Insyde kernel version by checking the UEFI firmware version or system documentation.
- 2. Determine which kernel branch (5.2, 5.3, 5.4, or 5.5) your device is currently running.
- 3. Obtain the firmware update from the device manufacturer (OEM) that includes the fixed kernel version for your specific branch.
- 4. Apply the firmware update using the OEM's standard firmware update process (typically via BIOS/UEFI flash utility or firmware management tool).
- 5. Verify the kernel version has been updated to the fixed release: for Kernel 5.2 to >=05.27.29, Kernel 5.3 to >=05.36.25, Kernel 5.4 to >=05.44.25, or Kernel 5.5 to >=05.52.25.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-30774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30774 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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