From: Jason Wang <jasowang@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Francisco Iglesias <frasse.iglesias@gmail.com>,
Jason Wang <jasowang@redhat.com>
Subject: [PULL V2 17/17] net/tap: Avoid variable-length array
Date: Mon, 18 Sep 2023 16:31:32 +0800 [thread overview]
Message-ID: <20230918083132.55423-18-jasowang@redhat.com> (raw)
In-Reply-To: <20230918083132.55423-1-jasowang@redhat.com>
From: Peter Maydell <peter.maydell@linaro.org>
Use a heap allocation instead of a variable length array in
tap_receive_iov().
The codebase has very few VLAs, and if we can get rid of them all we
can make the compiler error on new additions. This is a defensive
measure against security bugs where an on-stack dynamic allocation
isn't correctly size-checked (e.g. CVE-2021-3527).
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Francisco Iglesias <frasse.iglesias@gmail.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
net/tap.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/tap.c b/net/tap.c
index bcea8d0..c23d032 100644
--- a/net/tap.c
+++ b/net/tap.c
@@ -118,10 +118,11 @@ static ssize_t tap_receive_iov(NetClientState *nc, const struct iovec *iov,
{
TAPState *s = DO_UPCAST(TAPState, nc, nc);
const struct iovec *iovp = iov;
- struct iovec iov_copy[iovcnt + 1];
+ g_autofree struct iovec *iov_copy = NULL;
struct virtio_net_hdr_mrg_rxbuf hdr = { };
if (s->host_vnet_hdr_len && !s->using_vnet_hdr) {
+ iov_copy = g_new(struct iovec, iovcnt + 1);
iov_copy[0].iov_base = &hdr;
iov_copy[0].iov_len = s->host_vnet_hdr_len;
memcpy(&iov_copy[1], iov, iovcnt * sizeof(*iov));
--
2.7.4
next prev parent reply other threads:[~2023-09-18 8:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 8:31 [PULL V2 00/17] Net patches Jason Wang
2023-09-18 8:31 ` [PULL V2 01/17] tap: Add USO support to tap device Jason Wang
2023-09-18 8:31 ` [PULL V2 02/17] tap: Add check for USO features Jason Wang
2023-09-18 8:31 ` [PULL V2 03/17] virtio-net: Add USO flags to vhost support Jason Wang
2023-09-18 8:31 ` [PULL V2 04/17] virtio-net: Add support for USO features Jason Wang
2023-09-18 8:31 ` [PULL V2 05/17] igb: remove TCP ACK detection Jason Wang
2023-09-18 8:31 ` [PULL V2 06/17] igb: rename E1000E_RingInfo_st Jason Wang
2023-09-18 8:31 ` [PULL V2 07/17] igb: RX descriptors guest writting refactoring Jason Wang
2023-09-18 8:31 ` [PULL V2 08/17] igb: RX payload " Jason Wang
2023-09-18 8:31 ` [PULL V2 09/17] igb: add IPv6 extended headers traffic detection Jason Wang
2023-09-18 8:31 ` [PULL V2 10/17] igb: packet-split descriptors support Jason Wang
2023-09-18 8:31 ` [PULL V2 11/17] e1000e: rename e1000e_ba_state and e1000e_write_hdr_to_rx_buffers Jason Wang
2023-09-18 8:31 ` [PULL V2 12/17] tests: bump libvirt-ci for libasan and libxdp Jason Wang
2023-09-18 8:31 ` [PULL V2 13/17] net: add initial support for AF_XDP network backend Jason Wang
2023-09-18 8:31 ` [PULL V2 14/17] hw/net/fsl_etsec/rings.c: Avoid variable length array Jason Wang
2023-09-18 8:31 ` [PULL V2 15/17] hw/net/rocker: " Jason Wang
2023-09-18 8:31 ` [PULL V2 16/17] net/dump: " Jason Wang
2023-09-18 8:31 ` Jason Wang [this message]
2023-09-19 19:12 ` [PULL V2 00/17] Net patches Stefan Hajnoczi
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=20230918083132.55423-18-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=frasse.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).