Revision Date: | 2019-07-27 | Version: | 1 | Title: | CVE-2011-5327 on Ubuntu 18.04 LTS (bionic) - medium. | Description: | In the Linux kernel before 3.1, an off by one in the drivers/target/loopback/tcm_loop.c tcm_loop_make_naa_tpg() function could result in at least memory corruption.
| Family: | unix | Class: | vulnerability | Status: | | Reference(s): | CVE-2011-5327
| Platform(s): | Ubuntu 18.04 LTS
| Product(s): | | Definition Synopsis | Ubuntu 18.04 LTS (bionic) is installed. AND Package Information
linux package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
OR linux-aws package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
OR linux-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.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-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
OR linux-kvm package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-meta package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
OR linux-meta-aws package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
OR linux-meta-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-meta-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.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-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
OR linux-meta-kvm package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-meta-oem package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
OR linux-meta-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-meta-raspi2 package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-1005.5').
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, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
OR linux-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-raspi2 package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-1005.5').
OR linux-signed package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
OR linux-signed-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-signed-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.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-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
OR linux-signed-oem package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
OR linux-signed-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-snapdragon package in bionic, is related to the CVE in some way and has been fixed (note: '4.4.0-1077.82').
|
|