CVE Vulnerabilities

CVE-2019-12379

Missing Release of Memory after Effective Lifetime

Published: May 28, 2019 | Modified: Nov 21, 2024
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
4.9 MEDIUM
AV:L/AC:L/Au:N/C:N/I:N/A:C
RedHat/V2
RedHat/V3
4.3 LOW
CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Ubuntu
LOW
root.io logo minimus.io logo echo.ai logo

An issue was discovered in con_insert_unipair in drivers/tty/vt/consolemap.c in the Linux kernel through 5.1.5. There is a memory leak in a certain case of an ENOMEM outcome of kmalloc. NOTE: This id is disputed as not being an issue

Weakness

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Software

NameVendorStart VersionEnd Version
Linux_kernelLinux*5.1.5 (including)
LinuxUbuntubionic*
LinuxUbuntucosmic*
LinuxUbuntudisco*
LinuxUbuntuesm-infra-legacy/trusty*
LinuxUbuntuprecise/esm*
LinuxUbuntutrusty*
LinuxUbuntutrusty/esm*
LinuxUbuntuxenial*
Linux-awsUbuntubionic*
Linux-awsUbuntucosmic*
Linux-awsUbuntudisco*
Linux-awsUbuntuesm-infra-legacy/trusty*
Linux-awsUbuntutrusty*
Linux-awsUbuntutrusty/esm*
Linux-awsUbuntuxenial*
Linux-aws-hweUbuntuxenial*
Linux-azureUbuntubionic*
Linux-azureUbuntucosmic*
Linux-azureUbuntudisco*
Linux-azureUbuntuesm-infra-legacy/trusty*
Linux-azureUbuntutrusty*
Linux-azureUbuntutrusty/esm*
Linux-azureUbuntuxenial*
Linux-azure-edgeUbuntubionic*
Linux-azure-edgeUbuntuxenial*
Linux-euclidUbuntuxenial*
Linux-floUbuntutrusty*
Linux-floUbuntuxenial*
Linux-gcpUbuntubionic*
Linux-gcpUbuntucosmic*
Linux-gcpUbuntudisco*
Linux-gcpUbuntuxenial*
Linux-gcp-edgeUbuntubionic*
Linux-gkeUbuntuxenial*
Linux-gke-4.15Ubuntubionic*
Linux-gke-5.0Ubuntubionic*
Linux-goldfishUbuntutrusty*
Linux-goldfishUbuntuxenial*
Linux-grouperUbuntutrusty*
Linux-hweUbuntubionic*
Linux-hweUbuntuxenial*
Linux-hwe-edgeUbuntubionic*
Linux-hwe-edgeUbuntuxenial*
Linux-kvmUbuntubionic*
Linux-kvmUbuntucosmic*
Linux-kvmUbuntudisco*
Linux-kvmUbuntuxenial*
Linux-lts-trustyUbuntuprecise/esm*
Linux-lts-utopicUbuntutrusty*
Linux-lts-vividUbuntutrusty*
Linux-lts-wilyUbuntutrusty*
Linux-lts-xenialUbuntuesm-infra-legacy/trusty*
Linux-lts-xenialUbuntutrusty*
Linux-lts-xenialUbuntutrusty/esm*
Linux-maguroUbuntutrusty*
Linux-makoUbuntutrusty*
Linux-makoUbuntuxenial*
Linux-mantaUbuntutrusty*
Linux-oemUbuntubionic*
Linux-oemUbuntucosmic*
Linux-oemUbuntudisco*
Linux-oemUbuntuxenial*
Linux-oracleUbuntubionic*
Linux-oracleUbuntucosmic*
Linux-oracleUbuntudisco*
Linux-oracleUbuntuxenial*
Linux-raspi2Ubuntubionic*
Linux-raspi2Ubuntucosmic*
Linux-raspi2Ubuntudisco*
Linux-raspi2Ubuntuxenial*
Linux-snapdragonUbuntubionic*
Linux-snapdragonUbuntudisco*
Linux-snapdragonUbuntuxenial*

Potential Mitigations

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
  • For example, glibc in Linux provides protection against free of invalid pointers.
  • When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
  • To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References