| Revision Date: | 2018-03-26 | Version: | 1 | | Title: | CVE-2017-18249 on Ubuntu 18.04 LTS (bionic) - low. | | Description: | The add_free_nid function in fs/f2fs/node.c in the Linux kernel before 4.12 does not properly track an allocated nid, which allows local users to cause a denial of service (race condition) or possibly have unspecified other impact via concurrent threads. It was discovered that a race condition existed in the f2fs file system implementation in the Linux kernel. A local attacker could use this to cause a denial of service.
| | Family: | unix | Class: | vulnerability | | Status: | | Reference(s): | CVE-2017-18249
| | 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-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-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 was vulnerable but has been fixed (note: '4.15.0-1053.57').
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-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 was vulnerable but has been fixed (note: '4.15.0-1053.57').
|
|