CWE
119 362
Advisory Published

USN-4342-1: Linux kernel vulnerabilities

First published: Thu 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 SoftwareAffected VersionHow to fix
All of
ubuntu/linux-image-5.3.0-1016-kvm<5.3.0-1016.17
5.3.0-1016.17
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-1016-oracle<5.3.0-1016.18
5.3.0-1016.18
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-1017-aws<5.3.0-1017.18
5.3.0-1017.18
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-1018-gcp<5.3.0-1018.19
5.3.0-1018.19
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-1020-azure<5.3.0-1020.21
5.3.0-1020.21
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-1023-raspi2<5.3.0-1023.25
5.3.0-1023.25
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-51-generic<5.3.0-51.44
5.3.0-51.44
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-51-generic-lpae<5.3.0-51.44
5.3.0-51.44
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-51-lowlatency<5.3.0-51.44
5.3.0-51.44
Ubuntu Linux=19.10
All of
ubuntu/linux-image-5.3.0-51-snapdragon<5.3.0-51.44
5.3.0-51.44
Ubuntu Linux=19.10
All of
ubuntu/linux-image-aws<5.3.0.1017.19
5.3.0.1017.19
Ubuntu Linux=19.10
All of
ubuntu/linux-image-azure<5.3.0.1020.39
5.3.0.1020.39
Ubuntu Linux=19.10
All of
ubuntu/linux-image-gcp<5.3.0.1018.19
5.3.0.1018.19
Ubuntu Linux=19.10
All of
ubuntu/linux-image-generic<5.3.0.51.42
5.3.0.51.42
Ubuntu Linux=19.10
All of
ubuntu/linux-image-generic-lpae<5.3.0.51.42
5.3.0.51.42
Ubuntu Linux=19.10
All of
ubuntu/linux-image-gke<5.3.0.1018.19
5.3.0.1018.19
Ubuntu Linux=19.10
All of
ubuntu/linux-image-kvm<5.3.0.1016.18
5.3.0.1016.18
Ubuntu Linux=19.10
All of
ubuntu/linux-image-lowlatency<5.3.0.51.42
5.3.0.51.42
Ubuntu Linux=19.10
All of
ubuntu/linux-image-oracle<5.3.0.1016.31
5.3.0.1016.31
Ubuntu Linux=19.10
All of
ubuntu/linux-image-raspi2<5.3.0.1023.20
5.3.0.1023.20
Ubuntu Linux=19.10
All of
ubuntu/linux-image-snapdragon<5.3.0.51.42
5.3.0.51.42
Ubuntu Linux=19.10
All of
ubuntu/linux-image-virtual<5.3.0.51.42
5.3.0.51.42
Ubuntu Linux=19.10
All of
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 Linux=18.04
All of
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 Linux=18.04
All of
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 Linux=18.04
All of
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 Linux=18.04
All of
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 Linux=18.04
All of
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 Linux=18.04
All of
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 Linux=18.04
All of
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 Linux=18.04
All of
ubuntu/linux-image-azure<5.3.0.1020.20
5.3.0.1020.20
Ubuntu Linux=18.04
All of
ubuntu/linux-image-gcp<5.3.0.1018.17
5.3.0.1018.17
Ubuntu Linux=18.04
All of
ubuntu/linux-image-generic-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Linux=18.04
All of
ubuntu/linux-image-generic-lpae-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Linux=18.04
All of
ubuntu/linux-image-gke-5.3<5.3.0.1018.8
5.3.0.1018.8
Ubuntu Linux=18.04
All of
ubuntu/linux-image-lowlatency-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Linux=18.04
All of
ubuntu/linux-image-oracle<5.3.0.1016.17
5.3.0.1016.17
Ubuntu Linux=18.04
All of
ubuntu/linux-image-raspi2-hwe-18.04<5.3.0.1023.12
5.3.0.1023.12
Ubuntu Linux=18.04
All of
ubuntu/linux-image-snapdragon-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Linux=18.04
All of
ubuntu/linux-image-virtual-hwe-18.04<5.3.0.51.104
5.3.0.51.104
Ubuntu Linux=18.04

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • 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.

  • 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.

  • 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.

  • Is USN-4342-1 exploitable remotely?

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

  • 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.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203