CVE-2021-26344 is a high severity (CVSS 7.2) out-of-bounds memory write in the AMD PSP1 Configuration Block (APCB) handling on AMD EPYC processors. It requires the ability to modify and sign a BIOS image. AMD bulletin AMD-SB-3003 lists fixed platform initialization firmware by processor generation.
What's affected
- The NVD record lists the AMD EPYC 7203 and 7203P and their firmware. AMD bulletin AMD-SB-3003 is wider and covers several EPYC generations.
- For 3rd Gen EPYC (Milan), the bulletin lists MilanPI 1.0.0.5 (2021-08-05) as the fix for this CVE.
- For 2nd Gen EPYC (Rome), it lists RomePI 1.0.0.C (2021-07-22).
- For 1st Gen EPYC (Naples), the bulletin says no fix is planned for this CVE.
- The bulletin also gives minimum PI versions that cover every CVE it lists, which are newer than the ones for this CVE alone. Your server vendor ships the actual BIOS, so ask for their build that includes the PI version.
- Scope note: the record names two models, but the bulletin covers more. Use the bulletin for your processor family.
How to check if you're exposed
Identify the processor model and BIOS version on your servers, then ask your server vendor which AGESA or platform initialization version that BIOS contains.
sudo dmidecode -t bios
sudo dmidecode -s processor-version
Compare the PI version with the bulletin table for your generation. On many systems the PI version is reported in the vendor BIOS release notes and not in the OS.
What to do now
- List server models, CPU generations and BIOS versions across your estate.
- Check the AMD bulletin AMD-SB-3003 for your generation, and your server vendor release notes for a BIOS carrying the PI version.
- Schedule BIOS updates through the vendor tools, with a rollback plan, because firmware flashes need reboots.
- Restrict who can reach BIOS settings, the UEFI shell and out of band management interfaces.
- For Naples systems, where AMD plans no fix for this CVE, rely on physical and management access controls and plan hardware replacement.
Why it matters
The class is CWE-787, out-of-bounds write. The record says an attacker with the ability to modify the BIOS image, and to sign the result, could change the APCB block and reach arbitrary code execution. Those preconditions are strict, so the CVSS vector shows local access, high complexity and high privileges.
Firmware flaws matter because code that runs below the operating system is hard to detect and survives reinstallation. The realistic exposure is administrators and anyone who controls firmware update tooling, so the right controls are about who can flash or change firmware, and how firmware images are signed and checked.
Quick check
Is this reachable from the network?
No. The record gives a local vector and requires the ability to modify and sign a BIOS image.
Where do I get the fix?
From your server or board vendor as a BIOS update that includes the AMD platform initialization version listed in the bulletin.
Sources
Last reviewed: 19 October 2026.