USN-4208-1: Linux kernel vulnerabilities

Published Dec 2, 2019
·
Updated

Jann Horn discovered that the OverlayFS and ShiftFS Drivers in the Linux kernel did not properly handle reference counting during memory mapping operations when used in conjunction with AUFS. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-15794) Nicolas Waisman discovered that the WiFi driver stack in the Linux kernel did not properly validate SSID lengths. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2019-17133) It was discovered that the ARM Komeda display driver for the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2019-18810) It was discovered that the VirtualBox guest driver implementation in the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2019-19048) It was discovered that the ADIS16400 IIO IMU Driver for the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2019-19060, CVE-2019-19061) It was discovered that the Intel OPA Gen1 Infiniband Driver for the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2019-19065) It was discovered that the AMD Audio Coprocessor driver for the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker with the ability to load modules could use this to cause a denial of service (memory exhaustion). (CVE-2019-19067) It was discovered in the Qualcomm FastRPC Driver for the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2019-19069) It was discovered that the Cascoda CA8210 SPI 802.15.4 wireless controller driver for the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2019-19075) It was discovered that the AMD Display Engine Driver in the Linux kernel did not properly deallocate memory in certain error conditions. A local attack could use this to cause a denial of service (memory exhaustion). (CVE-2019-19083) Nicolas Waisman discovered that the Chelsio T4/T5 RDMA Driver for the Linux kernel performed DMA from a kernel stack. A local attacker could use this to cause a denial of service (system crash). (CVE-2019-17075)

Affected Software

41 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-5.3.0-1007-oracle<5.3.0-1007.8
5.3.0-1007.8
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1008-aws<5.3.0-1008.9
5.3.0-1008.9
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1008-kvm<5.3.0-1008.9
5.3.0-1008.9
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1009-gcp<5.3.0-1009.10
5.3.0-1009.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-24-generic<5.3.0-24.26
5.3.0-24.26
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-24-generic-lpae<5.3.0-24.26
5.3.0-24.26
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-24-lowlatency<5.3.0-24.26
5.3.0-24.26
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-24-snapdragon<5.3.0-24.26
5.3.0-24.26
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-aws<5.3.0.1008.10
5.3.0.1008.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-gcp<5.3.0.1009.10
5.3.0.1009.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-generic<5.3.0.24.28
5.3.0.24.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-generic-lpae<5.3.0.24.28
5.3.0.24.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-gke<5.3.0.1009.10
5.3.0.1009.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-kvm<5.3.0.1008.10
5.3.0.1008.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-lowlatency<5.3.0.24.28
5.3.0.24.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-oracle<5.3.0.1007.8
5.3.0.1007.8
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-snapdragon<5.3.0.24.28
5.3.0.24.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-virtual<5.3.0.24.28
5.3.0.24.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1009-gcp<5.3.0-1009.10~18.04.1
5.3.0-1009.10~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-gcp-edge<5.3.0.1009.9
5.3.0.1009.9
Ubuntu Ubuntu=18.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.3.0-1007.8
  2. Upgrade

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

    Fixed in 5.3.0-1008.9
  3. Upgrade

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

    Fixed in 5.3.0-1008.9
  4. Upgrade

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

    Fixed in 5.3.0-1009.10
  5. Upgrade

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

    Fixed in 5.3.0-24.26
  6. Upgrade

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

    Fixed in 5.3.0-24.26
  7. Upgrade

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

    Fixed in 5.3.0-24.26
  8. Upgrade

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

    Fixed in 5.3.0-24.26
  9. Upgrade

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

    Fixed in 5.3.0.1008.10
  10. Upgrade

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

    Fixed in 5.3.0.1009.10
  11. Upgrade

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

    Fixed in 5.3.0.24.28
  12. Upgrade

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

    Fixed in 5.3.0.24.28
  13. Upgrade

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

    Fixed in 5.3.0.1009.10
  14. Upgrade

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

    Fixed in 5.3.0.1008.10
  15. Upgrade

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

    Fixed in 5.3.0.24.28
  16. Upgrade

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

    Fixed in 5.3.0.1007.8
  17. Upgrade

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

    Fixed in 5.3.0.24.28
  18. Upgrade

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

    Fixed in 5.3.0.24.28
  19. Upgrade

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

    Fixed in 5.3.0-1009.10~18.04.1
  20. Upgrade

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

    Fixed in 5.3.0.1009.9

Event History

Dec 2, 2019
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-4208-1?

The severity of USN-4208-1 is medium.

2

How does the OverlayFS and ShiftFS Drivers in the Linux kernel vulnerability impact the system?

The vulnerability can cause a denial of service (system crash) or possible execution of arbitrary code.

3

Which versions of Ubuntu are affected by USN-4208-1?

Ubuntu 19.10 and Ubuntu 18.04 are affected by USN-4208-1.

4

What is the recommended remedy for USN-4208-1?

Upgrading to the specified versions of the Linux kernel packages is recommended: linux-image-5.3.0-1007-oracle version 5.3.0-1007.8, linux-image-5.3.0-1008-aws version 5.3.0-1008.9, linux-image-5.3.0-1008-kvm version 5.3.0-1008.9, linux-image-5.3.0-1009-gcp version 5.3.0-1009.10, linux-image-5.3.0-24-generic version 5.3.0-24.26, linux-image-5.3.0-24-generic-lpae version 5.3.0-24.26, linux-image-5.3.0-24-lowlatency version 5.3.0-24.26, linux-image-5.3.0-24-snapdragon version 5.3.0-24.26, linux-image-aws version 5.3.0.1008.10, linux-image-gcp version 5.3.0.1009.10, linux-image-generic version 5.3.0.24.28, linux-image-generic-lpae version 5.3.0.24.28, linux-image-gke version 5.3.0.1009.10, linux-image-kvm version 5.3.0.1008.10, linux-image-lowlatency version 5.3.0.24.28, linux-image-oracle version 5.3.0.1007.8, linux-image-snapdragon version 5.3.0.24.28, and linux-image-virtual version 5.3.0.24.28.

5

Where can I find more information about USN-4208-1 vulnerabilities?

For more information about the vulnerabilities, you can refer to the following references: [CVE-2019-15794](https://ubuntu.com/security/CVE-2019-15794), [CVE-2019-17075](https://ubuntu.com/security/CVE-2019-17075), [CVE-2019-17133](https://ubuntu.com/security/CVE-2019-17133).

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