USN-4751-1: Linux kernel vulnerabilities

Published Feb 25, 2021
·
Updated

It was discovered that the console keyboard driver in the Linux kernel contained a race condition. A local attacker could use this to expose sensitive information (kernel memory). (CVE-2020-25656) Minh Yuan discovered that the tty driver in the Linux kernel contained race conditions when handling fonts. A local attacker could possibly use this to expose sensitive information (kernel memory). (CVE-2020-25668) Bodong Zhao discovered a use-after-free in the Sun keyboard driver implementation in the Linux kernel. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2020-25669) Kiyin (尹亮) discovered that the perf subsystem in the Linux kernel did not properly deallocate memory in some situations. A privileged attacker could use this to cause a denial of service (kernel memory exhaustion). (CVE-2020-25704) Julien Grall discovered that the Xen dom0 event handler in the Linux kernel did not properly limit the number of events queued. An attacker in a guest VM could use this to cause a denial of service in the host OS. (CVE-2020-27673) Jinoh Kang discovered that the Xen event channel infrastructure in the Linux kernel contained a race condition. An attacker in guest could possibly use this to cause a denial of service (dom0 crash). (CVE-2020-27675) Daniel Axtens discovered that PowerPC RTAS implementation in the Linux kernel did not properly restrict memory accesses in some situations. A privileged local attacker could use this to arbitrarily modify kernel memory, potentially bypassing kernel lockdown restrictions. (CVE-2020-27777) It was discovered that the jfs file system implementation in the Linux kernel contained an out-of-bounds read vulnerability. A local attacker could use this to possibly cause a denial of service (system crash). (CVE-2020-27815) Shisong Qin and Bodong Zhao discovered that Speakup screen reader driver in the Linux kernel did not correctly handle setting line discipline in some situations. A local attacker could use this to cause a denial of service (system crash). (CVE-2020-27830, CVE-2020-28941) It was discovered that a use-after-free vulnerability existed in the infiniband hfi1 device driver in the Linux kernel. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2020-27835) It was discovered that an information leak existed in the syscall implementation in the Linux kernel on 32 bit systems. A local attacker could use this to expose sensitive information (kernel memory). (CVE-2020-28588) Minh Yuan discovered that the framebuffer console driver in the Linux kernel did not properly handle fonts in some conditions. A local attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information (kernel memory). (CVE-2020-28974) Michael Kurth and Pawel Wieczorkiewicz discovered that the Xen event processing backend in the Linux kernel did not properly limit the number of events queued. An attacker in a guest VM could use this to cause a denial of service in the host OS. (CVE-2020-29568) Olivier Benjamin and Pawel Wieczorkiewicz discovered a race condition the Xen paravirt block backend in the Linux kernel, leading to a use-after-free vulnerability. An attacker in a guest VM could use this to cause a denial of service in the host OS. (CVE-2020-29569) Jann Horn discovered that the tty subsystem of the Linux kernel did not use consistent locking in some situations, leading to a read-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information (kernel memory). (CVE-2020-29660) Jann Horn discovered a race condition in the tty subsystem of the Linux kernel in the locking for the TIOCSPGRP ioctl(), leading to a use-after- free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2020-29661) It was discovered that a race condition existed that caused the Linux kernel to not properly restrict exit signal delivery. A local attacker could possibly use this to send signals to arbitrary processes. (CVE-2020-35508)

Affected Software

67 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-5.8.0-1016-raspi<5.8.0-1016.19
5.8.0-1016.19
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1016-raspi-nolpae<5.8.0-1016.19
5.8.0-1016.19
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1019-kvm<5.8.0-1019.21
5.8.0-1019.21
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1021-oracle<5.8.0-1021.22
5.8.0-1021.22
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1023-azure<5.8.0-1023.25
5.8.0-1023.25
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1023-gcp<5.8.0-1023.24
5.8.0-1023.24
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-1024-aws<5.8.0-1024.26
5.8.0-1024.26
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-44-generic<5.8.0-44.50
5.8.0-44.50
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-44-generic-64k<5.8.0-44.50
5.8.0-44.50
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-44-generic-lpae<5.8.0-44.50
5.8.0-44.50
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-44-lowlatency<5.8.0-44.50
5.8.0-44.50
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-aws<5.8.0.1024.26
5.8.0.1024.26
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-azure<5.8.0.1023.23
5.8.0.1023.23
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-gcp<5.8.0.1023.23
5.8.0.1023.23
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-generic<5.8.0.44.49
5.8.0.44.49
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-generic-64k<5.8.0.44.49
5.8.0.44.49
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-generic-lpae<5.8.0.44.49
5.8.0.44.49
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-gke<5.8.0.1023.23
5.8.0.1023.23
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-kvm<5.8.0.1019.21
5.8.0.1019.21
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-lowlatency<5.8.0.44.49
5.8.0.44.49
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-oem-20.04<5.8.0.44.49
5.8.0.44.49
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-oracle<5.8.0.1021.20
5.8.0.1021.20
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-raspi<5.8.0.1016.19
5.8.0.1016.19
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-raspi-nolpae<5.8.0.1016.19
5.8.0.1016.19
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-virtual<5.8.0.44.49
5.8.0.44.49
Ubuntu Ubuntu=20.10
All of the following
ubuntu/linux-image-5.8.0-44-generic<5.8.0-44.50~20.04.1
5.8.0-44.50~20.04.1
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-5.8.0-44-generic-lpae<5.8.0-44.50~20.04.1
5.8.0-44.50~20.04.1
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-5.8.0-44-lowlatency<5.8.0-44.50~20.04.1
5.8.0-44.50~20.04.1
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-generic-64k-hwe-20.04<5.8.0.44.50~20.04.30
5.8.0.44.50~20.04.30
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-generic-hwe-20.04<5.8.0.44.50~20.04.30
5.8.0.44.50~20.04.30
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-generic-lpae-hwe-20.04<5.8.0.44.50~20.04.30
5.8.0.44.50~20.04.30
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-lowlatency-hwe-20.04<5.8.0.44.50~20.04.30
5.8.0.44.50~20.04.30
Ubuntu Ubuntu=20.04
All of the following
ubuntu/linux-image-virtual-hwe-20.04<5.8.0.44.50~20.04.30
5.8.0.44.50~20.04.30
Ubuntu Ubuntu=20.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.8.0-1016.19
  2. Upgrade

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

    Fixed in 5.8.0-1016.19
  3. Upgrade

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

    Fixed in 5.8.0-1019.21
  4. Upgrade

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

    Fixed in 5.8.0-1021.22
  5. Upgrade

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

    Fixed in 5.8.0-1023.25
  6. Upgrade

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

    Fixed in 5.8.0-1023.24
  7. Upgrade

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

    Fixed in 5.8.0-1024.26
  8. Upgrade

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

    Fixed in 5.8.0-44.50
  9. Upgrade

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

    Fixed in 5.8.0-44.50
  10. Upgrade

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

    Fixed in 5.8.0-44.50
  11. Upgrade

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

    Fixed in 5.8.0-44.50
  12. Upgrade

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

    Fixed in 5.8.0.1024.26
  13. Upgrade

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

    Fixed in 5.8.0.1023.23
  14. Upgrade

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

    Fixed in 5.8.0.1023.23
  15. Upgrade

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

    Fixed in 5.8.0.44.49
  16. Upgrade

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

    Fixed in 5.8.0.44.49
  17. Upgrade

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

    Fixed in 5.8.0.44.49
  18. Upgrade

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

    Fixed in 5.8.0.1023.23
  19. Upgrade

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

    Fixed in 5.8.0.1019.21
  20. Upgrade

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

    Fixed in 5.8.0.44.49
  21. Upgrade

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

    Fixed in 5.8.0.44.49
  22. Upgrade

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

    Fixed in 5.8.0.1021.20
  23. Upgrade

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

    Fixed in 5.8.0.1016.19
  24. Upgrade

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

    Fixed in 5.8.0.1016.19
  25. Upgrade

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

    Fixed in 5.8.0.44.49
  26. Upgrade

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

    Fixed in 5.8.0-44.50~20.04.1
  27. Upgrade

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

    Fixed in 5.8.0-44.50~20.04.1
  28. Upgrade

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

    Fixed in 5.8.0-44.50~20.04.1
  29. Upgrade

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

    Fixed in 5.8.0.44.50~20.04.30
  30. Upgrade

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

    Fixed in 5.8.0.44.50~20.04.30
  31. Upgrade

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

    Fixed in 5.8.0.44.50~20.04.30
  32. Upgrade

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

    Fixed in 5.8.0.44.50~20.04.30
  33. Upgrade

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

    Fixed in 5.8.0.44.50~20.04.30
  34. Upgrade

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

    Patch USN-4751-1

Event History

Feb 25, 2021
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of USN-4751-1?

The severity of USN-4751-1 is considered to be critical due to the possibility of exposing sensitive information in the kernel memory.

2

How do I fix USN-4751-1?

You can fix USN-4751-1 by upgrading to the latest patched version of the affected Linux kernel packages as recommended in the security advisory.

3

What packages are affected by USN-4751-1?

Affected packages include various linux-image versions for Ubuntu 20.10, including linux-image-5.8.0-1016.19, linux-image-5.8.0-1016-raspi, and others.

4

Who discovered the issue described in USN-4751-1?

The vulnerability described in USN-4751-1 was discovered by Minh Yuan.

5

Can USN-4751-1 be exploited remotely?

No, USN-4751-1 requires local access for exploitation, making it less critical for remote attack vectors.

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