From: Gerd Hoffmann <kraxel@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] gtk: avoid oob array access
Date: Wed, 04 Jan 2017 10:01:29 +0100 [thread overview]
Message-ID: <1483520489.5670.49.camel@redhat.com> (raw)
In-Reply-To: <20161207105511.25173-1-marcandre.lureau@redhat.com>
On Mi, 2016-12-07 at 13:55 +0300, Marc-André Lureau wrote:
> When too many consoles are created, vcs[] may be write out-of-bounds.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> ui/gtk.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/ui/gtk.c b/ui/gtk.c
> index e81642876a..67c52179ee 100644
> --- a/ui/gtk.c
> +++ b/ui/gtk.c
> @@ -1696,6 +1696,11 @@ static CharDriverState *gd_vc_handler(ChardevVC *vc, Error **errp)
> ChardevCommon *common = qapi_ChardevVC_base(vc);
> CharDriverState *chr;
>
> + if (nb_vcs == MAX_VCS) {
> + error_setg(errp, "Maximum number of consoles reached");
> + return NULL;
> + }
> +
> chr = qemu_chr_alloc(common, errp);
> if (!chr) {
> return NULL;
added to ui queue.
thanks,
Gerd
prev parent reply other threads:[~2017-01-04 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 10:55 [Qemu-devel] [PATCH] gtk: avoid oob array access Marc-André Lureau
2017-01-04 9:01 ` Gerd Hoffmann [this message]
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=1483520489.5670.49.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=marcandre.lureau@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).