CVE-2019-17075: High severity Linux Linux kernel vulnerability

Published Oct 1, 2019
·
Updated

An issue was discovered in writetptentry in drivers/infiniband/hw/cxgb4/mem.c in the Linux kernel through 5.3.2. The cxgb4 driver is directly calling dmamapsingle (a DMA function) from a stack variable. This could allow an attacker to trigger a Denial of Service, exploitable if this driver is used on an architecture for which this stack/DMA interaction has security relevance.

Affected Software

57 affected componentsFixes available
Linux Linux kernel>=2.6.35<4.4.198
Linux Linux kernel>=4.5.0<4.9.198
Linux Linux kernel>=4.10<4.14.151
Linux Linux kernel>=4.15<4.19.81
Linux Linux kernel>=4.20<5.3.8
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-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-gke*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-raspi-realtime*
ubuntu/linux-vmware*

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-1059.63
  3. Upgrade

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

    Fixed in 4.15.0-1064.69~14.04.1
  4. Upgrade

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

    Fixed in 4.4.0-170.199~14.04.1
  5. Upgrade

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

    Fixed in 4.4.0-170.199
  6. Upgrade

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

    Fixed in 4.4.0-1099.110
  7. Upgrade

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

    Fixed in 4.15.0-1056.58~16.04.1
  8. Upgrade

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

    Fixed in 4.15.0-1064.69
  9. Upgrade

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

    Fixed in 4.15.0-1050.53
  10. Upgrade

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

    Fixed in 4.15.0-72.81~16.04.1
  11. Upgrade

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

    Fixed in 4.4.0-1063.70
  12. Upgrade

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

    Fixed in 4.15.0-1030.33~16.04.1
  13. Upgrade

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

    Fixed in 4.4.0-1126.135
  14. Upgrade

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

    Fixed in 4.4.0-1130.138
  15. Upgrade

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

    Fixed in 4.4.0-1026.31
  16. Upgrade

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

    Fixed in 4.15.0-72.81
  17. Upgrade

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

    Fixed in 4.15.0-1056.58
  18. Upgrade

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

    Fixed in 5.0.0-1023.26~18.04.1
  19. Upgrade

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

    Fixed in 5.0.0-1028.30~18.04.1
  20. Upgrade

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

    Fixed in 5.3.0-1008.9~18.04.1
  21. Upgrade

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

    Fixed in 5.0.0-1028.29~18.04.1
  22. Upgrade

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

    Fixed in 5.3.0-1009.10~18.04.1
  23. Upgrade

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

    Fixed in 4.15.0-1049.52
  24. Upgrade

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

    Fixed in 5.0.0-1027.28~18.04.1
  25. Upgrade

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

    Fixed in 5.3.0-26.28~18.04.1
  26. Upgrade

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

    Fixed in 4.15.0-1051.51
  27. Upgrade

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

    Fixed in 4.15.0-1065.75
  28. Upgrade

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

    Fixed in 5.0.0-1033.38
  29. Upgrade

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

    Fixed in 4.15.0-1030.33
  30. Upgrade

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

    Fixed in 5.0.0-1009.14~18.04.1
  31. Upgrade

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

    Fixed in 4.15.0-1052.56
  32. Upgrade

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

    Fixed in 4.15.0-1069.76
  33. Upgrade

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

    Fixed in 4.15.0-2018.18
  34. Upgrade

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

    Fixed in 4.15.0-2006.7

Event History

Oct 1, 2019
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·08:07 PM
Data Sourced
via MITRE·08:07 PM
Description
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:15 PM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2019-17075?

CVE-2019-17075 has been classified with a high severity due to its potential to trigger a Denial of Service.

2

How do I fix CVE-2019-17075?

To fix CVE-2019-17075, upgrade to a patched version of the Linux kernel, such as 5.10.223-1 or later.

3

What versions of the Linux kernel are affected by CVE-2019-17075?

CVE-2019-17075 affects Linux kernel versions from 2.6.35 up to 5.3.2, specifically including various sub-versions.

4

What can an attacker achieve by exploiting CVE-2019-17075?

An attacker exploiting CVE-2019-17075 could cause a Denial of Service, impacting system availability.

5

Is CVE-2019-17075 related to the cxgb4 driver?

Yes, CVE-2019-17075 specifically involves the cxgb4 driver in the Linux kernel's handling of DMA functions.

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