CVE-2021-26402

HIGH

7.1

CVSS Score

Published: January 10, 2023 at 08:56 PM UTC

Updated: June 17, 2026 at 03:43 AM UTC

100 products affected across 1 vendorEpyc 7713P FirmwareEpyc 7663 FirmwareEpyc 7413 Firmware

Using 2nd Gen EPYC by AMD?

Get instant alerts when new vulnerabilities affect 2nd Gen EPYC - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.1

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

Insufficient bounds checking in ASP (AMD Secure Processor) firmware while handling BIOS mailbox commands, may allow an attacker to write partially-controlled data out-of-bounds to SMM or SEV-ES regions which may lead to a potential loss of integrity and availability.

Affected

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

Epyc 7002 Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7002 (same device)

Epyc 7003 Firmware · AMD

95%

v < milanpi_1.0.0.4

Affected range stops below milanpi_1.0.0.4, so it looks safe — our inference, not a vendor statement

Epyc 7232P Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7232p (same device)

Epyc 7252 Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7252 (same device)

Epyc 7262 Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7262 (same device)

Epyc 7272 Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7272 (same device)

Epyc 7282 Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7282 (same device)

Epyc 72F3 Firmware · AMD

95%

v < milanpi_1.0.0.4

Affected range stops below milanpi_1.0.0.4, so it looks safe — our inference, not a vendor statement

amd-epyc-72f3 (same device)

Epyc 7302 Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7302 (same device)

Epyc 7302P Firmware · AMD

95%

v < romepi_1.0.0.c

Affected range stops below romepi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7302p (same device)

Remediation

No guide yet

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

Patch and advisory references

https://www.amd.com/en/corporate/product-security/bulletin/AMD-SB-1032

References (1)

Vendor Advisory

Source: [email protected]

https://www.amd.com/en/corporate/product-security/bulletin/AMD-SB-1032

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

7.1HIGHCISA-ADP

Attack Vector: LOCAL
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-787

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.

Create account Sign in

Free plan, no card