AMD Secure Processor PCI driver - input validation: Improper input validation in the ASP PCI driver lets a local

Impact

Improper input validation in the ASP PCI driver lets a local attacker trigger a buffer overflow and crash the node. Practically this is availability: a tenant-adjacent process that can reach the driver can take the host down, and on a GPU node that means every co-resident training job dies with it.

Who can reach it

Local, through the ASP PCI driver interface. Not tenant-container reachable on a normally configured node - the ccp/PSP device is not handed to workload containers.

What to do

Fixed in AMD reference firmware (AGESA / SEV firmware) and delivered to you only as an OEM SBIOS/BIOS package - Dell, HPE, Supermicro, Lenovo, Gigabyte and the ODMs each rebuild and requalify AMD's AGESA drop before it ships. **Expect months, not weeks**: AMD publishes the bulletin, the OEM ships BIOS somewhere between one and six months later, and for platforms past their support window it may never arrive at all. Applying it is a full node power cycle with the host drained - not a driver reload, not a live patch. Track it as a firmware campaign per server SKU, not per kernel version, and verify afterwards by reading back the SMU/PSP firmware version rather than trusting the BIOS revision string. There is also a kernel-side component (the ccp driver); take the distro kernel update as well as the BIOS, since the OEM firmware will lag.

References