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

Published Mar 7, 2019
·
Updated

It was found that the cgroup limitation of system resources used by Kubernetes can be bypassed. A guest pod can be used to consume a large amount of system memory.

A suggested upstream patch set:

https://lore.kernel.org/netdev/20190401113110.GA20717@hmswarspite.think-freely.org/T/#u

Other sources

The SCTP socket buffer used by a userspace application is not accounted by the cgroups subsystem. An attacker can use this flaw to cause a denial of service attack. Kernel 3.10.x and 4.18.x branches are believed to be vulnerable.

— Ubuntu

Affected Software

60 affected componentsFixes available
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.1<=3.10.108
Linux Linux kernel>=4.18.1<=4.18.20
Debian Debian Linux=8.0
redhat Enterprise Linux=7.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
NetApp Active Iq Unified Manager For Vmware Vsphere>=9.5
NetApp Hci Management Node
NetApp Snapprotect
NetApp Solidfire
All of the following
NetApp Cn1610 Firmware
NetApp Cn1610
NetApp Cn1610 Firmware
NetApp Cn1610
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-1
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-azure-fde-5.15*
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*

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:4.18.0-147.rt24.93.el8
  2. Upgrade

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

    Fixed in 0:4.18.0-147.el8
  3. 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
  4. Upgrade

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

    Fixed in 4.4.0-1044.47
  5. Upgrade

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

    Fixed in 4.15.0-1045.49~14.04.1
  6. Upgrade

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

    Fixed in 4.4.0-148.174~14.04.1
  7. Upgrade

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

    Fixed in 4.4.0-148.174
  8. Upgrade

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

    Fixed in 4.4.0-1083.93
  9. Upgrade

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

    Fixed in 4.15.0-1039.41~16.04.1
  10. Upgrade

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

    Fixed in 4.15.0-1045.49
  11. Upgrade

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

    Fixed in 4.15.0-1032.34~16.04.1
  12. Upgrade

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

    Fixed in 4.15.0-50.54~16.04.1
  13. Upgrade

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

    Fixed in 4.4.0-1046.52
  14. Upgrade

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

    Fixed in 4.15.0-1013.15~16.04.1
  15. Upgrade

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

    Fixed in 4.4.0-1109.117
  16. Upgrade

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

    Fixed in 4.4.0-1113.118
  17. Upgrade

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

    Fixed in 4.4.0-1010.13
  18. Upgrade

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

    Fixed in 4.15.0-50.54
  19. Upgrade

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

    Fixed in 4.15.0-1039.41
  20. Upgrade

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

    Fixed in 4.18.0-1018.18~18.04.1
  21. Upgrade

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

    Fixed in 4.15.0-1032.34
  22. Upgrade

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

    Fixed in 4.18.0-1011.12~18.04.1
  23. Upgrade

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

    Fixed in 4.15.0-1032.34
  24. Upgrade

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

    Fixed in 4.18.0-20.21~18.04.1
  25. Upgrade

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

    Fixed in 4.15.0-1034.34
  26. Upgrade

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

    Fixed in 4.15.0-1038.43
  27. Upgrade

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

    Fixed in 4.15.0-1013.15
  28. Upgrade

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

    Fixed in 4.15.0-1036.38
  29. Upgrade

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

    Fixed in 4.15.0-1053.57
  30. Configuration

    Blacklist the 'sctp' kernel module if SELinux is not in use or a Security Context Constraint allows pods to run as the root user.

    Linux kernel module blacklist = sctp

Event History

Mar 7, 2019
Data Sourced
via Red Hat·11:05 AM
DescriptionSeverityAffected Software
Mar 19, 2019
CVE Published
12:00 AM
Mar 25, 2019
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·06:30 PM
Data Sourced
via MITRE·06:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07: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-3874?

CVE-2019-3874 has been classified as a medium severity vulnerability due to its potential to allow resource consumption beyond intended limits.

2

How do I fix CVE-2019-3874?

To mitigate CVE-2019-3874, update your kernel to version 4.18.0-147.rt24.93.el8 or later.

3

What systems are affected by CVE-2019-3874?

CVE-2019-3874 affects certain versions of the Linux kernel and Kubernetes running on various distributions like Red Hat, Ubuntu, and Debian.

4

How does CVE-2019-3874 exploit Kubernetes?

CVE-2019-3874 allows a guest pod to bypass cgroup restrictions, leading to uncontrolled memory usage in the host system.

5

What are the recommended actions to secure against CVE-2019-3874?

It is recommended to apply the latest kernel patches and updates from your distribution to remediate CVE-2019-3874.

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