From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
jasowang@redhat.com, lvivier@redhat.com
Subject: Re: [PATCH] vhost: Add a defensive check in vhost_commit against wrong deallocation
Date: Tue, 3 Oct 2023 08:43:58 -0400 [thread overview]
Message-ID: <20231003084047-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230913074657.523530-1-eric.auger@redhat.com>
On Wed, Sep 13, 2023 at 09:46:57AM +0200, Eric Auger wrote:
> In vhost_commit(), it may happen that dev->mem_sections and
> dev->tmp_sections are equal,
Could you please explain a bit more how this can happen?
I don't see how.
> in which case, unconditionally
> freeing old_sections at the end of the function will also free
> dev->mem_sections used on subsequent call leading to a segmentation
> fault.
>
> Check this situation before deallocating memory.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Fixes: c44317efecb2 ("vhost: Build temporary section list and deref
> after commit")
> CC: QEMU Stable <qemu-stable@nongnu.org>
>
> ---
>
> This SIGSEV condition can be reproduced with
> https://lore.kernel.org/all/20230904080451.424731-1-eric.auger@redhat.com/#r
> This is most probably happening in a situation where the memory API is
> used in a wrong manner but well.
sounds like misusing the memory API can lead to all kind of mischief.
> ---
> hw/virtio/vhost.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
> index e2f6ffb446..c02c599ef0 100644
> --- a/hw/virtio/vhost.c
> +++ b/hw/virtio/vhost.c
> @@ -545,6 +545,11 @@ static void vhost_commit(MemoryListener *listener)
> dev->mem_sections = dev->tmp_sections;
> dev->n_mem_sections = dev->n_tmp_sections;
>
> + if (old_sections == dev->mem_sections) {
> + assert(n_old_sections == dev->n_mem_sections);
> + return;
> + }
> +
> if (dev->n_mem_sections != n_old_sections) {
> changed = true;
> } else {
> --
> 2.41.0
next prev parent reply other threads:[~2023-10-03 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 7:46 [PATCH] vhost: Add a defensive check in vhost_commit against wrong deallocation Eric Auger
2023-09-14 3:46 ` Jason Wang
2023-09-14 7:45 ` Eric Auger
2023-10-03 12:43 ` Michael S. Tsirkin [this message]
2023-10-03 13:16 ` Eric Auger
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=20231003084047-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.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 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.