| Revision Date: | 2018-09-10 | Version: | 1 | | Title: | CVE-2018-14625 on Ubuntu 18.04 LTS (bionic) - medium. | | Description: | A flaw was found in the Linux Kernel where an attacker may be able to have an uncontrolled read to kernel-memory from within a vm guest. A race condition between connect() and close() function may allow an attacker using the AF_VSOCK protocol to gather a 4 byte information leak or possibly intercept or corrupt AF_VSOCK messages destined to other clients. It was discovered that a race condition existed in the vsock address family implementation of the Linux kernel that could lead to a use-after-free condition. A local attacker in a guest virtual machine could use this to expose sensitive information (host machine kernel memory).
| | Family: | unix | Class: | vulnerability | | Status: | | Reference(s): | CVE-2018-14625
| | Platform(s): | Ubuntu 18.04 LTS
| Product(s): | | | Definition Synopsis | | Ubuntu 18.04 LTS (bionic) is installed. AND Package Information
linux package in bionic was vulnerable but has been fixed (note: '4.15.0-44.47').
OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
OR linux-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
OR linux-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1037.39').
OR linux-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
OR linux-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1027.28').
OR linux-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
OR linux-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
OR linux-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
OR linux-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
OR linux-hwe package in bionic was vulnerable but has been fixed (note: '4.18.0-14.15~18.04.1').
OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.29').
OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-44.47').
OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
OR linux-meta-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1037.39').
OR linux-meta-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1027.28').
OR linux-meta-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
OR linux-meta-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
OR linux-meta-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
OR linux-meta-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
OR linux-meta-hwe package in bionic was vulnerable but has been fixed (note: '4.18.0-14.15~18.04.1').
OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.29').
OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.38').
OR linux-meta-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1008.10').
OR linux-meta-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1031.33').
OR linux-meta-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
OR linux-meta-snapdragon package in bionic, is related to the CVE in some way and has been fixed (note: '4.4.0-1077.82').
OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.38').
OR linux-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1008.10').
OR linux-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1031.33').
OR linux-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-44.47').
OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1037.39').
OR linux-signed-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1027.28').
OR linux-signed-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
OR linux-signed-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
OR linux-signed-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
OR linux-signed-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
OR linux-signed-hwe package in bionic was vulnerable but has been fixed (note: '4.18.0-14.15~18.04.1').
OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.38').
OR linux-signed-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1008.10').
OR linux-signed-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
OR linux-snapdragon package in bionic, is related to the CVE in some way and has been fixed (note: '4.4.0-1077.82').
|
|