From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Jason Wang <jasowang@redhat.com>, Jiri Pirko <jiri@resnulli.us>,
qemu-ppc@nongnu.org
Subject: Re: [PATCH 1/4] hw/net/fsl_etsec/rings.c: Avoid variable length array
Date: Thu, 24 Aug 2023 17:47:41 +0200 [thread overview]
Message-ID: <663d4cd3-50d5-d5db-bd43-efc55fe6bbf0@linaro.org> (raw)
In-Reply-To: <20230824153224.2517486-2-peter.maydell@linaro.org>
On 24/8/23 17:32, Peter Maydell wrote:
> In fill_rx_bd() we create a variable length array of size
> etsec->rx_padding. In fact we know that this will never be
> larger than 64 bytes, because rx_padding is set in rx_init_frame()
> in a way that ensures it is only that large. Use a fixed sized
> array and assert that it is big enough.
>
> Since padd[] is now potentially rather larger than the actual
> padding required, adjust the memset() we do on it to match the
> size that we write with cpu_physical_memory_write(), rather than
> clearing the entire array.
>
> 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>
> ---
> hw/net/fsl_etsec/rings.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/hw/net/fsl_etsec/rings.c b/hw/net/fsl_etsec/rings.c
> index 788463f1b62..2f2f359f7a5 100644
> --- a/hw/net/fsl_etsec/rings.c
> +++ b/hw/net/fsl_etsec/rings.c
> @@ -372,6 +372,12 @@ void etsec_walk_tx_ring(eTSEC *etsec, int ring_nbr)
> etsec->regs[TSTAT].value |= 1 << (31 - ring_nbr);
> }
>
> +/*
> + * rx_init_frame() ensures we never do more padding than this
> + * (checksum plus minimum data packet size)
> + */
> +#define MAX_RX_PADDING 64
> +
> static void fill_rx_bd(eTSEC *etsec,
> eTSEC_rxtx_bd *bd,
> const uint8_t **buf,
> @@ -380,9 +386,11 @@ static void fill_rx_bd(eTSEC *etsec,
> uint16_t to_write;
> hwaddr bufptr = bd->bufptr +
> ((hwaddr)(etsec->regs[TBDBPH].value & 0xF) << 32);
> - uint8_t padd[etsec->rx_padding];
> + uint8_t padd[MAX_RX_PADDING];
> uint8_t rem;
>
> + assert(etsec->rx_padding <= MAX_RX_PADDING);
> +
> RING_DEBUG("eTSEC fill Rx buffer @ 0x%016" HWADDR_PRIx
> " size:%zu(padding + crc:%u) + fcb:%u\n",
> bufptr, *size, etsec->rx_padding, etsec->rx_fcb_size);
> @@ -426,7 +434,7 @@ static void fill_rx_bd(eTSEC *etsec,
> rem = MIN(etsec->regs[MRBLR].value - bd->length, etsec->rx_padding);
>
> if (rem > 0) {
> - memset(padd, 0x0, sizeof(padd));
> + memset(padd, 0x0, rem);
> etsec->rx_padding -= rem;
> *size -= rem;
> bd->length += rem;
Maybe we can add this for clarity:
@@ -468,6 +468,6 @@ static void rx_init_frame(eTSEC *etsec, const
uint8_t *buf, size_t size)
* minimum MTU size bytes long (64)
*/
- if (etsec->rx_buffer_len < 60) {
- etsec->rx_padding += 60 - etsec->rx_buffer_len;
+ if (etsec->rx_padding + etsec->rx_buffer_len < MAX_RX_PADDING) {
+ etsec->rx_padding = MAX_RX_PADDING - etsec->rx_buffer_len;
}
next prev parent reply other threads:[~2023-08-24 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 15:32 [PATCH 0/4] net: avoid variable length arrays Peter Maydell
2023-08-24 15:32 ` [PATCH 1/4] hw/net/fsl_etsec/rings.c: Avoid variable length array Peter Maydell
2023-08-24 15:47 ` Philippe Mathieu-Daudé [this message]
2023-08-24 16:01 ` Peter Maydell
2023-08-24 16:07 ` Philippe Mathieu-Daudé
2023-08-24 15:32 ` [PATCH 2/4] hw/net/rocker: " Peter Maydell
2023-08-25 7:55 ` Francisco Iglesias
2023-08-24 15:32 ` [PATCH 3/4] net/dump: " Peter Maydell
2023-08-25 7:57 ` Francisco Iglesias
2023-08-24 15:32 ` [PATCH 4/4] net/tap: Avoid variable-length array Peter Maydell
2023-08-25 7:57 ` Francisco Iglesias
2023-09-12 14:20 ` [PATCH 0/4] net: avoid variable length arrays Peter Maydell
2023-09-13 3:26 ` Jason Wang
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=663d4cd3-50d5-d5db-bd43-efc55fe6bbf0@linaro.org \
--to=philmd@linaro.org \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).