CVE-2019-19524: Use After Free

Published Nov 15, 2019
·
Updated

A use-after-free flaw was found in the Linux kernel’s input device driver functionality when unplugging a device. A user with physical access could use this flaw to crash the system.

Other sources

In the Linux kernel before 5.3.12, there is a use-after-free bug that can be caused by a malicious USB device in the drivers/input/ff-memless.c driver, aka CID-fa3a5a1880c9.

— Ubuntu

In the Linux kernel, there is a use-after-free bug that can be caused by a malicious USB device in the drivers/input/ff-memless.c

References:

http://www.openwall.com/lists/oss-security/2019/12/03/4 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.12 http://seclists.org/oss-sec/2019/q4/115

Upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fa3a5a1880c91bb92594ad42dfe9eedad7996b86

— Red Hat

Affected Software

64 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1160.rt56.1131.el7
0:3.10.0-1160.rt56.1131.el7
redhat/kernel-alt<0:4.14.0-115.21.2.el7a
0:4.14.0-115.21.2.el7a
redhat/kernel<0:3.10.0-1160.el7
0:3.10.0-1160.el7
redhat/kernel-rt<0:4.18.0-240.rt7.54.el8
0:4.18.0-240.rt7.54.el8
redhat/kernel<0:4.18.0-240.el8
0:4.18.0-240.el8
Linux Linux kernel<5.3.12
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
Canonical Ubuntu Linux=19.10
Debian Debian Linux=8.0
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-1060.64
4.4.0-1060.64
ubuntu/linux-azure<4.15.0-1066.71~14.04.1
4.15.0-1066.71~14.04.1
ubuntu/linux-lts-xenial<4.4.0-171.200~14.04.1
4.4.0-171.200~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-171.200
4.4.0-171.200
ubuntu/linux-aws<4.4.0-1100.111
4.4.0-1100.111
ubuntu/linux-aws-hwe<4.15.0-1057.59~16.04.1
4.15.0-1057.59~16.04.1
ubuntu/linux-azure<4.15.0-1066.71
4.15.0-1066.71
ubuntu/linux-gcp<4.15.0-1052.56
4.15.0-1052.56
ubuntu/linux-hwe<4.15.0-74.83~16.04.1
4.15.0-74.83~16.04.1
ubuntu/linux-kvm<4.4.0-1064.71
4.4.0-1064.71
ubuntu/linux-oracle<4.15.0-1031.34~16.04.1
4.15.0-1031.34~16.04.1
ubuntu/linux-raspi2<4.4.0-1127.136
4.4.0-1127.136
ubuntu/linux-snapdragon<4.4.0-1131.139
4.4.0-1131.139
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1027.32
4.4.0-1027.32
ubuntu/linux-fips*
ubuntu/linux<4.15.0-74.84
4.15.0-74.84
ubuntu/linux-aws<4.15.0-1057.59
4.15.0-1057.59
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-1009.10~18.04.1
5.3.0-1009.10~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-1010.11~18.04.1
5.3.0-1010.11~18.04.1
ubuntu/linux-gke-4.15<4.15.0-1050.53
4.15.0-1050.53
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-1052.52
4.15.0-1052.52
ubuntu/linux-oem<4.15.0-1066.76
4.15.0-1066.76
ubuntu/linux-oem-osp1<5.0.0-1033.38
5.0.0-1033.38
ubuntu/linux-oracle<4.15.0-1031.34
4.15.0-1031.34
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-1053.57
4.15.0-1053.57
ubuntu/linux-snapdragon<4.15.0-1070.77
4.15.0-1070.77
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-gke*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
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.rt56.1131.el7
  2. Upgrade

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

    Fixed in 0:4.14.0-115.21.2.el7a
  3. Upgrade

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

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

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

    Fixed in 0:4.18.0-240.rt7.54.el8
  5. Upgrade

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

    Fixed in 0:4.18.0-240.el8
  6. 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
  7. Upgrade

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

    Fixed in 4.4.0-1060.64
  8. Upgrade

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

    Fixed in 4.15.0-1066.71~14.04.1
  9. Upgrade

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

    Fixed in 4.4.0-171.200~14.04.1
  10. Upgrade

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

    Fixed in 4.4.0-171.200
  11. Upgrade

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

    Fixed in 4.4.0-1100.111
  12. Upgrade

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

    Fixed in 4.15.0-1057.59~16.04.1
  13. Upgrade

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

    Fixed in 4.15.0-1066.71
  14. Upgrade

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

    Fixed in 4.15.0-1052.56
  15. Upgrade

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

    Fixed in 4.15.0-74.83~16.04.1
  16. Upgrade

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

    Fixed in 4.4.0-1064.71
  17. Upgrade

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

    Fixed in 4.15.0-1031.34~16.04.1
  18. Upgrade

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

    Fixed in 4.4.0-1127.136
  19. Upgrade

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

    Fixed in 4.4.0-1131.139
  20. Upgrade

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

    Fixed in 4.4.0-1027.32
  21. Upgrade

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

    Fixed in 4.15.0-74.84
  22. Upgrade

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

    Fixed in 4.15.0-1057.59
  23. Upgrade

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

    Fixed in 5.0.0-1023.26~18.04.1
  24. Upgrade

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

    Fixed in 5.0.0-1028.30~18.04.1
  25. Upgrade

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

    Fixed in 5.3.0-1009.10~18.04.1
  26. Upgrade

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

    Fixed in 5.0.0-1028.29~18.04.1
  27. Upgrade

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

    Fixed in 5.3.0-1010.11~18.04.1
  28. Upgrade

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

    Fixed in 4.15.0-1050.53
  29. Upgrade

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

    Fixed in 5.0.0-1027.28~18.04.1
  30. Upgrade

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

    Fixed in 5.3.0-26.28~18.04.1
  31. Upgrade

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

    Fixed in 4.15.0-1052.52
  32. Upgrade

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

    Fixed in 4.15.0-1066.76
  33. Upgrade

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

    Fixed in 5.0.0-1033.38
  34. Upgrade

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

    Fixed in 4.15.0-1031.34
  35. Upgrade

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

    Fixed in 5.0.0-1009.14~18.04.1
  36. Upgrade

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

    Fixed in 4.15.0-1053.57
  37. Upgrade

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

    Fixed in 4.15.0-1070.77
  38. Upgrade

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

    Fixed in 4.15.0-2018.18
  39. Upgrade

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

    Fixed in 4.15.0-2006.7
  40. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 5.3.12
  41. Configuration

    For Red Hat Enterprise Linux 7 or higher, blacklist the ff-memless kernel module to prevent it from loading automatically.

    Linux kernel ff-memless module loading = blacklisted

Event History

Nov 15, 2019
CVE Published
12:00 AM
Dec 3, 2019
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·03:42 PM
Data Sourced
via MITRE·03:42 PM
Description
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 13, 2019
Data Sourced
via Red Hat·07:27 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-19524?

CVE-2019-19524 is classified as a high severity vulnerability due to its potential to allow system crashes with physical access.

2

How do I fix CVE-2019-19524?

To fix CVE-2019-19524, ensure your kernel version is updated to at least 5.3.12 or the appropriate patched version for your distribution.

3

What systems are affected by CVE-2019-19524?

CVE-2019-19524 affects various Linux kernel versions prior to 5.3.12, including specific versions of Red Hat, Ubuntu, Debian, and Android.

4

Can CVE-2019-19524 be exploited remotely?

No, exploitation of CVE-2019-19524 requires physical access to the vulnerable system through a malicious USB device.

5

What type of vulnerability is CVE-2019-19524?

CVE-2019-19524 is a use-after-free vulnerability in the Linux kernel's input device driver functionality.

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