Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kai Kang <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Backport patches of qemu to fix CVE issues
Date: Thu, 18 Jun 2015 17:02:41 +0800	[thread overview]
Message-ID: <cover.1434618027.git.kai.kang@windriver.com> (raw)

The following changes since commit 1675ff6fff53dda89fa8d4f3a2c292c23fd346d7:

  bitbake: tests/data: Add new data tests (2015-06-12 00:02:28 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib kangkai/qemu
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/qemu

Kai Kang (1):
  qemu: backport patches to fix CVE issues

 ...f-modified-PCI-CFG-contents-CVE-2015-4103.patch | 140 +++++++++++
 ...o-control-MSI-mask-register-CVE-2015-4104.patch | 194 +++++++++++++++
 ...-MSI-X-limit-error-messages-CVE-2015-4105.patch |  90 +++++++
 ...s-through-of-enable-bit-mod-CVE-2015-4106.patch |  76 ++++++
 ...date-PM-capability-emu_mask-CVE-2015-4106.patch |  86 +++++++
 ...rectly-handle-PM-status-bit-CVE-2015-4106.patch |  38 +++
 ...ulation-of-throughable-mask-CVE-2015-4106.patch | 265 +++++++++++++++++++++
 ...e-capability-bits-read-only-CVE-2015-4106.patch |  38 +++
 ...-in-PCI-config-space-fields-CVE-2015-4106.patch |  94 ++++++++
 ...ig-space-field-descriptions-CVE-2015-4106.patch |  77 ++++++
 ...e-fields-should-be-readonly-CVE-2015-4106.patch | 137 +++++++++++
 meta/recipes-devtools/qemu/qemu_2.3.0.bb           |  13 +-
 12 files changed, 1247 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-devtools/qemu/qemu/01-xen-properly-gate-host-writes-of-modified-PCI-CFG-contents-CVE-2015-4103.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/02-xen-dont-allow-guest-to-control-MSI-mask-register-CVE-2015-4104.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/03-xen-MSI-X-limit-error-messages-CVE-2015-4105.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/04-xen-MSI-dont-open-code-pass-through-of-enable-bit-mod-CVE-2015-4106.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/05-xen-pt-consolidate-PM-capability-emu_mask-CVE-2015-4106.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/06-xen-pt-correctly-handle-PM-status-bit-CVE-2015-4106.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/07-xen-pt-split-out-calculation-of-throughable-mask-CVE-2015-4106.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/08-xen-pt-mark-all-PCIe-capability-bits-read-only-CVE-2015-4106.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/09-xen-pt-mark-reserved-bits-in-PCI-config-space-fields-CVE-2015-4106.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/10-xen-pt-add-a-few-PCI-config-space-field-descriptions-CVE-2015-4106.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/11-xen-pt-unknown-PCI-config-space-fields-should-be-readonly-CVE-2015-4106.patch

-- 
1.9.1



             reply	other threads:[~2015-06-18  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18  9:02 Kai Kang [this message]
2015-06-18  9:02 ` [PATCH 1/1] qemu: backport patches to fix CVE issues Kai Kang
2015-09-04 12:35   ` Sona Sarmadi

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.1434618027.git.kai.kang@windriver.com \
    --to=kai.kang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox