USN-4342-1: Linux kernel vulnerabilities

Published Apr 30, 2020
·
Updated

Al Viro discovered that the Linux kernel for s390x systems did not properly perform page table upgrades for kernel sections that use secondary address mode. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2020-11884) It was discovered that the Intel Wi-Fi driver in the Linux kernel did not properly check for errors in some situations. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2019-16234) Tristan Madani discovered that the block I/O tracing implementation in the Linux kernel contained a race condition. A local attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2019-19768) It was discovered that the vhost net driver in the Linux kernel contained a stack buffer overflow. A local attacker with the ability to perform ioctl() calls on /dev/vhost-net could use this to cause a denial of service (system crash). (CVE-2020-10942) It was discovered that the virtual terminal implementation in the Linux kernel contained a race condition. A local attacker could possibly use this to cause a denial of service (system crash) or expose sensitive information. (CVE-2020-8648) Shijie Luo discovered that the ext4 file system implementation in the Linux kernel did not properly check for a too-large journal size. An attacker could use this to construct a malicious ext4 image that, when mounted, could cause a denial of service (soft lockup). (CVE-2020-8992) Jordy Zomer discovered that the floppy driver in the Linux kernel did not properly check for errors in some situations. A local attacker could possibly use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2020-9383)

Affected Software

81 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-5.3.0-1016-kvm<5.3.0-1016.17
5.3.0-1016.17
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1016-oracle<5.3.0-1016.18
5.3.0-1016.18
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1017-aws<5.3.0-1017.18
5.3.0-1017.18
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1018-gcp<5.3.0-1018.19
5.3.0-1018.19
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1020-azure<5.3.0-1020.21
5.3.0-1020.21
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1023-raspi2<5.3.0-1023.25
5.3.0-1023.25
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-51-generic<5.3.0-51.44
5.3.0-51.44
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-51-generic-lpae<5.3.0-51.44
5.3.0-51.44
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-51-lowlatency<5.3.0-51.44
5.3.0-51.44
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-51-snapdragon<5.3.0-51.44
5.3.0-51.44
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-aws<5.3.0.1017.19
5.3.0.1017.19
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-azure<5.3.0.1020.39
5.3.0.1020.39
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-gcp<5.3.0.1018.19
5.3.0.1018.19
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-generic<5.3.0.51.42
5.3.0.51.42
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-generic-lpae<5.3.0.51.42
5.3.0.51.42
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-gke<5.3.0.1018.19
5.3.0.1018.19
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-kvm<5.3.0.1016.18
5.3.0.1016.18
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-lowlatency<5.3.0.51.42
5.3.0.51.42
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-oracle<5.3.0.1016.31
5.3.0.1016.31
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-raspi2<5.3.0.1023.20
5.3.0.1023.20
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-snapdragon<5.3.0.51.42
5.3.0.51.42
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-virtual<5.3.0.51.42
5.3.0.51.42
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1016-oracle<5.3.0-1016.18~18.04.1
5.3.0-1016.18~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.3.0-1018-gcp<5.3.0-1018.19~18.04.1
5.3.0-1018.19~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.3.0-1018-gke<5.3.0-1018.19~18.04.1
5.3.0-1018.19~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.3.0-1020-azure<5.3.0-1020.21~18.04.1
5.3.0-1020.21~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.3.0-1023-raspi2<5.3.0-1023.25~18.04.1
5.3.0-1023.25~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.3.0-51-generic<5.3.0-51.44~18.04.2
5.3.0-51.44~18.04.2
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.3.0-51-generic-lpae<5.3.0-51.44~18.04.2
5.3.0-51.44~18.04.2
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.3.0-51-lowlatency<5.3.0-51.44~18.04.2
5.3.0-51.44~18.04.2
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-azure<5.3.0.1020.20
5.3.0.1020.20
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-gcp<5.3.0.1018.17
5.3.0.1018.17
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-generic-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-generic-lpae-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-gke-5.3<5.3.0.1018.8
5.3.0.1018.8
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-lowlatency-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-oracle<5.3.0.1016.17
5.3.0.1016.17
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-raspi2-hwe-18.04<5.3.0.1023.12
5.3.0.1023.12
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-snapdragon-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-virtual-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Ubuntu=18.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.3.0-1016.17
  2. Upgrade

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

    Fixed in 5.3.0-1016.18
  3. Upgrade

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

    Fixed in 5.3.0-1017.18
  4. Upgrade

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

    Fixed in 5.3.0-1018.19
  5. Upgrade

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

    Fixed in 5.3.0-1020.21
  6. Upgrade

    Upgrade ubuntu/linux-image-5.3.0-1023-raspi2 to a version that resolves this vulnerability.

    Fixed in 5.3.0-1023.25
  7. Upgrade

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

    Fixed in 5.3.0-51.44
  8. Upgrade

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

    Fixed in 5.3.0-51.44
  9. Upgrade

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

    Fixed in 5.3.0-51.44
  10. Upgrade

    Upgrade ubuntu/linux-image-5.3.0-51-snapdragon to a version that resolves this vulnerability.

    Fixed in 5.3.0-51.44
  11. Upgrade

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

    Fixed in 5.3.0.1017.19
  12. Upgrade

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

    Fixed in 5.3.0.1020.39
  13. Upgrade

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

    Fixed in 5.3.0.1018.19
  14. Upgrade

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

    Fixed in 5.3.0.51.42
  15. Upgrade

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

    Fixed in 5.3.0.51.42
  16. Upgrade

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

    Fixed in 5.3.0.1018.19
  17. Upgrade

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

    Fixed in 5.3.0.1016.18
  18. Upgrade

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

    Fixed in 5.3.0.51.42
  19. Upgrade

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

    Fixed in 5.3.0.1016.31
  20. Upgrade

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

    Fixed in 5.3.0.1023.20
  21. Upgrade

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

    Fixed in 5.3.0.51.42
  22. Upgrade

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

    Fixed in 5.3.0.51.42
  23. Upgrade

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

    Fixed in 5.3.0-1016.18~18.04.1
  24. Upgrade

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

    Fixed in 5.3.0-1018.19~18.04.1
  25. Upgrade

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

    Fixed in 5.3.0-1018.19~18.04.1
  26. Upgrade

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

    Fixed in 5.3.0-1020.21~18.04.1
  27. Upgrade

    Upgrade ubuntu/linux-image-5.3.0-1023-raspi2 to a version that resolves this vulnerability.

    Fixed in 5.3.0-1023.25~18.04.1
  28. Upgrade

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

    Fixed in 5.3.0-51.44~18.04.2
  29. Upgrade

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

    Fixed in 5.3.0-51.44~18.04.2
  30. Upgrade

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

    Fixed in 5.3.0-51.44~18.04.2
  31. Upgrade

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

    Fixed in 5.3.0.1020.20
  32. Upgrade

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

    Fixed in 5.3.0.1018.17
  33. Upgrade

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

    Fixed in 5.3.0.51.104
  34. Upgrade

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

    Fixed in 5.3.0.51.104
  35. Upgrade

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

    Fixed in 5.3.0.1018.8
  36. Upgrade

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

    Fixed in 5.3.0.51.104
  37. Upgrade

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

    Fixed in 5.3.0.1016.17
  38. Upgrade

    Upgrade ubuntu/linux-image-raspi2-hwe-18.04 to a version that resolves this vulnerability.

    Fixed in 5.3.0.1023.12
  39. Upgrade

    Upgrade ubuntu/linux-image-snapdragon-hwe-18.04 to a version that resolves this vulnerability.

    Fixed in 5.3.0.51.104
  40. Upgrade

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

    Fixed in 5.3.0.51.104

Event History

Apr 30, 2020
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-4342-1?

The severity of USN-4342-1 is high due to the possibility of a denial of service or arbitrary code execution.

2

How do I fix USN-4342-1?

To fix USN-4342-1, you should update your Linux kernel packages to the latest versions as specified in the advisory.

3

What systems are affected by USN-4342-1?

USN-4342-1 affects Ubuntu 19.10 systems running the specified Linux kernel versions on s390x architecture.

4

Is USN-4342-1 exploitable remotely?

No, USN-4342-1 is not remotely exploitable; it requires local access for exploitation.

5

What consequences can arise from USN-4342-1 if left unpatched?

If left unpatched, USN-4342-1 can lead to system crashes and potential arbitrary code execution by local attackers.

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