From: Keir Fraser <keir@xen.org>
To: xen-devel@lists.xensource.com
Cc: Lars Kurth <lars.kurth@xen.org>
Subject: [ANNOUNCE] Xen 4.1.3 and 4.0.4 released
Date: Fri, 10 Aug 2012 14:11:18 +0100 [thread overview]
Message-ID: <CC4AC706.487CB%keir@xen.org> (raw)
Folks,
I am pleased to announce the release of Xen 4.0.4 and 4.1.3. These are
available immediately from their respective mercurial repositories:
http://xenbits.xen.org/xen-4.0-testing.hg (tag RELEASE-4.0.4)
http://xenbits.xen.org/xen-4.1-testing.hg (tag RELEASE-4.1.3)
These fix the following critical vulnerabilities:
* CVE-2012-0217 / XSA-7:
PV guest privilege escalation vulnerability
* CVE-2012-0218 / XSA-8:
guest denial of service on syscall/sysenter exception generation
* CVE-2012-2934 / XSA-9:
PV guest host Denial of Service
* CVE-2012-3432 / XSA-10:
HVM guest user mode MMIO emulation DoS vulnerability
* CVE-2012-3433 / XSA-11:
HVM guest destroy p2m teardown host DoS vulnerability
We recommend all users of the 4.0 and 4.1 stable series to update to these
latest point releases.
Among many bug fixes and improvements (over 100 since Xen 4.1.2):
* Updates for the latest Intel/AMD CPU revisions
* Bug fixes and improvements to the libxl tool stack
* Bug fixes for IOMMU handling (device passthrough to HVM guests)
* Bug fixes for host kexec/kdump
Regards,
Keir
reply other threads:[~2012-08-10 13:11 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=CC4AC706.487CB%keir@xen.org \
--to=keir@xen.org \
--cc=lars.kurth@xen.org \
--cc=xen-devel@lists.xensource.com \
/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).