SCIENTIFIC-LINUX-ERRATA Archives

December 2014

SCIENTIFIC-LINUX-ERRATA@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Pat Riehecky <[log in to unmask]>
Reply To:
Date:
Fri, 5 Dec 2014 17:07:41 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (72 lines)
Synopsis:          Moderate: kernel security and bug fix update
Advisory ID:       SLSA-2014:1959-1
Issue Date:        2014-12-04
CVE Numbers:       CVE-2014-0181
--

* It was found that the permission checks performed by the Linux kernel
when a netlink message was received were not sufficient. A local,
unprivileged user could potentially bypass these restrictions by passing a
netlink socket as stdout or stderr to a more privileged process and
altering the output of this process. (CVE-2014-0181, Moderate)

This update also fixes the following bugs:

* Previously, the kernel did not successfully deliver multicast packets
when the multicast querier was disabled. Consequently, the corosync
utility terminated unexpectedly and the affected storage node did not join
its intended cluster. With this update, multicast packets are delivered
properly when the multicast querier is disabled, and corosync handles the
node as expected.

* Previously, the kernel wrote the metadata contained in all system
information blocks on a single page of the /proc/sysinfo file. However,
when the machine configuration was very extensive and the data did not fit
on a single page, the system overwrote random memory regions, which in
turn caused data corruption when reading the /proc/sysconf file. With this
update, /proc/sysinfo automatically allocates a larger buffer if the data
output does not fit the current buffer, which prevents the data
corruption.

* Prior to this update, the it_real_fn() function did not, in certain
cases, successfully acquire the SIGLOCK signal when the do_setitimer()
function used the ITIMER_REAL timer. As a consequence, the current process
entered an endless loop and became unresponsive. This update fixes the bug
and it_real_fn() no longer causes the kernel to become unresponsive.

The system must be rebooted for this update to take effect.
--

SL5
  x86_64
    kernel-2.6.18-400.el5.x86_64.rpm
    kernel-debug-2.6.18-400.el5.x86_64.rpm
    kernel-debug-debuginfo-2.6.18-400.el5.x86_64.rpm
    kernel-debug-devel-2.6.18-400.el5.x86_64.rpm
    kernel-debuginfo-2.6.18-400.el5.x86_64.rpm
    kernel-debuginfo-common-2.6.18-400.el5.x86_64.rpm
    kernel-devel-2.6.18-400.el5.x86_64.rpm
    kernel-headers-2.6.18-400.el5.x86_64.rpm
    kernel-xen-2.6.18-400.el5.x86_64.rpm
    kernel-xen-debuginfo-2.6.18-400.el5.x86_64.rpm
    kernel-xen-devel-2.6.18-400.el5.x86_64.rpm
  i386
    kernel-2.6.18-400.el5.i686.rpm
    kernel-PAE-2.6.18-400.el5.i686.rpm
    kernel-PAE-debuginfo-2.6.18-400.el5.i686.rpm
    kernel-PAE-devel-2.6.18-400.el5.i686.rpm
    kernel-debug-2.6.18-400.el5.i686.rpm
    kernel-debug-debuginfo-2.6.18-400.el5.i686.rpm
    kernel-debug-devel-2.6.18-400.el5.i686.rpm
    kernel-debuginfo-2.6.18-400.el5.i686.rpm
    kernel-debuginfo-common-2.6.18-400.el5.i686.rpm
    kernel-devel-2.6.18-400.el5.i686.rpm
    kernel-headers-2.6.18-400.el5.i386.rpm
    kernel-xen-2.6.18-400.el5.i686.rpm
    kernel-xen-debuginfo-2.6.18-400.el5.i686.rpm
    kernel-xen-devel-2.6.18-400.el5.i686.rpm
  noarch
    kernel-doc-2.6.18-400.el5.noarch.rpm

- Scientific Linux Development Team

ATOM RSS1 RSS2