[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81d016a4-891c-47e6-8a85-7cd9e5661729@google.com>
Date: Sun, 22 May 2022 18:24:47 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: John Allen <john.allen@....com>
cc: herbert@...dor.apana.org.au, linux-crypto@...r.kernel.org,
seanjc@...gle.com, Thomas.Lendacky@....com, Ashish.Kalra@....com,
linux-kernel@...r.kernel.org, theflow@...gle.com,
pgonda@...gle.com, stable@...r.kernel.org
Subject: Re: [PATCH v4] crypto: ccp - Use kzalloc for sev ioctl interfaces
to prevent kernel memory leak
On Wed, 18 May 2022, 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 and memset the data buffer to zero
> in sev_ioctl_do_platform_status.
>
> Fixes: 38103671aad3 ("crypto: ccp: Use the stack and common buffer for status commands")
> Fixes: e799035609e15 ("crypto: ccp: Implement SEV_PEK_CSR ioctl command")
> Fixes: 76a2b524a4b1d ("crypto: ccp: Implement SEV_PDH_CERT_EXPORT ioctl command")
> Fixes: d6112ea0cb344 ("crypto: ccp - introduce SEV_GET_ID2 command")
> Cc: stable@...r.kernel.org
> Reported-by: Andy Nguyen <theflow@...gle.com>
> Suggested-by: David Rientjes <rientjes@...gle.com>
> Suggested-by: Peter Gonda <pgonda@...gle.com>
> Signed-off-by: John Allen <john.allen@....com>
Acked-by: David Rientjes <rientjes@...gle.com>
Thanks John!
Powered by blists - more mailing lists