{"id":"CVE-2017-14991","aliases":["DEBIAN-CVE-2017-14991","EUVD-2017-6467","GHSA-r79m-gm95-v29g","MGASA-2017-0381","MGASA-2017-0383","MGASA-2017-0384","MGASA-2017-0386","MGASA-2017-0387","MGASA-2017-0388","UBUNTU-CVE-2017-14991","USN-3469-1","USN-3469-2","USN-3754-1"],"status":"published","title":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users...","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","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-08","score":0.00414,"percentile":0.35931,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-200"],"published":"2017-10-03T00:00:00Z","modified":"2026-09-01T20:02:52Z","fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["4.13.4-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["4.13.4-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["4.13.4-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-98.121~14.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux","fixed_in":["4.4.0-98.121"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","fixed_in":["4.4.0-1039.48"],"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-gcp","fixed_in":["4.13.0-1002.5"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-gke","fixed_in":["4.4.0-1033.33"],"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-1009.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","fixed_in":["4.4.0-1076.84"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","fixed_in":["4.4.0-1078.83"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.4-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.4-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.4-1"}]}]},{"source":"osv","ecosystem":"Mageia:6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.56-1.mga6"}]}],"bundled":10},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-userspace-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.56-1.mga6"}]}],"bundled":10},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-vboxadditions","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.26-6.mga6"}]}],"bundled":10},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.26-6.mga6"}]}],"bundled":10},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.12-46.mga6"}]}],"bundled":10},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.56-1.mga6"}]}],"bundled":10},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-tmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.56-1.mga6"}]}],"bundled":10},{"source":"osv","ecosystem":"Mageia:5","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.92-1.mga5"}]}],"bundled":7},{"source":"osv","ecosystem":"Mageia:5","package":"kernel-userspace-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.92-1.mga5"}]}],"bundled":7},{"source":"osv","ecosystem":"Mageia:5","package":"kmod-vboxadditions","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.26-4.mga5"}]}],"bundled":7},{"source":"osv","ecosystem":"Mageia:5","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.26-4.mga5"}]}],"bundled":7},{"source":"osv","ecosystem":"Mageia:5","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10-48.mga5"}]}],"bundled":7},{"source":"osv","ecosystem":"Mageia:5","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.92-1.mga5"}]}],"bundled":7},{"source":"osv","ecosystem":"Mageia:5","package":"kernel-tmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.92-1.mga5"}]}],"bundled":7},{"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-98.121~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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-98.121"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1039.48"}]}],"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"]},{"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-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.0-1002.5"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1033.33"}]}],"versions":["4.4.0-1003.3","4.4.0-1005.6","4.4.0-1006.6","4.4.0-1008.8","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1012.12","4.4.0-1013.13","4.4.0-1014.14","4.4.0-1016.16","4.4.0-1018.18","4.4.0-1022.22","4.4.0-1024.24","4.4.0-1026.26","4.4.0-1027.27","4.4.0-1028.28","4.4.0-1031.31","4.4.0-1032.32"]},{"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-1009.14"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1076.84"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1078.83"}]}],"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"]},{"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-98.121"}]}],"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"],"bundled":12},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1039.48"}]}],"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"],"bundled":12},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1033.33"}]}],"versions":["4.4.0-1003.3","4.4.0-1005.6","4.4.0-1006.6","4.4.0-1008.8","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1012.12","4.4.0-1013.13","4.4.0-1014.14","4.4.0-1016.16","4.4.0-1018.18","4.4.0-1022.22","4.4.0-1024.24","4.4.0-1026.26","4.4.0-1027.27","4.4.0-1028.28","4.4.0-1031.31","4.4.0-1032.32"],"bundled":12},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1009.14"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13"],"bundled":12},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1076.84"}]}],"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"],"bundled":12},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-snapdragon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1078.83"}]}],"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"],"bundled":12},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-98.121~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"],"bundled":12},{"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.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.13.4","tags":["x_refsource_CONFIRM","x_transferred","Release Notes","Vendor Advisory","advisory"]},{"url":"https://github.com/torvalds/linux/commit/3e0097499839e0fe3af380410eababe5a47c4cf9","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix"]},{"url":"http://www.securityfocus.com/bid/101187","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"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=3e0097499839e0fe3af380410eababe5a47c4cf9","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-14991"},{"url":"https://usn.ubuntu.com/3754-1"},{"url":"https://github.com/advisories/GHSA-r79m-gm95-v29g"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-14991","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2017-0381.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=21849","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.51","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.52","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.53","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.54","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.55","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.56","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2017-0383.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=21850","tags":["report"]},{"url":"https://advisories.mageia.org/MGASA-2017-0384.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=21851","tags":["report"]},{"url":"https://advisories.mageia.org/MGASA-2017-0386.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=21852","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.89","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.90","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.91","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.92","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2017-0387.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=21853","tags":["report"]},{"url":"https://advisories.mageia.org/MGASA-2017-0388.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=21854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14991","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3469-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3469-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3754-1","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-14991","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-10911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-10208","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-2671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8831","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-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-14991","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","status":"published","published":"2017-10-03T07:00:00Z","modified":"2024-08-05T19:42:22.551Z","updated_at":"2026-11-02T14:33:12.267141Z"}],"euvd":[{"id":"EUVD-2017-6467","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","status":"published","published":"2017-10-03T07:00:00Z","modified":"2024-08-05T19:42:22Z","updated_at":"2026-11-03T02:23:15.298105Z"}],"ghsa":[{"id":"GHSA-r79m-gm95-v29g","title":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users...","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","status":"published","published":"2022-05-14T03:05:21Z","modified":"2025-04-20T03:47:20Z","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-200"],"updated_at":"2026-11-02T15:01:53.867735Z"}],"nvd":[{"id":"CVE-2017-14991","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","status":"published","published":"2017-10-04T01:29:03.183Z","modified":"2026-06-17T01:07:06.59Z","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-200"],"updated_at":"2026-11-02T14:04:01.734197Z"}],"osv":[{"id":"CVE-2017-14991","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","status":"published","published":"2017-10-04T01:29:03.183Z","modified":"2026-04-16T06:24:54.728021865Z","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:04.572713Z"},{"id":"DEBIAN-CVE-2017-14991","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","status":"published","published":"2017-10-04T01:29:03.183Z","modified":"2026-09-01T20:02:52.558331262Z","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:28.801885Z"},{"id":"UBUNTU-CVE-2017-14991","description":"The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4 allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0.","status":"published","published":"2017-10-03T00:00:00Z","modified":"2026-04-22T11:17:02.60366Z","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:14.563448Z"},{"id":"MGASA-2017-0381","title":"Updated kernel packages fix security vulnerabilities","description":"This kernel update is based on upstream 4.9.56 and fixes at least the\nfollowing security issues:\n\nA flaw was found in the way the Linux KVM module processed the trap flag(TF)\nbit in EFLAGS during emulation of the syscall instruction, which leads to a\ndebug exception(#DB) being raised in the guest stack. A user/process inside\na guest could use this flaw to potentially escalate their privileges inside\nthe guest (CVE-2017-7518).\n\nA kernel data leak due to an out-of-bound read was found in the Linux kernel\nin inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() functions\npresent since version 4.7-rc1 through version 4.13. A data leak happens when\nthese functions fill in sockaddr data structures used to export socket's\ndiagnostic information. As a result, up to 100 bytes of the slab data could\nbe leaked to a userspace (CVE-2017-7558).\n\nA security flaw was discovered in nl80211_set_rekey_data() function in the\nLinux kernel since v3.1-rc1 through v4.13. This function does not check\nwhether the required attributes are present in a netlink request. This\nrequest can be issued by a user with CAP_NET_ADMIN privilege and may result\nin NULL dereference and a system crash (CVE-2017-12153).\n\nLinux kernel built with the KVM visualization support (CONFIG_KVM), with\nnested visualization (nVMX) feature enabled (nested=1), is vulnerable to a\ncrash due to disabled external interrupts. As L2 guest could acce s (r/w)\nhardware CR8 register of the host(L0). In a nested visualization setup,\nL2 guest user could use this flaw to potentially crash the host(L0)\nresulting in DoS (CVE-2017-12154).\n\nThe tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel before\n4.12 allows local users to cause a denial of service (__tcp_select_window\ndivide-by-zero error and system crash) by triggering a disconnect within a\ncertain tcp_recvmsg code path (CVE-2017-14106).\n\nThe atyfb_ioctl function in drivers/video/fbdev/aty/atyfb_base.c in the\nLinux kernel through 4.12.10 does not initialize a certain data structure,\nwhich allows local users to obtain sensitive information from kernel stack\nmemory by reading locations associated with padding bytes (CVE-2017-14156).\n\nIt was found that the iscsi_if_rx() function in scsi_transport_iscsi.c in\nthe Linux kernel since v2.6.24-rc1 through 4.13.2 allows local users to\ncause a denial of service (a system panic) by making a number of certain\nsyscalls by leveraging incorrect length validation in the kernel code\n(CVE-2017-14489).\n\nThe sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4\nallows local users to obtain sensitive information from uninitialized kernel\nheap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0\n(CVE-2017-14991).\n\nThe tpacket_rcv() function in 'net/packet/af_packet.c' file in the Linux\nkernel before 4.13 mishandles vnet headers, which might allow local users\nto cause a denial of service (buffer overflow, and disk and memory\ncorruption) or possibly have unspecified other impact via crafted system\ncalls (CVE-2017-14497).\n\nA reachable assertion failure flaw was found in the Linux kernel built with\nKVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature\n(CONFIG_VFIO) enabled. This failure could occur if a malicious guest device\nsent a virtual interrupt (guest IRQ) with a larger (\u003e1024) index value\n(CVE-2017-1000252).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n","status":"published","published":"2017-10-19T22:05:51Z","modified":"2026-04-16T06:25:34.137770662Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2017-0383","title":"Updated kernel-linus packages fix security vulnerabilities","description":"This kernel-linus update is based on upstream 4.9.56 and fixes at least the\nfollowing security issues:\n\nA flaw was found in the way the Linux KVM module processed the trap flag(TF)\nbit in EFLAGS during emulation of the syscall instruction, which leads to a\ndebug exception(#DB) being raised in the guest stack. A user/process inside\na guest could use this flaw to potentially escalate their privileges inside\nthe guest (CVE-2017-7518).\n\nA kernel data leak due to an out-of-bound read was found in the Linux kernel\nin inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() functions\npresent since version 4.7-rc1 through version 4.13. A data leak happens when\nthese functions fill in sockaddr data structures used to export socket's\ndiagnostic information. As a result, up to 100 bytes of the slab data could\nbe leaked to a userspace (CVE-2017-7558).\n\nA security flaw was discovered in nl80211_set_rekey_data() function in the\nLinux kernel since v3.1-rc1 through v4.13. This function does not check\nwhether the required attributes are present in a netlink request. This\nrequest can be issued by a user with CAP_NET_ADMIN privilege and may result\nin NULL dereference and a system crash (CVE-2017-12153).\n\nLinux kernel built with the KVM visualization support (CONFIG_KVM), with\nnested visualization (nVMX) feature enabled (nested=1), is vulnerable to a\ncrash due to disabled external interrupts. As L2 guest could acce s (r/w)\nhardware CR8 register of the host(L0). In a nested visualization setup,\nL2 guest user could use this flaw to potentially crash the host(L0)\nresulting in DoS (CVE-2017-12154).\n\nThe tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel before\n4.12 allows local users to cause a denial of service (__tcp_select_window\ndivide-by-zero error and system crash) by triggering a disconnect within a\ncertain tcp_recvmsg code path (CVE-2017-14106).\n\nThe atyfb_ioctl function in drivers/video/fbdev/aty/atyfb_base.c in the\nLinux kernel through 4.12.10 does not initialize a certain data structure,\nwhich allows local users to obtain sensitive information from kernel stack\nmemory by reading locations associated with padding bytes (CVE-2017-14156).\n\nIt was found that the iscsi_if_rx() function in scsi_transport_iscsi.c in\nthe Linux kernel since v2.6.24-rc1 through 4.13.2 allows local users to\ncause a denial of service (a system panic) by making a number of certain\nsyscalls by leveraging incorrect length validation in the kernel code\n(CVE-2017-14489).\n\nThe sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4\nallows local users to obtain sensitive information from uninitialized kernel\nheap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0\n(CVE-2017-14991).\n\nThe tpacket_rcv() function in 'net/packet/af_packet.c' file in the Linux\nkernel before 4.13 mishandles vnet headers, which might allow local users\nto cause a denial of service (buffer overflow, and disk and memory\ncorruption) or possibly have unspecified other impact via crafted system\ncalls (CVE-2017-14497).\n\nA reachable assertion failure flaw was found in the Linux kernel built with\nKVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature\n(CONFIG_VFIO) enabled. This failure could occur if a malicious guest device\nsent a virtual interrupt (guest IRQ) with a larger (\u003e1024) index value\n(CVE-2017-1000252).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n","status":"published","published":"2017-10-24T05:50:58Z","modified":"2026-04-16T04:44:03.629827148Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2017-0384","title":"Updated kernel-tmb packages fix security vulnerabilities","description":"This kernel-tmb update is based on upstream 4.9.56 and fixes at least the\nfollowing security issues:\n\nA flaw was found in the way the Linux KVM module processed the trap flag(TF)\nbit in EFLAGS during emulation of the syscall instruction, which leads to a\ndebug exception(#DB) being raised in the guest stack. A user/process inside\na guest could use this flaw to potentially escalate their privileges inside\nthe guest (CVE-2017-7518).\n\nA kernel data leak due to an out-of-bound read was found in the Linux kernel\nin inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() functions\npresent since version 4.7-rc1 through version 4.13. A data leak happens when\nthese functions fill in sockaddr data structures used to export socket's\ndiagnostic information. As a result, up to 100 bytes of the slab data could\nbe leaked to a userspace (CVE-2017-7558).\n\nA security flaw was discovered in nl80211_set_rekey_data() function in the\nLinux kernel since v3.1-rc1 through v4.13. This function does not check\nwhether the required attributes are present in a netlink request. This\nrequest can be issued by a user with CAP_NET_ADMIN privilege and may result\nin NULL dereference and a system crash (CVE-2017-12153).\n\nLinux kernel built with the KVM visualization support (CONFIG_KVM), with\nnested visualization (nVMX) feature enabled (nested=1), is vulnerable to a\ncrash due to disabled external interrupts. As L2 guest could acce s (r/w)\nhardware CR8 register of the host(L0). In a nested visualization setup,\nL2 guest user could use this flaw to potentially crash the host(L0)\nresulting in DoS (CVE-2017-12154).\n\nThe tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel before\n4.12 allows local users to cause a denial of service (__tcp_select_window\ndivide-by-zero error and system crash) by triggering a disconnect within a\ncertain tcp_recvmsg code path (CVE-2017-14106).\n\nThe atyfb_ioctl function in drivers/video/fbdev/aty/atyfb_base.c in the\nLinux kernel through 4.12.10 does not initialize a certain data structure,\nwhich allows local users to obtain sensitive information from kernel stack\nmemory by reading locations associated with padding bytes (CVE-2017-14156).\n\nIt was found that the iscsi_if_rx() function in scsi_transport_iscsi.c in\nthe Linux kernel since v2.6.24-rc1 through 4.13.2 allows local users to\ncause a denial of service (a system panic) by making a number of certain\nsyscalls by leveraging incorrect length validation in the kernel code\n(CVE-2017-14489).\n\nThe sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4\nallows local users to obtain sensitive information from uninitialized kernel\nheap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0\n(CVE-2017-14991).\n\nThe tpacket_rcv() function in 'net/packet/af_packet.c' file in the Linux\nkernel before 4.13 mishandles vnet headers, which might allow local users\nto cause a denial of service (buffer overflow, and disk and memory\ncorruption) or possibly have unspecified other impact via crafted system\ncalls (CVE-2017-14497).\n\nA reachable assertion failure flaw was found in the Linux kernel built with\nKVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature\n(CONFIG_VFIO) enabled. This failure could occur if a malicious guest device\nsent a virtual interrupt (guest IRQ) with a larger (\u003e1024) index value\n(CVE-2017-1000252).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n","status":"published","published":"2017-10-24T05:50:58Z","modified":"2026-04-16T06:22:32.602926837Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2017-0386","title":"Updated kernel packages fix security vulnerabilities","description":"This kernel update is based on upstream 4.4.92 and fixes at least the\nfollowing security issues:\n\nA security flaw was discovered in nl80211_set_rekey_data() function in the\nLinux kernel since v3.1-rc1 through v4.13. This function does not check\nwhether the required attributes are present in a netlink request. This\nrequest can be issued by a user with CAP_NET_ADMIN privilege and may result\nin NULL dereference and a system crash (CVE-2017-12153).\n\nLinux kernel built with the KVM visualization support (CONFIG_KVM), with\nnested visualization (nVMX) feature enabled (nested=1), is vulnerable to a\ncrash due to disabled external interrupts. As L2 guest could acce s (r/w)\nhardware CR8 register of the host(L0). In a nested visualization setup,\nL2 guest user could use this flaw to potentially crash the host(L0)\nresulting in DoS (CVE-2017-12154).\n\nThe tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel before\n4.12 allows local users to cause a denial of service (__tcp_select_window\ndivide-by-zero error and system crash) by triggering a disconnect within a\ncertain tcp_recvmsg code path (CVE-2017-14106).\n\nThe atyfb_ioctl function in drivers/video/fbdev/aty/atyfb_base.c in the\nLinux kernel through 4.12.10 does not initialize a certain data structure,\nwhich allows local users to obtain sensitive information from kernel stack\nmemory by reading locations associated with padding bytes (CVE-2017-14156).\n\nIt was found that the iscsi_if_rx() function in scsi_transport_iscsi.c in\nthe Linux kernel since v2.6.24-rc1 through 4.13.2 allows local users to\ncause a denial of service (a system panic) by making a number of certain\nsyscalls by leveraging incorrect length validation in the kernel code\n(CVE-2017-14489).\n\nThe sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4\nallows local users to obtain sensitive information from uninitialized kernel\nheap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0\n(CVE-2017-14991).\n\nA reachable assertion failure flaw was found in the Linux kernel built with\nKVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature\n(CONFIG_VFIO) enabled. This failure could occur if a malicious guest device\nsent a virtual interrupt (guest IRQ) with a larger (\u003e1024) index value\n(CVE-2017-1000252).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n","status":"published","published":"2017-10-24T20:09:45Z","modified":"2026-04-16T04:42:49.775794717Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2017-0387","title":"Updated kernel-linus packages fix security vulnerabilities","description":"This kernel-linus update is based on upstream 4.4.92 and fixes at least the\nfollowing security issues:\n\nA security flaw was discovered in nl80211_set_rekey_data() function in the\nLinux kernel since v3.1-rc1 through v4.13. This function does not check\nwhether the required attributes are present in a netlink request. This\nrequest can be issued by a user with CAP_NET_ADMIN privilege and may result\nin NULL dereference and a system crash (CVE-2017-12153).\n\nLinux kernel built with the KVM visualization support (CONFIG_KVM), with\nnested visualization (nVMX) feature enabled (nested=1), is vulnerable to a\ncrash due to disabled external interrupts. As L2 guest could acce s (r/w)\nhardware CR8 register of the host(L0). In a nested visualization setup,\nL2 guest user could use this flaw to potentially crash the host(L0)\nresulting in DoS (CVE-2017-12154).\n\nThe tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel before\n4.12 allows local users to cause a denial of service (__tcp_select_window\ndivide-by-zero error and system crash) by triggering a disconnect within a\ncertain tcp_recvmsg code path (CVE-2017-14106).\n\nThe atyfb_ioctl function in drivers/video/fbdev/aty/atyfb_base.c in the\nLinux kernel through 4.12.10 does not initialize a certain data structure,\nwhich allows local users to obtain sensitive information from kernel stack\nmemory by reading locations associated with padding bytes (CVE-2017-14156).\n\nIt was found that the iscsi_if_rx() function in scsi_transport_iscsi.c in\nthe Linux kernel since v2.6.24-rc1 through 4.13.2 allows local users to\ncause a denial of service (a system panic) by making a number of certain\nsyscalls by leveraging incorrect length validation in the kernel code\n(CVE-2017-14489).\n\nThe sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4\nallows local users to obtain sensitive information from uninitialized kernel\nheap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0\n(CVE-2017-14991).\n\nA reachable assertion failure flaw was found in the Linux kernel built with\nKVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature\n(CONFIG_VFIO) enabled. This failure could occur if a malicious guest device\nsent a virtual interrupt (guest IRQ) with a larger (\u003e1024) index value\n(CVE-2017-1000252).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n","status":"published","published":"2017-10-24T20:09:45Z","modified":"2026-04-16T06:24:02.918339408Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2017-0388","title":"Updated kernel-tmb packages fix security vulnerabilities","description":"This kernel-tmb update is based on upstream 4.4.92 and fixes at least the\nfollowing security issues:\n\nA security flaw was discovered in nl80211_set_rekey_data() function in the\nLinux kernel since v3.1-rc1 through v4.13. This function does not check\nwhether the required attributes are present in a netlink request. This\nrequest can be issued by a user with CAP_NET_ADMIN privilege and may result\nin NULL dereference and a system crash (CVE-2017-12153).\n\nLinux kernel built with the KVM visualization support (CONFIG_KVM), with\nnested visualization (nVMX) feature enabled (nested=1), is vulnerable to a\ncrash due to disabled external interrupts. As L2 guest could acce s (r/w)\nhardware CR8 register of the host(L0). In a nested visualization setup,\nL2 guest user could use this flaw to potentially crash the host(L0)\nresulting in DoS (CVE-2017-12154).\n\nThe tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel before\n4.12 allows local users to cause a denial of service (__tcp_select_window\ndivide-by-zero error and system crash) by triggering a disconnect within a\ncertain tcp_recvmsg code path (CVE-2017-14106).\n\nThe atyfb_ioctl function in drivers/video/fbdev/aty/atyfb_base.c in the\nLinux kernel through 4.12.10 does not initialize a certain data structure,\nwhich allows local users to obtain sensitive information from kernel stack\nmemory by reading locations associated with padding bytes (CVE-2017-14156).\n\nIt was found that the iscsi_if_rx() function in scsi_transport_iscsi.c in\nthe Linux kernel since v2.6.24-rc1 through 4.13.2 allows local users to\ncause a denial of service (a system panic) by making a number of certain\nsyscalls by leveraging incorrect length validation in the kernel code\n(CVE-2017-14489).\n\nThe sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4\nallows local users to obtain sensitive information from uninitialized kernel\nheap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0\n(CVE-2017-14991).\n\nA reachable assertion failure flaw was found in the Linux kernel built with\nKVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature\n(CONFIG_VFIO) enabled. This failure could occur if a malicious guest device\nsent a virtual interrupt (guest IRQ) with a larger (\u003e1024) index value\n(CVE-2017-1000252).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n","status":"published","published":"2017-10-24T20:09:45Z","modified":"2026-04-16T06:22:52.069951847Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"USN-3469-1","title":"linux, linux-aws, linux-gke, linux-kvm, linux-raspi2, linux-snapdragon vulnerabilities","description":"Anthony Perard discovered that the Xen virtual block driver did not\nproperly initialize some data structures before passing them to user space.\nA local attacker in a guest VM could use this to expose sensitive\ninformation from the host OS or other guest VMs. (CVE-2017-10911)\n\nBo Zhang discovered that the netlink wireless configuration interface in\nthe Linux kernel did not properly validate attributes when handling certain\nrequests. A local attacker with the CAP_NET_ADMIN could use this to cause a\ndenial of service (system crash). (CVE-2017-12153)\n\nIt was discovered that the nested KVM implementation in the Linux\nkernel in some situations did not properly prevent second level guests\nfrom reading and writing the hardware CR8 register. A local attacker\nin a guest could use this to cause a denial of service (system crash).\n\nIt was discovered that the key management subsystem in the Linux kernel\ndid not properly restrict key reads on negatively instantiated keys. A\nlocal attacker could use this to cause a denial of service (system crash).\n(CVE-2017-12192)\n\nIt was discovered that an integer overflow existed in the sysfs interface\nfor the QLogic 24xx+ series SCSI driver in the Linux kernel. A local\nprivileged attacker could use this to cause a denial of service (system\ncrash). (CVE-2017-14051)\n\nIt was discovered that the ATI Radeon framebuffer driver in the Linux\nkernel did not properly initialize a data structure returned to user space.\nA local attacker could use this to expose sensitive information (kernel\nmemory). (CVE-2017-14156)\n\nDave Chinner discovered that the XFS filesystem did not enforce that the\nrealtime inode flag was settable only on filesystems on a realtime device.\nA local attacker could use this to cause a denial of service (system\ncrash). (CVE-2017-14340)\n\nChunYu Wang discovered that the iSCSI transport implementation in the Linux\nkernel did not properly validate data structures. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2017-14489)\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\nDmitry Vyukov discovered that the Floating Point Unit (fpu) subsystem in\nthe Linux kernel did not properly handle attempts to set reserved bits in a\ntask's extended state (xstate) area. A local attacker could use this to\ncause a denial of service (system crash). (CVE-2017-15537)\n\nPengfei Wang discovered that the Turtle Beach MultiSound audio device\ndriver in the Linux kernel contained race conditions when fetching\nfrom the ring-buffer. A local attacker could use this to cause a\ndenial of service (infinite loop). (CVE-2017-9984, CVE-2017-9985)\n","status":"published","published":"2017-10-31T10:25:13Z","modified":"2026-04-22T09:39:43.553459Z","updated_at":"2026-11-02T16:58:13.496563Z"},{"id":"USN-3469-2","title":"linux-lts-xenial vulnerabilities","description":"USN-3469-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\nAnthony Perard discovered that the Xen virtual block driver did not\nproperly initialize some data structures before passing them to user space.\nA local attacker in a guest VM could use this to expose sensitive\ninformation from the host OS or other guest VMs. (CVE-2017-10911)\n\nBo Zhang discovered that the netlink wireless configuration interface in\nthe Linux kernel did not properly validate attributes when handling certain\nrequests. A local attacker with the CAP_NET_ADMIN could use this to cause a\ndenial of service (system crash). (CVE-2017-12153)\n\nIt was discovered that the nested KVM implementation in the Linux\nkernel in some situations did not properly prevent second level guests\nfrom reading and writing the hardware CR8 register. A local attacker\nin a guest could use this to cause a denial of service (system crash).\n\nIt was discovered that the key management subsystem in the Linux kernel\ndid not properly restrict key reads on negatively instantiated keys. A\nlocal attacker could use this to cause a denial of service (system crash).\n(CVE-2017-12192)\n\nIt was discovered that an integer overflow existed in the sysfs interface\nfor the QLogic 24xx+ series SCSI driver in the Linux kernel. A local\nprivileged attacker could use this to cause a denial of service (system\ncrash). (CVE-2017-14051)\n\nIt was discovered that the ATI Radeon framebuffer driver in the Linux\nkernel did not properly initialize a data structure returned to user space.\nA local attacker could use this to expose sensitive information (kernel\nmemory). (CVE-2017-14156)\n\nDave Chinner discovered that the XFS filesystem did not enforce that the\nrealtime inode flag was settable only on filesystems on a realtime device.\nA local attacker could use this to cause a denial of service (system\ncrash). (CVE-2017-14340)\n\nChunYu Wang discovered that the iSCSI transport implementation in the Linux\nkernel did not properly validate data structures. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2017-14489)\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\nDmitry Vyukov discovered that the Floating Point Unit (fpu) subsystem in\nthe Linux kernel did not properly handle attempts to set reserved bits in a\ntask's extended state (xstate) area. A local attacker could use this to\ncause a denial of service (system crash). (CVE-2017-15537)\n\nPengfei Wang discovered that the Turtle Beach MultiSound audio device\ndriver in the Linux kernel contained race conditions when fetching\nfrom the ring-buffer. A local attacker could use this to cause a\ndenial of service (infinite loop). (CVE-2017-9984, CVE-2017-9985)\n","status":"published","published":"2017-10-31T10:29:27Z","modified":"2026-02-10T04:41:14Z","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"}]}}