USN-4949-1: Linux kernel vulnerabilities

Published May 11, 2021
·
Updated

Ryota Shiga discovered that the eBPF implementation in the Linux kernel did not properly verify that a BPF program only reserved as much memory for a ring buffer as was allocated. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3489) Manfred Paul discovered that the eBPF implementation in the Linux kernel did not properly track bounds on bitwise operations. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3490) Billy Jheng Bing-Jhong discovered that the iouring implementation of the Linux kernel did not properly enforce the MAXRWCOUNT limit in some situations. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3491) It was discovered that the Nouveau GPU driver in the Linux kernel did not properly handle error conditions in some situations. A local attacker could use this to cause a denial of service (system crash). (CVE-2020-25639) Olivier Benjamin, Norbert Manthey, Martin Mazein, and Jan H. Schönherr discovered that the Xen paravirtualization backend in the Linux kernel did not properly propagate errors to frontend drivers in some situations. An attacker in a guest VM could possibly use this to cause a denial of service (host domain crash). (CVE-2021-26930) Jan Beulich discovered that multiple Xen backends in the Linux kernel did not properly handle certain error conditions under paravirtualization. An attacker in a guest VM could possibly use this to cause a denial of service (host domain crash). (CVE-2021-26931) It was discovered that the fastrpc driver in the Linux kernel did not prevent user space applications from sending kernel RPC messages. A local attacker could possibly use this to gain elevated privileges. (CVE-2021-28375) It was discovered that the Freescale Gianfar Ethernet driver for the Linux kernel did not properly handle receive queue overrun when jumbo frames were enabled in some situations. An attacker could use this to cause a denial of service (system crash). (CVE-2021-29264) It was discovered that the USB/IP driver in the Linux kernel contained race conditions during the update of local and shared status. An attacker could use this to cause a denial of service (system crash). (CVE-2021-29265) It was discovered that the vDPA backend virtio driver in the Linux kernel contained a use-after-free vulnerability. An attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-29266) It was discovered that the TIPC protocol implementation in the Linux kernel did not properly validate passed encryption key sizes. A local attacker could use this to cause a denial of service (system crash). (CVE-2021-29646) It was discovered that a race condition existed in the netfilter subsystem of the Linux kernel when replacing tables. A local attacker could use this to cause a denial of service (system crash). (CVE-2021-29650)

Affected Software

69 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-5.8.0-1024-raspi<5.8.0-1024.27
5.8.0-1024.27
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1024-raspi-nolpae<5.8.0-1024.27
5.8.0-1024.27
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1027-kvm<5.8.0-1027.29
5.8.0-1027.29
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1029-oracle<5.8.0-1029.30
5.8.0-1029.30
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1031-gcp<5.8.0-1031.32
5.8.0-1031.32
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1032-azure<5.8.0-1032.34
5.8.0-1032.34
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1033-aws<5.8.0-1033.35
5.8.0-1033.35
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-53-generic<5.8.0-53.60
5.8.0-53.60
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-53-generic-64k<5.8.0-53.60
5.8.0-53.60
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-53-generic-lpae<5.8.0-53.60
5.8.0-53.60
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-53-lowlatency<5.8.0-53.60
5.8.0-53.60
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-aws<5.8.0.1033.35
5.8.0.1033.35
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-azure<5.8.0.1032.32
5.8.0.1032.32
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-gcp<5.8.0.1031.31
5.8.0.1031.31
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-generic<5.8.0.53.58
5.8.0.53.58
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-generic-64k<5.8.0.53.58
5.8.0.53.58
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-generic-lpae<5.8.0.53.58
5.8.0.53.58
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-gke<5.8.0.1031.31
5.8.0.1031.31
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-kvm<5.8.0.1027.29
5.8.0.1027.29
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-lowlatency<5.8.0.53.58
5.8.0.53.58
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-oem-20.04<5.8.0.53.58
5.8.0.53.58
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-oracle<5.8.0.1029.28
5.8.0.1029.28
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-raspi<5.8.0.1024.27
5.8.0.1024.27
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-raspi-nolpae<5.8.0.1024.27
5.8.0.1024.27
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-virtual<5.8.0.53.58
5.8.0.53.58
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-53-generic<5.8.0-53.60~20.04.1
5.8.0-53.60~20.04.1
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-5.8.0-53-generic-64k<5.8.0-53.60~20.04.1
5.8.0-53.60~20.04.1
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-5.8.0-53-generic-lpae<5.8.0-53.60~20.04.1
5.8.0-53.60~20.04.1
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-5.8.0-53-lowlatency<5.8.0-53.60~20.04.1
5.8.0-53.60~20.04.1
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-generic-64k-hwe-20.04<5.8.0.53.60~20.04.37
5.8.0.53.60~20.04.37
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-generic-hwe-20.04<5.8.0.53.60~20.04.37
5.8.0.53.60~20.04.37
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-generic-lpae-hwe-20.04<5.8.0.53.60~20.04.37
5.8.0.53.60~20.04.37
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-lowlatency-hwe-20.04<5.8.0.53.60~20.04.37
5.8.0.53.60~20.04.37
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-virtual-hwe-20.04<5.8.0.53.60~20.04.37
5.8.0.53.60~20.04.37
Ubuntu Ubuntu=20.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-1024-raspi to a version that resolves this vulnerability.

    Fixed in 5.8.0-1024.27
  2. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-1024-raspi-nolpae to a version that resolves this vulnerability.

    Fixed in 5.8.0-1024.27
  3. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-1027-kvm to a version that resolves this vulnerability.

    Fixed in 5.8.0-1027.29
  4. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-1029-oracle to a version that resolves this vulnerability.

    Fixed in 5.8.0-1029.30
  5. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-1031-gcp to a version that resolves this vulnerability.

    Fixed in 5.8.0-1031.32
  6. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-1032-azure to a version that resolves this vulnerability.

    Fixed in 5.8.0-1032.34
  7. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-1033-aws to a version that resolves this vulnerability.

    Fixed in 5.8.0-1033.35
  8. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-generic to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60
  9. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-generic-64k to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60
  10. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-generic-lpae to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60
  11. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60
  12. Upgrade

    Upgrade ubuntu/linux-image-aws to a version that resolves this vulnerability.

    Fixed in 5.8.0.1033.35
  13. Upgrade

    Upgrade ubuntu/linux-image-azure to a version that resolves this vulnerability.

    Fixed in 5.8.0.1032.32
  14. Upgrade

    Upgrade ubuntu/linux-image-gcp to a version that resolves this vulnerability.

    Fixed in 5.8.0.1031.31
  15. Upgrade

    Upgrade ubuntu/linux-image-generic to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.58
  16. Upgrade

    Upgrade ubuntu/linux-image-generic-64k to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.58
  17. Upgrade

    Upgrade ubuntu/linux-image-generic-lpae to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.58
  18. Upgrade

    Upgrade ubuntu/linux-image-gke to a version that resolves this vulnerability.

    Fixed in 5.8.0.1031.31
  19. Upgrade

    Upgrade ubuntu/linux-image-kvm to a version that resolves this vulnerability.

    Fixed in 5.8.0.1027.29
  20. Upgrade

    Upgrade ubuntu/linux-image-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.58
  21. Upgrade

    Upgrade ubuntu/linux-image-oem-20.04 to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.58
  22. Upgrade

    Upgrade ubuntu/linux-image-oracle to a version that resolves this vulnerability.

    Fixed in 5.8.0.1029.28
  23. Upgrade

    Upgrade ubuntu/linux-image-raspi to a version that resolves this vulnerability.

    Fixed in 5.8.0.1024.27
  24. Upgrade

    Upgrade ubuntu/linux-image-raspi-nolpae to a version that resolves this vulnerability.

    Fixed in 5.8.0.1024.27
  25. Upgrade

    Upgrade ubuntu/linux-image-virtual to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.58
  26. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-generic to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60~20.04.1
  27. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-generic-64k to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60~20.04.1
  28. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-generic-lpae to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60~20.04.1
  29. Upgrade

    Upgrade ubuntu/linux-image-5.8.0-53-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.8.0-53.60~20.04.1
  30. Upgrade

    Upgrade ubuntu/linux-image-generic-64k-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.60~20.04.37
  31. Upgrade

    Upgrade ubuntu/linux-image-generic-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.60~20.04.37
  32. Upgrade

    Upgrade ubuntu/linux-image-generic-lpae-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.60~20.04.37
  33. Upgrade

    Upgrade ubuntu/linux-image-lowlatency-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.60~20.04.37
  34. Upgrade

    Upgrade ubuntu/linux-image-virtual-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.8.0.53.60~20.04.37
  35. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch USN-4949-1

Event History

May 11, 2021
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of USN-4949-1?

The vulnerability USN-4949-1 is classified as critical due to its potential to cause a denial of service or allow arbitrary code execution by local attackers.

2

How do I fix USN-4949-1?

To fix USN-4949-1, you should update your Linux kernel packages to the specified versions or later as recommended in the security notice.

3

What systems are affected by USN-4949-1?

USN-4949-1 affects Ubuntu 20.10 systems running specific versions of the Linux kernel.

4

Can USN-4949-1 be exploited remotely?

No, USN-4949-1 can only be exploited by local attackers with user access to the system.

5

What are the consequences of not addressing USN-4949-1?

Failing to address USN-4949-1 could lead to system crashes or unauthorized control of the affected systems.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203