From: John Allen <john.allen@amd.com>
To: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Cc: seanjc@google.com, Thomas.Lendacky@amd.com, Ashish.Kalra@amd.com,
linux-kernel@vger.kernel.org, theflow@google.com,
rientjes@google.com, pgonda@google.com
Subject: Re: [PATCH] crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory leak
Date: Thu, 12 May 2022 16:51:58 -0500 [thread overview]
Message-ID: <Yn2BflKqBSybybC/@dell9853host> (raw)
In-Reply-To: <20220512203455.253357-1-john.allen@amd.com>
On Thu, May 12, 2022 at 08:34:55PM +0000, John Allen wrote:
> For some sev ioctl interfaces, input may be passed that is 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 buffer, the sev ioctl interfaces with the
> issue may return uninitialized slab memory.
>
> Currently, all of the ioctl interfaces in the ccp driver are safe, but
> to prevent future problems, change all ioctl interfaces that allocate
> memory with kmalloc to use kzalloc.
I should have CC'd stable@vger.kernel.org and added a Fixes tag for
this. I'll send a v2 with these, but I'll give it a couple days for
comments before I do.
Thanks,
John
>
> Reported-by: Andy Nguyen <theflow@google.com>
> Suggested-by: David Rientjes <rientjes@google.com>
> Suggested-by: Peter Gonda <pgonda@google.com>
> Signed-off-by: John Allen <john.allen@amd.com>
> ---
> drivers/crypto/ccp/sev-dev.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c
> index 6ab93dfd478a..e2298843ea8a 100644
> --- a/drivers/crypto/ccp/sev-dev.c
> +++ b/drivers/crypto/ccp/sev-dev.c
> @@ -604,7 +604,7 @@ static int sev_ioctl_do_pek_csr(struct sev_issue_cmd *argp, bool writable)
> if (input.length > SEV_FW_BLOB_MAX_SIZE)
> return -EFAULT;
>
> - blob = kmalloc(input.length, GFP_KERNEL);
> + blob = kzalloc(input.length, GFP_KERNEL);
> if (!blob)
> return -ENOMEM;
>
> @@ -828,7 +828,7 @@ static int sev_ioctl_do_get_id2(struct sev_issue_cmd *argp)
> input_address = (void __user *)input.address;
>
> if (input.address && input.length) {
> - id_blob = kmalloc(input.length, GFP_KERNEL);
> + id_blob = kzalloc(input.length, GFP_KERNEL);
> if (!id_blob)
> return -ENOMEM;
>
> @@ -947,14 +947,14 @@ static int sev_ioctl_do_pdh_export(struct sev_issue_cmd *argp, bool writable)
> if (input.cert_chain_len > SEV_FW_BLOB_MAX_SIZE)
> return -EFAULT;
>
> - pdh_blob = kmalloc(input.pdh_cert_len, GFP_KERNEL);
> + pdh_blob = kzalloc(input.pdh_cert_len, GFP_KERNEL);
> if (!pdh_blob)
> return -ENOMEM;
>
> data.pdh_cert_address = __psp_pa(pdh_blob);
> data.pdh_cert_len = input.pdh_cert_len;
>
> - cert_blob = kmalloc(input.cert_chain_len, GFP_KERNEL);
> + cert_blob = kzalloc(input.cert_chain_len, GFP_KERNEL);
> if (!cert_blob) {
> ret = -ENOMEM;
> goto e_free_pdh;
> --
> 2.34.1
>
prev parent reply other threads:[~2022-05-12 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 20:34 [PATCH] crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory leak John Allen
2022-05-12 21:51 ` John Allen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yn2BflKqBSybybC/@dell9853host \
--to=john.allen@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgonda@google.com \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--cc=theflow@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox