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

Published Dec 3, 2019
·
Updated

An OOB memory write issue was found in the way Linux kernel's KVM hypervisor handled 'KVMGETEMULATEDCPUID' ioctl(2) request to get cpuid features emulated by the KVM hypervisor.

A user/process able to access '/dev/kvm' device could use this flaw to crash the system resulting in DoS issue.

Upstream patch: --------------- -> https://git.kernel.org/linus/433f4ba1904100da65a311033f17a9bf586b287e

Reference: -> https://lore.kernel.org/kvm/000000000000ea5ec20598d90e50@google.com/

Other sources

An out-of-bounds memory write issue was found in the Linux Kernel, version 3.13 through 5.4, in the way the Linux kernel's KVM hypervisor handled the 'KVMGETEMULATEDCPUID' ioctl(2) request to get CPUID features emulated by the KVM hypervisor. A user or process able to access the '/dev/kvm' device could use this flaw to crash the system, resulting in a denial of service.

— Ubuntu

An out-of-bounds memory write issue was found in the way the Linux kernel's KVM hypervisor handled the 'KVMGETEMULATEDCPUID' ioctl(2) request to get CPUID features emulated by the KVM hypervisor. A user or process able to access the '/dev/kvm' device could use this flaw to crash the system, resulting in a denial of service.

Affected Software

60 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>=3.13<=5.4
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
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-1061.65
4.4.0-1061.65
ubuntu/linux-azure<4.15.0-1071.76~14.04.1
4.15.0-1071.76~14.04.1
ubuntu/linux-lts-xenial<4.4.0-173.203~14.04.1
4.4.0-173.203~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-173.203
4.4.0-173.203
ubuntu/linux-aws<4.4.0-1101.112
4.4.0-1101.112
ubuntu/linux-aws-hwe<4.15.0-1060.62~16.04.1
4.15.0-1060.62~16.04.1
ubuntu/linux-azure<4.15.0-1071.76
4.15.0-1071.76
ubuntu/linux-gcp<4.15.0-1055.59
4.15.0-1055.59
ubuntu/linux-hwe<4.15.0-88.88~16.04.1
4.15.0-88.88~16.04.1
ubuntu/linux-kvm<4.4.0-1065.72
4.4.0-1065.72
ubuntu/linux-oracle<4.15.0-1033.36~16.04.1
4.15.0-1033.36~16.04.1
ubuntu/linux-raspi2<4.4.0-1128.137
4.4.0-1128.137
ubuntu/linux-snapdragon<4.4.0-1132.140
4.4.0-1132.140
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1028.33
4.4.0-1028.33
ubuntu/linux-fips*
ubuntu/linux<4.15.0-88.88
4.15.0-88.88
ubuntu/linux-aws<4.15.0-1060.62
4.15.0-1060.62
ubuntu/linux-aws-5.0<5.0.0-1024.27~18.04.1
5.0.0-1024.27~18.04.1
ubuntu/linux-azure<5.0.0-1029.31~18.04.1
5.0.0-1029.31~18.04.1
ubuntu/linux-azure-5.3<5.3.0-1013.14~18.04.1
5.3.0-1013.14~18.04.1
ubuntu/linux-gcp<5.0.0-1029.30~18.04.1
5.0.0-1029.30~18.04.1
ubuntu/linux-gcp-5.3<5.3.0-1012.13~18.04.1
5.3.0-1012.13~18.04.1
ubuntu/linux-gke-4.15<4.15.0-1052.55
4.15.0-1052.55
ubuntu/linux-gke-5.0<5.0.0-1029.30~18.04.1
5.0.0-1029.30~18.04.1
ubuntu/linux-gke-5.3<5.3.0-1012.13~18.04.1
5.3.0-1012.13~18.04.1
ubuntu/linux-hwe<5.3.0-40.32~18.04.1
5.3.0-40.32~18.04.1
ubuntu/linux-kvm<4.15.0-1053.53
4.15.0-1053.53
ubuntu/linux-oem<4.15.0-1073.83
4.15.0-1073.83
ubuntu/linux-oem-osp1<5.0.0-1037.42
5.0.0-1037.42
ubuntu/linux-oracle<4.15.0-1033.36
4.15.0-1033.36
ubuntu/linux-oracle-5.0<5.0.0-1010.15~18.04.1
5.0.0-1010.15~18.04.1
ubuntu/linux-raspi2<4.15.0-1055.59
4.15.0-1055.59
ubuntu/linux-raspi2-5.3<5.3.0-1018.20~18.04.1
5.3.0-1018.20~18.04.1
ubuntu/linux-snapdragon<4.15.0-1072.79
4.15.0-1072.79
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-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 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 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
  6. Upgrade

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

    Fixed in 4.4.0-1061.65
  7. Upgrade

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

    Fixed in 4.15.0-1071.76~14.04.1
  8. Upgrade

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

    Fixed in 4.4.0-173.203~14.04.1
  9. Upgrade

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

    Fixed in 4.4.0-173.203
  10. Upgrade

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

    Fixed in 4.4.0-1101.112
  11. Upgrade

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

    Fixed in 4.15.0-1060.62~16.04.1
  12. Upgrade

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

    Fixed in 4.15.0-1071.76
  13. Upgrade

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

    Fixed in 4.15.0-1055.59
  14. Upgrade

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

    Fixed in 4.15.0-88.88~16.04.1
  15. Upgrade

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

    Fixed in 4.4.0-1065.72
  16. Upgrade

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

    Fixed in 4.15.0-1033.36~16.04.1
  17. Upgrade

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

    Fixed in 4.4.0-1128.137
  18. Upgrade

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

    Fixed in 4.4.0-1132.140
  19. Upgrade

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

    Fixed in 4.4.0-1028.33
  20. Upgrade

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

    Fixed in 4.15.0-88.88
  21. Upgrade

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

    Fixed in 4.15.0-1060.62
  22. Upgrade

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

    Fixed in 5.0.0-1024.27~18.04.1
  23. Upgrade

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

    Fixed in 5.0.0-1029.31~18.04.1
  24. Upgrade

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

    Fixed in 5.3.0-1013.14~18.04.1
  25. Upgrade

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

    Fixed in 5.0.0-1029.30~18.04.1
  26. Upgrade

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

    Fixed in 5.3.0-1012.13~18.04.1
  27. Upgrade

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

    Fixed in 4.15.0-1052.55
  28. Upgrade

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

    Fixed in 5.0.0-1029.30~18.04.1
  29. Upgrade

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

    Fixed in 5.3.0-1012.13~18.04.1
  30. Upgrade

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

    Fixed in 5.3.0-40.32~18.04.1
  31. Upgrade

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

    Fixed in 4.15.0-1053.53
  32. Upgrade

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

    Fixed in 4.15.0-1073.83
  33. Upgrade

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

    Fixed in 5.0.0-1037.42
  34. Upgrade

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

    Fixed in 4.15.0-1033.36
  35. Upgrade

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

    Fixed in 5.0.0-1010.15~18.04.1
  36. Upgrade

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

    Fixed in 4.15.0-1055.59
  37. Upgrade

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

    Fixed in 5.3.0-1018.20~18.04.1
  38. Upgrade

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

    Fixed in 4.15.0-1072.79
  39. Upgrade

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

    Fixed in 4.15.0-2018.18
  40. Upgrade

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

    Fixed in 4.15.0-2006.7

Event History

Dec 3, 2019
CVE Published
12:00 AM
Dec 4, 2019
Data Sourced
via Red Hat·10:36 AM
DescriptionSeverityAffected Software
Jan 9, 2020
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·02:41 PM
Data Sourced
via MITRE·02:41 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·03:15 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:15 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-19332?

CVE-2019-19332 has a high severity rating, as it can allow a local user to crash the system, leading to a denial of service.

2

How do I fix CVE-2019-19332?

To fix CVE-2019-19332, update the Linux kernel to a version that addresses this vulnerability.

3

Which systems are affected by CVE-2019-19332?

CVE-2019-19332 affects various versions of the Linux kernel, including Red Hat Enterprise Linux 7 and 8, and specific kernel-rt packages.

4

Can CVE-2019-19332 be exploited remotely?

CVE-2019-19332 cannot be exploited remotely as it requires local access to the '/dev/kvm' device.

5

What impact does CVE-2019-19332 have on system stability?

CVE-2019-19332 can lead to system crashes, significantly impacting system stability and availability.

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