From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL for-2.6 0/2] ehci: fix (s)iTD looping issue (CVE-2015-8558) in a different way.
Date: Tue, 19 Apr 2016 08:24:42 +0200 [thread overview]
Message-ID: <1461047084-17810-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
CVE-2015-8558 fix turned out to break FreeBSD and being
incomplete -- go for a different approach to fix things.
please pull,
Gerd
The following changes since commit c6c598ca5fba68fbd6612f3330c4015142f2f86a:
Merge remote-tracking branch 'remotes/weil/tags/pull-wxx-20160415' into staging (2016-04-18 09:55:16 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-usb-20160419-1
for you to fetch changes up to a49923d2837d20510d645d3758f1ad87c32d0730:
Revert "ehci: make idt processing more robust" (2016-04-19 08:20:56 +0200)
----------------------------------------------------------------
ehci: fix (s)iTD looping issue (CVE-2015-8558) in a different way.
----------------------------------------------------------------
Gerd Hoffmann (2):
ehci: apply limit to iTD/sidt descriptors
Revert "ehci: make idt processing more robust"
hw/usb/hcd-ehci.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
next reply other threads:[~2016-04-19 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 6:24 Gerd Hoffmann [this message]
2016-04-19 6:24 ` [Qemu-devel] [PULL 1/2] ehci: apply limit to iTD/sidt descriptors Gerd Hoffmann
2016-04-19 6:24 ` [Qemu-devel] [PULL 2/2] Revert "ehci: make idt processing more robust" Gerd Hoffmann
2016-04-19 12:48 ` [Qemu-devel] [PULL for-2.6 0/2] ehci: fix (s)iTD looping issue (CVE-2015-8558) in a different way Peter Maydell
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=1461047084-17810-1-git-send-email-kraxel@redhat.com \
--to=kraxel@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).