{"id":"CVE-2018-12904","aliases":["DEBIAN-CVE-2018-12904","EUVD-2018-4857","GHSA-vx6h-cqmq-qj84","MGASA-2018-0296","MGASA-2018-0340","MGASA-2018-0341","SUSE-SU-2018:2474-1","UBUNTU-CVE-2018-12904","USN-3752-1","USN-3752-2","USN-3752-3"],"status":"published","title":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used,...","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","severity":{"version":"3.0","score":4.9,"vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-07","score":0.0114,"percentile":0.66804,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"published":"2018-06-24T22:02:29Z","modified":"2026-10-23T18:03:53Z","exploits":[{"source":"exploitdb","id":"EDB-44944","title":"KVM (Nested Virtualization) - L1 Guest Privilege Escalation","type":"dos","platform":"linux","date":"2018-06-25","verified":true,"url":"https://www.exploit-db.com/exploits/44944"}],"fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["4.16.16-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["4.16.16-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["4.16.16-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","fixed_in":["4.15.0-1022.22~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","fixed_in":["4.15.0-1018.19~16.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","fixed_in":["4.15.0-33.36~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux","fixed_in":["4.15.0-33.36"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws","fixed_in":["4.15.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","fixed_in":["4.15.0-1022.23"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","fixed_in":["4.15.0-1018.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-kvm","fixed_in":["4.15.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","fixed_in":["4.15.0-1017.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-raspi2","fixed_in":["4.15.0-1021.23"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.16.16-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.16.16-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.16.16-1"}]}]},{"source":"osv","ecosystem":"Mageia:6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.50-2.mga6"}]}],"bundled":3},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-userspace-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.50-2.mga6"}]}],"bundled":3},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-vboxadditions","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.12-6.mga6"}]}],"bundled":3},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.12-6.mga6"}]}],"bundled":3},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.13-42.mga6"}]}],"bundled":3},{"source":"osv","ecosystem":"Mageia:6","package":"wireguard-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20180613-1.mga6"}]}],"bundled":3},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-tmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.62-1.mga6"}]}],"bundled":18},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.62-1.mga6"}]}],"bundled":18},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15","package":"kernel-livepatch-SLE15_Update_0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2-4.1"}]}],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1022.22~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","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1018.19~16.04.2"}]}],"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","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-33.36~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","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-33.36"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1020.20"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1022.23"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1018.19"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1020.20"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1017.20"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1021.23"}]}],"versions":["4.13.0-1005.5","4.13.0-1006.6","4.13.0-1008.8","4.15.0-1006.7","4.15.0-1009.10","4.15.0-1010.11","4.15.0-1011.12","4.15.0-1012.13","4.15.0-1013.14","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1020.22"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-33.36"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1020.20"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1018.19"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1020.20"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1021.23"}]}],"versions":["4.13.0-1005.5","4.13.0-1006.6","4.13.0-1008.8","4.15.0-1006.7","4.15.0-1009.10","4.15.0-1010.11","4.15.0-1011.12","4.15.0-1012.13","4.15.0-1013.14","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1020.22"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-33.36~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","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1022.22~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","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1018.19~16.04.2"}]}],"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","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1022.23"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1017.20"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18"],"bundled":18}],"products":[{"vendor":"canonical","product":"ubuntu_linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://usn.ubuntu.com/3752-2/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"https://github.com/torvalds/linux/commit/727ba748e110b4de50d142edca9d6a9b7e6111d8","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix"]},{"url":"https://usn.ubuntu.com/3752-3/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.17.2","tags":["x_refsource_MISC","x_transferred","Release Notes","Vendor Advisory","advisory"]},{"url":"https://bugs.chromium.org/p/project-zero/issues/detail?id=1589","tags":["x_refsource_MISC","x_transferred","Exploit","Third Party Advisory","evidence"]},{"url":"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=727ba748e110b4de50d142edca9d6a9b7e6111d8","tags":["x_refsource_MISC","x_transferred","Patch","Vendor Advisory","fix","report"]},{"url":"https://usn.ubuntu.com/3752-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"https://www.exploit-db.com/exploits/44944/","tags":["exploit","x_refsource_EXPLOIT-DB","x_transferred","Exploit","Third Party Advisory","VDB Entry","evidence"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-12904"},{"url":"https://github.com/advisories/GHSA-vx6h-cqmq-qj84"},{"url":"https://security-tracker.debian.org/tracker/CVE-2018-12904","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2018-0296.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=23193","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.45","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.46","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.47","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.48","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.49","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.50","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2018-0340.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=23418","tags":["report"]},{"url":"https://www.securityweek.com/segmentsmack-flaw-linux-kernel-allows-remote-dos-attacks","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.51","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.52","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.53","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.54","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.55","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.56","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.57","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.58","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.59","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.60","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.61","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.62","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2018-0341.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=23419","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20182474-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1097108","tags":["report"]},{"url":"https://bugzilla.suse.com/1099258","tags":["report"]},{"url":"https://bugzilla.suse.com/1099306","tags":["report"]},{"url":"https://bugzilla.suse.com/1102682","tags":["report"]},{"url":"https://bugzilla.suse.com/1103203","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-18344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-3646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5390","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2018-12904","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3752-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3752-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3752-3","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-12904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-9415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-11412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-11506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-13094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-13405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-13406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1000200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1000204","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2018-12904","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","status":"published","published":"2018-06-27T11:00:00Z","modified":"2024-08-05T08:45:02.357Z","updated_at":"2026-11-02T14:35:06.679212Z"}],"euvd":[{"id":"EUVD-2018-4857","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","status":"published","published":"2018-06-27T11:00:00Z","modified":"2024-08-05T08:45:02Z","updated_at":"2026-11-03T02:39:51.126842Z"}],"ghsa":[{"id":"GHSA-vx6h-cqmq-qj84","title":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used,...","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","status":"published","published":"2022-05-13T01:49:41Z","modified":"2023-02-02T05:01:54Z","cvss":[{"version":"3.0","score":4.9,"vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T14:51:17.99492Z"}],"nvd":[{"id":"CVE-2018-12904","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","status":"published","published":"2018-06-27T11:29:00.237Z","modified":"2026-06-17T01:38:33Z","cvss":[{"version":"3.0","score":4.9,"vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium","assessor":"primary"},{"version":"2.0","score":4.4,"vector":"AV:L/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"updated_at":"2026-11-02T14:04:30.900603Z"}],"osv":[{"id":"CVE-2018-12904","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","status":"published","published":"2018-06-27T11:29:00.237Z","modified":"2026-04-16T06:17:57.062129567Z","cvss":[{"version":"3.0","score":4.9,"vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:44:07.934182Z"},{"id":"DEBIAN-CVE-2018-12904","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","status":"published","published":"2018-06-27T11:29:00.237Z","modified":"2026-10-23T18:03:53.992681538Z","cvss":[{"version":"3.0","score":4.9,"vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:45:30.290351Z"},{"id":"UBUNTU-CVE-2018-12904","description":"In arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested virtualization is used, local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL.","status":"published","published":"2018-06-27T00:00:00Z","modified":"2026-04-22T11:35:59.44753Z","cvss":[{"version":"3.0","score":4.9,"vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:54:17.014176Z"},{"id":"MGASA-2018-0296","title":"Updated kernel packages fix security vulnerabilities","description":"This kernel update is based on the upstream 4.14.50 and fixes at least\nthe following security issues:\n\nIn the function sbusfb_ioctl_helper() in drivers/video/fbdev/sbuslib.c\nin the Linux kernel through 4.15, an integer signedness error allows\narbitrary information leakage for the FBIOPUTCMAP_SPARC and\nFBIOGETCMAP_SPARC commands (CVE-2018-6412).\n\nThe kvm functions that were used in the emulation of fxrstor, fxsave,\nsgdt and sidt were originally meant for task switching, and as such they\ndid not check privilege levels. This allowed guest userspace to guest\nkernel write (CVE-2018-10853).\n\nIn arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested\nvirtualization is used, local attackers could cause L1 KVM guests to\nVMEXIT, potentially allowing privilege escalations and denial of service\nattacks due to lack of checking of CPL (CVE-2018-12904).\n\nWireGuard has been updated to 0.0.20180613.\n\nFor other fixes in this update, see the referenced changelogs.\n","status":"published","published":"2018-06-24T22:02:29Z","modified":"2026-04-16T06:24:25.390253055Z","updated_at":"2026-11-02T15:49:40.793816Z"},{"id":"MGASA-2018-0340","title":"Updated kernel-tmb packages fix security vulnerabilities","description":"This kernel-tmb update is based on the upstream 4.14.62 and fixes at least\nthe following security issues:\n\nkernel KVM before versions kernel 4.16, kernel 4.16-rc7, kernel 4.17-rc1,\nkernel 4.17-rc2 and kernel 4.17-rc3 is vulnerable to a flaw in the way the\nLinux kernel's KVM hypervisor handled exceptions delivered after a stack\nswitch operation via Mov SS or Pop SS instructions. During the stack switch\noperation, the processor did not deliver interrupts and exceptions, rather\nthey are delivered once the first instruction after the stack switch is\nexecuted. An unprivileged KVM guest user could use this flaw to crash the\nguest or, potentially, escalate their privileges in the guest\n(CVE-2018-1087).\n\nLinux kernel vhost since version 4.8 does not properly initialize memory in\nmessages passed between virtual guests and the host operating system in the\nvhost/vhost.c:vhost_new_msg() function. This can allow local privileged\nusers to read some kernel memory contents when reading from the\n/dev/vhost-net device file (CVE-2018-1118).\n\nSecurity researchers from FICORA have identified a remote denial of\nservice attack against the Linux kernel caused by inefficient\nimplementation of TCP segment reassembly, named \"SegmentSmack\".\nA remote attacker could consume a lot of CPU resources in the kernel\nnetworking stack with just a low bandwidth or single host attack by\nusing lots of small TCP segments packets. Usually large botnets are\nneeded for similar effect. The rate needed for this denial of service\nattack to be effective is several magnitudes lower than the usual\npacket processing capability of the machine, as the attack exploits\nworst case behaviour of existing algorithms (CVE-2018-5390).\nIn the function sbusfb_ioctl_helper() in drivers/video/fbdev/sbuslib.c\nin the Linux kernel through 4.15, an integer signedness error allows\narbitrary information leakage for the FBIOPUTCMAP_SPARC and\nFBIOGETCMAP_SPARC commands (CVE-2018-6412).\n\nIn some circumstances, some operating systems or hypervisors may not expect\nor properly handle an Intel architecture hardware debug exception. The error\nappears to be due to developer interpretation of existing documentation for\ncertain Intel architecture interrupt/exception instructions, namely MOV SS\nand POP SS. An authenticated attacker may be able to read sensitive data in\nmemory or control low-level operating system functions (CVE-2018-8897).\n\nLinux kernel is vulnerable to a heap-based buffer overflow in the \nfs/ext4/xattr.c:ext4_xattr_set_entry() function. An attacker could exploit\nthis by operating on a mounted crafted ext4 image (CVE-2018-10840).\n\nThe kvm functions that were used in the emulation of fxrstor, fxsave,\nsgdt and sidt were originally meant for task switching, and as such they\ndid not check privilege levels. This allowed guest userspace to guest\nkernel write (CVE-2018-10853).\n\nA flaw was found in Linux kernel ext4 File System. A use-after-free in\next4_ext_remove_space() when mounting and operating a crafted ext4 image\n(CVE-2018-10876).\n\nLinux kernel ext4 filesystem is vulnerable to an out-of-bound access in the\next4_ext_drop_refs() function when operating on a crafted ext4 filesystem\nimage (CVE-2018-10877).\n\nA flaw was found in Linux kernel ext4 filesystem. A local user can cause a\nuse-after-free in ext4_xattr_set_entry function and so a denial of service\nor possibly unspecified other impact by when renaming a file in a crafted\next4 filesystem image (CVE-2018-10879).\n\nA flaw was found in Linux kernel ext4 filesystem code. A stack-out-of-bounds\nwrite in ext4_update_inline_data() is possible when mounting and writing to\na crafted ext4 image. An attacker could use this to cause  a system crash\nand a denial of service (CVE-2018-10880).\n\nA flaw was found in Linux kernel ext4 filesystem. A local user can cause an\nout-of-bound access in ext4_get_group_info function and so a denial of\nservice and a system crash by mounting and operating on a crafted ext4\nfilesystem image (CVE-2018-10881).\n\nA flaw was found in Linux kernel ext4 File System. An out-of-bound write\nwhen unmounting a crafted ext4 image in fs/jbd2/transaction.c. An attacker\ncould use this to cause a denial of service (system crash) (CVE-2018-10882).\n\nA flaw was found in Linux kernel ext4 File System. An out-of-bound write in\njbd2_journal_dirty_metadata() that kernel cannot handle when mounting and\noperating a crafted ext4 image. An attacker could use this to cause a\ndenial of service (system crash) (CVE-2018-10883).\n\nIn the Linux kernel 4.13 through 4.16.11, ext4_read_inline_data() in\nfs/ext4/inline.c performs a memcpy with an untrusted length value in certain\ncircumstances involving a crafted filesystem that stores the system.data\nextended attribute value in a dedicated inode (CVE-2018-11412).\n\nIn arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested\nvirtualization is used, local attackers could cause L1 KVM guests to\nVMEXIT, potentially allowing privilege escalations and denial of service\nattacks due to lack of checking of CPL (CVE-2018-12904).\n\nThe inode_init_owner function in fs/inode.c in the Linux kernel through\n4.17.4 allows local users to create files with an unintended group\nownership, in a scenario where a directory is SGID to a certain group and\nis writable by a user who is not a member of that group. Here, the\nnon-member can trigger creation of a plain file whose group ownership is\nthat group. The intended behavior was that the non-member can trigger\ncreation of a directory (but not a plain file) whose group ownership is\nthat group. The non-member can escalate privileges by making the plain\nfile executable and SGID (CVE-2018-13405).\n\nAn issue was discovered in the Linux kernel through 4.17.11, as used\nin Xen through 4.11.x. The xen_failsafe_callback entry point in \narch/x86/entry/entry_64.S does not properly maintain RBX, which allows\nlocal users to cause a denial of service (uninitialized memory usage\nand system crash). Within Xen, 64-bit x86 PV Linux guest OS users can\ntrigger a guest OS crash or possibly gain privileges (CVE-2018-14678).\n\nOther changes in this update:\n* WireGuard has been updated to 0.0.20180802\n* enable Mellanox5 support (mga#23263)\n* enable SMARTPQI support (mga#23305)\n* ext4: check for allocation block validity with block group locked,\n  fixes possible data corruption under heavy load\n* Add PCI ID for Cannon Lake PCH-LP and Ice Lake LP AHCI\n\nFor other upstream fixes in this update, see the referenced changelogs.\n","status":"published","published":"2018-08-15T15:45:26Z","modified":"2026-04-16T06:24:55.201319308Z","updated_at":"2026-11-02T15:49:40.793816Z"},{"id":"MGASA-2018-0341","title":"Updated kernel-linus packages fix security vulnerabilities","description":"This kernel-linus update is based on the upstream 4.14.62 and fixes at least\nthe following security issues:\n\nkernel KVM before versions kernel 4.16, kernel 4.16-rc7, kernel 4.17-rc1,\nkernel 4.17-rc2 and kernel 4.17-rc3 is vulnerable to a flaw in the way the\nLinux kernel's KVM hypervisor handled exceptions delivered after a stack\nswitch operation via Mov SS or Pop SS instructions. During the stack switch\noperation, the processor did not deliver interrupts and exceptions, rather\nthey are delivered once the first instruction after the stack switch is\nexecuted. An unprivileged KVM guest user could use this flaw to crash the\nguest or, potentially, escalate their privileges in the guest\n(CVE-2018-1087).\n\nLinux kernel vhost since version 4.8 does not properly initialize memory in\nmessages passed between virtual guests and the host operating system in the\nvhost/vhost.c:vhost_new_msg() function. This can allow local privileged\nusers to read some kernel memory contents when reading from the\n/dev/vhost-net device file (CVE-2018-1118).\n\nSecurity researchers from FICORA have identified a remote denial of\nservice attack against the Linux kernel caused by inefficient\nimplementation of TCP segment reassembly, named \"SegmentSmack\".\nA remote attacker could consume a lot of CPU resources in the kernel\nnetworking stack with just a low bandwidth or single host attack by\nusing lots of small TCP segments packets. Usually large botnets are\nneeded for similar effect. The rate needed for this denial of service\nattack to be effective is several magnitudes lower than the usual\npacket processing capability of the machine, as the attack exploits\nworst case behaviour of existing algorithms (CVE-2018-5390).\nIn the function sbusfb_ioctl_helper() in drivers/video/fbdev/sbuslib.c\nin the Linux kernel through 4.15, an integer signedness error allows\narbitrary information leakage for the FBIOPUTCMAP_SPARC and\nFBIOGETCMAP_SPARC commands (CVE-2018-6412).\n\nIn some circumstances, some operating systems or hypervisors may not expect\nor properly handle an Intel architecture hardware debug exception. The error\nappears to be due to developer interpretation of existing documentation for\ncertain Intel architecture interrupt/exception instructions, namely MOV SS\nand POP SS. An authenticated attacker may be able to read sensitive data in\nmemory or control low-level operating system functions (CVE-2018-8897).\n\nLinux kernel is vulnerable to a heap-based buffer overflow in the \nfs/ext4/xattr.c:ext4_xattr_set_entry() function. An attacker could exploit\nthis by operating on a mounted crafted ext4 image (CVE-2018-10840).\n\nThe kvm functions that were used in the emulation of fxrstor, fxsave,\nsgdt and sidt were originally meant for task switching, and as such they\ndid not check privilege levels. This allowed guest userspace to guest\nkernel write (CVE-2018-10853).\n\nA flaw was found in Linux kernel ext4 File System. A use-after-free in\next4_ext_remove_space() when mounting and operating a crafted ext4 image\n(CVE-2018-10876).\n\nLinux kernel ext4 filesystem is vulnerable to an out-of-bound access in the\next4_ext_drop_refs() function when operating on a crafted ext4 filesystem\nimage (CVE-2018-10877).\n\nA flaw was found in Linux kernel ext4 filesystem. A local user can cause a\nuse-after-free in ext4_xattr_set_entry function and so a denial of service\nor possibly unspecified other impact by when renaming a file in a crafted\next4 filesystem image (CVE-2018-10879).\n\nA flaw was found in Linux kernel ext4 filesystem code. A stack-out-of-bounds\nwrite in ext4_update_inline_data() is possible when mounting and writing to\na crafted ext4 image. An attacker could use this to cause  a system crash\nand a denial of service (CVE-2018-10880).\n\nA flaw was found in Linux kernel ext4 filesystem. A local user can cause an\nout-of-bound access in ext4_get_group_info function and so a denial of\nservice and a system crash by mounting and operating on a crafted ext4\nfilesystem image (CVE-2018-10881).\n\nA flaw was found in Linux kernel ext4 File System. An out-of-bound write\nwhen unmounting a crafted ext4 image in fs/jbd2/transaction.c. An attacker\ncould use this to cause a denial of service (system crash) (CVE-2018-10882).\n\nA flaw was found in Linux kernel ext4 File System. An out-of-bound write in\njbd2_journal_dirty_metadata() that kernel cannot handle when mounting and\noperating a crafted ext4 image. An attacker could use this to cause a\ndenial of service (system crash) (CVE-2018-10883).\n\nIn the Linux kernel 4.13 through 4.16.11, ext4_read_inline_data() in\nfs/ext4/inline.c performs a memcpy with an untrusted length value in certain\ncircumstances involving a crafted filesystem that stores the system.data\nextended attribute value in a dedicated inode (CVE-2018-11412).\n\nIn arch/x86/kvm/vmx.c in the Linux kernel before 4.17.2, when nested\nvirtualization is used, local attackers could cause L1 KVM guests to\nVMEXIT, potentially allowing privilege escalations and denial of service\nattacks due to lack of checking of CPL (CVE-2018-12904).\n\nThe inode_init_owner function in fs/inode.c in the Linux kernel through\n4.17.4 allows local users to create files with an unintended group\nownership, in a scenario where a directory is SGID to a certain group and\nis writable by a user who is not a member of that group. Here, the\nnon-member can trigger creation of a plain file whose group ownership is\nthat group. The intended behavior was that the non-member can trigger\ncreation of a directory (but not a plain file) whose group ownership is\nthat group. The non-member can escalate privileges by making the plain\nfile executable and SGID (CVE-2018-13405).\n\nAn issue was discovered in the Linux kernel through 4.17.11, as used\nin Xen through 4.11.x. The xen_failsafe_callback entry point in \narch/x86/entry/entry_64.S does not properly maintain RBX, which allows\nlocal users to cause a denial of service (uninitialized memory usage\nand system crash). Within Xen, 64-bit x86 PV Linux guest OS users can\ntrigger a guest OS crash or possibly gain privileges (CVE-2018-14678).\n\nOther changes in this update:\n* enable Mellanox5 support (mga#23263)\n* enable SMARTPQI support (mga#23305)\n\nFor other upstream fixes in this update, see the referenced changelogs.\n","status":"published","published":"2018-08-15T15:45:26Z","modified":"2026-04-16T06:24:44.716007479Z","updated_at":"2026-11-02T15:49:40.793816Z"},{"id":"SUSE-SU-2018:2474-1","title":"Security update for the Linux Kernel (Live Patch 0 for SLE 15)","description":"This update for the Linux Kernel 4.12.14-23 fixes several issues.\n\nThe following security issues were fixed:\n\n- CVE-2018-5390: Linux kernel versions 4.9+ can be forced to make very expensive calls to tcp_collapse_ofo_queue() and tcp_prune_ofo_queue() for every incoming packet which can lead to a denial of service (bsc#1102682).\n- CVE-2018-3646: Local attackers in virtualized guest systems could use speculative code patterns on hyperthreaded processors to read data present in the L1 Datacache used by other hyperthreads on the same CPU core, potentially leaking sensitive data, even from other virtual machines or the host system (bsc#1099306).\n- CVE-2017-18344: The timer_create syscall implementation in kernel/time/posix-timers.c didn't properly validate the sigevent-\u003esigev_notify field, which lead to out-of-bounds access in the show_timer function (called when /proc/$PID/timers is read). This allowed userspace applications to read arbitrary kernel memory (on a kernel built with CONFIG_POSIX_TIMERS and CONFIG_CHECKPOINT_RESTORE) (bsc#1103203).\nbefore 4.14.8\n- CVE-2018-12904: In arch/x86/kvm/vmx.c local attackers could cause L1 KVM guests to VMEXIT, potentially allowing privilege escalations and denial of service attacks due to lack of checking of CPL (bsc#1099258).\n- CVE-2018-10853: A flaw was found in kvm. In which certain instructions such as sgdt/sidt call segmented_write_std didn't propagate access correctly. As such, during userspace induced exception, the guest can incorrectly assume that the exception happened in the kernel and panic. (bsc#1097108).\n","status":"published","published":"2018-08-21T15:13:27Z","modified":"2026-02-04T04:03:27.067495Z","updated_at":"2026-11-02T15:53:45.378228Z"},{"id":"USN-3752-1","title":"linux, linux-aws, linux-gcp, linux-kvm, linux-raspi2 vulnerabilities","description":"It was discovered that, when attempting to handle an out-of-memory\nsituation, a null pointer dereference could be triggered in the Linux\nkernel in some circumstances. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2018-1000200)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly validate meta-data information. An attacker could\nuse this to construct a malicious xfs image that, when mounted, could cause\na denial of service (system crash). (CVE-2018-10323)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly validate xattr information. An attacker could use\nthis to construct a malicious xfs image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2018-10840)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly keep meta-data information consistent in some\nsituations. An attacker could use this to construct a malicious ext4 image\nthat, when mounted, could cause a denial of service (system crash).\n(CVE-2018-10881)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly handle corrupted meta data in some situations. An\nattacker could use this to specially craft an ext4 filesystem that caused a\ndenial of service (system crash) when mounted. (CVE-2018-1093)\n\nJann Horn discovered that the Linux kernel's implementation of random seed\ndata reported that it was in a ready state before it had gathered\nsufficient entropy. An attacker could use this to expose sensitive\ninformation. (CVE-2018-1108)\n\nIt was discovered that the procfs filesystem did not properly handle\nprocesses mapping some memory elements onto files. A local attacker could\nuse this to block utilities that examine the procfs filesystem to report\noperating system state, such as ps(1). (CVE-2018-1120)\n\nJann Horn discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly keep xattr information consistent in some\nsituations. An attacker could use this to construct a malicious ext4 image\nthat, when mounted, could cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2018-11412)\n\nPiotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer\noverflow in the CDROM driver implementation of the Linux kernel. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2018-11506)\n\nShankara Pailoor discovered that a race condition existed in the socket\nhandling code in the Linux kernel. A local attacker could use this to cause\na denial of service (system crash). (CVE-2018-12232)\n\nShankara Pailoor discovered that the JFS filesystem implementation in the\nLinux kernel contained a buffer overflow when handling extended attributes.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2018-12233)\n\nFelix Wilhelm discovered that the KVM implementation in the Linux kernel\ndid not properly perform permission checks in some situations when nested\nvirtualization is used. An attacker in a guest VM could possibly use this\nto escape into an outer VM or the host OS. (CVE-2018-12904)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly handle an error condition with a corrupted xfs\nimage. An attacker could use this to construct a malicious xfs image that,\nwhen mounted, could cause a denial of service (system crash).\n(CVE-2018-13094)\n\nIt was discovered that the Linux kernel did not properly handle setgid file\ncreation when performed by a non-member of the group. A local attacker\ncould use this to gain elevated privileges. (CVE-2018-13405)\n\nSilvio Cesare discovered that the generic VESA frame buffer driver in the\nLinux kernel contained an integer overflow. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-13406)\n\nJakub Jirasek discovered that multiple use-after-free errors existed in the\nUSB/IP implementation in the Linux kernel. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-5814)\n\nIt was discovered that a race condition existed in the ARM Advanced\nMicrocontroller Bus Architecture (AMBA) driver in the Linux kernel that\ncould result in a double free. A local attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2018-9415)\n\nIt was discovered that an information leak existed in the generic SCSI\ndriver in the Linux kernel. A local attacker could use this to expose\nsensitive information (kernel memory). (CVE-2018-1000204)\n","status":"published","published":"2018-08-24T00:33:18Z","modified":"2026-06-03T14:04:05.524878482Z","updated_at":"2026-11-02T16:58:14.019824Z"},{"id":"USN-3752-2","title":"linux-hwe vulnerabilities","description":"USN-3752-1 fixed vulnerabilities in the Linux kernel for Ubuntu 18.04\nLTS. This update provides the corresponding updates for the Linux\nHardware Enablement (HWE) kernel from Ubuntu 18.04 LTS for Ubuntu\n16.04 LTS.\n\nIt was discovered that, when attempting to handle an out-of-memory\nsituation, a null pointer dereference could be triggered in the Linux\nkernel in some circumstances. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2018-1000200)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly validate meta-data information. An attacker could\nuse this to construct a malicious xfs image that, when mounted, could cause\na denial of service (system crash). (CVE-2018-10323)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly validate xattr information. An attacker could use\nthis to construct a malicious xfs image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2018-10840)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly keep meta-data information consistent in some\nsituations. An attacker could use this to construct a malicious ext4 image\nthat, when mounted, could cause a denial of service (system crash).\n(CVE-2018-10881)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly handle corrupted meta data in some situations. An\nattacker could use this to specially craft an ext4 filesystem that caused a\ndenial of service (system crash) when mounted. (CVE-2018-1093)\n\nJann Horn discovered that the Linux kernel's implementation of random seed\ndata reported that it was in a ready state before it had gathered\nsufficient entropy. An attacker could use this to expose sensitive\ninformation. (CVE-2018-1108)\n\nIt was discovered that the procfs filesystem did not properly handle\nprocesses mapping some memory elements onto files. A local attacker could\nuse this to block utilities that examine the procfs filesystem to report\noperating system state, such as ps(1). (CVE-2018-1120)\n\nJann Horn discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly keep xattr information consistent in some\nsituations. An attacker could use this to construct a malicious ext4 image\nthat, when mounted, could cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2018-11412)\n\nPiotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer\noverflow in the CDROM driver implementation of the Linux kernel. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2018-11506)\n\nShankara Pailoor discovered that a race condition existed in the socket\nhandling code in the Linux kernel. A local attacker could use this to cause\na denial of service (system crash). (CVE-2018-12232)\n\nShankara Pailoor discovered that the JFS filesystem implementation in the\nLinux kernel contained a buffer overflow when handling extended attributes.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2018-12233)\n\nFelix Wilhelm discovered that the KVM implementation in the Linux kernel\ndid not properly perform permission checks in some situations when nested\nvirtualization is used. An attacker in a guest VM could possibly use this\nto escape into an outer VM or the host OS. (CVE-2018-12904)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly handle an error condition with a corrupted xfs\nimage. An attacker could use this to construct a malicious xfs image that,\nwhen mounted, could cause a denial of service (system crash).\n(CVE-2018-13094)\n\nIt was discovered that the Linux kernel did not properly handle setgid file\ncreation when performed by a non-member of the group. A local attacker\ncould use this to gain elevated privileges. (CVE-2018-13405)\n\nSilvio Cesare discovered that the generic VESA frame buffer driver in the\nLinux kernel contained an integer overflow. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-13406)\n\nJakub Jirasek discovered that multiple use-after-free errors existed in the\nUSB/IP implementation in the Linux kernel. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-5814)\n\nIt was discovered that a race condition existed in the ARM Advanced\nMicrocontroller Bus Architecture (AMBA) driver in the Linux kernel that\ncould result in a double free. A local attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2018-9415)\n\nIt was discovered that an information leak existed in the generic SCSI\ndriver in the Linux kernel. A local attacker could use this to expose\nsensitive information (kernel memory). (CVE-2018-1000204)\n","status":"published","published":"2018-08-24T00:41:04Z","modified":"2026-06-03T14:03:21.205338687Z","updated_at":"2026-11-02T16:58:14.019824Z"},{"id":"USN-3752-3","title":"linux-azure, linux-oem, linux-gcp vulnerabilities","description":"It was discovered that, when attempting to handle an out-of-memory\nsituation, a null pointer dereference could be triggered in the Linux\nkernel in some circumstances. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2018-1000200)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly validate meta-data information. An attacker could\nuse this to construct a malicious xfs image that, when mounted, could cause\na denial of service (system crash). (CVE-2018-10323)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly validate xattr information. An attacker could use\nthis to construct a malicious xfs image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2018-10840)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly keep meta-data information consistent in some\nsituations. An attacker could use this to construct a malicious ext4 image\nthat, when mounted, could cause a denial of service (system crash).\n(CVE-2018-10881)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly handle corrupted meta data in some situations. An\nattacker could use this to specially craft an ext4 filesystem that caused a\ndenial of service (system crash) when mounted. (CVE-2018-1093)\n\nJann Horn discovered that the Linux kernel's implementation of random seed\ndata reported that it was in a ready state before it had gathered\nsufficient entropy. An attacker could use this to expose sensitive\ninformation. (CVE-2018-1108)\n\nIt was discovered that the procfs filesystem did not properly handle\nprocesses mapping some memory elements onto files. A local attacker could\nuse this to block utilities that examine the procfs filesystem to report\noperating system state, such as ps(1). (CVE-2018-1120)\n\nJann Horn discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly keep xattr information consistent in some\nsituations. An attacker could use this to construct a malicious ext4 image\nthat, when mounted, could cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2018-11412)\n\nPiotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer\noverflow in the CDROM driver implementation of the Linux kernel. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2018-11506)\n\nShankara Pailoor discovered that a race condition existed in the socket\nhandling code in the Linux kernel. A local attacker could use this to cause\na denial of service (system crash). (CVE-2018-12232)\n\nShankara Pailoor discovered that the JFS filesystem implementation in the\nLinux kernel contained a buffer overflow when handling extended attributes.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2018-12233)\n\nFelix Wilhelm discovered that the KVM implementation in the Linux kernel\ndid not properly perform permission checks in some situations when nested\nvirtualization is used. An attacker in a guest VM could possibly use this\nto escape into an outer VM or the host OS. (CVE-2018-12904)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly handle an error condition with a corrupted xfs\nimage. An attacker could use this to construct a malicious xfs image that,\nwhen mounted, could cause a denial of service (system crash).\n(CVE-2018-13094)\n\nIt was discovered that the Linux kernel did not properly handle setgid file\ncreation when performed by a non-member of the group. A local attacker\ncould use this to gain elevated privileges. (CVE-2018-13405)\n\nSilvio Cesare discovered that the generic VESA frame buffer driver in the\nLinux kernel contained an integer overflow. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-13406)\n\nJakub Jirasek discovered that multiple use-after-free errors existed in the\nUSB/IP implementation in the Linux kernel. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-5814)\n\nIt was discovered that a race condition existed in the ARM Advanced\nMicrocontroller Bus Architecture (AMBA) driver in the Linux kernel that\ncould result in a double free. A local attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2018-9415)\n\nIt was discovered that an information leak existed in the generic SCSI\ndriver in the Linux kernel. A local attacker could use this to expose\nsensitive information (kernel memory). (CVE-2018-1000204)\n","status":"published","published":"2018-08-28T18:52:56Z","modified":"2026-06-03T14:03:28.841935041Z","updated_at":"2026-11-02T16:58:14.019824Z"}]}}