From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Junjie Cao <junjie.cao@intel.com>,
qemu-devel@nongnu.org, jasowang@redhat.com,
yuri.benditovich@daynix.com, berrange@redhat.com,
peter.maydell@linaro.org, qemu-stable@nongnu.org
Subject: Re: [PATCH v2] virtio-net: validate RSS indirections_len in post_load
Date: Wed, 13 May 2026 05:59:45 -0400 [thread overview]
Message-ID: <20260513055917-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f4e8921d-d1fb-4ff6-95d2-de6b44a5941e@tls.msk.ru>
On Wed, May 13, 2026 at 09:42:59AM +0300, Michael Tokarev wrote:
> On 24.03.2026 09:01, Junjie Cao wrote:
> > virtio_net_handle_rss() enforces that indirections_len is a non-zero
> > power of two no larger than VIRTIO_NET_RSS_MAX_TABLE_LEN, but
> > virtio_net_rss_post_load() applies none of these checks to values
> > restored from the migration stream.
> >
> > A corrupted save file or crafted migration stream can set
> > indirections_len to 0. Even if it also clears redirect,
> > virtio_load() calls set_features_nocheck() after the device vmstate
> > (including the RSS subsection and its post_load) has already been
> > loaded, re-deriving redirect from the negotiated guest features.
> > When VIRTIO_NET_F_RSS was negotiated, redirect is set back to true
> > regardless of the migration stream value. The receive path then
> > computes
> >
> > hash & (indirections_len - 1) /* wraps to 0xFFFFFFFF via int promotion */
> >
> > and uses the result to index into indirections_table, which was not
> > allocated by the VMState loader when the element count is zero (see
> > vmstate_handle_alloc()), resulting in a NULL pointer dereference that
> > crashes QEMU:
> >
> > #0 virtio_net_process_rss ../hw/net/virtio-net.c:1901
> > #1 virtio_net_receive_rcu ../hw/net/virtio-net.c:1921
> > #2 virtio_net_do_receive ../hw/net/virtio-net.c:2061
> > #3 nc_sendv_compat ../net/net.c:823
> > #4 qemu_deliver_packet_iov ../net/net.c:870
> >
> > The RSS subsection is only loaded when rss_data.enabled is true (via
> > virtio_net_rss_needed()), and the command path always produces
> > indirections_len in {1, 2, 4, …, 128}, so an unconditional check
> > cannot reject a legitimate migration stream.
> >
> > Factor the validation into virtio_net_rss_indirections_len_valid()
> > and call it from both virtio_net_handle_rss() and
> > virtio_net_rss_post_load().
> >
> > Fixes: e41b711485e5 ("virtio-net: add migration support for RSS and hash report")
> > Cc: qemu-stable@nongnu.org
> > Signed-off-by: Junjie Cao <junjie.cao@intel.com>
>
> Hi!
>
> Has this patch been forgotten, or is it not needed anymore?
>
> I'm preparing next set of the stable qemu releases, if it's needed,
> it would be nice if it lands in the master branch in the next 10
> days.
>
> Thanks,
>
> /mjt
I'll pick it now, thanks.
prev parent reply other threads:[~2026-05-13 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 6:01 [PATCH v2] virtio-net: validate RSS indirections_len in post_load Junjie Cao
2026-05-13 6:42 ` Michael Tokarev
2026-05-13 7:02 ` Philippe Mathieu-Daudé
2026-05-13 9:59 ` 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=20260513055917-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=berrange@redhat.com \
--cc=jasowang@redhat.com \
--cc=junjie.cao@intel.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=yuri.benditovich@daynix.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