RHSA-2013:1292: Moderate: kernel security and bug fix update

Published Sep 26, 2013
·
Updated

The kernel packages contain the Linux kernel, the core of any Linuxoperating system.This update fixes the following security issues: A use-after-free flaw was found in the madvise() system call implementation in the Linux kernel. A local, unprivileged user could usethis flaw to cause a denial of service or, potentially, escalate theirprivileges. (CVE-2012-3511, Moderate) A flaw was found in the way the Linux kernel's TCP/IP protocol suite implementation handled IPv6 sockets that used the UDPCORK option. A local,unprivileged user could use this flaw to cause a denial of service.(CVE-2013-4162, Moderate) An information leak flaw in the Linux kernel could allow a local, unprivileged user to leak kernel memory to user-space. (CVE-2013-2141, Low)Red Hat would like to thank Hannes Frederic Sowa for reportingCVE-2013-4162.This update also fixes the following bugs: A bug in the be2net driver prevented communication between NICs using be2net. This update applies a patch addressing this problem along withseveral other upstream patches that fix various other problems. Trafficbetween NICs using the be2net driver now proceeds as expected. (BZ#983864) A recent patch fixing a problem that prevented communication between NICs using the be2net driver caused the firmware of NICs to becomeunresponsive, and thus triggered a kernel panic. The problem was caused byunnecessary usage of a hardware workaround that allows skipping VLAN taginsertion. A patch has been applied and the workaround is now used onlywhen the multi-channel configuration is enabled on the NIC. Note that thebug only affected the NICs with firmware version 4.2.xxxx. (BZ#999819) A bug in the autofs4 mount expiration code could cause the autofs4 module to falsely report a busy tree of NFS mounts as "not in use".Consequently, automount attempted to unmount the tree and failed witha "failed to umount offset" error, leaving the mount tree to appear asempty directories. A patch has been applied to remove an incorrectly usedautofs dentry mount check and the aforementioned problem no longer occurs.(BZ#1001488) A race condition in the beopen function in the be2net driver could trigger the BUGON() macro, which resulted in a kernel panic. A patchaddressing this problem has been applied and the race condition is nowavoided by enabling polling before enabling interrupts globally. Thekernel no longer panics in this situation. (BZ#1005239)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

26 affected componentsFixes available
redhat/kernel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debug<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debug-debuginfo<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debug-devel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debuginfo<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debuginfo-common<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-devel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-doc<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-headers<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-xen<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-xen-debuginfo<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-xen-devel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debug<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debug-debuginfo<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debug-devel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debuginfo<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-debuginfo-common<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-devel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-headers<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-xen<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-xen-debuginfo<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-xen-devel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-kdump<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-kdump-debuginfo<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5
redhat/kernel-kdump-devel<2.6.18-348.18.1.el5
2.6.18-348.18.1.el5

Remediation

Event History

Sep 26, 2013
Advisory Published
12:00 AM

Frequently Asked Questions

1

What is the severity of RHSA-2013:1292?

RHSA-2013:1292 is classified as a moderate severity vulnerability due to a use-after-free flaw that could allow a local, unprivileged user to escalate privileges.

2

How do I fix RHSA-2013:1292?

To fix RHSA-2013:1292, ensure that your system is updated to kernel version 2.6.18-348.18.1.el5 or later.

3

What systems are affected by RHSA-2013:1292?

RHSA-2013:1292 affects Red Hat Enterprise Linux 5 (el5) systems using the specific kernel packages listed.

4

Is there a workaround for RHSA-2013:1292 if I cannot apply the patch immediately?

There are no effective workarounds for RHSA-2013:1292, so it is important to apply the update as soon as possible.

5

What component of the Linux kernel is impacted by RHSA-2013:1292?

The vulnerability in RHSA-2013:1292 specifically affects the madvise() system call implementation within the Linux kernel.

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