USN-4157-1: Linux kernel vulnerabilities
Wen Huang discovered that the Marvell Wi-Fi device driver in the Linux kernel did not properly perform bounds checking, leading to a heap overflow. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-14814, CVE-2019-14815, CVE-2019-14816) Matt Delco discovered that the KVM hypervisor implementation in the Linux kernel did not properly perform bounds checking when handling coalesced MMIO write operations. A local attacker with write access to /dev/kvm could use this to cause a denial of service (system crash). (CVE-2019-14821) Hui Peng and Mathias Payer discovered that the 91x Wi-Fi driver in the Linux kernel did not properly handle error conditions on initialization, leading to a double-free vulnerability. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2019-15504) It was discovered that the Technisat DVB-S/S2 USB device driver in the Linux kernel contained a buffer overread. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2019-15505) Brad Spengler discovered that a Spectre mitigation was improperly implemented in the ptrace susbsystem of the Linux kernel. A local attacker could possibly use this to expose sensitive information. (CVE-2019-15902) It was discovered that the IPv6 RDS implementation in the Linux kernel did not properly initialize fields in a data structure returned to user space. A local attacker could use this to expose sensitive information (kernel memory). Please note that the RDS protocol is disabled via blocklist in Ubuntu by default. (CVE-2019-16714) It was discovered that an integer overflow existed in the Binder implementation of the Linux kernel, leading to a buffer overflow. A local attacker could use this to escalate privileges. (CVE-2019-2181)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-5.0.0-1019-awsto a version that resolves this vulnerability.Fixed in 5.0.0-1019.21 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-1020-kvmto a version that resolves this vulnerability.Fixed in 5.0.0-1020.21 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-1020-raspi2to a version that resolves this vulnerability.Fixed in 5.0.0-1020.20 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-1021-gcpto a version that resolves this vulnerability.Fixed in 5.0.0-1021.21 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-1023-azureto a version that resolves this vulnerability.Fixed in 5.0.0-1023.24 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-1024-snapdragonto a version that resolves this vulnerability.Fixed in 5.0.0-1024.25 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-32-genericto a version that resolves this vulnerability.Fixed in 5.0.0-32.34 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-32-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.0.0-32.34 - Upgrade
Upgrade
ubuntu/linux-image-5.0.0-32-lowlatencyto a version that resolves this vulnerability.Fixed in 5.0.0-32.34 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 5.0.0.1019.20 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 5.0.0.1023.22 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 5.0.0.1021.47 - Upgrade
Upgrade
ubuntu/linux-image-genericto a version that resolves this vulnerability.Fixed in 5.0.0.32.33 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.0.0.32.33 - Upgrade
Upgrade
ubuntu/linux-image-gketo a version that resolves this vulnerability.Fixed in 5.0.0.1021.47 - Upgrade
Upgrade
ubuntu/linux-image-kvmto a version that resolves this vulnerability.Fixed in 5.0.0.1020.20 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 5.0.0.32.33 - Upgrade
Upgrade
ubuntu/linux-image-raspi2to a version that resolves this vulnerability.Fixed in 5.0.0.1020.17 - Upgrade
Upgrade
ubuntu/linux-image-snapdragonto a version that resolves this vulnerability.Fixed in 5.0.0.1024.17 - Upgrade
Upgrade
ubuntu/linux-image-virtualto a version that resolves this vulnerability.Fixed in 5.0.0.32.33 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch USN-4157-1
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the vulnerability ID for this Linux kernel vulnerability?
The vulnerability ID for this Linux kernel vulnerability is CVE-2019-14814, CVE-2019-14815, CVE-2019-14816.
What is the severity of this vulnerability?
The severity of this vulnerability is not specified.
Which Linux kernel versions are affected by this vulnerability?
The Linux kernel versions affected by this vulnerability are 5.0.0-1019.21, 5.0.0-1020.21, 5.0.0-1020.20, 5.0.0-1021.21, 5.0.0-1023.24, 5.0.0-1024.25, 5.0.0-32.34, 5.0.0-32.34, 5.0.0-32.34, 5.0.0.1019.20, 5.0.0.1023.22, 5.0.0.1021.47, 5.0.0.32.33, 5.0.0.32.33, 5.0.0.1021.47, 5.0.0.1020.20, 5.0.0.32.33, 5.0.0.1020.17, 5.0.0.1024.17, 5.0.0.32.33.
How can a local attacker exploit this vulnerability?
A local attacker can exploit this vulnerability by using it to cause a denial of service (system crash) or possibly execute arbitrary code.
Where can I find more information about this vulnerability?
You can find more information about this vulnerability at the following references: [CVE-2019-14814](https://ubuntu.com/security/CVE-2019-14814), [CVE-2019-14815](https://ubuntu.com/security/CVE-2019-14815), [CVE-2019-14816](https://ubuntu.com/security/CVE-2019-14816).