From: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: arei.gonglei@huawei.com, mst@redhat.com, davem@davemloft.net,
jasowangio@gmail.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, linux-crypto@vger.kernel.org,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
Bryam Vargas <hexlabsecurity@proton.me>
Subject: Re: [PATCH] crypto: virtio: validate akcipher completion length
Date: Tue, 08 Sep 2026 11:37:30 +0200 [thread overview]
Message-ID: <7fc9c66a8d89113854ecf8cc54ecb0c5@oss.cyber.gouv.fr> (raw)
In-Reply-To: <ap_TatiabFuXiiad@gondor.apana.org.au>
On 2026-09-08 11:20, Herbert Xu wrote:
> On Fri, Aug 21, 2026 at 09:55:12AM +0000, Jérémy Jean wrote:
>> The device controls the used length returned for an akcipher request.
>> Subtracting the status byte without validating that length can
>> underflow
>> dst_len, while accepting a payload larger than the submitted
>> destination
>> can make sg_copy_from_buffer() read past the response buffer.
>>
>> Reject malformed completion lengths before updating dst_len or copying
>> the
>> response.
>>
>> Fixes: a36bd0ad9fbf ("virtio-crypto: adjust dst_len at ops callback")
>> Assisted-by: Codex:gpt-5
>> Signed-off-by: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
>> ---
>> drivers/crypto/virtio/virtio_crypto_akcipher_algs.c | 13
>> ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/crypto/virtio/virtio_crypto_akcipher_algs.c
>> b/drivers/crypto/virtio/virtio_crypto_akcipher_algs.c
>> index d8d452cac391..886032abae80 100644
>> --- a/drivers/crypto/virtio/virtio_crypto_akcipher_algs.c
>> +++ b/drivers/crypto/virtio/virtio_crypto_akcipher_algs.c
>> @@ -69,6 +69,7 @@ static void
>> virtio_crypto_dataq_akcipher_callback(struct virtio_crypto_request *
>> struct akcipher_request *akcipher_req =
>> container_of((void *)vc_akcipher_req, struct akcipher_request,
>> __ctx);
>> + unsigned int dst_len;
>> int error;
>>
>> switch (vc_req->status) {
>> @@ -88,9 +89,19 @@ static void
>> virtio_crypto_dataq_akcipher_callback(struct virtio_crypto_request *
>> }
>>
>> /* actual length may be less than dst buffer */
>> - akcipher_req->dst_len = len - sizeof(vc_req->status);
>
> This appears to have already been fixed by
>
> commit f77a956f6a19f9463ef1527c9d0cda50dded6b92
> Author: Bryam Vargas <hexlabsecurity@proton.me>
> Date: Mon Jun 22 01:52:15 2026 -0500
>
> crypto: virtio - bound the akcipher result length
>
> Please check that commit and see if it's sufficient or not.
>
> Thanks,
Hello,
Indeed, this fixes the bug.
Thanks for the pointer, I missed that patch.
Regards,
Jérémy
prev parent reply other threads:[~2026-09-08 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 9:55 [PATCH] crypto: virtio: validate akcipher completion length Jérémy Jean
2026-09-08 9:20 ` Herbert Xu
2026-09-08 9:37 ` Jérémy Jean [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=7fc9c66a8d89113854ecf8cc54ecb0c5@oss.cyber.gouv.fr \
--to=jeremy.jean@oss.cyber.gouv.fr \
--cc=arei.gonglei@huawei.com \
--cc=davem@davemloft.net \
--cc=eperezma@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=hexlabsecurity@proton.me \
--cc=jasowangio@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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