USN-4227-1: Linux kernel vulnerabilities
7 January 2020
Several security issues were fixed in the Linux kernel.
Releases
Packages
- linux - Linux kernel
- linux-aws - Linux kernel for Amazon Web Services (AWS) systems
- linux-aws-hwe - Linux kernel for Amazon Web Services (AWS-HWE) systems
- linux-azure - Linux kernel for Microsoft Azure Cloud systems
- linux-gcp - Linux kernel for Google Cloud Platform (GCP) systems
- linux-gke-4.15 - Linux kernel for Google Container Engine (GKE) systems
- linux-hwe - Linux hardware enablement (HWE) kernel
- linux-kvm - Linux kernel for cloud environments
- linux-oem - Linux kernel for OEM processors
- linux-oracle - Linux kernel for Oracle Cloud systems
- linux-raspi2 - Linux kernel for Raspberry Pi 2
- linux-snapdragon - Linux kernel for Snapdragon processors
Details
It was discovered that a heap-based buffer overflow existed in the Marvell
WiFi-Ex Driver for the Linux kernel. A physically proximate attacker could
use this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2019-14895, CVE-2019-14901)
It was discovered that a heap-based buffer overflow existed in the Marvell
Libertas WLAN Driver for the Linux kernel. A physically proximate attacker
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2019-14896, CVE-2019-14897)
It was discovered that the Fujitsu ES network device driver for the Linux
kernel did not properly check for errors in some situations, leading to a
NULL pointer dereference. A local attacker could use this to cause a denial
of service. (CVE-2019-16231)
It was discovered that the QLogic Fibre Channel driver in the Linux kernel
did not properly check for error, leading to a NULL pointer dereference. A
local attacker could possibly use this to cause a denial of service (system
crash). (CVE-2019-16233)
Anthony Steinhauser discovered that the Linux kernel did not properly
perform Spectre_RSB mitigations to all processors for PowerPC architecture
systems in some situations. A local attacker could use this to expose
sensitive information. (CVE-2019-18660)
It was discovered that the Mellanox Technologies Innova driver in the Linux
kernel did not properly deallocate memory in certain failure conditions. A
local attacker could use this to cause a denial of service (kernel memory
exhaustion). (CVE-2019-19045)
It was discovered that Geschwister Schneider USB CAN interface driver in
the Linux kernel did not properly deallocate memory in certain failure
conditions. A physically proximate attacker could use this to cause a
denial of service (kernel memory exhaustion). (CVE-2019-19052)
It was discovered that the AMD Display Engine Driver in the Linux kernel
did not properly deallocate memory in certain error conditions. A local
attack could use this to cause a denial of service (memory exhaustion).
(CVE-2019-19083)
It was discovered that the driver for memoryless force-feedback input
devices in the Linux kernel contained a use-after-free vulnerability. A
physically proximate attacker could possibly use this to cause a denial of
service (system crash) or execute arbitrary code. (CVE-2019-19524)
It was discovered that the Microchip CAN BUS Analyzer driver in the Linux
kernel contained a use-after-free vulnerability on device disconnect. A
physically proximate attacker could use this to cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2019-19529)
It was discovered that the PEAK-System Technik USB driver in the Linux
kernel did not properly sanitize memory before sending it to the device. A
physically proximate attacker could use this to expose sensitive
information (kernel memory). (CVE-2019-19534)
Tristan Madani discovered that the ALSA timer implementation in the Linux
kernel contained a use-after-free vulnerability. A local attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2019-19807)
Update instructions
The problem can be corrected by updating your system to the following package versions:
Ubuntu 18.04
-
linux-image-4.15.0-1031-oracle
-
4.15.0-1031.34
-
linux-image-4.15.0-1050-gke
-
4.15.0-1050.53
-
linux-image-4.15.0-1052-kvm
-
4.15.0-1052.52
-
linux-image-4.15.0-1053-raspi2
-
4.15.0-1053.57
-
linux-image-4.15.0-1057-aws
-
4.15.0-1057.59
-
linux-image-4.15.0-1066-oem
-
4.15.0-1066.76
-
linux-image-4.15.0-1070-snapdragon
-
4.15.0-1070.77
-
linux-image-4.15.0-74-generic
-
4.15.0-74.84
-
linux-image-4.15.0-74-generic-lpae
-
4.15.0-74.84
-
linux-image-4.15.0-74-lowlatency
-
4.15.0-74.84
-
linux-image-aws
-
4.15.0.1057.58
-
linux-image-aws-lts-18.04
-
4.15.0.1057.58
-
linux-image-generic
-
4.15.0.74.76
-
linux-image-generic-lpae
-
4.15.0.74.76
-
linux-image-gke
-
4.15.0.1050.53
-
linux-image-gke-4.15
-
4.15.0.1050.53
-
linux-image-kvm
-
4.15.0.1052.52
-
linux-image-lowlatency
-
4.15.0.74.76
-
linux-image-oem
-
4.15.0.1066.70
-
linux-image-oracle
-
4.15.0.1031.36
-
linux-image-oracle-lts-18.04
-
4.15.0.1031.36
-
linux-image-raspi2
-
4.15.0.1053.51
-
linux-image-snapdragon
-
4.15.0.1070.73
-
linux-image-virtual
-
4.15.0.74.76
Ubuntu 16.04
-
linux-image-4.15.0-1031-oracle
-
4.15.0-1031.34~16.04.1
-
linux-image-4.15.0-1052-gcp
-
4.15.0-1052.56
-
linux-image-4.15.0-1057-aws
-
4.15.0-1057.59~16.04.1
-
linux-image-4.15.0-1066-azure
-
4.15.0-1066.71
-
linux-image-4.15.0-74-generic
-
4.15.0-74.83~16.04.1
-
linux-image-4.15.0-74-generic-lpae
-
4.15.0-74.83~16.04.1
-
linux-image-4.15.0-74-lowlatency
-
4.15.0-74.83~16.04.1
-
linux-image-aws-hwe
-
4.15.0.1057.57
-
linux-image-azure
-
4.15.0.1066.69
-
linux-image-azure-edge
-
4.15.0.1066.69
-
linux-image-gcp
-
4.15.0.1052.66
-
linux-image-generic-hwe-16.04
-
4.15.0.74.94
-
linux-image-generic-lpae-hwe-16.04
-
4.15.0.74.94
-
linux-image-gke
-
4.15.0.1052.66
-
linux-image-lowlatency-hwe-16.04
-
4.15.0.74.94
-
linux-image-oem
-
4.15.0.74.94
-
linux-image-oracle
-
4.15.0.1031.24
-
linux-image-virtual-hwe-16.04
-
4.15.0.74.94
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.