{"id":"CVE-2017-16995","aliases":["DEBIAN-CVE-2017-16995","DSA-4073-1","EUVD-2017-8163","GHSA-45mv-5p9c-6w7c","MGASA-2018-0062","MGASA-2018-0063","MGASA-2018-0064","UBUNTU-CVE-2017-16995","USN-3523-2","USN-3619-1","USN-3619-2","USN-3633-1","openSUSE-SU-2024:10728-1","openSUSE-SU-2024:13704-1"],"status":"published","title":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local...","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.30052,"percentile":0.98222,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-119"],"published":"2017-12-22T10:00:00Z","modified":"2026-10-05T19:18:00Z","exploits":[{"source":"metasploit","id":"exploit/linux/local/bpf_sign_extension_priv_esc","title":"Linux BPF Sign Extension Local Privilege Escalation","type":"exploit","platform":"Linux","date":"2017-11-12","verified":true,"url":"https://www.rapid7.com/db/modules/exploit/linux/local/bpf_sign_extension_priv_esc"},{"source":"exploitdb","id":"EDB-44298","title":"Linux Kernel \u003c 4.4.0-116 (Ubuntu 16.04.4) - Local Privilege Escalation","type":"local","platform":"linux","date":"2018-03-16","url":"https://www.exploit-db.com/exploits/44298"},{"source":"pocgithub","id":"C0dak/CVE-2017-16995","title":"C0dak/CVE-2017-16995","date":"2018-03-19","url":"https://github.com/C0dak/CVE-2017-16995"},{"source":"pocgithub","id":"Al1ex/CVE-2017-16995","title":"Al1ex/CVE-2017-16995","date":"2018-04-26","url":"https://github.com/Al1ex/CVE-2017-16995"},{"source":"exploitdb","id":"EDB-45010","title":"Linux Kernel \u003c 4.13.9 (Ubuntu 16.04 / Fedora 27) - Local Privilege Escalation","type":"local","platform":"linux","date":"2018-07-10","verified":true,"url":"https://www.exploit-db.com/exploits/45010"},{"source":"exploitdb","id":"EDB-45058","title":"Linux - BPF Sign Extension Local Privilege Escalation (Metasploit)","type":"local","platform":"linux","date":"2018-07-19","verified":true,"url":"https://www.exploit-db.com/exploits/45058"},{"source":"pocgithub","id":"gugronnier/CVE-2017-16995","title":"gugronnier/CVE-2017-16995","date":"2018-10-18","url":"https://github.com/gugronnier/CVE-2017-16995"},{"source":"pocgithub","id":"senyuuri/cve-2017-16995","title":"senyuuri/cve-2017-16995","date":"2019-01-22","url":"https://github.com/senyuuri/cve-2017-16995"},{"source":"pocgithub","id":"vnik5287/CVE-2017-16995","title":"vnik5287/CVE-2017-16995","date":"2019-07-23","url":"https://github.com/vnik5287/CVE-2017-16995"},{"source":"pocgithub","id":"littlebin404/CVE-2017-16995","title":"littlebin404/CVE-2017-16995","date":"2019-08-14","url":"https://github.com/littlebin404/CVE-2017-16995"},{"source":"pocgithub","id":"Lumindu/CVE-2017-16995-Linux-Kernel---BPF-Sign-Extension-Local-Privilege-Escalation-","title":"Lumindu/CVE-2017-16995-Linux-Kernel---BPF-Sign-Extension-Local-Privilege-Escalation-","date":"2020-05-12","url":"https://github.com/Lumindu/CVE-2017-16995-Linux-Kernel---BPF-Sign-Extension-Local-Privilege-Escalation-"},{"source":"pocgithub","id":"ph4ntonn/CVE-2017-16995","title":"ph4ntonn/CVE-2017-16995","date":"2021-01-28","url":"https://github.com/ph4ntonn/CVE-2017-16995"},{"source":"pocgithub","id":"ivilpez/cve-2017-16995.c","title":"ivilpez/cve-2017-16995.c","date":"2022-11-12","url":"https://github.com/ivilpez/cve-2017-16995.c"},{"source":"pocgithub","id":"fei9747/CVE-2017-16995","title":"fei9747/CVE-2017-16995","date":"2022-11-29","url":"https://github.com/fei9747/CVE-2017-16995"},{"source":"pocgithub","id":"anldori/CVE-2017-16995","title":"anldori/CVE-2017-16995","date":"2023-01-09","url":"https://github.com/anldori/CVE-2017-16995"},{"source":"pocgithub","id":"mareks1007/cve-2017-16995","title":"mareks1007/cve-2017-16995","date":"2023-12-13","url":"https://github.com/mareks1007/cve-2017-16995"},{"source":"pocgithub","id":"ZhiQiAnSecFork/cve-2017-16995","title":"ZhiQiAnSecFork/cve-2017-16995","date":"2023-12-15","url":"https://github.com/ZhiQiAnSecFork/cve-2017-16995"},{"source":"pocgithub","id":"xxxTectationxxx/CVE-2017-16995","title":"xxxTectationxxx/CVE-2017-16995","date":"2025-08-12","url":"https://github.com/xxxTectationxxx/CVE-2017-16995"},{"source":"pocgithub","id":"WhatsWrongAndWhy/CVE-2017-16995","title":"WhatsWrongAndWhy/CVE-2017-16995","date":"2026-07-21","url":"https://github.com/WhatsWrongAndWhy/CVE-2017-16995"}],"fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["4.14.7-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["4.14.7-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["4.14.7-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"linux-aws","fixed_in":["4.4.0-1016.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"linux-lts-xenial","fixed_in":["4.4.0-119.143~14.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux","fixed_in":["4.4.0-119.143"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","fixed_in":["4.4.0-1054.63"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","fixed_in":["4.13.0-1005.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-euclid","fixed_in":["4.4.0-9026.28"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","fixed_in":["4.13.0-1006.9"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","fixed_in":["4.13.0-32.35~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-kvm","fixed_in":["4.4.0-1020.25"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-oem","fixed_in":["4.13.0-1015.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","fixed_in":["4.4.0-1086.94"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","fixed_in":["4.4.0-1088.93"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:16.04:LTS","package":"linux-fips","fixed_in":["4.4.0-1008.10"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.7-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.7-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.7-1"}]}]},{"source":"osv","ecosystem":"Debian:9","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.65-3+deb9u1"}]}],"versions":["4.9.30-2","4.9.30-2+deb9u1","4.9.30-2+deb9u2","4.9.30-2+deb9u2~bpo8+1","4.9.30-2+deb9u3","4.9.30-2+deb9u4","4.9.30-2+deb9u5","4.9.30-2+deb9u5~bpo8+1","4.9.47-1","4.9.51-1","4.9.51-1~bpo8+1","4.9.65-1","4.9.65-2","4.9.65-3","4.9.65-3+deb9u1~bpo8+1","4.9.65-3~bpo8+1"],"bundled":18},{"source":"osv","ecosystem":"Mageia:6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-userspace-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-vboxadditions","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.2-5.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.2-5.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.13-8.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"wireguard-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20171221-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-tmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":25},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1016.16"}]}],"versions":["4.4.0-1002.2","4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1011.11","4.4.0-1012.12","4.4.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-119.143~14.04.1"}]}],"versions":["4.4.0-13.29~14.04.1","4.4.0-14.30~14.04.2","4.4.0-15.31~14.04.1","4.4.0-18.34~14.04.1","4.4.0-21.37~14.04.1","4.4.0-22.39~14.04.1","4.4.0-22.40~14.04.1","4.4.0-24.43~14.04.1","4.4.0-28.47~14.04.1","4.4.0-31.50~14.04.1","4.4.0-34.53~14.04.1","4.4.0-36.55~14.04.1","4.4.0-38.57~14.04.1","4.4.0-42.62~14.04.1","4.4.0-45.66~14.04.1","4.4.0-47.68~14.04.1","4.4.0-51.72~14.04.1","4.4.0-53.74~14.04.1","4.4.0-57.78~14.04.1","4.4.0-59.80~14.04.1","4.4.0-62.83~14.04.1","4.4.0-63.84~14.04.2","4.4.0-64.85~14.04.1","4.4.0-66.87~14.04.1","4.4.0-67.88~14.04.1","4.4.0-70.91~14.04.1","4.4.0-71.92~14.04.1","4.4.0-72.93~14.04.1","4.4.0-75.96~14.04.1","4.4.0-78.99~14.04.2","4.4.0-79.100~14.04.1","4.4.0-81.104~14.04.1","4.4.0-83.106~14.04.1","4.4.0-87.110~14.04.1","4.4.0-89.112~14.04.1","4.4.0-91.114~14.04.1","4.4.0-92.115~14.04.1","4.4.0-93.116~14.04.1","4.4.0-96.119~14.04.1","4.4.0-97.120~14.04.1","4.4.0-98.121~14.04.1","4.4.0-101.124~14.04.1","4.4.0-103.126~14.04.1","4.4.0-104.127~14.04.1","4.4.0-108.131~14.04.1","4.4.0-109.132~14.04.1","4.4.0-111.134~14.04.1","4.4.0-112.135~14.04.1","4.4.0-116.140~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-119.143"}]}],"versions":["4.2.0-16.19","4.2.0-17.21","4.2.0-19.23","4.3.0-1.10","4.3.0-2.11","4.3.0-5.16","4.3.0-6.17","4.3.0-7.18","4.4.0-2.16","4.4.0-4.19","4.4.0-6.21","4.4.0-7.22","4.4.0-8.23","4.4.0-9.24","4.4.0-10.25","4.4.0-11.26","4.4.0-12.28","4.4.0-13.29","4.4.0-14.30","4.4.0-15.31","4.4.0-16.32","4.4.0-17.33","4.4.0-18.34","4.4.0-21.37","4.4.0-22.39","4.4.0-22.40","4.4.0-24.43","4.4.0-28.47","4.4.0-31.50","4.4.0-34.53","4.4.0-36.55","4.4.0-38.57","4.4.0-42.62","4.4.0-43.63","4.4.0-45.66","4.4.0-47.68","4.4.0-51.72","4.4.0-53.74","4.4.0-57.78","4.4.0-59.80","4.4.0-62.83","4.4.0-63.84","4.4.0-64.85","4.4.0-65.86","4.4.0-66.87","4.4.0-67.88","4.4.0-70.91","4.4.0-71.92","4.4.0-72.93","4.4.0-75.96","4.4.0-77.98","4.4.0-78.99","4.4.0-79.100","4.4.0-81.104","4.4.0-83.106","4.4.0-87.110","4.4.0-89.112","4.4.0-91.114","4.4.0-92.115","4.4.0-93.116","4.4.0-96.119","4.4.0-97.120","4.4.0-98.121","4.4.0-101.124","4.4.0-103.126","4.4.0-104.127","4.4.0-108.131","4.4.0-109.132","4.4.0-112.135","4.4.0-116.140"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1054.63"}]}],"versions":["4.4.0-1001.10","4.4.0-1003.12","4.4.0-1004.13","4.4.0-1007.16","4.4.0-1009.18","4.4.0-1011.20","4.4.0-1012.21","4.4.0-1013.22","4.4.0-1016.25","4.4.0-1017.26","4.4.0-1018.27","4.4.0-1020.29","4.4.0-1022.31","4.4.0-1026.35","4.4.0-1028.37","4.4.0-1030.39","4.4.0-1031.40","4.4.0-1032.41","4.4.0-1035.44","4.4.0-1037.46","4.4.0-1038.47","4.4.0-1039.48","4.4.0-1041.50","4.4.0-1043.52","4.4.0-1044.53","4.4.0-1047.56","4.4.0-1048.57","4.4.0-1049.58","4.4.0-1050.59","4.4.0-1052.61"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-1005.7"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-euclid","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-9026.28"}]}],"versions":["4.4.0-9019.20","4.4.0-9020.21","4.4.0-9021.22","4.4.0-9022.23","4.4.0-9023.24","4.4.0-9025.27"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-1006.9"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-32.35~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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1020.25"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13","4.4.0-1009.14","4.4.0-1010.15","4.4.0-1012.17","4.4.0-1013.18","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-1015.16"}]}],"versions":["4.13.0-1008.9","4.13.0-1010.11","4.13.0-1012.13"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1086.94"}]}],"versions":["4.2.0-1013.19","4.2.0-1014.21","4.3.0-1006.6","4.4.0-1003.4","4.4.0-1004.5","4.4.0-1009.10","4.4.0-1010.12","4.4.0-1010.13","4.4.0-1012.16","4.4.0-1016.22","4.4.0-1017.23","4.4.0-1019.25","4.4.0-1021.27","4.4.0-1023.29","4.4.0-1027.33","4.4.0-1029.36","4.4.0-1034.41","4.4.0-1038.45","4.4.0-1040.47","4.4.0-1042.49","4.4.0-1044.51","4.4.0-1046.53","4.4.0-1048.55","4.4.0-1050.57","4.4.0-1051.58","4.4.0-1052.59","4.4.0-1054.61","4.4.0-1055.62","4.4.0-1057.64","4.4.0-1059.67","4.4.0-1061.69","4.4.0-1065.73","4.4.0-1067.75","4.4.0-1069.77","4.4.0-1070.78","4.4.0-1071.79","4.4.0-1074.82","4.4.0-1075.83","4.4.0-1076.84","4.4.0-1077.85","4.4.0-1079.87","4.4.0-1080.88","4.4.0-1082.90","4.4.0-1085.93"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1088.93"}]}],"versions":["4.4.0-1012.12","4.4.0-1013.14","4.4.0-1013.15","4.4.0-1015.18","4.4.0-1019.22","4.4.0-1020.23","4.4.0-1022.25","4.4.0-1024.27","4.4.0-1026.29","4.4.0-1030.33","4.4.0-1032.36","4.4.0-1035.39","4.4.0-1039.43","4.4.0-1042.46","4.4.0-1044.48","4.4.0-1046.50","4.4.0-1047.51","4.4.0-1048.52","4.4.0-1050.54","4.4.0-1051.55","4.4.0-1053.57","4.4.0-1054.58","4.4.0-1055.59","4.4.0-1057.61","4.4.0-1058.62","4.4.0-1059.63","4.4.0-1061.66","4.4.0-1063.68","4.4.0-1067.72","4.4.0-1069.74","4.4.0-1071.76","4.4.0-1072.77","4.4.0-1073.78","4.4.0-1076.81","4.4.0-1077.82","4.4.0-1078.83","4.4.0-1079.84","4.4.0-1081.86","4.4.0-1082.87","4.4.0-1084.89","4.4.0-1087.92"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1008.10"}]}],"versions":["4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-1005.7"}]}],"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"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-1006.9"}]}],"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"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-26.29~16.04.2"}]}],"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"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-1015.16"}]}],"versions":["4.13.0-1008.9","4.13.0-1010.11","4.13.0-1012.13"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-119.143"}]}],"versions":["4.2.0-16.19","4.2.0-17.21","4.2.0-19.23","4.3.0-1.10","4.3.0-2.11","4.3.0-5.16","4.3.0-6.17","4.3.0-7.18","4.4.0-2.16","4.4.0-4.19","4.4.0-6.21","4.4.0-7.22","4.4.0-8.23","4.4.0-9.24","4.4.0-10.25","4.4.0-11.26","4.4.0-12.28","4.4.0-13.29","4.4.0-14.30","4.4.0-15.31","4.4.0-16.32","4.4.0-17.33","4.4.0-18.34","4.4.0-21.37","4.4.0-22.39","4.4.0-22.40","4.4.0-24.43","4.4.0-28.47","4.4.0-31.50","4.4.0-34.53","4.4.0-36.55","4.4.0-38.57","4.4.0-42.62","4.4.0-43.63","4.4.0-45.66","4.4.0-47.68","4.4.0-51.72","4.4.0-53.74","4.4.0-57.78","4.4.0-59.80","4.4.0-62.83","4.4.0-63.84","4.4.0-64.85","4.4.0-65.86","4.4.0-66.87","4.4.0-67.88","4.4.0-70.91","4.4.0-71.92","4.4.0-72.93","4.4.0-75.96","4.4.0-77.98","4.4.0-78.99","4.4.0-79.100","4.4.0-81.104","4.4.0-83.106","4.4.0-87.110","4.4.0-89.112","4.4.0-91.114","4.4.0-92.115","4.4.0-93.116","4.4.0-96.119","4.4.0-97.120","4.4.0-98.121","4.4.0-101.124","4.4.0-103.126","4.4.0-104.127","4.4.0-108.131","4.4.0-109.132","4.4.0-112.135","4.4.0-116.140"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1054.63"}]}],"versions":["4.4.0-1001.10","4.4.0-1003.12","4.4.0-1004.13","4.4.0-1007.16","4.4.0-1009.18","4.4.0-1011.20","4.4.0-1012.21","4.4.0-1013.22","4.4.0-1016.25","4.4.0-1017.26","4.4.0-1018.27","4.4.0-1020.29","4.4.0-1022.31","4.4.0-1026.35","4.4.0-1028.37","4.4.0-1030.39","4.4.0-1031.40","4.4.0-1032.41","4.4.0-1035.44","4.4.0-1037.46","4.4.0-1038.47","4.4.0-1039.48","4.4.0-1041.50","4.4.0-1043.52","4.4.0-1044.53","4.4.0-1047.56","4.4.0-1048.57","4.4.0-1049.58","4.4.0-1050.59","4.4.0-1052.61"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1020.25"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13","4.4.0-1009.14","4.4.0-1010.15","4.4.0-1012.17","4.4.0-1013.18","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1086.94"}]}],"versions":["4.2.0-1013.19","4.2.0-1014.21","4.3.0-1006.6","4.4.0-1003.4","4.4.0-1004.5","4.4.0-1009.10","4.4.0-1010.12","4.4.0-1010.13","4.4.0-1012.16","4.4.0-1016.22","4.4.0-1017.23","4.4.0-1019.25","4.4.0-1021.27","4.4.0-1023.29","4.4.0-1027.33","4.4.0-1029.36","4.4.0-1034.41","4.4.0-1038.45","4.4.0-1040.47","4.4.0-1042.49","4.4.0-1044.51","4.4.0-1046.53","4.4.0-1048.55","4.4.0-1050.57","4.4.0-1051.58","4.4.0-1052.59","4.4.0-1054.61","4.4.0-1055.62","4.4.0-1057.64","4.4.0-1059.67","4.4.0-1061.69","4.4.0-1065.73","4.4.0-1067.75","4.4.0-1069.77","4.4.0-1070.78","4.4.0-1071.79","4.4.0-1074.82","4.4.0-1075.83","4.4.0-1076.84","4.4.0-1077.85","4.4.0-1079.87","4.4.0-1080.88","4.4.0-1082.90","4.4.0-1085.93"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1088.93"}]}],"versions":["4.4.0-1012.12","4.4.0-1013.14","4.4.0-1013.15","4.4.0-1015.18","4.4.0-1019.22","4.4.0-1020.23","4.4.0-1022.25","4.4.0-1024.27","4.4.0-1026.29","4.4.0-1030.33","4.4.0-1032.36","4.4.0-1035.39","4.4.0-1039.43","4.4.0-1042.46","4.4.0-1044.48","4.4.0-1046.50","4.4.0-1047.51","4.4.0-1048.52","4.4.0-1050.54","4.4.0-1051.55","4.4.0-1053.57","4.4.0-1054.58","4.4.0-1055.59","4.4.0-1057.61","4.4.0-1058.62","4.4.0-1059.63","4.4.0-1061.66","4.4.0-1063.68","4.4.0-1067.72","4.4.0-1069.74","4.4.0-1071.76","4.4.0-1072.77","4.4.0-1073.78","4.4.0-1076.81","4.4.0-1077.82","4.4.0-1078.83","4.4.0-1079.84","4.4.0-1081.86","4.4.0-1082.87","4.4.0-1084.89","4.4.0-1087.92"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1016.16"}]}],"versions":["4.4.0-1002.2","4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1011.11","4.4.0-1012.12","4.4.0-1014.14"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-119.143~14.04.1"}]}],"versions":["4.4.0-13.29~14.04.1","4.4.0-14.30~14.04.2","4.4.0-15.31~14.04.1","4.4.0-18.34~14.04.1","4.4.0-21.37~14.04.1","4.4.0-22.39~14.04.1","4.4.0-22.40~14.04.1","4.4.0-24.43~14.04.1","4.4.0-28.47~14.04.1","4.4.0-31.50~14.04.1","4.4.0-34.53~14.04.1","4.4.0-36.55~14.04.1","4.4.0-38.57~14.04.1","4.4.0-42.62~14.04.1","4.4.0-45.66~14.04.1","4.4.0-47.68~14.04.1","4.4.0-51.72~14.04.1","4.4.0-53.74~14.04.1","4.4.0-57.78~14.04.1","4.4.0-59.80~14.04.1","4.4.0-62.83~14.04.1","4.4.0-63.84~14.04.2","4.4.0-64.85~14.04.1","4.4.0-66.87~14.04.1","4.4.0-67.88~14.04.1","4.4.0-70.91~14.04.1","4.4.0-71.92~14.04.1","4.4.0-72.93~14.04.1","4.4.0-75.96~14.04.1","4.4.0-78.99~14.04.2","4.4.0-79.100~14.04.1","4.4.0-81.104~14.04.1","4.4.0-83.106~14.04.1","4.4.0-87.110~14.04.1","4.4.0-89.112~14.04.1","4.4.0-91.114~14.04.1","4.4.0-92.115~14.04.1","4.4.0-93.116~14.04.1","4.4.0-96.119~14.04.1","4.4.0-97.120~14.04.1","4.4.0-98.121~14.04.1","4.4.0-101.124~14.04.1","4.4.0-103.126~14.04.1","4.4.0-104.127~14.04.1","4.4.0-108.131~14.04.1","4.4.0-109.132~14.04.1","4.4.0-111.134~14.04.1","4.4.0-112.135~14.04.1","4.4.0-116.140~14.04.1"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-euclid","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-9026.28"}]}],"versions":["4.4.0-9019.20","4.4.0-9020.21","4.4.0-9021.22","4.4.0-9022.23","4.4.0-9023.24","4.4.0-9025.27"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.6-1.4"}]}],"bundled":119},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.17-1.1"}]}],"bundled":194}],"products":[{"vendor":"canonical","product":"ubuntu_linux"},{"vendor":"debian","product":"debian_linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://www.exploit-db.com/exploits/45058/","tags":["exploit","x_refsource_EXPLOIT-DB","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://github.com/torvalds/linux/commit/95a762e2c8c942780948091f8f2a4f32fce1ac6f","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory"]},{"url":"https://usn.ubuntu.com/3619-2/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"https://bugs.chromium.org/p/project-zero/issues/detail?id=1454","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory"]},{"url":"https://usn.ubuntu.com/3633-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"http://www.securityfocus.com/bid/102288","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://www.exploit-db.com/exploits/44298/","tags":["exploit","x_refsource_EXPLOIT-DB","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://www.exploit-db.com/exploits/45010/","tags":["exploit","x_refsource_EXPLOIT-DB","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://www.debian.org/security/2017/dsa-4073","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","Third Party Advisory","advisory"]},{"url":"https://usn.ubuntu.com/usn/usn-3523-2/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"http://openwall.com/lists/oss-security/2017/12/21/2","tags":["x_refsource_MISC","x_transferred","Mailing List","Third Party Advisory","advisory","report"]},{"url":"https://usn.ubuntu.com/3619-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=95a762e2c8c942780948091f8f2a4f32fce1ac6f","tags":["x_refsource_MISC","x_transferred","Vendor Advisory","advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=a6132276ab5dcc38b3299082efeb25b948263adb","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16995"},{"url":"https://usn.ubuntu.com/3619-1"},{"url":"https://usn.ubuntu.com/3619-2"},{"url":"https://usn.ubuntu.com/3633-1"},{"url":"https://usn.ubuntu.com/usn/usn-3523-2"},{"url":"https://www.exploit-db.com/exploits/44298"},{"url":"https://www.exploit-db.com/exploits/45010"},{"url":"https://www.exploit-db.com/exploits/45058"},{"url":"https://github.com/advisories/GHSA-45mv-5p9c-6w7c"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-16995","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2018-0062.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=22166","tags":["report"]},{"url":"https://kernelnewbies.org/Linux_4.10","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.11","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.12","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.13","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.14","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.1","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.2","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.3","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.4","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.5","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.6","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.7","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.8","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.9","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.10","tags":["web"]},{"url":"https://www.wireguard.com/","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2018-0063.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=22268","tags":["report"]},{"url":"https://advisories.mageia.org/MGASA-2018-0064.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=22269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16995","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3523-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3523-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3523-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3619-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3619-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3633-1","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-16995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-0861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-1000407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-6927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-7492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-8043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1000026","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2017-1000251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-13053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-8043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-8087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-8822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-17133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-17666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-18808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-18812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-18813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-6974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-7221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-7222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-8564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-8912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-12351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-12352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-14331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-14386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-24586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-24587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-24588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-2732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-23133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-26708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-32606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-33909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-38166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-3695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-43976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-22942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-24958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-26490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-29900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-29901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-29968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-34918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-40982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-41218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-41674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-44032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-44033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-44034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-20569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-20593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-31084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-39192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-39193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-46813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-5345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6610","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2017-16995","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","status":"published","published":"2017-12-22T10:00:00Z","modified":"2024-08-05T20:43:57.863Z","updated_at":"2026-11-02T14:33:21.142987Z"}],"euvd":[{"id":"EUVD-2017-8163","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","status":"published","published":"2017-12-22T10:00:00Z","modified":"2024-08-05T20:43:57Z","updated_at":"2026-11-03T02:23:11.095005Z"}],"ghsa":[{"id":"GHSA-45mv-5p9c-6w7c","title":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local...","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","status":"published","published":"2022-05-13T01:12:14Z","modified":"2025-04-20T03:51:33Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T15:01:57.945283Z"}],"nvd":[{"id":"CVE-2017-16995","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","status":"published","published":"2017-12-27T17:08:17.67Z","modified":"2026-06-17T01:10:14.097Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":7.2,"vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","level":"high","assessor":"primary"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T14:04:11.215487Z"}],"osv":[{"id":"CVE-2017-16995","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","status":"published","published":"2017-12-27T17:08:17.67Z","modified":"2026-04-16T06:18:49.943653543Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:04.853379Z"},{"id":"DEBIAN-CVE-2017-16995","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","status":"published","published":"2017-12-27T17:08:17.67Z","modified":"2026-09-01T20:03:45.287537957Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:29.100767Z"},{"id":"UBUNTU-CVE-2017-16995","description":"The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.","status":"published","published":"2017-12-27T00:00:00Z","modified":"2026-10-05T19:18:00.166781672Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"},{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:14.563448Z"},{"id":"DSA-4073-1","title":"linux - security update","status":"published","published":"2017-12-23T00:00:00Z","modified":"2026-03-09T01:22:10.986473Z","updated_at":"2026-11-02T15:46:16.523846Z"},{"id":"MGASA-2018-0062","title":"kernel update provides 4.14 series and fixes security vulnerabilities","description":"This kernel update provides an upgrade to the 4.14 longterm branch,\ncurrently based on 4.14.10. It also fixes at least the following\nsecurity issues:\n\nAn elevation of privilege vulnerability in the Broadcom wi-fi driver\n(CVE-2017-0786).\n\nUse-after-free vulnerability in the snd_pcm_info function in the ALSA\nsubsystem in the Linux kernel allows attackers to gain privileges via\nunspecified vectors (CVE-2017-0861).\n\nLinux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM)\nsupport is vulnerable to an incorrect debug exception(#DB) error. It\ncould occur while emulating a syscall instruction. A user/process\ninside guest could use this flaw to potentially escalate their\nprivileges inside guest. Linux guests are not affected.(CVE-2017-7518).\n\narch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested\nvirtualisation is used, does not properly traverse guest pagetable\nentries to resolve a guest virtual address, which allows L1 guest OS\nusers to execute arbitrary code on the host OS or cause a denial of\nservice (incorrect index during page walking, and host OS crash), aka\nan \"MMU potential stack buffer overrun\" (CVE-2017-12188).\n\nThe bio_map_user_iov and bio_unmap_user functions in block/bio.c in the\nLinux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O\nvector has small consecutive buffers belonging to the same page. The\nbio_add_pc_page function merges them into one, but the page reference\nis never dropped. This causes a memory leak and possible system lockup\n(exploitable against the host OS by a guest OS user, if a SCSI disk is\npassed through to a virtual machine) due to an out-of-memory condition\n(CVE-2017-12190).\n\nThe assoc_array_insert_into_terminal_node function in lib/assoc_array.c\nin the Linux kernel before 4.13.11 mishandles node splitting, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\npanic) via a crafted application, as demonstrated by the keyring key type,\nand key addition and link creation operations (CVE-2017-12193).\n\nWi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group\nTemporal Key (GTK) during the group key handshake, allowing an attacker\nwithin radio range to replay frames from access points to clients\n(CVE-2017-13080).\n\nThe sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel\nbefore 4.14 does not check whether the intended netns is used in a\npeel-off action, which allows local users to cause a denial of\nservice (use-after-free and system crash) or possibly have unspecified\nother impact via crafted system calls (CVE-2017-15115).\n\nRace condition in the ALSA subsystem in the Linux kernel before 4.13.8\nallows local users to cause a denial of service (use-after-free) or\npossibly have unspecified other impact via crafted /dev/snd/seq ioctl\ncalls, related to sound/core/seq/seq_clientmgr.c and \nsound/core/seq/seq_ports.c (CVE-2017-15265)\n\nThe KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of\nadd_key for a key that already exists but is uninstantiated, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\nsystem crash) or possibly have unspecified other impact via a crafted\nsystem call (CVE-2017-15299).\n\nThe XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux\nkernel before 4.13.11 allows local users to gain privileges or cause a\ndenial of service (use-after-free) via a crafted SO_RCVBUF setsockopt\nsystem call in conjunction with XFRM_MSG_GETPOLICY Netlink messages\n(CVE-2017-16939).\n\nThe walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel\nbefore 4.14.2 mishandles holes in hugetlb ranges, which allows local\nusers to obtain sensitive information from uninitialized kernel memory\nvia crafted use of the mincore() system call (CVE-2017-16994).\n\nThe check_alu_op function in kernel/bpf/verifier.c in the Linux kernel\nthrough 4.14.8 allows local users to cause a denial of service (memory\ncorruption) or possibly have unspecified other impact by leveraging\nincorrect sign extension (CVE-2017-16995).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging register truncation mishandling\n(CVE-2017-16996).\n\nThe KVM implementation in the Linux kernel through 4.14.7 allows attackers\nto obtain potentially sensitive information from kernel memory, aka a\nwrite_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c\nand include/trace/events/kvm.h (CVE-2017-17741).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging mishandling of 32-bit ALU ops\n(CVE-2017-17852).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging incorrect BPF_RSH signed bounds\ncalculations (CVE-2017-17853).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (integer overflow and memory\ncorruption) or possibly have unspecified other impact by leveraging\nunrestricted integer values for pointer arithmetic (CVE-2017-17854).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging improper use of pointers in\nplace of scalars (CVE-2017-17855).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly\nhave unspecified other impact by leveraging the lack of stack-pointer\nalignment enforcement (CVE-2017-17856).\n\nThe check_stack_boundary function in kernel/bpf/verifier.c in the Linux\nkernel through 4.14.8 allows local users to cause a denial of service\n(memory corruption) or possibly have unspecified other impact by\nleveraging mishandling of invalid variable stack read operations\n(CVE-2017-17857).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores\nunreachable code, even though it would still be processed by JIT\ncompilers. This behavior, also considered an improper branch-pruning\nlogic issue, could possibly be used by local users for denial of\nservice (CVE-2017-17862).\n\nkernel/bpf/verifier.c in the Linux kernel 4.9.x through 4.9.71 does not\ncheck the relationship between pointer values and the BPF stack, which\nallows local users to cause a denial of service (integer overflow or\ninvalid memory access) or possibly have unspecified other impact\n(CVE-2017-17863).\n\nkernel/bpf/verifier.c in the Linux kernel before 4.14 mishandles\nstates_equal comparisons between the pointer data type and the\nUNKNOWN_VALUE data type, which allows local users to obtain potentially\nsensitive address information, aka a \"pointer leak\" (CVE-2017-17864).\n\nThe timer_create syscall implementation in kernel/time/posix-timers.c\nin the Linux kernel before 4.14.8 doesn't properly validate the\nsigevent-\u003esigev_notify field, which leads to out-of-bounds access in\nthe show_timer function (called when /proc/$PID/timers is read).\nThis allows userspace applications to read arbitrary kernel memory\n(on a kernel built with CONFIG_POSIX_TIMERS and\nCONFIG_CHECKPOINT_RESTORE)(CVE-2017-18344).\n\nThe Linux Kernel 2.6.32 and later are affected by a denial of service,\nby flooding the diagnostic port 0x80 an exception can be triggered\nleading to a kernel panic (CVE-2017-1000407).\n\nThis update also adds support for WireGuard VPN.\n\nFor other changes in this update, read the referenced changelogs.\n","status":"published","published":"2018-01-06T00:53:31Z","modified":"2026-04-16T06:26:17.325590936Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2018-0063","title":"kernel-tmb update provides 4.14 series and fixes security vulnerabilities","description":"This kernel-tmb update provides an upgrade to the 4.14 longterm branch,\ncurrently based on 4.14.10. It also fixes at least the following\nsecurity issues:\n\nAn elevation of privilege vulnerability in the Broadcom wi-fi driver\n(CVE-2017-0786).\n\nUse-after-free vulnerability in the snd_pcm_info function in the ALSA\nsubsystem in the Linux kernel allows attackers to gain privileges via\nunspecified vectors (CVE-2017-0861).\n\nLinux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM)\nsupport is vulnerable to an incorrect debug exception(#DB) error. It\ncould occur while emulating a syscall instruction. A user/process\ninside guest could use this flaw to potentially escalate their\nprivileges inside guest. Linux guests are not affected.(CVE-2017-7518).\n\narch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested\nvirtualisation is used, does not properly traverse guest pagetable\nentries to resolve a guest virtual address, which allows L1 guest OS\nusers to execute arbitrary code on the host OS or cause a denial of\nservice (incorrect index during page walking, and host OS crash), aka\nan \"MMU potential stack buffer overrun\" (CVE-2017-12188).\n\nThe bio_map_user_iov and bio_unmap_user functions in block/bio.c in the\nLinux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O\nvector has small consecutive buffers belonging to the same page. The\nbio_add_pc_page function merges them into one, but the page reference\nis never dropped. This causes a memory leak and possible system lockup\n(exploitable against the host OS by a guest OS user, if a SCSI disk is\npassed through to a virtual machine) due to an out-of-memory condition\n(CVE-2017-12190).\n\nThe assoc_array_insert_into_terminal_node function in lib/assoc_array.c\nin the Linux kernel before 4.13.11 mishandles node splitting, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\npanic) via a crafted application, as demonstrated by the keyring key type,\nand key addition and link creation operations (CVE-2017-12193).\n\nWi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group\nTemporal Key (GTK) during the group key handshake, allowing an attacker\nwithin radio range to replay frames from access points to clients\n(CVE-2017-13080).\n\nThe sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel\nbefore 4.14 does not check whether the intended netns is used in a\npeel-off action, which allows local users to cause a denial of\nservice (use-after-free and system crash) or possibly have unspecified\nother impact via crafted system calls (CVE-2017-15115).\n\nRace condition in the ALSA subsystem in the Linux kernel before 4.13.8\nallows local users to cause a denial of service (use-after-free) or\npossibly have unspecified other impact via crafted /dev/snd/seq ioctl\ncalls, related to sound/core/seq/seq_clientmgr.c and \nsound/core/seq/seq_ports.c (CVE-2017-15265)\n\nThe KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of\nadd_key for a key that already exists but is uninstantiated, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\nsystem crash) or possibly have unspecified other impact via a crafted\nsystem call (CVE-2017-15299).\n\nThe XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux\nkernel before 4.13.11 allows local users to gain privileges or cause a\ndenial of service (use-after-free) via a crafted SO_RCVBUF setsockopt\nsystem call in conjunction with XFRM_MSG_GETPOLICY Netlink messages\n(CVE-2017-16939).\n\nThe walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel\nbefore 4.14.2 mishandles holes in hugetlb ranges, which allows local\nusers to obtain sensitive information from uninitialized kernel memory\nvia crafted use of the mincore() system call (CVE-2017-16994).\n\nThe check_alu_op function in kernel/bpf/verifier.c in the Linux kernel\nthrough 4.14.8 allows local users to cause a denial of service (memory\ncorruption) or possibly have unspecified other impact by leveraging\nincorrect sign extension (CVE-2017-16995).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging register truncation mishandling\n(CVE-2017-16996).\n\nThe KVM implementation in the Linux kernel through 4.14.7 allows attackers\nto obtain potentially sensitive information from kernel memory, aka a\nwrite_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c\nand include/trace/events/kvm.h (CVE-2017-17741).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging mishandling of 32-bit ALU ops\n(CVE-2017-17852).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging incorrect BPF_RSH signed bounds\ncalculations (CVE-2017-17853).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (integer overflow and memory\ncorruption) or possibly have unspecified other impact by leveraging\nunrestricted integer values for pointer arithmetic (CVE-2017-17854).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging improper use of pointers in\nplace of scalars (CVE-2017-17855).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly\nhave unspecified other impact by leveraging the lack of stack-pointer\nalignment enforcement (CVE-2017-17856).\n\nThe check_stack_boundary function in kernel/bpf/verifier.c in the Linux\nkernel through 4.14.8 allows local users to cause a denial of service\n(memory corruption) or possibly have unspecified other impact by\nleveraging mishandling of invalid variable stack read operations\n(CVE-2017-17857).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores\nunreachable code, even though it would still be processed by JIT\ncompilers. This behavior, also considered an improper branch-pruning\nlogic issue, could possibly be used by local users for denial of\nservice (CVE-2017-17862).\n\nkernel/bpf/verifier.c in the Linux kernel 4.9.x through 4.9.71 does not\ncheck the relationship between pointer values and the BPF stack, which\nallows local users to cause a denial of service (integer overflow or\ninvalid memory access) or possibly have unspecified other impact\n(CVE-2017-17863).\n\nkernel/bpf/verifier.c in the Linux kernel before 4.14 mishandles\nstates_equal comparisons between the pointer data type and the\nUNKNOWN_VALUE data type, which allows local users to obtain potentially\nsensitive address information, aka a \"pointer leak\" (CVE-2017-17864).\n\nThe timer_create syscall implementation in kernel/time/posix-timers.c\nin the Linux kernel before 4.14.8 doesn't properly validate the\nsigevent-\u003esigev_notify field, which leads to out-of-bounds access in\nthe show_timer function (called when /proc/$PID/timers is read).\nThis allows userspace applications to read arbitrary kernel memory\n(on a kernel built with CONFIG_POSIX_TIMERS and\nCONFIG_CHECKPOINT_RESTORE)(CVE-2017-18344).\n\nThe Linux Kernel 2.6.32 and later are affected by a denial of service,\nby flooding the diagnostic port 0x80 an exception can be triggered\nleading to a kernel panic (CVE-2017-1000407).\n\nThis update also adds support for WireGuard VPN.\n\nFor other changes in this update, read the referenced changelogs.\n","status":"published","published":"2018-01-06T00:53:31Z","modified":"2026-04-16T06:22:43.462881638Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2018-0064","title":"kernel-linus update provides 4.14 series and fixes security vulnerabilities","description":"This kernel-linus update provides an upgrade to the 4.14 longterm\nbranch, currently based on 4.14.10. It also fixes at least the\nfollowing security issues:\n\nAn elevation of privilege vulnerability in the Broadcom wi-fi driver\n(CVE-2017-0786).\n\nUse-after-free vulnerability in the snd_pcm_info function in the ALSA\nsubsystem in the Linux kernel allows attackers to gain privileges via\nunspecified vectors (CVE-2017-0861).\n\nLinux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM)\nsupport is vulnerable to an incorrect debug exception(#DB) error. It\ncould occur while emulating a syscall instruction. A user/process\ninside guest could use this flaw to potentially escalate their\nprivileges inside guest. Linux guests are not affected.(CVE-2017-7518).\n\narch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested\nvirtualisation is used, does not properly traverse guest pagetable\nentries to resolve a guest virtual address, which allows L1 guest OS\nusers to execute arbitrary code on the host OS or cause a denial of\nservice (incorrect index during page walking, and host OS crash), aka\nan \"MMU potential stack buffer overrun\" (CVE-2017-12188).\n\nThe bio_map_user_iov and bio_unmap_user functions in block/bio.c in the\nLinux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O\nvector has small consecutive buffers belonging to the same page. The\nbio_add_pc_page function merges them into one, but the page reference\nis never dropped. This causes a memory leak and possible system lockup\n(exploitable against the host OS by a guest OS user, if a SCSI disk is\npassed through to a virtual machine) due to an out-of-memory condition\n(CVE-2017-12190).\n\nThe assoc_array_insert_into_terminal_node function in lib/assoc_array.c\nin the Linux kernel before 4.13.11 mishandles node splitting, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\npanic) via a crafted application, as demonstrated by the keyring key type,\nand key addition and link creation operations (CVE-2017-12193).\n\nWi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group\nTemporal Key (GTK) during the group key handshake, allowing an attacker\nwithin radio range to replay frames from access points to clients\n(CVE-2017-13080).\n\nThe sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel\nbefore 4.14 does not check whether the intended netns is used in a\npeel-off action, which allows local users to cause a denial of\nservice (use-after-free and system crash) or possibly have unspecified\nother impact via crafted system calls (CVE-2017-15115).\n\nRace condition in the ALSA subsystem in the Linux kernel before 4.13.8\nallows local users to cause a denial of service (use-after-free) or\npossibly have unspecified other impact via crafted /dev/snd/seq ioctl\ncalls, related to sound/core/seq/seq_clientmgr.c and \nsound/core/seq/seq_ports.c (CVE-2017-15265)\n\nThe KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of\nadd_key for a key that already exists but is uninstantiated, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\nsystem crash) or possibly have unspecified other impact via a crafted\nsystem call (CVE-2017-15299).\n\nThe XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux\nkernel before 4.13.11 allows local users to gain privileges or cause a\ndenial of service (use-after-free) via a crafted SO_RCVBUF setsockopt\nsystem call in conjunction with XFRM_MSG_GETPOLICY Netlink messages\n(CVE-2017-16939).\n\nThe walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel\nbefore 4.14.2 mishandles holes in hugetlb ranges, which allows local\nusers to obtain sensitive information from uninitialized kernel memory\nvia crafted use of the mincore() system call (CVE-2017-16994).\n\nThe check_alu_op function in kernel/bpf/verifier.c in the Linux kernel\nthrough 4.14.8 allows local users to cause a denial of service (memory\ncorruption) or possibly have unspecified other impact by leveraging\nincorrect sign extension (CVE-2017-16995).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging register truncation mishandling\n(CVE-2017-16996).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging mishandling of 32-bit ALU ops\n(CVE-2017-17852).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging incorrect BPF_RSH signed bounds\ncalculations (CVE-2017-17853).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (integer overflow and memory\ncorruption) or possibly have unspecified other impact by leveraging\nunrestricted integer values for pointer arithmetic (CVE-2017-17854).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging improper use of pointers in\nplace of scalars (CVE-2017-17855).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly\nhave unspecified other impact by leveraging the lack of stack-pointer\nalignment enforcement (CVE-2017-17856).\n\nThe check_stack_boundary function in kernel/bpf/verifier.c in the Linux\nkernel through 4.14.8 allows local users to cause a denial of service\n(memory corruption) or possibly have unspecified other impact by\nleveraging mishandling of invalid variable stack read operations\n(CVE-2017-17857).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores\nunreachable code, even though it would still be processed by JIT\ncompilers. This behavior, also considered an improper branch-pruning\nlogic issue, could possibly be used by local users for denial of\nservice (CVE-2017-17862).\n\nkernel/bpf/verifier.c in the Linux kernel 4.9.x through 4.9.71 does not\ncheck the relationship between pointer values and the BPF stack, which\nallows local users to cause a denial of service (integer overflow or\ninvalid memory access) or possibly have unspecified other impact\n(CVE-2017-17863).\n\nkernel/bpf/verifier.c in the Linux kernel before 4.14 mishandles\nstates_equal comparisons between the pointer data type and the\nUNKNOWN_VALUE data type, which allows local users to obtain potentially\nsensitive address information, aka a \"pointer leak\" (CVE-2017-17864).\n\nThe timer_create syscall implementation in kernel/time/posix-timers.c\nin the Linux kernel before 4.14.8 doesn't properly validate the\nsigevent-\u003esigev_notify field, which leads to out-of-bounds access in\nthe show_timer function (called when /proc/$PID/timers is read).\nThis allows userspace applications to read arbitrary kernel memory\n(on a kernel built with CONFIG_POSIX_TIMERS and\nCONFIG_CHECKPOINT_RESTORE)(CVE-2017-18344).\n\nThe Linux Kernel 2.6.32 and later are affected by a denial of service,\nby flooding the diagnostic port 0x80 an exception can be triggered\nleading to a kernel panic (CVE-2017-1000407).\n\nFor other changes in this update, read the referenced changelogs.\n","status":"published","published":"2018-01-06T00:53:31Z","modified":"2026-04-16T06:22:49.505651352Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"openSUSE-SU-2024:10728-1","title":"kernel-devel-5.14.6-1.4 on GA media","description":"These are all security issues fixed in the kernel-devel-5.14.6-1.4 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:31:50.908235Z","updated_at":"2026-11-02T16:58:34.487567Z"},{"id":"openSUSE-SU-2024:13704-1","title":"kernel-devel-longterm-6.6.17-1.1 on GA media","description":"These are all security issues fixed in the kernel-devel-longterm-6.6.17-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:07:48.417979Z","updated_at":"2026-11-02T16:58:36.327643Z"},{"id":"USN-3523-2","title":"linux-hwe, linux-azure, linux-gcp, linux-oem vulnerabilities","description":"USN-3523-1 fixed vulnerabilities in the Linux kernel for Ubuntu 17.10.\nThis update provides the corresponding updates for the Linux\nHardware Enablement (HWE) kernel from Ubuntu 17.10 for Ubuntu\n16.04 LTS.\n\nJann Horn discovered that microprocessors utilizing speculative execution\nand indirect branch prediction may allow unauthorized memory reads via\nsidechannel attacks. This flaw is known as Meltdown. A local attacker could\nuse this to expose sensitive information, including kernel memory.\n(CVE-2017-5754)\n\nJann Horn discovered that the Berkeley Packet Filter (BPF) implementation\nin the Linux kernel did not properly check the relationship between pointer\nvalues and the BPF stack. A local attacker could use this to cause a denial\nof service (system crash) or possibly execute arbitrary code.\n(CVE-2017-17863)\n\nJann Horn discovered that the Berkeley Packet Filter (BPF) implementation\nin the Linux kernel improperly performed sign extension in some situations.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2017-16995)\n\nAlexei Starovoitov discovered that the Berkeley Packet Filter (BPF)\nimplementation in the Linux kernel contained a branch-pruning logic issue\naround unreachable code. A local attacker could use this to cause a denial\nof service. (CVE-2017-17862)\n\nJann Horn discovered that the Berkeley Packet Filter (BPF) implementation\nin the Linux kernel mishandled pointer data values in some situations. A\nlocal attacker could use this to to expose sensitive information (kernel\nmemory). (CVE-2017-17864)\n","status":"published","published":"2018-01-10T13:19:19Z","modified":"2026-05-29T18:00:27.976734737Z","updated_at":"2026-11-02T16:58:13.496563Z"},{"id":"USN-3619-1","title":"linux, linux-aws, linux-kvm, linux-raspi2, linux-snapdragon vulnerabilities","description":"Jann Horn discovered that the Berkeley Packet Filter (BPF) implementation\nin the Linux kernel improperly performed sign extension in some situations.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2017-16995)\n\nIt was discovered that a race condition leading to a use-after-free\nvulnerability existed in the ALSA PCM subsystem of the Linux kernel. A\nlocal attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2017-0861)\n\nIt was discovered that the KVM implementation in the Linux kernel allowed\npassthrough of the diagnostic I/O port 0x80. An attacker in a guest VM\ncould use this to cause a denial of service (system crash) in the host OS.\n(CVE-2017-1000407)\n\nIt was discovered that an information disclosure vulnerability existed in\nthe ACPI implementation of the Linux kernel. A local attacker could use\nthis to expose sensitive information (kernel memory addresses).\n(CVE-2017-11472)\n\nIt was discovered that a use-after-free vulnerability existed in the\nnetwork namespaces implementation in the Linux kernel. A local attacker\ncould use this to cause a denial of service (system crash) or possibly\nexecute arbitrary code. (CVE-2017-15129)\n\nIt was discovered that the Advanced Linux Sound Architecture (ALSA)\nsubsystem in the Linux kernel contained a use-after-free when handling\ndevice removal. A physically proximate attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2017-16528)\n\nAndrey Konovalov discovered that the usbtest device driver in the Linux\nkernel did not properly validate endpoint metadata. A physically proximate\nattacker could use this to cause a denial of service (system crash).\n(CVE-2017-16532)\n\nAndrey Konovalov discovered that the Conexant cx231xx USB video capture\ndriver in the Linux kernel did not properly validate interface descriptors.\nA physically proximate attacker could use this to cause a denial of service\n(system crash). (CVE-2017-16536)\n\nAndrey Konovalov discovered that the SoundGraph iMON USB driver in the\nLinux kernel did not properly validate device metadata. A physically\nproximate attacker could use this to cause a denial of service (system\ncrash). (CVE-2017-16537)\n\nAndrey Konovalov discovered that the IMS Passenger Control Unit USB driver\nin the Linux kernel did not properly validate device descriptors. A\nphysically proximate attacker could use this to cause a denial of service\n(system crash). (CVE-2017-16645)\n\nAndrey Konovalov discovered that the DiBcom DiB0700 USB DVB driver in the\nLinux kernel did not properly handle detach events. A physically proximate\nattacker could use this to cause a denial of service (system crash).\n(CVE-2017-16646)\n\nAndrey Konovalov discovered that the CDC USB Ethernet driver did not\nproperly validate device descriptors. A physically proximate attacker could\nuse this to cause a denial of service (system crash). (CVE-2017-16649)\n\nAndrey Konovalov discovered that the QMI WWAN USB driver did not properly\nvalidate device descriptors. A physically proximate attacker could use this\nto cause a denial of service (system crash). (CVE-2017-16650)\n\nIt was discovered that the USB Virtual Host Controller Interface (VHCI)\ndriver in the Linux kernel contained an information disclosure vulnerability.\nA physically proximate attacker could use this to expose sensitive\ninformation (kernel memory). (CVE-2017-16911)\n\nIt was discovered that the USB over IP implementation in the Linux kernel\ndid not validate endpoint numbers. A remote attacker could use this to\ncause a denial of service (system crash). (CVE-2017-16912)\n\nIt was discovered that the USB over IP implementation in the Linux kernel\ndid not properly validate CMD_SUBMIT packets. A remote attacker could use\nthis to cause a denial of service (excessive memory consumption).\n(CVE-2017-16913)\n\nIt was discovered that the USB over IP implementation in the Linux kernel\ncontained a NULL pointer dereference error. A remote attacker could use\nthis to cause a denial of service (system crash). (CVE-2017-16914)\n\nIt was discovered that the HugeTLB component of the Linux kernel did not\nproperly handle holes in hugetlb ranges. A local attacker could use this to\nexpose sensitive information (kernel memory). (CVE-2017-16994)\n\nIt was discovered that the netfilter component of the Linux did not\nproperly restrict access to the connection tracking helpers list. A local\nattacker could use this to bypass intended access restrictions.\n(CVE-2017-17448)\n\nIt was discovered that the netlink subsystem in the Linux kernel did not\nproperly restrict observations of netlink messages to the appropriate net\nnamespace. A local attacker could use this to expose sensitive information\n(kernel netlink traffic). (CVE-2017-17449)\n\nIt was discovered that the netfilter passive OS fingerprinting (xt_osf)\nmodule did not properly perform access control checks. A local attacker\ncould improperly modify the system-wide OS fingerprint list.\n(CVE-2017-17450)\n\nIt was discovered that the core USB subsystem in the Linux kernel did not\nvalidate the number of configurations and interfaces in a device. A\nphysically proximate attacker could use this to cause a denial of service\n(system crash). (CVE-2017-17558)\n\nDmitry Vyukov discovered that the KVM implementation in the Linux kernel\ncontained an out-of-bounds read when handling memory-mapped I/O. A local\nattacker could use this to expose sensitive information. (CVE-2017-17741)\n\nIt was discovered that the Salsa20 encryption algorithm implementations in\nthe Linux kernel did not properly handle zero-length inputs. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2017-17805)\n\nIt was discovered that the HMAC implementation did not validate the state\nof the underlying cryptographic hash algorithm. A local attacker could use\nthis to cause a denial of service (system crash) or possibly execute\narbitrary code. (CVE-2017-17806)\n\nIt was discovered that the keyring implementation in the Linux kernel did\nnot properly check permissions when a key request was performed on a\ntask's default keyring. A local attacker could use this to add keys to\nunauthorized keyrings. (CVE-2017-17807)\n\nAlexei Starovoitov discovered that the Berkeley Packet Filter (BPF)\nimplementation in the Linux kernel contained a branch-pruning logic issue\naround unreachable code. A local attacker could use this to cause a denial\nof service. (CVE-2017-17862)\n\nIt was discovered that the parallel cryptography component of the Linux\nkernel incorrectly freed kernel memory. A local attacker could use this to\ncause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2017-18075)\n\nIt was discovered that a race condition existed in the Device Mapper\ncomponent of the Linux kernel. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2017-18203)\n\nIt was discovered that a race condition existed in the OCFS2 file system\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (kernel deadlock). (CVE-2017-18204)\n\nIt was discovered that an infinite loop could occur in the madvise(2)\nimplementation in the Linux kernel in certain circumstances. A local\nattacker could use this to cause a denial of service (system hang).\n(CVE-2017-18208)\n\nAndy Lutomirski discovered that the KVM implementation in the Linux kernel\nwas vulnerable to a debug exception error when single-stepping through a\nsyscall. A local attacker in a non-Linux guest vm could possibly use this\nto gain administrative privileges in the guest vm. (CVE-2017-7518)\n\nIt was discovered that the Broadcom NetXtremeII ethernet driver in the\nLinux kernel did not properly validate Generic Segment Offload (GSO) packet\nsizes. An attacker could use this to cause a denial of service (interface\nunavailability). (CVE-2018-1000026)\n\nIt was discovered that the Reliable Datagram Socket (RDS)\nimplementation in the Linux kernel contained an out-of-bounds write\nduring RDMA page allocation. An attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2018-5332)\n\nMohamed Ghannam discovered a null pointer dereference in the RDS (Reliable\nDatagram Sockets) protocol implementation of the Linux kernel. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2018-5333)\n\n范龙飞 discovered that a race condition existed in loop block device\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-5344)\n\nIt was discovered that an integer overflow error existed in the futex\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (system crash). (CVE-2018-6927)\n\nIt was discovered that a NULL pointer dereference existed in the RDS\n(Reliable Datagram Sockets) protocol implementation in the Linux kernel. A\nlocal attacker could use this to cause a denial of service (system crash).\n(CVE-2018-7492)\n\nIt was discovered that the Broadcom UniMAC MDIO bus controller driver in\nthe Linux kernel did not properly validate device resources. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2018-8043)\n","status":"published","published":"2018-04-04T19:21:17Z","modified":"2026-04-22T09:45:39.830198Z","updated_at":"2026-11-02T16:58:13.496563Z"},{"id":"USN-3619-2","title":"linux-lts-xenial, linux-aws vulnerabilities","description":"USN-3619-1 fixed vulnerabilities in the Linux kernel for Ubuntu 16.04\nLTS. This update provides the corresponding updates for the Linux\nHardware Enablement (HWE) kernel from Ubuntu 16.04 LTS for Ubuntu\n14.04 LTS.\n\nJann Horn discovered that the Berkeley Packet Filter (BPF) implementation\nin the Linux kernel improperly performed sign extension in some situations.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2017-16995)\n\nIt was discovered that a race condition leading to a use-after-free\nvulnerability existed in the ALSA PCM subsystem of the Linux kernel. A\nlocal attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2017-0861)\n\nIt was discovered that the KVM implementation in the Linux kernel allowed\npassthrough of the diagnostic I/O port 0x80. An attacker in a guest VM\ncould use this to cause a denial of service (system crash) in the host OS.\n(CVE-2017-1000407)\n\nIt was discovered that an information disclosure vulnerability existed in\nthe ACPI implementation of the Linux kernel. A local attacker could use\nthis to expose sensitive information (kernel memory addresses).\n(CVE-2017-11472)\n\nIt was discovered that a use-after-free vulnerability existed in the\nnetwork namespaces implementation in the Linux kernel. A local attacker\ncould use this to cause a denial of service (system crash) or possibly\nexecute arbitrary code. (CVE-2017-15129)\n\nIt was discovered that the Advanced Linux Sound Architecture (ALSA)\nsubsystem in the Linux kernel contained a use-after-free when handling\ndevice removal. A physically proximate attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2017-16528)\n\nAndrey Konovalov discovered that the usbtest device driver in the Linux\nkernel did not properly validate endpoint metadata. A physically proximate\nattacker could use this to cause a denial of service (system crash).\n(CVE-2017-16532)\n\nAndrey Konovalov discovered that the Conexant cx231xx USB video capture\ndriver in the Linux kernel did not properly validate interface descriptors.\nA physically proximate attacker could use this to cause a denial of service\n(system crash). (CVE-2017-16536)\n\nAndrey Konovalov discovered that the SoundGraph iMON USB driver in the\nLinux kernel did not properly validate device metadata. A physically\nproximate attacker could use this to cause a denial of service (system\ncrash). (CVE-2017-16537)\n\nAndrey Konovalov discovered that the IMS Passenger Control Unit USB driver\nin the Linux kernel did not properly validate device descriptors. A\nphysically proximate attacker could use this to cause a denial of service\n(system crash). (CVE-2017-16645)\n\nAndrey Konovalov discovered that the DiBcom DiB0700 USB DVB driver in the\nLinux kernel did not properly handle detach events. A physically proximate\nattacker could use this to cause a denial of service (system crash).\n(CVE-2017-16646)\n\nAndrey Konovalov discovered that the CDC USB Ethernet driver did not\nproperly validate device descriptors. A physically proximate attacker could\nuse this to cause a denial of service (system crash). (CVE-2017-16649)\n\nAndrey Konovalov discovered that the QMI WWAN USB driver did not properly\nvalidate device descriptors. A physically proximate attacker could use this\nto cause a denial of service (system crash). (CVE-2017-16650)\n\nIt was discovered that the USB Virtual Host Controller Interface (VHCI)\ndriver in the Linux kernel contained an information disclosure\nvulnerability. A physically proximate attacker could use this to expose\nsensitive information (kernel memory). (CVE-2017-16911)\n\nIt was discovered that the USB over IP implementation in the Linux kernel\ndid not validate endpoint numbers. A remote attacker could use this to\ncause a denial of service (system crash). (CVE-2017-16912)\n\nIt was discovered that the USB over IP implementation in the Linux kernel\ndid not properly validate CMD_SUBMIT packets. A remote attacker could use\nthis to cause a denial of service (excessive memory consumption).\n(CVE-2017-16913)\n\nIt was discovered that the USB over IP implementation in the Linux kernel\ncontained a NULL pointer dereference error. A remote attacker could use\nthis to cause a denial of service (system crash). (CVE-2017-16914)\n\nIt was discovered that the HugeTLB component of the Linux kernel did not\nproperly handle holes in hugetlb ranges. A local attacker could use this to\nexpose sensitive information (kernel memory). (CVE-2017-16994)\n\nIt was discovered that the netfilter component of the Linux did not\nproperly restrict access to the connection tracking helpers list. A local\nattacker could use this to bypass intended access restrictions.\n(CVE-2017-17448)\n\nIt was discovered that the netlink subsystem in the Linux kernel did not\nproperly restrict observations of netlink messages to the appropriate net\nnamespace. A local attacker could use this to expose sensitive information\n(kernel netlink traffic). (CVE-2017-17449)\n\nIt was discovered that the netfilter passive OS fingerprinting (xt_osf)\nmodule did not properly perform access control checks. A local attacker\ncould improperly modify the system-wide OS fingerprint list.\n(CVE-2017-17450)\n\nIt was discovered that the core USB subsystem in the Linux kernel did not\nvalidate the number of configurations and interfaces in a device. A\nphysically proximate attacker could use this to cause a denial of service\n(system crash). (CVE-2017-17558)\n\nDmitry Vyukov discovered that the KVM implementation in the Linux kernel\ncontained an out-of-bounds read when handling memory-mapped I/O. A local\nattacker could use this to expose sensitive information. (CVE-2017-17741)\n\nIt was discovered that the Salsa20 encryption algorithm implementations in\nthe Linux kernel did not properly handle zero-length inputs. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2017-17805)\n\nIt was discovered that the HMAC implementation did not validate the state\nof the underlying cryptographic hash algorithm. A local attacker could use\nthis to cause a denial of service (system crash) or possibly execute\narbitrary code. (CVE-2017-17806)\n\nIt was discovered that the keyring implementation in the Linux kernel did\nnot properly check permissions when a key request was performed on a task's\ndefault keyring. A local attacker could use this to add keys to\nunauthorized keyrings. (CVE-2017-17807)\n\nAlexei Starovoitov discovered that the Berkeley Packet Filter (BPF)\nimplementation in the Linux kernel contained a branch-pruning logic issue\naround unreachable code. A local attacker could use this to cause a denial\nof service. (CVE-2017-17862)\n\nIt was discovered that the parallel cryptography component of the Linux\nkernel incorrectly freed kernel memory. A local attacker could use this to\ncause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2017-18075)\n\nIt was discovered that a race condition existed in the Device Mapper\ncomponent of the Linux kernel. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2017-18203)\n\nIt was discovered that a race condition existed in the OCFS2 file system\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (kernel deadlock). (CVE-2017-18204)\n\nIt was discovered that an infinite loop could occur in the madvise(2)\nimplementation in the Linux kernel in certain circumstances. A local\nattacker could use this to cause a denial of service (system hang).\n(CVE-2017-18208)\n\nAndy Lutomirski discovered that the KVM implementation in the Linux kernel\nwas vulnerable to a debug exception error when single-stepping through a\nsyscall. A local attacker in a non-Linux guest vm could possibly use this\nto gain administrative privileges in the guest vm. (CVE-2017-7518)\n\nIt was discovered that the Broadcom NetXtremeII ethernet driver in the\nLinux kernel did not properly validate Generic Segment Offload (GSO) packet\nsizes. An attacker could use this to cause a denial of service (interface\nunavailability). (CVE-2018-1000026)\n\nIt was discovered that the Reliable Datagram Socket (RDS) implementation in\nthe Linux kernel contained an out-of-bounds write during RDMA page\nallocation. An attacker could use this to cause a denial of service (system\ncrash) or possibly execute arbitrary code. (CVE-2018-5332)\n\nMohamed Ghannam discovered a null pointer dereference in the RDS (Reliable\nDatagram Sockets) protocol implementation of the Linux kernel. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2018-5333)\n\n范龙飞 discovered that a race condition existed in loop block device\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-5344)\n\nIt was discovered that an integer overflow error existed in the futex\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (system crash). (CVE-2018-6927)\n\nIt was discovered that a NULL pointer dereference existed in the RDS\n(Reliable Datagram Sockets) protocol implementation in the Linux kernel. A\nlocal attacker could use this to cause a denial of service (system crash).\n(CVE-2018-7492)\n\nIt was discovered that the Broadcom UniMAC MDIO bus controller driver in\nthe Linux kernel did not properly validate device resources. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2018-8043)\n","status":"published","published":"2018-04-05T20:14:49Z","modified":"2026-02-10T04:41:19Z","updated_at":"2026-11-02T16:58:13.496563Z"},{"id":"USN-3633-1","title":"linux-euclid vulnerability","description":"Jann Horn discovered that the Berkeley Packet Filter (BPF) implementation\nin the Linux kernel improperly performed sign extension in some situations.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code.\n","status":"published","published":"2018-04-24T06:48:49Z","modified":"2026-02-10T04:41:20Z","updated_at":"2026-11-02T16:58:13.496563Z"}]}}