From: Sean Christopherson <seanjc@google.com>
To: Ashish Kalra <ashkalra@amd.com>
Cc: Peter Gonda <pgonda@google.com>,
Ashish Kalra <Ashish.Kalra@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Joerg Roedel <joro@8bytes.org>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
Borislav Petkov <bp@alien8.de>,
the arch/x86 maintainers <x86@kernel.org>,
kvm list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Nguyen <theflow@google.com>,
David Rientjes <rientjes@google.com>,
John Allen <john.allen@amd.com>
Subject: Re: [PATCH] KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel memory leak.
Date: Fri, 13 May 2022 19:56:01 +0000 [thread overview]
Message-ID: <Yn630RFKQiiMRnnf@google.com> (raw)
In-Reply-To: <51219031-935d-8da4-7d8f-80073a79f794@amd.com>
On Fri, May 13, 2022, Ashish Kalra wrote:
> Hello Sean & Peter,
> > Looking through other copy_to_user() calls:
> >
> > - "blob" in sev_ioctl_do_pek_csr()
> > - "id_blob" in sev_ioctl_do_get_id2()
> > - "pdh_blob" and "cert_blob" in sev_ioctl_do_pdh_export()
>
> These functions are part of the ccp driver and a fix for them has already
> been sent upstream to linux-crypto@vger.kernel.org and
> linux-kernel@vger.kernel.org:
>
> [PATCH] crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel
> memory leak
Ha, that's why I was getting a bit of deja vu. I saw that fly by and then got it
confused with this patch.
next prev parent reply other threads:[~2022-05-13 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 20:23 [PATCH] KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel memory leak Ashish Kalra
2022-05-12 22:02 ` Borislav Petkov
2022-05-13 13:37 ` Peter Gonda
2022-05-13 14:49 ` Sean Christopherson
2022-05-13 18:11 ` Ashish Kalra
2022-05-13 19:56 ` Sean Christopherson [this message]
2022-05-13 20:09 ` Peter Gonda
2022-05-13 20:47 ` Ashish Kalra
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=Yn630RFKQiiMRnnf@google.com \
--to=seanjc@google.com \
--cc=Ashish.Kalra@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=ashkalra@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=john.allen@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=theflow@google.com \
--cc=x86@kernel.org \
/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