USN-4412-1: Linux kernel vulnerabilities
6 July 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-5.3 - Linux kernel for Amazon Web Services (AWS) systems
- linux-azure - Linux kernel for Microsoft Azure Cloud systems
- linux-azure-5.3 - Linux kernel for Microsoft Azure Cloud systems
- linux-gcp - Linux kernel for Google Cloud Platform (GCP) systems
- linux-gcp-5.3 - Linux kernel for Google Cloud Platform (GCP) systems
- linux-gke-5.3 - Linux kernel for Google Container Engine (GKE) systems
- linux-hwe - Linux hardware enablement (HWE) kernel
- linux-kvm - Linux kernel for cloud environments
- linux-oracle - Linux kernel for Oracle Cloud systems
- linux-oracle-5.3 - Linux kernel for Oracle Cloud systems
- linux-raspi2-5.3 - Linux kernel for Raspberry Pi (V7) systems
Details
Matthew Sheets discovered that the SELinux network label handling
implementation in the Linux kernel could be coerced into de-referencing a
NULL pointer. A remote attacker could use this to cause a denial of service
(system crash). (CVE-2020-10711)
It was discovered that the SCSI generic (sg) driver in the Linux kernel did
not properly handle certain error conditions correctly. A local privileged
attacker could use this to cause a denial of service (system crash).
(CVE-2020-12770)
It was discovered that the USB Gadget device driver in the Linux kernel did
not validate arguments passed from configfs in some situations. A local
attacker could possibly use this to cause a denial of service (system
crash) or possibly expose sensitive information. (CVE-2020-13143)
Dmitry Vyukov discovered that the SELinux netlink security hook in the
Linux kernel did not validate messages in some situations. A privileged
attacker could use this to bypass SELinux netlink restrictions.
(CVE-2020-10751)
It was discovered that the KVM implementation in the Linux kernel did not
properly deallocate memory on initialization for some processors. A local
attacker could possibly use this to cause a denial of service.
(CVE-2020-12768)
Update instructions
The problem can be corrected by updating your system to the following package versions:
Ubuntu 19.10
-
linux-image-5.3.0-1024-kvm
-
5.3.0-1024.26
-
linux-image-5.3.0-1028-oracle
-
5.3.0-1028.30
-
linux-image-5.3.0-1030-aws
-
5.3.0-1030.32
-
linux-image-5.3.0-1030-gcp
-
5.3.0-1030.32
-
linux-image-5.3.0-1032-azure
-
5.3.0-1032.33
-
linux-image-5.3.0-62-generic
-
5.3.0-62.56
-
linux-image-5.3.0-62-generic-lpae
-
5.3.0-62.56
-
linux-image-5.3.0-62-lowlatency
-
5.3.0-62.56
-
linux-image-5.3.0-62-snapdragon
-
5.3.0-62.56
-
linux-image-aws
-
5.3.0.1030.40
-
linux-image-azure
-
5.3.0.1032.50
-
linux-image-gcp
-
5.3.0.1030.40
-
linux-image-generic
-
5.3.0.62.52
-
linux-image-generic-lpae
-
5.3.0.62.52
-
linux-image-gke
-
5.3.0.1030.40
-
linux-image-kvm
-
5.3.0.1024.22
-
linux-image-lowlatency
-
5.3.0.62.52
-
linux-image-oracle
-
5.3.0.1028.43
-
linux-image-snapdragon
-
5.3.0.62.52
-
linux-image-virtual
-
5.3.0.62.52
Ubuntu 18.04
-
linux-image-5.3.0-1028-oracle
-
5.3.0-1028.30~18.04.1
-
linux-image-5.3.0-1028-raspi2
-
5.3.0-1028.30~18.04.2
-
linux-image-5.3.0-1030-aws
-
5.3.0-1030.32~18.04.1
-
linux-image-5.3.0-1030-gcp
-
5.3.0-1030.32~18.04.1
-
linux-image-5.3.0-1030-gke
-
5.3.0-1030.32~18.04.1
-
linux-image-5.3.0-1032-azure
-
5.3.0-1032.33~18.04.1
-
linux-image-5.3.0-62-generic
-
5.3.0-62.56~18.04.1
-
linux-image-5.3.0-62-generic-lpae
-
5.3.0-62.56~18.04.1
-
linux-image-5.3.0-62-lowlatency
-
5.3.0-62.56~18.04.1
-
linux-image-aws
-
5.3.0.1030.28
-
linux-image-azure
-
5.3.0.1032.28
-
linux-image-gcp
-
5.3.0.1030.24
-
linux-image-generic-hwe-18.04
-
5.3.0.62.115
-
linux-image-generic-lpae-hwe-18.04
-
5.3.0.62.115
-
linux-image-gke-5.3
-
5.3.0.1030.15
-
linux-image-gkeop-5.3
-
5.3.0.62.115
-
linux-image-lowlatency-hwe-18.04
-
5.3.0.62.115
-
linux-image-oracle
-
5.3.0.1028.25
-
linux-image-raspi2-hwe-18.04
-
5.3.0.1028.17
-
linux-image-snapdragon-hwe-18.04
-
5.3.0.62.115
-
linux-image-virtual-hwe-18.04
-
5.3.0.62.115
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.