| Revision Date: | 2018-02-21 | Version: | 1 | | Title: | CVE-2018-7273 on Ubuntu 19.04 (disco) - negligible. | | Description: | In the Linux kernel through 4.15.4, the floppy driver reveals the addresses of kernel functions and global variables using printk calls within the function show_floppy in drivers/block/floppy.c. An attacker can read this information from dmesg and use the addresses to find the locations of kernel code and data and bypass kernel security protections such as KASLR.
| | Family: | unix | Class: | vulnerability | | Status: | | Reference(s): | CVE-2018-7273
| | Platform(s): | Ubuntu 19.04
| Product(s): | | | Definition Synopsis | | Ubuntu 19.04 (disco) is installed. AND Package Information
linux package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-meta-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-meta-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-meta-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-meta-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-meta-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-meta-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1005.7').
OR linux-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1005.7').
OR linux-signed package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-signed-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-signed-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-signed-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-signed-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-signed-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-snapdragon package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.10').
|
|