From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, liezhi.yang@windriver.com,
openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Jethro-next: QEMU security fixes
Date: Wed, 27 Jul 2016 09:03:13 -0700 [thread overview]
Message-ID: <cover.1469634894.git.akuster@mvista.com> (raw)
From: Armin Kuster <akuster@mvista.com>
Please consider these patches for Jethro-next
The following changes since commit 7ed60009e2bcdd2380265ca95eb5de2328825eb5:
libxml2: Security fix for CVE-2016-4448 (2016-07-09 15:47:51 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akuster/jethro-next
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/jethro-next
Armin Kuster (4):
qemu: Security fix for CVE-2016-2858
qemu: Security fix for CVE-2016-4001
qemu: Security fix for CVE-2016-4020
qemu: Security fix for CVE-2016-4037
.../recipes-devtools/qemu/qemu/CVE-2016-2858.patch | 182 +++++++++++++++++++++
.../qemu/qemu/CVE-2016-2858_pre_1.patch | 99 +++++++++++
.../qemu/qemu/CVE-2016-2858_pre_2.patch | 137 ++++++++++++++++
.../qemu/qemu/CVE-2016-2858_pre_3.patch | 165 +++++++++++++++++++
.../recipes-devtools/qemu/qemu/CVE-2016-4001.patch | 50 ++++++
.../recipes-devtools/qemu/qemu/CVE-2016-4020.patch | 38 +++++
.../recipes-devtools/qemu/qemu/CVE-2016-4037.patch | 66 ++++++++
meta/recipes-devtools/qemu/qemu_2.4.0.bb | 7 +
8 files changed, 744 insertions(+)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-2858.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-2858_pre_1.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-2858_pre_2.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-2858_pre_3.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-4001.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-4020.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-4037.patch
--
2.3.5
reply other threads:[~2016-07-27 16:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1469634894.git.akuster@mvista.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.