RHSA-2015:1623: Important: kernel security and bug fix update

Published Aug 13, 2015
·
Updated

The kernel packages contain the Linux kernel, the core of any Linuxoperating system.Two flaws were found in the way the Linux kernel's networkingimplementation handled UDP packets with incorrect checksum values. A remoteattacker could potentially use these flaws to trigger an infinite loop inthe kernel, resulting in a denial of service on the system, or cause adenial of service in applications using the edge triggered epollfunctionality. (CVE-2015-5364, CVE-2015-5366, Important)This update also fixes the following bugs: When removing a directory, and a reference was held to that directory by a reference to a negative child dentry, the directory dentry was previouslynot killed. In addition, once the negative child dentry was killed, anunlinked and unused dentry was present in the cache. As a consequence,deadlock could be caused by forcing the dentry eviction while the filesystem in question was frozen. With this update, all unused dentries areunhashed and evicted just after a successful directory removal, whichavoids the deadlock, and the system no longer hangs in the aforementionedscenario. (BZ#1243400) Due to the broken sumount lock ordering, a race condition occurred when an unlinked file was closed and the sync (or syncfs) utility was run at thesame time. As a consequence, deadlock occurred on a frozen file systembetween sync and a process trying to unfreeze the file system. With thisupdate, sync (or syncfs) is skipped on a frozen file system, and deadlockno longer occurs in the aforementioned situation. (BZ#1243404) Previously, in the scenario when a file was opened by file handle (fhandle) with its dentry not present in dcache ("cold dcache") and thenmaking use of the unlink() and close() functions, the inode was not freedupon the close() system call. As a consequence, the iput() final wasdelayed indefinitely. A patch has been provided to fix this bug, and theinode is now freed as expected. (BZ#1243406) Due to a corrupted Executable and Linkable Format (ELF) header in the /proc/vmcore file, the kdump utility failed to provide any information.The underlying source code has been patched, and kdump now providesdebuging information for kernel crashes as intended. (BZ#1245195) Previously, running the multipath request queue caused regressions in cases where paths failed regularly under I/O load. This regressionmanifested as I/O stalls that exceeded 300 seconds. This update reverts thechanges aimed to reduce running the multipath request queue resulting inI/O completing in a timely manner. (BZ#1246095)All kernel users are advised to upgrade to these updated packages, whichcontain backported patches to correct these issues. The system must berebooted for this update to take effect.

Affected Software

32 affected componentsFixes available
redhat/kernel<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-abi-whitelists<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debug<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debug-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debug-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debug-devel<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debug-devel<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debuginfo-common-i686<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-devel<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-doc<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-firmware<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-headers<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/perf<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/perf-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/perf-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/python-perf<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/python-perf-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/python-perf-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debug<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-devel<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-headers<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/perf<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/python-perf<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debuginfo-common-s390x<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-kdump<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-kdump-debuginfo<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-kdump-devel<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-bootwrapper<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6
redhat/kernel-debuginfo-common-ppc64<2.6.32-573.3.1.el6
2.6.32-573.3.1.el6

Remediation

Event History

Aug 13, 2015
Advisory Published
12:00 AM

Frequently Asked Questions

1

What is the severity of RHSA-2015:1623?

RHSA-2015:1623 has a normal security severity rating.

2

How do I fix RHSA-2015:1623?

To fix RHSA-2015:1623, upgrade to kernel version 2.6.32-573.3.1.el6.

3

What systems are affected by RHSA-2015:1623?

RHSA-2015:1623 affects various Red Hat Linux systems using specific kernel package versions.

4

What vulnerabilities are addressed in RHSA-2015:1623?

RHSA-2015:1623 addresses vulnerabilities related to incorrect handling of UDP packets with checksum errors.

5

Is there a workaround for RHSA-2015:1623?

There is no officially recommended workaround for RHSA-2015:1623; patching is the preferred solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203