Scientific Linux Security Update : kernel on SL7.x x86_64 (20191205)

high Nessus Plugin ID 131832
New! Plugin Severity Now Using CVSS v3

The calculated severity for Plugins has been updated to use CVSS v3 by default. Plugins that do not have a CVSS v3 score will fall back to CVSS v2 for calculating severity. Severity display preferences can be toggled in the settings dropdown.

Synopsis

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

Description

Security Fix(es) :

- Kernel: KVM: OOB memory access via mmio ring buffer (CVE-2019-14821)

- kernel: local attacker can trigger multiple use-after-free conditions results in privilege escalation (CVE-2019-15239)

Bug Fix(es) :

- On SL 7.7 kernel SCSI VPD information for NVMe drives is missing (breaks InfoScale)

- SL7 fnic spamming logs: Current vnic speed set to :
40000

- kernel build: parallelize redhat/mod-sign.sh

- kernel build: speed up module compression step

- Nested VirtualBox VMs on Windows guest has the potential of impacting memory region allocated to other KVM guests

- NULL pointer dereference at check_preempt_wakeup+0x109

- Regression: panic in pick_next_task_rt

- ixgbe reports 'Detected Tx Unit Hang' with adapter reset on SL 7

- [Intel 7.8 Bug] [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

- nvme: dead loop in blk_mq_tagset_wait_completed_request() when it is called from timeout handler

- [mlx5] VF Representer naming is not consistent/persistent through reboots with OSPD deployment

- OS getting restarted because of driver issue with QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA [1077:2532] (rev 02).

- mlx5: Load balancing not working over VF LAG configuration

- SL7.8 - ISST-LTE: vimlp1: Running LTP af_alg04.c (crypto) crash the LPAR

- SL7.5 - Fix security issues on crypto vmx

- SL 7.7 RC1 - Host crashes about 4.5 hours into switch port bounce test

- SL7.6 - cacheinfo code unsafe vs LPM

- xfs hangs on acquiring xfs_buf semaphore

- single CPU VM hangs during open_posix_testsuite

- rcu_sched self-detected stall on CPU while booting with nohz_full

Solution

Update the affected packages.

See Also

http://www.nessus.org/u?7767f8d3

Plugin Details

Severity: High

ID: 131832

File Name: sl_20191205_kernel_on_SL7_x.nasl

Version: 1.3

Type: local

Agent: unix

Published: 12/9/2019

Updated: 2/24/2020

Dependencies: ssh_get_info.nasl

Risk Information

CVSS Score Source: CVE-2019-15239

VPR

Risk Factor: High

Score: 8.1

CVSS v2

Risk Factor: High

Base Score: 7.2

Temporal Score: 5.3

Vector: AV:L/AC:L/Au:N/C:C/I:C/A:C

Temporal Vector: E:U/RL:OF/RC:C

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.8

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Temporal Vector: E:U/RL:O/RC:C

Vulnerability Information

CPE: p-cpe:/a:fermilab:scientific_linux:bpftool, p-cpe:/a:fermilab:scientific_linux:bpftool-debuginfo, p-cpe:/a:fermilab:scientific_linux:kernel, p-cpe:/a:fermilab:scientific_linux:kernel-abi-whitelists, p-cpe:/a:fermilab:scientific_linux:kernel-debug, p-cpe:/a:fermilab:scientific_linux:kernel-debug-debuginfo, p-cpe:/a:fermilab:scientific_linux:kernel-debug-devel, p-cpe:/a:fermilab:scientific_linux:kernel-debuginfo, p-cpe:/a:fermilab:scientific_linux:kernel-debuginfo-common-x86_64, p-cpe:/a:fermilab:scientific_linux:kernel-devel, p-cpe:/a:fermilab:scientific_linux:kernel-doc, p-cpe:/a:fermilab:scientific_linux:kernel-headers, p-cpe:/a:fermilab:scientific_linux:kernel-tools, p-cpe:/a:fermilab:scientific_linux:kernel-tools-debuginfo, p-cpe:/a:fermilab:scientific_linux:kernel-tools-libs, p-cpe:/a:fermilab:scientific_linux:kernel-tools-libs-devel, p-cpe:/a:fermilab:scientific_linux:perf, p-cpe:/a:fermilab:scientific_linux:perf-debuginfo, p-cpe:/a:fermilab:scientific_linux:python-perf, p-cpe:/a:fermilab:scientific_linux:python-perf-debuginfo, x-cpe:/o:fermilab:scientific_linux

Required KB Items: Host/local_checks_enabled, Host/cpu, Host/RedHat/release, Host/RedHat/rpm-list

Exploit Ease: No known exploits are available

Patch Publication Date: 12/5/2019

Vulnerability Publication Date: 8/20/2019

Reference Information

CVE: CVE-2019-14821, CVE-2019-15239