From: Michael Tokarev <mjt@tls.msk.ru>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] gdbstub: Fix buffer overflows in gdb_handle_packet()
Date: Thu, 29 Oct 2015 10:30:24 +0300 [thread overview]
Message-ID: <5631CB10.30100@msgid.tls.msk.ru> (raw)
In-Reply-To: <1444721930-5121-1-git-send-email-kwolf@redhat.com>
13.10.2015 10:38, Kevin Wolf wrote:
> Some places in gdb_handle_packet() can get an arbitrary length (most
> times directly from the client) and either didn't check it at all or
> checked against the wrong value, potentially causing buffer overflows.
Applied to -trivial, thank you!
/mjt
prev parent reply other threads:[~2015-10-29 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 7:38 [Qemu-devel] [PATCH] gdbstub: Fix buffer overflows in gdb_handle_packet() Kevin Wolf
2015-10-14 6:53 ` P J P
2015-10-14 8:09 ` Kevin Wolf
2015-10-14 9:24 ` P J P
2015-10-29 7:30 ` Michael Tokarev [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=5631CB10.30100@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=qemu-trivial@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).