CVE-2019-15221: Null Pointer Dereference

Published Aug 19, 2019
·
Updated

An issue was discovered in the Linux kernel before 5.1.17. There is a NULL pointer dereference caused by a malicious USB device in the sound/usb/line6/pcm.c driver.

Upstream patch:

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

References:

https://www.openwall.com/lists/oss-security/2019/08/20/2 https://syzkaller.appspot.com/bug?id=240f09164db2c3d3af33a117c713dc7650dc29d6

Affected Software

61 affected componentsFixes available
Linux Linux kernel<5.1.17
NetApp H410c Firmware
NetApp H410c
NetApp Active Iq Unified Manager Vmware Vsphere
NetApp Data Availability Services
NetApp Solidfire \& Hci Management Node
NetApp Solidfire Baseboard Management Controller
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
Debian Debian Linux=8.0
openSUSE Leap=15.0
openSUSE Leap=15.1
NetApp Baseboard Management Controller H410c Firmware
NetApp Baseboard Management Controller H410c
All of the following
NetApp H410c Firmware
NetApp H410c
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1
ubuntu/linux-aws<4.4.0-1062.66
4.4.0-1062.66
ubuntu/linux-azure<4.15.0-1059.64~14.04.1
4.15.0-1059.64~14.04.1
ubuntu/linux-lts-xenial<4.4.0-174.204~14.04.1
4.4.0-174.204~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-174.204
4.4.0-174.204
ubuntu/linux-aws<4.4.0-1102.113
4.4.0-1102.113
ubuntu/linux-aws-hwe<4.15.0-1047.49~16.04.1
4.15.0-1047.49~16.04.1
ubuntu/linux-azure<4.15.0-1056.61
4.15.0-1056.61
ubuntu/linux-gcp<4.15.0-1041.43
4.15.0-1041.43
ubuntu/linux-hwe<4.15.0-60.67~16.04.1
4.15.0-60.67~16.04.1
ubuntu/linux-kvm<4.4.0-1066.73
4.4.0-1066.73
ubuntu/linux-oracle<4.15.0-1022.25~16.04.1
4.15.0-1022.25~16.04.1
ubuntu/linux-raspi2<4.4.0-1129.138
4.4.0-1129.138
ubuntu/linux-snapdragon<4.4.0-1133.141
4.4.0-1133.141
ubuntu/linux-fips<4.4.0-1029.34
4.4.0-1029.34
ubuntu/linux-fips*
ubuntu/linux<4.15.0-60.67
4.15.0-60.67
ubuntu/linux-aws<4.15.0-1047.49
4.15.0-1047.49
ubuntu/linux-azure<5.0.0-1022.23~18.04.1
5.0.0-1022.23~18.04.1
ubuntu/linux-gcp<4.15.0-1042.45
4.15.0-1042.45
ubuntu/linux-gke-4.15<4.15.0-1041.43
4.15.0-1041.43
ubuntu/linux-gke-5.0<5.0.0-1020.20~18.04.1
5.0.0-1020.20~18.04.1
ubuntu/linux-hwe<5.0.0-31.33~18.04.1
5.0.0-31.33~18.04.1
ubuntu/linux-kvm<4.15.0-1043.43
4.15.0-1043.43
ubuntu/linux-oem<4.15.0-1056.65
4.15.0-1056.65
ubuntu/linux-oem-osp1<5.0.0-1024.27
5.0.0-1024.27
ubuntu/linux-oracle<4.15.0-1022.25
4.15.0-1022.25
ubuntu/linux-raspi2<4.15.0-1044.47
4.15.0-1044.47
ubuntu/linux-snapdragon<4.15.0-1062.69
4.15.0-1062.69
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-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 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-1Fixed in 7.2.13-1
  2. Upgrade

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

    Fixed in 4.4.0-1062.66
  3. Upgrade

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

    Fixed in 4.15.0-1059.64~14.04.1
  4. Upgrade

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

    Fixed in 4.4.0-174.204~14.04.1
  5. Upgrade

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

    Fixed in 4.4.0-174.204
  6. Upgrade

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

    Fixed in 4.4.0-1102.113
  7. Upgrade

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

    Fixed in 4.15.0-1047.49~16.04.1
  8. Upgrade

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

    Fixed in 4.15.0-1056.61
  9. Upgrade

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

    Fixed in 4.15.0-1041.43
  10. Upgrade

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

    Fixed in 4.15.0-60.67~16.04.1
  11. Upgrade

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

    Fixed in 4.4.0-1066.73
  12. Upgrade

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

    Fixed in 4.15.0-1022.25~16.04.1
  13. Upgrade

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

    Fixed in 4.4.0-1129.138
  14. Upgrade

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

    Fixed in 4.4.0-1133.141
  15. Upgrade

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

    Fixed in 4.4.0-1029.34
  16. Upgrade

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

    Fixed in 4.15.0-60.67
  17. Upgrade

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

    Fixed in 4.15.0-1047.49
  18. Upgrade

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

    Fixed in 5.0.0-1022.23~18.04.1
  19. Upgrade

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

    Fixed in 4.15.0-1042.45
  20. Upgrade

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

    Fixed in 4.15.0-1041.43
  21. Upgrade

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

    Fixed in 5.0.0-1020.20~18.04.1
  22. Upgrade

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

    Fixed in 5.0.0-31.33~18.04.1
  23. Upgrade

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

    Fixed in 4.15.0-1043.43
  24. Upgrade

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

    Fixed in 4.15.0-1056.65
  25. Upgrade

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

    Fixed in 5.0.0-1024.27
  26. Upgrade

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

    Fixed in 4.15.0-1022.25
  27. Upgrade

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

    Fixed in 4.15.0-1044.47
  28. Upgrade

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

    Fixed in 4.15.0-1062.69
  29. Upgrade

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

    Fixed in 4.15.0-2018.18
  30. Upgrade

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

    Fixed in 4.15.0-2006.7
  31. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 5.1.17Patch 3450121997ce872eb7f1248417225827ea249710

Event History

Aug 19, 2019
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·09:45 PM
Data Sourced
via MITRE·09:45 PM
Description
Data Sourced
via NVD·10:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 7, 2019
Data Sourced
via Red Hat·01:16 AM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2019-15221?

CVE-2019-15221 has been classified as a high-severity vulnerability due to the potential for NULL pointer dereference leading to system crashes.

2

How do I fix CVE-2019-15221?

To fix CVE-2019-15221, you should upgrade your Linux kernel to version 5.1.17 or later.

3

Which systems are affected by CVE-2019-15221?

CVE-2019-15221 affects Linux kernel versions prior to 5.1.17, including various distributions like Ubuntu and Debian.

4

What can an attacker do with CVE-2019-15221?

An attacker could exploit CVE-2019-15221 through a malicious USB device, potentially causing a denial of service by crashing the kernel.

5

Is there a known exploit for CVE-2019-15221?

As of now, there are no publicly disclosed exploits specifically targeting CVE-2019-15221, but the risk remains significant.

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