USN-3930-1: Linux kernel vulnerabilities
Mathias Payer and Hui Peng discovered a use-after-free vulnerability in the Advanced Linux Sound Architecture (ALSA) subsystem. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2018-19824) Shlomi Oberman, Yuli Shapiro, and Ran Menscher discovered an information leak in the Bluetooth implementation of the Linux kernel. An attacker within Bluetooth range could use this to expose sensitive information (kernel memory). (CVE-2019-3459, CVE-2019-3460) Jann Horn discovered that the KVM implementation in the Linux kernel contained a use-after-free vulnerability. An attacker in a guest VM with access to /dev/kvm could use this to cause a denial of service (guest VM crash). (CVE-2019-6974) Jim Mattson and Felix Wilhelm discovered a use-after-free vulnerability in the KVM subsystem of the Linux kernel, when using nested virtual machines. A local attacker in a guest VM could use this to cause a denial of service (system crash) or possibly execute arbitrary code in the host system. (CVE-2019-7221) Felix Wilhelm discovered that an information leak vulnerability existed in the KVM subsystem of the Linux kernel, when nested virtualization is used. A local attacker could use this to expose sensitive information (host system memory to a guest VM). (CVE-2019-7222) Jann Horn discovered that the eBPF implementation in the Linux kernel was insufficiently hardened against Spectre V1 attacks. A local attacker could use this to expose sensitive information. (CVE-2019-7308) It was discovered that a use-after-free vulnerability existed in the user- space API for crypto (afalg) implementation in the Linux kernel. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-8912) Jakub Jirasek discovered a use-after-free vulnerability in the SCTP implementation in the Linux kernel. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-8956) It was discovered that the Linux kernel did not properly deallocate memory when handling certain errors while reading files. A local attacker could use this to cause a denial of service (excessive memory consumption). (CVE-2019-8980) It was discovered that a use-after-free vulnerability existed in the IPMI implementation in the Linux kernel. A local attacker with access to the IPMI character device files could use this to cause a denial of service (system crash). (CVE-2019-9003) Jann Horn discovered that the SNMP NAT implementation in the Linux kernel performed insufficient ASN.1 length checks. An attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-9162) Jann Horn discovered that the mmap implementation in the Linux kernel did not properly check for the mmap minimum address in some situations. A local attacker could use this to assist exploiting a kernel NULL pointer dereference vulnerability. (CVE-2019-9213)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-gketo a version that resolves this vulnerability.Fixed in 4.18.0.1008.8 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-17-snapdragonto a version that resolves this vulnerability.Fixed in 4.18.0-17.18 - Upgrade
Upgrade
ubuntu/linux-image-genericto a version that resolves this vulnerability.Fixed in 4.18.0.17.18 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-17-generic-lpaeto a version that resolves this vulnerability.Fixed in 4.18.0-17.18 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 4.18.0.1008.8 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 4.18.0.1014.15 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-1012-awsto a version that resolves this vulnerability.Fixed in 4.18.0-1012.14 - Upgrade
Upgrade
ubuntu/linux-image-virtualto a version that resolves this vulnerability.Fixed in 4.18.0.17.18 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-1011-raspi2to a version that resolves this vulnerability.Fixed in 4.18.0-1011.13 - Upgrade
Upgrade
ubuntu/linux-image-raspi2to a version that resolves this vulnerability.Fixed in 4.18.0.1011.8 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-1014-azureto a version that resolves this vulnerability.Fixed in 4.18.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpaeto a version that resolves this vulnerability.Fixed in 4.18.0.17.18 - Upgrade
Upgrade
ubuntu/linux-image-snapdragonto a version that resolves this vulnerability.Fixed in 4.18.0.17.18 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-17-genericto a version that resolves this vulnerability.Fixed in 4.18.0-17.18 - Upgrade
Upgrade
ubuntu/linux-image-kvmto a version that resolves this vulnerability.Fixed in 4.18.0.1009.9 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-1009-kvmto a version that resolves this vulnerability.Fixed in 4.18.0-1009.9 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-1008-gcpto a version that resolves this vulnerability.Fixed in 4.18.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 4.18.0.17.18 - Upgrade
Upgrade
ubuntu/linux-image-4.18.0-17-lowlatencyto a version that resolves this vulnerability.Fixed in 4.18.0-17.18 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 4.18.0.1012.12
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the vulnerability ID of this advisory?
The vulnerability ID of this advisory is USN-3930-1.
What is the severity of USN-3930-1?
The severity of USN-3930-1 is not specified in the provided information.
How can an attacker exploit CVE-2018-19824?
An attacker can exploit CVE-2018-19824 by physically proximate attack to cause a denial of service (system crash).
What software versions are affected by this vulnerability?
The affected software versions are Ubuntu Ubuntu 18.10 with linux-image-gke 4.18.0.1008.8, linux-image-4.18.0-17-snapdragon 4.18.0-17.18, linux-image-generic 4.18.0.17.18, linux-image-4.18.0-17-generic-lpae 4.18.0-17.18, linux-image-gcp 4.18.0.1008.8, linux-image-azure 4.18.0.1014.15, linux-image-4.18.0-1012-aws 4.18.0-1012.14, linux-image-virtual 4.18.0.17.18, linux-image-4.18.0-1011-raspi2 4.18.0-1011.13, linux-image-raspi2 4.18.0.1011.8, linux-image-4.18.0-1014-azure 4.18.0-1014.14, linux-image-generic-lpae 4.18.0.17.18, linux-image-snapdragon 4.18.0.17.18, linux-image-4.18.0-17-generic 4.18.0-17.18, linux-image-kvm 4.18.0.1009.9, linux-image-4.18.0-1009-kvm 4.18.0-1009.9, linux-image-4.18.0-1008-gcp 4.18.0-1008.9, linux-image-lowlatency 4.18.0.17.18, linux-image-4.18.0-17-lowlatency 4.18.0-17.18, linux-image-aws 4.18.0.1012.12.
Where can I find more information about this vulnerability?
You can find more information about this vulnerability at the following references: [CVE-2018-19824](https://ubuntu.com/security/CVE-2018-19824), [CVE-2019-3459](https://ubuntu.com/security/CVE-2019-3459), [CVE-2019-3460](https://ubuntu.com/security/CVE-2019-3460).