From: Paolo Bonzini <pbonzini@redhat.com>
To: P J P <ppandit@redhat.com>, Qemu Developers <qemu-devel@nongnu.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
Cyrille Chatras <cyrille.chatras@orange.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v1] ps2: check PS2Queue pointers in post_load routine
Date: Thu, 16 Nov 2017 10:10:52 +0100 [thread overview]
Message-ID: <658ecab6-1f09-0c94-c89e-55f71c37309a@redhat.com> (raw)
In-Reply-To: <20171116075155.22378-1-ppandit@redhat.com>
On 16/11/2017 08:51, P J P wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> During Qemu guest migration, a destination process invokes ps2
> post_load function. In that, if 'rptr' and 'count' values were
> invalid, it could lead to OOB access or infinite loop issue.
> Add check to avoid it.
>
> Reported-by: Cyrille Chatras <cyrille.chatras@orange.com>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
> hw/input/ps2.c | 21 +++++++++------------
> 1 file changed, 9 insertions(+), 12 deletions(-)
>
> Update: avoid changing field type, add range check on values
> -> https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg02815.html
>
> diff --git a/hw/input/ps2.c b/hw/input/ps2.c
> index f388a23c8e..de171a28dd 100644
> --- a/hw/input/ps2.c
> +++ b/hw/input/ps2.c
> @@ -1225,24 +1225,21 @@ static void ps2_common_reset(PS2State *s)
> static void ps2_common_post_load(PS2State *s)
> {
> PS2Queue *q = &s->queue;
> - int size;
> - int i;
> - int tmp_data[PS2_QUEUE_SIZE];
> + uint8_t i, size;
> + uint8_t tmp_data[PS2_QUEUE_SIZE];
Hi Prasad,
you don't need to change the invalid values to sane ones. Instead, make
ps2_common_post_load return an int (just like the .post_load member of
VMStateDescription). You can then detect out of range count/rptr/wptr
and return -1 for bad indices.
In the callers,
ps2_common_post_load(ps2);
return 0;
can then become simply
return ps2_common_post_load(ps2);
Thanks,
Paolo
> /* set the useful data buffer queue size, < PS2_QUEUE_SIZE */
> - size = q->count > PS2_QUEUE_SIZE ? 0 : q->count;
> + size = (q->count < 0 || q->count > PS2_QUEUE_SIZE) ? 0 : q->count;
>
> /* move the queue elements to the start of data array */
> - if (size > 0) {
> - for (i = 0; i < size; i++) {
> - /* move the queue elements to the temporary buffer */
> - tmp_data[i] = q->data[q->rptr];
> - if (++q->rptr == 256) {
> - q->rptr = 0;
> - }
> + for (i = 0; i < size; i++) {
> + if (q->rptr < 0 || q->rptr >= sizeof(q->data)) {
> + q->rptr = 0;
> }
> - memcpy(q->data, tmp_data, size);
> + tmp_data[i] = q->data[q->rptr++];
> }
> + memcpy(q->data, tmp_data, size);
> +
> /* reset rptr/wptr/count */
> q->rptr = 0;
> q->wptr = size;
>
next prev parent reply other threads:[~2017-11-16 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 7:51 [Qemu-devel] [PATCH v1] ps2: check PS2Queue pointers in post_load routine P J P
2017-11-16 9:10 ` Paolo Bonzini [this message]
2017-11-16 10:19 ` P J P
2017-11-17 9:35 ` Gerd Hoffmann
2017-11-21 13:18 ` Dr. David Alan Gilbert
2018-01-25 15:19 ` Gerd Hoffmann
2018-01-31 7:15 ` 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=658ecab6-1f09-0c94-c89e-55f71c37309a@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=cyrille.chatras@orange.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--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).