|Category:||Red Hat Local Security Checks|
|Title:||RedHat Update for kernel RHSA-2017:3200-01|
|Summary:||The remote host is missing an update for the 'kernel'; package(s) announced via the referenced advisory.|
The remote host is missing an update for the 'kernel'
package(s) announced via the referenced advisory.
The kernel packages contain the Linux
kernel, the core of any Linux operating system.
* A race condition issue leading to a use-after-free flaw was found in the
way the raw packet sockets are implemented in the Linux kernel networking
subsystem handling synchronization. A local user able to open a raw packet
socket (requires the CAP_NET_RAW capability) could use this flaw to elevate
their privileges on the system. (CVE-2017-1000111, Important)
* An exploitable memory corruption flaw was found in the Linux kernel. The
append path can be erroneously switched from UFO to non-UFO in
ip_ufo_append_data() when building an UFO packet with MSG_MORE option. If
unprivileged user namespaces are available, this flaw can be exploited to
gain root privileges. (CVE-2017-1000112, Important)
* A divide-by-zero vulnerability was found in the __tcp_select_window
function in the Linux kernel. This can result in a kernel panic causing a
local denial of service. (CVE-2017-14106, Moderate)
Red Hat would like to thank Willem de Bruijn for reporting CVE-2017-1000111
and Andrey Konovalov for reporting CVE-2017-1000112.
* When the operating system was booted with Red Hat Enterprise
Virtualization, and the eh_deadline sysfs parameter was set to 10s, the
Storage Area Network (SAN) issues caused eh_deadline to trigger with no
handler. Consequently, a kernel panic occurred. This update fixes the lpfc
driver, thus preventing the kernel panic under described circumstances.
* When an NFS server returned the NFS4ERR_BAD_SEQID error to an OPEN
request, the open-owner was removed from the state_owners rbtree.
Consequently, NFS4 client infinite loop that required a reboot to recover
occurred. This update changes NFS4ERR_BAD_SEQID handling to leave the
open-owner in the state_owners rbtree by updating the create_time parameter
so that it looks like a new open-owner. As a result, an NFS4 client is now
able to recover without falling into the infinite recovery loop after
receiving NFS4ERR_BAD_SEQID. (BZ#1491123)
* If an NFS client attempted to mount NFSv3 shares from an NFS server
exported directly to the client's IP address, and this NFS client had
already mounted other shares that originated from the same server but were
exported to the subnetwork which this client was part of, the auth.unix.ip
cache expiration was not handled correctly. Consequently, the client
received the 'stale file handle' errors when trying to mount the share.
This update fixes handling of the ...
Description truncated, please see the referenced URL(s) for more information.
Red Hat Enterprise Linux Desktop (v. 6),
Red Hat Enterprise Linux Server (v. 6),
Red Hat Enterprise Linux Workstation (v. 6)
Please Install the Updated Packages.
Common Vulnerability Exposure (CVE) ID: CVE-2017-14106|
Common Vulnerability Exposure (CVE) ID: CVE-2017-1000111
Common Vulnerability Exposure (CVE) ID: CVE-2017-1000112
|Copyright||Copyright (C) 2017 Greenbone Networks GmbH|
|This is only one of 97459 vulnerability tests in our test suite. Find out more about running a complete security audit.|
To run a free test of this vulnerability against your system, register below.