CVE-2019-19532: Buffer Overflow

Published Dec 3, 2019
·
Updated

An out-of-bounds write flaw was found in the Linux kernel’s HID drivers. An attacker, able to plug in a malicious USB device, can crash the system or read and write to memory with an incorrect address.

Other sources

In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, drivers/hid/hid-lg2ff.c, drivers/hid/hid-lg3ff.c, drivers/hid/hid-lg4ff.c, drivers/hid/hid-lgff.c, drivers/hid/hid-logitech-hidpp.c, drivers/hid/hid-microsoft.c, drivers/hid/hid-sony.c, drivers/hid/hid-tmff.c, and drivers/hid/hid-zpff.c.

— Ubuntu

Affected Software

60 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1160.21.1.rt56.1158.el7
0:3.10.0-1160.21.1.rt56.1158.el7
redhat/kernel<0:3.10.0-1160.21.1.el7
0:3.10.0-1160.21.1.el7
redhat/kernel<0:3.10.0-693.87.1.el7
0:3.10.0-693.87.1.el7
redhat/kernel<0:3.10.0-957.76.1.el7
0:3.10.0-957.76.1.el7
redhat/kernel<0:3.10.0-1062.49.1.el7
0:3.10.0-1062.49.1.el7
redhat/kernel-rt<0:4.18.0-193.rt13.51.el8
0:4.18.0-193.rt13.51.el8
redhat/kernel<0:4.18.0-193.el8
0:4.18.0-193.el8
Linux Linux kernel<5.3.9
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-1
Google Android
ubuntu/linux-aws<4.4.0-1059.63
4.4.0-1059.63
ubuntu/linux-azure<4.15.0-1064.69~14.04.1
4.15.0-1064.69~14.04.1
ubuntu/linux-lts-xenial<4.4.0-170.199~14.04.1
4.4.0-170.199~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-170.199
4.4.0-170.199
ubuntu/linux-aws<4.4.0-1099.110
4.4.0-1099.110
ubuntu/linux-aws-hwe<4.15.0-1056.58~16.04.1
4.15.0-1056.58~16.04.1
ubuntu/linux-azure<4.15.0-1064.69
4.15.0-1064.69
ubuntu/linux-gcp<4.15.0-1050.53
4.15.0-1050.53
ubuntu/linux-hwe<4.15.0-72.81~16.04.1
4.15.0-72.81~16.04.1
ubuntu/linux-kvm<4.4.0-1063.70
4.4.0-1063.70
ubuntu/linux-oracle<4.15.0-1030.33~16.04.1
4.15.0-1030.33~16.04.1
ubuntu/linux-raspi2<4.4.0-1126.135
4.4.0-1126.135
ubuntu/linux-snapdragon<4.4.0-1130.138
4.4.0-1130.138
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1026.31
4.4.0-1026.31
ubuntu/linux-fips*
ubuntu/linux<4.15.0-72.81
4.15.0-72.81
ubuntu/linux-aws<4.15.0-1056.58
4.15.0-1056.58
ubuntu/linux-aws-5.0<5.0.0-1023.26~18.04.1
5.0.0-1023.26~18.04.1
ubuntu/linux-azure<5.0.0-1028.30~18.04.1
5.0.0-1028.30~18.04.1
ubuntu/linux-azure-5.3<5.3.0-1008.9~18.04.1
5.3.0-1008.9~18.04.1
ubuntu/linux-gcp<5.0.0-1028.29~18.04.1
5.0.0-1028.29~18.04.1
ubuntu/linux-gcp-5.3<5.3.0-1009.10~18.04.1
5.3.0-1009.10~18.04.1
ubuntu/linux-gke-4.15<4.15.0-1049.52
4.15.0-1049.52
ubuntu/linux-gke-5.0<5.0.0-1027.28~18.04.1
5.0.0-1027.28~18.04.1
ubuntu/linux-hwe<5.3.0-26.28~18.04.1
5.3.0-26.28~18.04.1
ubuntu/linux-kvm<4.15.0-1051.51
4.15.0-1051.51
ubuntu/linux-oem<4.15.0-1065.75
4.15.0-1065.75
ubuntu/linux-oem-osp1<5.0.0-1033.38
5.0.0-1033.38
ubuntu/linux-oracle<4.15.0-1030.33
4.15.0-1030.33
ubuntu/linux-oracle-5.0<5.0.0-1009.14~18.04.1
5.0.0-1009.14~18.04.1
ubuntu/linux-raspi2<4.15.0-1052.56
4.15.0-1052.56
ubuntu/linux-snapdragon<4.15.0-1069.76
4.15.0-1069.76
ubuntu/linux-azure-edge*
ubuntu/linux-gcp-edge*
ubuntu/linux-hwe-edge*
ubuntu/linux-aws-fips<4.15.0-2018.18
4.15.0-2018.18
ubuntu/linux-azure-fips<4.15.0-2006.7
4.15.0-2006.7
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-azure-fde*
ubuntu/linux-azure-fde-5.15<5.15.0-1114.123~20.04.1
5.15.0-1114.123~20.04.1
ubuntu/linux-gke*
ubuntu/linux-raspi2*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-raspi-realtime*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-1160.21.1.rt56.1158.el7
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-1160.21.1.el7
  3. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-693.87.1.el7
  4. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-957.76.1.el7
  5. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-1062.49.1.el7
  6. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-193.rt13.51.el8
  7. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-193.el8
  8. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1
  9. Upgrade

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

    Fixed in 4.4.0-1059.63
  10. Upgrade

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

    Fixed in 4.15.0-1064.69~14.04.1
  11. Upgrade

    Upgrade ubuntu/linux-lts-xenial to a version that resolves this vulnerability.

    Fixed in 4.4.0-170.199~14.04.1
  12. Upgrade

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

    Fixed in 4.4.0-170.199
  13. Upgrade

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

    Fixed in 4.4.0-1099.110
  14. Upgrade

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

    Fixed in 4.15.0-1056.58~16.04.1
  15. Upgrade

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

    Fixed in 4.15.0-1064.69
  16. Upgrade

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

    Fixed in 4.15.0-1050.53
  17. Upgrade

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

    Fixed in 4.15.0-72.81~16.04.1
  18. Upgrade

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

    Fixed in 4.4.0-1063.70
  19. Upgrade

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

    Fixed in 4.15.0-1030.33~16.04.1
  20. Upgrade

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

    Fixed in 4.4.0-1126.135
  21. Upgrade

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

    Fixed in 4.4.0-1130.138
  22. Upgrade

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

    Fixed in 4.4.0-1026.31
  23. Upgrade

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

    Fixed in 4.15.0-72.81
  24. Upgrade

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

    Fixed in 4.15.0-1056.58
  25. Upgrade

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

    Fixed in 5.0.0-1023.26~18.04.1
  26. Upgrade

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

    Fixed in 5.0.0-1028.30~18.04.1
  27. Upgrade

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

    Fixed in 5.3.0-1008.9~18.04.1
  28. Upgrade

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

    Fixed in 5.0.0-1028.29~18.04.1
  29. Upgrade

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

    Fixed in 5.3.0-1009.10~18.04.1
  30. Upgrade

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

    Fixed in 4.15.0-1049.52
  31. Upgrade

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

    Fixed in 5.0.0-1027.28~18.04.1
  32. Upgrade

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

    Fixed in 5.3.0-26.28~18.04.1
  33. Upgrade

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

    Fixed in 4.15.0-1051.51
  34. Upgrade

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

    Fixed in 4.15.0-1065.75
  35. Upgrade

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

    Fixed in 5.0.0-1033.38
  36. Upgrade

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

    Fixed in 4.15.0-1030.33
  37. Upgrade

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

    Fixed in 5.0.0-1009.14~18.04.1
  38. Upgrade

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

    Fixed in 4.15.0-1052.56
  39. Upgrade

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

    Fixed in 4.15.0-1069.76
  40. Upgrade

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

    Fixed in 4.15.0-2018.18
  41. Upgrade

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

    Fixed in 4.15.0-2006.7
  42. Upgrade

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

    Fixed in 5.15.0-1114.123~20.04.1
  43. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 5.3.9

Event History

Dec 3, 2019
CVE Published
12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·03:39 PM
Data Sourced
via MITRE·03:39 PM
Description
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 10, 2019
Data Sourced
via Red Hat·04:20 PM
DescriptionSeverityAffected Software
Apr 6, 2020
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2019-19532?

CVE-2019-19532 has a severity rating that indicates it can lead to system crashes or unauthorized memory access if exploited.

2

How do I fix CVE-2019-19532?

To fix CVE-2019-19532, ensure your system is updated to a kernel version 5.3.9 or later.

3

What Linux kernel versions are affected by CVE-2019-19532?

CVE-2019-19532 affects Linux kernel versions prior to 5.3.9.

4

Is CVE-2019-19532 specific to any Linux distributions?

CVE-2019-19532 is known to affect major Linux distributions, including those using the affected kernel versions from Red Hat and Debian.

5

Can a USB device exploit CVE-2019-19532?

Yes, CVE-2019-19532 can be exploited by connecting a malicious USB device to the system.

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