From: P J P <ppandit@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
"Jason Wang" <jasowang@redhat.com>,
qemu-devel@nongnu.org,
"Alistair Francis" <alistair.francis@xilinx.com>,
qemu-arm@nongnu.org, 刘令 <liuling-it@360.cn>
Subject: Re: [Qemu-devel] [PATCH] cadence_gem: fix buffer overflow
Date: Thu, 14 Jan 2016 15:53:38 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1601141551390.29435@wniryva> (raw)
In-Reply-To: <1452764448-17953-1-git-send-email-mst@redhat.com>
+-- On Thu, 14 Jan 2016, 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.
|
| 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;
| + }
| +
Commit message says gem_receive, but the patch fixes gem_transmit() routine.
--
- P J P
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2016-01-14 10:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 9:43 [Qemu-devel] [PATCH] cadence_gem: fix buffer overflow Michael S. Tsirkin
2016-01-14 10:03 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2016-01-14 10:11 ` Michael S. Tsirkin
2016-01-15 6:19 ` Peter Crosthwaite
2016-01-15 8:06 ` P J P
2016-01-16 0:20 ` Alistair Francis
2016-01-16 5:23 ` P J P
2016-01-18 3:14 ` Jason Wang
2016-01-14 10:23 ` P J P [this message]
2016-01-15 3:16 ` [Qemu-devel] " Jason Wang
2016-01-15 5:39 ` P J P
2016-01-18 6:50 ` Jason Wang
2016-01-18 7:04 ` Peter Crosthwaite
2016-01-18 8:12 ` Jason Wang
2016-01-18 9:08 ` Peter Crosthwaite
2016-01-18 9:57 ` Jason Wang
2016-01-18 10:06 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2016-01-18 16:54 ` Alistair Francis
2016-01-19 2:48 ` Jason Wang
2016-01-19 2:48 ` 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=alpine.LFD.2.20.1601141551390.29435@wniryva \
--to=ppandit@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=crosthwaite.peter@gmail.com \
--cc=jasowang@redhat.com \
--cc=liuling-it@360.cn \
--cc=mst@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).