CVE-2019-3882: Medium severity Linux Linux kernel vulnerability

Published Mar 15, 2019
·
Updated

A flaw was found in the Linux kernel vfio interface implementation that permits violation of the user's locked memory limit. If a device is bound to a vfio driver, such as vfio-pci, and the local attacker is administratively granted ownership of the device, it may cause a system memory exhaustion and thus a denial of service (DoS).

References:

https://seclists.org/oss-sec/2019/q2/6

A suggested fix:

https://lore.kernel.org/lkml/155414977872.12780.13728555131525362206.stgit@gimli.home/T/#u

Other sources

A flaw was found in the Linux kernel's vfio interface implementation that permits violation of the user's locked memory limit. If a device is bound to a vfio driver, such as vfio-pci, and the local attacker is administratively granted ownership of the device, it may cause a system memory exhaustion and thus a denial of service (DoS). Versions 3.10, 4.14 and 4.18 are vulnerable.

— Ubuntu

Affected Software

70 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1062.rt56.1022.el7
0:3.10.0-1062.rt56.1022.el7
redhat/kernel<0:3.10.0-1062.el7
0:3.10.0-1062.el7
redhat/kernel-rt<0:4.18.0-147.rt24.93.el8
0:4.18.0-147.rt24.93.el8
redhat/kernel<0:4.18.0-147.el8
0:4.18.0-147.el8
Linux Linux kernel=3.10
Linux Linux kernel=4.14
Linux Linux kernel=4.18
Fedoraproject Fedora
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=18.10
Canonical Ubuntu Linux=19.04
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
NetApp Active Iq Unified Manager For Vmware Vsphere>=9.5
NetApp Hci Management Node
NetApp Snapprotect
NetApp Solidfire
NetApp Storage Replication Adapter For Clustered Data Ontap For Vmware Vsphere>=7.2
NetApp Vasa Provider For Clustered Data Ontap>=7.2
NetApp Virtual Storage Console for VMware vSphere>=7.2
All of the following
NetApp Cn1610 Firmware
NetApp Cn1610
NetApp Cn1610 Firmware
NetApp Cn1610
ubuntu/linux-aws<4.4.0-1044.47
4.4.0-1044.47
ubuntu/linux-azure<4.15.0-1045.49~14.04.1
4.15.0-1045.49~14.04.1
ubuntu/linux-lts-xenial<4.4.0-148.174~14.04.1
4.4.0-148.174~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-148.174
4.4.0-148.174
ubuntu/linux-aws<4.4.0-1083.93
4.4.0-1083.93
ubuntu/linux-aws-hwe<4.15.0-1039.41~16.04.1
4.15.0-1039.41~16.04.1
ubuntu/linux-azure<4.15.0-1045.49
4.15.0-1045.49
ubuntu/linux-gcp<4.15.0-1032.34~16.04.1
4.15.0-1032.34~16.04.1
ubuntu/linux-hwe<4.15.0-50.54~16.04.1
4.15.0-50.54~16.04.1
ubuntu/linux-kvm<4.4.0-1046.52
4.4.0-1046.52
ubuntu/linux-oracle<4.15.0-1013.15~16.04.1
4.15.0-1013.15~16.04.1
ubuntu/linux-raspi2<4.4.0-1109.117
4.4.0-1109.117
ubuntu/linux-snapdragon<4.4.0-1113.118
4.4.0-1113.118
ubuntu/linux-fips<4.4.0-1010.13
4.4.0-1010.13
ubuntu/linux<4.15.0-50.54
4.15.0-50.54
ubuntu/linux-aws<4.15.0-1039.41
4.15.0-1039.41
ubuntu/linux-azure<4.18.0-1018.18~18.04.1
4.18.0-1018.18~18.04.1
ubuntu/linux-gcp<4.15.0-1032.34
4.15.0-1032.34
ubuntu/linux-gcp-edge<4.18.0-1011.12~18.04.1
4.18.0-1011.12~18.04.1
ubuntu/linux-gke-4.15<4.15.0-1032.34
4.15.0-1032.34
ubuntu/linux-hwe<4.18.0-20.21~18.04.1
4.18.0-20.21~18.04.1
ubuntu/linux-kvm<4.15.0-1034.34
4.15.0-1034.34
ubuntu/linux-oem<4.15.0-1038.43
4.15.0-1038.43
ubuntu/linux-oracle<4.15.0-1013.15
4.15.0-1013.15
ubuntu/linux-raspi2<4.15.0-1036.38
4.15.0-1036.38
ubuntu/linux-snapdragon<4.15.0-1053.57
4.15.0-1053.57
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-azure-6.11*
ubuntu/linux-gcp-6.11*
ubuntu/linux-hwe-6.11*
ubuntu/linux-lowlatency-hwe-6.11*
ubuntu/linux-raspi-realtime*
debian/linux
6.1.176-16.1.190-16.12.107-16.12.116-17.2.15-17.3.3-1

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-1062.rt56.1022.el7
  2. Upgrade

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

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

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

    Fixed in 0:4.18.0-147.rt24.93.el8
  4. Upgrade

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

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

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

    Fixed in 4.4.0-1044.47
  6. Upgrade

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

    Fixed in 4.15.0-1045.49~14.04.1
  7. Upgrade

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

    Fixed in 4.4.0-148.174~14.04.1
  8. Upgrade

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

    Fixed in 4.4.0-148.174
  9. Upgrade

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

    Fixed in 4.4.0-1083.93
  10. Upgrade

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

    Fixed in 4.15.0-1039.41~16.04.1
  11. Upgrade

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

    Fixed in 4.15.0-1045.49
  12. Upgrade

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

    Fixed in 4.15.0-1032.34~16.04.1
  13. Upgrade

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

    Fixed in 4.15.0-50.54~16.04.1
  14. Upgrade

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

    Fixed in 4.4.0-1046.52
  15. Upgrade

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

    Fixed in 4.15.0-1013.15~16.04.1
  16. Upgrade

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

    Fixed in 4.4.0-1109.117
  17. Upgrade

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

    Fixed in 4.4.0-1113.118
  18. Upgrade

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

    Fixed in 4.4.0-1010.13
  19. Upgrade

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

    Fixed in 4.15.0-50.54
  20. Upgrade

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

    Fixed in 4.15.0-1039.41
  21. Upgrade

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

    Fixed in 4.18.0-1018.18~18.04.1
  22. Upgrade

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

    Fixed in 4.15.0-1032.34
  23. Upgrade

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

    Fixed in 4.18.0-1011.12~18.04.1
  24. Upgrade

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

    Fixed in 4.15.0-1032.34
  25. Upgrade

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

    Fixed in 4.18.0-20.21~18.04.1
  26. Upgrade

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

    Fixed in 4.15.0-1034.34
  27. Upgrade

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

    Fixed in 4.15.0-1038.43
  28. Upgrade

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

    Fixed in 4.15.0-1013.15
  29. Upgrade

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

    Fixed in 4.15.0-1036.38
  30. Upgrade

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

    Fixed in 4.15.0-1053.57
  31. 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.116-1Fixed in 7.2.15-1Fixed in 7.3.3-1

Event History

Mar 15, 2019
Data Sourced
via Red Hat·09:27 PM
DescriptionSeverityAffected Software
Apr 2, 2019
CVE Published
12:00 AM
Apr 24, 2019
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:29 PM
RemedyDescriptionSeverityWeaknessAffected 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-3882?

CVE-2019-3882 is classified as a high severity vulnerability due to its potential to allow attackers to exhaust system memory.

2

How do I fix CVE-2019-3882?

To fix CVE-2019-3882, users should update to the recommended kernel version specified by their Linux distribution.

3

Who is affected by CVE-2019-3882?

CVE-2019-3882 affects users of the Linux kernel versions 3.10, 4.14, and 4.18, particularly those who use vfio drivers.

4

What type of attack does CVE-2019-3882 enable?

CVE-2019-3882 enables local attackers to bypass user memory limits through administrative privileges on vfio-bound devices.

5

What platforms are impacted by CVE-2019-3882?

CVE-2019-3882 impacts various Linux distributions that incorporate the affected kernel versions, including Red Hat, Debian, 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