USN-4226-1: Linux kernel vulnerabilities

Published Jan 7, 2020
·
Updated

Michael Hanselmann discovered that the CIFS implementation in the Linux kernel did not sanitize paths returned by an SMB server. An attacker controlling an SMB server could use this to overwrite arbitrary files. (CVE-2019-10220) 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) It was discovered that the QLogic Fibre Channel driver in the Linux kernel did not properly check for error, leading to a NULL pointer dereference. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2019-16233) 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) 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 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 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 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 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) 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 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 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) 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 NXP PN533 NFC USB driver in the Linux kernel did not properly free resources after a late probe error, leading to a use- after-free vulnerability. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-19526) 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 multiple USB HID device drivers in the Linux kernel did not properly validate device metadata on attachment, leading to out-of- bounds writes. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-19532) 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) It was discovered that in some situations the fair scheduler in the Linux kernel did not permit a process to use its full quota time slice. A local attacker could use this to cause a denial of service. (CVE-2019-19922) It was discovered that the binder IPC implementation in the Linux kernel did not properly perform bounds checking in some situations, leading to an out-of-bounds write. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-2214) 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) 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

61 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-5.0.0-1009-oracle<5.0.0-1009.14
5.0.0-1009.14
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-1023-aws<5.0.0-1023.26
5.0.0-1023.26
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-1024-kvm<5.0.0-1024.26
5.0.0-1024.26
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-1024-raspi2<5.0.0-1024.25
5.0.0-1024.25
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-1028-azure<5.0.0-1028.30
5.0.0-1028.30
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-1028-gcp<5.0.0-1028.29
5.0.0-1028.29
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-38-generic<5.0.0-38.41
5.0.0-38.41
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-38-generic-lpae<5.0.0-38.41
5.0.0-38.41
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-38-lowlatency<5.0.0-38.41
5.0.0-38.41
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-aws<5.0.0.1023.25
5.0.0.1023.25
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-azure<5.0.0.1028.28
5.0.0.1028.28
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-gcp<5.0.0.1028.53
5.0.0.1028.53
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-generic<5.0.0.38.40
5.0.0.38.40
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-generic-lpae<5.0.0.38.40
5.0.0.38.40
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-gke<5.0.0.1028.53
5.0.0.1028.53
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-kvm<5.0.0.1024.25
5.0.0.1024.25
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-lowlatency<5.0.0.38.40
5.0.0.38.40
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-oracle<5.0.0.1009.35
5.0.0.1009.35
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-raspi2<5.0.0.1024.22
5.0.0.1024.22
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-virtual<5.0.0.38.40
5.0.0.38.40
Ubuntu Ubuntu=19.04
All of the following
ubuntu/linux-image-5.0.0-1009-oracle<5.0.0-1009.14~18.04.1
5.0.0-1009.14~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.0.0-1023-aws<5.0.0-1023.26~18.04.1
5.0.0-1023.26~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.0.0-1027-gke<5.0.0-1027.28~18.04.1
5.0.0-1027.28~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.0.0-1028-azure<5.0.0-1028.30~18.04.1
5.0.0-1028.30~18.04.1
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-5.0.0-1033-oem-osp1<5.0.0-1033.38
5.0.0-1033.38
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-aws-edge<5.0.0.1023.37
5.0.0.1023.37
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-azure<5.0.0.1028.39
5.0.0.1028.39
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-gke-5.0<5.0.0.1027.16
5.0.0.1027.16
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-oem-osp1<5.0.0.1033.37
5.0.0.1033.37
Ubuntu Ubuntu=18.04
All of the following
ubuntu/linux-image-oracle-edge<5.0.0.1009.8
5.0.0.1009.8
Ubuntu Ubuntu=18.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.0.0-1009.14
  2. Upgrade

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

    Fixed in 5.0.0-1023.26
  3. Upgrade

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

    Fixed in 5.0.0-1024.26
  4. Upgrade

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

    Fixed in 5.0.0-1024.25
  5. Upgrade

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

    Fixed in 5.0.0-1028.30
  6. Upgrade

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

    Fixed in 5.0.0-1028.29
  7. Upgrade

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

    Fixed in 5.0.0-38.41
  8. Upgrade

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

    Fixed in 5.0.0-38.41
  9. Upgrade

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

    Fixed in 5.0.0-38.41
  10. Upgrade

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

    Fixed in 5.0.0.1023.25
  11. Upgrade

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

    Fixed in 5.0.0.1028.28
  12. Upgrade

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

    Fixed in 5.0.0.1028.53
  13. Upgrade

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

    Fixed in 5.0.0.38.40
  14. Upgrade

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

    Fixed in 5.0.0.38.40
  15. Upgrade

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

    Fixed in 5.0.0.1028.53
  16. Upgrade

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

    Fixed in 5.0.0.1024.25
  17. Upgrade

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

    Fixed in 5.0.0.38.40
  18. Upgrade

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

    Fixed in 5.0.0.1009.35
  19. Upgrade

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

    Fixed in 5.0.0.1024.22
  20. Upgrade

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

    Fixed in 5.0.0.38.40
  21. Upgrade

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

    Fixed in 5.0.0-1009.14~18.04.1
  22. Upgrade

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

    Fixed in 5.0.0-1023.26~18.04.1
  23. Upgrade

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

    Fixed in 5.0.0-1027.28~18.04.1
  24. Upgrade

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

    Fixed in 5.0.0-1028.30~18.04.1
  25. Upgrade

    Upgrade ubuntu/linux-image-5.0.0-1033-oem-osp1 to a version that resolves this vulnerability.

    Fixed in 5.0.0-1033.38
  26. Upgrade

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

    Fixed in 5.0.0.1023.37
  27. Upgrade

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

    Fixed in 5.0.0.1028.39
  28. Upgrade

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

    Fixed in 5.0.0.1027.16
  29. Upgrade

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

    Fixed in 5.0.0.1033.37
  30. Upgrade

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

    Fixed in 5.0.0.1009.8
  31. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch USN-4226-1

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-4226-1?

USN-4226-1 addresses multiple vulnerabilities classified with high severity due to their potential impact on system integrity.

2

How do I fix USN-4226-1?

To resolve USN-4226-1, update your affected Ubuntu systems to the recommended kernel versions provided in the advisory.

3

What systems are affected by USN-4226-1?

USN-4226-1 affects Ubuntu 19.04 systems running specific kernel versions as detailed in the advisory.

4

What vulnerabilities are addressed in USN-4226-1?

USN-4226-1 addresses vulnerabilities including CVE-2019-10220, CVE-2019-14895, and CVE-2019-14896.

5

Who discovered the vulnerabilities in USN-4226-1?

The vulnerabilities addressed in USN-4226-1 were discovered by security researchers including Michael Hanselmann.

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