CVE-2022-35408 json
An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5.
published 4y ago modified 4mo ago also EUVD-2022-38298
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. An SMM callout vulnerability in the SMM driver in UsbLegacyControlSmm leads to possible arbitrary code execution in SMM and escalation of privileges. An attacker could overwrite the function pointers in the EFI_BOOT_SERVICES table before the USB SMI handler triggers. (This is not exploitable from code running in the operating system.)
Patch / fix
- insyde insydeh2o 05.09.38, 5.17.38, 05.27.28, 05.36.28, 05.44.28, 05.52.28
Is CVE-2022-35408 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- binarly.io https://binarly.io/advisories/BRLY-2022-022/index.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-123 Write-what-where Condition
References
-
binarly.io
/advisories/BRLY-2022-022/index.html
exploit, third-party-advisory
-
insyde.com
/security-pledge
vendor-advisory
-
insyde.com
/security-pledge/SA-2022031
vendor-advisory
Sources
- CVE List CVE-2022-35408
- NVD CVE-2022-35408
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.