{"id":"CVE-2017-5549","aliases":["DEBIAN-CVE-2017-5549","DLA-833-1","DSA-3791-1","EUVD-2017-14650","GHSA-286m-rx96-29m7","MGASA-2017-0063","MGASA-2017-0064","MGASA-2017-0065","UBUNTU-CVE-2017-5549","USN-3208-1","USN-3208-2","USN-3361-1","USN-3754-1"],"status":"published","title":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel...","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","severity":{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.0045,"percentile":0.39394,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-532"],"published":"2017-02-06T00:00:00Z","modified":"2026-09-01T20:03:48Z","fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["4.9.6-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["4.9.6-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["4.9.6-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"linux","fixed_in":["3.13.0-157.207"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"linux-lts-xenial","fixed_in":["4.4.0-63.84~14.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux","fixed_in":["4.4.0-63.84"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","fixed_in":["4.4.0-1003.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","fixed_in":["4.10.0-32.36~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","fixed_in":["4.4.0-1044.51"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","fixed_in":["4.4.0-1047.51"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.6-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.6-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.6-1"}]}]},{"source":"osv","ecosystem":"Debian:7","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.84-2"}]}],"versions":["3.2.41-2","3.2.41-2+deb7u1","3.2.41-2+deb7u2","3.2.41-2+deb7u2~bpo60+1","3.2.46-1","3.2.46-1+deb7u1","3.2.46-1+deb7u1~bpo60+1","3.2.46-1~bpo60+1","3.2.51-1","3.2.51-1~bpo60+1","3.2.53-1","3.2.53-2","3.2.54-1","3.2.54-2","3.2.54-2~bpo60+1","3.2.57-1","3.2.57-2","3.2.57-3","3.2.57-3+deb7u1","3.2.57-3+deb7u2","3.2.57-3+deb7u2~bpo60+1","3.2.60-1","3.2.60-1+deb7u1","3.2.60-1+deb7u2","3.2.60-1+deb7u3","3.2.60-1+deb7u3~bpo60+1","3.2.63-1","3.2.63-2","3.2.63-2+deb7u1","3.2.63-2+deb7u1~bpo60+1","3.2.63-2+deb7u2","3.2.63-2+deb7u2~bpo60+1","3.2.65-1","3.2.65-1+deb7u1","3.2.65-1+deb7u1~bpo60+1","3.2.65-1+deb7u2","3.2.65-1+deb7u2~bpo60+1","3.2.68-1","3.2.68-1+deb7u1","3.2.68-1+deb7u1~bpo60+1","3.2.68-1+deb7u2","3.2.68-1+deb7u2~bpo60+1","3.2.68-1+deb7u3","3.2.68-1+deb7u3~bpo60+1","3.2.68-1+deb7u4","3.2.68-1+deb7u4~bpo60+1","3.2.68-1+deb7u5","3.2.68-1+deb7u6","3.2.68-1+deb7u6~bpo60+1","3.2.71-1","3.2.71-2","3.2.73-1","3.2.73-2","3.2.73-2+deb7u1","3.2.73-2+deb7u2","3.2.73-2+deb7u2~bpo60+1","3.2.73-2+deb7u3","3.2.78-1","3.2.81-1","3.2.81-2","3.2.82-1","3.2.84-1"],"bundled":8},{"source":"osv","ecosystem":"Debian:8","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.16.39-1+deb8u1"}]}],"versions":["3.16.36-1","3.16.36-1+deb8u1","3.16.36-1+deb8u1~bpo70+1","3.16.36-1+deb8u2","3.16.36-1+deb8u2~bpo70+1","3.16.39-1","3.16.39-1+deb8u1~bpo70+1","3.16.39-1+deb8u1~bpo70+1+gcc4.4","3.16.39-1~bpo70+1","3.16.7-ckt11-1","3.16.7-ckt11-1+deb8u1","3.16.7-ckt11-1+deb8u2","3.16.7-ckt11-1+deb8u2~bpo70+1","3.16.7-ckt11-1+deb8u3","3.16.7-ckt11-1+deb8u3~bpo70+1","3.16.7-ckt11-1+deb8u4","3.16.7-ckt11-1+deb8u4~bpo70+1","3.16.7-ckt11-1+deb8u5","3.16.7-ckt11-1+deb8u6","3.16.7-ckt11-1+deb8u6~bpo70+1","3.16.7-ckt11-1~bpo70+1","3.16.7-ckt17-1","3.16.7-ckt20-1","3.16.7-ckt20-1+deb8u1","3.16.7-ckt20-1+deb8u2","3.16.7-ckt20-1+deb8u2~bpo70+1","3.16.7-ckt20-1+deb8u3","3.16.7-ckt20-1+deb8u3~bpo70+1","3.16.7-ckt20-1+deb8u4","3.16.7-ckt20-1+deb8u4~bpo70+1","3.16.7-ckt25-1","3.16.7-ckt25-1~bpo70+1","3.16.7-ckt25-2","3.16.7-ckt25-2+deb8u1","3.16.7-ckt25-2+deb8u2","3.16.7-ckt25-2+deb8u3","3.16.7-ckt25-2+deb8u3~bpo70+1","3.16.7-ckt25-2~bpo70+1","3.16.7-ckt9-2","3.16.7-ckt9-3","3.16.7-ckt9-3~deb8u1","3.16.7-ckt9-3~deb8u1~bpo70+1"],"bundled":14},{"source":"osv","ecosystem":"Mageia:5","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.50-2.mga5"}]}],"bundled":16},{"source":"osv","ecosystem":"Mageia:5","package":"kernel-userspace-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.50-2.mga5"}]}],"bundled":16},{"source":"osv","ecosystem":"Mageia:5","package":"kmod-vboxadditions","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.10-12.mga5"}]}],"bundled":16},{"source":"osv","ecosystem":"Mageia:5","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.10-12.mga5"}]}],"bundled":16},{"source":"osv","ecosystem":"Mageia:5","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10-32.mga5"}]}],"bundled":16},{"source":"osv","ecosystem":"Mageia:5","package":"kernel-tmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.50-2.mga5"}]}],"bundled":16},{"source":"osv","ecosystem":"Mageia:5","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.50-2.mga5"}]}],"bundled":16},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.13.0-157.207"}]}],"versions":["3.11.0-12.19","3.12.0-1.3","3.12.0-2.5","3.12.0-2.7","3.12.0-3.8","3.12.0-3.9","3.12.0-4.10","3.12.0-4.12","3.12.0-5.13","3.12.0-7.15","3.13.0-1.16","3.13.0-2.17","3.13.0-3.18","3.13.0-4.19","3.13.0-5.20","3.13.0-6.23","3.13.0-7.25","3.13.0-7.26","3.13.0-8.27","3.13.0-8.28","3.13.0-10.30","3.13.0-11.31","3.13.0-12.32","3.13.0-13.33","3.13.0-14.34","3.13.0-15.35","3.13.0-16.36","3.13.0-17.37","3.13.0-18.38","3.13.0-19.39","3.13.0-19.40","3.13.0-20.42","3.13.0-21.43","3.13.0-22.44","3.13.0-23.45","3.13.0-24.46","3.13.0-24.47","3.13.0-27.50","3.13.0-29.53","3.13.0-30.54","3.13.0-30.55","3.13.0-32.57","3.13.0-33.58","3.13.0-34.60","3.13.0-35.62","3.13.0-36.63","3.13.0-37.64","3.13.0-39.66","3.13.0-40.69","3.13.0-41.70","3.13.0-43.72","3.13.0-44.73","3.13.0-45.74","3.13.0-46.75","3.13.0-46.76","3.13.0-46.77","3.13.0-46.79","3.13.0-48.80","3.13.0-49.81","3.13.0-49.83","3.13.0-51.84","3.13.0-52.85","3.13.0-52.86","3.13.0-53.88","3.13.0-53.89","3.13.0-54.91","3.13.0-55.92","3.13.0-55.94","3.13.0-57.95","3.13.0-58.97","3.13.0-59.98","3.13.0-61.100","3.13.0-62.102","3.13.0-63.103","3.13.0-65.105","3.13.0-65.106","3.13.0-66.108","3.13.0-67.110","3.13.0-68.111","3.13.0-70.113","3.13.0-71.114","3.13.0-73.116","3.13.0-74.118","3.13.0-76.120","3.13.0-77.121","3.13.0-79.123","3.13.0-83.127","3.13.0-85.129","3.13.0-86.130","3.13.0-86.131","3.13.0-87.133","3.13.0-88.135","3.13.0-91.138","3.13.0-92.139","3.13.0-93.140","3.13.0-95.142","3.13.0-96.143","3.13.0-98.145","3.13.0-100.147","3.13.0-101.148","3.13.0-103.150","3.13.0-105.152","3.13.0-106.153","3.13.0-107.154","3.13.0-108.155","3.13.0-109.156","3.13.0-110.157","3.13.0-111.158","3.13.0-112.159","3.13.0-113.160","3.13.0-115.162","3.13.0-116.163","3.13.0-117.164","3.13.0-119.166","3.13.0-121.170","3.13.0-123.172","3.13.0-125.174","3.13.0-126.175","3.13.0-128.177","3.13.0-129.178","3.13.0-132.181","3.13.0-133.182","3.13.0-135.184","3.13.0-137.186","3.13.0-139.188","3.13.0-141.190","3.13.0-142.191","3.13.0-143.192","3.13.0-144.193","3.13.0-145.194","3.13.0-147.196","3.13.0-149.199","3.13.0-151.201","3.13.0-153.203","3.13.0-155.205","3.13.0-156.206"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-63.84~14.04.2"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-63.84"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1003.12"}]}],"versions":["4.4.0-1001.10"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.0-32.36~16.04.1"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1044.51"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1047.51"}]}],"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"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-64.85"}]}],"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"],"bundled":7},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1048.52"}]}],"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"],"bundled":7},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-64.85~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"],"bundled":7},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.0-27.30~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"],"bundled":40},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.13.0-157.207"}]}],"versions":["3.11.0-12.19","3.12.0-1.3","3.12.0-2.5","3.12.0-2.7","3.12.0-3.8","3.12.0-3.9","3.12.0-4.10","3.12.0-4.12","3.12.0-5.13","3.12.0-7.15","3.13.0-1.16","3.13.0-2.17","3.13.0-3.18","3.13.0-4.19","3.13.0-5.20","3.13.0-6.23","3.13.0-7.25","3.13.0-7.26","3.13.0-8.27","3.13.0-8.28","3.13.0-10.30","3.13.0-11.31","3.13.0-12.32","3.13.0-13.33","3.13.0-14.34","3.13.0-15.35","3.13.0-16.36","3.13.0-17.37","3.13.0-18.38","3.13.0-19.39","3.13.0-19.40","3.13.0-20.42","3.13.0-21.43","3.13.0-22.44","3.13.0-23.45","3.13.0-24.46","3.13.0-24.47","3.13.0-27.50","3.13.0-29.53","3.13.0-30.54","3.13.0-30.55","3.13.0-32.57","3.13.0-33.58","3.13.0-34.60","3.13.0-35.62","3.13.0-36.63","3.13.0-37.64","3.13.0-39.66","3.13.0-40.69","3.13.0-41.70","3.13.0-43.72","3.13.0-44.73","3.13.0-45.74","3.13.0-46.75","3.13.0-46.76","3.13.0-46.77","3.13.0-46.79","3.13.0-48.80","3.13.0-49.81","3.13.0-49.83","3.13.0-51.84","3.13.0-52.85","3.13.0-52.86","3.13.0-53.88","3.13.0-53.89","3.13.0-54.91","3.13.0-55.92","3.13.0-55.94","3.13.0-57.95","3.13.0-58.97","3.13.0-59.98","3.13.0-61.100","3.13.0-62.102","3.13.0-63.103","3.13.0-65.105","3.13.0-65.106","3.13.0-66.108","3.13.0-67.110","3.13.0-68.111","3.13.0-70.113","3.13.0-71.114","3.13.0-73.116","3.13.0-74.118","3.13.0-76.120","3.13.0-77.121","3.13.0-79.123","3.13.0-83.127","3.13.0-85.129","3.13.0-86.130","3.13.0-86.131","3.13.0-87.133","3.13.0-88.135","3.13.0-91.138","3.13.0-92.139","3.13.0-93.140","3.13.0-95.142","3.13.0-96.143","3.13.0-98.145","3.13.0-100.147","3.13.0-101.148","3.13.0-103.150","3.13.0-105.152","3.13.0-106.153","3.13.0-107.154","3.13.0-108.155","3.13.0-109.156","3.13.0-110.157","3.13.0-111.158","3.13.0-112.159","3.13.0-113.160","3.13.0-115.162","3.13.0-116.163","3.13.0-117.164","3.13.0-119.166","3.13.0-121.170","3.13.0-123.172","3.13.0-125.174","3.13.0-126.175","3.13.0-128.177","3.13.0-129.178","3.13.0-132.181","3.13.0-133.182","3.13.0-135.184","3.13.0-137.186","3.13.0-139.188","3.13.0-141.190","3.13.0-142.191","3.13.0-143.192","3.13.0-144.193","3.13.0-145.194","3.13.0-147.196","3.13.0-149.199","3.13.0-151.201","3.13.0-153.203","3.13.0-155.205","3.13.0-156.206"],"bundled":53}],"products":[{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"http://www.securityfocus.com/bid/95715","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"http://www.openwall.com/lists/oss-security/2017/01/21/3","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Patch","Third Party Advisory","fix"]},{"url":"https://usn.ubuntu.com/3754-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","web"]},{"url":"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=146cc8a17a3b4996f6805ee5c080e7101277c410","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix"]},{"url":"https://github.com/torvalds/linux/commit/146cc8a17a3b4996f6805ee5c080e7101277c410","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix"]},{"url":"http://www.debian.org/security/2017/dsa-3791","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","advisory"]},{"url":"http://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.5","tags":["x_refsource_CONFIRM","x_transferred","Release Notes","Vendor Advisory","advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1416114","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","fix"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-5549"},{"url":"https://usn.ubuntu.com/3754-1"},{"url":"https://github.com/advisories/GHSA-286m-rx96-29m7"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-5549","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2017-0063.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=20313","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.40","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.41","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.42","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.43","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.44","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.45","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.46","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.47","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.48","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.49","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.50","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2017-0064.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=20314","tags":["report"]},{"url":"https://advisories.mageia.org/MGASA-2017-0065.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=20315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5549","tags":["report"]},{"url":"http://seclists.org/oss-sec/2017/q1/161","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3208-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3208-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3361-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3754-1","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-5549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-10088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2015-1350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-8405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-8636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-10208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16535","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-16538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16645","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-17558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-13094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-13405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-13406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1000204","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2017-5549","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","status":"published","published":"2017-02-06T06:04:00Z","modified":"2024-08-05T15:04:15.318Z","updated_at":"2026-11-02T14:33:12.599234Z"}],"euvd":[{"id":"EUVD-2017-14650","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","status":"published","published":"2017-02-06T06:04:00Z","modified":"2024-08-05T15:04:15Z","updated_at":"2026-11-03T02:39:15.385305Z"}],"ghsa":[{"id":"GHSA-286m-rx96-29m7","title":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel...","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","status":"published","published":"2022-05-14T03:05:18Z","modified":"2025-04-20T03:32:25Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-532"],"updated_at":"2026-11-02T15:01:39.626411Z"}],"nvd":[{"id":"CVE-2017-5549","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","status":"published","published":"2017-02-06T06:59:00.623Z","modified":"2026-06-17T01:20:43.74Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"primary"},{"version":"2.0","score":2.1,"vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","level":"low","assessor":"primary"}],"cwes":["CWE-532"],"updated_at":"2026-11-02T14:03:42.372487Z"}],"osv":[{"id":"CVE-2017-5549","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","status":"published","published":"2017-02-06T06:59:00.623Z","modified":"2026-04-16T06:23:23.839468075Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:06.029968Z"},{"id":"DEBIAN-CVE-2017-5549","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","status":"published","published":"2017-02-06T06:59:00.623Z","modified":"2026-09-01T20:03:48.528364859Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:29.412243Z"},{"id":"UBUNTU-CVE-2017-5549","description":"The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log.","status":"published","published":"2017-02-06T00:00:00Z","modified":"2026-04-22T11:28:19.85724Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:54:15.388065Z"},{"id":"DLA-833-1","title":"linux - security update","status":"published","published":"2017-02-22T00:00:00Z","modified":"2026-03-09T02:09:01.444979Z","updated_at":"2026-11-02T15:46:13.207219Z"},{"id":"DSA-3791-1","title":"linux - security update","status":"published","published":"2017-02-22T00:00:00Z","modified":"2026-03-09T01:21:05.532448Z","updated_at":"2026-11-02T15:46:16.523846Z"},{"id":"MGASA-2017-0063","title":"Updated kernel and kmod packages fixes security vulnerabilities","description":"This kernel update is based on upstream 4.4.50 and fixes at least\nthe following security issues:\n\nThe cgroup offline implementation in the Linux kernel through 4.8.11\nmishandles certain drain operations, which allows local users to cause\na denial of service (system hang) by leveraging access to a container\nenvironment for executing a crafted application, as demonstrated by\ntrinity (CVE-2016-9191).\n\narch/x86/kvm/vmx.c in the Linux kernel through 4.9 mismanages the #BP\nand #OF exceptions, which allows guest OS users to cause a denial of\nservice (guest OS crash) by declining to handle an exception thrown by\nan L2 guest (CVE-2016-9588).\n\nThe sg implementation in the Linux kernel through 4.9 does not properly\nrestrict write operations in situations where the KERNEL_DS option is set,\nwhich allows local users to read or write to arbitrary kernel memory\nlocations or cause a denial of service (use-after-free) by leveraging\naccess to a /dev/sg device, related to block/bsg.c and drivers/scsi/sg.c\n(CVE-2016-10088).\n\nThe ext4_fill_super function in fs/ext4/super.c in the Linux kernel\nthrough 4.9.8 does not properly validate meta block groups, which\nallows physically proximate attackers to cause a denial of service\n(out-of-bounds read and system crash) via a crafted ext4 image\n(CVE-2016-10208).\n\nThe load_segment_descriptor implementation in arch/x86/kvm/emulate.c in\nthe Linux kernel before 4.9.5 improperly emulates a \"MOV SS, NULL\nselector\" instruction, which allows guest OS users to cause a denial of\nservice (guest OS crash) or gain guest OS privileges via a crafted\napplication (CVE-2017-2583).\n\narch/x86/kvm/emulate.c in the Linux kernel through 4.9.3 allows local\nusers to obtain sensitive information from kernel memory or cause a\ndenial of service (use-after-free) via a crafted application that\nleverages instruction emulation for fxrstor, fxsave, sgdt, and sidt\n(CVE-2017-2584).\n\ndrivers/hid/hid-corsair.c in the Linux kernel 4.9.x before 4.9.6\ninteracts incorrectly with the CONFIG_VMAP_STACK option, which allows\nlocal users to cause a denial of service (system crash or memory\ncorruption) or possibly have unspecified other impact by leveraging\nuse of more than one virtual page for a DMA scatterlist (CVE-2017-5547).\n\ndrivers/net/ieee802154/atusb.c in the Linux kernel 4.9.x before 4.9.6\ninteracts incorrectly with the CONFIG_VMAP_STACK option, which allows\nlocal users to cause a denial of service (system crash or memory\ncorruption) or possibly have unspecified other impact by leveraging\nuse of more than one virtual page for a DMA scatterlist (CVE-2017-5548).\n\nThe klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c\nin the Linux kernel before 4.9.5 places uninitialized heap-memory\ncontents into a log entry upon a failure to read the line status, which\nallows local users to obtain sensitive information by reading the log\n(CVE-2017-5549).\n\nThe simple_set_acl function in fs/posix_acl.c in the Linux kernel before\n4.9.6 preserves the setgid bit during a setxattr call involving a tmpfs\nfilesystem, which allows local users to gain group privileges by\nleveraging the existence of a setgid program with restrictions on\nexecute permissions (CVE-2017-5551).\n\nAn issue was found in the Linux kernel ipv6 implementation of GRE tunnels\nwhich allows a remote attacker to trigger an out-of-bounds access\n(CVE-2017-5897).\n\nThe ipv4_pktinfo_prepare function in net/ipv4/ip_sockglue.c in the Linux\nkernel through 4.9.9 allows attackers to cause a denial of service\n(system crash) via (1) an application that makes crafted system calls or\npossibly (2) IPv4 traffic with invalid IP options (CVE-2017-5970).\n\nRace condition in the sctp_wait_for_sndbuf function in net/sctp/socket.c\nin the Linux kernel before 4.9.11 allows local users to cause a denial\nof service (assertion failure and panic) via a multithreaded application\nthat peels off an association in a certain buffer-full state\n(CVE-2017-5986).\n\nThe dccp_rcv_state_process function in net/dccp/input.c in the Linux\nkernel through 4.9.11 mishandles DCCP_PKT_REQUEST packet data structures\nin the LISTEN state, which allows local users to obtain root privileges\nor cause a denial of service (double free) via an application that makes\nan IPV6_RECVPKTINFO setsockopt system call (CVE-2017-6074).\n\nThe tcp_splice_read function in net/ipv4/tcp.c in the Linux kernel before\n4.9.11 allows remote attackers to cause a denial of service (infinite loop\nand soft lockup) via vectors involving a TCP packet with the URG flag\n(CVE-2017-6214).\n\nnet/sctp/socket.c in the Linux kernel through 4.10.1 does not properly\nrestrict association peel-off operations during certain wait states, which\nallows local users to cause a denial of service (invalid unlock and double\nfree) via a multithreaded application (CVE-2017-6353).\n\nFor other upstream fixes in this update, see the referenced changelogs.\n","status":"published","published":"2017-02-25T08:29:30Z","modified":"2026-04-16T06:23:17.213917172Z","updated_at":"2026-11-02T15:49:40.103088Z"},{"id":"MGASA-2017-0064","title":"Updated kernel-tmb packages fixes security vulnerabilities","description":"This kernel-tmb update is based on upstream 4.4.50 and fixes at least\nthe following security issues:\n\nThe cgroup offline implementation in the Linux kernel through 4.8.11\nmishandles certain drain operations, which allows local users to cause\na denial of service (system hang) by leveraging access to a container\nenvironment for executing a crafted application, as demonstrated by\ntrinity (CVE-2016-9191).\n\narch/x86/kvm/vmx.c in the Linux kernel through 4.9 mismanages the #BP\nand #OF exceptions, which allows guest OS users to cause a denial of\nservice (guest OS crash) by declining to handle an exception thrown by\nan L2 guest (CVE-2016-9588).\n\nThe sg implementation in the Linux kernel through 4.9 does not properly\nrestrict write operations in situations where the KERNEL_DS option is set,\nwhich allows local users to read or write to arbitrary kernel memory\nlocations or cause a denial of service (use-after-free) by leveraging\naccess to a /dev/sg device, related to block/bsg.c and drivers/scsi/sg.c\n(CVE-2016-10088).\n\nThe ext4_fill_super function in fs/ext4/super.c in the Linux kernel\nthrough 4.9.8 does not properly validate meta block groups, which\nallows physically proximate attackers to cause a denial of service\n(out-of-bounds read and system crash) via a crafted ext4 image\n(CVE-2016-10208).\n\nThe load_segment_descriptor implementation in arch/x86/kvm/emulate.c in\nthe Linux kernel before 4.9.5 improperly emulates a \"MOV SS, NULL\nselector\" instruction, which allows guest OS users to cause a denial of\nservice (guest OS crash) or gain guest OS privileges via a crafted\napplication (CVE-2017-2583).\n\narch/x86/kvm/emulate.c in the Linux kernel through 4.9.3 allows local\nusers to obtain sensitive information from kernel memory or cause a\ndenial of service (use-after-free) via a crafted application that\nleverages instruction emulation for fxrstor, fxsave, sgdt, and sidt\n(CVE-2017-2584).\n\ndrivers/hid/hid-corsair.c in the Linux kernel 4.9.x before 4.9.6\ninteracts incorrectly with the CONFIG_VMAP_STACK option, which allows\nlocal users to cause a denial of service (system crash or memory\ncorruption) or possibly have unspecified other impact by leveraging\nuse of more than one virtual page for a DMA scatterlist (CVE-2017-5547).\n\ndrivers/net/ieee802154/atusb.c in the Linux kernel 4.9.x before 4.9.6\ninteracts incorrectly with the CONFIG_VMAP_STACK option, which allows\nlocal users to cause a denial of service (system crash or memory\ncorruption) or possibly have unspecified other impact by leveraging\nuse of more than one virtual page for a DMA scatterlist (CVE-2017-5548).\n\nThe klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c\nin the Linux kernel before 4.9.5 places uninitialized heap-memory\ncontents into a log entry upon a failure to read the line status, which\nallows local users to obtain sensitive information by reading the log\n(CVE-2017-5549).\n\nThe simple_set_acl function in fs/posix_acl.c in the Linux kernel before\n4.9.6 preserves the setgid bit during a setxattr call involving a tmpfs\nfilesystem, which allows local users to gain group privileges by\nleveraging the existence of a setgid program with restrictions on\nexecute permissions (CVE-2017-5551).\n\nAn issue was found in the Linux kernel ipv6 implementation of GRE tunnels\nwhich allows a remote attacker to trigger an out-of-bounds access\n(CVE-2017-5897).\n\nThe ipv4_pktinfo_prepare function in net/ipv4/ip_sockglue.c in the Linux\nkernel through 4.9.9 allows attackers to cause a denial of service\n(system crash) via (1) an application that makes crafted system calls or\npossibly (2) IPv4 traffic with invalid IP options (CVE-2017-5970).\n\nRace condition in the sctp_wait_for_sndbuf function in net/sctp/socket.c\nin the Linux kernel before 4.9.11 allows local users to cause a denial\nof service (assertion failure and panic) via a multithreaded application\nthat peels off an association in a certain buffer-full state\n(CVE-2017-5986).\n\nThe dccp_rcv_state_process function in net/dccp/input.c in the Linux\nkernel through 4.9.11 mishandles DCCP_PKT_REQUEST packet data structures\nin the LISTEN state, which allows local users to obtain root privileges\nor cause a denial of service (double free) via an application that makes\nan IPV6_RECVPKTINFO setsockopt system call (CVE-2017-6074).\n\nThe tcp_splice_read function in net/ipv4/tcp.c in the Linux kernel before\n4.9.11 allows remote attackers to cause a denial of service (infinite loop\nand soft lockup) via vectors involving a TCP packet with the URG flag\n(CVE-2017-6214).\n\nnet/sctp/socket.c in the Linux kernel through 4.10.1 does not properly\nrestrict association peel-off operations during certain wait states, which\nallows local users to cause a denial of service (invalid unlock and double\nfree) via a multithreaded application (CVE-2017-6353).\n\nFor other upstream fixes in this update, see the referenced changelogs.\n","status":"published","published":"2017-02-25T08:29:30Z","modified":"2026-04-16T06:26:02.360594521Z","updated_at":"2026-11-02T15:49:40.103088Z"},{"id":"MGASA-2017-0065","title":"Updated kernel-linus fixes security vulnerabilities","description":"This kernel-linus update is based on upstream 4.4.50 and fixes at least\nthe following security issues:\n\nThe cgroup offline implementation in the Linux kernel through 4.8.11\nmishandles certain drain operations, which allows local users to cause\na denial of service (system hang) by leveraging access to a container\nenvironment for executing a crafted application, as demonstrated by\ntrinity (CVE-2016-9191).\n\narch/x86/kvm/vmx.c in the Linux kernel through 4.9 mismanages the #BP\nand #OF exceptions, which allows guest OS users to cause a denial of\nservice (guest OS crash) by declining to handle an exception thrown by\nan L2 guest (CVE-2016-9588).\n\nThe sg implementation in the Linux kernel through 4.9 does not properly\nrestrict write operations in situations where the KERNEL_DS option is set,\nwhich allows local users to read or write to arbitrary kernel memory\nlocations or cause a denial of service (use-after-free) by leveraging\naccess to a /dev/sg device, related to block/bsg.c and drivers/scsi/sg.c\n(CVE-2016-10088).\n\nThe ext4_fill_super function in fs/ext4/super.c in the Linux kernel\nthrough 4.9.8 does not properly validate meta block groups, which\nallows physically proximate attackers to cause a denial of service\n(out-of-bounds read and system crash) via a crafted ext4 image\n(CVE-2016-10208).\n\nThe load_segment_descriptor implementation in arch/x86/kvm/emulate.c in\nthe Linux kernel before 4.9.5 improperly emulates a \"MOV SS, NULL\nselector\" instruction, which allows guest OS users to cause a denial of\nservice (guest OS crash) or gain guest OS privileges via a crafted\napplication (CVE-2017-2583).\n\narch/x86/kvm/emulate.c in the Linux kernel through 4.9.3 allows local\nusers to obtain sensitive information from kernel memory or cause a\ndenial of service (use-after-free) via a crafted application that\nleverages instruction emulation for fxrstor, fxsave, sgdt, and sidt\n(CVE-2017-2584).\n\ndrivers/hid/hid-corsair.c in the Linux kernel 4.9.x before 4.9.6\ninteracts incorrectly with the CONFIG_VMAP_STACK option, which allows\nlocal users to cause a denial of service (system crash or memory\ncorruption) or possibly have unspecified other impact by leveraging\nuse of more than one virtual page for a DMA scatterlist (CVE-2017-5547).\n\ndrivers/net/ieee802154/atusb.c in the Linux kernel 4.9.x before 4.9.6\ninteracts incorrectly with the CONFIG_VMAP_STACK option, which allows\nlocal users to cause a denial of service (system crash or memory\ncorruption) or possibly have unspecified other impact by leveraging\nuse of more than one virtual page for a DMA scatterlist (CVE-2017-5548).\n\nThe klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c\nin the Linux kernel before 4.9.5 places uninitialized heap-memory\ncontents into a log entry upon a failure to read the line status, which\nallows local users to obtain sensitive information by reading the log\n(CVE-2017-5549).\n\nThe simple_set_acl function in fs/posix_acl.c in the Linux kernel before\n4.9.6 preserves the setgid bit during a setxattr call involving a tmpfs\nfilesystem, which allows local users to gain group privileges by\nleveraging the existence of a setgid program with restrictions on\nexecute permissions (CVE-2017-5551).\n\nAn issue was found in the Linux kernel ipv6 implementation of GRE tunnels\nwhich allows a remote attacker to trigger an out-of-bounds access\n(CVE-2017-5897).\n\nThe ipv4_pktinfo_prepare function in net/ipv4/ip_sockglue.c in the Linux\nkernel through 4.9.9 allows attackers to cause a denial of service\n(system crash) via (1) an application that makes crafted system calls or\npossibly (2) IPv4 traffic with invalid IP options (CVE-2017-5970).\n\nRace condition in the sctp_wait_for_sndbuf function in net/sctp/socket.c\nin the Linux kernel before 4.9.11 allows local users to cause a denial\nof service (assertion failure and panic) via a multithreaded application\nthat peels off an association in a certain buffer-full state\n(CVE-2017-5986).\n\nThe dccp_rcv_state_process function in net/dccp/input.c in the Linux\nkernel through 4.9.11 mishandles DCCP_PKT_REQUEST packet data structures\nin the LISTEN state, which allows local users to obtain root privileges\nor cause a denial of service (double free) via an application that makes\nan IPV6_RECVPKTINFO setsockopt system call (CVE-2017-6074).\n\nThe tcp_splice_read function in net/ipv4/tcp.c in the Linux kernel before\n4.9.11 allows remote attackers to cause a denial of service (infinite loop\nand soft lockup) via vectors involving a TCP packet with the URG flag\n(CVE-2017-6214).\n\nnet/sctp/socket.c in the Linux kernel through 4.10.1 does not properly\nrestrict association peel-off operations during certain wait states, which\nallows local users to cause a denial of service (invalid unlock and double\nfree) via a multithreaded application (CVE-2017-6353).\n\nFor other upstream fixes in this update, see the referenced changelogs.\n","status":"published","published":"2017-02-25T08:29:30Z","modified":"2026-04-16T06:26:17.504761968Z","updated_at":"2026-11-02T15:49:40.103088Z"},{"id":"USN-3208-1","title":"linux, linux-snapdragon vulnerabilities","description":"It was discovered that the generic SCSI block layer in the Linux kernel did\nnot properly restrict write operations in certain situations. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly gain administrative privileges. (CVE-2016-10088)\n\nCAI Qian discovered that the sysctl implementation in the Linux kernel did\nnot properly perform reference counting in some situations. An unprivileged\nattacker could use this to cause a denial of service (system hang).\n(CVE-2016-9191)\n\nJim Mattson discovered that the KVM implementation in the Linux kernel\nmismanages the #BP and #OF exceptions. A local attacker in a guest virtual\nmachine could use this to cause a denial of service (guest OS crash).\n(CVE-2016-9588)\n\nAndy Lutomirski and Willy Tarreau discovered that the KVM implementation in\nthe Linux kernel did not properly emulate instructions on the SS segment\nregister. A local attacker in a guest virtual machine could use this to\ncause a denial of service (guest OS crash) or possibly gain administrative\nprivileges in the guest OS. (CVE-2017-2583)\n\nDmitry Vyukov discovered that the KVM implementation in the Linux kernel\nimproperly emulated certain instructions. A local attacker could use this\nto obtain sensitive information (kernel memory). (CVE-2017-2584)\n\nIt was discovered that the KLSI KL5KUSB105 serial-to-USB device driver in\nthe Linux kernel did not properly initialize memory related to logging. A\nlocal attacker could use this to expose sensitive information (kernel\nmemory). (CVE-2017-5549)\n\nAndrey Konovalov discovered a use-after-free vulnerability in the DCCP\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (system crash) or possibly gain administrative\nprivileges. (CVE-2017-6074)\n","status":"published","published":"2017-02-22T07:26:16Z","modified":"2026-04-22T09:32:19.250152Z","updated_at":"2026-11-02T16:58:10.303275Z"},{"id":"USN-3208-2","title":"linux-lts-xenial vulnerabilities","description":"USN-3208-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\nIt was discovered that the generic SCSI block layer in the Linux kernel did\nnot properly restrict write operations in certain situations. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly gain administrative privileges. (CVE-2016-10088)\n\nCAI Qian discovered that the sysctl implementation in the Linux kernel did\nnot properly perform reference counting in some situations. An unprivileged\nattacker could use this to cause a denial of service (system hang).\n(CVE-2016-9191)\n\nJim Mattson discovered that the KVM implementation in the Linux kernel\nmismanages the #BP and #OF exceptions. A local attacker in a guest virtual\nmachine could use this to cause a denial of service (guest OS crash).\n(CVE-2016-9588)\n\nAndy Lutomirski and Willy Tarreau discovered that the KVM implementation in\nthe Linux kernel did not properly emulate instructions on the SS segment\nregister. A local attacker in a guest virtual machine could use this to\ncause a denial of service (guest OS crash) or possibly gain administrative\nprivileges in the guest OS. (CVE-2017-2583)\n\nDmitry Vyukov discovered that the KVM implementation in the Linux kernel\nimproperly emulated certain instructions. A local attacker could use this\nto obtain sensitive information (kernel memory). (CVE-2017-2584)\n\nIt was discovered that the KLSI KL5KUSB105 serial-to-USB device driver in\nthe Linux kernel did not properly initialize memory related to logging. A\nlocal attacker could use this to expose sensitive information (kernel\nmemory). (CVE-2017-5549)\n\nAndrey Konovalov discovered a use-after-free vulnerability in the DCCP\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (system crash) or possibly gain administrative\nprivileges. (CVE-2017-6074)\n","status":"published","published":"2017-02-22T07:34:18Z","modified":"2026-02-10T04:41:05Z","updated_at":"2026-11-02T16:58:10.303275Z"},{"id":"USN-3361-1","title":"linux-hwe vulnerabilities","description":"USN-3358-1 fixed vulnerabilities in the Linux kernel for Ubuntu 17.04.\nThis update provides the corresponding updates for the Linux Hardware\nEnablement (HWE) kernel from Ubuntu 17.04 for Ubuntu 16.04 LTS. Please\nnote that this update changes the Linux HWE kernel to the 4.10 based\nkernel from Ubuntu 17.04, superseding the 4.8 based HWE kernel from\nUbuntu 16.10.\n\nBen Harris discovered that the Linux kernel would strip extended privilege\nattributes of files when performing a failed unprivileged system call. A\nlocal attacker could use this to cause a denial of service. (CVE-2015-1350)\n\nRalf Spenneberg discovered that the ext4 implementation in the Linux kernel\ndid not properly validate meta block groups. An attacker with physical\naccess could use this to specially craft an ext4 image that causes a denial\nof service (system crash). (CVE-2016-10208)\n\nPeter Pi discovered that the colormap handling for frame buffer devices in\nthe Linux kernel contained an integer overflow. A local attacker could use\nthis to disclose sensitive information (kernel memory). (CVE-2016-8405)\n\nIt was discovered that an integer overflow existed in the InfiniBand RDMA\nover ethernet (RXE) transport implementation in the Linux kernel. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2016-8636)\n\nVlad Tsyrklevich discovered an integer overflow vulnerability in the VFIO\nPCI driver for the Linux kernel. A local attacker with access to a vfio PCI\ndevice file could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2016-9083, CVE-2016-9084)\n\nCAI Qian discovered that the sysctl implementation in the Linux kernel did\nnot properly perform reference counting in some situations. An unprivileged\nattacker could use this to cause a denial of service (system hang).\n(CVE-2016-9191)\n\nIt was discovered that the keyring implementation in the Linux kernel in\nsome situations did not prevent special internal keyrings from being joined\nby userspace keyrings. A privileged local attacker could use this to bypass\nmodule verification. (CVE-2016-9604)\n\nDmitry Vyukov, Andrey Konovalov, Florian Westphal, and Eric Dumazet\ndiscovered that the netfiler subsystem in the Linux kernel mishandled IPv6\npacket reassembly. A local user could use this to cause a denial of service\n(system crash) or possibly execute arbitrary code. (CVE-2016-9755)\n\nAndy Lutomirski and Willy Tarreau discovered that the KVM implementation in\nthe Linux kernel did not properly emulate instructions on the SS segment\nregister. A local attacker in a guest virtual machine could use this to\ncause a denial of service (guest OS crash) or possibly gain administrative\nprivileges in the guest OS. (CVE-2017-2583)\n\nDmitry Vyukov discovered that the KVM implementation in the Linux kernel\nimproperly emulated certain instructions. A local attacker could use this\nto obtain sensitive information (kernel memory). (CVE-2017-2584)\n\nDmitry Vyukov discovered that KVM implementation in the Linux kernel\nimproperly emulated the VMXON instruction. A local attacker in a guest OS\ncould use this to cause a denial of service (memory consumption) in the\nhost OS. (CVE-2017-2596)\n\nIt was discovered that SELinux in the Linux kernel did not properly handle\nempty writes to /proc/pid/attr. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2017-2618)\n\nDaniel Jiang discovered that a race condition existed in the ipv4 ping\nsocket implementation in the Linux kernel. A local privileged attacker\ncould use this to cause a denial of service (system crash). (CVE-2017-2671)\n\nIt was discovered that the freelist-randomization in the SLAB memory\nallocator allowed duplicate freelist entries. A local attacker could use\nthis to cause a denial of service (system crash). (CVE-2017-5546)\n\nIt was discovered that the KLSI KL5KUSB105 serial-to-USB device driver in\nthe Linux kernel did not properly initialize memory related to logging. A\nlocal attacker could use this to expose sensitive information (kernel\nmemory). (CVE-2017-5549)\n\nIt was discovered that a fencepost error existed in the pipe_advance()\nfunction in the Linux kernel. A local attacker could use this to expose\nsensitive information (kernel memory). (CVE-2017-5550)\n\nIt was discovered that the Linux kernel did not clear the setgid bit during\na setxattr call on a tmpfs filesystem. A local attacker could use this to\ngain elevated group privileges. (CVE-2017-5551)\n\nMurray McAllister discovered that an integer overflow existed in the\nVideoCore DRM driver of the Linux kernel. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2017-5576)\n\nGareth Evans discovered that the shm IPC subsystem in the Linux kernel did\nnot properly restrict mapping page zero. A local privileged attacker could\nuse this to execute arbitrary code. (CVE-2017-5669)\n\nAndrey Konovalov discovered an out-of-bounds access in the IPv6 Generic\nRouting Encapsulation (GRE) tunneling implementation in the Linux kernel.\nAn attacker could use this to possibly expose sensitive information.\n(CVE-2017-5897)\n\nAndrey Konovalov discovered that the IPv4 implementation in the Linux\nkernel did not properly handle invalid IP options in some situations. An\nattacker could use this to cause a denial of service or possibly execute\narbitrary code. (CVE-2017-5970)\n\nDi Shen discovered that a race condition existed in the perf subsystem of\nthe Linux kernel. A local attacker could use this to cause a denial of\nservice or possibly gain administrative privileges. (CVE-2017-6001)\n\nDmitry Vyukov discovered that the Linux kernel did not properly handle TCP\npackets with the URG flag. A remote attacker could use this to cause a\ndenial of service. (CVE-2017-6214)\n\nAndrey Konovalov discovered that the LLC subsytem in the Linux kernel did\nnot properly set up a destructor in certain situations. A local attacker\ncould use this to cause a denial of service (system crash). (CVE-2017-6345)\n\nIt was discovered that a race condition existed in the AF_PACKET handling\ncode in the Linux kernel. A local attacker could use this to cause a denial\nof service (system crash) or possibly execute arbitrary code.\n(CVE-2017-6346)\n\nAndrey Konovalov discovered that the IP layer in the Linux kernel made\nimproper assumptions about internal data layout when performing checksums.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2017-6347)\n\nDmitry Vyukov discovered race conditions in the Infrared (IrDA) subsystem\nin the Linux kernel. A local attacker could use this to cause a denial of\nservice (deadlock). (CVE-2017-6348)\n\nDmitry Vyukov discovered that the generic SCSI (sg) subsystem in the Linux\nkernel contained a stack-based buffer overflow. A local attacker with\naccess to an sg device could use this to cause a denial of service (system\ncrash) or possibly execute arbitrary code. (CVE-2017-7187)\n\nIt was discovered that a NULL pointer dereference existed in the Direct\nRendering Manager (DRM) driver for VMWare devices in the Linux kernel. A\nlocal attacker could use this to cause a denial of service (system crash).\n(CVE-2017-7261)\n\nIt was discovered that the USB Cypress HID drivers for the Linux kernel did\nnot properly validate reported information from the device. An attacker\nwith physical access could use this to expose sensitive information (kernel\nmemory). (CVE-2017-7273)\n\nEric Biggers discovered a memory leak in the keyring implementation in the\nLinux kernel. A local attacker could use this to cause a denial of service\n(memory consumption). (CVE-2017-7472)\n\nIt was discovered that an information leak existed in the set_mempolicy and\nmbind compat syscalls in the Linux kernel. A local attacker could use this\nto expose sensitive information (kernel memory). (CVE-2017-7616)\n\nSabrina Dubroca discovered that the asynchronous cryptographic hash (ahash)\nimplementation in the Linux kernel did not properly handle a full request\nqueue. A local attacker could use this to cause a denial of service\n(infinite recursion). (CVE-2017-7618)\n\nTuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server\nimplementations in the Linux kernel did not properly handle certain long\nRPC replies. A remote attacker could use this to cause a denial of service\n(system crash). (CVE-2017-7645)\n\nTommi Rantala and Brad Spengler discovered that the memory manager in the\nLinux kernel did not properly enforce the CONFIG_STRICT_DEVMEM protection\nmechanism. A local attacker with access to /dev/mem could use this to\nexpose sensitive information or possibly execute arbitrary code.\n(CVE-2017-7889)\n\nTuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server\nimplementations in the Linux kernel did not properly check for the end of\nbuffer. A remote attacker could use this to craft requests that cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2017-7895)\n\nIt was discovered that an integer underflow existed in the Edgeport USB\nSerial Converter device driver of the Linux kernel. An attacker with\nphysical access could use this to expose sensitive information (kernel\nmemory). (CVE-2017-8924)\n\nIt was discovered that the USB ZyXEL omni.net LCD PLUS driver in the Linux\nkernel did not properly perform reference counting. A local attacker could\nuse this to cause a denial of service (tty exhaustion). (CVE-2017-8925)\n\nJann Horn discovered that bpf in Linux kernel does not restrict the output\nof the print_bpf_insn function. A local attacker could use this to obtain\nsensitive address information. (CVE-2017-9150)\n","status":"published","published":"2017-07-21T09:59:15Z","modified":"2026-06-03T14:04:19.16359445Z","updated_at":"2026-11-02T16:58:13.496563Z"},{"id":"USN-3754-1","title":"linux vulnerabilities","description":"Ralf Spenneberg discovered that the ext4 implementation in the Linux kernel\ndid not properly validate meta block groups. An attacker with physical\naccess could use this to specially craft an ext4 image that causes a denial\nof service (system crash). (CVE-2016-10208)\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 buffer overflow existed in the ACPI table parsing\nimplementation in the Linux kernel. A local attacker could use this to\nconstruct a malicious ACPI table that, when loaded, caused a denial of\nservice (system crash) or possibly execute arbitrary code.\n(CVE-2017-11473)\n\nIt was discovered that the generic SCSI driver in the Linux kernel did not\nproperly initialize data returned to user space in some situations. A local\nattacker could use this to expose sensitive information (kernel memory).\n(CVE-2017-14991)\n\nIt was discovered that a race condition existed in the packet fanout\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-2017-15649)\n\nAndrey Konovalov discovered that the Ultra Wide Band driver in the Linux\nkernel did not properly check for an error condition. A physically\nproximate attacker could use this to cause a denial of service (system\ncrash) or possibly execute arbitrary code. (CVE-2017-16526)\n\nAndrey Konovalov discovered that the ALSA subsystem in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2017-16527)\n\nAndrey Konovalov discovered that the ALSA subsystem in the Linux kernel did\nnot properly validate USB audio buffer descriptors. A physically proximate\nattacker could use this cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2017-16529)\n\nAndrey Konovalov discovered that the USB subsystem in the Linux kernel did\nnot properly validate USB interface association descriptors. A physically\nproximate attacker could use this to cause a denial of service (system\ncrash). (CVE-2017-16531)\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 USB subsystem in the Linux kernel did\nnot properly validate USB HID descriptors. A physically proximate attacker\ncould use this to cause a denial of service (system crash).\n(CVE-2017-16533)\n\nAndrey Konovalov discovered that the USB subsystem in the Linux kernel did\nnot properly validate USB BOS metadata. A physically proximate attacker\ncould use this to cause a denial of service (system crash).\n(CVE-2017-16535)\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\nIt was discovered that the DM04/QQBOX USB driver in the Linux kernel did\nnot properly handle device attachment and warm-start. A physically\nproximate attacker could use this to cause a denial of service (system\ncrash) or possibly execute arbitrary code. (CVE-2017-16538)\n\nAndrey Konovalov discovered an out-of-bounds read in the GTCO digitizer USB\ndriver for the Linux kernel. A physically proximate attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2017-16643)\n\nAndrey Konovalov discovered that the video4linux driver for Hauppauge HD\nPVR USB devices in the Linux kernel did not properly handle some error\nconditions. A physically proximate attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2017-16644)\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 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 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\nIt was discovered that an integer overflow existed in the perf subsystem of\nthe Linux kernel. A local attacker could use this to cause a denial of\nservice (system crash). (CVE-2017-18255)\n\nIt was discovered that the keyring subsystem in the Linux kernel did not\nproperly prevent a user from creating keyrings for other users. A local\nattacker could use this cause a denial of service or expose sensitive\ninformation. (CVE-2017-18270)\n\nAndy Lutomirski and Willy Tarreau discovered that the KVM implementation in\nthe Linux kernel did not properly emulate instructions on the SS segment\nregister. A local attacker in a guest virtual machine could use this to\ncause a denial of service (guest OS crash) or possibly gain administrative\nprivileges in the guest OS. (CVE-2017-2583)\n\nDmitry Vyukov discovered that the KVM implementation in the Linux kernel\nimproperly emulated certain instructions. A local attacker could use this\nto obtain sensitive information (kernel memory). (CVE-2017-2584)\n\nIt was discovered that the KLSI KL5KUSB105 serial-to-USB device driver in\nthe Linux kernel did not properly initialize memory related to logging. A\nlocal attacker could use this to expose sensitive information (kernel\nmemory). (CVE-2017-5549)\n\nAndrey Konovalov discovered an out-of-bounds access in the IPv6 Generic\nRouting Encapsulation (GRE) tunneling implementation in the Linux kernel.\nAn attacker could use this to possibly expose sensitive information.\n(CVE-2017-5897)\n\nAndrey Konovalov discovered that the LLC subsytem in the Linux kernel did\nnot properly set up a destructor in certain situations. A local attacker\ncould use this to cause a denial of service (system crash). (CVE-2017-6345)\n\nDmitry Vyukov discovered race conditions in the Infrared (IrDA) subsystem\nin the Linux kernel. A local attacker could use this to cause a denial of\nservice (deadlock). (CVE-2017-6348)\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\nTuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server\nimplementations in the Linux kernel did not properly handle certain long\nRPC replies. A remote attacker could use this to cause a denial of service\n(system crash). (CVE-2017-7645)\n\nPengfei Wang discovered that a race condition existed in the NXP SAA7164 TV\nDecoder driver for the Linux kernel. A local attacker could use this to\ncause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2017-8831)\n\nPengfei Wang discovered that the Turtle Beach MultiSound audio device\ndriver in the Linux kernel contained race conditions when fetching from the\nring-buffer. A local attacker could use this to cause a denial of service\n(infinite loop). (CVE-2017-9984, CVE-2017-9985)\n\nIt was discovered that the wait4() system call in the Linux kernel did not\nproperly validate its arguments in some situations. A local attacker could\npossibly use this to cause a denial of service. (CVE-2018-10087)\n\nIt was discovered that the kill() system call implementation in the Linux\nkernel did not properly validate its arguments in some situations. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2018-10124)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly validate meta-data information. An attacker could\nuse this to construct a malicious xfs image that, when mounted, could cause\na denial of service (system crash). (CVE-2018-10323)\n\nZhong Jiang discovered that a use-after-free vulnerability existed in the\nNUMA memory policy 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-2018-10675)\n\nWen Xu discovered that a buffer overflow existed in the ext4 filesystem\nimplementation in the Linux kernel. An attacker could use this to construct\na malicious ext4 image that, when mounted, could cause a denial of service\n(system crash) or possibly execute arbitrary code. (CVE-2018-10877)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly keep meta-data information consistent in some\nsituations. An attacker could use this to construct a malicious ext4 image\nthat, when mounted, could cause a denial of service (system crash).\n(CVE-2018-10881)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly handle corrupted meta data in some situations. An\nattacker could use this to specially craft an ext4 filesystem that caused\na denial of service (system crash) when mounted. (CVE-2018-1092)\n\nWen Xu discovered that the ext4 filesystem implementation in the Linux\nkernel did not properly handle corrupted meta data in some situations. An\nattacker could use this to specially craft an ext4 filesystem that caused a\ndenial of service (system crash) when mounted. (CVE-2018-1093)\n\nIt was discovered that the cdrom driver in the Linux kernel contained an\nincorrect bounds check. A local attacker could use this to expose sensitive\ninformation (kernel memory). (CVE-2018-10940)\n\nShankara Pailoor discovered that the JFS filesystem implementation in the\nLinux kernel contained a buffer overflow when handling extended attributes.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2018-12233)\n\nWen Xu discovered that the XFS filesystem implementation in the Linux\nkernel did not properly handle an error condition with a corrupted xfs\nimage. An attacker could use this to construct a malicious xfs image that,\nwhen mounted, could cause a denial of service (system crash).\n(CVE-2018-13094)\n\nIt was discovered that the Linux kernel did not properly handle setgid file\ncreation when performed by a non-member of the group. A local attacker\ncould use this to gain elevated privileges. (CVE-2018-13405)\n\nSilvio Cesare discovered that the generic VESA frame buffer driver in the\nLinux kernel contained an integer overflow. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2018-13406)\n\nDaniel Jiang discovered that a race condition existed in the ipv4 ping\nsocket implementation in the Linux kernel. A local privileged attacker\ncould use this to cause a denial of service (system crash). (CVE-2017-2671)\n\nIt was discovered that an information leak existed in the generic SCSI\ndriver in the Linux kernel. A local attacker could use this to expose\nsensitive information (kernel memory). (CVE-2018-1000204)\n\nIt was discovered that a memory leak existed in the Serial Attached SCSI\n(SAS) implementation in the Linux kernel. A physically proximate attacker\ncould use this to cause a denial of service (memory exhaustion).\n(CVE-2018-10021)\n","status":"published","published":"2018-08-24T00:38:00Z","modified":"2026-06-03T14:04:16.281658586Z","updated_at":"2026-11-02T16:58:14.019824Z"}]}}