From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jia Jia <physicalmtea@gmail.com>
Cc: "Jason Wang" <jaswangio@gmail.com>,
"Mike Christie" <michael.christie@oracle.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Nicholas Bellinger" <nab@linux-iscsi.org>,
"Asias He" <asias@redhat.com>,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vhost-scsi: fix event queue iov out-of-bounds
Date: Mon, 2 Nov 2026 09:15:04 -0500 [thread overview]
Message-ID: <20261102091441-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260904005240.502787-1-physicalmtea@gmail.com>
On Fri, Sep 04, 2026 at 08:52:40AM +0800, Jia Jia wrote:
> vhost_scsi_do_evt_work() uses vq->iov[out] after vhost_get_vq_desc()
> without checking that the descriptor chain contains an input segment.
> vq->iov has UIO_MAXIOV entries (1024). A chain of 1024 output-only
> descriptors yields out == 1024 and in == 0, so the length check reads
> one past the end of the array.
>
> With a host-side harness that sets VHOST_SCSI_SET_EVENTS_MISSED and
> kicks an event queue filled with 1024 OUT descriptors, UBSAN reports:
>
> UBSAN: array-index-out-of-bounds in drivers/vhost/scsi.c:611:14
> index 1024 is out of range for type 'iovec [1024]'
>
> Call Trace:
> <TASK>
> dump_stack_lvl+0x5f/0x90
> dump_stack+0x10/0x18
> ubsan_epilogue+0x9/0x39
> __ubsan_handle_out_of_bounds.cold+0x50/0x55
> vhost_scsi_complete_events+0x55f/0x5a0 [vhost_scsi]
> vhost_scsi_evt_work+0x17/0x30 [vhost_scsi]
> vhost_run_work_list+0x8e/0xd0 [vhost]
> vhost_task_fn+0xe1/0x210
> ret_from_fork+0x348/0x540
> ret_from_fork_asm+0x1a/0x30
> </TASK>
>
> Require at least one input descriptor before indexing iov[out], and
> treat a pure-output chain as a missed event like other invalid event
> buffers.
>
> Fixes: a6c9af87363c ("tcm_vhost: Add hotplug/hotunplug support")
> Signed-off-by: Jia Jia <physicalmtea@gmail.com>
Applied an alternative more comprehensive patch, credited you.
> ---
> drivers/vhost/scsi.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c
> index 9a1253b9d8c5..9b5f07f52b0c 100644
> --- a/drivers/vhost/scsi.c
> +++ b/drivers/vhost/scsi.c
> @@ -608,9 +608,10 @@
> return;
> }
>
> - if ((vq->iov[out].iov_len != sizeof(struct virtio_scsi_event))) {
> + if (!in ||
> + vq->iov[out].iov_len != sizeof(struct virtio_scsi_event)) {
> vq_err(vq, "Expecting virtio_scsi_event, got %zu bytes\n",
> - vq->iov[out].iov_len);
> + in ? vq->iov[out].iov_len : 0);
> vs->vs_events_missed = true;
> return;
> }
> --
> 2.43.0
prev parent reply other threads:[~2026-11-02 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 0:52 Jia Jia
2026-11-02 14:15 ` 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=20261102091441-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=asias@redhat.com \
--cc=eperezma@redhat.com \
--cc=jaswangio@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=nab@linux-iscsi.org \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=physicalmtea@gmail.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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
all inboxes | Powered by JetHome®