CVE-2021-26322

7.5 HIGH

📋 TL;DR

This vulnerability in AMD platform security processors (PSP) allows potential recovery of encrypted private keys due to insufficient initialization vector (IV) randomness. Attackers could decrypt platform keys, compromising secure boot and firmware integrity. Affects systems with AMD EPYC, Ryzen, and Athlon processors.

💻 Affected Systems

Products:
  • AMD EPYC processors
  • AMD Ryzen processors
  • AMD Athlon processors
Versions: Multiple generations prior to firmware updates
Operating Systems: All operating systems running on affected hardware
Default Config Vulnerable: ⚠️ Yes
Notes: Requires physical access or administrative privileges to exploit. Affects systems with AMD Secure Processor firmware.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of platform security keys enabling persistent firmware-level backdoors, secure boot bypass, and extraction of sensitive cryptographic material.

🟠

Likely Case

Extraction of platform keys allowing firmware modification, secure boot circumvention, and potential credential theft from encrypted storage.

🟢

If Mitigated

Limited impact with proper firmware updates and secure boot enforcement, though residual risk remains for unpatched systems.

🌐 Internet-Facing: LOW
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: HIGH

Exploitation requires administrative access or physical access to the system. No public exploits available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: AMD AGESA firmware updates (specific versions vary by platform)

Vendor Advisory: https://www.amd.com/en/corporate/product-security/bulletin/amd-sb-1021

Restart Required: Yes

Instructions:

1. Check system manufacturer for BIOS/UEFI updates. 2. Download appropriate firmware update. 3. Apply update following manufacturer instructions. 4. Reboot system to complete installation.

🔧 Temporary Workarounds

Enable Secure Boot

all

Enforce secure boot to prevent unauthorized firmware modifications

Physical Security Controls

all

Restrict physical access to affected systems

🧯 If You Can't Patch

  • Isolate affected systems from high-risk networks
  • Implement strict access controls and monitoring for physical access

🔍 How to Verify

Check if Vulnerable:

Check system BIOS/UEFI version against manufacturer's patched versions. Use 'dmidecode' on Linux or system information tools on Windows.

Check Version:

Linux: 'sudo dmidecode -t bios' or 'cat /sys/class/dmi/id/bios_version'. Windows: 'wmic bios get smbiosbiosversion'

Verify Fix Applied:

Verify BIOS/UEFI version matches or exceeds patched version from manufacturer advisory.

📡 Detection & Monitoring

Log Indicators:

  • BIOS/UEFI firmware modification events
  • Secure boot violations
  • Unexpected firmware update attempts

Network Indicators:

  • Unusual outbound connections from management interfaces

SIEM Query:

EventID=12 OR EventID=13 (Windows System logs for firmware changes) OR kernel: 'Secure boot violation' (Linux audit logs)

🔗 References

📤 Share & Export