{"id":"CVE-2024-35988","aliases":["BELL-CVE-2024-35988","DEBIAN-CVE-2024-35988","DLA-3842-1","EUVD-2024-35706","GHSA-cqwh-fpfr-9p4j","MGASA-2024-0263","MGASA-2024-0266","OESA-2024-1838","OESA-2024-1839","UBUNTU-CVE-2024-35988","USN-6898-1","USN-6898-2","USN-6898-3","USN-6898-4","USN-6917-1","USN-6919-1","USN-6927-1","USN-6949-1","USN-6949-2","USN-6952-1","USN-6952-2","USN-6955-1","USN-7019-1"],"status":"published","title":"riscv: Fix TASK_SIZE on 64-bit NOMMU","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix TASK_SIZE on 64-bit NOMMU\n\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.0021,"percentile":0.1133,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2024-05-20T09:47:54Z","modified":"2026-11-11T09:38:19Z","fixes":[{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.91-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.10.216","5.15.158","6.1.90","6.6.30","6.8.9"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.90-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.8.9-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.8.9-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1065.71~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1068.77~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1065.73~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","fixed_in":["5.15.0-1048.55~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-116.126~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1058.61~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1060.66~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-116.126~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1027.27~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1063.69~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1061.65~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-116.126"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1065.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1013.14~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1068.77"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1012.14~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","fixed_in":["5.15.0-1068.77.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1064.72"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1012.13~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1062.68"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1048.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-40.40~22.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1010.10~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1060.66"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1062.67"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-116.126"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-40.40.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1060.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1011.11~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1026.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1063.69"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1010.10~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-40.40.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1035.39"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1047.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1058.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1066.74"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1006.6~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1065.71+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1068.77+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-115.125+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1064.72+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-40.40"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1013.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1012.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1012.13"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1008.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1010.10"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-40.40.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1011.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1011.11.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1010.10"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1010.10"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1009.10"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","fixed_in":["6.8.0-40.40.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1006.6"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-78.78+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.89-r0"},{"fixed":"6.1.91-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.100-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.216"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.158"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.90"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.30"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.8.9"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.90-1"}]}],"versions":["6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1~bpo11+1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.9-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.9-1"}]}]},{"source":"osv","ecosystem":"Debian:10","package":"linux-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.216-1~deb10u1"}]}],"versions":["5.10.136-1~deb10u1","5.10.136-1~deb10u2","5.10.136-1~deb10u3","5.10.149-2~deb10u1","5.10.158-2~deb10u1","5.10.162-1~deb10u1","5.10.178-3~deb10u1","5.10.179-1~deb10u1","5.10.179-3~deb10u1","5.10.179-5~deb10u1","5.10.197-1~deb10u1","5.10.205-2~deb10u1","5.10.209-2~deb10u1"],"bundled":344},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.37-1.mga9"}]}],"bundled":320},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-59.mga9"}]}],"bundled":320},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.18-50.mga9"}]}],"bundled":320},{"source":"osv","ecosystem":"Mageia:9","package":"dwarves","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.27-1.mga9"}]}],"bundled":320},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.37-1.mga9"}]}],"bundled":320},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.84.0.165.oe2203sp1"}]}],"bundled":35},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-218.0.0.121.oe2203sp3"}]}],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.71~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.73~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1048.55~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.61~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.66~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1027.27~20.04.1"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.69~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.65~20.04.1"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"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-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"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-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"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:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.71"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","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","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.14~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.72"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.13~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.68"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1048.55"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40~22.04.3"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.61"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.66"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.67"}]}],"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-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.61"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.11~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1026.26"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1015.15"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","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-1009.9","5.15.0-1012.12","5.15.0-1013.13"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.69"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.61"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58"]},{"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:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1035.39"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1047.49"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1045.47"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.60"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.74"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1006.6~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.71+fips1"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77+fips1"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-115.125+fips1"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.72+fips1"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.14"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.13"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1008.11"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.11"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.11.1"}]}],"versions":["6.8.0-1009.9.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1009.10"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40.1"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2008.8"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1006.6"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-78.78+fips1"}]}],"versions":["6.8.0-38.38+fips4"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1048.55~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.66~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.72"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.68"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1048.55"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.61"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.66"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.67"}]}],"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-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.61"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.69"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.61~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.69~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-116.126~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.71"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","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","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.71~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1"],"bundled":152},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1"],"bundled":156},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77~20.04.1.1"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1","5.15.0-1063.72~20.04.1.1","5.15.0-1064.73~20.04.1.1","5.15.0-1065.74~20.04.1.1","5.15.0-1067.76~20.04.1.1"],"bundled":156},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76"],"bundled":156},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.77.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1"],"bundled":156},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.61"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58"],"bundled":304},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.73~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1"],"bundled":161},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.11~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.13"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1008.11"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.11"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-40.40.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1009.10"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.11.1"}]}],"versions":["6.8.0-1009.9.1"],"bundled":233},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8"],"bundled":233},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.14"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10"],"bundled":233},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9"],"bundled":225},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1035.39"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35"],"bundled":429}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"},{"vendor":"siemens","product":"simatic s7-1500 tm mfp - gnu/linux subsystem"}],"references":[{"url":"https://git.kernel.org/stable/c/04bf2e5f95c1a52e28a7567a507f926efe31c3b6","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/52e8a42b11078d2aad4b9ba96503d77c7299168b","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/4201b8c8f2c32af321fb50867e68ac6c1cbed4be","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/a0f0dbbb1bc49fa0de18e92c36492ff6d804cdaa","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/efdcfa554b6eb228943ef1dd4d023c606be647d2","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/6065e736f82c817c9a597a31ee67f0ce4628e948","tags":["x_transferred","Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html","tags":["x_transferred","Mailing List","Third Party Advisory","web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-265688.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35988","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-cqwh-fpfr-9p4j"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-35988","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35988.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2024-35988","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2024-0263.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33373","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.37","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.36","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.35","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.34","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.33","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.32","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.31","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.30","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.29","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2024-0266.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33374","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-1838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48765","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48772","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52873","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36489","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37353","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37354","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38547","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38553","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38554","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38577","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38579","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38596","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38603","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38633","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39467","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-1839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-31076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38634","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-35988","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35988","tags":["report"]},{"url":"https://git.kernel.org/linus/6065e736f82c817c9a597a31ee67f0ce4628e948","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-6898-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6898-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6898-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6898-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6917-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6919-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6927-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6949-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6952-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6955-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6949-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6952-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7019-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-38096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-7042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-0841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-21823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-22099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38564","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-31076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-33621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-33847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-34027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-34777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42247","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-35988","title":"riscv: Fix TASK_SIZE on 64-bit NOMMU","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix TASK_SIZE on 64-bit NOMMU\n\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.","status":"published","published":"2024-05-20T09:47:54.391Z","modified":"2026-10-15T00:41:59.524Z","updated_at":"2026-11-02T14:34:20.313092Z"}],"euvd":[{"id":"EUVD-2024-35706","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix TASK_SIZE on 64-bit NOMMU\n\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.","status":"published","published":"2024-05-20T09:47:54Z","modified":"2026-10-15T00:41:59Z","updated_at":"2026-11-02T17:27:10.207404Z"}],"ghsa":[{"id":"GHSA-cqwh-fpfr-9p4j","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix TASK_SIZE on 64...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix TASK_SIZE on 64-bit NOMMU\n\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.","status":"published","published":"2024-05-20T12:30:29Z","modified":"2026-05-12T12:31:52Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:08:01.307422Z"}],"nvd":[{"id":"CVE-2024-35988","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix TASK_SIZE on 64-bit NOMMU\n\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.","status":"published","published":"2024-05-20T10:15:13.12Z","modified":"2026-10-15T01:18:18.317Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"updated_at":"2026-11-02T14:10:01.327642Z"}],"osv":[{"id":"BELL-CVE-2024-35988","status":"published","published":"2024-05-21T05:57:08.542125Z","modified":"2026-01-26T09:37:32.282512Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:19.923987Z"},{"id":"DEBIAN-CVE-2024-35988","description":"In the Linux kernel, the following vulnerability has been resolved:  riscv: Fix TASK_SIZE on 64-bit NOMMU  On NOMMU, userspace memory can come from anywhere in physical RAM. The current definition of TASK_SIZE is wrong if any RAM exists above 4G, causing spurious failures in the userspace access routines.","status":"published","published":"2024-05-20T10:15:13.12Z","modified":"2026-11-02T12:02:34.153130191Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:42.835825Z"},{"id":"OESA-2024-1838","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nARM: 9170/1: fix panic when kasan and kprobe are enabled\r\n\r\narm32 uses software to simulate the instruction replaced\nby kprobe. some instructions may be simulated by constructing\nassembly functions. therefore, before executing instruction\nsimulation, it is necessary to construct assembly function\nexecution environment in C language through binding registers.\nafter kasan is enabled, the register binding relationship will\nbe destroyed, resulting in instruction simulation errors and\ncausing kernel panic.\r\n\r\nthe kprobe emulate instruction function is distributed in three\nfiles: actions-common.c actions-arm.c actions-thumb.c, so disable\nKASAN when compiling these files.\r\n\r\nfor example, use kprobe insert on cap_capable+20 after kasan\nenabled, the cap_capable assembly code is as follows:\n\u0026lt;cap_capable\u0026gt;:\ne92d47f0\tpush\t{r4, r5, r6, r7, r8, r9, sl, lr}\ne1a05000\tmov\tr5, r0\ne280006c\tadd\tr0, r0, #108    ; 0x6c\ne1a04001\tmov\tr4, r1\ne1a06002\tmov\tr6, r2\ne59fa090\tldr\tsl, [pc, #144]  ;\nebfc7bf8\tbl\tc03aa4b4 \u0026lt;__asan_load4\u0026gt;\ne595706c\tldr\tr7, [r5, #108]  ; 0x6c\ne2859014\tadd\tr9, r5, #20\n......\nThe emulate_ldr assembly code after enabling kasan is as follows:\nc06f1384 \u0026lt;emulate_ldr\u0026gt;:\ne92d47f0\tpush\t{r4, r5, r6, r7, r8, r9, sl, lr}\ne282803c\tadd\tr8, r2, #60     ; 0x3c\ne1a05000\tmov\tr5, r0\ne7e37855\tubfx\tr7, r5, #16, #4\ne1a00008\tmov\tr0, r8\ne1a09001\tmov\tr9, r1\ne1a04002\tmov\tr4, r2\nebf35462\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne357000f\tcmp\tr7, #15\ne7e36655\tubfx\tr6, r5, #12, #4\ne205a00f\tand\tsl, r5, #15\n0a000001\tbeq\tc06f13bc \u0026lt;emulate_ldr+0x38\u0026gt;\ne0840107\tadd\tr0, r4, r7, lsl #2\nebf3545c\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne084010a\tadd\tr0, r4, sl, lsl #2\nebf3545a\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne2890010\tadd\tr0, r9, #16\nebf35458\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne5990010\tldr\tr0, [r9, #16]\ne12fff30\tblx\tr0\ne356000f\tcm\tr6, #15\n1a000014\tbne\tc06f1430 \u0026lt;emulate_ldr+0xac\u0026gt;\ne1a06000\tmov\tr6, r0\ne2840040\tadd\tr0, r4, #64     ; 0x40\n......\r\n\r\nwhen running in emulate_ldr to simulate the ldr instruction, panic\noccurred, and the log is as follows:\nUnable to handle kernel NULL pointer dereference at virtual address\n00000090\npgd = ecb46400\n[00000090] *pgd=2e0fa003, *pmd=00000000\nInternal error: Oops: 206 [#1] SMP ARM\nPC is at cap_capable+0x14/0xb0\nLR is at emulate_ldr+0x50/0xc0\npsr: 600d0293 sp : ecd63af8  ip : 00000004  fp : c0a7c30c\nr10: 00000000  r9 : c30897f4  r8 : ecd63cd4\nr7 : 0000000f  r6 : 0000000a  r5 : e59fa090  r4 : ecd63c98\nr3 : c06ae294  r2 : 00000000  r1 : b7611300  r0 : bf4ec008\nFlags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user\nControl: 32c5387d  Table: 2d546400  DAC: 55555555\nProcess bash (pid: 1643, stack limit = 0xecd60190)\n(cap_capable) from (kprobe_handler+0x218/0x340)\n(kprobe_handler) from (kprobe_trap_handler+0x24/0x48)\n(kprobe_trap_handler) from (do_undefinstr+0x13c/0x364)\n(do_undefinstr) from (__und_svc_finish+0x0/0x30)\n(__und_svc_finish) from (cap_capable+0x18/0xb0)\n(cap_capable) from (cap_vm_enough_memory+0x38/0x48)\n(cap_vm_enough_memory) from\n(security_vm_enough_memory_mm+0x48/0x6c)\n(security_vm_enough_memory_mm) from\n(copy_process.constprop.5+0x16b4/0x25c8)\n(copy_process.constprop.5) from (_do_fork+0xe8/0x55c)\n(_do_fork) from (SyS_clone+0x1c/0x24)\n(SyS_clone) from (__sys_trace_return+0x0/0x10)\nCode: 0050a0e1 6c0080e2 0140a0e1 0260a0e1 (f801f0e7)(CVE-2021-47618)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: fix use-after-free after failure to create a snapshot\r\n\r\nAt ioctl.c:create_snapshot(), we allocate a pending snapshot structure and\nthen attach it to the transaction\u0026apos;s list of pending snapshots. After that\nwe call btrfs_commit_transaction(), and if that returns an error we jump\nto \u0026apos;fail\u0026apos; label, where we kfree() the pending snapshot structure. This can\nresult in a later use-after-free of the pending snapshot:\r\n\r\n1) We allocated the pending snapshot and added it to the transaction\u0026apos;s\n   list of pending snapshots;\r\n\r\n2) We call btrfs_commit_transaction(), and it fails either at the first\n   call to btrfs_run_delayed_refs() or btrfs_start_dirty_block_groups().\n   In both cases, we don\u0026apos;t abort the transaction and we release our\n   transaction handle. We jump to the \u0026apos;fail\u0026apos; label and free the pending\n   snapshot structure. We return with the pending snapshot still in the\n   transaction\u0026apos;s list;\r\n\r\n3) Another task commits the transaction. This time there\u0026apos;s no error at\n   all, and then during the transaction commit it accesses a pointer\n   to the pending snapshot structure that the snapshot creation task\n   has already freed, resulting in a user-after-free.\r\n\r\nThis issue could actually be detected by smatch, which produced the\nfollowing warning:\r\n\r\n  fs/btrfs/ioctl.c:843 create_snapshot() warn: \u0026apos;\u0026amp;pending_snapshot-\u0026gt;list\u0026apos; not removed from list\r\n\r\nSo fix this by not having the snapshot creation ioctl directly add the\npending snapshot to the transaction\u0026apos;s list. Instead add the pending\nsnapshot to the transaction handle, and then at btrfs_commit_transaction()\nwe add the snapshot to the list only when we can guarantee that any error\nreturned after that point will result in a transaction abort, in which\ncase the ioctl code can safely free the pending snapshot and no one can\naccess it anymore.(CVE-2022-48733)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5e: Avoid field-overflowing memcpy()\r\n\r\nIn preparation for FORTIFY_SOURCE performing compile-time and run-time\nfield bounds checking for memcpy(), memmove(), and memset(), avoid\nintentionally writing across neighboring fields.\r\n\r\nUse flexible arrays instead of zero-element arrays (which look like they\nare always overflowing) and split the cross-field memcpy() into two halves\nthat can be appropriately bounds-checked by the compiler.\r\n\r\nWe were doing:\r\n\r\n\t#define ETH_HLEN  14\n\t#define VLAN_HLEN  4\n\t...\n\t#define MLX5E_XDP_MIN_INLINE (ETH_HLEN + VLAN_HLEN)\n\t...\n        struct mlx5e_tx_wqe      *wqe  = mlx5_wq_cyc_get_wqe(wq, pi);\n\t...\n        struct mlx5_wqe_eth_seg  *eseg = \u0026amp;wqe-\u0026gt;eth;\n        struct mlx5_wqe_data_seg *dseg = wqe-\u0026gt;data;\n\t...\n\tmemcpy(eseg-\u0026gt;inline_hdr.start, xdptxd-\u0026gt;data, MLX5E_XDP_MIN_INLINE);\r\n\r\ntarget is wqe-\u0026gt;eth.inline_hdr.start (which the compiler sees as being\n2 bytes in size), but copying 18, intending to write across start\n(really vlan_tci, 2 bytes). The remaining 16 bytes get written into\nwqe-\u0026gt;data[0], covering byte_count (4 bytes), lkey (4 bytes), and addr\n(8 bytes).\r\n\r\nstruct mlx5e_tx_wqe {\n        struct mlx5_wqe_ctrl_seg   ctrl;                 /*     0    16 */\n        struct mlx5_wqe_eth_seg    eth;                  /*    16    16 */\n        struct mlx5_wqe_data_seg   data[];               /*    32     0 */\r\n\r\n        /* size: 32, cachelines: 1, members: 3 */\n        /* last cacheline: 32 bytes */\n};\r\n\r\nstruct mlx5_wqe_eth_seg {\n        u8                         swp_outer_l4_offset;  /*     0     1 */\n        u8                         swp_outer_l3_offset;  /*     1     1 */\n        u8                         swp_inner_l4_offset;  /*     2     1 */\n        u8                         swp_inner_l3_offset;  /*     3     1 */\n        u8                         cs_flags;             /*     4     1 */\n        u8                         swp_flags;            /*     5     1 */\n        __be16                     mss;                  /*     6     2 */\n        __be32                     flow_table_metadata;  /*     8     4 */\n        union {\n                struct {\n                        __be16     sz;                   /*    12     2 */\n                        u8         start[2];             /*    14     2 */\n                } inline_hdr;                            /*    12     4 */\n                struct {\n                        __be16     type;                 /*    12     2 */\n                        __be16     vlan_tci;             /*    14     2 */\n                } insert;                                /*    12     4 */\n                __be32             trailer;              /*    12     4 */\n        };                                               /*    12     4 */\r\n\r\n        /* size: 16, cachelines: 1, members: 9 */\n        /* last cacheline: 16 bytes */\n};\r\n\r\nstruct mlx5_wqe_data_seg {\n        __be32                     byte_count;           /*     0     4 */\n        __be32                     lkey;                 /*     4     4 */\n        __be64                     addr;                 /*     8     8 */\r\n\r\n        /* size: 16, cachelines: 1, members: 3 */\n        /* last cacheline: 16 bytes */\n};\r\n\r\nSo, split the memcpy() so the compiler can reason about the buffer\nsizes.\r\n\r\n\u0026quot;pahole\u0026quot; shows no size nor member offset changes to struct mlx5e_tx_wqe\nnor struct mlx5e_umr_wqe. \u0026quot;objdump -d\u0026quot; shows no meaningful object\ncode changes (i.e. only source line number induced differences and\noptimizations).(CVE-2022-48744)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: LAPIC: Also cancel preemption timer during SET_LAPIC\r\n\r\nThe below warning is splatting during guest reboot.\r\n\r\n  ------------[ cut here ]------------\n  WARNING: CPU: 0 PID: 1931 at arch/x86/kvm/x86.c:10322 kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]\n  CPU: 0 PID: 1931 Comm: qemu-system-x86 Tainted: G          I       5.17.0-rc1+ #5\n  RIP: 0010:kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kvm_vcpu_ioctl+0x279/0x710 [kvm]\n   __x64_sys_ioctl+0x83/0xb0\n   do_syscall_64+0x3b/0xc0\n   entry_SYSCALL_64_after_hwframe+0x44/0xae\n  RIP: 0033:0x7fd39797350b\r\n\r\nThis can be triggered by not exposing tsc-deadline mode and doing a reboot in\nthe guest. The lapic_shutdown() function which is called in sys_reboot path\nwill not disarm the flying timer, it just masks LVTT. lapic_shutdown() clears\nAPIC state w/ LVT_MASKED and timer-mode bit is 0, this can trigger timer-mode\nswitch between tsc-deadline and oneshot/periodic, which can result in preemption\ntimer be cancelled in apic_update_lvtt(). However, We can\u0026apos;t depend on this when\nnot exposing tsc-deadline mode and oneshot/periodic modes emulated by preemption\ntimer. Qemu will synchronise states around reset, let\u0026apos;s cancel preemption timer\nunder KVM_SET_LAPIC.(CVE-2022-48765)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: lgdt3306a: Add a check against null-pointer-def\r\n\r\nThe driver should check whether the client provides the platform_data.\r\n\r\nThe following log reveals it:\r\n\r\n[   29.610324] BUG: KASAN: null-ptr-deref in kmemdup+0x30/0x40\n[   29.610730] Read of size 40 at addr 0000000000000000 by task bash/414\n[   29.612820] Call Trace:\n[   29.613030]  \u0026lt;TASK\u0026gt;\n[   29.613201]  dump_stack_lvl+0x56/0x6f\n[   29.613496]  ? kmemdup+0x30/0x40\n[   29.613754]  print_report.cold+0x494/0x6b7\n[   29.614082]  ? kmemdup+0x30/0x40\n[   29.614340]  kasan_report+0x8a/0x190\n[   29.614628]  ? kmemdup+0x30/0x40\n[   29.614888]  kasan_check_range+0x14d/0x1d0\n[   29.615213]  memcpy+0x20/0x60\n[   29.615454]  kmemdup+0x30/0x40\n[   29.615700]  lgdt3306a_probe+0x52/0x310\n[   29.616339]  i2c_device_probe+0x951/0xa90(CVE-2022-48772)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nclk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data\r\n\r\nAdd the check for the return value of mtk_alloc_clk_data() in order to\navoid NULL pointer dereference.(CVE-2023-52873)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: dynamic: Synchronize of_changeset_destroy() with the devlink removals\r\n\r\nIn the following sequence:\n  1) of_platform_depopulate()\n  2) of_overlay_remove()\r\n\r\nDuring the step 1, devices are destroyed and devlinks are removed.\nDuring the step 2, OF nodes are destroyed but\n__of_changeset_entry_destroy() can raise warnings related to missing\nof_node_put():\n  ERROR: memory leak, expected refcount 1 instead of 2 ...\r\n\r\nIndeed, during the devlink removals performed at step 1, the removal\nitself releasing the device (and the attached of_node) is done by a job\nqueued in a workqueue and so, it is done asynchronously with respect to\nfunction calls.\nWhen the warning is present, of_node_put() will be called but wrongly\ntoo late from the workqueue job.\r\n\r\nIn order to be sure that any ongoing devlink removals are done before\nthe of_node destruction, synchronize the of_changeset_destroy() with the\ndevlink removals.(CVE-2024-35879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: act_skbmod: prevent kernel-infoleak\r\n\r\nsyzbot found that tcf_skbmod_dump() was copying four bytes\nfrom kernel stack to user space [1].\r\n\r\nThe issue here is that \u0026apos;struct tc_skbmod\u0026apos; has a four bytes hole.\r\n\r\nWe need to clear the structure before filling fields.\r\n\r\n[1]\nBUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline]\n BUG: KMSAN: kernel-infoleak in copy_to_user_iter lib/iov_iter.c:24 [inline]\n BUG: KMSAN: kernel-infoleak in iterate_ubuf include/linux/iov_iter.h:29 [inline]\n BUG: KMSAN: kernel-infoleak in iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\n BUG: KMSAN: kernel-infoleak in iterate_and_advance include/linux/iov_iter.h:271 [inline]\n BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n  instrument_copy_to_user include/linux/instrumented.h:114 [inline]\n  copy_to_user_iter lib/iov_iter.c:24 [inline]\n  iterate_ubuf include/linux/iov_iter.h:29 [inline]\n  iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\n  iterate_and_advance include/linux/iov_iter.h:271 [inline]\n  _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n  copy_to_iter include/linux/uio.h:196 [inline]\n  simple_copy_to_iter net/core/datagram.c:532 [inline]\n  __skb_datagram_iter+0x185/0x1000 net/core/datagram.c:420\n  skb_copy_datagram_iter+0x5c/0x200 net/core/datagram.c:546\n  skb_copy_datagram_msg include/linux/skbuff.h:4050 [inline]\n  netlink_recvmsg+0x432/0x1610 net/netlink/af_netlink.c:1962\n  sock_recvmsg_nosec net/socket.c:1046 [inline]\n  sock_recvmsg+0x2c4/0x340 net/socket.c:1068\n  __sys_recvfrom+0x35a/0x5f0 net/socket.c:2242\n  __do_sys_recvfrom net/socket.c:2260 [inline]\n  __se_sys_recvfrom net/socket.c:2256 [inline]\n  __x64_sys_recvfrom+0x126/0x1d0 net/socket.c:2256\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nUninit was stored to memory at:\n  pskb_expand_head+0x30f/0x19d0 net/core/skbuff.c:2253\n  netlink_trim+0x2c2/0x330 net/netlink/af_netlink.c:1317\n  netlink_unicast+0x9f/0x1260 net/netlink/af_netlink.c:1351\n  nlmsg_unicast include/net/netlink.h:1144 [inline]\n  nlmsg_notify+0x21d/0x2f0 net/netlink/af_netlink.c:2610\n  rtnetlink_send+0x73/0x90 net/core/rtnetlink.c:741\n  rtnetlink_maybe_send include/linux/rtnetlink.h:17 [inline]\n  tcf_add_notify net/sched/act_api.c:2048 [inline]\n  tcf_action_add net/sched/act_api.c:2071 [inline]\n  tc_ctl_action+0x146e/0x19d0 net/sched/act_api.c:2119\n  rtnetlink_rcv_msg+0x1737/0x1900 net/core/rtnetlink.c:6595\n  netlink_rcv_skb+0x375/0x650 net/netlink/af_netlink.c:2559\n  rtnetlink_rcv+0x34/0x40 net/core/rtnetlink.c:6613\n  netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]\n  netlink_unicast+0xf4c/0x1260 net/netlink/af_netlink.c:1361\n  netlink_sendmsg+0x10df/0x11f0 net/netlink/af_netlink.c:1905\n  sock_sendmsg_nosec net/socket.c:730 [inline]\n  __sock_sendmsg+0x30f/0x380 net/socket.c:745\n  ____sys_sendmsg+0x877/0xb60 net/socket.c:2584\n  ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2638\n  __sys_sendmsg net/socket.c:2667 [inline]\n  __do_sys_sendmsg net/socket.c:2676 [inline]\n  __se_sys_sendmsg net/socket.c:2674 [inline]\n  __x64_sys_sendmsg+0x307/0x4a0 net/socket.c:2674\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nUninit was stored to memory at:\n  __nla_put lib/nlattr.c:1041 [inline]\n  nla_put+0x1c6/0x230 lib/nlattr.c:1099\n  tcf_skbmod_dump+0x23f/0xc20 net/sched/act_skbmod.c:256\n  tcf_action_dump_old net/sched/act_api.c:1191 [inline]\n  tcf_action_dump_1+0x85e/0x970 net/sched/act_api.c:1227\n  tcf_action_dump+0x1fd/0x460 net/sched/act_api.c:1251\n  tca_get_fill+0x519/0x7a0 net/sched/act_api.c:1628\n  tcf_add_notify_msg net/sched/act_api.c:2023 [inline]\n  tcf_add_notify net/sched/act_api.c:2042 [inline]\n  tcf_action_add net/sched/act_api.c:2071 [inline]\n  tc_ctl_action+0x1365/0x19d0 net/sched/act_api.c:2119\n  rtnetlink_rcv_msg+0x1737/0x1900 net/core/rtnetlink.c:6595\n  netlink_rcv_skb+0x375/0x650 net/netlink/af_netli\n---truncated---(CVE-2024-35893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr\r\n\r\nAlthough ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it\nstill means hlist_for_each_entry_rcu can return an item that got removed\nfrom the list. The memory itself of such item is not freed thanks to RCU\nbut nothing guarantees the actual content of the memory is sane.\r\n\r\nIn particular, the reference count can be zero. This can happen if\nipv6_del_addr is called in parallel. ipv6_del_addr removes the entry\nfrom inet6_addr_lst (hlist_del_init_rcu(\u0026amp;ifp-\u0026gt;addr_lst)) and drops all\nreferences (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough\ntiming, this can happen:\r\n\r\n1. In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry.\r\n\r\n2. Then, the whole ipv6_del_addr is executed for the given entry. The\n   reference count drops to zero and kfree_rcu is scheduled.\r\n\r\n3. ipv6_get_ifaddr continues and tries to increments the reference count\n   (in6_ifa_hold).\r\n\r\n4. The rcu is unlocked and the entry is freed.\r\n\r\n5. The freed entry is returned.\r\n\r\nPrevent increasing of the reference count in such case. The name\nin6_ifa_hold_safe is chosen to mimic the existing fib6_info_hold_safe.\r\n\r\n[   41.506330] refcount_t: addition on 0; use-after-free.\n[   41.506760] WARNING: CPU: 0 PID: 595 at lib/refcount.c:25 refcount_warn_saturate+0xa5/0x130\n[   41.507413] Modules linked in: veth bridge stp llc\n[   41.507821] CPU: 0 PID: 595 Comm: python3 Not tainted 6.9.0-rc2.main-00208-g49563be82afa #14\n[   41.508479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)\n[   41.509163] RIP: 0010:refcount_warn_saturate+0xa5/0x130\n[   41.509586] Code: ad ff 90 0f 0b 90 90 c3 cc cc cc cc 80 3d c0 30 ad 01 00 75 a0 c6 05 b7 30 ad 01 01 90 48 c7 c7 38 cc 7a 8c e8 cc 18 ad ff 90 \u0026lt;0f\u0026gt; 0b 90 90 c3 cc cc cc cc 80 3d 98 30 ad 01 00 0f 85 75 ff ff ff\n[   41.510956] RSP: 0018:ffffbda3c026baf0 EFLAGS: 00010282\n[   41.511368] RAX: 0000000000000000 RBX: ffff9e9c46914800 RCX: 0000000000000000\n[   41.511910] RDX: ffff9e9c7ec29c00 RSI: ffff9e9c7ec1c900 RDI: ffff9e9c7ec1c900\n[   41.512445] RBP: ffff9e9c43660c9c R08: 0000000000009ffb R09: 00000000ffffdfff\n[   41.512998] R10: 00000000ffffdfff R11: ffffffff8ca58a40 R12: ffff9e9c4339a000\n[   41.513534] R13: 0000000000000001 R14: ffff9e9c438a0000 R15: ffffbda3c026bb48\n[   41.514086] FS:  00007fbc4cda1740(0000) GS:ffff9e9c7ec00000(0000) knlGS:0000000000000000\n[   41.514726] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   41.515176] CR2: 000056233b337d88 CR3: 000000000376e006 CR4: 0000000000370ef0\n[   41.515713] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[   41.516252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[   41.516799] Call Trace:\n[   41.517037]  \u0026lt;TASK\u0026gt;\n[   41.517249]  ? __warn+0x7b/0x120\n[   41.517535]  ? refcount_warn_saturate+0xa5/0x130\n[   41.517923]  ? report_bug+0x164/0x190\n[   41.518240]  ? handle_bug+0x3d/0x70\n[   41.518541]  ? exc_invalid_op+0x17/0x70\n[   41.520972]  ? asm_exc_invalid_op+0x1a/0x20\n[   41.521325]  ? refcount_warn_saturate+0xa5/0x130\n[   41.521708]  ipv6_get_ifaddr+0xda/0xe0\n[   41.522035]  inet6_rtm_getaddr+0x342/0x3f0\n[   41.522376]  ? __pfx_inet6_rtm_getaddr+0x10/0x10\n[   41.522758]  rtnetlink_rcv_msg+0x334/0x3d0\n[   41.523102]  ? netlink_unicast+0x30f/0x390\n[   41.523445]  ? __pfx_rtnetlink_rcv_msg+0x10/0x10\n[   41.523832]  netlink_rcv_skb+0x53/0x100\n[   41.524157]  netlink_unicast+0x23b/0x390\n[   41.524484]  netlink_sendmsg+0x1f2/0x440\n[   41.524826]  __sys_sendto+0x1d8/0x1f0\n[   41.525145]  __x64_sys_sendto+0x1f/0x30\n[   41.525467]  do_syscall_64+0xa5/0x1b0\n[   41.525794]  entry_SYSCALL_64_after_hwframe+0x72/0x7a\n[   41.526213] RIP: 0033:0x7fbc4cfcea9a\n[   41.526528] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89\n[   41.527942] RSP: 002b:00007f\n---truncated---(CVE-2024-35969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: Fix TASK_SIZE on 64-bit NOMMU\r\n\r\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.(CVE-2024-35988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndmaengine: idxd: Fix oops during rmmod on single-CPU platforms\r\n\r\nDuring the removal of the idxd driver, registered offline callback is\ninvoked as part of the clean up process. However, on systems with only\none CPU online, no valid target is available to migrate the\nperf context, resulting in a kernel oops:\r\n\r\n    BUG: unable to handle page fault for address: 000000000002a2b8\n    #PF: supervisor write access in kernel mode\n    #PF: error_code(0x0002) - not-present page\n    PGD 1470e1067 P4D 0\n    Oops: 0002 [#1] PREEMPT SMP NOPTI\n    CPU: 0 PID: 20 Comm: cpuhp/0 Not tainted 6.8.0-rc6-dsa+ #57\n    Hardware name: Intel Corporation AvenueCity/AvenueCity, BIOS BHSDCRB1.86B.2492.D03.2307181620 07/18/2023\n    RIP: 0010:mutex_lock+0x2e/0x50\n    ...\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    __die+0x24/0x70\n    page_fault_oops+0x82/0x160\n    do_user_addr_fault+0x65/0x6b0\n    __pfx___rdmsr_safe_on_cpu+0x10/0x10\n    exc_page_fault+0x7d/0x170\n    asm_exc_page_fault+0x26/0x30\n    mutex_lock+0x2e/0x50\n    mutex_lock+0x1e/0x50\n    perf_pmu_migrate_context+0x87/0x1f0\n    perf_event_cpu_offline+0x76/0x90 [idxd]\n    cpuhp_invoke_callback+0xa2/0x4f0\n    __pfx_perf_event_cpu_offline+0x10/0x10 [idxd]\n    cpuhp_thread_fun+0x98/0x150\n    smpboot_thread_fn+0x27/0x260\n    smpboot_thread_fn+0x1af/0x260\n    __pfx_smpboot_thread_fn+0x10/0x10\n    kthread+0x103/0x140\n    __pfx_kthread+0x10/0x10\n    ret_from_fork+0x31/0x50\n    __pfx_kthread+0x10/0x10\n    ret_from_fork_asm+0x1b/0x30\n    \u0026lt;TASK\u0026gt;\r\n\r\nFix the issue by preventing the migration of the perf context to an\ninvalid target.(CVE-2024-35989)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/arm/malidp: fix a possible null pointer dereference\r\n\r\nIn malidp_mw_connector_reset, new memory is allocated with kzalloc, but\nno check is performed. In order to prevent null pointer dereferencing,\nensure that mw_state is checked before calling\n__drm_atomic_helper_connector_reset.(CVE-2024-36014)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntls: fix missing memory barrier in tls_init\r\n\r\nIn tls_init(), a write memory barrier is missing, and store-store\nreordering may cause NULL dereference in tls_{setsockopt,getsockopt}.\r\n\r\nCPU0                               CPU1\n-----                              -----\n// In tls_init()\n// In tls_ctx_create()\nctx = kzalloc()\nctx-\u0026gt;sk_proto = READ_ONCE(sk-\u0026gt;sk_prot) -(1)\r\n\r\n// In update_sk_prot()\nWRITE_ONCE(sk-\u0026gt;sk_prot, tls_prots)     -(2)\r\n\r\n                                   // In sock_common_setsockopt()\n                                   READ_ONCE(sk-\u0026gt;sk_prot)-\u0026gt;setsockopt()\r\n\r\n                                   // In tls_{setsockopt,getsockopt}()\n                                   ctx-\u0026gt;sk_proto-\u0026gt;setsockopt()    -(3)\r\n\r\nIn the above scenario, when (1) and (2) are reordered, (3) can observe\nthe NULL value of ctx-\u0026gt;sk_proto, causing NULL dereference.\r\n\r\nTo fix it, we rely on rcu_assign_pointer() which implies the release\nbarrier semantic. By moving rcu_assign_pointer() after ctx-\u0026gt;sk_proto is\ninitialized, we can ensure that ctx-\u0026gt;sk_proto are visible when\nchanging sk-\u0026gt;sk_prot.(CVE-2024-36489)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nvirtio: delete vq in vp_find_vqs_msix() when request_irq() fails\r\n\r\nWhen request_irq() fails, error path calls vp_del_vqs(). There, as vq is\npresent in the list, free_irq() is called for the same vector. That\ncauses following splat:\r\n\r\n[    0.414355] Trying to free already-free IRQ 27\n[    0.414403] WARNING: CPU: 1 PID: 1 at kernel/irq/manage.c:1899 free_irq+0x1a1/0x2d0\n[    0.414510] Modules linked in:\n[    0.414540] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.9.0-rc4+ #27\n[    0.414540] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014\n[    0.414540] RIP: 0010:free_irq+0x1a1/0x2d0\n[    0.414540] Code: 1e 00 48 83 c4 08 48 89 e8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 90 8b 74 24 04 48 c7 c7 98 80 6c b1 e8 00 c9 f7 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 89 ee 4c 89 ef e8 e0 20 b8 00 49 8b 47 40 48 8b 40\n[    0.414540] RSP: 0000:ffffb71480013ae0 EFLAGS: 00010086\n[    0.414540] RAX: 0000000000000000 RBX: ffffa099c2722000 RCX: 0000000000000000\n[    0.414540] RDX: 0000000000000000 RSI: ffffb71480013998 RDI: 0000000000000001\n[    0.414540] RBP: 0000000000000246 R08: 00000000ffffdfff R09: 0000000000000001\n[    0.414540] R10: 00000000ffffdfff R11: ffffffffb18729c0 R12: ffffa099c1c91760\n[    0.414540] R13: ffffa099c1c916a4 R14: ffffa099c1d2f200 R15: ffffa099c1c91600\n[    0.414540] FS:  0000000000000000(0000) GS:ffffa099fec40000(0000) knlGS:0000000000000000\n[    0.414540] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    0.414540] CR2: 0000000000000000 CR3: 0000000008e3e001 CR4: 0000000000370ef0\n[    0.414540] Call Trace:\n[    0.414540]  \u0026lt;TASK\u0026gt;\n[    0.414540]  ? __warn+0x80/0x120\n[    0.414540]  ? free_irq+0x1a1/0x2d0\n[    0.414540]  ? report_bug+0x164/0x190\n[    0.414540]  ? handle_bug+0x3b/0x70\n[    0.414540]  ? exc_invalid_op+0x17/0x70\n[    0.414540]  ? asm_exc_invalid_op+0x1a/0x20\n[    0.414540]  ? free_irq+0x1a1/0x2d0\n[    0.414540]  vp_del_vqs+0xc1/0x220\n[    0.414540]  vp_find_vqs_msix+0x305/0x470\n[    0.414540]  vp_find_vqs+0x3e/0x1a0\n[    0.414540]  vp_modern_find_vqs+0x1b/0x70\n[    0.414540]  init_vqs+0x387/0x600\n[    0.414540]  virtnet_probe+0x50a/0xc80\n[    0.414540]  virtio_dev_probe+0x1e0/0x2b0\n[    0.414540]  really_probe+0xc0/0x2c0\n[    0.414540]  ? __pfx___driver_attach+0x10/0x10\n[    0.414540]  __driver_probe_device+0x73/0x120\n[    0.414540]  driver_probe_device+0x1f/0xe0\n[    0.414540]  __driver_attach+0x88/0x180\n[    0.414540]  bus_for_each_dev+0x85/0xd0\n[    0.414540]  bus_add_driver+0xec/0x1f0\n[    0.414540]  driver_register+0x59/0x100\n[    0.414540]  ? __pfx_virtio_net_driver_init+0x10/0x10\n[    0.414540]  virtio_net_driver_init+0x90/0xb0\n[    0.414540]  do_one_initcall+0x58/0x230\n[    0.414540]  kernel_init_freeable+0x1a3/0x2d0\n[    0.414540]  ? __pfx_kernel_init+0x10/0x10\n[    0.414540]  kernel_init+0x1a/0x1c0\n[    0.414540]  ret_from_fork+0x31/0x50\n[    0.414540]  ? __pfx_kernel_init+0x10/0x10\n[    0.414540]  ret_from_fork_asm+0x1a/0x30\n[    0.414540]  \u0026lt;/TASK\u0026gt;\r\n\r\nFix this by calling deleting the current vq when request_irq() fails.(CVE-2024-37353)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: fix crash on racing fsync and size-extending write into prealloc\r\n\r\nWe have been seeing crashes on duplicate keys in\nbtrfs_set_item_key_safe():\r\n\r\n  BTRFS critical (device vdb): slot 4 key (450 108 8192) new key (450 108 8192)\n  ------------[ cut here ]------------\n  kernel BUG at fs/btrfs/ctree.c:2620!\n  invalid opcode: 0000 [#1] PREEMPT SMP PTI\n  CPU: 0 PID: 3139 Comm: xfs_io Kdump: loaded Not tainted 6.9.0 #6\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:btrfs_set_item_key_safe+0x11f/0x290 [btrfs]\r\n\r\nWith the following stack trace:\r\n\r\n  #0  btrfs_set_item_key_safe (fs/btrfs/ctree.c:2620:4)\n  #1  btrfs_drop_extents (fs/btrfs/file.c:411:4)\n  #2  log_one_extent (fs/btrfs/tree-log.c:4732:9)\n  #3  btrfs_log_changed_extents (fs/btrfs/tree-log.c:4955:9)\n  #4  btrfs_log_inode (fs/btrfs/tree-log.c:6626:9)\n  #5  btrfs_log_inode_parent (fs/btrfs/tree-log.c:7070:8)\n  #6  btrfs_log_dentry_safe (fs/btrfs/tree-log.c:7171:8)\n  #7  btrfs_sync_file (fs/btrfs/file.c:1933:8)\n  #8  vfs_fsync_range (fs/sync.c:188:9)\n  #9  vfs_fsync (fs/sync.c:202:9)\n  #10 do_fsync (fs/sync.c:212:9)\n  #11 __do_sys_fdatasync (fs/sync.c:225:9)\n  #12 __se_sys_fdatasync (fs/sync.c:223:1)\n  #13 __x64_sys_fdatasync (fs/sync.c:223:1)\n  #14 do_syscall_x64 (arch/x86/entry/common.c:52:14)\n  #15 do_syscall_64 (arch/x86/entry/common.c:83:7)\n  #16 entry_SYSCALL_64+0xaf/0x14c (arch/x86/entry/entry_64.S:121)\r\n\r\nSo we\u0026apos;re logging a changed extent from fsync, which is splitting an\nextent in the log tree. But this split part already exists in the tree,\ntriggering the BUG().\r\n\r\nThis is the state of the log tree at the time of the crash, dumped with\ndrgn (https://github.com/osandov/drgn/blob/main/contrib/btrfs_tree.py)\nto get more details than btrfs_print_leaf() gives us:\r\n\r\n  \u0026gt;\u0026gt;\u0026gt; print_extent_buffer(prog.crashed_thread().stack_trace()[0][\u0026quot;eb\u0026quot;])\n  leaf 33439744 level 0 items 72 generation 9 owner 18446744073709551610\n  leaf 33439744 flags 0x100000000000000\n  fs uuid e5bd3946-400c-4223-8923-190ef1f18677\n  chunk uuid d58cb17e-6d02-494a-829a-18b7d8a399da\n          item 0 key (450 INODE_ITEM 0) itemoff 16123 itemsize 160\n                  generation 7 transid 9 size 8192 nbytes 8473563889606862198\n                  block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0\n                  sequence 204 flags 0x10(PREALLOC)\n                  atime 1716417703.220000000 (2024-05-22 15:41:43)\n                  ctime 1716417704.983333333 (2024-05-22 15:41:44)\n                  mtime 1716417704.983333333 (2024-05-22 15:41:44)\n                  otime 17592186044416.000000000 (559444-03-08 01:40:16)\n          item 1 key (450 INODE_REF 256) itemoff 16110 itemsize 13\n                  index 195 namelen 3 name: 193\n          item 2 key (450 XATTR_ITEM 1640047104) itemoff 16073 itemsize 37\n                  location key (0 UNKNOWN.0 0) type XATTR\n                  transid 7 data_len 1 name_len 6\n                  name: user.a\n                  data a\n          item 3 key (450 EXTENT_DATA 0) itemoff 16020 itemsize 53\n                  generation 9 type 1 (regular)\n                  extent data disk byte 303144960 nr 12288\n                  extent data offset 0 nr 4096 ram 12288\n                  extent compression 0 (none)\n          item 4 key (450 EXTENT_DATA 4096) itemoff 15967 itemsize 53\n                  generation 9 type 2 (prealloc)\n                  prealloc data disk byte 303144960 nr 12288\n                  prealloc data offset 4096 nr 8192\n          item 5 key (450 EXTENT_DATA 8192) itemoff 15914 itemsize 53\n                  generation 9 type 2 (prealloc)\n                  prealloc data disk byte 303144960 nr 12288\n                  prealloc data offset 8192 nr 4096\n  ...\r\n\r\nSo the real problem happened earlier: notice that items 4 (4k-12k) and 5\n(8k-12k) overlap. Both are prealloc extents. Item 4 straddles i_size and\nitem 5 starts at i_size.\r\n\r\nHere is the state of \n---truncated---(CVE-2024-37354)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: Fix uninit-value in nci_rx_work\r\n\r\nsyzbot reported the following uninit-value access issue [1]\r\n\r\nnci_rx_work() parses received packet from ndev-\u0026gt;rx_q. It should be\nvalidated header size, payload size and total packet size before\nprocessing the packet. If an invalid packet is detected, it should be\nsilently discarded.(CVE-2024-38381)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries\r\n\r\nThe allocation failure of mycs-\u0026gt;yuv_scaler_binary in load_video_binaries()\nis followed with a dereference of mycs-\u0026gt;yuv_scaler_binary after the\nfollowing call chain:\r\n\r\nsh_css_pipe_load_binaries()\n  |-\u0026gt; load_video_binaries(mycs-\u0026gt;yuv_scaler_binary == NULL)\n  |\n  |-\u0026gt; sh_css_pipe_unload_binaries()\n        |-\u0026gt; unload_video_binaries()\r\n\r\nIn unload_video_binaries(), it calls to ia_css_binary_unload with argument\n\u0026amp;pipe-\u0026gt;pipe_settings.video.yuv_scaler_binary[i], which refers to the\nsame memory slot as mycs-\u0026gt;yuv_scaler_binary. Thus, a null-pointer\ndereference is triggered.(CVE-2024-38547)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Fix potential index out of bounds in color transformation function\r\n\r\nFixes index out of bounds issue in the color transformation function.\nThe issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer\nfunction points (TRANSFER_FUNC_POINTS).\r\n\r\nThe fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the\ntransfer function points. If \u0026apos;i\u0026apos; is out of bounds, an error message is\nlogged and the function returns false to indicate an error.\r\n\r\nReported by smatch:\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:405 cm_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:406 cm_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:407 cm_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-38552)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fec: remove .ndo_poll_controller to avoid deadlocks\r\n\r\nThere is a deadlock issue found in sungem driver, please refer to the\ncommit ac0a230f719b (\u0026quot;eth: sungem: remove .ndo_poll_controller to avoid\ndeadlocks\u0026quot;). The root cause of the issue is that netpoll is in atomic\ncontext and disable_irq() is called by .ndo_poll_controller interface\nof sungem driver, however, disable_irq() might sleep. After analyzing\nthe implementation of fec_poll_controller(), the fec driver should have\nthe same issue. Due to the fec driver uses NAPI for TX completions, the\n.ndo_poll_controller is unnecessary to be implemented in the fec driver,\nso fec_poll_controller() can be safely removed.(CVE-2024-38553)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nax25: Fix reference count leak issue of net_device\r\n\r\nThere is a reference count leak issue of the object \u0026quot;net_device\u0026quot; in\nax25_dev_device_down(). When the ax25 device is shutting down, the\nax25_dev_device_down() drops the reference count of net_device one\nor zero times depending on if we goto unlock_put or not, which will\ncause memory leak.\r\n\r\nIn order to solve the above issue, decrease the reference count of\nnet_device after dev-\u0026gt;ax25_ptr is set to null.(CVE-2024-38554)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nrcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow\r\n\r\nThere is a possibility of buffer overflow in\nshow_rcu_tasks_trace_gp_kthread() if counters, passed\nto sprintf() are huge. Counter numbers, needed for this\nare unrealistically high, but buffer overflow is still\npossible.\r\n\r\nUse snprintf() with buffer size instead of sprintf().\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38577)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: bcm - Fix pointer arithmetic\r\n\r\nIn spu2_dump_omd() value of ptr is increased by ciph_key_len\ninstead of hash_iv_len which could lead to going beyond the\nbuffer boundaries.\nFix this bug by changing ciph_key_len to hash_iv_len.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38579)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential hang in nilfs_detach_log_writer()\r\n\r\nSyzbot has reported a potential hang in nilfs_detach_log_writer() called\nduring nilfs2 unmount.\r\n\r\nAnalysis revealed that this is because nilfs_segctor_sync(), which\nsynchronizes with the log writer thread, can be called after\nnilfs_segctor_destroy() terminates that thread, as shown in the call trace\nbelow:\r\n\r\nnilfs_detach_log_writer\n  nilfs_segctor_destroy\n    nilfs_segctor_kill_thread  --\u0026gt; Shut down log writer thread\n    flush_work\n      nilfs_iput_work_func\n        nilfs_dispose_list\n          iput\n            nilfs_evict_inode\n              nilfs_transaction_commit\n                nilfs_construct_segment (if inode needs sync)\n                  nilfs_segctor_sync  --\u0026gt; Attempt to synchronize with\n                                          log writer thread\n                           *** DEADLOCK ***\r\n\r\nFix this issue by changing nilfs_segctor_sync() so that the log writer\nthread returns normally without synchronizing after it terminates, and by\nforcing tasks that are already waiting to complete once after the thread\nterminates.\r\n\r\nThe skipped inode metadata flushout will then be processed together in the\nsubsequent cleanup work in nilfs_segctor_destroy().(CVE-2024-38582)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix use-after-free of timer for log writer thread\r\n\r\nPatch series \u0026quot;nilfs2: fix log writer related issues\u0026quot;.\r\n\r\nThis bug fix series covers three nilfs2 log writer-related issues,\nincluding a timer use-after-free issue and potential deadlock issue on\nunmount, and a potential freeze issue in event synchronization found\nduring their analysis.  Details are described in each commit log.\r\n\r\n\nThis patch (of 3):\r\n\r\nA use-after-free issue has been reported regarding the timer sc_timer on\nthe nilfs_sc_info structure.\r\n\r\nThe problem is that even though it is used to wake up a sleeping log\nwriter thread, sc_timer is not shut down until the nilfs_sc_info structure\nis about to be freed, and is used regardless of the thread\u0026apos;s lifetime.\r\n\r\nFix this issue by limiting the use of sc_timer only while the log writer\nthread is alive.(CVE-2024-38583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/hns: Modify the print level of CQE error\r\n\r\nToo much print may lead to a panic in kernel. Change ibdev_err() to\nibdev_err_ratelimited(), and change the printing level of cqe dump\nto debug level.(CVE-2024-38590)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\naf_unix: Fix data races in unix_release_sock/unix_stream_sendmsg\r\n\r\nA data-race condition has been identified in af_unix. In one data path,\nthe write function unix_release_sock() atomically writes to\nsk-\u0026gt;sk_shutdown using WRITE_ONCE. However, on the reader side,\nunix_stream_sendmsg() does not read it atomically. Consequently, this\nissue is causing the following KCSAN splat to occur:\r\n\r\n\tBUG: KCSAN: data-race in unix_release_sock / unix_stream_sendmsg\r\n\r\n\twrite (marked) to 0xffff88867256ddbb of 1 bytes by task 7270 on cpu 28:\n\tunix_release_sock (net/unix/af_unix.c:640)\n\tunix_release (net/unix/af_unix.c:1050)\n\tsock_close (net/socket.c:659 net/socket.c:1421)\n\t__fput (fs/file_table.c:422)\n\t__fput_sync (fs/file_table.c:508)\n\t__se_sys_close (fs/open.c:1559 fs/open.c:1541)\n\t__x64_sys_close (fs/open.c:1541)\n\tx64_sys_call (arch/x86/entry/syscall_64.c:33)\n\tdo_syscall_64 (arch/x86/entry/common.c:?)\n\tentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n\tread to 0xffff88867256ddbb of 1 bytes by task 989 on cpu 14:\n\tunix_stream_sendmsg (net/unix/af_unix.c:2273)\n\t__sock_sendmsg (net/socket.c:730 net/socket.c:745)\n\t____sys_sendmsg (net/socket.c:2584)\n\t__sys_sendmmsg (net/socket.c:2638 net/socket.c:2724)\n\t__x64_sys_sendmmsg (net/socket.c:2753 net/socket.c:2750 net/socket.c:2750)\n\tx64_sys_call (arch/x86/entry/syscall_64.c:33)\n\tdo_syscall_64 (arch/x86/entry/common.c:?)\n\tentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n\tvalue changed: 0x01 -\u0026gt; 0x03\r\n\r\nThe line numbers are related to commit dd5a440a31fa (\u0026quot;Linux 6.9-rc7\u0026quot;).\r\n\r\nCommit e1d09c2c2f57 (\u0026quot;af_unix: Fix data races around sk-\u0026gt;sk_shutdown.\u0026quot;)\naddressed a comparable issue in the past regarding sk-\u0026gt;sk_shutdown.\nHowever, it overlooked resolving this particular data path.\nThis patch only offending unix_stream_sendmsg() function, since the\nother reads seem to be protected by unix_state_lock() as discussed in(CVE-2024-38596)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nax25: Fix reference count leak issues of ax25_dev\r\n\r\nThe ax25_addr_ax25dev() and ax25_dev_device_down() exist a reference\ncount leak issue of the object \u0026quot;ax25_dev\u0026quot;.\r\n\r\nMemory leak issue in ax25_addr_ax25dev():\r\n\r\nThe reference count of the object \u0026quot;ax25_dev\u0026quot; can be increased multiple\ntimes in ax25_addr_ax25dev(). This will cause a memory leak.\r\n\r\nMemory leak issues in ax25_dev_device_down():\r\n\r\nThe reference count of ax25_dev is set to 1 in ax25_dev_device_up() and\nthen increase the reference count when ax25_dev is added to ax25_dev_list.\nAs a result, the reference count of ax25_dev is 2. But when the device is\nshutting down. The ax25_dev_device_down() drops the reference count once\nor twice depending on if we goto unlock_put or not, which will cause\nmemory leak.\r\n\r\nAs for the issue of ax25_addr_ax25dev(), it is impossible for one pointer\nto be on a list twice. So add a break in ax25_addr_ax25dev(). As for the\nissue of ax25_dev_device_down(), increase the reference count of ax25_dev\nonce in ax25_dev_device_up() and decrease the reference count of ax25_dev\nafter it is removed from the ax25_dev_list.(CVE-2024-38602)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrivers/perf: hisi: hns3: Actually use devm_add_action_or_reset()\r\n\r\npci_alloc_irq_vectors() allocates an irq vector. When devm_add_action()\nfails, the irq vector is not freed, which leads to a memory leak.\r\n\r\nReplace the devm_add_action with devm_add_action_or_reset to ensure\nthe irq vector can be destroyed when it fails.(CVE-2024-38603)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Check \u0026apos;folio\u0026apos; pointer for NULL\r\n\r\nIt can be NULL if bmap is called.(CVE-2024-38625)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: max3100: Update uart_driver_registered on driver removal\r\n\r\nThe removal of the last MAX3100 device triggers the removal of\nthe driver. However, code doesn\u0026apos;t update the respective global\nvariable and after insmod — rmmod — insmod cycle the kernel\noopses:\r\n\r\n  max3100 spi-PRP0001:01: max3100_probe: adding port 0\n  BUG: kernel NULL pointer dereference, address: 0000000000000408\n  ...\n  RIP: 0010:serial_core_register_port+0xa0/0x840\n  ...\n   max3100_probe+0x1b6/0x280 [max3100]\n   spi_probe+0x8d/0xb0\r\n\r\nUpdate the actual state so next time UART driver will be registered\nagain.\r\n\r\nHugo also noticed, that the error path in the probe also affected\nby having the variable set, and not cleared. Instead of clearing it\nmove the assignment after the successfull uart_register_driver() call.(CVE-2024-38633)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngreybus: lights: check return of get_channel_from_mode\r\n\r\nIf channel for the given node is not found we return null from\nget_channel_from_mode. Make sure we validate the return pointer\nbefore using it in two of the missing places.\r\n\r\nThis was originally reported in [0]:\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\r\n\r\n[0] https://lore.kernel.org/all/20240301190425.120605-1-m.lobanov@rosalinux.ru(CVE-2024-38637)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-buf/sw-sync: don\u0026apos;t enable IRQ from sync_print_obj()\r\n\r\nSince commit a6aa8fca4d79 (\u0026quot;dma-buf/sw-sync: Reduce irqsave/irqrestore from\nknown context\u0026quot;) by error replaced spin_unlock_irqrestore() with\nspin_unlock_irq() for both sync_debugfs_show() and sync_print_obj() despite\nsync_print_obj() is called from sync_debugfs_show(), lockdep complains\ninconsistent lock state warning.\r\n\r\nUse plain spin_{lock,unlock}() for sync_print_obj(), for\nsync_debugfs_show() is already using spin_{lock,unlock}_irq().(CVE-2024-38780)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/9p: fix uninit-value in p9_client_rpc()\r\n\r\nSyzbot with the help of KMSAN reported the following error:\r\n\r\nBUG: KMSAN: uninit-value in trace_9p_client_res include/trace/events/9p.h:146 [inline]\nBUG: KMSAN: uninit-value in p9_client_rpc+0x1314/0x1340 net/9p/client.c:754\n trace_9p_client_res include/trace/events/9p.h:146 [inline]\n p9_client_rpc+0x1314/0x1340 net/9p/client.c:754\n p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031\n v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410\n v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122\n legacy_get_tree+0x114/0x290 fs/fs_context.c:662\n vfs_get_tree+0xa7/0x570 fs/super.c:1797\n do_new_mount+0x71f/0x15e0 fs/namespace.c:3352\n path_mount+0x742/0x1f20 fs/namespace.c:3679\n do_mount fs/namespace.c:3692 [inline]\n __do_sys_mount fs/namespace.c:3898 [inline]\n __se_sys_mount+0x725/0x810 fs/namespace.c:3875\n __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nUninit was created at:\n __alloc_pages+0x9d6/0xe70 mm/page_alloc.c:4598\n __alloc_pages_node include/linux/gfp.h:238 [inline]\n alloc_pages_node include/linux/gfp.h:261 [inline]\n alloc_slab_page mm/slub.c:2175 [inline]\n allocate_slab mm/slub.c:2338 [inline]\n new_slab+0x2de/0x1400 mm/slub.c:2391\n ___slab_alloc+0x1184/0x33d0 mm/slub.c:3525\n __slab_alloc mm/slub.c:3610 [inline]\n __slab_alloc_node mm/slub.c:3663 [inline]\n slab_alloc_node mm/slub.c:3835 [inline]\n kmem_cache_alloc+0x6d3/0xbe0 mm/slub.c:3852\n p9_tag_alloc net/9p/client.c:278 [inline]\n p9_client_prepare_req+0x20a/0x1770 net/9p/client.c:641\n p9_client_rpc+0x27e/0x1340 net/9p/client.c:688\n p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031\n v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410\n v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122\n legacy_get_tree+0x114/0x290 fs/fs_context.c:662\n vfs_get_tree+0xa7/0x570 fs/super.c:1797\n do_new_mount+0x71f/0x15e0 fs/namespace.c:3352\n path_mount+0x742/0x1f20 fs/namespace.c:3679\n do_mount fs/namespace.c:3692 [inline]\n __do_sys_mount fs/namespace.c:3898 [inline]\n __se_sys_mount+0x725/0x810 fs/namespace.c:3875\n __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nIf p9_check_errors() fails early in p9_client_rpc(), req-\u0026gt;rc.tag\nwill not be properly initialized. However, trace_9p_client_res()\nends up trying to print it out anyway before p9_client_rpc()\nfinishes.\r\n\r\nFix this issue by assigning default values to p9_fcall fields\nsuch as \u0026apos;tag\u0026apos; and (just in case KMSAN unearths something new) \u0026apos;id\u0026apos;\nduring the tag allocation stage.(CVE-2024-39301)\r\n\r\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2024-39362)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()\r\n\r\nsyzbot reports a kernel bug as below:\r\n\r\nF2FS-fs (loop0): Mounted with checkpoint version = 48b305e4\n==================================================================\nBUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]\nBUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline]\nBUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600\nRead of size 1 at addr ffff88807a58c76c by task syz-executor280/5076\r\n\r\nCPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n print_address_description mm/kasan/report.c:377 [inline]\n print_report+0x169/0x550 mm/kasan/report.c:488\n kasan_report+0x143/0x180 mm/kasan/report.c:601\n f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]\n current_nat_addr fs/f2fs/node.h:213 [inline]\n f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600\n f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline]\n f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925\n ioctl_fiemap fs/ioctl.c:220 [inline]\n do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838\n __do_sys_ioctl fs/ioctl.c:902 [inline]\n __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nThe root cause is we missed to do sanity check on i_xattr_nid during\nf2fs_iget(), so that in fiemap() path, current_nat_addr() will access\nnat_bitmap w/ offset from invalid i_xattr_nid, result in triggering\nkasan bug report, fix it.(CVE-2024-39467)","status":"published","published":"2024-07-12T11:07:18Z","modified":"2026-08-18T01:18:30.542513364Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-1839","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: SOF: Fix DSP oops stack dump output contents\r\n\r\nFix @buf arg given to hex_dump_to_buffer() and stack address used\nin dump error output.(CVE-2021-47381)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nARM: 9170/1: fix panic when kasan and kprobe are enabled\r\n\r\narm32 uses software to simulate the instruction replaced\nby kprobe. some instructions may be simulated by constructing\nassembly functions. therefore, before executing instruction\nsimulation, it is necessary to construct assembly function\nexecution environment in C language through binding registers.\nafter kasan is enabled, the register binding relationship will\nbe destroyed, resulting in instruction simulation errors and\ncausing kernel panic.\r\n\r\nthe kprobe emulate instruction function is distributed in three\nfiles: actions-common.c actions-arm.c actions-thumb.c, so disable\nKASAN when compiling these files.\r\n\r\nfor example, use kprobe insert on cap_capable+20 after kasan\nenabled, the cap_capable assembly code is as follows:\n\u0026lt;cap_capable\u0026gt;:\ne92d47f0\tpush\t{r4, r5, r6, r7, r8, r9, sl, lr}\ne1a05000\tmov\tr5, r0\ne280006c\tadd\tr0, r0, #108    ; 0x6c\ne1a04001\tmov\tr4, r1\ne1a06002\tmov\tr6, r2\ne59fa090\tldr\tsl, [pc, #144]  ;\nebfc7bf8\tbl\tc03aa4b4 \u0026lt;__asan_load4\u0026gt;\ne595706c\tldr\tr7, [r5, #108]  ; 0x6c\ne2859014\tadd\tr9, r5, #20\n......\nThe emulate_ldr assembly code after enabling kasan is as follows:\nc06f1384 \u0026lt;emulate_ldr\u0026gt;:\ne92d47f0\tpush\t{r4, r5, r6, r7, r8, r9, sl, lr}\ne282803c\tadd\tr8, r2, #60     ; 0x3c\ne1a05000\tmov\tr5, r0\ne7e37855\tubfx\tr7, r5, #16, #4\ne1a00008\tmov\tr0, r8\ne1a09001\tmov\tr9, r1\ne1a04002\tmov\tr4, r2\nebf35462\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne357000f\tcmp\tr7, #15\ne7e36655\tubfx\tr6, r5, #12, #4\ne205a00f\tand\tsl, r5, #15\n0a000001\tbeq\tc06f13bc \u0026lt;emulate_ldr+0x38\u0026gt;\ne0840107\tadd\tr0, r4, r7, lsl #2\nebf3545c\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne084010a\tadd\tr0, r4, sl, lsl #2\nebf3545a\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne2890010\tadd\tr0, r9, #16\nebf35458\tbl\tc03c6530 \u0026lt;__asan_load4\u0026gt;\ne5990010\tldr\tr0, [r9, #16]\ne12fff30\tblx\tr0\ne356000f\tcm\tr6, #15\n1a000014\tbne\tc06f1430 \u0026lt;emulate_ldr+0xac\u0026gt;\ne1a06000\tmov\tr6, r0\ne2840040\tadd\tr0, r4, #64     ; 0x40\n......\r\n\r\nwhen running in emulate_ldr to simulate the ldr instruction, panic\noccurred, and the log is as follows:\nUnable to handle kernel NULL pointer dereference at virtual address\n00000090\npgd = ecb46400\n[00000090] *pgd=2e0fa003, *pmd=00000000\nInternal error: Oops: 206 [#1] SMP ARM\nPC is at cap_capable+0x14/0xb0\nLR is at emulate_ldr+0x50/0xc0\npsr: 600d0293 sp : ecd63af8  ip : 00000004  fp : c0a7c30c\nr10: 00000000  r9 : c30897f4  r8 : ecd63cd4\nr7 : 0000000f  r6 : 0000000a  r5 : e59fa090  r4 : ecd63c98\nr3 : c06ae294  r2 : 00000000  r1 : b7611300  r0 : bf4ec008\nFlags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user\nControl: 32c5387d  Table: 2d546400  DAC: 55555555\nProcess bash (pid: 1643, stack limit = 0xecd60190)\n(cap_capable) from (kprobe_handler+0x218/0x340)\n(kprobe_handler) from (kprobe_trap_handler+0x24/0x48)\n(kprobe_trap_handler) from (do_undefinstr+0x13c/0x364)\n(do_undefinstr) from (__und_svc_finish+0x0/0x30)\n(__und_svc_finish) from (cap_capable+0x18/0xb0)\n(cap_capable) from (cap_vm_enough_memory+0x38/0x48)\n(cap_vm_enough_memory) from\n(security_vm_enough_memory_mm+0x48/0x6c)\n(security_vm_enough_memory_mm) from\n(copy_process.constprop.5+0x16b4/0x25c8)\n(copy_process.constprop.5) from (_do_fork+0xe8/0x55c)\n(_do_fork) from (SyS_clone+0x1c/0x24)\n(SyS_clone) from (__sys_trace_return+0x0/0x10)\nCode: 0050a0e1 6c0080e2 0140a0e1 0260a0e1 (f801f0e7)(CVE-2021-47618)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: fix use-after-free after failure to create a snapshot\r\n\r\nAt ioctl.c:create_snapshot(), we allocate a pending snapshot structure and\nthen attach it to the transaction\u0026apos;s list of pending snapshots. After that\nwe call btrfs_commit_transaction(), and if that returns an error we jump\nto \u0026apos;fail\u0026apos; label, where we kfree() the pending snapshot structure. This can\nresult in a later use-after-free of the pending snapshot:\r\n\r\n1) We allocated the pending snapshot and added it to the transaction\u0026apos;s\n   list of pending snapshots;\r\n\r\n2) We call btrfs_commit_transaction(), and it fails either at the first\n   call to btrfs_run_delayed_refs() or btrfs_start_dirty_block_groups().\n   In both cases, we don\u0026apos;t abort the transaction and we release our\n   transaction handle. We jump to the \u0026apos;fail\u0026apos; label and free the pending\n   snapshot structure. We return with the pending snapshot still in the\n   transaction\u0026apos;s list;\r\n\r\n3) Another task commits the transaction. This time there\u0026apos;s no error at\n   all, and then during the transaction commit it accesses a pointer\n   to the pending snapshot structure that the snapshot creation task\n   has already freed, resulting in a user-after-free.\r\n\r\nThis issue could actually be detected by smatch, which produced the\nfollowing warning:\r\n\r\n  fs/btrfs/ioctl.c:843 create_snapshot() warn: \u0026apos;\u0026amp;pending_snapshot-\u0026gt;list\u0026apos; not removed from list\r\n\r\nSo fix this by not having the snapshot creation ioctl directly add the\npending snapshot to the transaction\u0026apos;s list. Instead add the pending\nsnapshot to the transaction handle, and then at btrfs_commit_transaction()\nwe add the snapshot to the list only when we can guarantee that any error\nreturned after that point will result in a transaction abort, in which\ncase the ioctl code can safely free the pending snapshot and no one can\naccess it anymore.(CVE-2022-48733)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5e: Avoid field-overflowing memcpy()\r\n\r\nIn preparation for FORTIFY_SOURCE performing compile-time and run-time\nfield bounds checking for memcpy(), memmove(), and memset(), avoid\nintentionally writing across neighboring fields.\r\n\r\nUse flexible arrays instead of zero-element arrays (which look like they\nare always overflowing) and split the cross-field memcpy() into two halves\nthat can be appropriately bounds-checked by the compiler.\r\n\r\nWe were doing:\r\n\r\n\t#define ETH_HLEN  14\n\t#define VLAN_HLEN  4\n\t...\n\t#define MLX5E_XDP_MIN_INLINE (ETH_HLEN + VLAN_HLEN)\n\t...\n        struct mlx5e_tx_wqe      *wqe  = mlx5_wq_cyc_get_wqe(wq, pi);\n\t...\n        struct mlx5_wqe_eth_seg  *eseg = \u0026amp;wqe-\u0026gt;eth;\n        struct mlx5_wqe_data_seg *dseg = wqe-\u0026gt;data;\n\t...\n\tmemcpy(eseg-\u0026gt;inline_hdr.start, xdptxd-\u0026gt;data, MLX5E_XDP_MIN_INLINE);\r\n\r\ntarget is wqe-\u0026gt;eth.inline_hdr.start (which the compiler sees as being\n2 bytes in size), but copying 18, intending to write across start\n(really vlan_tci, 2 bytes). The remaining 16 bytes get written into\nwqe-\u0026gt;data[0], covering byte_count (4 bytes), lkey (4 bytes), and addr\n(8 bytes).\r\n\r\nstruct mlx5e_tx_wqe {\n        struct mlx5_wqe_ctrl_seg   ctrl;                 /*     0    16 */\n        struct mlx5_wqe_eth_seg    eth;                  /*    16    16 */\n        struct mlx5_wqe_data_seg   data[];               /*    32     0 */\r\n\r\n        /* size: 32, cachelines: 1, members: 3 */\n        /* last cacheline: 32 bytes */\n};\r\n\r\nstruct mlx5_wqe_eth_seg {\n        u8                         swp_outer_l4_offset;  /*     0     1 */\n        u8                         swp_outer_l3_offset;  /*     1     1 */\n        u8                         swp_inner_l4_offset;  /*     2     1 */\n        u8                         swp_inner_l3_offset;  /*     3     1 */\n        u8                         cs_flags;             /*     4     1 */\n        u8                         swp_flags;            /*     5     1 */\n        __be16                     mss;                  /*     6     2 */\n        __be32                     flow_table_metadata;  /*     8     4 */\n        union {\n                struct {\n                        __be16     sz;                   /*    12     2 */\n                        u8         start[2];             /*    14     2 */\n                } inline_hdr;                            /*    12     4 */\n                struct {\n                        __be16     type;                 /*    12     2 */\n                        __be16     vlan_tci;             /*    14     2 */\n                } insert;                                /*    12     4 */\n                __be32             trailer;              /*    12     4 */\n        };                                               /*    12     4 */\r\n\r\n        /* size: 16, cachelines: 1, members: 9 */\n        /* last cacheline: 16 bytes */\n};\r\n\r\nstruct mlx5_wqe_data_seg {\n        __be32                     byte_count;           /*     0     4 */\n        __be32                     lkey;                 /*     4     4 */\n        __be64                     addr;                 /*     8     8 */\r\n\r\n        /* size: 16, cachelines: 1, members: 3 */\n        /* last cacheline: 16 bytes */\n};\r\n\r\nSo, split the memcpy() so the compiler can reason about the buffer\nsizes.\r\n\r\n\u0026quot;pahole\u0026quot; shows no size nor member offset changes to struct mlx5e_tx_wqe\nnor struct mlx5e_umr_wqe. \u0026quot;objdump -d\u0026quot; shows no meaningful object\ncode changes (i.e. only source line number induced differences and\noptimizations).(CVE-2022-48744)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: LAPIC: Also cancel preemption timer during SET_LAPIC\r\n\r\nThe below warning is splatting during guest reboot.\r\n\r\n  ------------[ cut here ]------------\n  WARNING: CPU: 0 PID: 1931 at arch/x86/kvm/x86.c:10322 kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]\n  CPU: 0 PID: 1931 Comm: qemu-system-x86 Tainted: G          I       5.17.0-rc1+ #5\n  RIP: 0010:kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kvm_vcpu_ioctl+0x279/0x710 [kvm]\n   __x64_sys_ioctl+0x83/0xb0\n   do_syscall_64+0x3b/0xc0\n   entry_SYSCALL_64_after_hwframe+0x44/0xae\n  RIP: 0033:0x7fd39797350b\r\n\r\nThis can be triggered by not exposing tsc-deadline mode and doing a reboot in\nthe guest. The lapic_shutdown() function which is called in sys_reboot path\nwill not disarm the flying timer, it just masks LVTT. lapic_shutdown() clears\nAPIC state w/ LVT_MASKED and timer-mode bit is 0, this can trigger timer-mode\nswitch between tsc-deadline and oneshot/periodic, which can result in preemption\ntimer be cancelled in apic_update_lvtt(). However, We can\u0026apos;t depend on this when\nnot exposing tsc-deadline mode and oneshot/periodic modes emulated by preemption\ntimer. Qemu will synchronise states around reset, let\u0026apos;s cancel preemption timer\nunder KVM_SET_LAPIC.(CVE-2022-48765)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: lgdt3306a: Add a check against null-pointer-def\r\n\r\nThe driver should check whether the client provides the platform_data.\r\n\r\nThe following log reveals it:\r\n\r\n[   29.610324] BUG: KASAN: null-ptr-deref in kmemdup+0x30/0x40\n[   29.610730] Read of size 40 at addr 0000000000000000 by task bash/414\n[   29.612820] Call Trace:\n[   29.613030]  \u0026lt;TASK\u0026gt;\n[   29.613201]  dump_stack_lvl+0x56/0x6f\n[   29.613496]  ? kmemdup+0x30/0x40\n[   29.613754]  print_report.cold+0x494/0x6b7\n[   29.614082]  ? kmemdup+0x30/0x40\n[   29.614340]  kasan_report+0x8a/0x190\n[   29.614628]  ? kmemdup+0x30/0x40\n[   29.614888]  kasan_check_range+0x14d/0x1d0\n[   29.615213]  memcpy+0x20/0x60\n[   29.615454]  kmemdup+0x30/0x40\n[   29.615700]  lgdt3306a_probe+0x52/0x310\n[   29.616339]  i2c_device_probe+0x951/0xa90(CVE-2022-48772)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: btusb: Add date-\u0026gt;evt_skb is NULL check\r\n\r\nfix crash because of null pointers\r\n\r\n[ 6104.969662] BUG: kernel NULL pointer dereference, address: 00000000000000c8\n[ 6104.969667] #PF: supervisor read access in kernel mode\n[ 6104.969668] #PF: error_code(0x0000) - not-present page\n[ 6104.969670] PGD 0 P4D 0\n[ 6104.969673] Oops: 0000 [#1] SMP NOPTI\n[ 6104.969684] RIP: 0010:btusb_mtk_hci_wmt_sync+0x144/0x220 [btusb]\n[ 6104.969688] RSP: 0018:ffffb8d681533d48 EFLAGS: 00010246\n[ 6104.969689] RAX: 0000000000000000 RBX: ffff8ad560bb2000 RCX: 0000000000000006\n[ 6104.969691] RDX: 0000000000000000 RSI: ffffb8d681533d08 RDI: 0000000000000000\n[ 6104.969692] RBP: ffffb8d681533d70 R08: 0000000000000001 R09: 0000000000000001\n[ 6104.969694] R10: 0000000000000001 R11: 00000000fa83b2da R12: ffff8ad461d1d7c0\n[ 6104.969695] R13: 0000000000000000 R14: ffff8ad459618c18 R15: ffffb8d681533d90\n[ 6104.969697] FS:  00007f5a1cab9d40(0000) GS:ffff8ad578200000(0000) knlGS:00000\n[ 6104.969699] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 6104.969700] CR2: 00000000000000c8 CR3: 000000018620c001 CR4: 0000000000760ef0\n[ 6104.969701] PKRU: 55555554\n[ 6104.969702] Call Trace:\n[ 6104.969708]  btusb_mtk_shutdown+0x44/0x80 [btusb]\n[ 6104.969732]  hci_dev_do_close+0x470/0x5c0 [bluetooth]\n[ 6104.969748]  hci_rfkill_set_block+0x56/0xa0 [bluetooth]\n[ 6104.969753]  rfkill_set_block+0x92/0x160\n[ 6104.969755]  rfkill_fop_write+0x136/0x1e0\n[ 6104.969759]  __vfs_write+0x18/0x40\n[ 6104.969761]  vfs_write+0xdf/0x1c0\n[ 6104.969763]  ksys_write+0xb1/0xe0\n[ 6104.969765]  __x64_sys_write+0x1a/0x20\n[ 6104.969769]  do_syscall_64+0x51/0x180\n[ 6104.969771]  entry_SYSCALL_64_after_hwframe+0x44/0xa9\n[ 6104.969773] RIP: 0033:0x7f5a21f18fef\n[ 6104.9] RSP: 002b:00007ffeefe39010 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\n[ 6104.969780] RAX: ffffffffffffffda RBX: 000055c10a7560a0 RCX: 00007f5a21f18fef\n[ 6104.969781] RDX: 0000000000000008 RSI: 00007ffeefe39060 RDI: 0000000000000012\n[ 6104.969782] RBP: 00007ffeefe39060 R08: 0000000000000000 R09: 0000000000000017\n[ 6104.969784] R10: 00007ffeefe38d97 R11: 0000000000000293 R12: 0000000000000002\n[ 6104.969785] R13: 00007ffeefe39220 R14: 00007ffeefe391a0 R15: 000055c10a72acf0(CVE-2023-52833)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngenirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline\r\n\r\nThe absence of IRQD_MOVE_PCNTXT prevents immediate effectiveness of\ninterrupt affinity reconfiguration via procfs. Instead, the change is\ndeferred until the next instance of the interrupt being triggered on the\noriginal CPU.\r\n\r\nWhen the interrupt next triggers on the original CPU, the new affinity is\nenforced within __irq_move_irq(). A vector is allocated from the new CPU,\nbut the old vector on the original CPU remains and is not immediately\nreclaimed. Instead, apicd-\u0026gt;move_in_progress is flagged, and the reclaiming\nprocess is delayed until the next trigger of the interrupt on the new CPU.\r\n\r\nUpon the subsequent triggering of the interrupt on the new CPU,\nirq_complete_move() adds a task to the old CPU\u0026apos;s vector_cleanup list if it\nremains online. Subsequently, the timer on the old CPU iterates over its\nvector_cleanup list, reclaiming old vectors.\r\n\r\nHowever, a rare scenario arises if the old CPU is outgoing before the\ninterrupt triggers again on the new CPU.\r\n\r\nIn that case irq_force_complete_move() is not invoked on the outgoing CPU\nto reclaim the old apicd-\u0026gt;prev_vector because the interrupt isn\u0026apos;t currently\naffine to the outgoing CPU, and irq_needs_fixup() returns false. Even\nthough __vector_schedule_cleanup() is later called on the new CPU, it\ndoesn\u0026apos;t reclaim apicd-\u0026gt;prev_vector; instead, it simply resets both\napicd-\u0026gt;move_in_progress and apicd-\u0026gt;prev_vector to 0.\r\n\r\nAs a result, the vector remains unreclaimed in vector_matrix, leading to a\nCPU vector leak.\r\n\r\nTo address this issue, move the invocation of irq_force_complete_move()\nbefore the irq_needs_fixup() call to reclaim apicd-\u0026gt;prev_vector, if the\ninterrupt is currently or used to be affine to the outgoing CPU.\r\n\r\nAdditionally, reclaim the vector in __vector_schedule_cleanup() as well,\nfollowing a warning message, although theoretically it should never see\napicd-\u0026gt;move_in_progress with apicd-\u0026gt;prev_cpu pointing to an offline CPU.(CVE-2024-31076)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: dynamic: Synchronize of_changeset_destroy() with the devlink removals\r\n\r\nIn the following sequence:\n  1) of_platform_depopulate()\n  2) of_overlay_remove()\r\n\r\nDuring the step 1, devices are destroyed and devlinks are removed.\nDuring the step 2, OF nodes are destroyed but\n__of_changeset_entry_destroy() can raise warnings related to missing\nof_node_put():\n  ERROR: memory leak, expected refcount 1 instead of 2 ...\r\n\r\nIndeed, during the devlink removals performed at step 1, the removal\nitself releasing the device (and the attached of_node) is done by a job\nqueued in a workqueue and so, it is done asynchronously with respect to\nfunction calls.\nWhen the warning is present, of_node_put() will be called but wrongly\ntoo late from the workqueue job.\r\n\r\nIn order to be sure that any ongoing devlink removals are done before\nthe of_node destruction, synchronize the of_changeset_destroy() with the\ndevlink removals.(CVE-2024-35879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: act_skbmod: prevent kernel-infoleak\r\n\r\nsyzbot found that tcf_skbmod_dump() was copying four bytes\nfrom kernel stack to user space [1].\r\n\r\nThe issue here is that \u0026apos;struct tc_skbmod\u0026apos; has a four bytes hole.\r\n\r\nWe need to clear the structure before filling fields.\r\n\r\n[1]\nBUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline]\n BUG: KMSAN: kernel-infoleak in copy_to_user_iter lib/iov_iter.c:24 [inline]\n BUG: KMSAN: kernel-infoleak in iterate_ubuf include/linux/iov_iter.h:29 [inline]\n BUG: KMSAN: kernel-infoleak in iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\n BUG: KMSAN: kernel-infoleak in iterate_and_advance include/linux/iov_iter.h:271 [inline]\n BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n  instrument_copy_to_user include/linux/instrumented.h:114 [inline]\n  copy_to_user_iter lib/iov_iter.c:24 [inline]\n  iterate_ubuf include/linux/iov_iter.h:29 [inline]\n  iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\n  iterate_and_advance include/linux/iov_iter.h:271 [inline]\n  _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n  copy_to_iter include/linux/uio.h:196 [inline]\n  simple_copy_to_iter net/core/datagram.c:532 [inline]\n  __skb_datagram_iter+0x185/0x1000 net/core/datagram.c:420\n  skb_copy_datagram_iter+0x5c/0x200 net/core/datagram.c:546\n  skb_copy_datagram_msg include/linux/skbuff.h:4050 [inline]\n  netlink_recvmsg+0x432/0x1610 net/netlink/af_netlink.c:1962\n  sock_recvmsg_nosec net/socket.c:1046 [inline]\n  sock_recvmsg+0x2c4/0x340 net/socket.c:1068\n  __sys_recvfrom+0x35a/0x5f0 net/socket.c:2242\n  __do_sys_recvfrom net/socket.c:2260 [inline]\n  __se_sys_recvfrom net/socket.c:2256 [inline]\n  __x64_sys_recvfrom+0x126/0x1d0 net/socket.c:2256\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nUninit was stored to memory at:\n  pskb_expand_head+0x30f/0x19d0 net/core/skbuff.c:2253\n  netlink_trim+0x2c2/0x330 net/netlink/af_netlink.c:1317\n  netlink_unicast+0x9f/0x1260 net/netlink/af_netlink.c:1351\n  nlmsg_unicast include/net/netlink.h:1144 [inline]\n  nlmsg_notify+0x21d/0x2f0 net/netlink/af_netlink.c:2610\n  rtnetlink_send+0x73/0x90 net/core/rtnetlink.c:741\n  rtnetlink_maybe_send include/linux/rtnetlink.h:17 [inline]\n  tcf_add_notify net/sched/act_api.c:2048 [inline]\n  tcf_action_add net/sched/act_api.c:2071 [inline]\n  tc_ctl_action+0x146e/0x19d0 net/sched/act_api.c:2119\n  rtnetlink_rcv_msg+0x1737/0x1900 net/core/rtnetlink.c:6595\n  netlink_rcv_skb+0x375/0x650 net/netlink/af_netlink.c:2559\n  rtnetlink_rcv+0x34/0x40 net/core/rtnetlink.c:6613\n  netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]\n  netlink_unicast+0xf4c/0x1260 net/netlink/af_netlink.c:1361\n  netlink_sendmsg+0x10df/0x11f0 net/netlink/af_netlink.c:1905\n  sock_sendmsg_nosec net/socket.c:730 [inline]\n  __sock_sendmsg+0x30f/0x380 net/socket.c:745\n  ____sys_sendmsg+0x877/0xb60 net/socket.c:2584\n  ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2638\n  __sys_sendmsg net/socket.c:2667 [inline]\n  __do_sys_sendmsg net/socket.c:2676 [inline]\n  __se_sys_sendmsg net/socket.c:2674 [inline]\n  __x64_sys_sendmsg+0x307/0x4a0 net/socket.c:2674\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nUninit was stored to memory at:\n  __nla_put lib/nlattr.c:1041 [inline]\n  nla_put+0x1c6/0x230 lib/nlattr.c:1099\n  tcf_skbmod_dump+0x23f/0xc20 net/sched/act_skbmod.c:256\n  tcf_action_dump_old net/sched/act_api.c:1191 [inline]\n  tcf_action_dump_1+0x85e/0x970 net/sched/act_api.c:1227\n  tcf_action_dump+0x1fd/0x460 net/sched/act_api.c:1251\n  tca_get_fill+0x519/0x7a0 net/sched/act_api.c:1628\n  tcf_add_notify_msg net/sched/act_api.c:2023 [inline]\n  tcf_add_notify net/sched/act_api.c:2042 [inline]\n  tcf_action_add net/sched/act_api.c:2071 [inline]\n  tc_ctl_action+0x1365/0x19d0 net/sched/act_api.c:2119\n  rtnetlink_rcv_msg+0x1737/0x1900 net/core/rtnetlink.c:6595\n  netlink_rcv_skb+0x375/0x650 net/netlink/af_netli\n---truncated---(CVE-2024-35893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr\r\n\r\nAlthough ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it\nstill means hlist_for_each_entry_rcu can return an item that got removed\nfrom the list. The memory itself of such item is not freed thanks to RCU\nbut nothing guarantees the actual content of the memory is sane.\r\n\r\nIn particular, the reference count can be zero. This can happen if\nipv6_del_addr is called in parallel. ipv6_del_addr removes the entry\nfrom inet6_addr_lst (hlist_del_init_rcu(\u0026amp;ifp-\u0026gt;addr_lst)) and drops all\nreferences (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough\ntiming, this can happen:\r\n\r\n1. In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry.\r\n\r\n2. Then, the whole ipv6_del_addr is executed for the given entry. The\n   reference count drops to zero and kfree_rcu is scheduled.\r\n\r\n3. ipv6_get_ifaddr continues and tries to increments the reference count\n   (in6_ifa_hold).\r\n\r\n4. The rcu is unlocked and the entry is freed.\r\n\r\n5. The freed entry is returned.\r\n\r\nPrevent increasing of the reference count in such case. The name\nin6_ifa_hold_safe is chosen to mimic the existing fib6_info_hold_safe.\r\n\r\n[   41.506330] refcount_t: addition on 0; use-after-free.\n[   41.506760] WARNING: CPU: 0 PID: 595 at lib/refcount.c:25 refcount_warn_saturate+0xa5/0x130\n[   41.507413] Modules linked in: veth bridge stp llc\n[   41.507821] CPU: 0 PID: 595 Comm: python3 Not tainted 6.9.0-rc2.main-00208-g49563be82afa #14\n[   41.508479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)\n[   41.509163] RIP: 0010:refcount_warn_saturate+0xa5/0x130\n[   41.509586] Code: ad ff 90 0f 0b 90 90 c3 cc cc cc cc 80 3d c0 30 ad 01 00 75 a0 c6 05 b7 30 ad 01 01 90 48 c7 c7 38 cc 7a 8c e8 cc 18 ad ff 90 \u0026lt;0f\u0026gt; 0b 90 90 c3 cc cc cc cc 80 3d 98 30 ad 01 00 0f 85 75 ff ff ff\n[   41.510956] RSP: 0018:ffffbda3c026baf0 EFLAGS: 00010282\n[   41.511368] RAX: 0000000000000000 RBX: ffff9e9c46914800 RCX: 0000000000000000\n[   41.511910] RDX: ffff9e9c7ec29c00 RSI: ffff9e9c7ec1c900 RDI: ffff9e9c7ec1c900\n[   41.512445] RBP: ffff9e9c43660c9c R08: 0000000000009ffb R09: 00000000ffffdfff\n[   41.512998] R10: 00000000ffffdfff R11: ffffffff8ca58a40 R12: ffff9e9c4339a000\n[   41.513534] R13: 0000000000000001 R14: ffff9e9c438a0000 R15: ffffbda3c026bb48\n[   41.514086] FS:  00007fbc4cda1740(0000) GS:ffff9e9c7ec00000(0000) knlGS:0000000000000000\n[   41.514726] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   41.515176] CR2: 000056233b337d88 CR3: 000000000376e006 CR4: 0000000000370ef0\n[   41.515713] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[   41.516252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[   41.516799] Call Trace:\n[   41.517037]  \u0026lt;TASK\u0026gt;\n[   41.517249]  ? __warn+0x7b/0x120\n[   41.517535]  ? refcount_warn_saturate+0xa5/0x130\n[   41.517923]  ? report_bug+0x164/0x190\n[   41.518240]  ? handle_bug+0x3d/0x70\n[   41.518541]  ? exc_invalid_op+0x17/0x70\n[   41.520972]  ? asm_exc_invalid_op+0x1a/0x20\n[   41.521325]  ? refcount_warn_saturate+0xa5/0x130\n[   41.521708]  ipv6_get_ifaddr+0xda/0xe0\n[   41.522035]  inet6_rtm_getaddr+0x342/0x3f0\n[   41.522376]  ? __pfx_inet6_rtm_getaddr+0x10/0x10\n[   41.522758]  rtnetlink_rcv_msg+0x334/0x3d0\n[   41.523102]  ? netlink_unicast+0x30f/0x390\n[   41.523445]  ? __pfx_rtnetlink_rcv_msg+0x10/0x10\n[   41.523832]  netlink_rcv_skb+0x53/0x100\n[   41.524157]  netlink_unicast+0x23b/0x390\n[   41.524484]  netlink_sendmsg+0x1f2/0x440\n[   41.524826]  __sys_sendto+0x1d8/0x1f0\n[   41.525145]  __x64_sys_sendto+0x1f/0x30\n[   41.525467]  do_syscall_64+0xa5/0x1b0\n[   41.525794]  entry_SYSCALL_64_after_hwframe+0x72/0x7a\n[   41.526213] RIP: 0033:0x7fbc4cfcea9a\n[   41.526528] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89\n[   41.527942] RSP: 002b:00007f\n---truncated---(CVE-2024-35969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: Fix TASK_SIZE on 64-bit NOMMU\r\n\r\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.(CVE-2024-35988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/arm/malidp: fix a possible null pointer dereference\r\n\r\nIn malidp_mw_connector_reset, new memory is allocated with kzalloc, but\nno check is performed. In order to prevent null pointer dereferencing,\nensure that mw_state is checked before calling\n__drm_atomic_helper_connector_reset.(CVE-2024-36014)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntls: fix missing memory barrier in tls_init\r\n\r\nIn tls_init(), a write memory barrier is missing, and store-store\nreordering may cause NULL dereference in tls_{setsockopt,getsockopt}.\r\n\r\nCPU0                               CPU1\n-----                              -----\n// In tls_init()\n// In tls_ctx_create()\nctx = kzalloc()\nctx-\u0026gt;sk_proto = READ_ONCE(sk-\u0026gt;sk_prot) -(1)\r\n\r\n// In update_sk_prot()\nWRITE_ONCE(sk-\u0026gt;sk_prot, tls_prots)     -(2)\r\n\r\n                                   // In sock_common_setsockopt()\n                                   READ_ONCE(sk-\u0026gt;sk_prot)-\u0026gt;setsockopt()\r\n\r\n                                   // In tls_{setsockopt,getsockopt}()\n                                   ctx-\u0026gt;sk_proto-\u0026gt;setsockopt()    -(3)\r\n\r\nIn the above scenario, when (1) and (2) are reordered, (3) can observe\nthe NULL value of ctx-\u0026gt;sk_proto, causing NULL dereference.\r\n\r\nTo fix it, we rely on rcu_assign_pointer() which implies the release\nbarrier semantic. By moving rcu_assign_pointer() after ctx-\u0026gt;sk_proto is\ninitialized, we can ensure that ctx-\u0026gt;sk_proto are visible when\nchanging sk-\u0026gt;sk_prot.(CVE-2024-36489)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nvirtio: delete vq in vp_find_vqs_msix() when request_irq() fails\r\n\r\nWhen request_irq() fails, error path calls vp_del_vqs(). There, as vq is\npresent in the list, free_irq() is called for the same vector. That\ncauses following splat:\r\n\r\n[    0.414355] Trying to free already-free IRQ 27\n[    0.414403] WARNING: CPU: 1 PID: 1 at kernel/irq/manage.c:1899 free_irq+0x1a1/0x2d0\n[    0.414510] Modules linked in:\n[    0.414540] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.9.0-rc4+ #27\n[    0.414540] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014\n[    0.414540] RIP: 0010:free_irq+0x1a1/0x2d0\n[    0.414540] Code: 1e 00 48 83 c4 08 48 89 e8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 90 8b 74 24 04 48 c7 c7 98 80 6c b1 e8 00 c9 f7 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 89 ee 4c 89 ef e8 e0 20 b8 00 49 8b 47 40 48 8b 40\n[    0.414540] RSP: 0000:ffffb71480013ae0 EFLAGS: 00010086\n[    0.414540] RAX: 0000000000000000 RBX: ffffa099c2722000 RCX: 0000000000000000\n[    0.414540] RDX: 0000000000000000 RSI: ffffb71480013998 RDI: 0000000000000001\n[    0.414540] RBP: 0000000000000246 R08: 00000000ffffdfff R09: 0000000000000001\n[    0.414540] R10: 00000000ffffdfff R11: ffffffffb18729c0 R12: ffffa099c1c91760\n[    0.414540] R13: ffffa099c1c916a4 R14: ffffa099c1d2f200 R15: ffffa099c1c91600\n[    0.414540] FS:  0000000000000000(0000) GS:ffffa099fec40000(0000) knlGS:0000000000000000\n[    0.414540] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    0.414540] CR2: 0000000000000000 CR3: 0000000008e3e001 CR4: 0000000000370ef0\n[    0.414540] Call Trace:\n[    0.414540]  \u0026lt;TASK\u0026gt;\n[    0.414540]  ? __warn+0x80/0x120\n[    0.414540]  ? free_irq+0x1a1/0x2d0\n[    0.414540]  ? report_bug+0x164/0x190\n[    0.414540]  ? handle_bug+0x3b/0x70\n[    0.414540]  ? exc_invalid_op+0x17/0x70\n[    0.414540]  ? asm_exc_invalid_op+0x1a/0x20\n[    0.414540]  ? free_irq+0x1a1/0x2d0\n[    0.414540]  vp_del_vqs+0xc1/0x220\n[    0.414540]  vp_find_vqs_msix+0x305/0x470\n[    0.414540]  vp_find_vqs+0x3e/0x1a0\n[    0.414540]  vp_modern_find_vqs+0x1b/0x70\n[    0.414540]  init_vqs+0x387/0x600\n[    0.414540]  virtnet_probe+0x50a/0xc80\n[    0.414540]  virtio_dev_probe+0x1e0/0x2b0\n[    0.414540]  really_probe+0xc0/0x2c0\n[    0.414540]  ? __pfx___driver_attach+0x10/0x10\n[    0.414540]  __driver_probe_device+0x73/0x120\n[    0.414540]  driver_probe_device+0x1f/0xe0\n[    0.414540]  __driver_attach+0x88/0x180\n[    0.414540]  bus_for_each_dev+0x85/0xd0\n[    0.414540]  bus_add_driver+0xec/0x1f0\n[    0.414540]  driver_register+0x59/0x100\n[    0.414540]  ? __pfx_virtio_net_driver_init+0x10/0x10\n[    0.414540]  virtio_net_driver_init+0x90/0xb0\n[    0.414540]  do_one_initcall+0x58/0x230\n[    0.414540]  kernel_init_freeable+0x1a3/0x2d0\n[    0.414540]  ? __pfx_kernel_init+0x10/0x10\n[    0.414540]  kernel_init+0x1a/0x1c0\n[    0.414540]  ret_from_fork+0x31/0x50\n[    0.414540]  ? __pfx_kernel_init+0x10/0x10\n[    0.414540]  ret_from_fork_asm+0x1a/0x30\n[    0.414540]  \u0026lt;/TASK\u0026gt;\r\n\r\nFix this by calling deleting the current vq when request_irq() fails.(CVE-2024-37353)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: fix crash on racing fsync and size-extending write into prealloc\r\n\r\nWe have been seeing crashes on duplicate keys in\nbtrfs_set_item_key_safe():\r\n\r\n  BTRFS critical (device vdb): slot 4 key (450 108 8192) new key (450 108 8192)\n  ------------[ cut here ]------------\n  kernel BUG at fs/btrfs/ctree.c:2620!\n  invalid opcode: 0000 [#1] PREEMPT SMP PTI\n  CPU: 0 PID: 3139 Comm: xfs_io Kdump: loaded Not tainted 6.9.0 #6\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:btrfs_set_item_key_safe+0x11f/0x290 [btrfs]\r\n\r\nWith the following stack trace:\r\n\r\n  #0  btrfs_set_item_key_safe (fs/btrfs/ctree.c:2620:4)\n  #1  btrfs_drop_extents (fs/btrfs/file.c:411:4)\n  #2  log_one_extent (fs/btrfs/tree-log.c:4732:9)\n  #3  btrfs_log_changed_extents (fs/btrfs/tree-log.c:4955:9)\n  #4  btrfs_log_inode (fs/btrfs/tree-log.c:6626:9)\n  #5  btrfs_log_inode_parent (fs/btrfs/tree-log.c:7070:8)\n  #6  btrfs_log_dentry_safe (fs/btrfs/tree-log.c:7171:8)\n  #7  btrfs_sync_file (fs/btrfs/file.c:1933:8)\n  #8  vfs_fsync_range (fs/sync.c:188:9)\n  #9  vfs_fsync (fs/sync.c:202:9)\n  #10 do_fsync (fs/sync.c:212:9)\n  #11 __do_sys_fdatasync (fs/sync.c:225:9)\n  #12 __se_sys_fdatasync (fs/sync.c:223:1)\n  #13 __x64_sys_fdatasync (fs/sync.c:223:1)\n  #14 do_syscall_x64 (arch/x86/entry/common.c:52:14)\n  #15 do_syscall_64 (arch/x86/entry/common.c:83:7)\n  #16 entry_SYSCALL_64+0xaf/0x14c (arch/x86/entry/entry_64.S:121)\r\n\r\nSo we\u0026apos;re logging a changed extent from fsync, which is splitting an\nextent in the log tree. But this split part already exists in the tree,\ntriggering the BUG().\r\n\r\nThis is the state of the log tree at the time of the crash, dumped with\ndrgn (https://github.com/osandov/drgn/blob/main/contrib/btrfs_tree.py)\nto get more details than btrfs_print_leaf() gives us:\r\n\r\n  \u0026gt;\u0026gt;\u0026gt; print_extent_buffer(prog.crashed_thread().stack_trace()[0][\u0026quot;eb\u0026quot;])\n  leaf 33439744 level 0 items 72 generation 9 owner 18446744073709551610\n  leaf 33439744 flags 0x100000000000000\n  fs uuid e5bd3946-400c-4223-8923-190ef1f18677\n  chunk uuid d58cb17e-6d02-494a-829a-18b7d8a399da\n          item 0 key (450 INODE_ITEM 0) itemoff 16123 itemsize 160\n                  generation 7 transid 9 size 8192 nbytes 8473563889606862198\n                  block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0\n                  sequence 204 flags 0x10(PREALLOC)\n                  atime 1716417703.220000000 (2024-05-22 15:41:43)\n                  ctime 1716417704.983333333 (2024-05-22 15:41:44)\n                  mtime 1716417704.983333333 (2024-05-22 15:41:44)\n                  otime 17592186044416.000000000 (559444-03-08 01:40:16)\n          item 1 key (450 INODE_REF 256) itemoff 16110 itemsize 13\n                  index 195 namelen 3 name: 193\n          item 2 key (450 XATTR_ITEM 1640047104) itemoff 16073 itemsize 37\n                  location key (0 UNKNOWN.0 0) type XATTR\n                  transid 7 data_len 1 name_len 6\n                  name: user.a\n                  data a\n          item 3 key (450 EXTENT_DATA 0) itemoff 16020 itemsize 53\n                  generation 9 type 1 (regular)\n                  extent data disk byte 303144960 nr 12288\n                  extent data offset 0 nr 4096 ram 12288\n                  extent compression 0 (none)\n          item 4 key (450 EXTENT_DATA 4096) itemoff 15967 itemsize 53\n                  generation 9 type 2 (prealloc)\n                  prealloc data disk byte 303144960 nr 12288\n                  prealloc data offset 4096 nr 8192\n          item 5 key (450 EXTENT_DATA 8192) itemoff 15914 itemsize 53\n                  generation 9 type 2 (prealloc)\n                  prealloc data disk byte 303144960 nr 12288\n                  prealloc data offset 8192 nr 4096\n  ...\r\n\r\nSo the real problem happened earlier: notice that items 4 (4k-12k) and 5\n(8k-12k) overlap. Both are prealloc extents. Item 4 straddles i_size and\nitem 5 starts at i_size.\r\n\r\nHere is the state of \n---truncated---(CVE-2024-37354)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: Fix uninit-value in nci_rx_work\r\n\r\nsyzbot reported the following uninit-value access issue [1]\r\n\r\nnci_rx_work() parses received packet from ndev-\u0026gt;rx_q. It should be\nvalidated header size, payload size and total packet size before\nprocessing the packet. If an invalid packet is detected, it should be\nsilently discarded.(CVE-2024-38381)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries\r\n\r\nThe allocation failure of mycs-\u0026gt;yuv_scaler_binary in load_video_binaries()\nis followed with a dereference of mycs-\u0026gt;yuv_scaler_binary after the\nfollowing call chain:\r\n\r\nsh_css_pipe_load_binaries()\n  |-\u0026gt; load_video_binaries(mycs-\u0026gt;yuv_scaler_binary == NULL)\n  |\n  |-\u0026gt; sh_css_pipe_unload_binaries()\n        |-\u0026gt; unload_video_binaries()\r\n\r\nIn unload_video_binaries(), it calls to ia_css_binary_unload with argument\n\u0026amp;pipe-\u0026gt;pipe_settings.video.yuv_scaler_binary[i], which refers to the\nsame memory slot as mycs-\u0026gt;yuv_scaler_binary. Thus, a null-pointer\ndereference is triggered.(CVE-2024-38547)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Fix potential index out of bounds in color transformation function\r\n\r\nFixes index out of bounds issue in the color transformation function.\nThe issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer\nfunction points (TRANSFER_FUNC_POINTS).\r\n\r\nThe fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the\ntransfer function points. If \u0026apos;i\u0026apos; is out of bounds, an error message is\nlogged and the function returns false to indicate an error.\r\n\r\nReported by smatch:\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:405 cm_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:406 cm_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:407 cm_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-38552)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nax25: Fix reference count leak issue of net_device\r\n\r\nThere is a reference count leak issue of the object \u0026quot;net_device\u0026quot; in\nax25_dev_device_down(). When the ax25 device is shutting down, the\nax25_dev_device_down() drops the reference count of net_device one\nor zero times depending on if we goto unlock_put or not, which will\ncause memory leak.\r\n\r\nIn order to solve the above issue, decrease the reference count of\nnet_device after dev-\u0026gt;ax25_ptr is set to null.(CVE-2024-38554)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nrcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow\r\n\r\nThere is a possibility of buffer overflow in\nshow_rcu_tasks_trace_gp_kthread() if counters, passed\nto sprintf() are huge. Counter numbers, needed for this\nare unrealistically high, but buffer overflow is still\npossible.\r\n\r\nUse snprintf() with buffer size instead of sprintf().\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38577)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: bcm - Fix pointer arithmetic\r\n\r\nIn spu2_dump_omd() value of ptr is increased by ciph_key_len\ninstead of hash_iv_len which could lead to going beyond the\nbuffer boundaries.\nFix this bug by changing ciph_key_len to hash_iv_len.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38579)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential hang in nilfs_detach_log_writer()\r\n\r\nSyzbot has reported a potential hang in nilfs_detach_log_writer() called\nduring nilfs2 unmount.\r\n\r\nAnalysis revealed that this is because nilfs_segctor_sync(), which\nsynchronizes with the log writer thread, can be called after\nnilfs_segctor_destroy() terminates that thread, as shown in the call trace\nbelow:\r\n\r\nnilfs_detach_log_writer\n  nilfs_segctor_destroy\n    nilfs_segctor_kill_thread  --\u0026gt; Shut down log writer thread\n    flush_work\n      nilfs_iput_work_func\n        nilfs_dispose_list\n          iput\n            nilfs_evict_inode\n              nilfs_transaction_commit\n                nilfs_construct_segment (if inode needs sync)\n                  nilfs_segctor_sync  --\u0026gt; Attempt to synchronize with\n                                          log writer thread\n                           *** DEADLOCK ***\r\n\r\nFix this issue by changing nilfs_segctor_sync() so that the log writer\nthread returns normally without synchronizing after it terminates, and by\nforcing tasks that are already waiting to complete once after the thread\nterminates.\r\n\r\nThe skipped inode metadata flushout will then be processed together in the\nsubsequent cleanup work in nilfs_segctor_destroy().(CVE-2024-38582)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix use-after-free of timer for log writer thread\r\n\r\nPatch series \u0026quot;nilfs2: fix log writer related issues\u0026quot;.\r\n\r\nThis bug fix series covers three nilfs2 log writer-related issues,\nincluding a timer use-after-free issue and potential deadlock issue on\nunmount, and a potential freeze issue in event synchronization found\nduring their analysis.  Details are described in each commit log.\r\n\r\n\nThis patch (of 3):\r\n\r\nA use-after-free issue has been reported regarding the timer sc_timer on\nthe nilfs_sc_info structure.\r\n\r\nThe problem is that even though it is used to wake up a sleeping log\nwriter thread, sc_timer is not shut down until the nilfs_sc_info structure\nis about to be freed, and is used regardless of the thread\u0026apos;s lifetime.\r\n\r\nFix this issue by limiting the use of sc_timer only while the log writer\nthread is alive.(CVE-2024-38583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/hns: Modify the print level of CQE error\r\n\r\nToo much print may lead to a panic in kernel. Change ibdev_err() to\nibdev_err_ratelimited(), and change the printing level of cqe dump\nto debug level.(CVE-2024-38590)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd: fix resync softlockup when bitmap size is less than array size\r\n\r\nIs is reported that for dm-raid10, lvextend + lvchange --syncaction will\ntrigger following softlockup:\r\n\r\nkernel:watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [mdX_resync:6976]\nCPU: 7 PID: 3588 Comm: mdX_resync Kdump: loaded Not tainted 6.9.0-rc4-next-20240419 #1\nRIP: 0010:_raw_spin_unlock_irq+0x13/0x30\nCall Trace:\n \u0026lt;TASK\u0026gt;\n md_bitmap_start_sync+0x6b/0xf0\n raid10_sync_request+0x25c/0x1b40 [raid10]\n md_do_sync+0x64b/0x1020\n md_thread+0xa7/0x170\n kthread+0xcf/0x100\n ret_from_fork+0x30/0x50\n ret_from_fork_asm+0x1a/0x30\r\n\r\nAnd the detailed process is as follows:\r\n\r\nmd_do_sync\n j = mddev-\u0026gt;resync_min\n while (j \u0026lt; max_sectors)\n  sectors = raid10_sync_request(mddev, j, \u0026amp;skipped)\n   if (!md_bitmap_start_sync(..., \u0026amp;sync_blocks))\n    // md_bitmap_start_sync set sync_blocks to 0\n    return sync_blocks + sectors_skippe;\n  // sectors = 0;\n  j += sectors;\n  // j never change\r\n\r\nRoot cause is that commit 301867b1c168 (\u0026quot;md/raid10: check\nslab-out-of-bounds in md_bitmap_get_counter\u0026quot;) return early from\nmd_bitmap_get_counter(), without setting returned blocks.\r\n\r\nFix this problem by always set returned blocks from\nmd_bitmap_get_counter\u0026quot;(), as it used to be.\r\n\r\nNoted that this patch just fix the softlockup problem in kernel, the\ncase that bitmap size doesn\u0026apos;t match array size still need to be fixed.(CVE-2024-38598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nax25: Fix reference count leak issues of ax25_dev\r\n\r\nThe ax25_addr_ax25dev() and ax25_dev_device_down() exist a reference\ncount leak issue of the object \u0026quot;ax25_dev\u0026quot;.\r\n\r\nMemory leak issue in ax25_addr_ax25dev():\r\n\r\nThe reference count of the object \u0026quot;ax25_dev\u0026quot; can be increased multiple\ntimes in ax25_addr_ax25dev(). This will cause a memory leak.\r\n\r\nMemory leak issues in ax25_dev_device_down():\r\n\r\nThe reference count of ax25_dev is set to 1 in ax25_dev_device_up() and\nthen increase the reference count when ax25_dev is added to ax25_dev_list.\nAs a result, the reference count of ax25_dev is 2. But when the device is\nshutting down. The ax25_dev_device_down() drops the reference count once\nor twice depending on if we goto unlock_put or not, which will cause\nmemory leak.\r\n\r\nAs for the issue of ax25_addr_ax25dev(), it is impossible for one pointer\nto be on a list twice. So add a break in ax25_addr_ax25dev(). As for the\nissue of ax25_dev_device_down(), increase the reference count of ax25_dev\nonce in ax25_dev_device_up() and decrease the reference count of ax25_dev\nafter it is removed from the ax25_dev_list.(CVE-2024-38602)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrivers/perf: hisi: hns3: Actually use devm_add_action_or_reset()\r\n\r\npci_alloc_irq_vectors() allocates an irq vector. When devm_add_action()\nfails, the irq vector is not freed, which leads to a memory leak.\r\n\r\nReplace the devm_add_action with devm_add_action_or_reset to ensure\nthe irq vector can be destroyed when it fails.(CVE-2024-38603)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncpufreq: exit() callback is optional\r\n\r\nThe exit() callback is optional and shouldn\u0026apos;t be called without checking\na valid pointer first.\r\n\r\nAlso, we must clear freq_table pointer even if the exit() callback isn\u0026apos;t\npresent.(CVE-2024-38615)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: stk1160: fix bounds checking in stk1160_copy_video()\r\n\r\nThe subtract in this condition is reversed.  The -\u0026gt;length is the length\nof the buffer.  The -\u0026gt;bytesused is how many bytes we have copied thus\nfar.  When the condition is reversed that means the result of the\nsubtraction is always negative but since it\u0026apos;s unsigned then the result\nis a very high positive value.  That means the overflow check is never\ntrue.\r\n\r\nAdditionally, the -\u0026gt;bytesused doesn\u0026apos;t actually work for this purpose\nbecause we\u0026apos;re not writing to \u0026quot;buf-\u0026gt;mem + buf-\u0026gt;bytesused\u0026quot;.  Instead, the\nmath to calculate the destination where we are writing is a bit\ninvolved.  You calculate the number of full lines already written,\nmultiply by two, skip a line if necessary so that we start on an odd\nnumbered line, and add the offset into the line.\r\n\r\nTo fix this buffer overflow, just take the actual destination where we\nare writing, if the offset is already out of bounds print an error and\nreturn.  Otherwise, write up to buf-\u0026gt;length bytes.(CVE-2024-38621)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Use variable length array instead of fixed size\r\n\r\nShould fix smatch warning:\n\tntfs_set_label() error: __builtin_memcpy() \u0026apos;uni-\u0026gt;name\u0026apos; too small (20 vs 256)(CVE-2024-38623)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Check \u0026apos;folio\u0026apos; pointer for NULL\r\n\r\nIt can be NULL if bmap is called.(CVE-2024-38625)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: max3100: Update uart_driver_registered on driver removal\r\n\r\nThe removal of the last MAX3100 device triggers the removal of\nthe driver. However, code doesn\u0026apos;t update the respective global\nvariable and after insmod — rmmod — insmod cycle the kernel\noopses:\r\n\r\n  max3100 spi-PRP0001:01: max3100_probe: adding port 0\n  BUG: kernel NULL pointer dereference, address: 0000000000000408\n  ...\n  RIP: 0010:serial_core_register_port+0xa0/0x840\n  ...\n   max3100_probe+0x1b6/0x280 [max3100]\n   spi_probe+0x8d/0xb0\r\n\r\nUpdate the actual state so next time UART driver will be registered\nagain.\r\n\r\nHugo also noticed, that the error path in the probe also affected\nby having the variable set, and not cleared. Instead of clearing it\nmove the assignment after the successfull uart_register_driver() call.(CVE-2024-38633)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: max3100: Lock port-\u0026gt;lock when calling uart_handle_cts_change()\r\n\r\nuart_handle_cts_change() has to be called with port lock taken,\nSince we run it in a separate work, the lock may not be taken at\nthe time of running. Make sure that it\u0026apos;s taken by explicitly doing\nthat. Without it we got a splat:\r\n\r\n  WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0\n  ...\n  Workqueue: max3100-0 max3100_work [max3100]\n  RIP: 0010:uart_handle_cts_change+0xa6/0xb0\n  ...\n   max3100_handlerx+0xc5/0x110 [max3100]\n   max3100_work+0x12a/0x340 [max3100](CVE-2024-38634)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngreybus: lights: check return of get_channel_from_mode\r\n\r\nIf channel for the given node is not found we return null from\nget_channel_from_mode. Make sure we validate the return pointer\nbefore using it in two of the missing places.\r\n\r\nThis was originally reported in [0]:\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\r\n\r\n[0] https://lore.kernel.org/all/20240301190425.120605-1-m.lobanov@rosalinux.ru(CVE-2024-38637)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-buf/sw-sync: don\u0026apos;t enable IRQ from sync_print_obj()\r\n\r\nSince commit a6aa8fca4d79 (\u0026quot;dma-buf/sw-sync: Reduce irqsave/irqrestore from\nknown context\u0026quot;) by error replaced spin_unlock_irqrestore() with\nspin_unlock_irq() for both sync_debugfs_show() and sync_print_obj() despite\nsync_print_obj() is called from sync_debugfs_show(), lockdep complains\ninconsistent lock state warning.\r\n\r\nUse plain spin_{lock,unlock}() for sync_print_obj(), for\nsync_debugfs_show() is already using spin_{lock,unlock}_irq().(CVE-2024-38780)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/9p: fix uninit-value in p9_client_rpc()\r\n\r\nSyzbot with the help of KMSAN reported the following error:\r\n\r\nBUG: KMSAN: uninit-value in trace_9p_client_res include/trace/events/9p.h:146 [inline]\nBUG: KMSAN: uninit-value in p9_client_rpc+0x1314/0x1340 net/9p/client.c:754\n trace_9p_client_res include/trace/events/9p.h:146 [inline]\n p9_client_rpc+0x1314/0x1340 net/9p/client.c:754\n p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031\n v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410\n v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122\n legacy_get_tree+0x114/0x290 fs/fs_context.c:662\n vfs_get_tree+0xa7/0x570 fs/super.c:1797\n do_new_mount+0x71f/0x15e0 fs/namespace.c:3352\n path_mount+0x742/0x1f20 fs/namespace.c:3679\n do_mount fs/namespace.c:3692 [inline]\n __do_sys_mount fs/namespace.c:3898 [inline]\n __se_sys_mount+0x725/0x810 fs/namespace.c:3875\n __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nUninit was created at:\n __alloc_pages+0x9d6/0xe70 mm/page_alloc.c:4598\n __alloc_pages_node include/linux/gfp.h:238 [inline]\n alloc_pages_node include/linux/gfp.h:261 [inline]\n alloc_slab_page mm/slub.c:2175 [inline]\n allocate_slab mm/slub.c:2338 [inline]\n new_slab+0x2de/0x1400 mm/slub.c:2391\n ___slab_alloc+0x1184/0x33d0 mm/slub.c:3525\n __slab_alloc mm/slub.c:3610 [inline]\n __slab_alloc_node mm/slub.c:3663 [inline]\n slab_alloc_node mm/slub.c:3835 [inline]\n kmem_cache_alloc+0x6d3/0xbe0 mm/slub.c:3852\n p9_tag_alloc net/9p/client.c:278 [inline]\n p9_client_prepare_req+0x20a/0x1770 net/9p/client.c:641\n p9_client_rpc+0x27e/0x1340 net/9p/client.c:688\n p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031\n v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410\n v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122\n legacy_get_tree+0x114/0x290 fs/fs_context.c:662\n vfs_get_tree+0xa7/0x570 fs/super.c:1797\n do_new_mount+0x71f/0x15e0 fs/namespace.c:3352\n path_mount+0x742/0x1f20 fs/namespace.c:3679\n do_mount fs/namespace.c:3692 [inline]\n __do_sys_mount fs/namespace.c:3898 [inline]\n __se_sys_mount+0x725/0x810 fs/namespace.c:3875\n __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nIf p9_check_errors() fails early in p9_client_rpc(), req-\u0026gt;rc.tag\nwill not be properly initialized. However, trace_9p_client_res()\nends up trying to print it out anyway before p9_client_rpc()\nfinishes.\r\n\r\nFix this issue by assigning default values to p9_fcall fields\nsuch as \u0026apos;tag\u0026apos; and (just in case KMSAN unearths something new) \u0026apos;id\u0026apos;\nduring the tag allocation stage.(CVE-2024-39301)\r\n\r\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2024-39362)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()\r\n\r\nsyzbot reports a kernel bug as below:\r\n\r\nF2FS-fs (loop0): Mounted with checkpoint version = 48b305e4\n==================================================================\nBUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]\nBUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline]\nBUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600\nRead of size 1 at addr ffff88807a58c76c by task syz-executor280/5076\r\n\r\nCPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n print_address_description mm/kasan/report.c:377 [inline]\n print_report+0x169/0x550 mm/kasan/report.c:488\n kasan_report+0x143/0x180 mm/kasan/report.c:601\n f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]\n current_nat_addr fs/f2fs/node.h:213 [inline]\n f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600\n f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline]\n f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925\n ioctl_fiemap fs/ioctl.c:220 [inline]\n do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838\n __do_sys_ioctl fs/ioctl.c:902 [inline]\n __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nThe root cause is we missed to do sanity check on i_xattr_nid during\nf2fs_iget(), so that in fiemap() path, current_nat_addr() will access\nnat_bitmap w/ offset from invalid i_xattr_nid, result in triggering\nkasan bug report, fix it.(CVE-2024-39467)","status":"published","published":"2024-07-12T11:07:18Z","modified":"2026-08-18T01:18:30.732582495Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"UBUNTU-CVE-2024-35988","description":"In the Linux kernel, the following vulnerability has been resolved: riscv: Fix TASK_SIZE on 64-bit NOMMU On NOMMU, userspace memory can come from anywhere in physical RAM. The current definition of TASK_SIZE is wrong if any RAM exists above 4G, causing spurious failures in the userspace access routines.","status":"published","published":"2024-05-20T10:15:00Z","modified":"2026-11-11T09:38:19.235843956Z","cvss":[{"version":"4.0","score":5.7,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"medium"},{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-11T09:59:56.348783Z"},{"id":"CVE-2024-35988","title":"riscv: Fix TASK_SIZE on 64-bit NOMMU","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Fix TASK_SIZE on 64-bit NOMMU\n\nOn NOMMU, userspace memory can come from anywhere in physical RAM. The\ncurrent definition of TASK_SIZE is wrong if any RAM exists above 4G,\ncausing spurious failures in the userspace access routines.","status":"published","published":"2024-05-20T09:47:54.391Z","modified":"2026-10-28T02:31:01.827183931Z","updated_at":"2026-11-02T15:44:40.704083Z"},{"id":"DLA-3842-1","title":"linux-5.10 - security update","status":"published","published":"2024-06-25T00:00:00Z","modified":"2026-03-09T01:22:14.203921Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"MGASA-2024-0263","title":"Updated kernel kmod-xtables-addons kmod-virtualbox dwarves packages fix security vulnerabilities","description":"Upstream kernel version 6.6.37 fix bugs and vulnerabilities.\nThe dwarves, kmod-virtualbox and kmod-xtables-addons packages have been\nupdated to work with this new kernel.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2024-07-13T07:54:44Z","modified":"2026-04-16T04:42:07.647203406Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"MGASA-2024-0266","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.37 fix bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2024-07-14T05:23:38Z","modified":"2026-04-16T04:42:58.217738372Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"USN-6898-1","title":"linux, linux-gcp, linux-gke, linux-gkeop, linux-gkeop-5.15, linux-ibm, linux-intel-iotg, linux-intel-iotg-5.15, linux-kvm, linux-nvidia, linux-oracle vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - FAT file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - Netfilter;\n  - BPF subsystem;\n  - Core kernel;\n  - PCI iomap interfaces;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - Unix domain sockets;\n  - eXpress Data Path;\n  - ALSA SH drivers;\n  - KVM core;\n(CVE-2024-35955, CVE-2024-35805, CVE-2024-26814, CVE-2024-27008,\nCVE-2024-26970, CVE-2024-35944, CVE-2024-27013, CVE-2024-35938,\nCVE-2024-35853, CVE-2024-35969, CVE-2024-26981, CVE-2024-26929,\nCVE-2024-27020, CVE-2024-35885, CVE-2024-35973, CVE-2024-35958,\nCVE-2024-26961, CVE-2024-35912, CVE-2024-35890, CVE-2024-35804,\nCVE-2024-35813, CVE-2024-27393, CVE-2024-26956, CVE-2024-35915,\nCVE-2024-26642, CVE-2024-35847, CVE-2024-26960, CVE-2024-26923,\nCVE-2024-35935, CVE-2024-36025, CVE-2024-35898, CVE-2024-26810,\nCVE-2024-35809, CVE-2024-26813, CVE-2024-36007, CVE-2024-35817,\nCVE-2024-35849, CVE-2024-35819, CVE-2024-35884, CVE-2024-35922,\nCVE-2024-36008, CVE-2024-27004, CVE-2024-35902, CVE-2024-26828,\nCVE-2024-35791, CVE-2024-35930, CVE-2024-26973, CVE-2024-26984,\nCVE-2024-35806, CVE-2024-26629, CVE-2024-26955, CVE-2024-26937,\nCVE-2024-27059, CVE-2024-35872, CVE-2024-35978, CVE-2024-26950,\nCVE-2024-27018, CVE-2024-35857, CVE-2024-35990, CVE-2024-27437,\nCVE-2024-35822, CVE-2024-36020, CVE-2024-26931, CVE-2024-26977,\nCVE-2024-26654, CVE-2024-26988, CVE-2024-36005, CVE-2024-26969,\nCVE-2024-35960, CVE-2024-27016, CVE-2024-36006, CVE-2024-35936,\nCVE-2024-35982, CVE-2024-36029, CVE-2024-27395, CVE-2024-26999,\nCVE-2024-35871, CVE-2024-35893, CVE-2024-26925, CVE-2024-26965,\nCVE-2024-35933, CVE-2024-35976, CVE-2024-35899, CVE-2024-35852,\nCVE-2024-35918, CVE-2024-26951, CVE-2024-27001, CVE-2024-35905,\nCVE-2024-35907, CVE-2024-26976, CVE-2024-27000, CVE-2024-35910,\nCVE-2024-35950, CVE-2024-26974, CVE-2024-35785, CVE-2023-52488,\nCVE-2023-52880, CVE-2024-35877, CVE-2024-35888, CVE-2024-35807,\nCVE-2024-35796, CVE-2024-35821, CVE-2024-35854, CVE-2024-27015,\nCVE-2024-35823, CVE-2024-35900, CVE-2024-35815, CVE-2024-26966,\nCVE-2024-26817, CVE-2024-35896, CVE-2024-27396, CVE-2024-27009,\nCVE-2024-35940, CVE-2024-26996, CVE-2024-35825, CVE-2024-35984,\nCVE-2024-35886, CVE-2024-27019, CVE-2024-26922, CVE-2024-35989,\nCVE-2024-26926, CVE-2024-35988, CVE-2024-26957, CVE-2024-26812,\nCVE-2024-35925, CVE-2024-35970, CVE-2024-26989, CVE-2024-26811,\nCVE-2024-35895, CVE-2024-26935, CVE-2024-26958, CVE-2024-35855,\nCVE-2024-35879, CVE-2024-26993, CVE-2024-35934, CVE-2024-36004,\nCVE-2024-35997, CVE-2024-26994, CVE-2023-52699, CVE-2024-35789,\nCVE-2024-26964, CVE-2024-26687, CVE-2024-35851, CVE-2024-35897,\nCVE-2024-26934)\n","status":"published","published":"2024-07-15T16:13:04Z","modified":"2026-10-23T10:34:35.080811398Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6898-2","title":"linux-ibm-5.15, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-oracle-5.15 vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - FAT file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - Netfilter;\n  - BPF subsystem;\n  - Core kernel;\n  - PCI iomap interfaces;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - Unix domain sockets;\n  - eXpress Data Path;\n  - ALSA SH drivers;\n  - KVM core;\n(CVE-2024-35955, CVE-2024-35805, CVE-2024-26814, CVE-2024-27008,\nCVE-2024-26970, CVE-2024-35944, CVE-2024-27013, CVE-2024-35938,\nCVE-2024-35853, CVE-2024-35969, CVE-2024-26981, CVE-2024-26929,\nCVE-2024-27020, CVE-2024-35885, CVE-2024-35973, CVE-2024-35958,\nCVE-2024-26961, CVE-2024-35912, CVE-2024-35890, CVE-2024-35804,\nCVE-2024-35813, CVE-2024-27393, CVE-2024-26956, CVE-2024-35915,\nCVE-2024-26642, CVE-2024-35847, CVE-2024-26960, CVE-2024-26923,\nCVE-2024-35935, CVE-2024-36025, CVE-2024-35898, CVE-2024-26810,\nCVE-2024-35809, CVE-2024-26813, CVE-2024-36007, CVE-2024-35817,\nCVE-2024-35849, CVE-2024-35819, CVE-2024-35884, CVE-2024-35922,\nCVE-2024-36008, CVE-2024-27004, CVE-2024-35902, CVE-2024-26828,\nCVE-2024-35791, CVE-2024-35930, CVE-2024-26973, CVE-2024-26984,\nCVE-2024-35806, CVE-2024-26629, CVE-2024-26955, CVE-2024-26937,\nCVE-2024-27059, CVE-2024-35872, CVE-2024-35978, CVE-2024-26950,\nCVE-2024-27018, CVE-2024-35857, CVE-2024-35990, CVE-2024-27437,\nCVE-2024-35822, CVE-2024-36020, CVE-2024-26931, CVE-2024-26977,\nCVE-2024-26654, CVE-2024-26988, CVE-2024-36005, CVE-2024-26969,\nCVE-2024-35960, CVE-2024-27016, CVE-2024-36006, CVE-2024-35936,\nCVE-2024-35982, CVE-2024-36029, CVE-2024-27395, CVE-2024-26999,\nCVE-2024-35871, CVE-2024-35893, CVE-2024-26925, CVE-2024-26965,\nCVE-2024-35933, CVE-2024-35976, CVE-2024-35899, CVE-2024-35852,\nCVE-2024-35918, CVE-2024-26951, CVE-2024-27001, CVE-2024-35905,\nCVE-2024-35907, CVE-2024-26976, CVE-2024-27000, CVE-2024-35910,\nCVE-2024-35950, CVE-2024-26974, CVE-2024-35785, CVE-2023-52488,\nCVE-2023-52880, CVE-2024-35877, CVE-2024-35888, CVE-2024-35807,\nCVE-2024-35796, CVE-2024-35821, CVE-2024-35854, CVE-2024-27015,\nCVE-2024-35823, CVE-2024-35900, CVE-2024-35815, CVE-2024-26966,\nCVE-2024-26817, CVE-2024-35896, CVE-2024-27396, CVE-2024-27009,\nCVE-2024-35940, CVE-2024-26996, CVE-2024-35825, CVE-2024-35984,\nCVE-2024-35886, CVE-2024-27019, CVE-2024-26922, CVE-2024-35989,\nCVE-2024-26926, CVE-2024-35988, CVE-2024-26957, CVE-2024-26812,\nCVE-2024-35925, CVE-2024-35970, CVE-2024-26989, CVE-2024-26811,\nCVE-2024-35895, CVE-2024-26935, CVE-2024-26958, CVE-2024-35855,\nCVE-2024-35879, CVE-2024-26993, CVE-2024-35934, CVE-2024-36004,\nCVE-2024-35997, CVE-2024-26994, CVE-2023-52699, CVE-2024-35789,\nCVE-2024-26964, CVE-2024-26687, CVE-2024-35851, CVE-2024-35897,\nCVE-2024-26934)\n","status":"published","published":"2024-07-17T15:09:25Z","modified":"2026-10-23T10:33:31.093486969Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6898-3","title":"linux-aws, linux-hwe-5.15 vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - FAT file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - Netfilter;\n  - BPF subsystem;\n  - Core kernel;\n  - PCI iomap interfaces;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - Unix domain sockets;\n  - eXpress Data Path;\n  - ALSA SH drivers;\n  - KVM core;\n(CVE-2024-35955, CVE-2024-35805, CVE-2024-26814, CVE-2024-27008,\nCVE-2024-26970, CVE-2024-35944, CVE-2024-27013, CVE-2024-35938,\nCVE-2024-35853, CVE-2024-35969, CVE-2024-26981, CVE-2024-26929,\nCVE-2024-27020, CVE-2024-35885, CVE-2024-35973, CVE-2024-35958,\nCVE-2024-26961, CVE-2024-35912, CVE-2024-35890, CVE-2024-35804,\nCVE-2024-35813, CVE-2024-27393, CVE-2024-26956, CVE-2024-35915,\nCVE-2024-26642, CVE-2024-35847, CVE-2024-26960, CVE-2024-26923,\nCVE-2024-35935, CVE-2024-36025, CVE-2024-35898, CVE-2024-26810,\nCVE-2024-35809, CVE-2024-26813, CVE-2024-36007, CVE-2024-35817,\nCVE-2024-35849, CVE-2024-35819, CVE-2024-35884, CVE-2024-35922,\nCVE-2024-36008, CVE-2024-27004, CVE-2024-35902, CVE-2024-26828,\nCVE-2024-35791, CVE-2024-35930, CVE-2024-26973, CVE-2024-26984,\nCVE-2024-35806, CVE-2024-26629, CVE-2024-26955, CVE-2024-26937,\nCVE-2024-27059, CVE-2024-35872, CVE-2024-35978, CVE-2024-26950,\nCVE-2024-27018, CVE-2024-35857, CVE-2024-35990, CVE-2024-27437,\nCVE-2024-35822, CVE-2024-36020, CVE-2024-26931, CVE-2024-26977,\nCVE-2024-26654, CVE-2024-26988, CVE-2024-36005, CVE-2024-26969,\nCVE-2024-35960, CVE-2024-27016, CVE-2024-36006, CVE-2024-35936,\nCVE-2024-35982, CVE-2024-36029, CVE-2024-27395, CVE-2024-26999,\nCVE-2024-35871, CVE-2024-35893, CVE-2024-26925, CVE-2024-26965,\nCVE-2024-35933, CVE-2024-35976, CVE-2024-35899, CVE-2024-35852,\nCVE-2024-35918, CVE-2024-26951, CVE-2024-27001, CVE-2024-35905,\nCVE-2024-35907, CVE-2024-26976, CVE-2024-27000, CVE-2024-35910,\nCVE-2024-35950, CVE-2024-26974, CVE-2024-35785, CVE-2023-52488,\nCVE-2023-52880, CVE-2024-35877, CVE-2024-35888, CVE-2024-35807,\nCVE-2024-35796, CVE-2024-35821, CVE-2024-35854, CVE-2024-27015,\nCVE-2024-35823, CVE-2024-35900, CVE-2024-35815, CVE-2024-26966,\nCVE-2024-26817, CVE-2024-35896, CVE-2024-27396, CVE-2024-27009,\nCVE-2024-35940, CVE-2024-26996, CVE-2024-35825, CVE-2024-35984,\nCVE-2024-35886, CVE-2024-27019, CVE-2024-26922, CVE-2024-35989,\nCVE-2024-26926, CVE-2024-35988, CVE-2024-26957, CVE-2024-26812,\nCVE-2024-35925, CVE-2024-35970, CVE-2024-26989, CVE-2024-26811,\nCVE-2024-35895, CVE-2024-26935, CVE-2024-26958, CVE-2024-35855,\nCVE-2024-35879, CVE-2024-26993, CVE-2024-35934, CVE-2024-36004,\nCVE-2024-35997, CVE-2024-26994, CVE-2023-52699, CVE-2024-35789,\nCVE-2024-26964, CVE-2024-26687, CVE-2024-35851, CVE-2024-35897,\nCVE-2024-26934)\n","status":"published","published":"2024-07-19T09:39:56Z","modified":"2026-10-23T10:33:14.792601574Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6898-4","title":"linux-aws-5.15 vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - FAT file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - Netfilter;\n  - BPF subsystem;\n  - Core kernel;\n  - PCI iomap interfaces;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - Unix domain sockets;\n  - eXpress Data Path;\n  - ALSA SH drivers;\n  - KVM core;\n(CVE-2024-35872, CVE-2024-35807, CVE-2024-27013, CVE-2024-35989,\nCVE-2024-36008, CVE-2024-26957, CVE-2024-35912, CVE-2024-27000,\nCVE-2024-35918, CVE-2024-26977, CVE-2024-35821, CVE-2024-35853,\nCVE-2024-26814, CVE-2024-35823, CVE-2024-35958, CVE-2024-26813,\nCVE-2024-26811, CVE-2024-26937, CVE-2024-26951, CVE-2024-35925,\nCVE-2024-26929, CVE-2024-35988, CVE-2024-35902, CVE-2024-26994,\nCVE-2024-27001, CVE-2024-36029, CVE-2024-36005, CVE-2024-35970,\nCVE-2024-36007, CVE-2024-35809, CVE-2024-27019, CVE-2024-26970,\nCVE-2024-27059, CVE-2024-35877, CVE-2024-35899, CVE-2024-26989,\nCVE-2024-27008, CVE-2024-26812, CVE-2024-35969, CVE-2024-35785,\nCVE-2024-35871, CVE-2024-35847, CVE-2024-36006, CVE-2024-35973,\nCVE-2024-27396, CVE-2024-35849, CVE-2024-35990, CVE-2024-26960,\nCVE-2024-26931, CVE-2024-35852, CVE-2024-26965, CVE-2024-35960,\nCVE-2024-35813, CVE-2024-26976, CVE-2024-36004, CVE-2024-35895,\nCVE-2024-27018, CVE-2024-26969, CVE-2024-27016, CVE-2024-27437,\nCVE-2024-26956, CVE-2024-26629, CVE-2024-35879, CVE-2024-35817,\nCVE-2024-26922, CVE-2024-35815, CVE-2024-35935, CVE-2024-35940,\nCVE-2023-52880, CVE-2024-35851, CVE-2024-35854, CVE-2024-35893,\nCVE-2024-26973, CVE-2024-35997, CVE-2024-26984, CVE-2024-26961,\nCVE-2024-26966, CVE-2024-35885, CVE-2024-27020, CVE-2024-26950,\nCVE-2024-35934, CVE-2024-26988, CVE-2024-35938, CVE-2024-26958,\nCVE-2024-35888, CVE-2024-27395, CVE-2024-35915, CVE-2024-35806,\nCVE-2024-26934, CVE-2024-35825, CVE-2024-35796, CVE-2024-35900,\nCVE-2024-35791, CVE-2024-26925, CVE-2024-35982, CVE-2024-26810,\nCVE-2024-26955, CVE-2024-26935, CVE-2024-35805, CVE-2024-35896,\nCVE-2024-35855, CVE-2024-35819, CVE-2024-26642, CVE-2024-27009,\nCVE-2024-35804, CVE-2024-35898, CVE-2024-35822, CVE-2024-35930,\nCVE-2024-35789, CVE-2024-26687, CVE-2024-26964, CVE-2024-35978,\nCVE-2024-35976, CVE-2024-35936, CVE-2024-26926, CVE-2024-26993,\nCVE-2024-35933, CVE-2024-35884, CVE-2024-26974, CVE-2024-35922,\nCVE-2024-35886, CVE-2024-27004, CVE-2024-36020, CVE-2024-35955,\nCVE-2024-26996, CVE-2024-26981, CVE-2024-36025, CVE-2024-26654,\nCVE-2024-27015, CVE-2024-35984, CVE-2024-26828, CVE-2024-35950,\nCVE-2024-35944, CVE-2024-35905, CVE-2024-35890, CVE-2024-26923,\nCVE-2024-35897, CVE-2024-27393, CVE-2023-52699, CVE-2024-26817,\nCVE-2024-35910, CVE-2024-35857, CVE-2024-35907, CVE-2023-52488,\nCVE-2024-26999)\n","status":"published","published":"2024-07-23T09:43:14Z","modified":"2026-10-23T10:33:09.145877861Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6917-1","title":"linux-azure, linux-azure-5.15, linux-azure-fde, linux-azure-fde-5.15 vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - FAT file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - Netfilter;\n  - BPF subsystem;\n  - Core kernel;\n  - PCI iomap interfaces;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - Unix domain sockets;\n  - eXpress Data Path;\n  - Key management;\n  - ALSA SH drivers;\n  - KVM core;\n(CVE-2024-26993, CVE-2024-26996, CVE-2024-35879, CVE-2024-26812,\nCVE-2024-26984, CVE-2024-26817, CVE-2024-35950, CVE-2024-26960,\nCVE-2024-27437, CVE-2024-26964, CVE-2024-27059, CVE-2024-35969,\nCVE-2024-35936, CVE-2024-35912, CVE-2024-35915, CVE-2024-35938,\nCVE-2024-27019, CVE-2024-35822, CVE-2024-35997, CVE-2024-35855,\nCVE-2024-26925, CVE-2024-26654, CVE-2024-26923, CVE-2024-36031,\nCVE-2024-36020, CVE-2024-35823, CVE-2024-35852, CVE-2024-35989,\nCVE-2024-27000, CVE-2024-35853, CVE-2024-27013, CVE-2024-35854,\nCVE-2024-35922, CVE-2024-26937, CVE-2023-52880, CVE-2024-26974,\nCVE-2024-26629, CVE-2024-35804, CVE-2024-35958, CVE-2024-26814,\nCVE-2024-35890, CVE-2024-35940, CVE-2024-26999, CVE-2024-35847,\nCVE-2024-27015, CVE-2024-26687, CVE-2024-26970, CVE-2024-35930,\nCVE-2024-26813, CVE-2024-26810, CVE-2024-26969, CVE-2024-26977,\nCVE-2024-26956, CVE-2024-35901, CVE-2024-27020, CVE-2024-35905,\nCVE-2024-35785, CVE-2024-27009, CVE-2024-35877, CVE-2024-35893,\nCVE-2024-26989, CVE-2024-26642, CVE-2024-35857, CVE-2024-35935,\nCVE-2024-26828, CVE-2024-26965, CVE-2024-35888, CVE-2024-35900,\nCVE-2024-26951, CVE-2024-35809, CVE-2024-27008, CVE-2024-26958,\nCVE-2024-35973, CVE-2024-26935, CVE-2024-26934, CVE-2024-35982,\nCVE-2023-52488, CVE-2024-35884, CVE-2024-35907, CVE-2024-27018,\nCVE-2024-26929, CVE-2024-35984, CVE-2024-35899, CVE-2024-26976,\nCVE-2024-26922, CVE-2024-35817, CVE-2024-26961, CVE-2024-35925,\nCVE-2024-35821, CVE-2024-36005, CVE-2024-35988, CVE-2024-35970,\nCVE-2024-27001, CVE-2024-35960, CVE-2022-48808, CVE-2024-35927,\nCVE-2024-35806, CVE-2024-27016, CVE-2024-35897, CVE-2024-26957,\nCVE-2024-36025, CVE-2024-35872, CVE-2024-26988, CVE-2024-35819,\nCVE-2024-35896, CVE-2024-36007, CVE-2024-35944, CVE-2024-35990,\nCVE-2024-36006, CVE-2024-36004, CVE-2024-35955, CVE-2024-35898,\nCVE-2024-26973, CVE-2024-26950, CVE-2024-36008, CVE-2024-35805,\nCVE-2024-35807, CVE-2024-35934, CVE-2024-26926, CVE-2024-35902,\nCVE-2024-35918, CVE-2024-35895, CVE-2024-35978, CVE-2024-35849,\nCVE-2024-35791, CVE-2024-26931, CVE-2024-35886, CVE-2024-26981,\nCVE-2024-27395, CVE-2024-35815, CVE-2024-26994, CVE-2024-35825,\nCVE-2024-35789, CVE-2024-35813, CVE-2024-35885, CVE-2024-35851,\nCVE-2024-35796, CVE-2023-52699, CVE-2024-35871, CVE-2024-26811,\nCVE-2024-26966, CVE-2024-35976, CVE-2024-26955, CVE-2024-36029,\nCVE-2024-27396, CVE-2024-27004, CVE-2024-27393, CVE-2024-35910,\nCVE-2024-35933)\n","status":"published","published":"2024-07-26T13:52:00Z","modified":"2026-10-26T22:31:46.738868768Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6919-1","title":"linux-raspi vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nIt was discovered that the ATA over Ethernet (AoE) driver in the Linux\nkernel contained a race condition, leading to a use-after-free\nvulnerability. An attacker could use this to cause a denial of service or\npossibly execute arbitrary code. (CVE-2023-6270)\n\nIt was discovered that the Atheros 802.11ac wireless driver did not\nproperly validate certain data structures, leading to a NULL pointer\ndereference. An attacker could possibly use this to cause a denial of\nservice. (CVE-2023-7042)\n\nIt was discovered that the HugeTLB file system component of the Linux\nKernel contained a NULL pointer dereference vulnerability. A privileged\nattacker could possibly use this to to cause a denial of service.\n(CVE-2024-0841)\n\nIt was discovered that the Intel Data Streaming and Intel Analytics\nAccelerator drivers in the Linux kernel allowed direct access to the\ndevices for unprivileged users and virtual machines. A local attacker could\nuse this to cause a denial of service. (CVE-2024-21823)\n\nYuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux\nKernel contained a race condition, leading to a NULL pointer dereference.\nAn attacker could possibly use this to cause a denial of service (system\ncrash). (CVE-2024-22099)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - EFI core;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - MediaTek PM domains;\n  - Power supply drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - BPF subsystem;\n  - Netfilter;\n  - TLS protocol;\n  - io_uring subsystem;\n  - Core kernel;\n  - PCI iomap interfaces;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - Netlink;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - ALSA SH drivers;\n  - USB sound devices;\n  - KVM core;\n(CVE-2024-26984, CVE-2024-26838, CVE-2024-26925, CVE-2024-26790,\nCVE-2024-26955, CVE-2024-27431, CVE-2024-26737, CVE-2024-27044,\nCVE-2024-26964, CVE-2024-26880, CVE-2024-26926, CVE-2024-26843,\nCVE-2024-26735, CVE-2024-26881, CVE-2023-52644, CVE-2024-26747,\nCVE-2024-27405, CVE-2024-26875, CVE-2024-35896, CVE-2024-35829,\nCVE-2024-26877, CVE-2024-26855, CVE-2024-27414, CVE-2024-35897,\nCVE-2024-35845, CVE-2024-26601, CVE-2024-35817, CVE-2024-36006,\nCVE-2024-26957, CVE-2024-27019, CVE-2024-35830, CVE-2024-26977,\nCVE-2024-26803, CVE-2024-26629, CVE-2024-26994, CVE-2024-27078,\nCVE-2024-35789, CVE-2023-52641, CVE-2024-27016, CVE-2024-26752,\nCVE-2024-27028, CVE-2024-26817, CVE-2024-26840, CVE-2024-26969,\nCVE-2024-26965, CVE-2023-52656, CVE-2024-35973, CVE-2024-35852,\nCVE-2024-26651, CVE-2024-27432, CVE-2024-27416, CVE-2024-26792,\nCVE-2024-35877, CVE-2024-26584, CVE-2024-26903, CVE-2024-26951,\nCVE-2024-36004, CVE-2024-26861, CVE-2024-27412, CVE-2024-26788,\nCVE-2024-35813, CVE-2024-26931, CVE-2023-52620, CVE-2024-27075,\nCVE-2024-36008, CVE-2024-35855, CVE-2024-27059, CVE-2024-35806,\nCVE-2024-26763, CVE-2024-35955, CVE-2024-35936, CVE-2024-26856,\nCVE-2024-26966, CVE-2024-35969, CVE-2024-35960, CVE-2024-35796,\nCVE-2024-26810, CVE-2024-26862, CVE-2023-52434, CVE-2024-27046,\nCVE-2024-26999, CVE-2024-26778, CVE-2023-52497, CVE-2024-35872,\nCVE-2024-26585, CVE-2024-35978, CVE-2024-35918, CVE-2024-35879,\nCVE-2024-27388, CVE-2024-26898, CVE-2024-26879, CVE-2024-26882,\nCVE-2023-52650, CVE-2024-35884, CVE-2024-27396, CVE-2024-35785,\nCVE-2024-36005, CVE-2024-35989, CVE-2023-52662, CVE-2024-35857,\nCVE-2024-26828, CVE-2024-27054, CVE-2024-26688, CVE-2024-35997,\nCVE-2024-26603, CVE-2024-26820, CVE-2024-35915, CVE-2024-35982,\nCVE-2024-26874, CVE-2024-26801, CVE-2024-26814, CVE-2024-27045,\nCVE-2024-26897, CVE-2024-35895, CVE-2024-35944, CVE-2024-35804,\nCVE-2024-26805, CVE-2024-27052, CVE-2024-35851, CVE-2024-35900,\nCVE-2024-35807, CVE-2024-26816, CVE-2024-26769, CVE-2024-27004,\nCVE-2024-27001, CVE-2024-27415, CVE-2024-35825, CVE-2024-26777,\nCVE-2024-27000, CVE-2024-27030, CVE-2024-26878, CVE-2024-26804,\nCVE-2024-27051, CVE-2024-26934, CVE-2024-27043, CVE-2024-26791,\nCVE-2024-27009, CVE-2024-26795, CVE-2023-52640, CVE-2024-35893,\nCVE-2024-35898, CVE-2024-26859, CVE-2024-27393, CVE-2024-26766,\nCVE-2024-26659, CVE-2024-26642, CVE-2024-26989, CVE-2024-26811,\nCVE-2024-26846, CVE-2024-26743, CVE-2024-35823, CVE-2024-27076,\nCVE-2024-26935, CVE-2023-52645, CVE-2024-26813, CVE-2024-26782,\nCVE-2024-26970, CVE-2024-26915, CVE-2024-27039, CVE-2024-26906,\nCVE-2024-35791, CVE-2024-35990, CVE-2024-26845, CVE-2024-35805,\nCVE-2024-35912, CVE-2024-27437, CVE-2024-27436, CVE-2024-26772,\nCVE-2024-26812, CVE-2024-26754, CVE-2024-26958, CVE-2024-26956,\nCVE-2024-26749, CVE-2024-27413, CVE-2024-27037, CVE-2023-52447,\nCVE-2024-27403, CVE-2023-52652, CVE-2024-36025, CVE-2024-26996,\nCVE-2024-35847, CVE-2022-48808, CVE-2024-26976, CVE-2024-26802,\nCVE-2024-36020, CVE-2024-27034, CVE-2024-26993, CVE-2024-27065,\nCVE-2024-35930, CVE-2024-26774, CVE-2024-26872, CVE-2024-26924,\nCVE-2024-26852, CVE-2024-26923, CVE-2024-26771, CVE-2024-35933,\nCVE-2024-35925, CVE-2024-26937, CVE-2024-26894, CVE-2024-26839,\nCVE-2024-35899, CVE-2024-26889, CVE-2024-35958, CVE-2024-35885,\nCVE-2024-35828, CVE-2024-26870, CVE-2024-26583, CVE-2024-26736,\nCVE-2024-35938, CVE-2024-26793, CVE-2024-26891, CVE-2024-35910,\nCVE-2024-26654, CVE-2024-35940, CVE-2024-26851, CVE-2024-35984,\nCVE-2024-26809, CVE-2024-35819, CVE-2024-35821, CVE-2024-26643,\nCVE-2024-36029, CVE-2024-35888, CVE-2024-27390, CVE-2024-26773,\nCVE-2024-26733, CVE-2024-26961, CVE-2024-35822, CVE-2024-35854,\nCVE-2024-35950, CVE-2024-35970, CVE-2024-27053, CVE-2024-26907,\nCVE-2024-26776, CVE-2024-26748, CVE-2024-26988, CVE-2024-35935,\nCVE-2024-26744, CVE-2024-27008, CVE-2024-35905, CVE-2024-26974,\nCVE-2024-26950, CVE-2024-26787, CVE-2024-27077, CVE-2024-35886,\nCVE-2024-35907, CVE-2024-27020, CVE-2024-26764, CVE-2024-26835,\nCVE-2024-35988, CVE-2024-26687, CVE-2024-35809, CVE-2024-35844,\nCVE-2024-26901, CVE-2024-26848, CVE-2024-26857, CVE-2024-26751,\nCVE-2024-27074, CVE-2024-26885, CVE-2024-26884, CVE-2024-27410,\nCVE-2024-35871, CVE-2024-26883, CVE-2023-52699, CVE-2024-35922,\nCVE-2024-26895, CVE-2024-26798, CVE-2024-26981, CVE-2024-27013,\nCVE-2024-27419, CVE-2024-26779, CVE-2024-27395, CVE-2024-27015,\nCVE-2024-35890, CVE-2024-26863, CVE-2024-26922, CVE-2024-27417,\nCVE-2023-52488, CVE-2024-26929, CVE-2024-26960, CVE-2024-26833,\nCVE-2024-26750, CVE-2024-27024, CVE-2024-36007, CVE-2024-27047,\nCVE-2024-35853, CVE-2024-26973, CVE-2024-27038, CVE-2024-35934,\nCVE-2024-27073, CVE-2024-35849, CVE-2023-52880, CVE-2024-35976)\n","status":"published","published":"2024-07-26T15:11:55Z","modified":"2026-10-27T04:15:56.421672634Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6927-1","title":"linux-gcp-5.15 vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nBenedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde\ndiscovered that an untrusted hypervisor could inject malicious #VC\ninterrupts and compromise the security guarantees of AMD SEV-SNP. This flaw\nis known as WeSee. A local attacker in control of the hypervisor could use\nthis to expose sensitive information or possibly execute arbitrary code in\nthe trusted execution environment. (CVE-2024-25742)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - FAT file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - Netfilter;\n  - BPF subsystem;\n  - Core kernel;\n  - PCI iomap interfaces;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - Unix domain sockets;\n  - eXpress Data Path;\n  - ALSA SH drivers;\n  - KVM core;\n(CVE-2024-35902, CVE-2024-35958, CVE-2024-35978, CVE-2024-35886,\nCVE-2024-35807, CVE-2024-26994, CVE-2024-36004, CVE-2024-35955,\nCVE-2024-26925, CVE-2024-27059, CVE-2024-35989, CVE-2024-35940,\nCVE-2024-26952, CVE-2024-35907, CVE-2024-35819, CVE-2024-35872,\nCVE-2024-36016, CVE-2023-52488, CVE-2024-35884, CVE-2024-26886,\nCVE-2024-27018, CVE-2024-35905, CVE-2024-35897, CVE-2024-26929,\nCVE-2024-36007, CVE-2024-35855, CVE-2024-35885, CVE-2024-26965,\nCVE-2024-35896, CVE-2024-36029, CVE-2024-35813, CVE-2024-26811,\nCVE-2024-26923, CVE-2024-26961, CVE-2024-26958, CVE-2024-35997,\nCVE-2024-35809, CVE-2024-27396, CVE-2023-52880, CVE-2024-26966,\nCVE-2024-27017, CVE-2024-26812, CVE-2024-35960, CVE-2024-35805,\nCVE-2024-35982, CVE-2024-35976, CVE-2024-35888, CVE-2024-26955,\nCVE-2024-27019, CVE-2024-35970, CVE-2024-35984, CVE-2024-27393,\nCVE-2024-26977, CVE-2024-27000, CVE-2024-35918, CVE-2024-26937,\nCVE-2024-35785, CVE-2024-35933, CVE-2024-26973, CVE-2022-48808,\nCVE-2024-35922, CVE-2024-35915, CVE-2024-35806, CVE-2024-26976,\nCVE-2024-26934, CVE-2024-26981, CVE-2024-36005, CVE-2024-26935,\nCVE-2024-26960, CVE-2024-26642, CVE-2024-27395, CVE-2024-35900,\nCVE-2024-26814, CVE-2024-26922, CVE-2024-35804, CVE-2024-26957,\nCVE-2024-35930, CVE-2023-52699, CVE-2024-36020, CVE-2024-35796,\nCVE-2024-35934, CVE-2024-26931, CVE-2024-35899, CVE-2024-27004,\nCVE-2024-35853, CVE-2024-35871, CVE-2024-26984, CVE-2024-35925,\nCVE-2024-35969, CVE-2024-35789, CVE-2024-35879, CVE-2024-36006,\nCVE-2024-26813, CVE-2024-35988, CVE-2024-36008, CVE-2024-35910,\nCVE-2024-35791, CVE-2024-26974, CVE-2024-26993, CVE-2024-35849,\nCVE-2024-26926, CVE-2024-35877, CVE-2024-26989, CVE-2024-35935,\nCVE-2024-26817, CVE-2024-35912, CVE-2024-27013, CVE-2024-35973,\nCVE-2024-35890, CVE-2024-35823, CVE-2024-35822, CVE-2024-27015,\nCVE-2024-35944, CVE-2024-35821, CVE-2024-26687, CVE-2024-27009,\nCVE-2024-35895, CVE-2024-35852, CVE-2024-35893, CVE-2024-26810,\nCVE-2024-26950, CVE-2024-35817, CVE-2024-26996, CVE-2024-27020,\nCVE-2024-35990, CVE-2024-26956, CVE-2024-27001, CVE-2024-26988,\nCVE-2024-26629, CVE-2024-26654, CVE-2024-35851, CVE-2024-27437,\nCVE-2024-35854, CVE-2024-35857, CVE-2024-26964, CVE-2024-35847,\nCVE-2024-35936, CVE-2023-52752, CVE-2024-36025, CVE-2024-26924,\nCVE-2024-26643, CVE-2024-26969, CVE-2024-35950, CVE-2024-35825,\nCVE-2024-27016, CVE-2024-35938, CVE-2024-26999, CVE-2024-35898,\nCVE-2024-26828, CVE-2024-35815, CVE-2024-26970, CVE-2024-26951,\nCVE-2024-27008)\n","status":"published","published":"2024-07-30T11:26:31Z","modified":"2026-10-26T22:31:40.727150652Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6949-1","title":"linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-nvidia, linux-nvidia-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - M68K architecture;\n  - OpenRISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - FireWire subsystem;\n  - EFI core;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - MMC subsystem;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Device tree and open firmware driver;\n  - HiSilicon SoC PMU drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Thermal drivers;\n  - Userspace I/O drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - ACRN Hypervisor Service Module driver;\n  - Virtio drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - eCrypt file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - Network file systems library;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Mellanox drivers;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Slab allocator;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Core kernel;\n  - BPF subsystem;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Dynamic debug library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Heterogeneous memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - Kirkwood ASoC drivers;\n  - MediaTek ASoC drivers;\n(CVE-2024-36006, CVE-2024-36922, CVE-2024-38567, CVE-2024-38584,\nCVE-2024-36923, CVE-2024-36892, CVE-2024-35855, CVE-2024-35853,\nCVE-2024-38562, CVE-2024-36920, CVE-2024-38543, CVE-2024-38576,\nCVE-2024-38572, CVE-2024-36898, CVE-2024-38560, CVE-2024-36004,\nCVE-2024-36956, CVE-2024-36881, CVE-2024-36977, CVE-2024-36955,\nCVE-2024-36906, CVE-2024-36013, CVE-2024-36884, CVE-2024-38563,\nCVE-2024-36966, CVE-2024-38547, CVE-2024-38594, CVE-2024-36926,\nCVE-2024-38587, CVE-2024-38566, CVE-2024-27400, CVE-2024-36941,\nCVE-2024-36017, CVE-2024-38544, CVE-2024-36899, CVE-2024-35851,\nCVE-2024-38577, CVE-2024-38590, CVE-2024-38568, CVE-2024-38559,\nCVE-2024-38611, CVE-2024-36887, CVE-2024-36886, CVE-2024-35996,\nCVE-2024-38612, CVE-2024-36925, CVE-2024-38586, CVE-2024-38596,\nCVE-2024-36932, CVE-2024-39482, CVE-2024-38585, CVE-2024-36033,\nCVE-2024-38614, CVE-2024-35852, CVE-2024-36908, CVE-2024-36939,\nCVE-2024-36963, CVE-2024-27401, CVE-2024-36029, CVE-2024-38540,\nCVE-2024-38565, CVE-2024-36927, CVE-2024-36910, CVE-2024-42134,\nCVE-2024-36888, CVE-2024-35859, CVE-2024-36911, CVE-2024-35947,\nCVE-2024-36940, CVE-2024-36921, CVE-2024-36913, CVE-2024-36943,\nCVE-2024-35986, CVE-2024-38616, CVE-2024-36900, CVE-2024-36954,\nCVE-2024-36915, CVE-2024-38602, CVE-2024-41011, CVE-2024-35991,\nCVE-2024-36909, CVE-2024-38603, CVE-2023-52882, CVE-2024-36953,\nCVE-2024-38599, CVE-2024-38574, CVE-2024-36967, CVE-2024-36895,\nCVE-2024-36003, CVE-2024-36961, CVE-2024-38545, CVE-2024-38538,\nCVE-2024-36001, CVE-2024-36912, CVE-2024-36952, CVE-2024-38550,\nCVE-2024-38570, CVE-2024-36969, CVE-2024-38595, CVE-2024-35849,\nCVE-2024-36936, CVE-2024-35949, CVE-2024-36009, CVE-2024-35987,\nCVE-2024-38541, CVE-2024-38564, CVE-2024-36032, CVE-2024-38615,\nCVE-2024-36960, CVE-2024-36934, CVE-2024-36951, CVE-2024-35999,\nCVE-2024-38551, CVE-2024-36903, CVE-2024-36931, CVE-2024-38593,\nCVE-2024-36938, CVE-2024-38607, CVE-2024-36928, CVE-2024-38552,\nCVE-2024-36002, CVE-2024-38605, CVE-2024-38582, CVE-2024-36933,\nCVE-2024-38620, CVE-2024-27395, CVE-2024-27396, CVE-2024-36012,\nCVE-2024-38591, CVE-2024-38597, CVE-2024-36889, CVE-2024-36964,\nCVE-2024-38606, CVE-2024-38553, CVE-2024-36945, CVE-2024-35848,\nCVE-2024-36962, CVE-2024-36947, CVE-2024-27399, CVE-2024-38546,\nCVE-2024-38583, CVE-2024-38573, CVE-2024-35850, CVE-2024-38549,\nCVE-2024-38588, CVE-2024-38610, CVE-2024-36917, CVE-2024-36957,\nCVE-2024-35846, CVE-2024-38579, CVE-2024-36965, CVE-2024-35857,\nCVE-2024-38548, CVE-2024-36975, CVE-2024-36919, CVE-2024-38542,\nCVE-2024-36948, CVE-2024-36011, CVE-2024-38556, CVE-2024-36897,\nCVE-2024-38557, CVE-2024-36890, CVE-2024-36882, CVE-2024-38613,\nCVE-2024-36914, CVE-2024-35998, CVE-2024-36958, CVE-2024-38580,\nCVE-2024-36896, CVE-2024-36891, CVE-2024-36924, CVE-2024-38589,\nCVE-2024-38592, CVE-2024-36904, CVE-2024-36894, CVE-2024-36028,\nCVE-2024-36014, CVE-2024-36880, CVE-2024-36944, CVE-2024-38598,\nCVE-2024-36929, CVE-2024-36883, CVE-2024-35858, CVE-2024-38555,\nCVE-2024-36005, CVE-2024-38539, CVE-2024-35994, CVE-2024-36030,\nCVE-2024-27394, CVE-2024-36930, CVE-2024-36937, CVE-2024-38561,\nCVE-2024-38578, CVE-2024-36959, CVE-2024-36935, CVE-2024-36916,\nCVE-2024-36902, CVE-2024-38604, CVE-2024-38554, CVE-2024-38575,\nCVE-2024-36918, CVE-2024-36979, CVE-2024-35854, CVE-2024-36968,\nCVE-2024-38558, CVE-2024-36000, CVE-2024-27398, CVE-2024-35983,\nCVE-2024-36949, CVE-2024-38600, CVE-2024-36950, CVE-2024-36946,\nCVE-2024-36031, CVE-2024-35847, CVE-2024-36905, CVE-2024-38571,\nCVE-2024-36007, CVE-2024-35856, CVE-2024-38601, CVE-2024-38569,\nCVE-2024-38617, CVE-2024-35988, CVE-2024-35989, CVE-2024-35993,\nCVE-2024-36893, CVE-2024-36901)\n","status":"published","published":"2024-08-08T21:48:26Z","modified":"2026-10-26T22:31:34.27064585Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6949-2","title":"linux-lowlatency, linux-raspi vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - M68K architecture;\n  - OpenRISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - FireWire subsystem;\n  - EFI core;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - MMC subsystem;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Device tree and open firmware driver;\n  - HiSilicon SoC PMU drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Thermal drivers;\n  - Userspace I/O drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - ACRN Hypervisor Service Module driver;\n  - Virtio drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - eCrypt file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - Network file systems library;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Mellanox drivers;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Slab allocator;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Core kernel;\n  - BPF subsystem;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Dynamic debug library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Heterogeneous memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - Kirkwood ASoC drivers;\n  - MediaTek ASoC drivers;\n(CVE-2024-36006, CVE-2024-36922, CVE-2024-38567, CVE-2024-38584,\nCVE-2024-36923, CVE-2024-36892, CVE-2024-35855, CVE-2024-35853,\nCVE-2024-38562, CVE-2024-36920, CVE-2024-38543, CVE-2024-38576,\nCVE-2024-38572, CVE-2024-36898, CVE-2024-38560, CVE-2024-36004,\nCVE-2024-36956, CVE-2024-36881, CVE-2024-36977, CVE-2024-36955,\nCVE-2024-36906, CVE-2024-36013, CVE-2024-36884, CVE-2024-38563,\nCVE-2024-36966, CVE-2024-38547, CVE-2024-38594, CVE-2024-36926,\nCVE-2024-38587, CVE-2024-38566, CVE-2024-27400, CVE-2024-36941,\nCVE-2024-36017, CVE-2024-38544, CVE-2024-36899, CVE-2024-35851,\nCVE-2024-38577, CVE-2024-38590, CVE-2024-38568, CVE-2024-38559,\nCVE-2024-38611, CVE-2024-36887, CVE-2024-36886, CVE-2024-35996,\nCVE-2024-38612, CVE-2024-36925, CVE-2024-38586, CVE-2024-38596,\nCVE-2024-36932, CVE-2024-39482, CVE-2024-38585, CVE-2024-36033,\nCVE-2024-38614, CVE-2024-35852, CVE-2024-36908, CVE-2024-36939,\nCVE-2024-36963, CVE-2024-27401, CVE-2024-36029, CVE-2024-38540,\nCVE-2024-38565, CVE-2024-36927, CVE-2024-36910, CVE-2024-42134,\nCVE-2024-36888, CVE-2024-35859, CVE-2024-36911, CVE-2024-35947,\nCVE-2024-36940, CVE-2024-36921, CVE-2024-36913, CVE-2024-36943,\nCVE-2024-35986, CVE-2024-38616, CVE-2024-36900, CVE-2024-36954,\nCVE-2024-36915, CVE-2024-38602, CVE-2024-41011, CVE-2024-35991,\nCVE-2024-36909, CVE-2024-38603, CVE-2023-52882, CVE-2024-36953,\nCVE-2024-38599, CVE-2024-38574, CVE-2024-36967, CVE-2024-36895,\nCVE-2024-36003, CVE-2024-36961, CVE-2024-38545, CVE-2024-38538,\nCVE-2024-36001, CVE-2024-36912, CVE-2024-36952, CVE-2024-38550,\nCVE-2024-38570, CVE-2024-36969, CVE-2024-38595, CVE-2024-35849,\nCVE-2024-36936, CVE-2024-35949, CVE-2024-36009, CVE-2024-35987,\nCVE-2024-38541, CVE-2024-38564, CVE-2024-36032, CVE-2024-38615,\nCVE-2024-36960, CVE-2024-36934, CVE-2024-36951, CVE-2024-35999,\nCVE-2024-38551, CVE-2024-36903, CVE-2024-36931, CVE-2024-38593,\nCVE-2024-36938, CVE-2024-38607, CVE-2024-36928, CVE-2024-38552,\nCVE-2024-36002, CVE-2024-38605, CVE-2024-38582, CVE-2024-36933,\nCVE-2024-38620, CVE-2024-27395, CVE-2024-27396, CVE-2024-36012,\nCVE-2024-38591, CVE-2024-38597, CVE-2024-36889, CVE-2024-36964,\nCVE-2024-38606, CVE-2024-38553, CVE-2024-36945, CVE-2024-35848,\nCVE-2024-36962, CVE-2024-36947, CVE-2024-27399, CVE-2024-38546,\nCVE-2024-38583, CVE-2024-38573, CVE-2024-35850, CVE-2024-38549,\nCVE-2024-38588, CVE-2024-38610, CVE-2024-36917, CVE-2024-36957,\nCVE-2024-35846, CVE-2024-38579, CVE-2024-36965, CVE-2024-35857,\nCVE-2024-38548, CVE-2024-36975, CVE-2024-36919, CVE-2024-38542,\nCVE-2024-36948, CVE-2024-36011, CVE-2024-38556, CVE-2024-36897,\nCVE-2024-38557, CVE-2024-36890, CVE-2024-36882, CVE-2024-38613,\nCVE-2024-36914, CVE-2024-35998, CVE-2024-36958, CVE-2024-38580,\nCVE-2024-36896, CVE-2024-36891, CVE-2024-36924, CVE-2024-38589,\nCVE-2024-38592, CVE-2024-36904, CVE-2024-36894, CVE-2024-36028,\nCVE-2024-36014, CVE-2024-36880, CVE-2024-36944, CVE-2024-38598,\nCVE-2024-36929, CVE-2024-36883, CVE-2024-35858, CVE-2024-38555,\nCVE-2024-36005, CVE-2024-38539, CVE-2024-35994, CVE-2024-36030,\nCVE-2024-27394, CVE-2024-36930, CVE-2024-36937, CVE-2024-38561,\nCVE-2024-38578, CVE-2024-36959, CVE-2024-36935, CVE-2024-36916,\nCVE-2024-36902, CVE-2024-38604, CVE-2024-38554, CVE-2024-38575,\nCVE-2024-36918, CVE-2024-36979, CVE-2024-35854, CVE-2024-36968,\nCVE-2024-38558, CVE-2024-36000, CVE-2024-27398, CVE-2024-35983,\nCVE-2024-36949, CVE-2024-38600, CVE-2024-36950, CVE-2024-36946,\nCVE-2024-36031, CVE-2024-35847, CVE-2024-36905, CVE-2024-38571,\nCVE-2024-36007, CVE-2024-35856, CVE-2024-38601, CVE-2024-38569,\nCVE-2024-38617, CVE-2024-35988, CVE-2024-35989, CVE-2024-35993,\nCVE-2024-36893, CVE-2024-36901)\n","status":"published","published":"2024-08-13T17:30:34Z","modified":"2026-10-26T22:31:42.289937588Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6952-1","title":"linux-nvidia-lowlatency, linux-oracle vulnerabilities","description":"\nBenedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde\ndiscovered that an untrusted hypervisor could inject malicious #VC\ninterrupts and compromise the security guarantees of AMD SEV-SNP. This flaw\nis known as WeSee. A local attacker in control of the hypervisor could use\nthis to expose sensitive information or possibly execute arbitrary code in\nthe trusted execution environment. (CVE-2024-25742)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - M68K architecture;\n  - OpenRISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - FireWire subsystem;\n  - EFI core;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - MMC subsystem;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Device tree and open firmware driver;\n  - HiSilicon SoC PMU drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - ACRN Hypervisor Service Module driver;\n  - Virtio drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - eCrypt file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - Network file systems library;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Mellanox drivers;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Slab allocator;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Core kernel;\n  - BPF subsystem;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Dynamic debug library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Heterogeneous memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - Kirkwood ASoC drivers;\n  - MediaTek ASoC drivers;\n(CVE-2024-38601, CVE-2024-36935, CVE-2024-35991, CVE-2024-36032,\nCVE-2024-35988, CVE-2024-36886, CVE-2024-36913, CVE-2024-36928,\nCVE-2024-38553, CVE-2024-36927, CVE-2024-38615, CVE-2024-36958,\nCVE-2024-36977, CVE-2024-36889, CVE-2024-38554, CVE-2024-38590,\nCVE-2024-42134, CVE-2024-35857, CVE-2024-35850, CVE-2024-35986,\nCVE-2024-36921, CVE-2024-38569, CVE-2024-36966, CVE-2024-38542,\nCVE-2024-38585, CVE-2024-36884, CVE-2024-36006, CVE-2024-38577,\nCVE-2024-36016, CVE-2024-38584, CVE-2024-36887, CVE-2024-38598,\nCVE-2024-35994, CVE-2024-38603, CVE-2024-35998, CVE-2024-27401,\nCVE-2024-35852, CVE-2024-36944, CVE-2024-38572, CVE-2024-36917,\nCVE-2024-36943, CVE-2024-36009, CVE-2024-38587, CVE-2024-35949,\nCVE-2024-36945, CVE-2024-36004, CVE-2024-36919, CVE-2024-27398,\nCVE-2024-38582, CVE-2024-35847, CVE-2024-38580, CVE-2024-38602,\nCVE-2024-36916, CVE-2024-36903, CVE-2024-38555, CVE-2024-36952,\nCVE-2024-38589, CVE-2024-27394, CVE-2024-36933, CVE-2024-36975,\nCVE-2024-38591, CVE-2024-38612, CVE-2024-36939, CVE-2024-35983,\nCVE-2024-38607, CVE-2024-36929, CVE-2024-35849, CVE-2024-36941,\nCVE-2024-35858, CVE-2024-38599, CVE-2024-35996, CVE-2024-36031,\nCVE-2024-36931, CVE-2024-35990, CVE-2024-35851, CVE-2024-38556,\nCVE-2024-36000, CVE-2024-36910, CVE-2024-38573, CVE-2024-36906,\nCVE-2024-36951, CVE-2024-38604, CVE-2024-38613, CVE-2024-38547,\nCVE-2024-36014, CVE-2024-36949, CVE-2024-36033, CVE-2024-38597,\nCVE-2024-36880, CVE-2024-38594, CVE-2024-36894, CVE-2024-38546,\nCVE-2024-36947, CVE-2024-38541, CVE-2024-35989, CVE-2024-27399,\nCVE-2024-38550, CVE-2024-36922, CVE-2024-36008, CVE-2024-38540,\nCVE-2024-36924, CVE-2024-36892, CVE-2024-38549, CVE-2024-36882,\nCVE-2024-36908, CVE-2024-38566, CVE-2024-36005, CVE-2024-38583,\nCVE-2024-36968, CVE-2024-36017, CVE-2024-38565, CVE-2024-36881,\nCVE-2024-38611, CVE-2024-36897, CVE-2024-38560, CVE-2024-36923,\nCVE-2024-38575, CVE-2024-36899, CVE-2024-38570, CVE-2024-36898,\nCVE-2024-36896, CVE-2024-38559, CVE-2024-38588, CVE-2024-38606,\nCVE-2024-38551, CVE-2024-36891, CVE-2024-38567, CVE-2024-36895,\nCVE-2024-35993, CVE-2024-38552, CVE-2024-36925, CVE-2024-36964,\nCVE-2024-36888, CVE-2024-36956, CVE-2024-36946, CVE-2024-38600,\nCVE-2024-35997, CVE-2024-36912, CVE-2024-35984, CVE-2024-35848,\nCVE-2024-38545, CVE-2024-38563, CVE-2024-36918, CVE-2024-36001,\nCVE-2024-36957, CVE-2024-38576, CVE-2024-36030, CVE-2024-38574,\nCVE-2024-36963, CVE-2024-36890, CVE-2024-36960, CVE-2024-36901,\nCVE-2024-38614, CVE-2024-35859, CVE-2024-38593, CVE-2024-36904,\nCVE-2024-36012, CVE-2024-38578, CVE-2024-36011, CVE-2024-36930,\nCVE-2024-36938, CVE-2024-36893, CVE-2024-35987, CVE-2024-36905,\nCVE-2024-35853, CVE-2024-36003, CVE-2024-38562, CVE-2024-38617,\nCVE-2024-35855, CVE-2024-36965, CVE-2024-38596, CVE-2024-38558,\nCVE-2024-38568, CVE-2024-36955, CVE-2024-36029, CVE-2024-36967,\nCVE-2024-36940, CVE-2024-38595, CVE-2024-36028, CVE-2024-38610,\nCVE-2024-36911, CVE-2024-35999, CVE-2024-35854, CVE-2024-38571,\nCVE-2024-38548, CVE-2024-36948, CVE-2024-36002, CVE-2024-36961,\nCVE-2024-36900, CVE-2024-36932, CVE-2024-36902, CVE-2024-35992,\nCVE-2024-36914, CVE-2024-38592, CVE-2024-38616, CVE-2024-27400,\nCVE-2024-36937, CVE-2024-36920, CVE-2024-38586, CVE-2024-36909,\nCVE-2024-35846, CVE-2024-39482, CVE-2024-38579, CVE-2024-38539,\nCVE-2024-27395, CVE-2024-36962, CVE-2024-36013, CVE-2024-27396,\nCVE-2024-38557, CVE-2024-36953, CVE-2024-41011, CVE-2023-52882,\nCVE-2024-36969, CVE-2024-36007, CVE-2024-35856, CVE-2024-38605,\nCVE-2024-36915, CVE-2024-36979, CVE-2024-36954, CVE-2024-38538,\nCVE-2024-36950, CVE-2024-36926, CVE-2024-38544, CVE-2024-36959,\nCVE-2024-38561, CVE-2024-36883, CVE-2024-36936, CVE-2024-38564,\nCVE-2024-38543, CVE-2024-36934, CVE-2024-35947, CVE-2024-38620)\n","status":"published","published":"2024-08-09T00:06:04Z","modified":"2026-10-26T22:32:56.429488012Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6952-2","title":"linux-azure vulnerabilities","description":"Benedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde\ndiscovered that an untrusted hypervisor could inject malicious #VC\ninterrupts and compromise the security guarantees of AMD SEV-SNP. This flaw\nis known as WeSee. A local attacker in control of the hypervisor could use\nthis to expose sensitive information or possibly execute arbitrary code in\nthe trusted execution environment. (CVE-2024-25742)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - M68K architecture;\n  - OpenRISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - FireWire subsystem;\n  - EFI core;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - MMC subsystem;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Device tree and open firmware driver;\n  - HiSilicon SoC PMU drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - ACRN Hypervisor Service Module driver;\n  - Virtio drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - eCrypt file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - Network file systems library;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Mellanox drivers;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Slab allocator;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Core kernel;\n  - BPF subsystem;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Dynamic debug library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Heterogeneous memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - Kirkwood ASoC drivers;\n  - MediaTek ASoC drivers;\n(CVE-2024-38601, CVE-2024-36935, CVE-2024-35991, CVE-2024-36032,\nCVE-2024-35988, CVE-2024-36886, CVE-2024-36913, CVE-2024-36928,\nCVE-2024-38553, CVE-2024-36927, CVE-2024-38615, CVE-2024-36958,\nCVE-2024-36977, CVE-2024-36889, CVE-2024-38554, CVE-2024-38590,\nCVE-2024-42134, CVE-2024-35857, CVE-2024-35850, CVE-2024-35986,\nCVE-2024-36921, CVE-2024-38569, CVE-2024-36966, CVE-2024-38542,\nCVE-2024-38585, CVE-2024-36884, CVE-2024-36006, CVE-2024-38577,\nCVE-2024-36016, CVE-2024-38584, CVE-2024-36887, CVE-2024-38598,\nCVE-2024-35994, CVE-2024-38603, CVE-2024-35998, CVE-2024-27401,\nCVE-2024-35852, CVE-2024-36944, CVE-2024-38572, CVE-2024-36917,\nCVE-2024-36943, CVE-2024-36009, CVE-2024-38587, CVE-2024-35949,\nCVE-2024-36945, CVE-2024-36004, CVE-2024-36919, CVE-2024-27398,\nCVE-2024-38582, CVE-2024-35847, CVE-2024-38580, CVE-2024-38602,\nCVE-2024-36916, CVE-2024-36903, CVE-2024-38555, CVE-2024-36952,\nCVE-2024-38589, CVE-2024-27394, CVE-2024-36933, CVE-2024-36975,\nCVE-2024-38591, CVE-2024-38612, CVE-2024-36939, CVE-2024-35983,\nCVE-2024-38607, CVE-2024-36929, CVE-2024-35849, CVE-2024-36941,\nCVE-2024-35858, CVE-2024-38599, CVE-2024-35996, CVE-2024-36031,\nCVE-2024-36931, CVE-2024-35990, CVE-2024-35851, CVE-2024-38556,\nCVE-2024-36000, CVE-2024-36910, CVE-2024-38573, CVE-2024-36906,\nCVE-2024-36951, CVE-2024-38604, CVE-2024-38613, CVE-2024-38547,\nCVE-2024-36014, CVE-2024-36949, CVE-2024-36033, CVE-2024-38597,\nCVE-2024-36880, CVE-2024-38594, CVE-2024-36894, CVE-2024-38546,\nCVE-2024-36947, CVE-2024-38541, CVE-2024-35989, CVE-2024-27399,\nCVE-2024-38550, CVE-2024-36922, CVE-2024-36008, CVE-2024-38540,\nCVE-2024-36924, CVE-2024-36892, CVE-2024-38549, CVE-2024-36882,\nCVE-2024-36908, CVE-2024-38566, CVE-2024-36005, CVE-2024-38583,\nCVE-2024-36968, CVE-2024-36017, CVE-2024-38565, CVE-2024-36881,\nCVE-2024-38611, CVE-2024-36897, CVE-2024-38560, CVE-2024-36923,\nCVE-2024-38575, CVE-2024-36899, CVE-2024-38570, CVE-2024-36898,\nCVE-2024-36896, CVE-2024-38559, CVE-2024-38588, CVE-2024-38606,\nCVE-2024-38551, CVE-2024-36891, CVE-2024-38567, CVE-2024-36895,\nCVE-2024-35993, CVE-2024-38552, CVE-2024-36925, CVE-2024-36964,\nCVE-2024-36888, CVE-2024-36956, CVE-2024-36946, CVE-2024-38600,\nCVE-2024-35997, CVE-2024-36912, CVE-2024-35984, CVE-2024-35848,\nCVE-2024-38545, CVE-2024-38563, CVE-2024-36918, CVE-2024-36001,\nCVE-2024-36957, CVE-2024-38576, CVE-2024-36030, CVE-2024-38574,\nCVE-2024-36963, CVE-2024-36890, CVE-2024-36960, CVE-2024-36901,\nCVE-2024-38614, CVE-2024-35859, CVE-2024-38593, CVE-2024-36904,\nCVE-2024-36012, CVE-2024-38578, CVE-2024-36011, CVE-2024-36930,\nCVE-2024-36938, CVE-2024-36893, CVE-2024-35987, CVE-2024-36905,\nCVE-2024-35853, CVE-2024-36003, CVE-2024-38562, CVE-2024-38617,\nCVE-2024-35855, CVE-2024-36965, CVE-2024-38596, CVE-2024-38558,\nCVE-2024-38568, CVE-2024-36955, CVE-2024-36029, CVE-2024-36967,\nCVE-2024-36940, CVE-2024-38595, CVE-2024-36028, CVE-2024-38610,\nCVE-2024-36911, CVE-2024-35999, CVE-2024-35854, CVE-2024-38571,\nCVE-2024-38548, CVE-2024-36948, CVE-2024-36002, CVE-2024-36961,\nCVE-2024-36900, CVE-2024-36932, CVE-2024-36902, CVE-2024-35992,\nCVE-2024-36914, CVE-2024-38592, CVE-2024-38616, CVE-2024-27400,\nCVE-2024-36937, CVE-2024-36920, CVE-2024-38586, CVE-2024-36909,\nCVE-2024-35846, CVE-2024-39482, CVE-2024-38579, CVE-2024-38539,\nCVE-2024-27395, CVE-2024-36962, CVE-2024-36013, CVE-2024-27396,\nCVE-2024-38557, CVE-2024-36953, CVE-2024-41011, CVE-2023-52882,\nCVE-2024-36969, CVE-2024-36007, CVE-2024-35856, CVE-2024-38605,\nCVE-2024-36915, CVE-2024-36979, CVE-2024-36954, CVE-2024-38538,\nCVE-2024-36950, CVE-2024-36926, CVE-2024-38544, CVE-2024-36959,\nCVE-2024-38561, CVE-2024-36883, CVE-2024-36936, CVE-2024-38564,\nCVE-2024-38543, CVE-2024-36934, CVE-2024-35947, CVE-2024-38620)\n","status":"published","published":"2024-08-13T18:11:04Z","modified":"2026-10-26T22:33:03.423818109Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6955-1","title":"linux-oem-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - M68K architecture;\n  - OpenRISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Accessibility subsystem;\n  - Bluetooth drivers;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - FireWire subsystem;\n  - EFI core;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - MMC subsystem;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Device tree and open firmware driver;\n  - HiSilicon SoC PMU drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Thermal drivers;\n  - Userspace I/O drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - ACRN Hypervisor Service Module driver;\n  - Virtio drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - eCrypt file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - Network file systems library;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Mellanox drivers;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Slab allocator;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Core kernel;\n  - BPF subsystem;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Dynamic debug library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Heterogeneous memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - Kirkwood ASoC drivers;\n  - MediaTek ASoC drivers;\n(CVE-2024-35987, CVE-2024-36931, CVE-2024-38614, CVE-2024-35857,\nCVE-2024-36949, CVE-2024-38599, CVE-2024-35994, CVE-2024-35849,\nCVE-2024-36916, CVE-2024-38590, CVE-2024-36944, CVE-2024-38561,\nCVE-2024-38538, CVE-2024-36017, CVE-2024-38593, CVE-2024-36028,\nCVE-2024-36960, CVE-2024-36002, CVE-2024-36967, CVE-2024-36898,\nCVE-2024-35989, CVE-2024-36975, CVE-2024-38578, CVE-2024-38582,\nCVE-2024-38588, CVE-2024-38579, CVE-2024-38617, CVE-2024-36901,\nCVE-2024-38550, CVE-2023-52882, CVE-2024-38603, CVE-2024-38620,\nCVE-2024-36956, CVE-2024-36880, CVE-2024-36895, CVE-2024-36979,\nCVE-2024-36887, CVE-2024-27396, CVE-2024-27400, CVE-2024-36952,\nCVE-2024-36886, CVE-2024-36905, CVE-2024-36883, CVE-2024-38540,\nCVE-2024-38605, CVE-2024-36029, CVE-2024-36934, CVE-2024-27395,\nCVE-2024-36000, CVE-2024-38549, CVE-2024-35999, CVE-2024-38585,\nCVE-2024-38589, CVE-2024-38565, CVE-2024-36917, CVE-2024-36930,\nCVE-2024-36940, CVE-2024-36900, CVE-2024-35850, CVE-2024-38592,\nCVE-2024-38553, CVE-2024-36929, CVE-2024-36915, CVE-2024-36004,\nCVE-2024-38573, CVE-2024-36941, CVE-2024-38607, CVE-2024-36009,\nCVE-2024-27398, CVE-2024-36909, CVE-2024-35848, CVE-2024-36950,\nCVE-2024-38564, CVE-2024-36947, CVE-2024-38613, CVE-2024-38570,\nCVE-2024-38612, CVE-2024-38580, CVE-2024-38557, CVE-2024-36959,\nCVE-2024-27399, CVE-2024-41011, CVE-2024-36928, CVE-2024-38543,\nCVE-2024-38541, CVE-2024-38583, CVE-2024-35855, CVE-2024-38611,\nCVE-2024-36891, CVE-2024-38587, CVE-2024-35851, CVE-2024-38546,\nCVE-2024-38596, CVE-2024-35998, CVE-2024-35991, CVE-2024-36965,\nCVE-2024-36925, CVE-2024-36894, CVE-2024-38567, CVE-2024-38572,\nCVE-2024-36882, CVE-2024-38594, CVE-2024-38563, CVE-2024-38616,\nCVE-2024-36951, CVE-2024-36005, CVE-2024-42134, CVE-2024-38602,\nCVE-2024-36014, CVE-2024-38601, CVE-2024-36001, CVE-2024-38575,\nCVE-2024-27401, CVE-2024-36961, CVE-2024-38576, CVE-2024-36935,\nCVE-2024-36893, CVE-2024-38562, CVE-2024-36904, CVE-2024-36939,\nCVE-2024-38591, CVE-2024-38539, CVE-2024-36030, CVE-2024-36920,\nCVE-2024-39482, CVE-2024-36977, CVE-2024-36013, CVE-2024-35856,\nCVE-2024-36922, CVE-2024-36033, CVE-2024-35859, CVE-2024-36919,\nCVE-2024-35846, CVE-2024-36913, CVE-2024-35854, CVE-2024-36924,\nCVE-2024-38547, CVE-2024-38551, CVE-2024-36899, CVE-2024-36932,\nCVE-2024-38545, CVE-2024-36966, CVE-2024-36911, CVE-2024-36946,\nCVE-2024-36906, CVE-2024-38595, CVE-2024-36012, CVE-2024-38552,\nCVE-2024-36933, CVE-2024-36936, CVE-2024-38548, CVE-2024-38558,\nCVE-2024-36006, CVE-2024-36908, CVE-2024-36892, CVE-2024-35988,\nCVE-2024-35993, CVE-2024-36914, CVE-2024-36896, CVE-2024-38615,\nCVE-2024-36890, CVE-2024-36969, CVE-2024-38559, CVE-2024-36964,\nCVE-2024-38560, CVE-2024-38574, CVE-2024-36962, CVE-2024-38542,\nCVE-2024-36926, CVE-2024-36968, CVE-2024-36032, CVE-2024-38544,\nCVE-2024-36938, CVE-2024-38597, CVE-2024-38577, CVE-2024-36958,\nCVE-2024-36945, CVE-2024-36943, CVE-2024-38610, CVE-2024-36927,\nCVE-2024-38554, CVE-2024-38555, CVE-2024-36031, CVE-2024-36011,\nCVE-2024-38569, CVE-2024-35847, CVE-2024-36921, CVE-2024-38606,\nCVE-2024-35949, CVE-2024-35947, CVE-2024-36889, CVE-2024-36884,\nCVE-2024-36954, CVE-2024-36902, CVE-2024-36007, CVE-2024-38586,\nCVE-2024-36918, CVE-2024-38571, CVE-2024-36955, CVE-2024-36888,\nCVE-2024-38556, CVE-2024-38604, CVE-2024-27394, CVE-2024-38600,\nCVE-2024-35983, CVE-2024-38568, CVE-2024-38566, CVE-2024-35853,\nCVE-2024-35858, CVE-2024-36910, CVE-2024-36903, CVE-2024-36881,\nCVE-2024-36937, CVE-2024-36957, CVE-2024-36912, CVE-2024-36948,\nCVE-2024-36953, CVE-2024-35996, CVE-2024-36963, CVE-2024-36923,\nCVE-2024-35852, CVE-2024-38598, CVE-2024-36003, CVE-2024-35986,\nCVE-2024-38584)\n","status":"published","published":"2024-08-12T18:05:26Z","modified":"2026-10-26T22:33:10.379382439Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-7019-1","title":"linux-xilinx-zynqmp vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nChenyuan Yang discovered that the CEC driver driver 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-2024-23848)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nBenedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde\ndiscovered that an untrusted hypervisor could inject malicious #VC\ninterrupts and compromise the security guarantees of AMD SEV-SNP. This flaw\nis known as WeSee. A local attacker in control of the hypervisor could use\nthis to expose sensitive information or possibly execute arbitrary code in\nthe trusted execution environment. (CVE-2024-25742)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FireWire subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Trusted Execution Environment drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Xen hypervisor drivers;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - eCrypt file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Core kernel;\n  - Tracing infrastructure;\n  - Dynamic debug library;\n  - PCI iomap interfaces;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - ALSA SH drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n  - KVM core;\n(CVE-2024-42085, CVE-2024-42154, CVE-2024-42229, CVE-2024-38548,\nCVE-2024-42120, CVE-2024-38555, CVE-2024-38598, CVE-2024-40954,\nCVE-2024-38571, CVE-2024-36020, CVE-2024-36270, CVE-2024-39482,\nCVE-2024-39468, CVE-2024-38607, CVE-2024-26923, CVE-2024-42145,\nCVE-2024-41040, CVE-2024-35852, CVE-2024-35805, CVE-2024-35890,\nCVE-2024-36965, CVE-2024-42077, CVE-2024-26958, CVE-2024-35823,\nCVE-2024-42124, CVE-2024-26680, CVE-2024-38549, CVE-2024-36286,\nCVE-2024-27398, CVE-2024-35990, CVE-2024-36975, CVE-2024-27437,\nCVE-2024-35848, CVE-2024-26900, CVE-2024-26654, CVE-2024-40971,\nCVE-2024-35847, CVE-2024-35982, CVE-2024-42232, CVE-2022-48808,\nCVE-2024-35822, CVE-2024-36950, CVE-2024-33621, CVE-2024-39276,\nCVE-2024-40968, CVE-2024-35857, CVE-2024-40905, CVE-2023-52880,\nCVE-2024-35819, CVE-2024-35791, CVE-2024-42076, CVE-2024-40904,\nCVE-2024-35976, CVE-2024-35854, CVE-2024-26642, CVE-2024-27393,\nCVE-2024-26934, CVE-2024-26960, CVE-2024-42137, CVE-2024-38588,\nCVE-2024-40970, CVE-2024-36972, CVE-2024-26977, CVE-2024-38546,\nCVE-2024-41095, CVE-2024-39292, CVE-2024-41087, CVE-2024-33847,\nCVE-2024-40978, CVE-2024-41049, CVE-2024-35895, CVE-2024-35804,\nCVE-2024-42093, CVE-2024-36017, CVE-2024-38591, CVE-2024-42080,\nCVE-2024-41089, CVE-2024-38613, CVE-2024-39466, CVE-2024-40931,\nCVE-2024-35907, CVE-2024-36919, CVE-2024-36934, CVE-2024-42240,\nCVE-2024-35940, CVE-2024-36938, CVE-2024-42121, CVE-2024-39490,\nCVE-2024-40961, CVE-2024-42223, CVE-2024-41041, CVE-2024-41093,\nCVE-2024-42068, CVE-2024-41044, CVE-2024-42086, CVE-2024-42105,\nCVE-2024-36954, CVE-2024-35796, CVE-2024-38610, CVE-2024-36929,\nCVE-2024-35893, CVE-2024-38601, CVE-2024-40981, CVE-2024-36889,\nCVE-2024-27015, CVE-2024-35897, CVE-2024-39469, CVE-2024-35825,\nCVE-2024-26922, CVE-2024-38573, CVE-2024-42130, CVE-2024-38580,\nCVE-2024-26814, CVE-2024-36955, CVE-2024-26813, CVE-2024-27396,\nCVE-2024-36937, CVE-2024-36928, CVE-2024-42224, CVE-2024-27004,\nCVE-2024-42104, CVE-2024-42225, CVE-2024-38659, CVE-2024-35955,\nCVE-2024-42106, CVE-2024-39489, CVE-2024-31076, CVE-2024-26817,\nCVE-2024-35884, CVE-2024-42095, CVE-2024-42131, CVE-2024-40956,\nCVE-2024-40941, CVE-2024-36007, CVE-2024-27009, CVE-2024-40959,\nCVE-2024-42089, CVE-2024-37078, CVE-2024-35960, CVE-2024-41002,\nCVE-2024-39301, CVE-2024-35988, CVE-2023-52887, CVE-2024-35885,\nCVE-2024-39484, CVE-2024-35872, CVE-2024-40974, CVE-2024-35851,\nCVE-2024-26957, CVE-2024-38623, CVE-2024-35944, CVE-2024-41005,\nCVE-2024-42152, CVE-2024-35888, CVE-2024-38621, CVE-2024-26989,\nCVE-2024-42148, CVE-2024-27401, CVE-2024-36883, CVE-2024-35855,\nCVE-2024-26936, CVE-2024-26935, CVE-2022-48772, CVE-2024-35853,\nCVE-2024-35997, CVE-2024-27059, CVE-2024-36953, CVE-2024-35969,\nCVE-2024-42094, CVE-2024-38661, CVE-2024-35925, CVE-2024-40914,\nCVE-2024-36940, CVE-2024-27016, CVE-2024-26828, CVE-2024-40911,\nCVE-2024-38634, CVE-2024-38558, CVE-2024-38582, CVE-2023-52629,\nCVE-2024-27020, CVE-2024-35247, CVE-2024-26999, CVE-2024-26687,\nCVE-2024-38565, CVE-2024-38612, CVE-2024-39495, CVE-2024-26974,\nCVE-2024-42101, CVE-2024-38597, CVE-2024-26929, CVE-2024-40927,\nCVE-2024-26830, CVE-2024-26973, CVE-2024-40980, CVE-2024-38560,\nCVE-2024-41047, CVE-2024-42098, CVE-2024-39507, CVE-2024-38599,\nCVE-2024-35789, CVE-2024-27395, CVE-2024-41092, CVE-2024-42161,\nCVE-2024-41006, CVE-2024-36931, CVE-2024-38619, CVE-2024-35813,\nCVE-2024-35898, CVE-2024-41027, CVE-2024-40932, CVE-2024-40960,\nCVE-2024-26925, CVE-2024-41048, CVE-2024-36886, CVE-2024-35877,\nCVE-2024-40963, CVE-2024-36960, CVE-2024-38590, CVE-2024-40902,\nCVE-2024-35871, CVE-2024-38579, CVE-2024-40987, CVE-2024-36025,\nCVE-2024-35806, CVE-2024-35899, CVE-2024-26993, CVE-2024-41097,\nCVE-2024-39488, CVE-2024-42115, CVE-2024-42127, CVE-2024-37356,\nCVE-2024-26812, CVE-2024-36939, CVE-2024-35807, CVE-2024-26886,\nCVE-2024-35809, CVE-2024-40937, CVE-2024-35970, CVE-2024-35817,\nCVE-2024-35973, CVE-2024-40945, CVE-2024-42153, CVE-2024-36964,\nCVE-2024-42090, CVE-2024-38552, CVE-2024-39467, CVE-2024-26961,\nCVE-2024-38615, CVE-2024-38618, CVE-2024-40988, CVE-2024-38605,\nCVE-2024-41004, CVE-2024-26966, CVE-2024-42096, CVE-2024-26996,\nCVE-2024-36969, CVE-2024-36489, CVE-2024-40957, CVE-2024-36974,\nCVE-2024-39502, CVE-2024-26976, CVE-2024-27399, CVE-2024-36905,\nCVE-2024-35958, CVE-2024-35927, CVE-2024-27001, CVE-2024-39487,\nCVE-2024-41034, CVE-2024-36904, CVE-2024-41055, CVE-2024-38550,\nCVE-2024-38567, CVE-2024-38586, CVE-2024-40916, CVE-2024-38589,\nCVE-2023-52884, CVE-2024-26810, CVE-2024-35989, CVE-2024-36894,\nCVE-2024-39471, CVE-2024-35900, CVE-2024-42097, CVE-2024-36959,\nCVE-2024-26931, CVE-2024-40934, CVE-2024-36947, CVE-2024-34777,\nCVE-2024-27018, CVE-2024-39499, CVE-2024-36906, CVE-2024-35984,\nCVE-2024-39500, CVE-2024-26965, CVE-2024-26921, CVE-2024-27013,\nCVE-2024-39509, CVE-2024-27008, CVE-2024-36916, CVE-2024-40942,\nCVE-2024-35978, CVE-2024-26969, CVE-2024-26964, CVE-2024-35879,\nCVE-2024-36016, CVE-2024-26629, CVE-2024-42236, CVE-2024-40943,\nCVE-2024-36902, CVE-2024-42247, CVE-2024-36006, CVE-2024-36014,\nCVE-2024-26955, CVE-2024-39277, CVE-2024-39506, CVE-2024-35936,\nCVE-2024-26950, CVE-2024-35938, CVE-2024-41035, CVE-2024-42140,\nCVE-2024-36971, CVE-2024-35910, CVE-2024-34027, CVE-2024-35933,\nCVE-2024-35886, CVE-2024-39501, CVE-2024-42109, CVE-2024-42157,\nCVE-2024-35905, CVE-2024-41007, CVE-2024-40912, CVE-2024-26984,\nCVE-2024-35915, CVE-2024-35934, CVE-2024-38633, CVE-2024-26952,\nCVE-2024-27017, CVE-2024-38627, CVE-2024-42070, CVE-2024-41046,\nCVE-2024-35821, CVE-2024-35815, CVE-2024-36978, CVE-2024-36967,\nCVE-2023-52752, CVE-2024-38583, CVE-2024-38578, CVE-2024-26926,\nCVE-2023-52699, CVE-2024-36952, CVE-2024-38600, CVE-2024-42102,\nCVE-2024-38559, CVE-2024-38637, CVE-2024-42082, CVE-2023-52488,\nCVE-2024-36032, CVE-2024-35950, CVE-2024-35930, CVE-2024-38780,\nCVE-2024-40995, CVE-2024-36004, CVE-2024-26956, CVE-2024-35896,\nCVE-2024-26994, CVE-2024-38624, CVE-2024-39480, CVE-2023-52882,\nCVE-2024-35912, CVE-2024-36015, CVE-2024-27019, CVE-2024-40983,\nCVE-2023-52760, CVE-2024-39503, CVE-2024-36957, CVE-2024-26980,\nCVE-2024-40908, CVE-2024-40958, CVE-2024-35902, CVE-2024-42087,\nCVE-2024-36933, CVE-2024-38635, CVE-2024-26988, CVE-2024-36941,\nCVE-2024-26970, CVE-2024-36005, CVE-2024-36029, CVE-2024-36008,\nCVE-2024-42244, CVE-2024-40967, CVE-2023-52585, CVE-2024-26951,\nCVE-2024-39475, CVE-2024-35922, CVE-2024-36901, CVE-2024-40901,\nCVE-2024-36031, CVE-2024-41000, CVE-2024-40929, CVE-2024-40994,\nCVE-2024-42084, CVE-2024-38547, CVE-2024-26937, CVE-2024-40984,\nCVE-2024-27000, CVE-2024-35785, CVE-2024-35849, CVE-2024-42119,\nCVE-2024-35947, CVE-2024-39505, CVE-2024-42092, CVE-2024-26811,\nCVE-2024-35935, CVE-2024-36946, CVE-2024-40990, CVE-2024-26981,\nCVE-2024-38596, CVE-2024-40976, CVE-2024-36880)\n","status":"published","published":"2024-09-18T10:00:09Z","modified":"2026-10-26T22:33:18.442136814Z","updated_at":"2026-11-02T16:58:18.876384Z"}]}}