Issued:

2012-06-12

Updated:

2012-06-12

RHSA-2012:0721 - Important: kernel security update

Synopsis

Important: kernel security update

Type/Severity

Security Advisory Important

Topic

Updated kernel packages that fix two security issues are now available for Red Hat Enterprise Linux 5.

The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Description

The kernel packages contain the Linux kernel, the core of any Linux operating system.

This update fixes the following security issues:

• It was found that the Xen hypervisor implementation as shipped with Red Hat Enterprise Linux 5 did not properly restrict the syscall return addresses in the sysret return path to canonical addresses. An unprivileged user in a 64-bit para-virtualized guest, that is running on a 64-bit host that has an Intel CPU, could use this flaw to crash the host or, potentially, escalate their privileges, allowing them to execute arbitrary code at the hypervisor level. (CVE-2012-0217, Important)

• It was found that guests could trigger a bug in earlier AMD CPUs, leading to a CPU hard lockup, when running on the Xen hypervisor implementation. An unprivileged user in a 64-bit para-virtualized guest could use this flaw to crash the host. Warning: After installing this update, hosts that are using an affected AMD CPU (refer to Red Hat Bugzilla bug #824966 for a list) will fail to boot. In order to boot such hosts, the new kernel parameter, allow_unsafe, can be used ("allow_unsafe=on"). This option should only be used with hosts that are running trusted guests, as setting it to "on" reintroduces the flaw (allowing guests to crash the host). (CVE-2012-2934, Moderate)

Note: For Red Hat Enterprise Linux guests, only privileged guest users can exploit the CVE-2012-0217 and CVE-2012-2934 issues.

Red Hat would like to thank the Xen project for reporting these issues. Upstream acknowledges Rafal Wojtczuk as the original reporter of CVE-2012-0217.

Users should upgrade to these updated packages, which contain backported patches to correct these issues. The system must be rebooted for this update to take effect.

Solution

Before applying this update, make sure all previously-released errata relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.

Affected Products

Updated Packages

• kernel-devel-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-kdump-debuginfo-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-debuginfo-common-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-kdump-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-xen-devel-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-debug-2.6.18-308.8.2.el5.ia64.rpm
• kernel-2.6.18-308.8.2.el5.s390x.rpm
• kernel-headers-2.6.18-308.8.2.el5.i386.rpm
• kernel-kdump-devel-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-headers-2.6.18-308.8.2.el5.s390x.rpm
• kernel-debug-debuginfo-2.6.18-308.8.2.el5.i686.rpm
• kernel-debuginfo-common-2.6.18-308.8.2.el5.ia64.rpm
• kernel-doc-2.6.18-308.8.2.el5.noarch.rpm
• kernel-xen-2.6.18-308.8.2.el5.ia64.rpm
• kernel-xen-debuginfo-2.6.18-308.8.2.el5.i686.rpm
• kernel-debug-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-xen-debuginfo-2.6.18-308.8.2.el5.ia64.rpm
• kernel-debug-devel-2.6.18-308.8.2.el5.i686.rpm
• kernel-debuginfo-common-2.6.18-308.8.2.el5.s390x.rpm
• kernel-PAE-devel-2.6.18-308.8.2.el5.i686.rpm
• kernel-debug-debuginfo-2.6.18-308.8.2.el5.s390x.rpm
• kernel-debug-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-headers-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-headers-2.6.18-308.8.2.el5.ppc.rpm
• kernel-debuginfo-2.6.18-308.8.2.el5.ia64.rpm
• kernel-devel-2.6.18-308.8.2.el5.s390x.rpm
• kernel-headers-2.6.18-308.8.2.el5.ia64.rpm
• kernel-headers-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-xen-devel-2.6.18-308.8.2.el5.ia64.rpm
• kernel-debuginfo-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-debug-devel-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-debug-2.6.18-308.8.2.el5.s390x.rpm
• kernel-debug-debuginfo-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-kdump-devel-2.6.18-308.8.2.el5.s390x.rpm
• kernel-debug-devel-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-debug-debuginfo-2.6.18-308.8.2.el5.ia64.rpm
• kernel-debuginfo-2.6.18-308.8.2.el5.s390x.rpm
• kernel-debuginfo-2.6.18-308.8.2.el5.i686.rpm
• kernel-debug-devel-2.6.18-308.8.2.el5.s390x.rpm
• kernel-xen-devel-2.6.18-308.8.2.el5.i686.rpm
• kernel-PAE-debuginfo-2.6.18-308.8.2.el5.i686.rpm
• kernel-debuginfo-common-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-debug-2.6.18-308.8.2.el5.i686.rpm
• kernel-devel-2.6.18-308.8.2.el5.i686.rpm
• kernel-xen-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-debug-devel-2.6.18-308.8.2.el5.ia64.rpm
• kernel-PAE-2.6.18-308.8.2.el5.i686.rpm
• kernel-2.6.18-308.8.2.el5.src.rpm
• kernel-devel-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-kdump-debuginfo-2.6.18-308.8.2.el5.s390x.rpm
• kernel-debug-debuginfo-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-xen-2.6.18-308.8.2.el5.i686.rpm
• kernel-xen-debuginfo-2.6.18-308.8.2.el5.x86_64.rpm
• kernel-debuginfo-2.6.18-308.8.2.el5.ppc64.rpm
• kernel-debuginfo-common-2.6.18-308.8.2.el5.i686.rpm
• kernel-kdump-2.6.18-308.8.2.el5.s390x.rpm
• kernel-2.6.18-308.8.2.el5.ia64.rpm
• kernel-devel-2.6.18-308.8.2.el5.ia64.rpm
• kernel-2.6.18-308.8.2.el5.i686.rpm

Fixes

• This content is not included.BZ - 813428
• This content is not included.BZ - 824966

CVEs

• CVE-2012-2934
• CVE-2012-0217

References

• https://access.redhat.com/security/updates/classification/#important
• This content is not included.This content is not included.https://bugzilla.redhat.com/show_bug.cgi?id=824966

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.