KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak

KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak

For some sev ioctl interfaces, the length parameter that is passed maybe
less than or equal to SEV_FW_BLOB_MAX_SIZE, but larger than the data
that PSP firmware returns. In this case, kmalloc will allocate memory
that is the size of the input rather than the size of the data.
Since PSP firmware doesn't fully overwrite the allocated buffer, these
sev ioctl interface may return uninitialized kernel slab memory.

Reported-by: Andy Nguyen <theflow@google.com>
Suggested-by: David Rientjes <rientjes@google.com>
Suggested-by: Peter Gonda <pgonda@google.com>
Cc: kvm@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Fixes: d6b4ad578516a ("KVM: SVM: Move SEV code to separate file")
Fixes: 4e010b15d9ae7 ("KVM: SVM: add support for SEV attestation command")
Fixes: 395f95ab67c49 ("KVM: SVM: Add KVM_SEV SEND_START command")
Fixes: e281ff5bf5f3e ("KVM: SVM: Add KVM_SEND_UPDATE_DATA command")
Fixes: 95f62b2be194f ("KVM: x86: Account a variety of miscellaneous allocations")
Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
Reviewed-by: Peter Gonda <pgonda@google.com>
Message-Id: <20220516154310.3685678-1-Ashish.Kalra@amd.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>