USN-4999-1: Linux kernel vulnerabilities
Norbert Slusarek discovered a race condition in the CAN BCM networking protocol of the Linux kernel leading to multiple use-after-free vulnerabilities. A local attacker could use this issue to execute arbitrary code. (CVE-2021-3609) Piotr Krysiuk discovered that the eBPF implementation in the Linux kernel did not properly enforce limits for pointer operations. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-33200) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation did not properly clear received fragments from memory in some situations. A physically proximate attacker could possibly use this issue to inject packets or expose sensitive information. (CVE-2020-24586) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation incorrectly handled encrypted fragments. A physically proximate attacker could possibly use this issue to decrypt fragments. (CVE-2020-24587) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation incorrectly handled certain malformed frames. If a user were tricked into connecting to a malicious server, a physically proximate attacker could use this issue to inject packets. (CVE-2020-24588) Kiyin (尹亮) discovered that the NFC LLCP protocol implementation in the Linux kernel contained a reference counting error. A local attacker could use this to cause a denial of service (system crash). (CVE-2020-25670) Kiyin (尹亮) discovered that the NFC LLCP protocol implementation in the Linux kernel did not properly deallocate memory in certain error situations. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2020-25671, CVE-2020-25672) Kiyin (尹亮) discovered that the NFC LLCP protocol implementation in the Linux kernel did not properly handle error conditions in some situations, leading to an infinite loop. A local attacker could use this to cause a denial of service. (CVE-2020-25673) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation incorrectly handled EAPOL frames from unauthenticated senders. A physically proximate attacker could inject malicious packets to cause a denial of service (system crash). (CVE-2020-26139) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation did not properly verify certain fragmented frames. A physically proximate attacker could possibly use this issue to inject or decrypt packets. (CVE-2020-26141) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation accepted plaintext fragments in certain situations. A physically proximate attacker could use this issue to inject packets. (CVE-2020-26145) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation could reassemble mixed encrypted and plaintext fragments. A physically proximate attacker could possibly use this issue to inject packets or exfiltrate selected fragments. (CVE-2020-26147) Or Cohen discovered that the SCTP implementation in the Linux kernel contained a race condition in some situations, leading to a use-after-free condition. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-23133) Piotr Krysiuk and Benedict Schlueter discovered that the eBPF implementation in the Linux kernel performed out of bounds speculation on pointer arithmetic. A local attacker could use this to expose sensitive information. (CVE-2021-29155) Manfred Paul discovered that the extended Berkeley Packet Filter (eBPF) implementation in the Linux kernel contained an out-of-bounds vulnerability. A local attacker could use this issue to execute arbitrary code. (CVE-2021-31440) Piotr Krysiuk discovered that the eBPF implementation in the Linux kernel did not properly prevent speculative loads in certain situations. A local attacker could use this to expose sensitive information (kernel memory). (CVE-2021-31829)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-lowlatencyto a version that resolves this vulnerability.Fixed in 5.8.0-59.66 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1029-raspito a version that resolves this vulnerability.Fixed in 5.8.0-1029.32 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1038-awsto a version that resolves this vulnerability.Fixed in 5.8.0-1038.40 - Upgrade
Upgrade
ubuntu/linux-image-oracleto a version that resolves this vulnerability.Fixed in 5.8.0.1033.32 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 5.8.0.1036.36 - Upgrade
Upgrade
ubuntu/linux-image-raspi-nolpaeto a version that resolves this vulnerability.Fixed in 5.8.0.1029.31 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-generic-64kto a version that resolves this vulnerability.Fixed in 5.8.0-59.66 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.8.0-59.66 - Upgrade
Upgrade
ubuntu/linux-image-virtualto a version that resolves this vulnerability.Fixed in 5.8.0.59.64 - Upgrade
Upgrade
ubuntu/linux-image-raspito a version that resolves this vulnerability.Fixed in 5.8.0.1029.31 - Upgrade
Upgrade
ubuntu/linux-image-gketo a version that resolves this vulnerability.Fixed in 5.8.0.1035.35 - Upgrade
Upgrade
ubuntu/linux-image-generic-64kto a version that resolves this vulnerability.Fixed in 5.8.0.59.64 - Upgrade
Upgrade
ubuntu/linux-image-genericto a version that resolves this vulnerability.Fixed in 5.8.0.59.64 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1036-azureto a version that resolves this vulnerability.Fixed in 5.8.0-1036.38 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1033-oracleto a version that resolves this vulnerability.Fixed in 5.8.0-1033.34 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 5.8.0.1038.40 - Upgrade
Upgrade
ubuntu/linux-image-kvmto a version that resolves this vulnerability.Fixed in 5.8.0.1030.32 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1030-kvmto a version that resolves this vulnerability.Fixed in 5.8.0-1030.32 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.8.0.59.64 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 5.8.0.1035.35 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1029-raspi-nolpaeto a version that resolves this vulnerability.Fixed in 5.8.0-1029.32 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1035-gcpto a version that resolves this vulnerability.Fixed in 5.8.0-1035.37 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-genericto a version that resolves this vulnerability.Fixed in 5.8.0-59.66 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 5.8.0.59.64 - Upgrade
Upgrade
ubuntu/linux-image-virtual-hwe-20.04to a version that resolves this vulnerability.Fixed in 5.8.0.59.66~20.04.42 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-generic-64kto a version that resolves this vulnerability.Fixed in 5.8.0-59.66~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-lowlatencyto a version that resolves this vulnerability.Fixed in 5.8.0-59.66~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpae-hwe-20.04to a version that resolves this vulnerability.Fixed in 5.8.0.59.66~20.04.42 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-genericto a version that resolves this vulnerability.Fixed in 5.8.0-59.66~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 5.8.0.1035.37~20.04.9 - Upgrade
Upgrade
ubuntu/linux-image-generic-64k-hwe-20.04to a version that resolves this vulnerability.Fixed in 5.8.0.59.66~20.04.42 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1036-azureto a version that resolves this vulnerability.Fixed in 5.8.0-1036.38~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1033-oracleto a version that resolves this vulnerability.Fixed in 5.8.0-1033.34~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-hwe-20.04to a version that resolves this vulnerability.Fixed in 5.8.0.59.66~20.04.42 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1035-gcpto a version that resolves this vulnerability.Fixed in 5.8.0-1035.37~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 5.8.0.1038.40~20.04.11 - Upgrade
Upgrade
ubuntu/linux-image-generic-hwe-20.04to a version that resolves this vulnerability.Fixed in 5.8.0.59.66~20.04.42 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-1038-awsto a version that resolves this vulnerability.Fixed in 5.8.0-1038.40~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.8.0-59-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.8.0-59.66~20.04.1 - Upgrade
Upgrade
ubuntu/linux-image-oracleto a version that resolves this vulnerability.Fixed in 5.8.0.1033.34~20.04.9 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 5.8.0.1036.38~20.04.8
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-4999-1?
The severity of USN-4999-1 is classified as high due to the potential for local attackers to execute arbitrary code.
How do I fix USN-4999-1?
To fix USN-4999-1, users should update their system packages to the latest recommended versions as specified in the advisory.
Which Ubuntu versions are affected by USN-4999-1?
USN-4999-1 affects Ubuntu 20.10, specifically targeting various kernel image packages.
What vulnerabilities are addressed in USN-4999-1?
USN-4999-1 addresses multiple use-after-free vulnerabilities related to a race condition in the Linux kernel's CAN BCM networking protocol.
Can I check if my system is vulnerable to USN-4999-1?
You can check if your system is vulnerable to USN-4999-1 by reviewing the installed kernel version against the versions listed in the security advisory.