qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: [Qemu-devel] [ANNOUNCE] QEMU 2.8.1.1 CVE update released
Date: Thu, 20 Apr 2017 18:14:54 -0500	[thread overview]
Message-ID: <149273009469.5829.1877204641747528305@loki> (raw)

Hi everyone,

A security update to the QEMU 2.8 series is now available at:

  http://wiki.qemu.org/download/qemu-2.8.1.1.tar.xz
  http://wiki.qemu.org/download/qemu-2.8.1.1.tar.xz.sig

v2.8.1.1 is now tagged in the official qemu.git repository,
and the stable-2.8 branch has been updated accordingly:

  http://git.qemu.org/?p=qemu.git;a=shortlog;h=refs/heads/stable-2.8

This release includes security fixes for:

  virtfs/virtio-9p shared directories (CVE-2017-7471)  

Please see the changelogs and relevant CVEs for more information, and
update accordingly.

Thank you to everyone involved!

CHANGELOG:

d1b725e: Update version for 2.8.1.1 release (Michael Roth)
96bae14: 9pfs: local: set the path of the export root to "." (Greg Kurz)

                 reply	other threads:[~2017-04-20 23:15 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=149273009469.5829.1877204641747528305@loki \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).