The issue is related to a missing `sev decommission` in `sev receive start`, which can result in subsequent SEV launch failures due to firmware memory leaks. According to AMD's SEV API, `RECEIVE START` generates a new guest context and needs to be paired with `DECOMMISSION`. The `RECEIVE START` command is the only command other than `LAUNCH START` that generates a new guest context and guest handle. Local network access enables an attack, but no exploit is yet available.