USN-4225-1: Linux kernel vulnerabilities

Published Jan 7, 2020
·
Updated

It was discovered that a heap-based buffer overflow existed in the Marvell WiFi-Ex Driver for the Linux kernel. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-14895, CVE-2019-14901) It was discovered that a heap-based buffer overflow existed in the Marvell Libertas WLAN Driver for the Linux kernel. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-14896, CVE-2019-14897) It was discovered that the Fujitsu ES network device driver for the Linux kernel did not properly check for errors in some situations, leading to a NULL pointer dereference. A local attacker could use this to cause a denial of service. (CVE-2019-16231) Anthony Steinhauser discovered that the Linux kernel did not properly perform SpectreRSB mitigations to all processors for PowerPC architecture systems in some situations. A local attacker could use this to expose sensitive information. (CVE-2019-18660) It was discovered that the Broadcom V3D DRI driver in the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could possibly use this to cause a denial of service (kernel memory exhaustion). (CVE-2019-19044) It was discovered that the Mellanox Technologies Innova driver in the Linux kernel did not properly deallocate memory in certain failure conditions. A local attacker could use this to cause a denial of service (kernel memory exhaustion). (CVE-2019-19045) It was discovered that the Mellanox Technologies ConnectX driver in the Linux kernel did not properly deallocate memory in certain failure conditions. A local attacker could use this to cause a denial of service (kernel memory exhaustion). (CVE-2019-19047) It was discovered that the Intel WiMAX 2400 driver in the Linux kernel did not properly deallocate memory in certain situations. A local attacker could use this to cause a denial of service (kernel memory exhaustion). (CVE-2019-19051) It was discovered that Geschwister Schneider USB CAN interface driver in the Linux kernel did not properly deallocate memory in certain failure conditions. A physically proximate attacker could use this to cause a denial of service (kernel memory exhaustion). (CVE-2019-19052) It was discovered that the netlink-based 802.11 configuration interface in the Linux kernel did not deallocate memory in certain error conditions. A local attacker could possibly use this to cause a denial of service (kernel memory exhaustion). (CVE-2019-19055) It was discovered that the event tracing subsystem of the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (kernel memory exhaustion). (CVE-2019-19072) It was discovered that the driver for memoryless force-feedback input devices in the Linux kernel contained a use-after-free vulnerability. A physically proximate attacker could possibly use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2019-19524) It was discovered that the Microchip CAN BUS Analyzer driver in the Linux kernel contained a use-after-free vulnerability on device disconnect. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-19529) It was discovered that the PEAK-System Technik USB driver in the Linux kernel did not properly sanitize memory before sending it to the device. A physically proximate attacker could use this to expose sensitive information (kernel memory). (CVE-2019-19534) Tristan Madani discovered that the ALSA timer implementation in the Linux kernel contained 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-2019-19807) It was discovered that the DesignWare USB3 controller driver in the Linux kernel did not properly deallocate memory in some error conditions. A local attacker could possibly use this to cause a denial of service (memory exhaustion). (CVE-2019-18813)

Affected Software

53 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-5.3.0-1008-oracle<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-aws<5.3.0-1009.10
5.3.0-1009.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1009-azure<5.3.0-1009.10
5.3.0-1009.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1009-kvm<5.3.0-1009.10
5.3.0-1009.10
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1011-gcp<5.3.0-1011.12
5.3.0-1011.12
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1015-raspi2<5.3.0-1015.17
5.3.0-1015.17
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-26-generic<5.3.0-26.28
5.3.0-26.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-26-generic-lpae<5.3.0-26.28
5.3.0-26.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-26-lowlatency<5.3.0-26.28
5.3.0-26.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-26-snapdragon<5.3.0-26.28
5.3.0-26.28
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-aws<5.3.0.1009.11
5.3.0.1009.11
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-azure<5.3.0.1009.27
5.3.0.1009.27
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-gcp<5.3.0.1011.12
5.3.0.1011.12
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-generic<5.3.0.26.30
5.3.0.26.30
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-generic-lpae<5.3.0.26.30
5.3.0.26.30
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-gke<5.3.0.1011.12
5.3.0.1011.12
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-kvm<5.3.0.1009.11
5.3.0.1009.11
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-lowlatency<5.3.0.26.30
5.3.0.26.30
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-oracle<5.3.0.1008.9
5.3.0.1008.9
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-raspi2<5.3.0.1015.12
5.3.0.1015.12
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-snapdragon<5.3.0.26.30
5.3.0.26.30
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-virtual<5.3.0.26.30
5.3.0.26.30
Ubuntu Ubuntu=19.10
All of the following
ubuntu/linux-image-5.3.0-1009-azure<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-5.3.0-1010-gcp<5.3.0-1010.11~18.04.1
5.3.0-1010.11~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-azure-edge<5.3.0.1009.9
5.3.0.1009.9
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-gcp-edge<5.3.0.1010.10
5.3.0.1010.10
Ubuntu Ubuntu=18.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.3.0-1008.9
  2. Upgrade

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

    Fixed in 5.3.0-1009.10
  3. Upgrade

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

    Fixed in 5.3.0-1009.10
  4. Upgrade

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

    Fixed in 5.3.0-1009.10
  5. Upgrade

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

    Fixed in 5.3.0-1011.12
  6. Upgrade

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

    Fixed in 5.3.0-1015.17
  7. Upgrade

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

    Fixed in 5.3.0-26.28
  8. Upgrade

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

    Fixed in 5.3.0-26.28
  9. Upgrade

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

    Fixed in 5.3.0-26.28
  10. Upgrade

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

    Fixed in 5.3.0-26.28
  11. Upgrade

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

    Fixed in 5.3.0.1009.11
  12. Upgrade

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

    Fixed in 5.3.0.1009.27
  13. Upgrade

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

    Fixed in 5.3.0.1011.12
  14. Upgrade

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

    Fixed in 5.3.0.26.30
  15. Upgrade

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

    Fixed in 5.3.0.26.30
  16. Upgrade

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

    Fixed in 5.3.0.1011.12
  17. Upgrade

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

    Fixed in 5.3.0.1009.11
  18. Upgrade

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

    Fixed in 5.3.0.26.30
  19. Upgrade

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

    Fixed in 5.3.0.1008.9
  20. Upgrade

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

    Fixed in 5.3.0.1015.12
  21. Upgrade

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

    Fixed in 5.3.0.26.30
  22. Upgrade

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

    Fixed in 5.3.0.26.30
  23. Upgrade

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

    Fixed in 5.3.0-1009.10~18.04.1
  24. Upgrade

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

    Fixed in 5.3.0-1010.11~18.04.1
  25. Upgrade

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

    Fixed in 5.3.0.1009.9
  26. Upgrade

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

    Fixed in 5.3.0.1010.10
  27. Upgrade

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

    Patch USN-4225-1
  28. Compensating control

    Perform Spectre_RSB mitigations on all processors for the PowerPC architecture.

Event History

Jan 7, 2020
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-4225-1?

The severity of USN-4225-1 is medium.

2

How can an attacker exploit CVE-2019-14895?

An attacker can exploit CVE-2019-14895 by using a heap-based buffer overflow vulnerability in the Marvell WiFi-Ex Driver for the Linux kernel.

3

What is the remedy for USN-4225-1?

To fix USN-4225-1, update to version 5.3.0-1008.9 or later of the Linux kernel.

4

Which products are affected by USN-4225-1?

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

5

Where can I find more information about USN-4225-1?

You can find more information about USN-4225-1 on the Ubuntu Security website.

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