CVE-2021-26335 json
Improper input and range checking in the AMD Secure Processor (ASP) boot loader image header may allow an attacker to use attacker-controll…
published 2021-11-16 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-13141
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
Improper input and range checking in the AMD Secure Processor (ASP) boot loader image header may allow an attacker to use attacker-controlled values prior to signature validation potentially resulting in arbitrary code execution.
Patch / fix
- amd epyc_7003_firmware milanpi-sp3_1.0.0.4
- amd epyc_7002_firmware romepi-sp3_1.0.0.c
- amd epyc_7001_firmware naplespi-sp3_1.0.0.g
- amd epyc_72f3_firmware milanpi-sp3_1.0.0.4
- amd epyc_7313_firmware milanpi-sp3_1.0.0.4
- amd epyc_7313p_firmware milanpi-sp3_1.0.0.4
- amd epyc_7343_firmware milanpi-sp3_1.0.0.4
- amd epyc_73f3_firmware milanpi-sp3_1.0.0.4
- amd epyc_7413_firmware milanpi-sp3_1.0.0.4
- amd epyc_7443_firmware milanpi-sp3_1.0.0.4
- amd epyc_7443p_firmware milanpi-sp3_1.0.0.4
- amd epyc_7453_firmware milanpi-sp3_1.0.0.4
- amd epyc_74f3_firmware milanpi-sp3_1.0.0.4
- amd epyc_7513_firmware milanpi-sp3_1.0.0.4
- amd epyc_7543_firmware milanpi-sp3_1.0.0.4
- amd epyc_7543p_firmware milanpi-sp3_1.0.0.4
- amd epyc_75f3_firmware milanpi-sp3_1.0.0.4
- amd epyc_7643_firmware milanpi-sp3_1.0.0.4
- amd epyc_7663_firmware milanpi-sp3_1.0.0.4
- amd epyc_7713_firmware milanpi-sp3_1.0.0.4
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- AMD Ryzen™ Series
- AMD Athlon™ Series
References
Sources
- CVE List CVE-2021-26335
- NVD CVE-2021-26335
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.