CVE-2022-30283
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 · uneditedIn UsbCoreDxe, tampering with the contents of the USB working buffer using DMA while certain USB transactions are in process leads to a TOCTOU problem that could be used by an attacker to cause SMRAM corruption and escalation of privileges The UsbCoreDxe module creates a working buffer for USB transactions outside of SMRAM. The code which uses can be inside of SMM, making the working buffer untrusted input. The buffer can be corrupted by DMA transfers. The SMM code code attempts to sanitize pointers to ensure all pointers refer to the working buffer, but when a pointer is not found in the list of pointers to sanitize, the current action is not aborted, leading to undefined behavior. This issue was discovered by Insyde engineering based on the general description provided by Intel's iSTARE group. Fixed in: Kernel 5.0: Version 05.09. 21 Kernel 5.1: Version 05.17.21 Kernel 5.2: Version 05.27.21 Kernel 5.3: Version 05.36.21 Kernel 5.4: Version 05.44.21 Kernel 5.5: Version 05.52.21 https://www.insyde.com/security-pledge/SA-2022063
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 confidenceA TOCTOU vulnerability in UsbCoreDxe allows DMA-corrupted USB working buffers to corrupt SMRAM. The SMM code validates pointers against a sanitize list but fails to abort when a pointer is not found, leading to undefined behavior and potential privilege escalation to SMM.
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.0, < 5.0.05.09.21>= 5.1, < 5.1.05.17.21>= 5.2, < 5.2.05.27.21>= 5.3, < 5.3.05.36.21>= 5.4, < 5.4.05.44.21>= 5.5, < 5.5.05.52.21CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the system firmware vendorRun `dmidecode -s bios-vendor` or check UEFI/BIOS setup to confirm the system uses Insyde firmwareAffected if The vendor is not Insyde (this CVE only applies to Insyde-based firmware)
-
Retrieve the Insyde Kernel versionRun `dmidecode -s bios-version` or use the Insyde-specific firmware update tool to obtain the BIOS/firmware version stringAffected if Unable to retrieve a version string from Insyde firmware
-
Compare the installed version against affected rangesParse the version string and compare numerically to the vulnerable ranges: < 5.0.05.09.21, < 5.1.05.17.21, < 5.2.05.27.21, < 5.3.05.36.21, < 5.4.05.44.21, or < 5.5.05.52.21 depending on the major.minor branchAffected if The version falls within any of the vulnerable ranges (e.g., 5.0.05.09.00 or 5.3.05.20.00 would be affected)
-
Verify UsbCoreDxe component presenceInspect the loaded UEFI drivers via `efibootmgr -v` or firmware ROM dump analysis to confirm UsbCoreDxe is present in the firmwareAffected if The UsbCoreDxe driver is not found in the firmware (the vulnerability only applies if this component exists)
The system is affected if it uses Insyde firmware with a Kernel version in any of the listed vulnerable ranges and includes the UsbCoreDxe component.
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.0.05.09.215.1.05.17.215.2.05.27.21
Apply vendor firmware updates for the specified kernel versions (05.09.21, 05.17.21, 05.27.21, 05.36.21, 05.44.21, or 05.52.21 depending on kernel version). No workarounds available; this is a firmware-level fix.
Insyde Kernel 5.0:05.09.21, 5.1:05.17.21, 5.2:05.27.21, 5.3:05.36.21, 5.4:05.44.21, or 5.5:05.52.21 (depending on your kernel branch)
- Identify the current Insyde Kernel version by checking the UEFI/BIOS version reported by the system (via system information tool, BIOS setup, or dmidecode)
- Determine the kernel branch (5.0, 5.1, 5.2, 5.3, 5.4, or 5.5) from the current version number
- Obtain the fixed firmware update from the system manufacturer (OEM/ODM) that includes the patched Insyde Kernel version
- Apply the firmware update following the manufacturer's recommended process (typically via BIOS update utility, EFI shell, or USB flash tool)
- Verify the firmware was successfully updated by checking the BIOS/UEFI version after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30283 — 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-30283 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