From: P J P <ppandit@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Gaoning Pan <pgn@zju.edu.cn>, Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] ati: mask x y display parameter values
Date: Tue, 20 Oct 2020 12:41:42 +0530 (IST) [thread overview]
Message-ID: <nycvar.YSQ.7.78.906.2010201220140.1506567@xnncv> (raw)
In-Reply-To: <1e94cbca-121f-52f2-b1e3-6d2fdb59ee42@eik.bme.hu>
Hi,
+-- On Mon, 19 Oct 2020, BALATON Zoltan wrote --+
| On Mon, 19 Oct 2020, P J P wrote:
| > dst_x = ... (s->regs.dst_x(=0) + 1 - s->regs.dst_width(=16383))
| > dst_y = ... (s->regs.dst_y(=0) + 1 - s->regs.dst_height(=16383))
| >
| > ati_2d_blt
| > pixman_blt(0x7f03cbe00000, 0x7f03cbe00000, 131064, 131064, 32, 32,
| > src_x=0, src_y=-16382, dst_x=0, dst_y=-16382, 16383, 16383)
| >
| > Shown as negative values due to signed '%d' conversion.
|
| Checking the docs again I see that the allowed range of at least
| s->regs.[src|dst]_[xy] can actually be negative (-8192:8191)
* But 'struct ATIVGARegs' declares these fields as 'uint32_t' type. Ie. no
negativeve values.
* I guess that range applies to src->regs.dst_[width|height] too? Considering
it being subtracted from s->regs.dst_[xy] values above.
| > uint8_t *end = s->vga.vram_ptr + s->vga.vram_size;
| > if (dst_bits >= end || dst_bits + dst_x + (dst_y + s->regs.dst_height) *
| > dst_stride >= end) {
| > qemu_log_mask(LOG_UNIMP, "blt outside vram not implemented\n");
| > return;
|
| ... Could it be it overflows?
* Yes, following expression
dst_y(=4294950914(=-16382)) + s->regs.dst_height(=16383)) overflows to => 1
Ie. (dst_bits + dst_x(=0) + (1) * dst_stride >= end) returns false.
| maybe rather add additional term for src|dst_x|y to the already existing
| checks if their condition cannot be fixed to detect it properly.
===
diff --git a/hw/display/ati_2d.c b/hw/display/ati_2d.c
index 524bc03a83..5fa7362305 100644
--- a/hw/display/ati_2d.c
+++ b/hw/display/ati_2d.c
@@ -54,9 +54,9 @@ void ati_2d_blt(ATIVGAState *s)
...
- if (dst_bits >= end || dst_bits + dst_x + (dst_y + s->regs.dst_height) *
- dst_stride >= end) {
+ if (dst_x > 0x3fff || dst_y > 0x3fff || dst_bits >= end
+ || dst_bits + dst_x + (dst_y + s->regs.dst_height)
+ * dst_stride >= end) {
qemu_log_mask(LOG_UNIMP, "blt outside vram not implemented\n");
return;
}
...
- if (src_bits >= end || src_bits + src_x +
- (src_y + s->regs.dst_height) * src_stride >= end) {
+ if (src_x > 0x3fff || src_y > 0x3ff || src_bits >= end
+ || src_bits + src_x + (src_y + s->regs.dst_height)
+ * src_stride >= end) {
qemu_log_mask(LOG_UNIMP, "blt outside vram not implemented\n");
return;
}
===
* Does it look okay?
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D
next prev parent reply other threads:[~2020-10-20 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 12:08 [PATCH] ati: mask x y display parameter values P J P
2020-10-18 13:58 ` BALATON Zoltan via
2020-10-19 6:27 ` P J P
2020-10-19 18:26 ` BALATON Zoltan via
2020-10-20 7:11 ` P J P [this message]
2020-10-20 11:29 ` BALATON Zoltan via
2020-10-20 13:08 ` P J P
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=nycvar.YSQ.7.78.906.2010201220140.1506567@xnncv \
--to=ppandit@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=pgn@zju.edu.cn \
--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).