Bug 859946 - kernel: xen: change the default behaviour of CVE-2012-2934 fix [rhel-5.8.z]
kernel: xen: change the default behaviour of CVE-2012-2934 fix [rhel-5.8.z]
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
x86_64 Other
high Severity high
: rc
: ---
Assigned To: Alexander Gordeev
Virtualization Bugs
: ZStream
Depends On: 858724
  Show dependency treegraph
Reported: 2012-09-24 09:07 EDT by RHEL Product and Program Management
Modified: 2013-01-09 20:09 EST (History)
17 users (show)

See Also:
Fixed In Version: kernel-2.6.18-308.19.1.el5
Doc Type: Bug Fix
Doc Text:
This update changes Xen hypervisor's behavior introduced in the CVE-2012-2934 issue: the host was prevented from booting on AMD processors with the AMD #121 erratum applied. Users were prompted to pass the "allow_unsafe" parameter on the command line to allow booting the Xen host. However, this could prevent remotely managed hosts from being started. With this update, the boot process is no longer denied by default; only guest creation is denied. The allow_unsafe semantics has changed to allow creation of guests instead of allowing booting the host.
Story Points: ---
Clone Of:
Last Closed: 2012-11-13 10:42:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description RHEL Product and Program Management 2012-09-24 09:07:55 EDT
This bug has been copied from bug #858724 and has been proposed
to be backported to 5.8 z-stream (EUS).
Comment 5 Alexander Gordeev 2012-10-22 03:21:32 EDT
in kernel-2.6.18-308.19.1.el5
Comment 9 errata-xmlrpc 2012-11-13 10:42:08 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.