qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Corentin Chary <corentincj@iksaif.net>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Peter Lieven <pl@dlh.net>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org, weil@mail.berlios.de
Subject: [Qemu-devel] [PATCH 2/2] vnc: Limit r/w access to size of allocated memory
Date: Wed, 14 Mar 2012 07:58:48 +0100	[thread overview]
Message-ID: <1331708328-21414-3-git-send-email-corentincj@iksaif.net> (raw)
In-Reply-To: <1331708328-21414-1-git-send-email-corentincj@iksaif.net>

From: Stefan Weil <weil@mail.berlios.de>

This fixes memory reads and writes which exceeded the upper limit
of allocated memory vd->guest.ds->data and vd->server->data.

Cc: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
 ui/vnc.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/ui/vnc.c b/ui/vnc.c
index aef6d3a..deb9ecd 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -2562,6 +2562,9 @@ static int vnc_refresh_server_surface(VncDisplay *vd)
      * Update server dirty map.
      */
     cmp_bytes = 16 * ds_get_bytes_per_pixel(vd->ds);
+    if (cmp_bytes > vd->ds->surface->linesize) {
+        cmp_bytes = vd->ds->surface->linesize;
+    }
     guest_row  = vd->guest.ds->data;
     server_row = vd->server->data;
     for (y = 0; y < vd->guest.ds->height; y++) {
-- 
1.7.3.4

  parent reply	other threads:[~2012-03-14  6:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  6:58 [Qemu-devel] [PATCH 0/2] Lost VNC patches Corentin Chary
2012-03-14  6:58 ` [Qemu-devel] [PATCH 1/2] vnc: don't mess up with iohandlers in the vnc thread Corentin Chary
2012-03-14  6:58 ` Corentin Chary [this message]
2012-03-14 21:46 ` [Qemu-devel] [PATCH 0/2] Lost VNC patches Anthony Liguori
2012-03-14 22:16   ` Stefan Weil
2012-03-15  6:28     ` Corentin Chary

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=1331708328-21414-3-git-send-email-corentincj@iksaif.net \
    --to=corentincj@iksaif.net \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pl@dlh.net \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).