From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: "Alistair Francis" <alistair.francis@xilinx.com>,
"Prasad Pandit" <ppandit@redhat.com>, 刘令 <liuling-it@360.cn>,
qemu-arm@nongnu.org
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH] cadence_gem: fix buffer overflow
Date: Mon, 18 Jan 2016 14:50:17 +0800 [thread overview]
Message-ID: <569C8B29.4040300@redhat.com> (raw)
In-Reply-To: <1452764448-17953-1-git-send-email-mst@redhat.com>
On 01/14/2016 05:43 PM, Michael S. Tsirkin wrote:
> gem_receive copies a packet received from network into an rxbuf[2048]
> array on stack, with size limited by descriptor length set by guest. If
> guest is malicious and specifies a descriptor length that is too large,
> and should packet size exceed array size, this results in a buffer
> overflow.
>
> Reported-by: 刘令 <liuling-it@360.cn>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> hw/net/cadence_gem.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Apply to my -net with tweak on commit log (changing receive to transmit
as noticed).
Thanks
>
> diff --git a/hw/net/cadence_gem.c b/hw/net/cadence_gem.c
> index 3639fc1..15a0786 100644
> --- a/hw/net/cadence_gem.c
> +++ b/hw/net/cadence_gem.c
> @@ -862,6 +862,14 @@ static void gem_transmit(CadenceGEMState *s)
> break;
> }
>
> + if (tx_desc_get_length(desc) > sizeof(tx_packet) - (p - tx_packet)) {
> + DB_PRINT("TX descriptor @ 0x%x too large: size 0x%x space 0x%x\n",
> + (unsigned)packet_desc_addr,
> + (unsigned)tx_desc_get_length(desc),
> + sizeof(tx_packet) - (p - tx_packet));
> + break;
> + }
> +
> /* Gather this fragment of the packet from "dma memory" to our contig.
> * buffer.
> */
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: "Alistair Francis" <alistair.francis@xilinx.com>,
"Prasad Pandit" <ppandit@redhat.com>, 刘令 <liuling-it@360.cn>,
qemu-arm@nongnu.org,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] cadence_gem: fix buffer overflow
Date: Mon, 18 Jan 2016 14:50:17 +0800 [thread overview]
Message-ID: <569C8B29.4040300@redhat.com> (raw)
In-Reply-To: <1452764448-17953-1-git-send-email-mst@redhat.com>
On 01/14/2016 05:43 PM, Michael S. Tsirkin wrote:
> gem_receive copies a packet received from network into an rxbuf[2048]
> array on stack, with size limited by descriptor length set by guest. If
> guest is malicious and specifies a descriptor length that is too large,
> and should packet size exceed array size, this results in a buffer
> overflow.
>
> Reported-by: 刘令 <liuling-it@360.cn>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> hw/net/cadence_gem.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Apply to my -net with tweak on commit log (changing receive to transmit
as noticed).
Thanks
>
> diff --git a/hw/net/cadence_gem.c b/hw/net/cadence_gem.c
> index 3639fc1..15a0786 100644
> --- a/hw/net/cadence_gem.c
> +++ b/hw/net/cadence_gem.c
> @@ -862,6 +862,14 @@ static void gem_transmit(CadenceGEMState *s)
> break;
> }
>
> + if (tx_desc_get_length(desc) > sizeof(tx_packet) - (p - tx_packet)) {
> + DB_PRINT("TX descriptor @ 0x%x too large: size 0x%x space 0x%x\n",
> + (unsigned)packet_desc_addr,
> + (unsigned)tx_desc_get_length(desc),
> + sizeof(tx_packet) - (p - tx_packet));
> + break;
> + }
> +
> /* Gather this fragment of the packet from "dma memory" to our contig.
> * buffer.
> */
next prev parent reply other threads:[~2016-01-18 6:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 9:43 [Qemu-arm] [PATCH] cadence_gem: fix buffer overflow Michael S. Tsirkin
2016-01-14 9:43 ` [Qemu-devel] " Michael S. Tsirkin
2016-01-14 10:03 ` [Qemu-arm] " Peter Maydell
2016-01-14 10:03 ` [Qemu-devel] " Peter Maydell
2016-01-14 10:11 ` Michael S. Tsirkin
2016-01-14 10:11 ` [Qemu-devel] " Michael S. Tsirkin
2016-01-15 6:19 ` Peter Crosthwaite
2016-01-15 6:19 ` [Qemu-devel] " Peter Crosthwaite
2016-01-15 8:06 ` P J P
2016-01-15 8:06 ` [Qemu-devel] " P J P
2016-01-16 0:20 ` Alistair Francis
2016-01-16 5:23 ` [Qemu-arm] [Qemu-devel] " P J P
2016-01-16 5:23 ` [Qemu-devel] [Qemu-arm] " P J P
2016-01-18 3:14 ` Jason Wang
2016-01-18 3:14 ` [Qemu-devel] " Jason Wang
2016-01-14 10:23 ` [Qemu-devel] " P J P
2016-01-15 3:16 ` Jason Wang
2016-01-15 5:39 ` [Qemu-arm] " P J P
2016-01-15 5:39 ` P J P
2016-01-18 6:50 ` Jason Wang [this message]
2016-01-18 6:50 ` Jason Wang
2016-01-18 7:04 ` Peter Crosthwaite
2016-01-18 8:12 ` [Qemu-arm] " Jason Wang
2016-01-18 8:12 ` Jason Wang
2016-01-18 9:08 ` [Qemu-arm] " Peter Crosthwaite
2016-01-18 9:08 ` Peter Crosthwaite
2016-01-18 9:57 ` [Qemu-arm] " Jason Wang
2016-01-18 9:57 ` Jason Wang
2016-01-18 10:06 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2016-01-18 16:54 ` [Qemu-arm] [Qemu-devel] " Alistair Francis
2016-01-18 16:54 ` [Qemu-devel] [Qemu-arm] " Alistair Francis
2016-01-19 2:48 ` [Qemu-arm] [Qemu-devel] " Jason Wang
2016-01-19 2:48 ` [Qemu-devel] [Qemu-arm] " Jason Wang
2016-01-19 2:48 ` [Qemu-arm] [Qemu-devel] " Jason Wang
2016-01-19 2:48 ` [Qemu-devel] [Qemu-arm] " 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=569C8B29.4040300@redhat.com \
--to=jasowang@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=liuling-it@360.cn \
--cc=mst@redhat.com \
--cc=ppandit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.