Skip to content
Fencer Vulns
medium 4.4

CVE-2021-26328 json

Failure to verify the mode of CPU execution at the time of SNP_INIT may lead to a potential loss of memory integrity for SNP guests.

published 2023-01-10 3 y ago modified 2026-06-17 4 mo ago also EUVD-2021-13134

cvss
4.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

Failure to verify the mode of CPU execution at the time of SNP_INIT may lead to a potential loss of memory integrity for SNP guests.

Patch / fix

  • amd epyc_7003_firmware milanpi_1.0.0.8
  • amd epyc_72f3_firmware milanpi_1.0.0.8
  • amd epyc_7313_firmware milanpi_1.0.0.8
  • amd epyc_7313p_firmware milanpi_1.0.0.8
  • amd epyc_7343_firmware milanpi_1.0.0.8
  • amd epyc_7373x_firmware milanpi_1.0.0.8
  • amd epyc_73f3_firmware milanpi_1.0.0.8
  • amd epyc_7413_firmware milanpi_1.0.0.8
  • amd epyc_7443_firmware milanpi_1.0.0.8
  • amd epyc_7443p_firmware milanpi_1.0.0.8
  • amd epyc_7453_firmware milanpi_1.0.0.8
  • amd epyc_74f3_firmware milanpi_1.0.0.8
  • amd epyc_7513_firmware milanpi_1.0.0.8
  • amd epyc_7543_firmware milanpi_1.0.0.8
  • amd epyc_7543p_firmware milanpi_1.0.0.8
  • amd epyc_7573x_firmware milanpi_1.0.0.8
  • amd epyc_75f3_firmware milanpi_1.0.0.8
  • amd epyc_7643_firmware milanpi_1.0.0.8
  • amd epyc_7663_firmware milanpi_1.0.0.8
  • amd epyc_7713_firmware milanpi_1.0.0.8

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
19 mo ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
NVD 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
CNA 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Affected products

  • AMD 3rd Gen EPYC

Classification

Weakness
  • CWE-358 Improperly Implemented Security Check for Standard

References

Sources

Fencer Vulns 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.