Please Install the Updated Packages.

The kernel packages contain the Linux kernel, the core of any Linux operating system. This update fixes the following security issue: * A flaw was found in the way the Xen hypervisor AMD IOMMU driver handled interrupt remapping entries. By default, a single interrupt remapping table is used, and old interrupt remapping entries are not cleared, potentially allowing a privileged guest user in a guest that has a passed-through, bus-mastering capable PCI device to inject interrupt entries into others guests, including the privileged management domain (Dom0), leading to a denial of service. (CVE-2013-0153, Moderate) Red Hat would like to thank the Xen project for reporting the CVE-2013-0153 issue. This update also fixes the following bugs: * When a process is opening a file over NFSv4, sometimes an OPEN call can succeed while the following GETATTR operation fails with an NFS4ERR_DELAY error. The NFSv4 code did not handle such a situation correctly and allowed an NFSv4 client to attempt to use the buffer that should contain the GETATTR information. However, the buffer did not contain the valid GETATTR information, which caused the client to return a &quot -ENOTDIR&quot error. Consequently, the process failed to open the requested file. This update backports a patch that adds a test condition verifying validity of the GETATTR information. If the GETATTR information is invalid, it is obtained later and the process opens the requested file as expected. (BZ#947736) * Previously, the xdr routines in NFS version 2 and 3 conditionally updated the res-&gt count variable. Read retry attempts after a short NFS read() call could fail to update the res-&gt count variable, resulting in truncated read data being returned. With this update, the res-&gt count variable is updated unconditionally so this bug can no longer occur. (BZ#952098) * When handling requests from Intelligent Platform Management Interface (IPMI) clients, the IPMI driver previously used two different locks for an IPMI request. If two IPMI clients sent their requests at the same time, each request could receive one of the locks and then wait for the second lock to become available. This resulted in a deadlock situation and the system became unresponsive. The problem could occur more likely in environments with many IPMI clients. This update modifies the IPMI driver to handle the received messages using tasklets so the driver now uses a safe locking technique when handling IPMI requests and the mentioned deadlock can no longer occur. (BZ#953435) * In ... Description truncated, for more information please check the Reference URL

kernel on CentOS 5

• http://lists.centos.org/pipermail/centos-announce/2013-May/019735.html

---

Updated on 2015-03-25