From: "Michael S. Tsirkin" <mst@redhat.com>
To: gerben@altlinux.org
Cc: qemu-devel@nongnu.org, sdl.qemu@linuxtesting.org
Subject: Re: [PATCH] hw/virtio/virtio-pci: add defensive check for vector_irqfd
Date: Thu, 14 Aug 2025 09:07:32 -0400 [thread overview]
Message-ID: <20250814090615-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250814110830.14660-1-gerben@altlinux.org>
On Thu, Aug 14, 2025 at 02:08:08PM +0300, gerben@altlinux.org wrote:
> From: Denis Rastyogin <gerben@altlinux.org>
>
> Add a NULL check for proxy->vector_irqfd in
> virtio_pci_one_vector_unmask() before taking the irqfd path.
> This prevents potential access to uninitialized state if
> vector_irqfd is absent.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Reported-by: Alexey Appolonov <alexey@altlinux.org>
> Signed-off-by: Denis Rastyogin <gerben@altlinux.org>
I don't really understand what this description means. defensive against
what? found in what sense? what is the uninitialized state accessed?
when is the potential for this access?
> ---
> hw/virtio/virtio-pci.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> index 767216d795..07904f6f9b 100644
> --- a/hw/virtio/virtio-pci.c
> +++ b/hw/virtio/virtio-pci.c
> @@ -1015,7 +1015,11 @@ static int virtio_pci_one_vector_unmask(VirtIOPCIProxy *proxy,
> event_notifier_set(n);
> }
> } else {
> - ret = kvm_virtio_pci_irqfd_use(proxy, n, vector);
> + if (proxy->vector_irqfd) {
> + ret = kvm_virtio_pci_irqfd_use(proxy, n, vector);
> + } else {
> + ret = -EFAULT;
> + }
> }
> return ret;
> }
> --
> 2.42.2
prev parent reply other threads:[~2025-08-14 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 11:08 [PATCH] hw/virtio/virtio-pci: add defensive check for vector_irqfd gerben
2025-08-14 11:47 ` Philippe Mathieu-Daudé
2025-08-14 13:07 ` Michael S. Tsirkin [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=20250814090615-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=gerben@altlinux.org \
--cc=qemu-devel@nongnu.org \
--cc=sdl.qemu@linuxtesting.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;
as well as URLs for NNTP newsgroup(s).