GPU VulnDB

Database/NVIDIA / GPU stack

AMD Platform Configuration Blob (APCB) SMM driver, EPYC and Instinct MI300A/MI300C: Incorrect use of the UEFI

CVE-2025-54502NVIDIA / GPU stackAPCB SMM driver LocateProtocol misusecurated

Impact

Incorrect use of the UEFI LocateProtocol boot service in the APCB SMM driver lets ring 0 escalate to SMM and execute arbitrary code. What makes this one worth flagging for AI operators specifically is the affected list: alongside EPYC 7002 through 9005 it explicitly includes AMD Instinct MI300A and the MI300C-based EPYC 9V64H. Those are accelerator nodes, frequently sold bare metal or with device passthrough, where the customer legitimately has ring 0. Ring -2 code on an MI300A node persists across every tenant that follows.

Who can reach it

Privileged local attacker at ring 0 - on a bare-metal MI300A rental that is the customer by design.

What to do

Platform Initialization firmware per AMD-SB-7054: MI300A 1.0.0.C (OEM release 2025-12-11), MI300C 1.0.0.3 (2025-12-10), TurinPI 1.0.0.9 for EPYC 9005 (2025-12-31), GenoaPI 1.0.0.H, MilanPI 1.0.0.J, RomePI 1.0.0.P. BIOS flash and reboot per node - on an Instinct fleet that means evicting whatever is training on it. Given the bare-metal exposure, prioritize Instinct nodes over general-purpose EPYC and add a firmware measurement to the between-tenants checklist.

References

https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-7054.htmlhttps://nvd.nist.gov/vuln/detail/CVE-2025-54502

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.