USN-5164-1: Linux kernel vulnerabilities
It was discovered that the Option USB High Speed Mobile device driver in the Linux kernel did not properly handle error conditions. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-37159) It was discovered that the AMD Cryptographic Coprocessor (CCP) driver in the Linux kernel did not properly deallocate memory in some error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2021-3744, CVE-2021-3764)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1031-dell300xto a version that resolves this vulnerability.Fixed in 4.15.0-1031.36 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1084-oracleto a version that resolves this vulnerability.Fixed in 4.15.0-1084.92 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1099-raspi2to a version that resolves this vulnerability.Fixed in 4.15.0-1099.106 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1103-kvmto a version that resolves this vulnerability.Fixed in 4.15.0-1103.105 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1112-gcpto a version that resolves this vulnerability.Fixed in 4.15.0-1112.126 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1116-awsto a version that resolves this vulnerability.Fixed in 4.15.0-1116.123 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1116-snapdragonto a version that resolves this vulnerability.Fixed in 4.15.0-1116.125 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1127-azureto a version that resolves this vulnerability.Fixed in 4.15.0-1127.140 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-163-genericto a version that resolves this vulnerability.Fixed in 4.15.0-163.171 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-163-generic-lpaeto a version that resolves this vulnerability.Fixed in 4.15.0-163.171 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-163-lowlatencyto a version that resolves this vulnerability.Fixed in 4.15.0-163.171 - Upgrade
Upgrade
ubuntu/linux-image-aws-lts-18.04to a version that resolves this vulnerability.Fixed in 4.15.0.1116.119 - Upgrade
Upgrade
ubuntu/linux-image-azure-lts-18.04to a version that resolves this vulnerability.Fixed in 4.15.0.1127.100 - Upgrade
Upgrade
ubuntu/linux-image-dell300xto a version that resolves this vulnerability.Fixed in 4.15.0.1031.33 - Upgrade
Upgrade
ubuntu/linux-image-gcp-lts-18.04to a version that resolves this vulnerability.Fixed in 4.15.0.1112.131 - Upgrade
Upgrade
ubuntu/linux-image-genericto a version that resolves this vulnerability.Fixed in 4.15.0.163.152 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpaeto a version that resolves this vulnerability.Fixed in 4.15.0.163.152 - Upgrade
Upgrade
ubuntu/linux-image-kvmto a version that resolves this vulnerability.Fixed in 4.15.0.1103.99 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 4.15.0.163.152 - Upgrade
Upgrade
ubuntu/linux-image-oracle-lts-18.04to a version that resolves this vulnerability.Fixed in 4.15.0.1084.94 - Upgrade
Upgrade
ubuntu/linux-image-raspi2to a version that resolves this vulnerability.Fixed in 4.15.0.1099.97 - Upgrade
Upgrade
ubuntu/linux-image-snapdragonto a version that resolves this vulnerability.Fixed in 4.15.0.1116.119 - Upgrade
Upgrade
ubuntu/linux-image-virtualto a version that resolves this vulnerability.Fixed in 4.15.0.163.152 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1084-oracleto a version that resolves this vulnerability.Fixed in 4.15.0-1084.92~16.04.1 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1112-gcpto a version that resolves this vulnerability.Fixed in 4.15.0-1112.126~16.04.1 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1116-awsto a version that resolves this vulnerability.Fixed in 4.15.0-1116.123~16.04.1 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1127-azureto a version that resolves this vulnerability.Fixed in 4.15.0-1127.140~16.04.1 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-163-genericto a version that resolves this vulnerability.Fixed in 4.15.0-163.171~16.04.1 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-163-lowlatencyto a version that resolves this vulnerability.Fixed in 4.15.0-163.171~16.04.1 - Upgrade
Upgrade
ubuntu/linux-image-aws-hweto a version that resolves this vulnerability.Fixed in 4.15.0.1116.106 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 4.15.0.1127.118 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 4.15.0.1112.113 - Upgrade
Upgrade
ubuntu/linux-image-generic-hwe-16.04to a version that resolves this vulnerability.Fixed in 4.15.0.163.156 - Upgrade
Upgrade
ubuntu/linux-image-gketo a version that resolves this vulnerability.Fixed in 4.15.0.1112.113 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-hwe-16.04to a version that resolves this vulnerability.Fixed in 4.15.0.163.156 - Upgrade
Upgrade
ubuntu/linux-image-oemto a version that resolves this vulnerability.Fixed in 4.15.0.163.156 - Upgrade
Upgrade
ubuntu/linux-image-oracleto a version that resolves this vulnerability.Fixed in 4.15.0.1084.72 - Upgrade
Upgrade
ubuntu/linux-image-virtual-hwe-16.04to a version that resolves this vulnerability.Fixed in 4.15.0.163.156 - Upgrade
Upgrade
ubuntu/linux-image-4.15.0-1127-azureto a version that resolves this vulnerability.Fixed in 4.15.0-1127.140~14.04.1 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 4.15.0.1127.100
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-5164-1?
The severity of USN-5164-1 is high due to the potential for denial of service or arbitrary code execution.
How do I fix USN-5164-1?
You can fix USN-5164-1 by upgrading to the patched versions of the affected packages listed in the advisory.
Which systems are affected by USN-5164-1?
USN-5164-1 affects various packages in Ubuntu 18.04 that utilize the Linux kernel.
What is CVE-2021-37159 related to USN-5164-1?
CVE-2021-37159 is the identifier for the vulnerability that USN-5164-1 addresses, which involves poor error handling in the USB device driver.
Is there a workaround for USN-5164-1?
No official workaround is available for USN-5164-1, so it is advised to apply the security updates as soon as possible.