CVE-2019-16233: Null Pointer Dereference

Published Sep 9, 2019
·
Updated

A flaw was found in the Linux kernel. A NULL pointer dereference flaw was found in the QLOGIC drivers for HBA. A call to allocworkqueue return was not validated and can cause a denial of service. The highest threat from this vulnerability is to system availability.

Other sources

A NULL pointer dereference flaw was found in qla2x00probeone in drivers/scsi/qla2xxx/qlaos.c in Qlogic drivers for HBA. Here a call to allocworkqueue return was not validated and this can cause a denial of service at the time of failure. This could allow an attacker to crash the system or leak kernel internal information.

Reference: https://lkml.org/lkml/2019/9/9/487

— Red Hat

drivers/scsi/qla2xxx/qlaos.c in the Linux kernel 5.2.14 does not check the allocworkqueue return value, leading to a NULL pointer dereference.

— Ubuntu

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<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.2.14
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
openSUSE Leap=15.0
openSUSE Leap=15.1
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
debian/linux<=6.1.176-1, <=6.1.190-1, <=6.12.107-1, <=6.12.113-1, <=7.2.12-1
ubuntu/linux-aws<4.4.0-1066.70
4.4.0-1066.70
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-178.208~14.04.1
4.4.0-178.208~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-178.208
4.4.0-178.208
ubuntu/linux-aws<4.4.0-1106.117
4.4.0-1106.117
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-1070.77
4.4.0-1070.77
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-1132.141
4.4.0-1132.141
ubuntu/linux-snapdragon<4.4.0-1136.144
4.4.0-1136.144
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1033.38
4.4.0-1033.38
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-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-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 to a version that resolves this vulnerability.

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

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

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

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

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

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

    Fixed in 4.4.0-1066.70
  6. Upgrade

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

    Fixed in 4.15.0-1066.71~14.04.1
  7. Upgrade

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

    Fixed in 4.4.0-178.208~14.04.1
  8. Upgrade

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

    Fixed in 4.4.0-178.208
  9. Upgrade

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

    Fixed in 4.4.0-1106.117
  10. Upgrade

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

    Fixed in 4.15.0-1057.59~16.04.1
  11. Upgrade

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

    Fixed in 4.15.0-1066.71
  12. Upgrade

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

    Fixed in 4.15.0-1052.56
  13. Upgrade

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

    Fixed in 4.15.0-74.83~16.04.1
  14. Upgrade

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

    Fixed in 4.4.0-1070.77
  15. Upgrade

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

    Fixed in 4.15.0-1031.34~16.04.1
  16. Upgrade

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

    Fixed in 4.4.0-1132.141
  17. Upgrade

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

    Fixed in 4.4.0-1136.144
  18. Upgrade

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

    Fixed in 4.4.0-1033.38
  19. Upgrade

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

    Fixed in 4.15.0-74.84
  20. Upgrade

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

    Fixed in 4.15.0-1057.59
  21. Upgrade

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

    Fixed in 5.0.0-1023.26~18.04.1
  22. Upgrade

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

    Fixed in 5.0.0-1028.30~18.04.1
  23. Upgrade

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

    Fixed in 5.3.0-1008.9~18.04.1
  24. Upgrade

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

    Fixed in 5.0.0-1028.29~18.04.1
  25. Upgrade

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

    Fixed in 5.3.0-1009.10~18.04.1
  26. Upgrade

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

    Fixed in 4.15.0-1050.53
  27. Upgrade

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

    Fixed in 5.0.0-1027.28~18.04.1
  28. Upgrade

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

    Fixed in 5.3.0-26.28~18.04.1
  29. Upgrade

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

    Fixed in 4.15.0-1052.52
  30. Upgrade

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

    Fixed in 4.15.0-1066.76
  31. Upgrade

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

    Fixed in 5.0.0-1033.38
  32. Upgrade

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

    Fixed in 4.15.0-1031.34
  33. Upgrade

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

    Fixed in 5.0.0-1009.14~18.04.1
  34. Upgrade

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

    Fixed in 4.15.0-1053.57
  35. Upgrade

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

    Fixed in 4.15.0-1070.77
  36. Upgrade

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

    Fixed in 4.15.0-2018.18
  37. Upgrade

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

    Fixed in 4.15.0-2006.7

Event History

Sep 9, 2019
CVE Published
12:00 AM
Sep 11, 2019
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·03:30 PM
Data Sourced
via MITRE·03:30 PM
Description
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 10, 2019
Data Sourced
via Red Hat·02:00 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2019-16233?

The severity of CVE-2019-16233 is critical, primarily affecting system availability due to a NULL pointer dereference.

2

How do I fix CVE-2019-16233?

To fix CVE-2019-16233, update to the fixed kernel versions provided by your distribution such as Red Hat Enterprise Linux or Ubuntu.

3

Which versions are affected by CVE-2019-16233?

CVE-2019-16233 affects multiple versions of the Linux kernel, specifically those before the patched versions indicated by your distribution.

4

What type of vulnerability is CVE-2019-16233?

CVE-2019-16233 is a NULL pointer dereference vulnerability found in the QLOGIC drivers.

5

What systems are impacted by CVE-2019-16233?

CVE-2019-16233 impacts systems running vulnerable versions of the Linux kernel across various distributions like Red Hat and Ubuntu.

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