All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Victor Tom <vv474172261@gmail.com>,
	qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH] virtio-net: fix map leaking on error during receive
Date: Tue, 8 Mar 2022 01:56:49 -0500	[thread overview]
Message-ID: <20220308015601-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220308055642.20961-1-jasowang@redhat.com>

On Tue, Mar 08, 2022 at 01:56:42PM +0800, Jason Wang wrote:
> Commit bedd7e93d0196 ("virtio-net: fix use after unmap/free for sg")
> tries to fix the use after free of the sg by caching the virtqueue
> elements in an array and unmap them at once after receiving the
> packets, But it forgot to unmap the cached elements on error which
> will lead to leaking of mapping and other unexpected results.
> 
> Fixing this by detaching the cached elements on error. This addresses
> CVE-2022-26353.


Pls use a tag:

Fixes: CVE-2022-26353


Besides that

Reviewed-by: Michael S. Tsirkin <mst@redhat.com>

Feel free to merge.

> Reported-by: Victor Tom <vv474172261@gmail.com>
> Cc: qemu-stable@nongnu.org
> Fixes: bedd7e93d0196 ("virtio-net: fix use after unmap/free for sg")
> Signed-off-by: Jason Wang <jasowang@redhat.com>

> ---
>  hw/net/virtio-net.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> index cf8ab0f8af..65b61c836c 100644
> --- a/hw/net/virtio-net.c
> +++ b/hw/net/virtio-net.c
> @@ -1867,6 +1867,7 @@ static ssize_t virtio_net_receive_rcu(NetClientState *nc, const uint8_t *buf,
>  
>  err:
>      for (j = 0; j < i; j++) {
> +        virtqueue_detach_element(q->rx_vq, elems[j], lens[j]);
>          g_free(elems[j]);
>      }
>  
> -- 
> 2.25.1



  reply	other threads:[~2022-03-08  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  5:56 [PATCH] virtio-net: fix map leaking on error during receive Jason Wang
2022-03-08  6:56 ` Michael S. Tsirkin [this message]
2022-03-08  7:02   ` Jason Wang

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=20220308015601-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=vv474172261@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.