AMD SEV firmware - incomplete memory cleanup (AMD-SB-3003): MULTI-TENANT ISOLATION: Incomplete memory cleanup

Impact

MULTI-TENANT ISOLATION: Incomplete memory cleanup in the SEV firmware allows corruption of guest private memory. The recurring pattern in this database - firmware that does not scrub or fully release state between uses - applied to the memory of confidential guests, where the whole product claim is that nobody but the guest can touch it.

Who can reach it

Local, privileged, on a host running SEV guests.

What to do

Fixed in AMD PI/AGESA firmware and delivered only as an OEM SBIOS package - AMD ships the PI drop to Dell, HPE, Supermicro, Lenovo and the ODMs, who each requalify before releasing BIOS. **Budget one to six months of OEM lag**, and note that several CVEs in this batch are marked 'no fix planned' on Naples (EPYC 7001) - for those the only remediation is retiring the hardware. Applying it means cordon, drain and a full power cycle per node; there is no driver reload, no live patch and no VBIOS step. Because this touches the SEV-SNP trust boundary, the update moves the platform TCB version: refresh VCEK certificates from AMD's KDS and update tenant attestation policy, or confidential guest launches will fail immediately after the BIOS lands.

References