CVE-2022-33908 json
DMA transactions which are targeted at input buffers used for the SdHostDriver software SMI handler could cause SMRAM corruption through a…
published 3y ago modified 4mo ago also EUVD-2022-36945
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
DMA transactions which are targeted at input buffers used for the SdHostDriver software SMI handler could cause SMRAM corruption through a TOCTOU attack. DMA transactions which are targeted at input buffers used for the software SMI handler used by the SdHostDriver driver could cause SMRAM corruption through a TOCTOU attack. This issue was discovered by Insyde engineering based on the general description provided by Intel's iSTARE group. Fixed in kernel 5.2: 05.27.25, kernel 5.3: 05.36.25, kernel 5.4: 05.44.25, kernel 5.5: 05.52.25 https://www.insyde.com/security-pledge/SA-2022050
Patch / fix
- insyde kernel 5.2.05.27.25, 5.3.05.36.25, 5.4.05.44.25, 5.5.05.52.25
Is CVE-2022-33908 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-23-047-08 updated cvss 7.0
Siemens RUGGEDCOM APE1808
-
Siemens RUGGEDCOM APE1808 ADM (6GK6015-0AL20-0GL0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 ADM CC (6GK6015-0AL20-0GL1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CKP (6GK6015-0AL20-0GK0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CKP CC (6GK6015-0AL20-0GK1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CLOUDCONNECT (6GK6015-0AL20-0GM0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CLOUDCONNECT CC (6GK6015-0AL20-0GM1) <BIOS_V1.0.212Naffected: fixed in V1.0.212N support.industry.siemens.com
+16 more productsfewer
Siemens RUGGEDCOM APE1808 ELAN (6GK6015-0AL20-0GP0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 ELAN CC (6GK6015-0AL20-0GP1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 SAM-L (6GK6015-0AL20-0GN0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 SAM-L CC (6GK6015-0AL20-0GN1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-P (6GK6015-0AL20-1AA0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-P CC (6GK6015-0AL20-1AA1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S1 (6GK6015-0AL20-1AB0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S1 CC (6GK6015-0AL20-1AB1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S3 (6GK6015-0AL20-1AD0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S3 CC (6GK6015-0AL20-1AD1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S5 (6GK6015-0AL20-1AF0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S5 CC (6GK6015-0AL20-1AF1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808LNX (6GK6015-0AL20-0GH0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808LNX CC (6GK6015-0AL20-0GH1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808W10 (6GK6015-0AL20-0GJ0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808W10 CC (6GK6015-0AL20-0GJ1) <BIOS_V1.0.212N
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
References
-
insyde.com
/security-pledge
vendor-advisory
-
insyde.com
/security-pledge/SA-2022050
vendor-advisory
Sources
- CVE List CVE-2022-33908
- NVD CVE-2022-33908
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.