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

Published Nov 18, 2019
·
Updated

A flaw was found in the Linux kernel. The cryptoreport function mishandles resource cleanup on error. A local attacker able to induce the error conditions could use this flaw to crash the system. The highest threat from this vulnerability is to system availability.

Other sources

A memory leak in the cryptoreport() function in crypto/cryptouserbase.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering cryptoreportalg() failures, aka CID-ffdde5932042.

— Ubuntu

A memory leak in the cryptoreport() function in crypto/cryptouserbase.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering cryptoreportalg() failures.

Upstream Issue:

https://github.com/torvalds/linux/commit/ffdde5932042600c6807d46c1550b28b0db6a3bc

— Red Hat

Affected Software

69 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1160.rt56.1131.el7
0:3.10.0-1160.rt56.1131.el7
redhat/kernel-alt<0:4.14.0-115.26.1.el7a
0:4.14.0-115.26.1.el7a
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.3.11
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.10
Debian Debian Linux=8.0
Fedoraproject Fedora=30
Fedoraproject Fedora=31
openSUSE Leap=15.1
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-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-alt to a version that resolves this vulnerability.

    Fixed in 0:4.14.0-115.26.1.el7a
  3. Upgrade

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

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

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

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

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

    Fixed in 0:4.18.0-240.el8
  6. 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-1
  7. Upgrade

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

    Fixed in 4.4.0-1061.65
  8. Upgrade

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

    Fixed in 4.15.0-1071.76~14.04.1
  9. Upgrade

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

    Fixed in 4.4.0-173.203~14.04.1
  10. Upgrade

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

    Fixed in 4.4.0-173.203
  11. Upgrade

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

    Fixed in 4.4.0-1101.112
  12. Upgrade

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

    Fixed in 4.15.0-1060.62~16.04.1
  13. Upgrade

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

    Fixed in 4.15.0-1071.76
  14. Upgrade

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

    Fixed in 4.15.0-1055.59
  15. Upgrade

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

    Fixed in 4.15.0-88.88~16.04.1
  16. Upgrade

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

    Fixed in 4.4.0-1065.72
  17. Upgrade

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

    Fixed in 4.15.0-1033.36~16.04.1
  18. Upgrade

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

    Fixed in 4.4.0-1128.137
  19. Upgrade

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

    Fixed in 4.4.0-1132.140
  20. Upgrade

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

    Fixed in 4.4.0-1028.33
  21. Upgrade

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

    Fixed in 4.15.0-88.88
  22. Upgrade

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

    Fixed in 4.15.0-1060.62
  23. Upgrade

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

    Fixed in 5.0.0-1024.27~18.04.1
  24. Upgrade

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

    Fixed in 5.0.0-1029.31~18.04.1
  25. Upgrade

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

    Fixed in 5.3.0-1013.14~18.04.1
  26. Upgrade

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

    Fixed in 5.0.0-1029.30~18.04.1
  27. Upgrade

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

    Fixed in 5.3.0-1012.13~18.04.1
  28. Upgrade

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

    Fixed in 4.15.0-1052.55
  29. Upgrade

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

    Fixed in 5.0.0-1029.30~18.04.1
  30. Upgrade

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

    Fixed in 5.3.0-1012.13~18.04.1
  31. Upgrade

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

    Fixed in 5.3.0-40.32~18.04.1
  32. Upgrade

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

    Fixed in 4.15.0-1053.53
  33. Upgrade

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

    Fixed in 4.15.0-1073.83
  34. Upgrade

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

    Fixed in 5.0.0-1037.42
  35. Upgrade

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

    Fixed in 4.15.0-1033.36
  36. Upgrade

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

    Fixed in 5.0.0-1010.15~18.04.1
  37. Upgrade

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

    Fixed in 4.15.0-1055.59
  38. Upgrade

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

    Fixed in 5.3.0-1018.20~18.04.1
  39. Upgrade

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

    Fixed in 4.15.0-1072.79
  40. Upgrade

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

    Fixed in 4.15.0-2018.18
  41. Upgrade

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

    Fixed in 4.15.0-2006.7
  42. Configuration

    Blacklist the crypto_user kernel module to prevent the affected code from being loaded.

    Linux kernel module crypto_user blacklist = crypto_user

Event History

Nov 18, 2019
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·05:24 AM
Data Sourced
via MITRE·05:24 AM
Description
Data Sourced
via OSV·06:15 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 21, 2019
Data Sourced
via Red Hat·11:28 AM
DescriptionSeverityAffected 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-19062?

CVE-2019-19062 has a high severity impacting system availability due to potential crashes induced by attackers.

2

How do I fix CVE-2019-19062?

To fix CVE-2019-19062, update the Linux kernel to versions 0:3.10.0-1160.rt56.1131.el7, 0:4.14.0-115.26.1.el7a, or later patched versions depending on your system.

3

What systems are affected by CVE-2019-19062?

CVE-2019-19062 affects various Linux distributions including specific versions of Red Hat, Debian, and Ubuntu.

4

What type of vulnerability is CVE-2019-19062?

CVE-2019-19062 is a resource cleanup vulnerability in the Linux kernel that can lead to memory leaks and system crashes.

5

Can CVE-2019-19062 be exploited remotely?

CVE-2019-19062 requires local access to the system to exploit, as it involves creating error conditions within the kernel.

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