From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org, Chuhong Yuan <hslester96@gmail.com>
Cc: Alexander Bulekov <alxndr@bu.edu>,
qemu-arm@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH-for-9.0?] hw/net/smc91c111: Fix out of bounds access in packets buffer
Date: Mon, 8 Apr 2024 12:28:44 +0200 [thread overview]
Message-ID: <1926e063-5621-440b-a957-c9f76d4dc073@linaro.org> (raw)
In-Reply-To: <20240408102711.58485-1-philmd@linaro.org>
On 8/4/24 12:27, Philippe Mathieu-Daudé wrote:
> While the Packet Number Register is 6-bit wide and could hold
> up to 64 packets [*] our implementation is clamped at 4 packets.
>
> Reproducer:
>
> $ cat << EOF | qemu-system-arm -display none \
> -machine mainstone,accel=qtest \
> -qtest stdio
> outl 0xcf8 0x80000010
> outl 0xcfc 0x10000300
> outl 0xcf8 0x80000004
> outl 0xcfc 0x07
> writel 0x1000030c 0x66027cd6
> writel 0x10000300 0x64af8eda
> readw 0x10000308
> EOF
> hw/net/smc91c111.c:607:24: runtime error:
> index 175 out of bounds for type 'uint8_t[4][2048]' (aka 'unsigned char[4][2048]')
> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
> =================================================================
> ==397944==ERROR: AddressSanitizer: SEGV on unknown address 0x629000077db4
> (pc 0x56272aed3b8d bp 0x7ffd1471f290 sp 0x7ffd1471ea20 T0)
> ==397944==The signal is caused by a READ memory access.
> #0 0x56272aed3b8d in smc91c111_readb hw/net/smc91c111.c:607:24
> #1 0x56272aecfd61 in smc91c111_readfn hw/net/smc91c111.c:650:16
> #2 0x56272d4b228b in memory_region_read_accessor system/memory.c:445:11
> #3 0x56272d46fb85 in access_with_adjusted_size system/memory.c:573:18
> #4 0x56272d46c58e in memory_region_dispatch_read1 system/memory.c:1426:16
> #5 0x56272d46bcd7 in memory_region_dispatch_read system/memory.c:1459:9
> #6 0x56272d4e8e03 in flatview_read_continue_step system/physmem.c:2794:18
> #7 0x56272d4e871e in flatview_read_continue system/physmem.c:2835:19
> #8 0x56272d4e98b8 in flatview_read system/physmem.c:2865:12
> #9 0x56272d4e9388 in address_space_read_full system/physmem.c:2878:18
> #10 0x56272d6e7840 in address_space_read include/exec/memory.h:3026:18
> ...
>
> Broken since model introduction in commit 80337b66a8.
>
> [*] LAN91C111 DS00002276A.pdf, chapter 8.17, Packet Number Register
>
> Reported-by: Will Lester
Apparently also
Reported-by: Chuhong Yuan <hslester96@gmail.com>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2268
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> hw/net/smc91c111.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/net/smc91c111.c b/hw/net/smc91c111.c
> index 702d0e8e83..286298bf06 100644
> --- a/hw/net/smc91c111.c
> +++ b/hw/net/smc91c111.c
> @@ -429,7 +429,7 @@ static void smc91c111_writeb(void *opaque, hwaddr offset,
> /* Ignore. */
> return;
> case 2: /* Packet Number Register */
> - s->packet_num = value;
> + s->packet_num = value & (NUM_PACKETS - 1);
> return;
> case 3: case 4: case 5:
> /* Should be readonly, but linux writes to them anyway. Ignore. */
prev parent reply other threads:[~2024-04-08 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 10:27 [PATCH-for-9.0?] hw/net/smc91c111: Fix out of bounds access in packets buffer Philippe Mathieu-Daudé
2024-04-08 10:28 ` Philippe Mathieu-Daudé [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=1926e063-5621-440b-a957-c9f76d4dc073@linaro.org \
--to=philmd@linaro.org \
--cc=alxndr@bu.edu \
--cc=hslester96@gmail.com \
--cc=jasowang@redhat.com \
--cc=qemu-arm@nongnu.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).