From: Junjie Cao <junjie.cao@intel.com>
To: qemu-devel@nongnu.org
Cc: jasowang@redhat.com, mst@redhat.com, yuri.benditovich@daynix.com,
akihiko.odaki@daynix.com, qemu-stable@nongnu.org,
junjie.cao@intel.com
Subject: [PATCH] virtio-net: validate RSS indirections_len in post_load
Date: Mon, 23 Mar 2026 21:15:31 +0800 [thread overview]
Message-ID: <20260323131531.1976-1-junjie.cao@intel.com> (raw)
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
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
next reply other threads:[~2026-03-23 13:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:15 Junjie Cao [this message]
2026-03-23 13:41 ` [PATCH] virtio-net: validate RSS indirections_len in post_load Daniel P. Berrangé
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=20260323131531.1976-1-junjie.cao@intel.com \
--to=junjie.cao@intel.com \
--cc=akihiko.odaki@daynix.com \
--cc=jasowang@redhat.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