CVE Vulnerabilities

CVE-2018-14678

Improper Initialization

Published: Jul 28, 2018 | Modified: Nov 21, 2024
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.2 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
7 MODERATE
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

An issue was discovered in the Linux kernel through 4.17.11, as used in Xen through 4.11.x. The xen_failsafe_callback entry point in arch/x86/entry/entry_64.S does not properly maintain RBX, which allows local users to cause a denial of service (uninitialized memory usage and system crash). Within Xen, 64-bit x86 PV Linux guest OS users can trigger a guest OS crash or possibly gain privileges.

Weakness

The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.

Affected Software

NameVendorStart VersionEnd Version
Linux_kernelLinux4.14.21 (including)4.14.61 (excluding)
Linux_kernelLinux4.15.5 (including)4.17.13 (excluding)
LinuxUbuntubionic*
LinuxUbuntuesm-infra/bionic*
LinuxUbuntuupstream*
Linux-awsUbuntubionic*
Linux-awsUbuntuesm-infra/bionic*
Linux-awsUbuntuupstream*
Linux-aws-hweUbuntuesm-infra/xenial*
Linux-aws-hweUbuntuupstream*
Linux-aws-hweUbuntuxenial*
Linux-azureUbuntubionic*
Linux-azureUbuntuesm-infra-legacy/trusty*
Linux-azureUbuntuesm-infra/bionic*
Linux-azureUbuntuesm-infra/xenial*
Linux-azureUbuntutrusty*
Linux-azureUbuntutrusty/esm*
Linux-azureUbuntuupstream*
Linux-azureUbuntuxenial*
Linux-azure-edgeUbuntubionic*
Linux-azure-edgeUbuntuesm-infra/bionic*
Linux-azure-edgeUbuntuupstream*
Linux-azure-edgeUbuntuxenial*
Linux-euclidUbuntuupstream*
Linux-floUbuntutrusty*
Linux-floUbuntuupstream*
Linux-floUbuntuxenial*
Linux-gcpUbuntubionic*
Linux-gcpUbuntuesm-infra/bionic*
Linux-gcpUbuntuesm-infra/xenial*
Linux-gcpUbuntuupstream*
Linux-gcpUbuntuxenial*
Linux-gcp-edgeUbuntuupstream*
Linux-gkeUbuntuupstream*
Linux-gkeUbuntuxenial*
Linux-goldfishUbuntutrusty*
Linux-goldfishUbuntuupstream*
Linux-goldfishUbuntuxenial*
Linux-grouperUbuntutrusty*
Linux-grouperUbuntuupstream*
Linux-hweUbuntuesm-infra/xenial*
Linux-hweUbuntuupstream*
Linux-hweUbuntuxenial*
Linux-hwe-edgeUbuntuesm-infra/xenial*
Linux-hwe-edgeUbuntuupstream*
Linux-hwe-edgeUbuntuxenial*
Linux-kvmUbuntubionic*
Linux-kvmUbuntuesm-infra/bionic*
Linux-kvmUbuntuupstream*
Linux-lts-trustyUbuntuupstream*
Linux-lts-utopicUbuntutrusty*
Linux-lts-utopicUbuntutrusty/esm*
Linux-lts-utopicUbuntuupstream*
Linux-lts-vividUbuntutrusty*
Linux-lts-vividUbuntutrusty/esm*
Linux-lts-vividUbuntuupstream*
Linux-lts-wilyUbuntutrusty*
Linux-lts-wilyUbuntutrusty/esm*
Linux-lts-wilyUbuntuupstream*
Linux-lts-xenialUbuntuupstream*
Linux-maguroUbuntutrusty*
Linux-maguroUbuntuupstream*
Linux-makoUbuntutrusty*
Linux-makoUbuntuupstream*
Linux-makoUbuntuxenial*
Linux-mantaUbuntutrusty*
Linux-mantaUbuntuupstream*
Linux-oemUbuntubionic*
Linux-oemUbuntucosmic*
Linux-oemUbuntuesm-infra/bionic*
Linux-oemUbuntuupstream*
Linux-oracleUbuntubionic*
Linux-oracleUbuntucosmic*
Linux-oracleUbuntuesm-infra/bionic*
Linux-oracleUbuntuesm-infra/xenial*
Linux-oracleUbuntuupstream*
Linux-oracleUbuntuxenial*
Linux-raspi2Ubuntubionic*
Linux-raspi2Ubuntuupstream*
Linux-snapdragonUbuntuupstream*

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable’s type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.

References