{"id":"USN-3718-2","aliases":[],"status":"published","title":"linux-hwe, linux-azure, linux-gcp regression","description":"USN-3695-2 fixed vulnerabilities in the Linux Hardware Enablement\nKernel (HWE) kernel for Ubuntu 16.04 LTS. Unfortunately, the fix\nfor CVE-2018-1108 introduced a regression where insufficient early\nentropy prevented services from starting, leading in some situations\nto a failure to boot, This update addresses the issue.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n Jann Horn discovered that the Linux kernel's implementation of random\n seed data reported that it was in a ready state before it had gathered\n sufficient entropy. An attacker could use this to expose sensitive\n information. (CVE-2018-1108)\n\n Wen Xu discovered that the ext4 file system implementation in the Linux\n kernel did not properly initialize the crc32c checksum driver. A local\n attacker could use this to cause a denial of service (system crash).\n (CVE-2018-1094)\n\n It was discovered that the cdrom driver in the Linux kernel contained an\n incorrect bounds check. A local attacker could use this to expose sensitive\n information (kernel memory). (CVE-2018-10940)\n\n Wen Xu discovered that the ext4 file system implementation in the Linux\n kernel did not properly validate xattr sizes. A local attacker could use\n this to cause a denial of service (system crash). (CVE-2018-1095)\n\n Jann Horn discovered that the 32 bit adjtimex() syscall implementation for\n 64 bit Linux kernels did not properly initialize memory returned to user\n space in some situations. A local attacker could use this to expose\n sensitive information (kernel memory). (CVE-2018-11508)\n\n It was discovered that an information leak vulnerability existed in the\n floppy driver in the Linux kernel. A local attacker could use this to\n expose sensitive information (kernel memory). (CVE-2018-7755)","facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2018-07-21T00:20:11Z","modified":"2026-02-10T04:41:23Z","fixes":[{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","fixed_in":["4.15.0-1018.18~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","fixed_in":["4.15.0-1014.14~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","fixed_in":["4.15.0-29.31~16.04.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1018.18~16.04.1"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1014.14~16.04.1"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-29.31~16.04.1"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1"]}],"references":[{"url":"https://ubuntu.com/security/notices/USN-3718-2","tags":["advisory"]},{"url":"https://launchpad.net/bugs/1779827","tags":["report"]}],"sources":{"osv":[{"id":"USN-3718-2","title":"linux-hwe, linux-azure, linux-gcp regression","description":"USN-3695-2 fixed vulnerabilities in the Linux Hardware Enablement\nKernel (HWE) kernel for Ubuntu 16.04 LTS. Unfortunately, the fix\nfor CVE-2018-1108 introduced a regression where insufficient early\nentropy prevented services from starting, leading in some situations\nto a failure to boot, This update addresses the issue.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n Jann Horn discovered that the Linux kernel's implementation of random\n seed data reported that it was in a ready state before it had gathered\n sufficient entropy. An attacker could use this to expose sensitive\n information. (CVE-2018-1108)\n\n Wen Xu discovered that the ext4 file system implementation in the Linux\n kernel did not properly initialize the crc32c checksum driver. A local\n attacker could use this to cause a denial of service (system crash).\n (CVE-2018-1094)\n\n It was discovered that the cdrom driver in the Linux kernel contained an\n incorrect bounds check. A local attacker could use this to expose sensitive\n information (kernel memory). (CVE-2018-10940)\n\n Wen Xu discovered that the ext4 file system implementation in the Linux\n kernel did not properly validate xattr sizes. A local attacker could use\n this to cause a denial of service (system crash). (CVE-2018-1095)\n\n Jann Horn discovered that the 32 bit adjtimex() syscall implementation for\n 64 bit Linux kernels did not properly initialize memory returned to user\n space in some situations. A local attacker could use this to expose\n sensitive information (kernel memory). (CVE-2018-11508)\n\n It was discovered that an information leak vulnerability existed in the\n floppy driver in the Linux kernel. A local attacker could use this to\n expose sensitive information (kernel memory). (CVE-2018-7755)\n","status":"published","published":"2018-07-21T00:20:11Z","modified":"2026-02-10T04:41:23Z","updated_at":"2026-11-02T16:58:13.496563Z"}]}}