What’s Vulnerable › Vulnerabilities
CVE-2022-30283
- Severity: high (CVSS 7.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2022-11-15 · updated 2026-06-17
- Weakness: CWE-367
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 products
- Insyde Kernel: from 5.0 before 5.0.05.09.21; from 5.1 before 5.1.05.17.21; from 5.2 before 5.2.05.27.21; from 5.3 before 5.3.05.36.21; from 5.4 before 5.4.05.44.21; from 5.5 before 5.5.05.52.21 — fixed in 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, 5.5.05.52.21
How to fix
Upgrade to a fixed version: Insyde Kernel 5.0.05.09.21, 5.1.05.17.21, 5.2.05.27.21, 5.3.05.36.21. Check the vendor advisory for mitigations.
References
- https://www.insyde.com/security-pledge
- https://www.insyde.com/security-pledge/SA-2022063
- https://www.insyde.com/security-pledge
- https://www.insyde.com/security-pledge/SA-2022063
Get alerted when CVE-2022-30283 or the next vulnerability affects your stack