CVE-2022-30283

HIGH
7.5
CVSS Score
Published: November 15, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 04:43 AM UTC
1 product affected across 1 vendorKernel

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In 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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.0 ≤ v < 5.0.05.09.215.1 ≤ v < 5.1.05.17.215.2 ≤ v < 5.2.05.27.215.3 ≤ v < 5.3.05.36.215.4 ≤ v < 5.4.05.44.215.5 ≤ v < 5.5.05.52.21
Affected range stops below 5.0.05.09.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.1.05.17.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.2.05.27.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.3.05.36.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.4.05.44.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5.05.52.21, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHCISA-ADP
Attack Vector
LOCAL
Complexity
HIGH
Privileges
HIGH
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-367

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card