From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Junjie Cao <junjie.cao@intel.com>
Cc: qemu-devel@nongnu.org, jasowang@redhat.com, mst@redhat.com,
yuri.benditovich@daynix.com, akihiko.odaki@daynix.com,
qemu-stable@nongnu.org
Subject: Re: [PATCH] virtio-net: validate RSS indirections_len in post_load
Date: Mon, 23 Mar 2026 13:41:40 +0000 [thread overview]
Message-ID: <acFDFHsh8Rjhfncc@redhat.com> (raw)
In-Reply-To: <20260323131531.1976-1-junjie.cao@intel.com>
On Mon, Mar 23, 2026 at 09:15:31PM +0800, 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 crafted migration stream can set indirections_len to 0. Even if it
The migration stream originating from the source QEMU is trusted.
Is there a problem you can demonstrate with regular QEMU commands
/ versions, not crafting a malicious migration stream.
> 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.
>
> 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>
> ---
> hw/net/virtio-net.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> index 2a5d642a64..3038836098 100644
> --- a/hw/net/virtio-net.c
> +++ b/hw/net/virtio-net.c
> @@ -3427,6 +3427,15 @@ static int virtio_net_rss_post_load(void *opaque, int version_id)
> n->rss_data.supported_hash_types = VIRTIO_NET_RSS_SUPPORTED_HASHES;
> }
>
> + if (n->rss_data.indirections_len == 0 ||
> + n->rss_data.indirections_len > VIRTIO_NET_RSS_MAX_TABLE_LEN ||
> + !is_power_of_2(n->rss_data.indirections_len)) {
> + error_report("virtio-net: saved image has invalid RSS "
> + "indirections_len: %u",
> + n->rss_data.indirections_len);
> + return -EINVAL;
> + }
> +
> return 0;
> }
>
> --
> 2.43.0
>
>
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-03-23 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:15 [PATCH] virtio-net: validate RSS indirections_len in post_load Junjie Cao
2026-03-23 13:41 ` Daniel P. Berrangé [this message]
2026-03-23 13:53 ` Peter Maydell
2026-03-23 13:57 ` Michael S. Tsirkin
2026-03-23 14:56 ` Daniel P. Berrangé
2026-03-23 15:25 ` Peter Maydell
2026-03-23 15:58 ` Daniel P. Berrangé
2026-03-23 16:15 ` Peter Maydell
2026-03-23 16:45 ` Daniel P. Berrangé
2026-03-23 14:11 ` Daniel P. Berrangé
2026-03-23 15:33 ` Peter Maydell
2026-03-23 13:56 ` Michael S. Tsirkin
2026-03-24 6:04 ` Junjie Cao
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=acFDFHsh8Rjhfncc@redhat.com \
--to=berrange@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=jasowang@redhat.com \
--cc=junjie.cao@intel.com \
--cc=mst@redhat.com \
--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