Scientific Linux Security Update : kernel on SL6.x i386/x86_64

This script is Copyright (C) 2017 Tenable Network Security, Inc.


Synopsis :

The remote Scientific Linux host is missing one or more security
updates.

Description :

Security Fix(es) :

- A flaw was found in the Linux kernel's handling of
packets with the URG flag. Applications using the
splice() and tcp_splice_read() functionality can allow a
remote attacker to force the kernel to enter a condition
in which it can loop indefinitely. (CVE-2017-6214,
Moderate)

Bug Fix(es) :

- When executing certain Hadoop jobs, a kernel panic
occasionally occurred on multiple nodes of a cluster.
This update fixes the kernel scheduler, and the kernel
panic no longer occurs under the described
circumstances.

- Previously, memory leak of the struct cred data
structure and related data structures occasionally
occurred. Consequently, system performance was
suboptimal with the symptoms of high I/O operations wait
and small amount of free memory. This update fixes the
reference counter of the struct slab cache to no longer
cause imbalance between the calls to the get_cred()
function and the put_cred() function. As a result, the
memory leak no longer occurs under the described
circumstances.

- Previously, the be2net driver could not detect the link
status properly on IBM Power Systems. Consequently, the
link status was always reported as disconnected. With
this update, be2net has been fixed, and the Network
Interface Cards (NICs) now report the link status
correctly.

- Previously, the RFF_ID and RFT_ID commands in the lpfc
driver were issued in an incorrect order. Consequently,
users were not able to access Logical Unit Numbers
(LUNs). With this update, lpfc has been fixed to issue
RFT_ID before RFF_ID, which is the correct order. As a
result, users can now access LUNs as expected.

- Previously, the kdump mechanism was trying to get the
lock by the vmalloc_sync_all() function during a kernel
panic. Consequently, a deadlock occurred, and the
crashkernel did not boot. This update fixes the
vmalloc_sync_all() function to avoid synchronizing the
vmalloc area on the crashing CPU. As a result, the
crashkernel parameter now boots as expected, and the
kernel dump is collected successfully under the
described circumstances.

See also :

http://www.nessus.org/u?9a8bf96c

Solution :

Update the affected packages.

Risk factor :

Medium / CVSS Base Score : 5.0
(CVSS2#AV:N/AC:L/Au:N/C:N/I:N/A:P)

Family: Scientific Linux Local Security Checks

Nessus Plugin ID: 100568 ()

Bugtraq ID:

CVE ID: CVE-2017-6214

Ready to Amp Up Your Nessus Experience?

Get Nessus Professional to scan unlimited IPs, run compliance checks & more

Buy Nessus Professional Now