Linux crypto/ccp - SEV platform shutdown error handling: The ccp driver's SEV/SNP platform shutdown path could

Impact

The ccp driver's SEV/SNP platform shutdown path could be called without a valid error pointer, dereferencing it and panicking the host. Since this is on the SEV platform teardown path, the crash lands during operations like driver unload or SNP re-initialisation - the exact moments you are already doing maintenance on a confidential-computing host.

Who can reach it

Local, in the host's SEV platform management path; reachable by whatever drives SEV init/shutdown, i.e. host administration rather than tenants.

What to do

Fixed in the Linux kernel - KVM/x86 SEV code or the ccp/PSP driver. Take the distro kernel update (RHEL/Rocky, Ubuntu, SLES) and **reboot the host**; SEV/SNP hypervisor paths cannot be live-patched in any meaningful way, and SNP platform init/shutdown is not safe to cycle under running guests. Drain confidential-VM tenants, reboot, then re-admit. No firmware, VBIOS or AGESA step needed, which makes this one of the cheaper classes of SEV fix to roll out.

References