{"id":"CVE-2024-45021","aliases":["AZL-49170","AZL-49242","BELL-CVE-2024-45021","CLSA-2024-1731602566","CLSA-2024-1731603213","CLSA-2024-1731605761","CLSA-2024-1731606243","DEBIAN-CVE-2024-45021","DLA-3912-1","DLA-4008-1","DSA-5782-1","EUVD-2024-41501","GHSA-5m73-3pch-86m2","OESA-2024-2217","OESA-2024-2367","OESA-2024-2368","OESA-2024-2369","OESA-2024-2371","SUSE-SU-2024:3547-1","SUSE-SU-2024:3551-1","SUSE-SU-2024:3553-1","SUSE-SU-2024:3561-1","SUSE-SU-2024:3563-1","SUSE-SU-2024:3564-1","SUSE-SU-2024:3565-1","SUSE-SU-2024:3567-1","SUSE-SU-2024:3569-1","SUSE-SU-2024:3585-1","SUSE-SU-2024:3587-1","SUSE-SU-2024:3592-1","SUSE-SU-2024:3617-1","SUSE-SU-2025:01983-1","SUSE-SU-2025:20073-1","SUSE-SU-2025:20077-1","UBUNTU-CVE-2024-45021","USN-7088-1","USN-7088-2","USN-7088-3","USN-7088-4","USN-7088-5","USN-7100-1","USN-7100-2","USN-7119-1","USN-7123-1","USN-7144-1","USN-7154-1","USN-7154-2","USN-7155-1","USN-7156-1","USN-7183-1","USN-7184-1","USN-7185-1","USN-7185-2","USN-7194-1","USN-7196-1"],"status":"published","title":"memcg_write_event_control(): fix a user-triggerable oops","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00255,"percentile":0.17294,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-476"],"published":"2024-09-11T15:13:55Z","modified":"2026-11-12T17:24:25Z","fixes":[{"ecosystem":"Azure Linux:2","package":"kernel","fixed_in":["5.15.167.1-1"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.51.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.110-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":["4.19.321","5.4.283","5.10.225","5.15.166","6.1.107","6.6.48","6.10.7"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.112-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.10.7-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.10.7-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-aws","fixed_in":["4.4.0-1139.145"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-azure","fixed_in":["4.15.0-1184.199~14.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-lts-xenial","fixed_in":["4.4.0-262.296~14.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux","fixed_in":["4.4.0-262.296"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws","fixed_in":["4.4.0-1177.192"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws-hwe","fixed_in":["4.15.0-1176.189~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","fixed_in":["4.15.0-1184.199~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","fixed_in":["4.15.0-1169.186~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","fixed_in":["4.15.0-232.244~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-kvm","fixed_in":["4.4.0-1140.151"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","fixed_in":["4.15.0-1138.149~16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:16.04:LTS","package":"linux-fips","fixed_in":["4.4.0-1108.115"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","fixed_in":["4.15.0-232.244"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","fixed_in":["4.15.0-1176.189"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","fixed_in":["5.4.0-1135.145~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-4.15","fixed_in":["4.15.0-1184.199"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","fixed_in":["5.4.0-1140.147~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-4.15","fixed_in":["4.15.0-1169.186"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","fixed_in":["5.4.0-1139.148~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","fixed_in":["5.4.0-200.220~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","fixed_in":["5.4.0-1082.87~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-kvm","fixed_in":["4.15.0-1159.164"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle","fixed_in":["4.15.0-1138.149"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","fixed_in":["5.4.0-1134.143~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","fixed_in":["5.4.0-1119.131~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-aws-fips","fixed_in":["4.15.0-2114.120"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-azure-fips","fixed_in":["4.15.0-2093.99"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-fips","fixed_in":["4.15.0-1130.141"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-gcp-fips","fixed_in":["4.15.0-2077.83"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux","fixed_in":["5.4.0-200.220"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","fixed_in":["5.4.0-1135.145"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1072.78~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","fixed_in":["5.4.0-1140.147"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1078.87~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","fixed_in":["5.4.0-1095.102"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","fixed_in":["5.4.0-1139.148"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1071.79~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","fixed_in":["5.4.0-1102.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","fixed_in":["5.15.0-1055.62~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-125.135~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","fixed_in":["5.4.0-1082.87"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1065.68~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1067.73~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","fixed_in":["5.4.0-1044.45"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","fixed_in":["5.4.0-1123.131"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-125.135~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1032.32~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","fixed_in":["5.4.0-1134.143"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1070.76~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","fixed_in":["5.4.0-1119.131"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1068.72~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.4.0-1054.58"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","fixed_in":["5.4.0-1135.145+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","fixed_in":["5.4.0-1140.147+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","fixed_in":["5.4.0-1109.119"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","fixed_in":["5.4.0-1139.148+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-125.135"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1072.78"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1020.22~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1075.84"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1020.23~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","fixed_in":["5.15.0-1076.85.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1071.79"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1019.21~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1069.75"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1055.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-50.51~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1065.68"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1017.17~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1067.73"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1069.74"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-125.135"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-50.51.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1067.68"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1019.21~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1032.32"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1070.76"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1017.18~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1065.68"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-50.51.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1038.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1056.58"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1066.68"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1073.81"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1013.14~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1072.78+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1075.84+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-125.135+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1071.79+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-50.51"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1020.22"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1020.23"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1019.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1015.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1002.4"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1017.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-50.51.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1019.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1019.21.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1018.18"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1017.18"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1016.18"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","fixed_in":["6.8.0-50.51.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1017.18"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2015.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1013.14"],"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":"Azure Linux:2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.167.1-1"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.51.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.106-r0"},{"fixed":"6.1.110-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":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-240-tuxcare.els28","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-crashdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-240-tuxcare.els28","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-extra-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-240-tuxcare.els28","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-240-tuxcare.els28","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-crashdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-240-tuxcare.els28","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-extra-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-240-tuxcare.els28","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-240-tuxcare.els28-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-240-tuxcare.els28-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.240.251"}]}],"bundled":76},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-267-tuxcare.els38","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-crashdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-267-tuxcare.els38","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-extra-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source-4.4.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-267-tuxcare.els38","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-267-tuxcare.els38","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-crashdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-267-tuxcare.els38","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-extra-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source-4.4.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-267-tuxcare.els38","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-267-tuxcare.els38-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-267-tuxcare.els38-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0.267.301"}]}],"bundled":67},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.34"},{"fixed":"4.19.321"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.20.0"},{"fixed":"5.4.283"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.225"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.166"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.107"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.48"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.10.7"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.112-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","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","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.10.7-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.10.7-1"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.226-1"}]}],"versions":["5.10.103-1","5.10.103-1~bpo10+1","5.10.106-1","5.10.113-1","5.10.120-1","5.10.120-1~bpo10+1","5.10.127-1","5.10.127-2","5.10.127-2~bpo10+1","5.10.136-1","5.10.140-1","5.10.148-1","5.10.149-1","5.10.149-2","5.10.158-1","5.10.158-2","5.10.162-1","5.10.178-1","5.10.178-2","5.10.178-3","5.10.179-1","5.10.179-2","5.10.179-3","5.10.179-4","5.10.179-5","5.10.191-1","5.10.197-1","5.10.205-1","5.10.205-2","5.10.209-1","5.10.209-2","5.10.216-1","5.10.218-1","5.10.221-1","5.10.223-1","5.10.46-4","5.10.46-5","5.10.70-1","5.10.70-1~bpo10+1","5.10.84-1","5.10.92-1","5.10.92-1~bpo10+1","5.10.92-2"],"bundled":147},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.119-1~deb11u1"}]}],"versions":["6.1.106-3~deb11u1","6.1.106-3~deb11u2","6.1.106-3~deb11u3","6.1.112-1~deb11u1"],"bundled":838},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.112-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","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","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"],"bundled":145},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2410.1.0.0298.oe2003sp4"}]}],"bundled":18},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-50.0.0.55.oe2403"}]}],"bundled":121},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-235.0.0.134.oe2203sp4"}]}],"bundled":75},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-235.0.0.137.oe2203sp3"}]}],"bundled":75},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.100.0.181.oe2203sp1"}]}],"bundled":89},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-livepatch-SLE15-SP4_Update_32","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150400.9.3.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1.150400.24.66.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.136.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-source-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-syms-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1.150600.12.10.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1.150600.12.10.2"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.97.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.97.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.97.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.97.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.3.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-livepatch-SLE15-SP2_Update_53","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150200.5.3.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1.150200.9.107.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1.150200.9.107.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1.150200.9.107.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.206.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.187.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.187.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.187.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.187.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1.150500.6.37.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1.150500.6.37.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_20","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1"}]}],"bundled":130},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.83.1.150500.6.37.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-livepatch-SLE15-SP3_Update_49","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150300.7.3.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1.150300.18.105.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1.150300.18.105.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1.150300.18.105.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1.150300.18.105.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1.150300.18.105.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1.150300.18.105.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.179.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.69.1"}]}],"bundled":132},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.69.1"}]}],"bundled":132},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.69.1"}]}],"bundled":132},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.69.1"}]}],"bundled":132},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.69.1"}]}],"bundled":132},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.69.1"}]}],"bundled":132},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5-RT_Update_21","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.73.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.165.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-ec2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.165.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.165.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.165.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-trace","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.165.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.165.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.261.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_69","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.261.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.261.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.261.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.261.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.261.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.261.1"}]}],"bundled":169},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-20.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-17.1.1.51"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-20.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-20.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0-RT_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-11.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-11.1"}]}],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.11.0-12.19","3.12.0-1.3","3.12.0-2.5","3.12.0-2.7","3.12.0-3.8","3.12.0-3.9","3.12.0-4.10","3.12.0-4.12","3.12.0-5.13","3.12.0-7.15","3.13.0-1.16","3.13.0-2.17","3.13.0-3.18","3.13.0-4.19","3.13.0-5.20","3.13.0-6.23","3.13.0-7.25","3.13.0-7.26","3.13.0-8.27","3.13.0-8.28","3.13.0-10.30","3.13.0-11.31","3.13.0-12.32","3.13.0-13.33","3.13.0-14.34","3.13.0-15.35","3.13.0-16.36","3.13.0-17.37","3.13.0-18.38","3.13.0-19.39","3.13.0-19.40","3.13.0-20.42","3.13.0-21.43","3.13.0-22.44","3.13.0-23.45","3.13.0-24.46","3.13.0-24.47","3.13.0-27.50","3.13.0-29.53","3.13.0-30.54","3.13.0-30.55","3.13.0-32.57","3.13.0-33.58","3.13.0-34.60","3.13.0-35.62","3.13.0-36.63","3.13.0-37.64","3.13.0-39.66","3.13.0-40.69","3.13.0-41.70","3.13.0-43.72","3.13.0-44.73","3.13.0-45.74","3.13.0-46.75","3.13.0-46.76","3.13.0-46.77","3.13.0-46.79","3.13.0-48.80","3.13.0-49.81","3.13.0-49.83","3.13.0-51.84","3.13.0-52.85","3.13.0-52.86","3.13.0-53.88","3.13.0-53.89","3.13.0-54.91","3.13.0-55.92","3.13.0-55.94","3.13.0-57.95","3.13.0-58.97","3.13.0-59.98","3.13.0-61.100","3.13.0-62.102","3.13.0-63.103","3.13.0-65.105","3.13.0-65.106","3.13.0-66.108","3.13.0-67.110","3.13.0-68.111","3.13.0-70.113","3.13.0-71.114","3.13.0-73.116","3.13.0-74.118","3.13.0-76.120","3.13.0-77.121","3.13.0-79.123","3.13.0-83.127","3.13.0-85.129","3.13.0-86.130","3.13.0-86.131","3.13.0-87.133","3.13.0-88.135","3.13.0-91.138","3.13.0-92.139","3.13.0-93.140","3.13.0-95.142","3.13.0-96.143","3.13.0-98.145","3.13.0-100.147","3.13.0-101.148","3.13.0-103.150","3.13.0-105.152","3.13.0-106.153","3.13.0-107.154","3.13.0-108.155","3.13.0-109.156","3.13.0-110.157","3.13.0-111.158","3.13.0-112.159","3.13.0-113.160","3.13.0-115.162","3.13.0-116.163","3.13.0-117.164","3.13.0-119.166","3.13.0-121.170","3.13.0-123.172","3.13.0-125.174","3.13.0-126.175","3.13.0-128.177","3.13.0-129.178","3.13.0-132.181","3.13.0-133.182","3.13.0-135.184","3.13.0-137.186","3.13.0-139.188","3.13.0-141.190","3.13.0-142.191","3.13.0-143.192","3.13.0-144.193","3.13.0-145.194","3.13.0-147.196","3.13.0-149.199","3.13.0-151.201","3.13.0-153.203","3.13.0-155.205","3.13.0-156.206","3.13.0-157.207","3.13.0-158.208","3.13.0-160.210","3.13.0-161.211","3.13.0-162.212","3.13.0-163.213","3.13.0-164.214","3.13.0-165.215","3.13.0-166.216","3.13.0-167.217","3.13.0-168.218","3.13.0-169.219","3.13.0-170.220","3.13.0-171.222","3.13.0-172.223","3.13.0-173.224","3.13.0-174.225","3.13.0-175.226","3.13.0-176.227","3.13.0-180.231","3.13.0-181.232","3.13.0-182.233","3.13.0-183.234","3.13.0-184.235","3.13.0-185.236","3.13.0-186.237","3.13.0-187.238","3.13.0-188.239","3.13.0-189.240","3.13.0-190.241","3.13.0-191.242","3.13.0-192.243","3.13.0-193.244","3.13.0-194.245","3.13.0-195.246","3.13.0-196.247","3.13.0-197.248","3.13.0-198.249","3.13.0-199.250","3.13.0-200.251","3.13.0-201.252","3.13.0-202.253","3.13.0-203.254","3.13.0-204.255","3.13.0-205.256","3.13.0-206.257","3.13.0-207.258","3.13.0-208.259","3.13.0-209.260","3.13.0-210.261","3.13.0-211.262","3.13.0-212.263","3.13.0-214.265","3.13.0-215.266","3.13.0-217.268","3.13.0-218.269","3.13.0-219.270","3.13.0-220.271"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1139.145"}]}],"versions":["4.4.0-1002.2","4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1011.11","4.4.0-1012.12","4.4.0-1014.14","4.4.0-1016.16","4.4.0-1017.17","4.4.0-1019.19","4.4.0-1022.22","4.4.0-1023.23","4.4.0-1024.25","4.4.0-1025.26","4.4.0-1027.30","4.4.0-1028.31","4.4.0-1029.32","4.4.0-1031.34","4.4.0-1032.35","4.4.0-1034.37","4.4.0-1036.39","4.4.0-1037.40","4.4.0-1038.41","4.4.0-1039.42","4.4.0-1040.43","4.4.0-1042.45","4.4.0-1044.47","4.4.0-1045.48","4.4.0-1046.50","4.4.0-1048.52","4.4.0-1050.54","4.4.0-1052.56","4.4.0-1054.58","4.4.0-1055.59","4.4.0-1056.60","4.4.0-1058.62","4.4.0-1059.63","4.4.0-1060.64","4.4.0-1061.65","4.4.0-1062.66","4.4.0-1064.68","4.4.0-1065.69","4.4.0-1066.70","4.4.0-1067.71","4.4.0-1073.77","4.4.0-1074.78","4.4.0-1075.79","4.4.0-1076.80","4.4.0-1077.81","4.4.0-1078.82","4.4.0-1081.85","4.4.0-1082.86","4.4.0-1083.87","4.4.0-1085.89","4.4.0-1086.90","4.4.0-1087.91","4.4.0-1088.92","4.4.0-1090.94","4.4.0-1091.95","4.4.0-1092.96","4.4.0-1093.97","4.4.0-1094.99","4.4.0-1095.100","4.4.0-1096.101","4.4.0-1097.102","4.4.0-1098.103","4.4.0-1099.104","4.4.0-1101.106","4.4.0-1102.107","4.4.0-1103.108","4.4.0-1104.109","4.4.0-1107.113","4.4.0-1109.115","4.4.0-1110.116","4.4.0-1111.117","4.4.0-1112.118","4.4.0-1113.119","4.4.0-1114.120","4.4.0-1115.121","4.4.0-1116.122","4.4.0-1117.123","4.4.0-1118.124","4.4.0-1119.125","4.4.0-1120.126","4.4.0-1121.127","4.4.0-1122.128","4.4.0-1123.129","4.4.0-1124.130","4.4.0-1125.131","4.4.0-1127.133","4.4.0-1128.134","4.4.0-1129.135","4.4.0-1130.136","4.4.0-1131.137","4.4.0-1133.139","4.4.0-1134.140","4.4.0-1135.141","4.4.0-1136.142","4.4.0-1137.143","4.4.0-1138.144"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1184.199~14.04.1"}]}],"versions":["4.15.0-1023.24~14.04.1","4.15.0-1030.31~14.04.1","4.15.0-1031.32~14.04.1","4.15.0-1032.33~14.04.2","4.15.0-1035.36~14.04.2","4.15.0-1036.38~14.04.2","4.15.0-1037.39~14.04.2","4.15.0-1039.41~14.04.2","4.15.0-1040.44~14.04.1","4.15.0-1041.45~14.04.1","4.15.0-1042.46~14.04.1","4.15.0-1045.49~14.04.1","4.15.0-1046.50~14.04.1","4.15.0-1047.51~14.04.1","4.15.0-1049.54~14.04.1","4.15.0-1050.55~14.04.1","4.15.0-1051.56~14.04.1","4.15.0-1052.57~14.04.1","4.15.0-1055.60~14.04.1","4.15.0-1056.61~14.04.1","4.15.0-1057.62~14.04.1","4.15.0-1059.64~14.04.1","4.15.0-1060.65~14.04.1","4.15.0-1061.66~14.04.1","4.15.0-1063.68~14.04.1","4.15.0-1064.69~14.04.1","4.15.0-1066.71~14.04.1","4.15.0-1067.72~14.04.1","4.15.0-1069.74~14.04.1","4.15.0-1071.76~14.04.1","4.15.0-1074.79~14.04.1","4.15.0-1077.82~14.04.1","4.15.0-1082.92~14.04.1","4.15.0-1083.93~14.04.1","4.15.0-1089.99~14.04.1","4.15.0-1091.101~14.04.1","4.15.0-1092.102~14.04.1","4.15.0-1093.103~14.04.1","4.15.0-1095.105~14.04.1","4.15.0-1096.106~14.04.1","4.15.0-1098.109~14.04.1","4.15.0-1100.111~14.04.1","4.15.0-1102.113~14.04.1","4.15.0-1103.114~14.04.1","4.15.0-1106.118~14.04.1","4.15.0-1108.120~14.04.1","4.15.0-1109.121~14.04.1","4.15.0-1110.122~14.04.1","4.15.0-1111.123~14.04.1","4.15.0-1112.124~14.04.1","4.15.0-1113.126~14.04.1","4.15.0-1114.127~14.04.1","4.15.0-1115.128~14.04.1","4.15.0-1118.131~14.04.1","4.15.0-1121.134~14.04.1","4.15.0-1122.135~14.04.1","4.15.0-1123.136~14.04.1","4.15.0-1124.137~14.04.1","4.15.0-1125.138~14.04.1","4.15.0-1126.139~14.04.1","4.15.0-1127.140~14.04.1","4.15.0-1129.142~14.04.1","4.15.0-1130.143~14.04.1","4.15.0-1131.144~14.04.1","4.15.0-1133.146~14.04.1","4.15.0-1134.147~14.04.1","4.15.0-1136.149~14.04.1","4.15.0-1137.150~14.04.1","4.15.0-1138.151~14.04.1","4.15.0-1139.152~14.04.1","4.15.0-1142.156~14.04.1","4.15.0-1145.160~14.04.1","4.15.0-1146.161~14.04.1","4.15.0-1149.164~14.04.1","4.15.0-1150.165~14.04.1","4.15.0-1151.166~14.04.1","4.15.0-1153.168~14.04.1","4.15.0-1157.172~14.04.2","4.15.0-1158.173~14.04.1","4.15.0-1159.174~14.04.1","4.15.0-1162.177~14.04.1","4.15.0-1163.178~14.04.1","4.15.0-1164.179~14.04.1","4.15.0-1165.180~14.04.1","4.15.0-1166.181~14.04.1","4.15.0-1167.182~14.04.1","4.15.0-1168.183~14.04.1","4.15.0-1169.184~14.04.1","4.15.0-1170.185~14.04.1","4.15.0-1171.186~14.04.1","4.15.0-1172.187~14.04.1","4.15.0-1173.188~14.04.1","4.15.0-1174.189~14.04.1","4.15.0-1175.190~14.04.1","4.15.0-1176.191~14.04.1","4.15.0-1177.192~14.04.1","4.15.0-1178.193~14.04.1","4.15.0-1179.194~14.04.1","4.15.0-1180.195~14.04.1","4.15.0-1181.196~14.04.1","4.15.0-1182.197~14.04.1","4.15.0-1183.198~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-262.296~14.04.1"}]}],"versions":["4.4.0-13.29~14.04.1","4.4.0-14.30~14.04.2","4.4.0-15.31~14.04.1","4.4.0-18.34~14.04.1","4.4.0-21.37~14.04.1","4.4.0-22.39~14.04.1","4.4.0-22.40~14.04.1","4.4.0-24.43~14.04.1","4.4.0-28.47~14.04.1","4.4.0-31.50~14.04.1","4.4.0-34.53~14.04.1","4.4.0-36.55~14.04.1","4.4.0-38.57~14.04.1","4.4.0-42.62~14.04.1","4.4.0-45.66~14.04.1","4.4.0-47.68~14.04.1","4.4.0-51.72~14.04.1","4.4.0-53.74~14.04.1","4.4.0-57.78~14.04.1","4.4.0-59.80~14.04.1","4.4.0-62.83~14.04.1","4.4.0-63.84~14.04.2","4.4.0-64.85~14.04.1","4.4.0-66.87~14.04.1","4.4.0-67.88~14.04.1","4.4.0-70.91~14.04.1","4.4.0-71.92~14.04.1","4.4.0-72.93~14.04.1","4.4.0-75.96~14.04.1","4.4.0-78.99~14.04.2","4.4.0-79.100~14.04.1","4.4.0-81.104~14.04.1","4.4.0-83.106~14.04.1","4.4.0-87.110~14.04.1","4.4.0-89.112~14.04.1","4.4.0-91.114~14.04.1","4.4.0-92.115~14.04.1","4.4.0-93.116~14.04.1","4.4.0-96.119~14.04.1","4.4.0-97.120~14.04.1","4.4.0-98.121~14.04.1","4.4.0-101.124~14.04.1","4.4.0-103.126~14.04.1","4.4.0-104.127~14.04.1","4.4.0-108.131~14.04.1","4.4.0-109.132~14.04.1","4.4.0-111.134~14.04.1","4.4.0-112.135~14.04.1","4.4.0-116.140~14.04.1","4.4.0-119.143~14.04.1","4.4.0-121.145~14.04.1","4.4.0-124.148~14.04.1","4.4.0-127.153~14.04.1","4.4.0-128.154~14.04.1","4.4.0-130.156~14.04.1","4.4.0-131.157~14.04.1","4.4.0-133.159~14.04.1","4.4.0-134.160~14.04.1","4.4.0-135.161~14.04.1","4.4.0-137.163~14.04.1","4.4.0-138.164~14.04.1","4.4.0-139.165~14.04.1","4.4.0-140.166~14.04.1","4.4.0-141.167~14.04.1","4.4.0-142.168~14.04.1","4.4.0-143.169~14.04.2","4.4.0-144.170~14.04.1","4.4.0-146.172~14.04.1","4.4.0-148.174~14.04.1","4.4.0-150.176~14.04.1","4.4.0-151.178~14.04.1","4.4.0-154.181~14.04.1","4.4.0-157.185~14.04.1","4.4.0-159.187~14.04.1","4.4.0-161.189~14.04.1","4.4.0-164.192~14.04.1","4.4.0-165.193~14.04.1","4.4.0-166.195~14.04.1","4.4.0-168.197~14.04.1","4.4.0-169.198~14.04.1","4.4.0-170.199~14.04.1","4.4.0-171.200~14.04.1","4.4.0-173.203~14.04.1","4.4.0-174.204~14.04.1","4.4.0-176.206~14.04.1","4.4.0-177.207~14.04.1","4.4.0-178.208~14.04.1","4.4.0-179.209~14.04.1","4.4.0-184.214~14.04.1","4.4.0-185.215~14.04.1","4.4.0-186.216~14.04.1","4.4.0-187.217~14.04.1","4.4.0-189.219~14.04.1","4.4.0-190.220~14.04.1","4.4.0-193.224~14.04.1","4.4.0-194.226~14.04.1","4.4.0-197.229~14.04.1","4.4.0-198.230~14.04.1","4.4.0-200.232~14.04.1","4.4.0-201.233~14.04.1","4.4.0-203.235~14.04.1","4.4.0-204.236~14.04.1","4.4.0-206.238~14.04.1","4.4.0-208.240~14.04.1","4.4.0-209.241~14.04.1","4.4.0-210.242~14.04.1","4.4.0-211.243~14.04.1","4.4.0-212.244~14.04.1","4.4.0-213.245~14.04.1","4.4.0-214.246~14.04.1","4.4.0-215.247~14.04.1","4.4.0-218.251~14.04.1","4.4.0-219.252~14.04.1","4.4.0-221.254~14.04.1","4.4.0-222.255~14.04.1","4.4.0-223.256~14.04.1","4.4.0-224.257~14.04.1","4.4.0-227.261~14.04.1","4.4.0-229.263~14.04.1","4.4.0-230.264~14.04.1","4.4.0-231.265~14.04.1","4.4.0-233.267~14.04.1","4.4.0-234.268~14.04.1","4.4.0-235.269~14.04.1","4.4.0-236.270~14.04.1","4.4.0-237.271~14.04.1","4.4.0-239.273~14.04.1","4.4.0-240.274~14.04.1","4.4.0-241.275~14.04.1","4.4.0-242.276~14.04.1","4.4.0-243.277~14.04.1","4.4.0-244.278~14.04.1","4.4.0-245.279~14.04.1","4.4.0-246.280~14.04.1","4.4.0-248.282~14.04.1","4.4.0-250.284~14.04.1","4.4.0-251.285~14.04.1","4.4.0-252.286~14.04.1","4.4.0-253.287~14.04.1","4.4.0-254.288~14.04.1","4.4.0-256.290~14.04.1","4.4.0-257.291~14.04.1","4.4.0-258.292~14.04.2","4.4.0-259.293~14.04.1","4.4.0-260.294~14.04.1","4.4.0-261.295~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-262.296"}]}],"versions":["4.2.0-16.19","4.2.0-17.21","4.2.0-19.23","4.3.0-1.10","4.3.0-2.11","4.3.0-5.16","4.3.0-6.17","4.3.0-7.18","4.4.0-2.16","4.4.0-4.19","4.4.0-6.21","4.4.0-7.22","4.4.0-8.23","4.4.0-9.24","4.4.0-10.25","4.4.0-11.26","4.4.0-12.28","4.4.0-13.29","4.4.0-14.30","4.4.0-15.31","4.4.0-16.32","4.4.0-17.33","4.4.0-18.34","4.4.0-21.37","4.4.0-22.39","4.4.0-22.40","4.4.0-24.43","4.4.0-28.47","4.4.0-31.50","4.4.0-34.53","4.4.0-36.55","4.4.0-38.57","4.4.0-42.62","4.4.0-43.63","4.4.0-45.66","4.4.0-47.68","4.4.0-51.72","4.4.0-53.74","4.4.0-57.78","4.4.0-59.80","4.4.0-62.83","4.4.0-63.84","4.4.0-64.85","4.4.0-65.86","4.4.0-66.87","4.4.0-67.88","4.4.0-70.91","4.4.0-71.92","4.4.0-72.93","4.4.0-75.96","4.4.0-77.98","4.4.0-78.99","4.4.0-79.100","4.4.0-81.104","4.4.0-83.106","4.4.0-87.110","4.4.0-89.112","4.4.0-91.114","4.4.0-92.115","4.4.0-93.116","4.4.0-96.119","4.4.0-97.120","4.4.0-98.121","4.4.0-101.124","4.4.0-103.126","4.4.0-104.127","4.4.0-108.131","4.4.0-109.132","4.4.0-112.135","4.4.0-116.140","4.4.0-119.143","4.4.0-121.145","4.4.0-122.146","4.4.0-124.148","4.4.0-127.153","4.4.0-128.154","4.4.0-130.156","4.4.0-131.157","4.4.0-133.159","4.4.0-134.160","4.4.0-135.161","4.4.0-137.163","4.4.0-138.164","4.4.0-139.165","4.4.0-140.166","4.4.0-141.167","4.4.0-142.168","4.4.0-143.169","4.4.0-145.171","4.4.0-146.172","4.4.0-148.174","4.4.0-150.176","4.4.0-151.178","4.4.0-154.181","4.4.0-157.185","4.4.0-159.187","4.4.0-161.189","4.4.0-164.192","4.4.0-165.193","4.4.0-166.195","4.4.0-168.197","4.4.0-169.198","4.4.0-170.199","4.4.0-171.200","4.4.0-173.203","4.4.0-174.204","4.4.0-176.206","4.4.0-177.207","4.4.0-178.208","4.4.0-179.209","4.4.0-184.214","4.4.0-185.215","4.4.0-186.216","4.4.0-187.217","4.4.0-189.219","4.4.0-190.220","4.4.0-193.224","4.4.0-194.226","4.4.0-197.229","4.4.0-198.230","4.4.0-200.232","4.4.0-201.233","4.4.0-203.235","4.4.0-204.236","4.4.0-206.238","4.4.0-208.240","4.4.0-209.241","4.4.0-210.242","4.4.0-211.243","4.4.0-212.244","4.4.0-213.245","4.4.0-214.246","4.4.0-216.249","4.4.0-217.250","4.4.0-218.251","4.4.0-219.252","4.4.0-221.254","4.4.0-222.255","4.4.0-223.256","4.4.0-224.257","4.4.0-227.261","4.4.0-229.263","4.4.0-230.264","4.4.0-231.265","4.4.0-233.267","4.4.0-234.268","4.4.0-235.269","4.4.0-236.270","4.4.0-237.271","4.4.0-239.273","4.4.0-240.274","4.4.0-241.275","4.4.0-242.276","4.4.0-243.277","4.4.0-244.278","4.4.0-245.279","4.4.0-246.280","4.4.0-248.282","4.4.0-250.284","4.4.0-251.285","4.4.0-252.286","4.4.0-253.287","4.4.0-254.288","4.4.0-256.290","4.4.0-257.291","4.4.0-258.292","4.4.0-259.293","4.4.0-260.294","4.4.0-261.295"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1177.192"}]}],"versions":["4.4.0-1001.10","4.4.0-1003.12","4.4.0-1004.13","4.4.0-1007.16","4.4.0-1009.18","4.4.0-1011.20","4.4.0-1012.21","4.4.0-1013.22","4.4.0-1016.25","4.4.0-1017.26","4.4.0-1018.27","4.4.0-1020.29","4.4.0-1022.31","4.4.0-1026.35","4.4.0-1028.37","4.4.0-1030.39","4.4.0-1031.40","4.4.0-1032.41","4.4.0-1035.44","4.4.0-1037.46","4.4.0-1038.47","4.4.0-1039.48","4.4.0-1041.50","4.4.0-1043.52","4.4.0-1044.53","4.4.0-1047.56","4.4.0-1048.57","4.4.0-1049.58","4.4.0-1050.59","4.4.0-1052.61","4.4.0-1054.63","4.4.0-1055.64","4.4.0-1057.66","4.4.0-1060.69","4.4.0-1061.70","4.4.0-1062.71","4.4.0-1063.72","4.4.0-1065.75","4.4.0-1066.76","4.4.0-1067.77","4.4.0-1069.79","4.4.0-1070.80","4.4.0-1072.82","4.4.0-1073.83","4.4.0-1074.84","4.4.0-1075.85","4.4.0-1077.87","4.4.0-1079.89","4.4.0-1081.91","4.4.0-1083.93","4.4.0-1084.94","4.4.0-1085.96","4.4.0-1087.98","4.4.0-1088.99","4.4.0-1090.101","4.4.0-1092.103","4.4.0-1094.105","4.4.0-1095.106","4.4.0-1096.107","4.4.0-1098.109","4.4.0-1099.110","4.4.0-1100.111","4.4.0-1101.112","4.4.0-1102.113","4.4.0-1104.115","4.4.0-1105.116","4.4.0-1106.117","4.4.0-1107.118","4.4.0-1109.120","4.4.0-1110.121","4.4.0-1111.123","4.4.0-1112.124","4.4.0-1113.126","4.4.0-1114.127","4.4.0-1117.131","4.4.0-1118.132","4.4.0-1119.133","4.4.0-1121.135","4.4.0-1122.136","4.4.0-1123.137","4.4.0-1124.138","4.4.0-1126.140","4.4.0-1127.141","4.4.0-1128.142","4.4.0-1129.143","4.4.0-1130.144","4.4.0-1131.145","4.4.0-1132.146","4.4.0-1133.147","4.4.0-1134.148","4.4.0-1135.149","4.4.0-1137.151","4.4.0-1138.152","4.4.0-1139.153","4.4.0-1140.154","4.4.0-1143.158","4.4.0-1145.160","4.4.0-1146.161","4.4.0-1147.162","4.4.0-1148.163","4.4.0-1150.165","4.4.0-1151.166","4.4.0-1152.167","4.4.0-1153.168","4.4.0-1154.169","4.4.0-1155.170","4.4.0-1156.171","4.4.0-1157.172","4.4.0-1158.173","4.4.0-1159.174","4.4.0-1160.175","4.4.0-1161.176","4.4.0-1162.177","4.4.0-1163.178","4.4.0-1164.179","4.4.0-1165.180","4.4.0-1166.181","4.4.0-1167.182","4.4.0-1168.183","4.4.0-1169.184","4.4.0-1171.186","4.4.0-1172.187","4.4.0-1173.188","4.4.0-1174.189","4.4.0-1175.190","4.4.0-1176.191"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1176.189~16.04.1"}]}],"versions":["4.15.0-1030.31~16.04.1","4.15.0-1031.33~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1035.37~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1039.41~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43~16.04.1","4.15.0-1043.45~16.04.1","4.15.0-1044.46~16.04.1","4.15.0-1045.47~16.04.1","4.15.0-1047.49~16.04.1","4.15.0-1048.50~16.04.1","4.15.0-1050.52~16.04.1","4.15.0-1051.53~16.04.1","4.15.0-1052.54~16.04.1","4.15.0-1054.56~16.04.1","4.15.0-1056.58~16.04.1","4.15.0-1057.59~16.04.1","4.15.0-1058.60~16.04.1","4.15.0-1060.62~16.04.1","4.15.0-1063.67~16.04.1","4.15.0-1065.69~16.04.1","4.15.0-1066.70~16.04.1","4.15.0-1067.71~16.04.1","4.15.0-1073.77~16.04.1","4.15.0-1074.78~16.04.1","4.15.0-1079.83~16.04.1","4.15.0-1080.84~16.04.1","4.15.0-1082.86~16.04.1","4.15.0-1083.87~16.04.1","4.15.0-1085.90~16.04.1","4.15.0-1088.93~16.04.1","4.15.0-1090.95~16.04.1","4.15.0-1091.96~16.04.1","4.15.0-1093.99~16.04.1","4.15.0-1094.101~16.04.1","4.15.0-1095.102~16.04.1","4.15.0-1096.103~16.04.1","4.15.0-1097.104~16.04.1","4.15.0-1098.105~16.04.1","4.15.0-1099.106~16.04.1","4.15.0-1102.109~16.04.1","4.15.0-1103.110~16.04.1","4.15.0-1106.113~16.04.1","4.15.0-1109.116~16.04.1","4.15.0-1110.117~16.04.1","4.15.0-1111.118~16.04.1","4.15.0-1112.119~16.04.1","4.15.0-1113.120~16.04.1","4.15.0-1115.122~16.04.1","4.15.0-1116.123~16.04.1","4.15.0-1118.125~16.04.1","4.15.0-1119.126~16.04.2","4.15.0-1120.128~16.04.1","4.15.0-1123.132~16.04.1","4.15.0-1124.133~16.04.1","4.15.0-1126.135~16.04.2","4.15.0-1127.136~16.04.1","4.15.0-1128.137~16.04.1","4.15.0-1130.139~16.04.1","4.15.0-1133.143~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.154~16.04.1","4.15.0-1143.155~16.04.1","4.15.0-1146.158~16.04.2","4.15.0-1147.159~16.04.1","4.15.0-1148.160~16.04.1","4.15.0-1151.164~16.04.1","4.15.0-1153.166~16.04.1","4.15.0-1154.167~16.04.1","4.15.0-1155.168~16.04.1","4.15.0-1156.169~16.04.1","4.15.0-1157.170~16.04.1","4.15.0-1158.171~16.04.1","4.15.0-1159.172~16.04.1","4.15.0-1160.173~16.04.1","4.15.0-1161.174~16.04.1","4.15.0-1162.175~16.04.1","4.15.0-1163.176~16.04.1","4.15.0-1164.177~16.04.1","4.15.0-1165.178~16.04.1","4.15.0-1166.179~16.04.1","4.15.0-1167.180~16.04.1","4.15.0-1168.181~16.04.1","4.15.0-1169.182~16.04.1","4.15.0-1170.183~16.04.1","4.15.0-1172.185~16.04.1","4.15.0-1173.186~16.04.1","4.15.0-1174.187~16.04.1","4.15.0-1175.188~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1184.199~16.04.1"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1","4.15.0-1022.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1025.26~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1030.31~16.04.1","4.15.0-1031.32~16.04.1","4.15.0-1032.33~16.04.1","4.15.0-1035.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1039.43","4.15.0-1040.44","4.15.0-1041.45","4.15.0-1042.46","4.15.0-1045.49","4.15.0-1046.50","4.15.0-1047.51","4.15.0-1049.54","4.15.0-1050.55","4.15.0-1051.56","4.15.0-1052.57","4.15.0-1055.60","4.15.0-1056.61","4.15.0-1057.62","4.15.0-1059.64","4.15.0-1060.65","4.15.0-1061.66","4.15.0-1063.68","4.15.0-1064.69","4.15.0-1066.71","4.15.0-1067.72","4.15.0-1069.74","4.15.0-1071.76","4.15.0-1075.80","4.15.0-1077.82","4.15.0-1082.92~16.04.1","4.15.0-1083.93~16.04.1","4.15.0-1089.99~16.04.1","4.15.0-1091.101~16.04.1","4.15.0-1092.102~16.04.1","4.15.0-1093.103~16.04.1","4.15.0-1095.105~16.04.1","4.15.0-1096.106~16.04.1","4.15.0-1098.109~16.04.1","4.15.0-1100.111~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1103.114~16.04.1","4.15.0-1106.118~16.04.1","4.15.0-1108.120~16.04.1","4.15.0-1109.121~16.04.1","4.15.0-1110.122~16.04.1","4.15.0-1111.123~16.04.1","4.15.0-1112.124~16.04.1","4.15.0-1113.126~16.04.1","4.15.0-1114.127~16.04.1","4.15.0-1115.128~16.04.1","4.15.0-1118.131~16.04.1","4.15.0-1121.134~16.04.1","4.15.0-1122.135~16.04.1","4.15.0-1123.136~16.04.1","4.15.0-1124.137~16.04.1","4.15.0-1125.138~16.04.1","4.15.0-1126.139~16.04.1","4.15.0-1127.140~16.04.1","4.15.0-1129.142~16.04.1","4.15.0-1130.143~16.04.1","4.15.0-1131.144~16.04.1","4.15.0-1133.146~16.04.1","4.15.0-1134.147~16.04.1","4.15.0-1136.149~16.04.1","4.15.0-1137.150~16.04.1","4.15.0-1138.151~16.04.1","4.15.0-1139.152~16.04.1","4.15.0-1142.156~16.04.1","4.15.0-1145.160~16.04.1","4.15.0-1146.161~16.04.1","4.15.0-1149.164~16.04.1","4.15.0-1150.165~16.04.1","4.15.0-1151.166~16.04.1","4.15.0-1153.168~16.04.1","4.15.0-1159.174~16.04.1","4.15.0-1162.177~16.04.1","4.15.0-1163.178~16.04.1","4.15.0-1164.179~16.04.1","4.15.0-1165.180~16.04.1","4.15.0-1166.181~16.04.1","4.15.0-1167.182~16.04.1","4.15.0-1168.183~16.04.1","4.15.0-1169.184~16.04.1","4.15.0-1170.185~16.04.1","4.15.0-1171.186~16.04.1","4.15.0-1172.187~16.04.1","4.15.0-1173.188~16.04.1","4.15.0-1174.189~16.04.1","4.15.0-1175.190~16.04.1","4.15.0-1176.191~16.04.1","4.15.0-1177.192~16.04.1","4.15.0-1178.193~16.04.1","4.15.0-1179.194~16.04.1","4.15.0-1180.195~16.04.1","4.15.0-1181.196~16.04.1","4.15.0-1182.197~16.04.1","4.15.0-1183.198~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1169.186~16.04.1"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1","4.15.0-1018.19~16.04.2","4.15.0-1019.20~16.04.1","4.15.0-1021.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1024.25~16.04.2","4.15.0-1025.26~16.04.1","4.15.0-1026.27~16.04.1","4.15.0-1027.28~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1029.31~16.04.1","4.15.0-1030.32~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1034.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1046.49","4.15.0-1047.50","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.56","4.15.0-1055.59","4.15.0-1058.62","4.15.0-1060.64","4.15.0-1061.65","4.15.0-1071.81~16.04.1","4.15.0-1077.87~16.04.1","4.15.0-1078.88~16.04.1","4.15.0-1080.90~16.04.1","4.15.0-1081.92~16.04.1","4.15.0-1083.94~16.04.1","4.15.0-1084.95~16.04.1","4.15.0-1086.98~16.04.1","4.15.0-1087.100~16.04.1","4.15.0-1088.101~16.04.1","4.15.0-1090.103~16.04.1","4.15.0-1091.104~16.04.1","4.15.0-1092.105~16.04.1","4.15.0-1093.106~16.04.1","4.15.0-1094.107~16.04.1","4.15.0-1095.108~16.04.1","4.15.0-1096.109~16.04.1","4.15.0-1097.110~16.04.1","4.15.0-1098.111~16.04.1","4.15.0-1099.112~16.04.1","4.15.0-1100.113~16.04.1","4.15.0-1103.116~16.04.1","4.15.0-1106.120~16.04.1","4.15.0-1107.121~16.04.1","4.15.0-1108.122~16.04.1","4.15.0-1109.123~16.04.1","4.15.0-1110.124~16.04.1","4.15.0-1111.125~16.04.1","4.15.0-1112.126~16.04.1","4.15.0-1114.128~16.04.1","4.15.0-1115.129~16.04.1","4.15.0-1116.130~16.04.1","4.15.0-1118.132~16.04.1","4.15.0-1119.133~16.04.1","4.15.0-1120.134~16.04.1","4.15.0-1121.135~16.04.1","4.15.0-1122.136~16.04.1","4.15.0-1124.138~16.04.1","4.15.0-1127.142~16.04.1","4.15.0-1130.146~16.04.1","4.15.0-1131.147~16.04.1","4.15.0-1134.150~16.04.2","4.15.0-1135.151~16.04.2","4.15.0-1136.152~16.04.1","4.15.0-1137.153~16.04.1","4.15.0-1138.154~16.04.1","4.15.0-1141.157~16.04.2","4.15.0-1142.158~16.04.1","4.15.0-1143.159~16.04.1","4.15.0-1146.162~16.04.1","4.15.0-1147.163~16.04.1","4.15.0-1148.164~16.04.1","4.15.0-1149.165~16.04.1","4.15.0-1150.166~16.04.1","4.15.0-1151.167~16.04.1","4.15.0-1152.168~16.04.1","4.15.0-1153.170~16.04.1","4.15.0-1154.171~16.04.1","4.15.0-1155.172~16.04.1","4.15.0-1156.173~16.04.1","4.15.0-1157.174~16.04.1","4.15.0-1158.175~16.04.1","4.15.0-1159.176~16.04.1","4.15.0-1160.177~16.04.1","4.15.0-1161.178~16.04.1","4.15.0-1162.179~16.04.1","4.15.0-1163.180~16.04.1","4.15.0-1164.181~16.04.1","4.15.0-1165.182~16.04.1","4.15.0-1166.183~16.04.1","4.15.0-1167.184~16.04.2","4.15.0-1168.185~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-232.244~16.04.1"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1","4.15.0-33.36~16.04.1","4.15.0-34.37~16.04.1","4.15.0-36.39~16.04.1","4.15.0-38.41~16.04.1","4.15.0-39.42~16.04.1","4.15.0-42.45~16.04.1","4.15.0-43.46~16.04.1","4.15.0-45.48~16.04.1","4.15.0-46.49~16.04.1","4.15.0-47.50~16.04.1","4.15.0-48.51~16.04.1","4.15.0-50.54~16.04.1","4.15.0-51.55~16.04.1","4.15.0-52.56~16.04.1","4.15.0-54.58~16.04.1","4.15.0-55.60~16.04.2","4.15.0-58.64~16.04.1","4.15.0-60.67~16.04.1","4.15.0-62.69~16.04.1","4.15.0-64.73~16.04.1","4.15.0-65.74~16.04.1","4.15.0-66.75~16.04.1","4.15.0-69.78~16.04.1","4.15.0-70.79~16.04.1","4.15.0-72.81~16.04.1","4.15.0-74.83~16.04.1","4.15.0-76.86~16.04.1","4.15.0-88.88~16.04.1","4.15.0-91.92~16.04.1","4.15.0-96.97~16.04.1","4.15.0-99.100~16.04.1","4.15.0-101.102~16.04.1","4.15.0-106.107~16.04.1","4.15.0-107.108~16.04.1","4.15.0-112.113~16.04.1","4.15.0-115.116~16.04.1","4.15.0-117.118~16.04.1","4.15.0-118.119~16.04.1","4.15.0-120.122~16.04.1","4.15.0-122.124~16.04.1","4.15.0-123.126~16.04.1","4.15.0-126.129~16.04.1","4.15.0-128.131~16.04.1","4.15.0-129.132~16.04.1","4.15.0-132.136~16.04.1","4.15.0-133.137~16.04.1","4.15.0-136.140~16.04.1","4.15.0-137.141~16.04.1","4.15.0-139.143~16.04.1","4.15.0-140.144~16.04.1","4.15.0-142.146~16.04.1","4.15.0-143.147~16.04.3","4.15.0-144.148~16.04.1","4.15.0-147.151~16.04.1","4.15.0-151.157~16.04.1","4.15.0-153.160~16.04.1","4.15.0-154.161~16.04.1","4.15.0-156.163~16.04.1","4.15.0-158.166~16.04.1","4.15.0-159.167~16.04.1","4.15.0-161.169~16.04.1","4.15.0-162.170~16.04.1","4.15.0-163.171~16.04.1","4.15.0-166.174~16.04.1","4.15.0-167.175~16.04.1","4.15.0-169.177~16.04.1","4.15.0-171.180~16.04.1","4.15.0-173.182~16.04.1","4.15.0-175.184~16.04.1","4.15.0-176.185~16.04.1","4.15.0-177.186~16.04.1","4.15.0-180.189~16.04.1","4.15.0-184.194~16.04.1","4.15.0-187.198~16.04.1","4.15.0-188.199~16.04.1","4.15.0-189.200~16.04.1","4.15.0-191.202~16.04.1","4.15.0-192.203~16.04.1","4.15.0-193.204~16.04.1","4.15.0-194.205~16.04.1","4.15.0-196.207~16.04.1","4.15.0-197.208~16.04.1","4.15.0-200.211~16.04.2","4.15.0-201.212~16.04.1","4.15.0-202.213~16.04.1","4.15.0-206.217~16.04.1","4.15.0-208.219~16.04.1","4.15.0-209.220~16.04.1","4.15.0-210.221~16.04.1","4.15.0-211.222~16.04.1","4.15.0-212.223~16.04.1","4.15.0-213.224~16.04.1","4.15.0-214.225~16.04.1","4.15.0-216.227~16.04.1","4.15.0-218.229~16.04.1","4.15.0-219.230~16.04.1","4.15.0-220.231~16.04.1","4.15.0-221.232~16.04.1","4.15.0-222.233~16.04.1","4.15.0-223.235~16.04.1","4.15.0-224.236~16.04.1","4.15.0-225.237~16.04.1","4.15.0-226.238~16.04.1","4.15.0-227.239~16.04.1","4.15.0-228.240~16.04.1","4.15.0-229.241~16.04.1","4.15.0-230.242~16.04.1","4.15.0-231.243~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1140.151"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13","4.4.0-1009.14","4.4.0-1010.15","4.4.0-1012.17","4.4.0-1013.18","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1020.25","4.4.0-1021.26","4.4.0-1023.28","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1029.34","4.4.0-1031.37","4.4.0-1032.38","4.4.0-1033.39","4.4.0-1035.41","4.4.0-1036.42","4.4.0-1037.43","4.4.0-1038.44","4.4.0-1039.45","4.4.0-1040.46","4.4.0-1041.47","4.4.0-1043.49","4.4.0-1044.50","4.4.0-1046.52","4.4.0-1047.53","4.4.0-1048.55","4.4.0-1051.58","4.4.0-1052.59","4.4.0-1054.61","4.4.0-1056.63","4.4.0-1058.65","4.4.0-1059.66","4.4.0-1060.67","4.4.0-1062.69","4.4.0-1063.70","4.4.0-1064.71","4.4.0-1065.72","4.4.0-1066.73","4.4.0-1068.75","4.4.0-1069.76","4.4.0-1070.77","4.4.0-1071.78","4.4.0-1075.82","4.4.0-1076.83","4.4.0-1077.84","4.4.0-1078.85","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1082.91","4.4.0-1084.93","4.4.0-1085.94","4.4.0-1087.96","4.4.0-1088.97","4.4.0-1089.98","4.4.0-1090.99","4.4.0-1091.100","4.4.0-1092.101","4.4.0-1093.102","4.4.0-1094.103","4.4.0-1095.104","4.4.0-1096.105","4.4.0-1097.106","4.4.0-1098.107","4.4.0-1099.108","4.4.0-1100.109","4.4.0-1102.111","4.4.0-1103.112","4.4.0-1104.113","4.4.0-1105.114","4.4.0-1108.118","4.4.0-1110.120","4.4.0-1111.121","4.4.0-1112.122","4.4.0-1113.123","4.4.0-1114.124","4.4.0-1115.125","4.4.0-1116.126","4.4.0-1117.127","4.4.0-1118.128","4.4.0-1119.129","4.4.0-1120.130","4.4.0-1121.131","4.4.0-1122.132","4.4.0-1123.133","4.4.0-1124.134","4.4.0-1125.135","4.4.0-1126.136","4.4.0-1128.138","4.4.0-1129.139","4.4.0-1130.140","4.4.0-1131.141","4.4.0-1132.142","4.4.0-1134.144","4.4.0-1135.145","4.4.0-1136.146","4.4.0-1137.147","4.4.0-1138.148","4.4.0-1139.149"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1138.149~16.04.1"}]}],"versions":["4.15.0-1007.9~16.04.1","4.15.0-1008.10~16.04.1","4.15.0-1009.11~16.04.1","4.15.0-1010.12~16.04.1","4.15.0-1011.13~16.04.1","4.15.0-1013.15~16.04.1","4.15.0-1014.16~16.04.1","4.15.0-1015.17~16.04.1","4.15.0-1017.19~16.04.2","4.15.0-1018.20~16.04.1","4.15.0-1021.23~16.04.1","4.15.0-1022.25~16.04.1","4.15.0-1023.26~16.04.1","4.15.0-1025.28~16.04.1","4.15.0-1026.29~16.04.1","4.15.0-1027.30~16.04.1","4.15.0-1029.32~16.04.1","4.15.0-1030.33~16.04.1","4.15.0-1031.34~16.04.1","4.15.0-1033.36~16.04.1","4.15.0-1035.38~16.04.1","4.15.0-1037.41~16.04.1","4.15.0-1038.42~16.04.1","4.15.0-1039.43~16.04.1","4.15.0-1045.49~16.04.1","4.15.0-1046.50~16.04.1","4.15.0-1050.54~16.04.1","4.15.0-1051.55~16.04.1","4.15.0-1053.57~16.04.1","4.15.0-1054.58~16.04.1","4.15.0-1056.61~16.04.1","4.15.0-1058.64~16.04.1","4.15.0-1059.65~16.04.1","4.15.0-1061.67~16.04.1","4.15.0-1062.68~16.04.1","4.15.0-1064.71~16.04.1","4.15.0-1065.73~16.04.1","4.15.0-1066.74~16.04.1","4.15.0-1067.75~16.04.1","4.15.0-1068.76~16.04.1","4.15.0-1069.77~16.04.1","4.15.0-1070.78~16.04.1","4.15.0-1071.79~16.04.1","4.15.0-1072.80~16.04.1","4.15.0-1075.83~16.04.1","4.15.0-1078.86~16.04.1","4.15.0-1079.87~16.04.1","4.15.0-1080.88~16.04.1","4.15.0-1081.89~16.04.1","4.15.0-1082.90~16.04.1","4.15.0-1083.91~16.04.1","4.15.0-1084.92~16.04.1","4.15.0-1085.93~16.04.1","4.15.0-1086.94~16.04.1","4.15.0-1087.95~16.04.1","4.15.0-1089.98~16.04.1","4.15.0-1090.99~16.04.1","4.15.0-1091.100~16.04.1","4.15.0-1092.101~16.04.1","4.15.0-1093.102~16.04.1","4.15.0-1095.104~16.04.1","4.15.0-1098.108~16.04.1","4.15.0-1101.112~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1104.115~16.04.1","4.15.0-1105.116~16.04.1","4.15.0-1106.117~16.04.1","4.15.0-1107.118~16.04.1","4.15.0-1108.119~16.04.1","4.15.0-1111.122~16.04.2","4.15.0-1112.123~16.04.1","4.15.0-1113.124~16.04.1","4.15.0-1115.126~16.04.1","4.15.0-1116.127~16.04.1","4.15.0-1117.128~16.04.1","4.15.0-1118.129~16.04.1","4.15.0-1119.130~16.04.1","4.15.0-1120.131~16.04.1","4.15.0-1121.132~16.04.1","4.15.0-1122.133~16.04.1","4.15.0-1123.134~16.04.1","4.15.0-1124.135~16.04.1","4.15.0-1125.136~16.04.1","4.15.0-1126.137~16.04.1","4.15.0-1127.138~16.04.1","4.15.0-1128.139~16.04.1","4.15.0-1129.140~16.04.1","4.15.0-1130.141~16.04.1","4.15.0-1131.142~16.04.1","4.15.0-1132.143~16.04.1","4.15.0-1133.144~16.04.1","4.15.0-1134.145~16.04.1","4.15.0-1135.146~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1"]},{"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:Pro:FIPS-updates:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1108.115"}]}],"versions":["4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1008.10","4.4.0-1010.13","4.4.0-1011.14","4.4.0-1012.16","4.4.0-1013.17","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1021.26","4.4.0-1022.27","4.4.0-1023.28","4.4.0-1025.30","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1028.33","4.4.0-1029.34","4.4.0-1031.36","4.4.0-1032.37","4.4.0-1033.38","4.4.0-1034.39","4.4.0-1041.46","4.4.0-1042.47","4.4.0-1043.48","4.4.0-1044.49","4.4.0-1045.50","4.4.0-1046.51","4.4.0-1048.53","4.4.0-1049.55","4.4.0-1051.57","4.4.0-1052.58","4.4.0-1054.60","4.4.0-1055.61","4.4.0-1056.62","4.4.0-1057.63","4.4.0-1058.64","4.4.0-1060.66","4.4.0-1061.67","4.4.0-1062.68","4.4.0-1063.69","4.4.0-1064.70","4.4.0-1065.71","4.4.0-1066.72","4.4.0-1067.73","4.4.0-1068.74","4.4.0-1069.75","4.4.0-1071.77","4.4.0-1072.78","4.4.0-1073.79","4.4.0-1074.80","4.4.0-1077.84","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1081.88","4.4.0-1082.89","4.4.0-1083.90","4.4.0-1084.91","4.4.0-1085.92","4.4.0-1086.93","4.4.0-1088.95","4.4.0-1089.96","4.4.0-1090.97","4.4.0-1091.98","4.4.0-1092.99","4.4.0-1093.100","4.4.0-1094.101","4.4.0-1095.102","4.4.0-1097.104","4.4.0-1099.106","4.4.0-1100.107","4.4.0-1101.108","4.4.0-1102.109","4.4.0-1103.110","4.4.0-1104.111","4.4.0-1105.112","4.4.0-1106.113","4.4.0-1107.114"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1001.1","4.4.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-232.244"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35","4.15.0-33.36","4.15.0-34.37","4.15.0-36.39","4.15.0-38.41","4.15.0-39.42","4.15.0-42.45","4.15.0-43.46","4.15.0-44.47","4.15.0-45.48","4.15.0-46.49","4.15.0-47.50","4.15.0-48.51","4.15.0-50.54","4.15.0-51.55","4.15.0-52.56","4.15.0-54.58","4.15.0-55.60","4.15.0-58.64","4.15.0-60.67","4.15.0-62.69","4.15.0-64.73","4.15.0-65.74","4.15.0-66.75","4.15.0-69.78","4.15.0-70.79","4.15.0-72.81","4.15.0-74.84","4.15.0-76.86","4.15.0-88.88","4.15.0-91.92","4.15.0-96.97","4.15.0-99.100","4.15.0-101.102","4.15.0-106.107","4.15.0-108.109","4.15.0-109.110","4.15.0-111.112","4.15.0-112.113","4.15.0-115.116","4.15.0-117.118","4.15.0-118.119","4.15.0-121.123","4.15.0-122.124","4.15.0-123.126","4.15.0-124.127","4.15.0-126.129","4.15.0-128.131","4.15.0-129.132","4.15.0-130.134","4.15.0-132.136","4.15.0-134.138","4.15.0-135.139","4.15.0-136.140","4.15.0-137.141","4.15.0-139.143","4.15.0-140.144","4.15.0-141.145","4.15.0-142.146","4.15.0-143.147","4.15.0-144.148","4.15.0-147.151","4.15.0-151.157","4.15.0-153.160","4.15.0-154.161","4.15.0-156.163","4.15.0-158.166","4.15.0-159.167","4.15.0-161.169","4.15.0-162.170","4.15.0-163.171","4.15.0-166.174","4.15.0-167.175","4.15.0-169.177","4.15.0-171.180","4.15.0-173.182","4.15.0-175.184","4.15.0-176.185","4.15.0-177.186","4.15.0-180.189","4.15.0-184.194","4.15.0-187.198","4.15.0-188.199","4.15.0-189.200","4.15.0-191.202","4.15.0-192.203","4.15.0-193.204","4.15.0-194.205","4.15.0-196.207","4.15.0-197.208","4.15.0-200.211","4.15.0-201.212","4.15.0-202.213","4.15.0-204.215","4.15.0-206.217","4.15.0-208.220","4.15.0-209.220","4.15.0-210.221","4.15.0-211.222","4.15.0-212.223","4.15.0-213.224","4.15.0-214.225","4.15.0-216.227","4.15.0-218.229","4.15.0-219.230","4.15.0-220.231","4.15.0-221.232","4.15.0-222.233","4.15.0-223.235","4.15.0-224.236","4.15.0-225.237","4.15.0-226.238","4.15.0-227.239","4.15.0-228.240","4.15.0-229.241","4.15.0-230.242","4.15.0-231.243"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1176.189"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1027.27","4.15.0-1029.30","4.15.0-1031.33","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1035.37","4.15.0-1037.39","4.15.0-1039.41","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1043.45","4.15.0-1044.46","4.15.0-1045.47","4.15.0-1047.49","4.15.0-1048.50","4.15.0-1050.52","4.15.0-1051.53","4.15.0-1052.54","4.15.0-1054.56","4.15.0-1056.58","4.15.0-1057.59","4.15.0-1058.60","4.15.0-1060.62","4.15.0-1063.67","4.15.0-1065.69","4.15.0-1066.70","4.15.0-1067.71","4.15.0-1073.77","4.15.0-1076.80","4.15.0-1077.81","4.15.0-1079.83","4.15.0-1080.84","4.15.0-1082.86","4.15.0-1083.87","4.15.0-1086.91","4.15.0-1087.92","4.15.0-1088.93","4.15.0-1090.95","4.15.0-1091.96","4.15.0-1092.98","4.15.0-1093.99","4.15.0-1094.101","4.15.0-1095.102","4.15.0-1096.103","4.15.0-1097.104","4.15.0-1098.105","4.15.0-1099.106","4.15.0-1101.108","4.15.0-1102.109","4.15.0-1103.110","4.15.0-1106.113","4.15.0-1109.116","4.15.0-1110.117","4.15.0-1111.118","4.15.0-1112.119","4.15.0-1114.121","4.15.0-1115.122","4.15.0-1116.123","4.15.0-1118.125","4.15.0-1119.127","4.15.0-1121.129","4.15.0-1123.132","4.15.0-1124.133","4.15.0-1126.135","4.15.0-1127.136","4.15.0-1128.137","4.15.0-1130.139","4.15.0-1133.143","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1150.163","4.15.0-1151.164","4.15.0-1153.166","4.15.0-1154.167","4.15.0-1155.168","4.15.0-1156.169","4.15.0-1157.170","4.15.0-1158.171","4.15.0-1159.172","4.15.0-1160.173","4.15.0-1161.174","4.15.0-1162.175","4.15.0-1163.176","4.15.0-1164.177","4.15.0-1165.178","4.15.0-1166.179","4.15.0-1167.180","4.15.0-1168.181","4.15.0-1169.182","4.15.0-1170.183","4.15.0-1172.185","4.15.0-1173.186","4.15.0-1174.187","4.15.0-1175.188"]},{"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:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1135.145~18.04.1"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~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-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1","5.4.0-1124.134~18.04.1","5.4.0-1125.135~18.04.1","5.4.0-1126.136~18.04.1","5.4.0-1127.137~18.04.2","5.4.0-1128.138~18.04.1","5.4.0-1129.139~18.04.1","5.4.0-1130.140~18.04.1","5.4.0-1131.141~18.04.1","5.4.0-1132.142~18.04.1","5.4.0-1133.143~18.04.1","5.4.0-1134.144~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-azure-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1184.199"}]}],"versions":["4.15.0-1082.92","4.15.0-1083.93","4.15.0-1089.99","4.15.0-1091.101","4.15.0-1092.102","4.15.0-1093.103","4.15.0-1095.105","4.15.0-1096.106","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1102.113","4.15.0-1103.114","4.15.0-1104.116","4.15.0-1106.118","4.15.0-1108.120","4.15.0-1109.121","4.15.0-1110.122","4.15.0-1111.123","4.15.0-1112.125","4.15.0-1113.126","4.15.0-1114.127","4.15.0-1115.128","4.15.0-1118.131","4.15.0-1121.134","4.15.0-1122.135","4.15.0-1123.136","4.15.0-1124.137","4.15.0-1125.138","4.15.0-1126.139","4.15.0-1127.140","4.15.0-1129.142","4.15.0-1130.143","4.15.0-1131.144","4.15.0-1133.146","4.15.0-1134.147","4.15.0-1136.149","4.15.0-1137.150","4.15.0-1138.151","4.15.0-1139.152","4.15.0-1142.156","4.15.0-1145.160","4.15.0-1146.161","4.15.0-1149.164","4.15.0-1150.165","4.15.0-1151.166","4.15.0-1153.168","4.15.0-1157.172","4.15.0-1158.173","4.15.0-1159.174","4.15.0-1161.176","4.15.0-1162.177","4.15.0-1163.178","4.15.0-1164.179","4.15.0-1165.180","4.15.0-1166.181","4.15.0-1167.182","4.15.0-1168.183","4.15.0-1169.184","4.15.0-1170.185","4.15.0-1171.186","4.15.0-1172.187","4.15.0-1173.188","4.15.0-1174.189","4.15.0-1175.190","4.15.0-1176.191","4.15.0-1177.192","4.15.0-1178.193","4.15.0-1179.194","4.15.0-1180.195","4.15.0-1181.196","4.15.0-1182.197","4.15.0-1183.198"]},{"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:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.147~18.04.1"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~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-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.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-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1","5.4.0-1129.136~18.04.1","5.4.0-1130.137~18.04.1","5.4.0-1131.138~18.04.1","5.4.0-1132.139~18.04.1","5.4.0-1133.140~18.04.1","5.4.0-1134.141~18.04.1","5.4.0-1135.142~18.04.1","5.4.0-1136.143~18.04.1","5.4.0-1137.144~18.04.1","5.4.0-1138.145~18.04.1","5.4.0-1139.146~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-gcp-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1169.186"}]}],"versions":["4.15.0-1071.81","4.15.0-1077.87","4.15.0-1078.88","4.15.0-1080.90","4.15.0-1081.92","4.15.0-1083.94","4.15.0-1084.95","4.15.0-1086.98","4.15.0-1087.100","4.15.0-1088.101","4.15.0-1090.103","4.15.0-1091.104","4.15.0-1092.105","4.15.0-1093.106","4.15.0-1094.107","4.15.0-1095.108","4.15.0-1096.109","4.15.0-1097.110","4.15.0-1098.111","4.15.0-1099.112","4.15.0-1100.113","4.15.0-1103.116","4.15.0-1106.120","4.15.0-1107.121","4.15.0-1108.122","4.15.0-1109.123","4.15.0-1110.124","4.15.0-1111.125","4.15.0-1112.126","4.15.0-1114.128","4.15.0-1115.129","4.15.0-1116.130","4.15.0-1118.132","4.15.0-1119.133","4.15.0-1120.134","4.15.0-1121.135","4.15.0-1122.136","4.15.0-1124.138","4.15.0-1127.142","4.15.0-1130.146","4.15.0-1131.147","4.15.0-1134.150","4.15.0-1135.151","4.15.0-1136.152","4.15.0-1137.153","4.15.0-1138.154","4.15.0-1141.157","4.15.0-1142.158","4.15.0-1143.159","4.15.0-1145.161","4.15.0-1146.162","4.15.0-1147.163","4.15.0-1148.164","4.15.0-1149.165","4.15.0-1150.166","4.15.0-1151.167","4.15.0-1152.168","4.15.0-1153.170","4.15.0-1154.171","4.15.0-1155.172","4.15.0-1156.173","4.15.0-1157.174","4.15.0-1158.175","4.15.0-1159.176","4.15.0-1160.177","4.15.0-1161.178","4.15.0-1162.179","4.15.0-1163.180","4.15.0-1164.181","4.15.0-1165.182","4.15.0-1166.183","4.15.0-1167.184","4.15.0-1168.185"]},{"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:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1139.148~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~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-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1128.137~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~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:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-200.220~18.04.1"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1","5.4.0-181.201~18.04.1","5.4.0-182.202~18.04.1","5.4.0-186.206~18.04.1","5.4.0-187.207~18.04.1","5.4.0-189.209~18.04.1","5.4.0-190.210~18.04.1","5.4.0-192.212~18.04.1","5.4.0-193.213~18.04.1","5.4.0-195.215~18.04.1","5.4.0-196.216~18.04.1","5.4.0-198.218~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1082.87~18.04.1"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1076.81~18.04.1","5.4.0-1077.82~18.04.1","5.4.0-1078.83~18.04.1","5.4.0-1079.84~18.04.1","5.4.0-1080.85~18.04.1","5.4.0-1081.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1159.164"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1026.26","4.15.0-1027.27","4.15.0-1028.28","4.15.0-1029.29","4.15.0-1030.30","4.15.0-1031.31","4.15.0-1032.32","4.15.0-1034.34","4.15.0-1035.35","4.15.0-1036.36","4.15.0-1038.38","4.15.0-1039.39","4.15.0-1042.42","4.15.0-1043.43","4.15.0-1044.44","4.15.0-1046.46","4.15.0-1047.47","4.15.0-1048.48","4.15.0-1050.50","4.15.0-1051.51","4.15.0-1052.52","4.15.0-1053.53","4.15.0-1056.57","4.15.0-1058.59","4.15.0-1059.60","4.15.0-1060.61","4.15.0-1067.68","4.15.0-1069.70","4.15.0-1071.72","4.15.0-1072.73","4.15.0-1074.75","4.15.0-1075.76","4.15.0-1077.79","4.15.0-1079.81","4.15.0-1081.83","4.15.0-1082.84","4.15.0-1084.86","4.15.0-1085.87","4.15.0-1086.88","4.15.0-1087.89","4.15.0-1088.90","4.15.0-1089.91","4.15.0-1090.92","4.15.0-1091.93","4.15.0-1092.94","4.15.0-1094.96","4.15.0-1097.99","4.15.0-1098.100","4.15.0-1099.101","4.15.0-1100.102","4.15.0-1101.103","4.15.0-1102.104","4.15.0-1103.105","4.15.0-1105.107","4.15.0-1106.108","4.15.0-1107.109","4.15.0-1109.112","4.15.0-1110.113","4.15.0-1112.115","4.15.0-1113.116","4.15.0-1114.117","4.15.0-1116.119","4.15.0-1119.123","4.15.0-1122.127","4.15.0-1123.128","4.15.0-1125.130","4.15.0-1126.131","4.15.0-1127.132","4.15.0-1128.133","4.15.0-1129.134","4.15.0-1132.137","4.15.0-1133.138","4.15.0-1134.139","4.15.0-1135.140","4.15.0-1136.141","4.15.0-1137.142","4.15.0-1138.143","4.15.0-1139.144","4.15.0-1140.145","4.15.0-1141.146","4.15.0-1142.147","4.15.0-1143.148","4.15.0-1144.149","4.15.0-1145.150","4.15.0-1146.151","4.15.0-1147.152","4.15.0-1148.153","4.15.0-1149.154","4.15.0-1150.155","4.15.0-1151.156","4.15.0-1152.157","4.15.0-1153.158","4.15.0-1154.159","4.15.0-1155.160","4.15.0-1156.161","4.15.0-1157.162","4.15.0-1158.163"]},{"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:Pro:18.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1138.149"}]}],"versions":["4.15.0-1007.9","4.15.0-1008.10","4.15.0-1009.11","4.15.0-1010.12","4.15.0-1011.13","4.15.0-1013.15","4.15.0-1014.16","4.15.0-1015.17","4.15.0-1017.19","4.15.0-1018.20","4.15.0-1021.23","4.15.0-1022.25","4.15.0-1023.26","4.15.0-1025.28","4.15.0-1026.29","4.15.0-1027.30","4.15.0-1029.32","4.15.0-1030.33","4.15.0-1031.34","4.15.0-1033.36","4.15.0-1035.39","4.15.0-1037.41","4.15.0-1038.42","4.15.0-1039.43","4.15.0-1045.49","4.15.0-1047.51","4.15.0-1048.52","4.15.0-1050.54","4.15.0-1051.55","4.15.0-1053.57","4.15.0-1054.58","4.15.0-1057.62","4.15.0-1058.64","4.15.0-1059.65","4.15.0-1061.67","4.15.0-1062.68","4.15.0-1063.70","4.15.0-1064.71","4.15.0-1065.73","4.15.0-1066.74","4.15.0-1067.75","4.15.0-1068.76","4.15.0-1069.77","4.15.0-1070.78","4.15.0-1071.79","4.15.0-1072.80","4.15.0-1075.83","4.15.0-1078.86","4.15.0-1079.87","4.15.0-1080.88","4.15.0-1081.89","4.15.0-1082.90","4.15.0-1083.91","4.15.0-1084.92","4.15.0-1085.93","4.15.0-1086.94","4.15.0-1087.95","4.15.0-1089.98","4.15.0-1090.99","4.15.0-1091.100","4.15.0-1092.101","4.15.0-1093.102","4.15.0-1095.104","4.15.0-1098.108","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1106.117","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1120.131","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148"]},{"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:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1134.143~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1131.140~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1119.131~18.04.1"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1","5.4.0-1108.120~18.04.1","5.4.0-1109.121~18.04.1","5.4.0-1110.122~18.04.1","5.4.0-1111.123~18.04.1","5.4.0-1112.124~18.04.1","5.4.0-1114.126~18.04.1","5.4.0-1115.127~18.04.1","5.4.0-1116.128~18.04.1","5.4.0-1117.129~18.04.1","5.4.0-1118.130~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-2114.120"}]}],"versions":["4.15.0-2000.4","4.15.0-2018.18","4.15.0-2021.21","4.15.0-2022.22","4.15.0-2024.24","4.15.0-2025.25","4.15.0-2026.26","4.15.0-2027.27","4.15.0-2030.31","4.15.0-2031.32","4.15.0-2033.34","4.15.0-2034.35","4.15.0-2035.37","4.15.0-2036.38","4.15.0-2037.39","4.15.0-2038.40","4.15.0-2039.41","4.15.0-2040.42","4.15.0-2041.43","4.15.0-2042.44","4.15.0-2044.46","4.15.0-2045.47","4.15.0-2048.50","4.15.0-2051.53","4.15.0-2052.54","4.15.0-2053.55","4.15.0-2054.56","4.15.0-2055.57","4.15.0-2056.58","4.15.0-2057.59","4.15.0-2059.61","4.15.0-2060.62","4.15.0-2061.63","4.15.0-2063.66","4.15.0-2064.67","4.15.0-2065.68","4.15.0-2066.69","4.15.0-2067.70","4.15.0-2069.72","4.15.0-2072.76","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2078.83","4.15.0-2079.84","4.15.0-2080.85","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2085.91","4.15.0-2087.93","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2103.109","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2107.113","4.15.0-2108.114","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-2093.99"}]}],"versions":["4.15.0-1002.2","4.15.0-2006.7","4.15.0-2007.8","4.15.0-2008.9","4.15.0-2009.10","4.15.0-2012.14","4.15.0-2013.15","4.15.0-2015.17","4.15.0-2016.18","4.15.0-2017.20","4.15.0-2018.21","4.15.0-2020.23","4.15.0-2021.24","4.15.0-2022.25","4.15.0-2023.26","4.15.0-2024.27","4.15.0-2025.28","4.15.0-2026.29","4.15.0-2027.30","4.15.0-2030.33","4.15.0-2033.37","4.15.0-2034.38","4.15.0-2035.39","4.15.0-2036.40","4.15.0-2037.41","4.15.0-2038.42","4.15.0-2039.43","4.15.0-2041.45","4.15.0-2042.46","4.15.0-2043.47","4.15.0-2045.49","4.15.0-2046.50","4.15.0-2047.51","4.15.0-2048.52","4.15.0-2049.53","4.15.0-2050.54","4.15.0-2053.58","4.15.0-2056.62","4.15.0-2057.63","4.15.0-2059.65","4.15.0-2060.66","4.15.0-2062.68","4.15.0-2066.72","4.15.0-2067.73","4.15.0-2068.74","4.15.0-2070.76","4.15.0-2071.77","4.15.0-2072.78","4.15.0-2073.79","4.15.0-2074.80","4.15.0-2075.81","4.15.0-2076.82","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1130.141"}]}],"versions":["4.15.0-1027.32","4.15.0-1029.34","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1037.42","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1040.45","4.15.0-1041.46","4.15.0-1044.50","4.15.0-1045.52","4.15.0-1046.53","4.15.0-1048.55","4.15.0-1049.56","4.15.0-1050.58","4.15.0-1051.59","4.15.0-1052.60","4.15.0-1053.61","4.15.0-1054.62","4.15.0-1055.63","4.15.0-1056.64","4.15.0-1057.65","4.15.0-1058.66","4.15.0-1059.67","4.15.0-1060.68","4.15.0-1063.71","4.15.0-1066.75","4.15.0-1067.76","4.15.0-1068.77","4.15.0-1069.78","4.15.0-1070.79","4.15.0-1071.80","4.15.0-1072.81","4.15.0-1073.82","4.15.0-1075.84","4.15.0-1076.85","4.15.0-1078.87","4.15.0-1080.89","4.15.0-1081.90","4.15.0-1083.92","4.15.0-1084.93","4.15.0-1085.94","4.15.0-1087.96","4.15.0-1090.100","4.15.0-1093.104","4.15.0-1094.105","4.15.0-1096.107","4.15.0-1097.108","4.15.0-1098.109","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1103.114","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1109.120","4.15.0-1110.121","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-2077.83"}]}],"versions":["4.15.0-2013.14","4.15.0-2016.18","4.15.0-2017.19","4.15.0-2018.20","4.15.0-2019.21","4.15.0-2020.22","4.15.0-2021.23","4.15.0-2022.24","4.15.0-2024.26","4.15.0-2025.27","4.15.0-2026.28","4.15.0-2028.31","4.15.0-2029.32","4.15.0-2030.33","4.15.0-2031.34","4.15.0-2032.35","4.15.0-2034.37","4.15.0-2037.41","4.15.0-2040.45","4.15.0-2041.46","4.15.0-2043.48","4.15.0-2044.49","4.15.0-2045.50","4.15.0-2047.52","4.15.0-2050.55","4.15.0-2052.57","4.15.0-2054.59","4.15.0-2055.60","4.15.0-2056.61","4.15.0-2057.62","4.15.0-2058.63","4.15.0-2059.64","4.15.0-2060.65","4.15.0-2061.66","4.15.0-2062.67","4.15.0-2063.68","4.15.0-2064.69","4.15.0-2065.70","4.15.0-2066.71","4.15.0-2067.72","4.15.0-2068.73","4.15.0-2069.74","4.15.0-2070.75","4.15.0-2071.76","4.15.0-2072.77","4.15.0-2073.78","4.15.0-2074.79","4.15.0-2075.80","4.15.0-2076.81"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1011.12"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-200.220"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197","5.4.0-181.201","5.4.0-182.202","5.4.0-186.206","5.4.0-187.207","5.4.0-189.209","5.4.0-190.210","5.4.0-192.212","5.4.0-193.213","5.4.0-195.215","5.4.0-196.216","5.4.0-198.218"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1135.145"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1129.139","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.78~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","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.147"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135","5.4.0-1129.136","5.4.0-1130.137","5.4.0-1131.138","5.4.0-1132.139","5.4.0-1133.140","5.4.0-1134.141","5.4.0-1135.142","5.4.0-1136.143","5.4.0-1137.144","5.4.0-1138.145","5.4.0-1139.146"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1078.87~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","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1095.102"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1139.148"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1128.137","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1071.79~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","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1102.106"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","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-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.62~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","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~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-125.135~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","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1082.87"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1077.82","5.4.0-1078.83","5.4.0-1079.84","5.4.0-1080.85","5.4.0-1081.86"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.68~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","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~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-1067.73~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","5.15.0-1060.66~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","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1044.45"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1042.43","5.4.0-1043.44"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1123.131"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","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-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1113.120","5.4.0-1114.121","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.127","5.4.0-1120.128","5.4.0-1121.129","5.4.0-1122.130"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135~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","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~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-1032.32~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","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1134.143"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1070.76~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","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1119.131"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119","5.4.0-1108.120","5.4.0-1109.121","5.4.0-1110.122","5.4.0-1111.123","5.4.0-1112.124","5.4.0-1113.125","5.4.0-1114.126","5.4.0-1115.127","5.4.0-1116.128","5.4.0-1117.129","5.4.0-1118.130"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.72~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","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1054.58"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.51","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1050.54","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57"]},{"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:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1135.145+fips1"}]}],"versions":["5.4.0-1021.21+fips2","5.4.0-1069.73+fips2","5.4.0-1071.76+fips1","5.4.0-1072.77+fips1","5.4.0-1073.78+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1083.90+fips1","5.4.0-1085.92+fips1","5.4.0-1086.93+fips1","5.4.0-1088.96+fips1","5.4.0-1089.97+fips1","5.4.0-1092.100+fips1","5.4.0-1093.101+fips1","5.4.0-1094.102+fips1","5.4.0-1096.104+fips1","5.4.0-1099.107+fips1","5.4.0-1100.108+fips1","5.4.0-1101.109+fips1","5.4.0-1102.110+fips1","5.4.0-1103.111+fips1","5.4.0-1104.112+fips1","5.4.0-1105.113+fips1","5.4.0-1106.114+fips1","5.4.0-1107.115+fips1","5.4.0-1108.116+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.123+fips1","5.4.0-1114.124+fips1","5.4.0-1116.126+fips1","5.4.0-1117.127+fips1","5.4.0-1118.128+fips1","5.4.0-1119.129+fips1","5.4.0-1120.130+fips1","5.4.0-1121.131+fips1","5.4.0-1122.132+fips1","5.4.0-1123.133+fips1","5.4.0-1124.134+fips1","5.4.0-1125.135+fips1","5.4.0-1126.136+fips2","5.4.0-1127.137+fips1","5.4.0-1128.138+fips1","5.4.0-1129.139+fips1","5.4.0-1130.140+fips1","5.4.0-1131.141+fips1","5.4.0-1132.142+fips1","5.4.0-1133.143+fips1","5.4.0-1134.144+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.147+fips1"}]}],"versions":["5.4.0-1022.22+fips1","5.4.0-1073.76+fips1","5.4.0-1074.77+fips1","5.4.0-1076.79+fips1","5.4.0-1078.81+fips1","5.4.0-1080.83+fips1","5.4.0-1083.87+fips1","5.4.0-1085.90+fips1","5.4.0-1086.91+fips1","5.4.0-1089.94+fips1","5.4.0-1090.95+fips1","5.4.0-1091.96+fips1","5.4.0-1094.100+fips1","5.4.0-1095.101+fips1","5.4.0-1098.104+fips1","5.4.0-1100.106+fips1","5.4.0-1101.107+fips1","5.4.0-1103.109+fips1","5.4.0-1104.110+fips1","5.4.0-1105.111+fips1","5.4.0-1106.112+fips1","5.4.0-1107.113+fips1","5.4.0-1108.114+fips1","5.4.0-1109.115+fips1","5.4.0-1110.116+fips1","5.4.0-1111.117+fips1","5.4.0-1112.118+fips1","5.4.0-1113.119+fips1","5.4.0-1114.120+fips1","5.4.0-1115.122+fips1","5.4.0-1116.123+fips1","5.4.0-1117.124+fips1","5.4.0-1118.125+fips1","5.4.0-1119.126+fips1","5.4.0-1121.128+fips1","5.4.0-1122.129+fips1","5.4.0-1123.130+fips1","5.4.0-1124.131+fips1","5.4.0-1126.133+fips1","5.4.0-1127.134+fips1","5.4.0-1128.135+fips1","5.4.0-1129.136+fips1","5.4.0-1130.137+fips1","5.4.0-1131.138+fips1","5.4.0-1132.139+fips1","5.4.0-1133.140+fips1","5.4.0-1134.141+fips1","5.4.0-1135.142+fips1","5.4.0-1136.143+fips1","5.4.0-1137.144+fips1","5.4.0-1138.145+fips1","5.4.0-1139.146+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1109.119"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32","5.4.0-1031.36","5.4.0-1032.37","5.4.0-1033.38","5.4.0-1034.40","5.4.0-1035.41","5.4.0-1036.42","5.4.0-1037.43","5.4.0-1038.44","5.4.0-1040.46","5.4.0-1041.47","5.4.0-1042.48","5.4.0-1043.49","5.4.0-1045.51","5.4.0-1046.52","5.4.0-1047.53","5.4.0-1048.54","5.4.0-1049.55","5.4.0-1051.57","5.4.0-1054.61","5.4.0-1056.64","5.4.0-1057.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1061.69","5.4.0-1062.70","5.4.0-1064.73","5.4.0-1065.74","5.4.0-1068.77","5.4.0-1069.78","5.4.0-1070.79","5.4.0-1072.81","5.4.0-1073.82","5.4.0-1074.83","5.4.0-1075.84","5.4.0-1076.85","5.4.0-1077.86","5.4.0-1078.87","5.4.0-1079.88","5.4.0-1080.89","5.4.0-1081.90","5.4.0-1082.91","5.4.0-1083.92","5.4.0-1084.93","5.4.0-1085.94","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1088.97","5.4.0-1089.98","5.4.0-1090.100","5.4.0-1091.101","5.4.0-1092.102","5.4.0-1094.104","5.4.0-1095.105","5.4.0-1096.106","5.4.0-1097.107","5.4.0-1098.108","5.4.0-1099.109","5.4.0-1100.110","5.4.0-1101.111","5.4.0-1102.112","5.4.0-1103.113","5.4.0-1104.114","5.4.0-1105.115","5.4.0-1106.116","5.4.0-1107.117","5.4.0-1108.118"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1139.148+fips1"}]}],"versions":["5.4.0-1021.21+fips1","5.4.0-1067.71~20.04.1","5.4.0-1069.73+fips2","5.4.0-1071.75+fips1","5.4.0-1073.78+fips1","5.4.0-1075.80+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1086.94+fips1","5.4.0-1087.95+fips1","5.4.0-1089.97+fips1","5.4.0-1092.101+fips1","5.4.0-1093.102+fips1","5.4.0-1096.105+fips1","5.4.0-1097.106+fips1","5.4.0-1098.107+fips1","5.4.0-1100.109+fips1","5.4.0-1101.110+fips1","5.4.0-1102.111+fips1","5.4.0-1103.112+fips1","5.4.0-1104.113+fips1","5.4.0-1105.114+fips1","5.4.0-1106.115+fips1","5.4.0-1107.116+fips1","5.4.0-1108.117+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.122+fips1","5.4.0-1115.124+fips1","5.4.0-1116.125+fips1","5.4.0-1117.126+fips1","5.4.0-1118.127+fips1","5.4.0-1120.129+fips1","5.4.0-1121.130+fips1","5.4.0-1122.131+fips1","5.4.0-1124.133+fips1","5.4.0-1125.134+fips1","5.4.0-1126.135+fips1","5.4.0-1127.136+fips1","5.4.0-1128.137+fips1","5.4.0-1129.138+fips1","5.4.0-1130.139+fips1","5.4.0-1131.140+fips1","5.4.0-1132.141+fips1","5.4.0-1133.142+fips1","5.4.0-1134.143+fips1","5.4.0-1135.144+fips1","5.4.0-1136.145+fips1","5.4.0-1137.146+fips1","5.4.0-1138.147+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135"}]}],"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","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134"]},{"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-1072.78"}]}],"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","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77"]},{"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-1020.22~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","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.84"}]}],"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","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83"]},{"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-1020.23~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","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1076.85.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","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.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-1071.79"}]}],"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","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78"]},{"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-1019.21~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75"}]}],"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","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.62"}]}],"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","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61"]},{"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-50.51~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.68"}]}],"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","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.17~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73"}]}],"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","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","5.15.0-1065.71","5.15.0-1066.72"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.74"}]}],"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","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135"}]}],"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","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134"]},{"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-50.51.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.68"}]}],"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","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67"]},{"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-1019.21~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","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1032.32"}]}],"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","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1020.20"}]}],"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","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19"]},{"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-1070.76"}]}],"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","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75"]},{"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-1017.18~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.68"}]}],"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","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67"]},{"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-50.51.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.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-1038.42"}]}],"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","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1056.58"}]}],"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","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1050.52","5.15.0-1051.53","5.15.0-1052.54","5.15.0-1053.55","5.15.0-1054.56"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.68"}]}],"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","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1073.81"}]}],"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","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1013.14~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1"]},{"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-1072.78+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","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+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-1075.84+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","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135+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","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+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-1071.79+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","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51"}]}],"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","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.22"}]}],"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","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.23"}]}],"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","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21"}]}],"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","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.19"}]}],"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","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1002.4"}]}],"versions":["6.8.0-1001.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.17"}]}],"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","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51.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","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.18"}]}],"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","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.18"}]}],"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","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.18"}]}],"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","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51.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","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.18"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2015.16"}]}],"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","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1013.14"}]}],"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","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12"]},{"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:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1139.148~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~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-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1128.137~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-200.220~18.04.1"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1","5.4.0-181.201~18.04.1","5.4.0-182.202~18.04.1","5.4.0-186.206~18.04.1","5.4.0-187.207~18.04.1","5.4.0-189.209~18.04.1","5.4.0-190.210~18.04.1","5.4.0-192.212~18.04.1","5.4.0-193.213~18.04.1","5.4.0-195.215~18.04.1","5.4.0-196.216~18.04.1","5.4.0-198.218~18.04.1"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1082.87~18.04.1"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1076.81~18.04.1","5.4.0-1077.82~18.04.1","5.4.0-1078.83~18.04.1","5.4.0-1079.84~18.04.1","5.4.0-1080.85~18.04.1","5.4.0-1081.86~18.04.1"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-200.220"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197","5.4.0-181.201","5.4.0-182.202","5.4.0-186.206","5.4.0-187.207","5.4.0-189.209","5.4.0-190.210","5.4.0-192.212","5.4.0-193.213","5.4.0-195.215","5.4.0-196.216","5.4.0-198.218"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1139.148"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1128.137","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1102.106"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","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-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1082.87"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1077.82","5.4.0-1078.83","5.4.0-1079.84","5.4.0-1080.85","5.4.0-1081.86"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.147"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135","5.4.0-1129.136","5.4.0-1130.137","5.4.0-1131.138","5.4.0-1132.139","5.4.0-1133.140","5.4.0-1134.141","5.4.0-1135.142","5.4.0-1136.143","5.4.0-1137.144","5.4.0-1138.145","5.4.0-1139.146"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1095.102"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1135.145~18.04.1"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~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-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1","5.4.0-1124.134~18.04.1","5.4.0-1125.135~18.04.1","5.4.0-1126.136~18.04.1","5.4.0-1127.137~18.04.2","5.4.0-1128.138~18.04.1","5.4.0-1129.139~18.04.1","5.4.0-1130.140~18.04.1","5.4.0-1131.141~18.04.1","5.4.0-1132.142~18.04.1","5.4.0-1133.143~18.04.1","5.4.0-1134.144~18.04.1"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1134.143~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1131.140~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.147~18.04.1"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~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-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.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-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1","5.4.0-1129.136~18.04.1","5.4.0-1130.137~18.04.1","5.4.0-1131.138~18.04.1","5.4.0-1132.139~18.04.1","5.4.0-1133.140~18.04.1","5.4.0-1134.141~18.04.1","5.4.0-1135.142~18.04.1","5.4.0-1136.143~18.04.1","5.4.0-1137.144~18.04.1","5.4.0-1138.145~18.04.1","5.4.0-1139.146~18.04.1"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1135.145"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1129.139","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1123.131"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","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-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1113.120","5.4.0-1114.121","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.127","5.4.0-1120.128","5.4.0-1121.129","5.4.0-1122.130"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1134.143"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1054.58"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.51","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1050.54","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1119.131~18.04.1"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1","5.4.0-1108.120~18.04.1","5.4.0-1109.121~18.04.1","5.4.0-1110.122~18.04.1","5.4.0-1111.123~18.04.1","5.4.0-1112.124~18.04.1","5.4.0-1114.126~18.04.1","5.4.0-1115.127~18.04.1","5.4.0-1116.128~18.04.1","5.4.0-1117.129~18.04.1","5.4.0-1118.130~18.04.1"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1119.131"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119","5.4.0-1108.120","5.4.0-1109.121","5.4.0-1110.122","5.4.0-1111.123","5.4.0-1112.124","5.4.0-1113.125","5.4.0-1114.126","5.4.0-1115.127","5.4.0-1116.128","5.4.0-1117.129","5.4.0-1118.130"],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.78~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","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1071.79~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","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.62~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","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135~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","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.68~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","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135~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","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1070.76~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","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135"}]}],"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","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1071.79"}]}],"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","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75"}]}],"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","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.62"}]}],"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","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.68"}]}],"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","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.74"}]}],"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","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-125.135"}]}],"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","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.68"}]}],"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","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1070.76"}]}],"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","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.68"}]}],"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","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1038.42"}]}],"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","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.78"}]}],"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","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77"],"bundled":223},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1044.45"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1042.43","5.4.0-1043.44"],"bundled":175},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.84"}]}],"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","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73~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","5.15.0-1060.66~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","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1"],"bundled":222},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73"}]}],"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","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","5.15.0-1065.71","5.15.0-1066.72"],"bundled":222},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.22~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","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.18~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51"}]}],"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","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.22"}]}],"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","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21"}]}],"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","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.19"}]}],"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","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.17"}]}],"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","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51.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","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.18"}]}],"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","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.18"}]}],"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","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.18"}]}],"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","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21~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","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1"],"bundled":401},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20"],"bundled":401},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1"],"bundled":401},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1002.4"}]}],"versions":["6.8.0-1001.3"],"bundled":607},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-262.296~14.04.1"}]}],"versions":["4.4.0-13.29~14.04.1","4.4.0-14.30~14.04.2","4.4.0-15.31~14.04.1","4.4.0-18.34~14.04.1","4.4.0-21.37~14.04.1","4.4.0-22.39~14.04.1","4.4.0-22.40~14.04.1","4.4.0-24.43~14.04.1","4.4.0-28.47~14.04.1","4.4.0-31.50~14.04.1","4.4.0-34.53~14.04.1","4.4.0-36.55~14.04.1","4.4.0-38.57~14.04.1","4.4.0-42.62~14.04.1","4.4.0-45.66~14.04.1","4.4.0-47.68~14.04.1","4.4.0-51.72~14.04.1","4.4.0-53.74~14.04.1","4.4.0-57.78~14.04.1","4.4.0-59.80~14.04.1","4.4.0-62.83~14.04.1","4.4.0-63.84~14.04.2","4.4.0-64.85~14.04.1","4.4.0-66.87~14.04.1","4.4.0-67.88~14.04.1","4.4.0-70.91~14.04.1","4.4.0-71.92~14.04.1","4.4.0-72.93~14.04.1","4.4.0-75.96~14.04.1","4.4.0-78.99~14.04.2","4.4.0-79.100~14.04.1","4.4.0-81.104~14.04.1","4.4.0-83.106~14.04.1","4.4.0-87.110~14.04.1","4.4.0-89.112~14.04.1","4.4.0-91.114~14.04.1","4.4.0-92.115~14.04.1","4.4.0-93.116~14.04.1","4.4.0-96.119~14.04.1","4.4.0-97.120~14.04.1","4.4.0-98.121~14.04.1","4.4.0-101.124~14.04.1","4.4.0-103.126~14.04.1","4.4.0-104.127~14.04.1","4.4.0-108.131~14.04.1","4.4.0-109.132~14.04.1","4.4.0-111.134~14.04.1","4.4.0-112.135~14.04.1","4.4.0-116.140~14.04.1","4.4.0-119.143~14.04.1","4.4.0-121.145~14.04.1","4.4.0-124.148~14.04.1","4.4.0-127.153~14.04.1","4.4.0-128.154~14.04.1","4.4.0-130.156~14.04.1","4.4.0-131.157~14.04.1","4.4.0-133.159~14.04.1","4.4.0-134.160~14.04.1","4.4.0-135.161~14.04.1","4.4.0-137.163~14.04.1","4.4.0-138.164~14.04.1","4.4.0-139.165~14.04.1","4.4.0-140.166~14.04.1","4.4.0-141.167~14.04.1","4.4.0-142.168~14.04.1","4.4.0-143.169~14.04.2","4.4.0-144.170~14.04.1","4.4.0-146.172~14.04.1","4.4.0-148.174~14.04.1","4.4.0-150.176~14.04.1","4.4.0-151.178~14.04.1","4.4.0-154.181~14.04.1","4.4.0-157.185~14.04.1","4.4.0-159.187~14.04.1","4.4.0-161.189~14.04.1","4.4.0-164.192~14.04.1","4.4.0-165.193~14.04.1","4.4.0-166.195~14.04.1","4.4.0-168.197~14.04.1","4.4.0-169.198~14.04.1","4.4.0-170.199~14.04.1","4.4.0-171.200~14.04.1","4.4.0-173.203~14.04.1","4.4.0-174.204~14.04.1","4.4.0-176.206~14.04.1","4.4.0-177.207~14.04.1","4.4.0-178.208~14.04.1","4.4.0-179.209~14.04.1","4.4.0-184.214~14.04.1","4.4.0-185.215~14.04.1","4.4.0-186.216~14.04.1","4.4.0-187.217~14.04.1","4.4.0-189.219~14.04.1","4.4.0-190.220~14.04.1","4.4.0-193.224~14.04.1","4.4.0-194.226~14.04.1","4.4.0-197.229~14.04.1","4.4.0-198.230~14.04.1","4.4.0-200.232~14.04.1","4.4.0-201.233~14.04.1","4.4.0-203.235~14.04.1","4.4.0-204.236~14.04.1","4.4.0-206.238~14.04.1","4.4.0-208.240~14.04.1","4.4.0-209.241~14.04.1","4.4.0-210.242~14.04.1","4.4.0-211.243~14.04.1","4.4.0-212.244~14.04.1","4.4.0-213.245~14.04.1","4.4.0-214.246~14.04.1","4.4.0-215.247~14.04.1","4.4.0-218.251~14.04.1","4.4.0-219.252~14.04.1","4.4.0-221.254~14.04.1","4.4.0-222.255~14.04.1","4.4.0-223.256~14.04.1","4.4.0-224.257~14.04.1","4.4.0-227.261~14.04.1","4.4.0-229.263~14.04.1","4.4.0-230.264~14.04.1","4.4.0-231.265~14.04.1","4.4.0-233.267~14.04.1","4.4.0-234.268~14.04.1","4.4.0-235.269~14.04.1","4.4.0-236.270~14.04.1","4.4.0-237.271~14.04.1","4.4.0-239.273~14.04.1","4.4.0-240.274~14.04.1","4.4.0-241.275~14.04.1","4.4.0-242.276~14.04.1","4.4.0-243.277~14.04.1","4.4.0-244.278~14.04.1","4.4.0-245.279~14.04.1","4.4.0-246.280~14.04.1","4.4.0-248.282~14.04.1","4.4.0-250.284~14.04.1","4.4.0-251.285~14.04.1","4.4.0-252.286~14.04.1","4.4.0-253.287~14.04.1","4.4.0-254.288~14.04.1","4.4.0-256.290~14.04.1","4.4.0-257.291~14.04.1","4.4.0-258.292~14.04.2","4.4.0-259.293~14.04.1","4.4.0-260.294~14.04.1","4.4.0-261.295~14.04.1"],"bundled":33},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-262.296"}]}],"versions":["4.2.0-16.19","4.2.0-17.21","4.2.0-19.23","4.3.0-1.10","4.3.0-2.11","4.3.0-5.16","4.3.0-6.17","4.3.0-7.18","4.4.0-2.16","4.4.0-4.19","4.4.0-6.21","4.4.0-7.22","4.4.0-8.23","4.4.0-9.24","4.4.0-10.25","4.4.0-11.26","4.4.0-12.28","4.4.0-13.29","4.4.0-14.30","4.4.0-15.31","4.4.0-16.32","4.4.0-17.33","4.4.0-18.34","4.4.0-21.37","4.4.0-22.39","4.4.0-22.40","4.4.0-24.43","4.4.0-28.47","4.4.0-31.50","4.4.0-34.53","4.4.0-36.55","4.4.0-38.57","4.4.0-42.62","4.4.0-43.63","4.4.0-45.66","4.4.0-47.68","4.4.0-51.72","4.4.0-53.74","4.4.0-57.78","4.4.0-59.80","4.4.0-62.83","4.4.0-63.84","4.4.0-64.85","4.4.0-65.86","4.4.0-66.87","4.4.0-67.88","4.4.0-70.91","4.4.0-71.92","4.4.0-72.93","4.4.0-75.96","4.4.0-77.98","4.4.0-78.99","4.4.0-79.100","4.4.0-81.104","4.4.0-83.106","4.4.0-87.110","4.4.0-89.112","4.4.0-91.114","4.4.0-92.115","4.4.0-93.116","4.4.0-96.119","4.4.0-97.120","4.4.0-98.121","4.4.0-101.124","4.4.0-103.126","4.4.0-104.127","4.4.0-108.131","4.4.0-109.132","4.4.0-112.135","4.4.0-116.140","4.4.0-119.143","4.4.0-121.145","4.4.0-122.146","4.4.0-124.148","4.4.0-127.153","4.4.0-128.154","4.4.0-130.156","4.4.0-131.157","4.4.0-133.159","4.4.0-134.160","4.4.0-135.161","4.4.0-137.163","4.4.0-138.164","4.4.0-139.165","4.4.0-140.166","4.4.0-141.167","4.4.0-142.168","4.4.0-143.169","4.4.0-145.171","4.4.0-146.172","4.4.0-148.174","4.4.0-150.176","4.4.0-151.178","4.4.0-154.181","4.4.0-157.185","4.4.0-159.187","4.4.0-161.189","4.4.0-164.192","4.4.0-165.193","4.4.0-166.195","4.4.0-168.197","4.4.0-169.198","4.4.0-170.199","4.4.0-171.200","4.4.0-173.203","4.4.0-174.204","4.4.0-176.206","4.4.0-177.207","4.4.0-178.208","4.4.0-179.209","4.4.0-184.214","4.4.0-185.215","4.4.0-186.216","4.4.0-187.217","4.4.0-189.219","4.4.0-190.220","4.4.0-193.224","4.4.0-194.226","4.4.0-197.229","4.4.0-198.230","4.4.0-200.232","4.4.0-201.233","4.4.0-203.235","4.4.0-204.236","4.4.0-206.238","4.4.0-208.240","4.4.0-209.241","4.4.0-210.242","4.4.0-211.243","4.4.0-212.244","4.4.0-213.245","4.4.0-214.246","4.4.0-216.249","4.4.0-217.250","4.4.0-218.251","4.4.0-219.252","4.4.0-221.254","4.4.0-222.255","4.4.0-223.256","4.4.0-224.257","4.4.0-227.261","4.4.0-229.263","4.4.0-230.264","4.4.0-231.265","4.4.0-233.267","4.4.0-234.268","4.4.0-235.269","4.4.0-236.270","4.4.0-237.271","4.4.0-239.273","4.4.0-240.274","4.4.0-241.275","4.4.0-242.276","4.4.0-243.277","4.4.0-244.278","4.4.0-245.279","4.4.0-246.280","4.4.0-248.282","4.4.0-250.284","4.4.0-251.285","4.4.0-252.286","4.4.0-253.287","4.4.0-254.288","4.4.0-256.290","4.4.0-257.291","4.4.0-258.292","4.4.0-259.293","4.4.0-260.294","4.4.0-261.295"],"bundled":33},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1139.145"}]}],"versions":["4.4.0-1002.2","4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1011.11","4.4.0-1012.12","4.4.0-1014.14","4.4.0-1016.16","4.4.0-1017.17","4.4.0-1019.19","4.4.0-1022.22","4.4.0-1023.23","4.4.0-1024.25","4.4.0-1025.26","4.4.0-1027.30","4.4.0-1028.31","4.4.0-1029.32","4.4.0-1031.34","4.4.0-1032.35","4.4.0-1034.37","4.4.0-1036.39","4.4.0-1037.40","4.4.0-1038.41","4.4.0-1039.42","4.4.0-1040.43","4.4.0-1042.45","4.4.0-1044.47","4.4.0-1045.48","4.4.0-1046.50","4.4.0-1048.52","4.4.0-1050.54","4.4.0-1052.56","4.4.0-1054.58","4.4.0-1055.59","4.4.0-1056.60","4.4.0-1058.62","4.4.0-1059.63","4.4.0-1060.64","4.4.0-1061.65","4.4.0-1062.66","4.4.0-1064.68","4.4.0-1065.69","4.4.0-1066.70","4.4.0-1067.71","4.4.0-1073.77","4.4.0-1074.78","4.4.0-1075.79","4.4.0-1076.80","4.4.0-1077.81","4.4.0-1078.82","4.4.0-1081.85","4.4.0-1082.86","4.4.0-1083.87","4.4.0-1085.89","4.4.0-1086.90","4.4.0-1087.91","4.4.0-1088.92","4.4.0-1090.94","4.4.0-1091.95","4.4.0-1092.96","4.4.0-1093.97","4.4.0-1094.99","4.4.0-1095.100","4.4.0-1096.101","4.4.0-1097.102","4.4.0-1098.103","4.4.0-1099.104","4.4.0-1101.106","4.4.0-1102.107","4.4.0-1103.108","4.4.0-1104.109","4.4.0-1107.113","4.4.0-1109.115","4.4.0-1110.116","4.4.0-1111.117","4.4.0-1112.118","4.4.0-1113.119","4.4.0-1114.120","4.4.0-1115.121","4.4.0-1116.122","4.4.0-1117.123","4.4.0-1118.124","4.4.0-1119.125","4.4.0-1120.126","4.4.0-1121.127","4.4.0-1122.128","4.4.0-1123.129","4.4.0-1124.130","4.4.0-1125.131","4.4.0-1127.133","4.4.0-1128.134","4.4.0-1129.135","4.4.0-1130.136","4.4.0-1131.137","4.4.0-1133.139","4.4.0-1134.140","4.4.0-1135.141","4.4.0-1136.142","4.4.0-1137.143","4.4.0-1138.144"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1177.192"}]}],"versions":["4.4.0-1001.10","4.4.0-1003.12","4.4.0-1004.13","4.4.0-1007.16","4.4.0-1009.18","4.4.0-1011.20","4.4.0-1012.21","4.4.0-1013.22","4.4.0-1016.25","4.4.0-1017.26","4.4.0-1018.27","4.4.0-1020.29","4.4.0-1022.31","4.4.0-1026.35","4.4.0-1028.37","4.4.0-1030.39","4.4.0-1031.40","4.4.0-1032.41","4.4.0-1035.44","4.4.0-1037.46","4.4.0-1038.47","4.4.0-1039.48","4.4.0-1041.50","4.4.0-1043.52","4.4.0-1044.53","4.4.0-1047.56","4.4.0-1048.57","4.4.0-1049.58","4.4.0-1050.59","4.4.0-1052.61","4.4.0-1054.63","4.4.0-1055.64","4.4.0-1057.66","4.4.0-1060.69","4.4.0-1061.70","4.4.0-1062.71","4.4.0-1063.72","4.4.0-1065.75","4.4.0-1066.76","4.4.0-1067.77","4.4.0-1069.79","4.4.0-1070.80","4.4.0-1072.82","4.4.0-1073.83","4.4.0-1074.84","4.4.0-1075.85","4.4.0-1077.87","4.4.0-1079.89","4.4.0-1081.91","4.4.0-1083.93","4.4.0-1084.94","4.4.0-1085.96","4.4.0-1087.98","4.4.0-1088.99","4.4.0-1090.101","4.4.0-1092.103","4.4.0-1094.105","4.4.0-1095.106","4.4.0-1096.107","4.4.0-1098.109","4.4.0-1099.110","4.4.0-1100.111","4.4.0-1101.112","4.4.0-1102.113","4.4.0-1104.115","4.4.0-1105.116","4.4.0-1106.117","4.4.0-1107.118","4.4.0-1109.120","4.4.0-1110.121","4.4.0-1111.123","4.4.0-1112.124","4.4.0-1113.126","4.4.0-1114.127","4.4.0-1117.131","4.4.0-1118.132","4.4.0-1119.133","4.4.0-1121.135","4.4.0-1122.136","4.4.0-1123.137","4.4.0-1124.138","4.4.0-1126.140","4.4.0-1127.141","4.4.0-1128.142","4.4.0-1129.143","4.4.0-1130.144","4.4.0-1131.145","4.4.0-1132.146","4.4.0-1133.147","4.4.0-1134.148","4.4.0-1135.149","4.4.0-1137.151","4.4.0-1138.152","4.4.0-1139.153","4.4.0-1140.154","4.4.0-1143.158","4.4.0-1145.160","4.4.0-1146.161","4.4.0-1147.162","4.4.0-1148.163","4.4.0-1150.165","4.4.0-1151.166","4.4.0-1152.167","4.4.0-1153.168","4.4.0-1154.169","4.4.0-1155.170","4.4.0-1156.171","4.4.0-1157.172","4.4.0-1158.173","4.4.0-1159.174","4.4.0-1160.175","4.4.0-1161.176","4.4.0-1162.177","4.4.0-1163.178","4.4.0-1164.179","4.4.0-1165.180","4.4.0-1166.181","4.4.0-1167.182","4.4.0-1168.183","4.4.0-1169.184","4.4.0-1171.186","4.4.0-1172.187","4.4.0-1173.188","4.4.0-1174.189","4.4.0-1175.190","4.4.0-1176.191"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1140.151"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13","4.4.0-1009.14","4.4.0-1010.15","4.4.0-1012.17","4.4.0-1013.18","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1020.25","4.4.0-1021.26","4.4.0-1023.28","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1029.34","4.4.0-1031.37","4.4.0-1032.38","4.4.0-1033.39","4.4.0-1035.41","4.4.0-1036.42","4.4.0-1037.43","4.4.0-1038.44","4.4.0-1039.45","4.4.0-1040.46","4.4.0-1041.47","4.4.0-1043.49","4.4.0-1044.50","4.4.0-1046.52","4.4.0-1047.53","4.4.0-1048.55","4.4.0-1051.58","4.4.0-1052.59","4.4.0-1054.61","4.4.0-1056.63","4.4.0-1058.65","4.4.0-1059.66","4.4.0-1060.67","4.4.0-1062.69","4.4.0-1063.70","4.4.0-1064.71","4.4.0-1065.72","4.4.0-1066.73","4.4.0-1068.75","4.4.0-1069.76","4.4.0-1070.77","4.4.0-1071.78","4.4.0-1075.82","4.4.0-1076.83","4.4.0-1077.84","4.4.0-1078.85","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1082.91","4.4.0-1084.93","4.4.0-1085.94","4.4.0-1087.96","4.4.0-1088.97","4.4.0-1089.98","4.4.0-1090.99","4.4.0-1091.100","4.4.0-1092.101","4.4.0-1093.102","4.4.0-1094.103","4.4.0-1095.104","4.4.0-1096.105","4.4.0-1097.106","4.4.0-1098.107","4.4.0-1099.108","4.4.0-1100.109","4.4.0-1102.111","4.4.0-1103.112","4.4.0-1104.113","4.4.0-1105.114","4.4.0-1108.118","4.4.0-1110.120","4.4.0-1111.121","4.4.0-1112.122","4.4.0-1113.123","4.4.0-1114.124","4.4.0-1115.125","4.4.0-1116.126","4.4.0-1117.127","4.4.0-1118.128","4.4.0-1119.129","4.4.0-1120.130","4.4.0-1121.131","4.4.0-1122.132","4.4.0-1123.133","4.4.0-1124.134","4.4.0-1125.135","4.4.0-1126.136","4.4.0-1128.138","4.4.0-1129.139","4.4.0-1130.140","4.4.0-1131.141","4.4.0-1132.142","4.4.0-1134.144","4.4.0-1135.145","4.4.0-1136.146","4.4.0-1137.147","4.4.0-1138.148","4.4.0-1139.149"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1176.189~16.04.1"}]}],"versions":["4.15.0-1030.31~16.04.1","4.15.0-1031.33~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1035.37~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1039.41~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43~16.04.1","4.15.0-1043.45~16.04.1","4.15.0-1044.46~16.04.1","4.15.0-1045.47~16.04.1","4.15.0-1047.49~16.04.1","4.15.0-1048.50~16.04.1","4.15.0-1050.52~16.04.1","4.15.0-1051.53~16.04.1","4.15.0-1052.54~16.04.1","4.15.0-1054.56~16.04.1","4.15.0-1056.58~16.04.1","4.15.0-1057.59~16.04.1","4.15.0-1058.60~16.04.1","4.15.0-1060.62~16.04.1","4.15.0-1063.67~16.04.1","4.15.0-1065.69~16.04.1","4.15.0-1066.70~16.04.1","4.15.0-1067.71~16.04.1","4.15.0-1073.77~16.04.1","4.15.0-1074.78~16.04.1","4.15.0-1079.83~16.04.1","4.15.0-1080.84~16.04.1","4.15.0-1082.86~16.04.1","4.15.0-1083.87~16.04.1","4.15.0-1085.90~16.04.1","4.15.0-1088.93~16.04.1","4.15.0-1090.95~16.04.1","4.15.0-1091.96~16.04.1","4.15.0-1093.99~16.04.1","4.15.0-1094.101~16.04.1","4.15.0-1095.102~16.04.1","4.15.0-1096.103~16.04.1","4.15.0-1097.104~16.04.1","4.15.0-1098.105~16.04.1","4.15.0-1099.106~16.04.1","4.15.0-1102.109~16.04.1","4.15.0-1103.110~16.04.1","4.15.0-1106.113~16.04.1","4.15.0-1109.116~16.04.1","4.15.0-1110.117~16.04.1","4.15.0-1111.118~16.04.1","4.15.0-1112.119~16.04.1","4.15.0-1113.120~16.04.1","4.15.0-1115.122~16.04.1","4.15.0-1116.123~16.04.1","4.15.0-1118.125~16.04.1","4.15.0-1119.126~16.04.2","4.15.0-1120.128~16.04.1","4.15.0-1123.132~16.04.1","4.15.0-1124.133~16.04.1","4.15.0-1126.135~16.04.2","4.15.0-1127.136~16.04.1","4.15.0-1128.137~16.04.1","4.15.0-1130.139~16.04.1","4.15.0-1133.143~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.154~16.04.1","4.15.0-1143.155~16.04.1","4.15.0-1146.158~16.04.2","4.15.0-1147.159~16.04.1","4.15.0-1148.160~16.04.1","4.15.0-1151.164~16.04.1","4.15.0-1153.166~16.04.1","4.15.0-1154.167~16.04.1","4.15.0-1155.168~16.04.1","4.15.0-1156.169~16.04.1","4.15.0-1157.170~16.04.1","4.15.0-1158.171~16.04.1","4.15.0-1159.172~16.04.1","4.15.0-1160.173~16.04.1","4.15.0-1161.174~16.04.1","4.15.0-1162.175~16.04.1","4.15.0-1163.176~16.04.1","4.15.0-1164.177~16.04.1","4.15.0-1165.178~16.04.1","4.15.0-1166.179~16.04.1","4.15.0-1167.180~16.04.1","4.15.0-1168.181~16.04.1","4.15.0-1169.182~16.04.1","4.15.0-1170.183~16.04.1","4.15.0-1172.185~16.04.1","4.15.0-1173.186~16.04.1","4.15.0-1174.187~16.04.1","4.15.0-1175.188~16.04.1"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1169.186~16.04.1"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1","4.15.0-1018.19~16.04.2","4.15.0-1019.20~16.04.1","4.15.0-1021.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1024.25~16.04.2","4.15.0-1025.26~16.04.1","4.15.0-1026.27~16.04.1","4.15.0-1027.28~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1029.31~16.04.1","4.15.0-1030.32~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1034.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1046.49","4.15.0-1047.50","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.56","4.15.0-1055.59","4.15.0-1058.62","4.15.0-1060.64","4.15.0-1061.65","4.15.0-1071.81~16.04.1","4.15.0-1077.87~16.04.1","4.15.0-1078.88~16.04.1","4.15.0-1080.90~16.04.1","4.15.0-1081.92~16.04.1","4.15.0-1083.94~16.04.1","4.15.0-1084.95~16.04.1","4.15.0-1086.98~16.04.1","4.15.0-1087.100~16.04.1","4.15.0-1088.101~16.04.1","4.15.0-1090.103~16.04.1","4.15.0-1091.104~16.04.1","4.15.0-1092.105~16.04.1","4.15.0-1093.106~16.04.1","4.15.0-1094.107~16.04.1","4.15.0-1095.108~16.04.1","4.15.0-1096.109~16.04.1","4.15.0-1097.110~16.04.1","4.15.0-1098.111~16.04.1","4.15.0-1099.112~16.04.1","4.15.0-1100.113~16.04.1","4.15.0-1103.116~16.04.1","4.15.0-1106.120~16.04.1","4.15.0-1107.121~16.04.1","4.15.0-1108.122~16.04.1","4.15.0-1109.123~16.04.1","4.15.0-1110.124~16.04.1","4.15.0-1111.125~16.04.1","4.15.0-1112.126~16.04.1","4.15.0-1114.128~16.04.1","4.15.0-1115.129~16.04.1","4.15.0-1116.130~16.04.1","4.15.0-1118.132~16.04.1","4.15.0-1119.133~16.04.1","4.15.0-1120.134~16.04.1","4.15.0-1121.135~16.04.1","4.15.0-1122.136~16.04.1","4.15.0-1124.138~16.04.1","4.15.0-1127.142~16.04.1","4.15.0-1130.146~16.04.1","4.15.0-1131.147~16.04.1","4.15.0-1134.150~16.04.2","4.15.0-1135.151~16.04.2","4.15.0-1136.152~16.04.1","4.15.0-1137.153~16.04.1","4.15.0-1138.154~16.04.1","4.15.0-1141.157~16.04.2","4.15.0-1142.158~16.04.1","4.15.0-1143.159~16.04.1","4.15.0-1146.162~16.04.1","4.15.0-1147.163~16.04.1","4.15.0-1148.164~16.04.1","4.15.0-1149.165~16.04.1","4.15.0-1150.166~16.04.1","4.15.0-1151.167~16.04.1","4.15.0-1152.168~16.04.1","4.15.0-1153.170~16.04.1","4.15.0-1154.171~16.04.1","4.15.0-1155.172~16.04.1","4.15.0-1156.173~16.04.1","4.15.0-1157.174~16.04.1","4.15.0-1158.175~16.04.1","4.15.0-1159.176~16.04.1","4.15.0-1160.177~16.04.1","4.15.0-1161.178~16.04.1","4.15.0-1162.179~16.04.1","4.15.0-1163.180~16.04.1","4.15.0-1164.181~16.04.1","4.15.0-1165.182~16.04.1","4.15.0-1166.183~16.04.1","4.15.0-1167.184~16.04.2","4.15.0-1168.185~16.04.1"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-232.244~16.04.1"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1","4.15.0-33.36~16.04.1","4.15.0-34.37~16.04.1","4.15.0-36.39~16.04.1","4.15.0-38.41~16.04.1","4.15.0-39.42~16.04.1","4.15.0-42.45~16.04.1","4.15.0-43.46~16.04.1","4.15.0-45.48~16.04.1","4.15.0-46.49~16.04.1","4.15.0-47.50~16.04.1","4.15.0-48.51~16.04.1","4.15.0-50.54~16.04.1","4.15.0-51.55~16.04.1","4.15.0-52.56~16.04.1","4.15.0-54.58~16.04.1","4.15.0-55.60~16.04.2","4.15.0-58.64~16.04.1","4.15.0-60.67~16.04.1","4.15.0-62.69~16.04.1","4.15.0-64.73~16.04.1","4.15.0-65.74~16.04.1","4.15.0-66.75~16.04.1","4.15.0-69.78~16.04.1","4.15.0-70.79~16.04.1","4.15.0-72.81~16.04.1","4.15.0-74.83~16.04.1","4.15.0-76.86~16.04.1","4.15.0-88.88~16.04.1","4.15.0-91.92~16.04.1","4.15.0-96.97~16.04.1","4.15.0-99.100~16.04.1","4.15.0-101.102~16.04.1","4.15.0-106.107~16.04.1","4.15.0-107.108~16.04.1","4.15.0-112.113~16.04.1","4.15.0-115.116~16.04.1","4.15.0-117.118~16.04.1","4.15.0-118.119~16.04.1","4.15.0-120.122~16.04.1","4.15.0-122.124~16.04.1","4.15.0-123.126~16.04.1","4.15.0-126.129~16.04.1","4.15.0-128.131~16.04.1","4.15.0-129.132~16.04.1","4.15.0-132.136~16.04.1","4.15.0-133.137~16.04.1","4.15.0-136.140~16.04.1","4.15.0-137.141~16.04.1","4.15.0-139.143~16.04.1","4.15.0-140.144~16.04.1","4.15.0-142.146~16.04.1","4.15.0-143.147~16.04.3","4.15.0-144.148~16.04.1","4.15.0-147.151~16.04.1","4.15.0-151.157~16.04.1","4.15.0-153.160~16.04.1","4.15.0-154.161~16.04.1","4.15.0-156.163~16.04.1","4.15.0-158.166~16.04.1","4.15.0-159.167~16.04.1","4.15.0-161.169~16.04.1","4.15.0-162.170~16.04.1","4.15.0-163.171~16.04.1","4.15.0-166.174~16.04.1","4.15.0-167.175~16.04.1","4.15.0-169.177~16.04.1","4.15.0-171.180~16.04.1","4.15.0-173.182~16.04.1","4.15.0-175.184~16.04.1","4.15.0-176.185~16.04.1","4.15.0-177.186~16.04.1","4.15.0-180.189~16.04.1","4.15.0-184.194~16.04.1","4.15.0-187.198~16.04.1","4.15.0-188.199~16.04.1","4.15.0-189.200~16.04.1","4.15.0-191.202~16.04.1","4.15.0-192.203~16.04.1","4.15.0-193.204~16.04.1","4.15.0-194.205~16.04.1","4.15.0-196.207~16.04.1","4.15.0-197.208~16.04.1","4.15.0-200.211~16.04.2","4.15.0-201.212~16.04.1","4.15.0-202.213~16.04.1","4.15.0-206.217~16.04.1","4.15.0-208.219~16.04.1","4.15.0-209.220~16.04.1","4.15.0-210.221~16.04.1","4.15.0-211.222~16.04.1","4.15.0-212.223~16.04.1","4.15.0-213.224~16.04.1","4.15.0-214.225~16.04.1","4.15.0-216.227~16.04.1","4.15.0-218.229~16.04.1","4.15.0-219.230~16.04.1","4.15.0-220.231~16.04.1","4.15.0-221.232~16.04.1","4.15.0-222.233~16.04.1","4.15.0-223.235~16.04.1","4.15.0-224.236~16.04.1","4.15.0-225.237~16.04.1","4.15.0-226.238~16.04.1","4.15.0-227.239~16.04.1","4.15.0-228.240~16.04.1","4.15.0-229.241~16.04.1","4.15.0-230.242~16.04.1","4.15.0-231.243~16.04.1"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1138.149~16.04.1"}]}],"versions":["4.15.0-1007.9~16.04.1","4.15.0-1008.10~16.04.1","4.15.0-1009.11~16.04.1","4.15.0-1010.12~16.04.1","4.15.0-1011.13~16.04.1","4.15.0-1013.15~16.04.1","4.15.0-1014.16~16.04.1","4.15.0-1015.17~16.04.1","4.15.0-1017.19~16.04.2","4.15.0-1018.20~16.04.1","4.15.0-1021.23~16.04.1","4.15.0-1022.25~16.04.1","4.15.0-1023.26~16.04.1","4.15.0-1025.28~16.04.1","4.15.0-1026.29~16.04.1","4.15.0-1027.30~16.04.1","4.15.0-1029.32~16.04.1","4.15.0-1030.33~16.04.1","4.15.0-1031.34~16.04.1","4.15.0-1033.36~16.04.1","4.15.0-1035.38~16.04.1","4.15.0-1037.41~16.04.1","4.15.0-1038.42~16.04.1","4.15.0-1039.43~16.04.1","4.15.0-1045.49~16.04.1","4.15.0-1046.50~16.04.1","4.15.0-1050.54~16.04.1","4.15.0-1051.55~16.04.1","4.15.0-1053.57~16.04.1","4.15.0-1054.58~16.04.1","4.15.0-1056.61~16.04.1","4.15.0-1058.64~16.04.1","4.15.0-1059.65~16.04.1","4.15.0-1061.67~16.04.1","4.15.0-1062.68~16.04.1","4.15.0-1064.71~16.04.1","4.15.0-1065.73~16.04.1","4.15.0-1066.74~16.04.1","4.15.0-1067.75~16.04.1","4.15.0-1068.76~16.04.1","4.15.0-1069.77~16.04.1","4.15.0-1070.78~16.04.1","4.15.0-1071.79~16.04.1","4.15.0-1072.80~16.04.1","4.15.0-1075.83~16.04.1","4.15.0-1078.86~16.04.1","4.15.0-1079.87~16.04.1","4.15.0-1080.88~16.04.1","4.15.0-1081.89~16.04.1","4.15.0-1082.90~16.04.1","4.15.0-1083.91~16.04.1","4.15.0-1084.92~16.04.1","4.15.0-1085.93~16.04.1","4.15.0-1086.94~16.04.1","4.15.0-1087.95~16.04.1","4.15.0-1089.98~16.04.1","4.15.0-1090.99~16.04.1","4.15.0-1091.100~16.04.1","4.15.0-1092.101~16.04.1","4.15.0-1093.102~16.04.1","4.15.0-1095.104~16.04.1","4.15.0-1098.108~16.04.1","4.15.0-1101.112~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1104.115~16.04.1","4.15.0-1105.116~16.04.1","4.15.0-1106.117~16.04.1","4.15.0-1107.118~16.04.1","4.15.0-1108.119~16.04.1","4.15.0-1111.122~16.04.2","4.15.0-1112.123~16.04.1","4.15.0-1113.124~16.04.1","4.15.0-1115.126~16.04.1","4.15.0-1116.127~16.04.1","4.15.0-1117.128~16.04.1","4.15.0-1118.129~16.04.1","4.15.0-1119.130~16.04.1","4.15.0-1120.131~16.04.1","4.15.0-1121.132~16.04.1","4.15.0-1122.133~16.04.1","4.15.0-1123.134~16.04.1","4.15.0-1124.135~16.04.1","4.15.0-1125.136~16.04.1","4.15.0-1126.137~16.04.1","4.15.0-1127.138~16.04.1","4.15.0-1128.139~16.04.1","4.15.0-1129.140~16.04.1","4.15.0-1130.141~16.04.1","4.15.0-1131.142~16.04.1","4.15.0-1132.143~16.04.1","4.15.0-1133.144~16.04.1","4.15.0-1134.145~16.04.1","4.15.0-1135.146~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-232.244"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35","4.15.0-33.36","4.15.0-34.37","4.15.0-36.39","4.15.0-38.41","4.15.0-39.42","4.15.0-42.45","4.15.0-43.46","4.15.0-44.47","4.15.0-45.48","4.15.0-46.49","4.15.0-47.50","4.15.0-48.51","4.15.0-50.54","4.15.0-51.55","4.15.0-52.56","4.15.0-54.58","4.15.0-55.60","4.15.0-58.64","4.15.0-60.67","4.15.0-62.69","4.15.0-64.73","4.15.0-65.74","4.15.0-66.75","4.15.0-69.78","4.15.0-70.79","4.15.0-72.81","4.15.0-74.84","4.15.0-76.86","4.15.0-88.88","4.15.0-91.92","4.15.0-96.97","4.15.0-99.100","4.15.0-101.102","4.15.0-106.107","4.15.0-108.109","4.15.0-109.110","4.15.0-111.112","4.15.0-112.113","4.15.0-115.116","4.15.0-117.118","4.15.0-118.119","4.15.0-121.123","4.15.0-122.124","4.15.0-123.126","4.15.0-124.127","4.15.0-126.129","4.15.0-128.131","4.15.0-129.132","4.15.0-130.134","4.15.0-132.136","4.15.0-134.138","4.15.0-135.139","4.15.0-136.140","4.15.0-137.141","4.15.0-139.143","4.15.0-140.144","4.15.0-141.145","4.15.0-142.146","4.15.0-143.147","4.15.0-144.148","4.15.0-147.151","4.15.0-151.157","4.15.0-153.160","4.15.0-154.161","4.15.0-156.163","4.15.0-158.166","4.15.0-159.167","4.15.0-161.169","4.15.0-162.170","4.15.0-163.171","4.15.0-166.174","4.15.0-167.175","4.15.0-169.177","4.15.0-171.180","4.15.0-173.182","4.15.0-175.184","4.15.0-176.185","4.15.0-177.186","4.15.0-180.189","4.15.0-184.194","4.15.0-187.198","4.15.0-188.199","4.15.0-189.200","4.15.0-191.202","4.15.0-192.203","4.15.0-193.204","4.15.0-194.205","4.15.0-196.207","4.15.0-197.208","4.15.0-200.211","4.15.0-201.212","4.15.0-202.213","4.15.0-204.215","4.15.0-206.217","4.15.0-208.220","4.15.0-209.220","4.15.0-210.221","4.15.0-211.222","4.15.0-212.223","4.15.0-213.224","4.15.0-214.225","4.15.0-216.227","4.15.0-218.229","4.15.0-219.230","4.15.0-220.231","4.15.0-221.232","4.15.0-222.233","4.15.0-223.235","4.15.0-224.236","4.15.0-225.237","4.15.0-226.238","4.15.0-227.239","4.15.0-228.240","4.15.0-229.241","4.15.0-230.242","4.15.0-231.243"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1176.189"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1027.27","4.15.0-1029.30","4.15.0-1031.33","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1035.37","4.15.0-1037.39","4.15.0-1039.41","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1043.45","4.15.0-1044.46","4.15.0-1045.47","4.15.0-1047.49","4.15.0-1048.50","4.15.0-1050.52","4.15.0-1051.53","4.15.0-1052.54","4.15.0-1054.56","4.15.0-1056.58","4.15.0-1057.59","4.15.0-1058.60","4.15.0-1060.62","4.15.0-1063.67","4.15.0-1065.69","4.15.0-1066.70","4.15.0-1067.71","4.15.0-1073.77","4.15.0-1076.80","4.15.0-1077.81","4.15.0-1079.83","4.15.0-1080.84","4.15.0-1082.86","4.15.0-1083.87","4.15.0-1086.91","4.15.0-1087.92","4.15.0-1088.93","4.15.0-1090.95","4.15.0-1091.96","4.15.0-1092.98","4.15.0-1093.99","4.15.0-1094.101","4.15.0-1095.102","4.15.0-1096.103","4.15.0-1097.104","4.15.0-1098.105","4.15.0-1099.106","4.15.0-1101.108","4.15.0-1102.109","4.15.0-1103.110","4.15.0-1106.113","4.15.0-1109.116","4.15.0-1110.117","4.15.0-1111.118","4.15.0-1112.119","4.15.0-1114.121","4.15.0-1115.122","4.15.0-1116.123","4.15.0-1118.125","4.15.0-1119.127","4.15.0-1121.129","4.15.0-1123.132","4.15.0-1124.133","4.15.0-1126.135","4.15.0-1127.136","4.15.0-1128.137","4.15.0-1130.139","4.15.0-1133.143","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1150.163","4.15.0-1151.164","4.15.0-1153.166","4.15.0-1154.167","4.15.0-1155.168","4.15.0-1156.169","4.15.0-1157.170","4.15.0-1158.171","4.15.0-1159.172","4.15.0-1160.173","4.15.0-1161.174","4.15.0-1162.175","4.15.0-1163.176","4.15.0-1164.177","4.15.0-1165.178","4.15.0-1166.179","4.15.0-1167.180","4.15.0-1168.181","4.15.0-1169.182","4.15.0-1170.183","4.15.0-1172.185","4.15.0-1173.186","4.15.0-1174.187","4.15.0-1175.188"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1169.186"}]}],"versions":["4.15.0-1071.81","4.15.0-1077.87","4.15.0-1078.88","4.15.0-1080.90","4.15.0-1081.92","4.15.0-1083.94","4.15.0-1084.95","4.15.0-1086.98","4.15.0-1087.100","4.15.0-1088.101","4.15.0-1090.103","4.15.0-1091.104","4.15.0-1092.105","4.15.0-1093.106","4.15.0-1094.107","4.15.0-1095.108","4.15.0-1096.109","4.15.0-1097.110","4.15.0-1098.111","4.15.0-1099.112","4.15.0-1100.113","4.15.0-1103.116","4.15.0-1106.120","4.15.0-1107.121","4.15.0-1108.122","4.15.0-1109.123","4.15.0-1110.124","4.15.0-1111.125","4.15.0-1112.126","4.15.0-1114.128","4.15.0-1115.129","4.15.0-1116.130","4.15.0-1118.132","4.15.0-1119.133","4.15.0-1120.134","4.15.0-1121.135","4.15.0-1122.136","4.15.0-1124.138","4.15.0-1127.142","4.15.0-1130.146","4.15.0-1131.147","4.15.0-1134.150","4.15.0-1135.151","4.15.0-1136.152","4.15.0-1137.153","4.15.0-1138.154","4.15.0-1141.157","4.15.0-1142.158","4.15.0-1143.159","4.15.0-1145.161","4.15.0-1146.162","4.15.0-1147.163","4.15.0-1148.164","4.15.0-1149.165","4.15.0-1150.166","4.15.0-1151.167","4.15.0-1152.168","4.15.0-1153.170","4.15.0-1154.171","4.15.0-1155.172","4.15.0-1156.173","4.15.0-1157.174","4.15.0-1158.175","4.15.0-1159.176","4.15.0-1160.177","4.15.0-1161.178","4.15.0-1162.179","4.15.0-1163.180","4.15.0-1164.181","4.15.0-1165.182","4.15.0-1166.183","4.15.0-1167.184","4.15.0-1168.185"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1159.164"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1026.26","4.15.0-1027.27","4.15.0-1028.28","4.15.0-1029.29","4.15.0-1030.30","4.15.0-1031.31","4.15.0-1032.32","4.15.0-1034.34","4.15.0-1035.35","4.15.0-1036.36","4.15.0-1038.38","4.15.0-1039.39","4.15.0-1042.42","4.15.0-1043.43","4.15.0-1044.44","4.15.0-1046.46","4.15.0-1047.47","4.15.0-1048.48","4.15.0-1050.50","4.15.0-1051.51","4.15.0-1052.52","4.15.0-1053.53","4.15.0-1056.57","4.15.0-1058.59","4.15.0-1059.60","4.15.0-1060.61","4.15.0-1067.68","4.15.0-1069.70","4.15.0-1071.72","4.15.0-1072.73","4.15.0-1074.75","4.15.0-1075.76","4.15.0-1077.79","4.15.0-1079.81","4.15.0-1081.83","4.15.0-1082.84","4.15.0-1084.86","4.15.0-1085.87","4.15.0-1086.88","4.15.0-1087.89","4.15.0-1088.90","4.15.0-1089.91","4.15.0-1090.92","4.15.0-1091.93","4.15.0-1092.94","4.15.0-1094.96","4.15.0-1097.99","4.15.0-1098.100","4.15.0-1099.101","4.15.0-1100.102","4.15.0-1101.103","4.15.0-1102.104","4.15.0-1103.105","4.15.0-1105.107","4.15.0-1106.108","4.15.0-1107.109","4.15.0-1109.112","4.15.0-1110.113","4.15.0-1112.115","4.15.0-1113.116","4.15.0-1114.117","4.15.0-1116.119","4.15.0-1119.123","4.15.0-1122.127","4.15.0-1123.128","4.15.0-1125.130","4.15.0-1126.131","4.15.0-1127.132","4.15.0-1128.133","4.15.0-1129.134","4.15.0-1132.137","4.15.0-1133.138","4.15.0-1134.139","4.15.0-1135.140","4.15.0-1136.141","4.15.0-1137.142","4.15.0-1138.143","4.15.0-1139.144","4.15.0-1140.145","4.15.0-1141.146","4.15.0-1142.147","4.15.0-1143.148","4.15.0-1144.149","4.15.0-1145.150","4.15.0-1146.151","4.15.0-1147.152","4.15.0-1148.153","4.15.0-1149.154","4.15.0-1150.155","4.15.0-1151.156","4.15.0-1152.157","4.15.0-1153.158","4.15.0-1154.159","4.15.0-1155.160","4.15.0-1156.161","4.15.0-1157.162","4.15.0-1158.163"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1138.149"}]}],"versions":["4.15.0-1007.9","4.15.0-1008.10","4.15.0-1009.11","4.15.0-1010.12","4.15.0-1011.13","4.15.0-1013.15","4.15.0-1014.16","4.15.0-1015.17","4.15.0-1017.19","4.15.0-1018.20","4.15.0-1021.23","4.15.0-1022.25","4.15.0-1023.26","4.15.0-1025.28","4.15.0-1026.29","4.15.0-1027.30","4.15.0-1029.32","4.15.0-1030.33","4.15.0-1031.34","4.15.0-1033.36","4.15.0-1035.39","4.15.0-1037.41","4.15.0-1038.42","4.15.0-1039.43","4.15.0-1045.49","4.15.0-1047.51","4.15.0-1048.52","4.15.0-1050.54","4.15.0-1051.55","4.15.0-1053.57","4.15.0-1054.58","4.15.0-1057.62","4.15.0-1058.64","4.15.0-1059.65","4.15.0-1061.67","4.15.0-1062.68","4.15.0-1063.70","4.15.0-1064.71","4.15.0-1065.73","4.15.0-1066.74","4.15.0-1067.75","4.15.0-1068.76","4.15.0-1069.77","4.15.0-1070.78","4.15.0-1071.79","4.15.0-1072.80","4.15.0-1075.83","4.15.0-1078.86","4.15.0-1079.87","4.15.0-1080.88","4.15.0-1081.89","4.15.0-1082.90","4.15.0-1083.91","4.15.0-1084.92","4.15.0-1085.93","4.15.0-1086.94","4.15.0-1087.95","4.15.0-1089.98","4.15.0-1090.99","4.15.0-1091.100","4.15.0-1092.101","4.15.0-1093.102","4.15.0-1095.104","4.15.0-1098.108","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1106.117","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1120.131","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1184.199~14.04.1"}]}],"versions":["4.15.0-1023.24~14.04.1","4.15.0-1030.31~14.04.1","4.15.0-1031.32~14.04.1","4.15.0-1032.33~14.04.2","4.15.0-1035.36~14.04.2","4.15.0-1036.38~14.04.2","4.15.0-1037.39~14.04.2","4.15.0-1039.41~14.04.2","4.15.0-1040.44~14.04.1","4.15.0-1041.45~14.04.1","4.15.0-1042.46~14.04.1","4.15.0-1045.49~14.04.1","4.15.0-1046.50~14.04.1","4.15.0-1047.51~14.04.1","4.15.0-1049.54~14.04.1","4.15.0-1050.55~14.04.1","4.15.0-1051.56~14.04.1","4.15.0-1052.57~14.04.1","4.15.0-1055.60~14.04.1","4.15.0-1056.61~14.04.1","4.15.0-1057.62~14.04.1","4.15.0-1059.64~14.04.1","4.15.0-1060.65~14.04.1","4.15.0-1061.66~14.04.1","4.15.0-1063.68~14.04.1","4.15.0-1064.69~14.04.1","4.15.0-1066.71~14.04.1","4.15.0-1067.72~14.04.1","4.15.0-1069.74~14.04.1","4.15.0-1071.76~14.04.1","4.15.0-1074.79~14.04.1","4.15.0-1077.82~14.04.1","4.15.0-1082.92~14.04.1","4.15.0-1083.93~14.04.1","4.15.0-1089.99~14.04.1","4.15.0-1091.101~14.04.1","4.15.0-1092.102~14.04.1","4.15.0-1093.103~14.04.1","4.15.0-1095.105~14.04.1","4.15.0-1096.106~14.04.1","4.15.0-1098.109~14.04.1","4.15.0-1100.111~14.04.1","4.15.0-1102.113~14.04.1","4.15.0-1103.114~14.04.1","4.15.0-1106.118~14.04.1","4.15.0-1108.120~14.04.1","4.15.0-1109.121~14.04.1","4.15.0-1110.122~14.04.1","4.15.0-1111.123~14.04.1","4.15.0-1112.124~14.04.1","4.15.0-1113.126~14.04.1","4.15.0-1114.127~14.04.1","4.15.0-1115.128~14.04.1","4.15.0-1118.131~14.04.1","4.15.0-1121.134~14.04.1","4.15.0-1122.135~14.04.1","4.15.0-1123.136~14.04.1","4.15.0-1124.137~14.04.1","4.15.0-1125.138~14.04.1","4.15.0-1126.139~14.04.1","4.15.0-1127.140~14.04.1","4.15.0-1129.142~14.04.1","4.15.0-1130.143~14.04.1","4.15.0-1131.144~14.04.1","4.15.0-1133.146~14.04.1","4.15.0-1134.147~14.04.1","4.15.0-1136.149~14.04.1","4.15.0-1137.150~14.04.1","4.15.0-1138.151~14.04.1","4.15.0-1139.152~14.04.1","4.15.0-1142.156~14.04.1","4.15.0-1145.160~14.04.1","4.15.0-1146.161~14.04.1","4.15.0-1149.164~14.04.1","4.15.0-1150.165~14.04.1","4.15.0-1151.166~14.04.1","4.15.0-1153.168~14.04.1","4.15.0-1157.172~14.04.2","4.15.0-1158.173~14.04.1","4.15.0-1159.174~14.04.1","4.15.0-1162.177~14.04.1","4.15.0-1163.178~14.04.1","4.15.0-1164.179~14.04.1","4.15.0-1165.180~14.04.1","4.15.0-1166.181~14.04.1","4.15.0-1167.182~14.04.1","4.15.0-1168.183~14.04.1","4.15.0-1169.184~14.04.1","4.15.0-1170.185~14.04.1","4.15.0-1171.186~14.04.1","4.15.0-1172.187~14.04.1","4.15.0-1173.188~14.04.1","4.15.0-1174.189~14.04.1","4.15.0-1175.190~14.04.1","4.15.0-1176.191~14.04.1","4.15.0-1177.192~14.04.1","4.15.0-1178.193~14.04.1","4.15.0-1179.194~14.04.1","4.15.0-1180.195~14.04.1","4.15.0-1181.196~14.04.1","4.15.0-1182.197~14.04.1","4.15.0-1183.198~14.04.1"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1184.199~16.04.1"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1","4.15.0-1022.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1025.26~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1030.31~16.04.1","4.15.0-1031.32~16.04.1","4.15.0-1032.33~16.04.1","4.15.0-1035.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1039.43","4.15.0-1040.44","4.15.0-1041.45","4.15.0-1042.46","4.15.0-1045.49","4.15.0-1046.50","4.15.0-1047.51","4.15.0-1049.54","4.15.0-1050.55","4.15.0-1051.56","4.15.0-1052.57","4.15.0-1055.60","4.15.0-1056.61","4.15.0-1057.62","4.15.0-1059.64","4.15.0-1060.65","4.15.0-1061.66","4.15.0-1063.68","4.15.0-1064.69","4.15.0-1066.71","4.15.0-1067.72","4.15.0-1069.74","4.15.0-1071.76","4.15.0-1075.80","4.15.0-1077.82","4.15.0-1082.92~16.04.1","4.15.0-1083.93~16.04.1","4.15.0-1089.99~16.04.1","4.15.0-1091.101~16.04.1","4.15.0-1092.102~16.04.1","4.15.0-1093.103~16.04.1","4.15.0-1095.105~16.04.1","4.15.0-1096.106~16.04.1","4.15.0-1098.109~16.04.1","4.15.0-1100.111~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1103.114~16.04.1","4.15.0-1106.118~16.04.1","4.15.0-1108.120~16.04.1","4.15.0-1109.121~16.04.1","4.15.0-1110.122~16.04.1","4.15.0-1111.123~16.04.1","4.15.0-1112.124~16.04.1","4.15.0-1113.126~16.04.1","4.15.0-1114.127~16.04.1","4.15.0-1115.128~16.04.1","4.15.0-1118.131~16.04.1","4.15.0-1121.134~16.04.1","4.15.0-1122.135~16.04.1","4.15.0-1123.136~16.04.1","4.15.0-1124.137~16.04.1","4.15.0-1125.138~16.04.1","4.15.0-1126.139~16.04.1","4.15.0-1127.140~16.04.1","4.15.0-1129.142~16.04.1","4.15.0-1130.143~16.04.1","4.15.0-1131.144~16.04.1","4.15.0-1133.146~16.04.1","4.15.0-1134.147~16.04.1","4.15.0-1136.149~16.04.1","4.15.0-1137.150~16.04.1","4.15.0-1138.151~16.04.1","4.15.0-1139.152~16.04.1","4.15.0-1142.156~16.04.1","4.15.0-1145.160~16.04.1","4.15.0-1146.161~16.04.1","4.15.0-1149.164~16.04.1","4.15.0-1150.165~16.04.1","4.15.0-1151.166~16.04.1","4.15.0-1153.168~16.04.1","4.15.0-1159.174~16.04.1","4.15.0-1162.177~16.04.1","4.15.0-1163.178~16.04.1","4.15.0-1164.179~16.04.1","4.15.0-1165.180~16.04.1","4.15.0-1166.181~16.04.1","4.15.0-1167.182~16.04.1","4.15.0-1168.183~16.04.1","4.15.0-1169.184~16.04.1","4.15.0-1170.185~16.04.1","4.15.0-1171.186~16.04.1","4.15.0-1172.187~16.04.1","4.15.0-1173.188~16.04.1","4.15.0-1174.189~16.04.1","4.15.0-1175.190~16.04.1","4.15.0-1176.191~16.04.1","4.15.0-1177.192~16.04.1","4.15.0-1178.193~16.04.1","4.15.0-1179.194~16.04.1","4.15.0-1180.195~16.04.1","4.15.0-1181.196~16.04.1","4.15.0-1182.197~16.04.1","4.15.0-1183.198~16.04.1"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1184.199"}]}],"versions":["4.15.0-1082.92","4.15.0-1083.93","4.15.0-1089.99","4.15.0-1091.101","4.15.0-1092.102","4.15.0-1093.103","4.15.0-1095.105","4.15.0-1096.106","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1102.113","4.15.0-1103.114","4.15.0-1104.116","4.15.0-1106.118","4.15.0-1108.120","4.15.0-1109.121","4.15.0-1110.122","4.15.0-1111.123","4.15.0-1112.125","4.15.0-1113.126","4.15.0-1114.127","4.15.0-1115.128","4.15.0-1118.131","4.15.0-1121.134","4.15.0-1122.135","4.15.0-1123.136","4.15.0-1124.137","4.15.0-1125.138","4.15.0-1126.139","4.15.0-1127.140","4.15.0-1129.142","4.15.0-1130.143","4.15.0-1131.144","4.15.0-1133.146","4.15.0-1134.147","4.15.0-1136.149","4.15.0-1137.150","4.15.0-1138.151","4.15.0-1139.152","4.15.0-1142.156","4.15.0-1145.160","4.15.0-1146.161","4.15.0-1149.164","4.15.0-1150.165","4.15.0-1151.166","4.15.0-1153.168","4.15.0-1157.172","4.15.0-1158.173","4.15.0-1159.174","4.15.0-1161.176","4.15.0-1162.177","4.15.0-1163.178","4.15.0-1164.179","4.15.0-1165.180","4.15.0-1166.181","4.15.0-1167.182","4.15.0-1168.183","4.15.0-1169.184","4.15.0-1170.185","4.15.0-1171.186","4.15.0-1172.187","4.15.0-1173.188","4.15.0-1174.189","4.15.0-1175.190","4.15.0-1176.191","4.15.0-1177.192","4.15.0-1178.193","4.15.0-1179.194","4.15.0-1180.195","4.15.0-1181.196","4.15.0-1182.197","4.15.0-1183.198"],"bundled":38},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1078.87~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","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1"],"bundled":407},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.23~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","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1"],"bundled":403},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.23"}]}],"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","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21"],"bundled":403}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/fa5bfdf6cb5846a00e712d630a43e3cf55ccb411","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/1b37ec85ad95b612307627758c6018cd9d92cca8","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/ad149f5585345e383baa65f1539d816cd715fd3b","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/0fbe2a72e853a1052abe9bc2b7df8ddb102da227","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/43768fa80fd192558737e24ed6548f74554611d7","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/f1aa7c509aa766080db7ab3aec2e31b1df09e57c","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/21b578f1d599edb87462f11113c5b0fc7a04ac61","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/046667c4d3196938e992fba0dfcde570aa85cd0e","tags":["Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html","tags":["web"]},{"url":"https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45021","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-5m73-3pch-86m2"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-45021","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/ubuntu18-els/CLSA-2024-1731602566.html","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/ubuntu18-els/CLSA-2024-1731603213.html","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/ubuntu16-els/CLSA-2024-1731605761.html","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/ubuntu16-els/CLSA-2024-1731606243.html","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/45xxx/CVE-2024-45021.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-45021","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2217","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46722","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46750","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46777","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46781","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2367","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46735","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47690","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47691","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47727","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47751","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47753","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49850","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49874","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49896","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49909","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50088","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2368","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47723","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50035","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2369","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50046","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243547-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1216223","tags":["report"]},{"url":"https://bugzilla.suse.com/1223600","tags":["report"]},{"url":"https://bugzilla.suse.com/1223958","tags":["report"]},{"url":"https://bugzilla.suse.com/1225272","tags":["report"]},{"url":"https://bugzilla.suse.com/1227487","tags":["report"]},{"url":"https://bugzilla.suse.com/1228466","tags":["report"]},{"url":"https://bugzilla.suse.com/1229407","tags":["report"]},{"url":"https://bugzilla.suse.com/1229633","tags":["report"]},{"url":"https://bugzilla.suse.com/1229662","tags":["report"]},{"url":"https://bugzilla.suse.com/1229947","tags":["report"]},{"url":"https://bugzilla.suse.com/1230015","tags":["report"]},{"url":"https://bugzilla.suse.com/1230398","tags":["report"]},{"url":"https://bugzilla.suse.com/1230434","tags":["report"]},{"url":"https://bugzilla.suse.com/1230507","tags":["report"]},{"url":"https://bugzilla.suse.com/1230767","tags":["report"]},{"url":"https://bugzilla.suse.com/1231016","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46774","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243551-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1183045","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1216776","tags":["report"]},{"url":"https://bugzilla.suse.com/1220382","tags":["report"]},{"url":"https://bugzilla.suse.com/1221527","tags":["report"]},{"url":"https://bugzilla.suse.com/1221610","tags":["report"]},{"url":"https://bugzilla.suse.com/1221650","tags":["report"]},{"url":"https://bugzilla.suse.com/1222629","tags":["report"]},{"url":"https://bugzilla.suse.com/1223848","tags":["report"]},{"url":"https://bugzilla.suse.com/1225487","tags":["report"]},{"url":"https://bugzilla.suse.com/1225812","tags":["report"]},{"url":"https://bugzilla.suse.com/1225903","tags":["report"]},{"url":"https://bugzilla.suse.com/1226003","tags":["report"]},{"url":"https://bugzilla.suse.com/1226507","tags":["report"]},{"url":"https://bugzilla.suse.com/1226606","tags":["report"]},{"url":"https://bugzilla.suse.com/1226666","tags":["report"]},{"url":"https://bugzilla.suse.com/1226846","tags":["report"]},{"url":"https://bugzilla.suse.com/1226860","tags":["report"]},{"url":"https://bugzilla.suse.com/1227694","tags":["report"]},{"url":"https://bugzilla.suse.com/1227726","tags":["report"]},{"url":"https://bugzilla.suse.com/1227819","tags":["report"]},{"url":"https://bugzilla.suse.com/1227885","tags":["report"]},{"url":"https://bugzilla.suse.com/1227890","tags":["report"]},{"url":"https://bugzilla.suse.com/1227962","tags":["report"]},{"url":"https://bugzilla.suse.com/1228090","tags":["report"]},{"url":"https://bugzilla.suse.com/1228140","tags":["report"]},{"url":"https://bugzilla.suse.com/1228244","tags":["report"]},{"url":"https://bugzilla.suse.com/1228507","tags":["report"]},{"url":"https://bugzilla.suse.com/1228771","tags":["report"]},{"url":"https://bugzilla.suse.com/1229001","tags":["report"]},{"url":"https://bugzilla.suse.com/1229004","tags":["report"]},{"url":"https://bugzilla.suse.com/1229019","tags":["report"]},{"url":"https://bugzilla.suse.com/1229086","tags":["report"]},{"url":"https://bugzilla.suse.com/1229167","tags":["report"]},{"url":"https://bugzilla.suse.com/1229169","tags":["report"]},{"url":"https://bugzilla.suse.com/1229289","tags":["report"]},{"url":"https://bugzilla.suse.com/1229334","tags":["report"]},{"url":"https://bugzilla.suse.com/1229362","tags":["report"]},{"url":"https://bugzilla.suse.com/1229363","tags":["report"]},{"url":"https://bugzilla.suse.com/1229364","tags":["report"]},{"url":"https://bugzilla.suse.com/1229371","tags":["report"]},{"url":"https://bugzilla.suse.com/1229380","tags":["report"]},{"url":"https://bugzilla.suse.com/1229389","tags":["report"]},{"url":"https://bugzilla.suse.com/1229394","tags":["report"]},{"url":"https://bugzilla.suse.com/1229429","tags":["report"]},{"url":"https://bugzilla.suse.com/1229443","tags":["report"]},{"url":"https://bugzilla.suse.com/1229452","tags":["report"]},{"url":"https://bugzilla.suse.com/1229455","tags":["report"]},{"url":"https://bugzilla.suse.com/1229456","tags":["report"]},{"url":"https://bugzilla.suse.com/1229494","tags":["report"]},{"url":"https://bugzilla.suse.com/1229585","tags":["report"]},{"url":"https://bugzilla.suse.com/1229753","tags":["report"]},{"url":"https://bugzilla.suse.com/1229764","tags":["report"]},{"url":"https://bugzilla.suse.com/1229768","tags":["report"]},{"url":"https://bugzilla.suse.com/1229790","tags":["report"]},{"url":"https://bugzilla.suse.com/1229810","tags":["report"]},{"url":"https://bugzilla.suse.com/1229899","tags":["report"]},{"url":"https://bugzilla.suse.com/1229928","tags":["report"]},{"url":"https://bugzilla.suse.com/1230119","tags":["report"]},{"url":"https://bugzilla.suse.com/1230123","tags":["report"]},{"url":"https://bugzilla.suse.com/1230124","tags":["report"]},{"url":"https://bugzilla.suse.com/1230125","tags":["report"]},{"url":"https://bugzilla.suse.com/1230169","tags":["report"]},{"url":"https://bugzilla.suse.com/1230170","tags":["report"]},{"url":"https://bugzilla.suse.com/1230171","tags":["report"]},{"url":"https://bugzilla.suse.com/1230173","tags":["report"]},{"url":"https://bugzilla.suse.com/1230174","tags":["report"]},{"url":"https://bugzilla.suse.com/1230175","tags":["report"]},{"url":"https://bugzilla.suse.com/1230176","tags":["report"]},{"url":"https://bugzilla.suse.com/1230178","tags":["report"]},{"url":"https://bugzilla.suse.com/1230180","tags":["report"]},{"url":"https://bugzilla.suse.com/1230181","tags":["report"]},{"url":"https://bugzilla.suse.com/1230185","tags":["report"]},{"url":"https://bugzilla.suse.com/1230191","tags":["report"]},{"url":"https://bugzilla.suse.com/1230192","tags":["report"]},{"url":"https://bugzilla.suse.com/1230193","tags":["report"]},{"url":"https://bugzilla.suse.com/1230194","tags":["report"]},{"url":"https://bugzilla.suse.com/1230195","tags":["report"]},{"url":"https://bugzilla.suse.com/1230200","tags":["report"]},{"url":"https://bugzilla.suse.com/1230204","tags":["report"]},{"url":"https://bugzilla.suse.com/1230206","tags":["report"]},{"url":"https://bugzilla.suse.com/1230207","tags":["report"]},{"url":"https://bugzilla.suse.com/1230209","tags":["report"]},{"url":"https://bugzilla.suse.com/1230211","tags":["report"]},{"url":"https://bugzilla.suse.com/1230213","tags":["report"]},{"url":"https://bugzilla.suse.com/1230217","tags":["report"]},{"url":"https://bugzilla.suse.com/1230221","tags":["report"]},{"url":"https://bugzilla.suse.com/1230224","tags":["report"]},{"url":"https://bugzilla.suse.com/1230230","tags":["report"]},{"url":"https://bugzilla.suse.com/1230232","tags":["report"]},{"url":"https://bugzilla.suse.com/1230233","tags":["report"]},{"url":"https://bugzilla.suse.com/1230240","tags":["report"]},{"url":"https://bugzilla.suse.com/1230244","tags":["report"]},{"url":"https://bugzilla.suse.com/1230245","tags":["report"]},{"url":"https://bugzilla.suse.com/1230247","tags":["report"]},{"url":"https://bugzilla.suse.com/1230248","tags":["report"]},{"url":"https://bugzilla.suse.com/1230269","tags":["report"]},{"url":"https://bugzilla.suse.com/1230270","tags":["report"]},{"url":"https://bugzilla.suse.com/1230295","tags":["report"]},{"url":"https://bugzilla.suse.com/1230340","tags":["report"]},{"url":"https://bugzilla.suse.com/1230350","tags":["report"]},{"url":"https://bugzilla.suse.com/1230413","tags":["report"]},{"url":"https://bugzilla.suse.com/1230426","tags":["report"]},{"url":"https://bugzilla.suse.com/1230430","tags":["report"]},{"url":"https://bugzilla.suse.com/1230431","tags":["report"]},{"url":"https://bugzilla.suse.com/1230432","tags":["report"]},{"url":"https://bugzilla.suse.com/1230433","tags":["report"]},{"url":"https://bugzilla.suse.com/1230435","tags":["report"]},{"url":"https://bugzilla.suse.com/1230440","tags":["report"]},{"url":"https://bugzilla.suse.com/1230441","tags":["report"]},{"url":"https://bugzilla.suse.com/1230442","tags":["report"]},{"url":"https://bugzilla.suse.com/1230444","tags":["report"]},{"url":"https://bugzilla.suse.com/1230450","tags":["report"]},{"url":"https://bugzilla.suse.com/1230451","tags":["report"]},{"url":"https://bugzilla.suse.com/1230454","tags":["report"]},{"url":"https://bugzilla.suse.com/1230455","tags":["report"]},{"url":"https://bugzilla.suse.com/1230457","tags":["report"]},{"url":"https://bugzilla.suse.com/1230459","tags":["report"]},{"url":"https://bugzilla.suse.com/1230506","tags":["report"]},{"url":"https://bugzilla.suse.com/1230511","tags":["report"]},{"url":"https://bugzilla.suse.com/1230515","tags":["report"]},{"url":"https://bugzilla.suse.com/1230517","tags":["report"]},{"url":"https://bugzilla.suse.com/1230518","tags":["report"]},{"url":"https://bugzilla.suse.com/1230519","tags":["report"]},{"url":"https://bugzilla.suse.com/1230520","tags":["report"]},{"url":"https://bugzilla.suse.com/1230521","tags":["report"]},{"url":"https://bugzilla.suse.com/1230524","tags":["report"]},{"url":"https://bugzilla.suse.com/1230526","tags":["report"]},{"url":"https://bugzilla.suse.com/1230533","tags":["report"]},{"url":"https://bugzilla.suse.com/1230535","tags":["report"]},{"url":"https://bugzilla.suse.com/1230539","tags":["report"]},{"url":"https://bugzilla.suse.com/1230540","tags":["report"]},{"url":"https://bugzilla.suse.com/1230549","tags":["report"]},{"url":"https://bugzilla.suse.com/1230556","tags":["report"]},{"url":"https://bugzilla.suse.com/1230562","tags":["report"]},{"url":"https://bugzilla.suse.com/1230563","tags":["report"]},{"url":"https://bugzilla.suse.com/1230564","tags":["report"]},{"url":"https://bugzilla.suse.com/1230580","tags":["report"]},{"url":"https://bugzilla.suse.com/1230582","tags":["report"]},{"url":"https://bugzilla.suse.com/1230589","tags":["report"]},{"url":"https://bugzilla.suse.com/1230602","tags":["report"]},{"url":"https://bugzilla.suse.com/1230699","tags":["report"]},{"url":"https://bugzilla.suse.com/1230700","tags":["report"]},{"url":"https://bugzilla.suse.com/1230701","tags":["report"]},{"url":"https://bugzilla.suse.com/1230702","tags":["report"]},{"url":"https://bugzilla.suse.com/1230703","tags":["report"]},{"url":"https://bugzilla.suse.com/1230704","tags":["report"]},{"url":"https://bugzilla.suse.com/1230705","tags":["report"]},{"url":"https://bugzilla.suse.com/1230706","tags":["report"]},{"url":"https://bugzilla.suse.com/1230709","tags":["report"]},{"url":"https://bugzilla.suse.com/1230711","tags":["report"]},{"url":"https://bugzilla.suse.com/1230712","tags":["report"]},{"url":"https://bugzilla.suse.com/1230715","tags":["report"]},{"url":"https://bugzilla.suse.com/1230719","tags":["report"]},{"url":"https://bugzilla.suse.com/1230722","tags":["report"]},{"url":"https://bugzilla.suse.com/1230724","tags":["report"]},{"url":"https://bugzilla.suse.com/1230725","tags":["report"]},{"url":"https://bugzilla.suse.com/1230726","tags":["report"]},{"url":"https://bugzilla.suse.com/1230727","tags":["report"]},{"url":"https://bugzilla.suse.com/1230730","tags":["report"]},{"url":"https://bugzilla.suse.com/1230731","tags":["report"]},{"url":"https://bugzilla.suse.com/1230732","tags":["report"]},{"url":"https://bugzilla.suse.com/1230747","tags":["report"]},{"url":"https://bugzilla.suse.com/1230748","tags":["report"]},{"url":"https://bugzilla.suse.com/1230749","tags":["report"]},{"url":"https://bugzilla.suse.com/1230751","tags":["report"]},{"url":"https://bugzilla.suse.com/1230752","tags":["report"]},{"url":"https://bugzilla.suse.com/1230753","tags":["report"]},{"url":"https://bugzilla.suse.com/1230756","tags":["report"]},{"url":"https://bugzilla.suse.com/1230761","tags":["report"]},{"url":"https://bugzilla.suse.com/1230766","tags":["report"]},{"url":"https://bugzilla.suse.com/1230768","tags":["report"]},{"url":"https://bugzilla.suse.com/1230771","tags":["report"]},{"url":"https://bugzilla.suse.com/1230772","tags":["report"]},{"url":"https://bugzilla.suse.com/1230775","tags":["report"]},{"url":"https://bugzilla.suse.com/1230776","tags":["report"]},{"url":"https://bugzilla.suse.com/1230780","tags":["report"]},{"url":"https://bugzilla.suse.com/1230783","tags":["report"]},{"url":"https://bugzilla.suse.com/1230786","tags":["report"]},{"url":"https://bugzilla.suse.com/1230787","tags":["report"]},{"url":"https://bugzilla.suse.com/1230791","tags":["report"]},{"url":"https://bugzilla.suse.com/1230794","tags":["report"]},{"url":"https://bugzilla.suse.com/1230796","tags":["report"]},{"url":"https://bugzilla.suse.com/1230802","tags":["report"]},{"url":"https://bugzilla.suse.com/1230806","tags":["report"]},{"url":"https://bugzilla.suse.com/1230808","tags":["report"]},{"url":"https://bugzilla.suse.com/1230809","tags":["report"]},{"url":"https://bugzilla.suse.com/1230810","tags":["report"]},{"url":"https://bugzilla.suse.com/1230812","tags":["report"]},{"url":"https://bugzilla.suse.com/1230813","tags":["report"]},{"url":"https://bugzilla.suse.com/1230814","tags":["report"]},{"url":"https://bugzilla.suse.com/1230815","tags":["report"]},{"url":"https://bugzilla.suse.com/1230821","tags":["report"]},{"url":"https://bugzilla.suse.com/1230825","tags":["report"]},{"url":"https://bugzilla.suse.com/1230830","tags":["report"]},{"url":"https://bugzilla.suse.com/1230831","tags":["report"]},{"url":"https://bugzilla.suse.com/1230854","tags":["report"]},{"url":"https://bugzilla.suse.com/1230948","tags":["report"]},{"url":"https://bugzilla.suse.com/1231008","tags":["report"]},{"url":"https://bugzilla.suse.com/1231035","tags":["report"]},{"url":"https://bugzilla.suse.com/1231120","tags":["report"]},{"url":"https://bugzilla.suse.com/1231146","tags":["report"]},{"url":"https://bugzilla.suse.com/1231182","tags":["report"]},{"url":"https://bugzilla.suse.com/1231183","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52610","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46822","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243553-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1229748","tags":["report"]},{"url":"https://bugzilla.suse.com/1230212","tags":["report"]},{"url":"https://bugzilla.suse.com/1230542","tags":["report"]},{"url":"https://bugzilla.suse.com/1230707","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46727","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243561-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243563-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243564-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243565-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1185988","tags":["report"]},{"url":"https://bugzilla.suse.com/1220826","tags":["report"]},{"url":"https://bugzilla.suse.com/1226145","tags":["report"]},{"url":"https://bugzilla.suse.com/1230326","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36971","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243567-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243569-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1199769","tags":["report"]},{"url":"https://bugzilla.suse.com/1222973","tags":["report"]},{"url":"https://bugzilla.suse.com/1224085","tags":["report"]},{"url":"https://bugzilla.suse.com/1226662","tags":["report"]},{"url":"https://bugzilla.suse.com/1226875","tags":["report"]},{"url":"https://bugzilla.suse.com/1226915","tags":["report"]},{"url":"https://bugzilla.suse.com/1227832","tags":["report"]},{"url":"https://bugzilla.suse.com/1228576","tags":["report"]},{"url":"https://bugzilla.suse.com/1228620","tags":["report"]},{"url":"https://bugzilla.suse.com/1229031","tags":["report"]},{"url":"https://bugzilla.suse.com/1229034","tags":["report"]},{"url":"https://bugzilla.suse.com/1229156","tags":["report"]},{"url":"https://bugzilla.suse.com/1229453","tags":["report"]},{"url":"https://bugzilla.suse.com/1229572","tags":["report"]},{"url":"https://bugzilla.suse.com/1229573","tags":["report"]},{"url":"https://bugzilla.suse.com/1229607","tags":["report"]},{"url":"https://bugzilla.suse.com/1229619","tags":["report"]},{"url":"https://bugzilla.suse.com/1229830","tags":["report"]},{"url":"https://bugzilla.suse.com/1230129","tags":["report"]},{"url":"https://bugzilla.suse.com/1230130","tags":["report"]},{"url":"https://bugzilla.suse.com/1230339","tags":["report"]},{"url":"https://bugzilla.suse.com/1230392","tags":["report"]},{"url":"https://bugzilla.suse.com/1230591","tags":["report"]},{"url":"https://bugzilla.suse.com/1230592","tags":["report"]},{"url":"https://bugzilla.suse.com/1230710","tags":["report"]},{"url":"https://bugzilla.suse.com/1230733","tags":["report"]},{"url":"https://bugzilla.suse.com/1231013","tags":["report"]},{"url":"https://bugzilla.suse.com/1231017","tags":["report"]},{"url":"https://bugzilla.suse.com/1231116","tags":["report"]},{"url":"https://bugzilla.suse.com/1231180","tags":["report"]},{"url":"https://bugzilla.suse.com/1231181","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-37353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46830","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243585-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243587-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1054914","tags":["report"]},{"url":"https://bugzilla.suse.com/1065729","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1226631","tags":["report"]},{"url":"https://bugzilla.suse.com/1228747","tags":["report"]},{"url":"https://bugzilla.suse.com/1229891","tags":["report"]},{"url":"https://bugzilla.suse.com/1230055","tags":["report"]},{"url":"https://bugzilla.suse.com/1230289","tags":["report"]},{"url":"https://bugzilla.suse.com/1230550","tags":["report"]},{"url":"https://bugzilla.suse.com/1230763","tags":["report"]},{"url":"https://bugzilla.suse.com/1230774","tags":["report"]},{"url":"https://bugzilla.suse.com/1231084","tags":["report"]},{"url":"https://bugzilla.suse.com/1231085","tags":["report"]},{"url":"https://bugzilla.suse.com/1231087","tags":["report"]},{"url":"https://bugzilla.suse.com/1231115","tags":["report"]},{"url":"https://bugzilla.suse.com/1231277","tags":["report"]},{"url":"https://bugzilla.suse.com/1231327","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46857","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243592-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243617-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1214298","tags":["report"]},{"url":"https://bugzilla.suse.com/1227764","tags":["report"]},{"url":"https://bugzilla.suse.com/1228487","tags":["report"]},{"url":"https://bugzilla.suse.com/1228654","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42148","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501983-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1184350","tags":["report"]},{"url":"https://bugzilla.suse.com/1190317","tags":["report"]},{"url":"https://bugzilla.suse.com/1190601","tags":["report"]},{"url":"https://bugzilla.suse.com/1194227","tags":["report"]},{"url":"https://bugzilla.suse.com/1206073","tags":["report"]},{"url":"https://bugzilla.suse.com/1206649","tags":["report"]},{"url":"https://bugzilla.suse.com/1206677","tags":["report"]},{"url":"https://bugzilla.suse.com/1206887","tags":["report"]},{"url":"https://bugzilla.suse.com/1209292","tags":["report"]},{"url":"https://bugzilla.suse.com/1209556","tags":["report"]},{"url":"https://bugzilla.suse.com/1209684","tags":["report"]},{"url":"https://bugzilla.suse.com/1210336","tags":["report"]},{"url":"https://bugzilla.suse.com/1210337","tags":["report"]},{"url":"https://bugzilla.suse.com/1211466","tags":["report"]},{"url":"https://bugzilla.suse.com/1213012","tags":["report"]},{"url":"https://bugzilla.suse.com/1213013","tags":["report"]},{"url":"https://bugzilla.suse.com/1218752","tags":["report"]},{"url":"https://bugzilla.suse.com/1222004","tags":["report"]},{"url":"https://bugzilla.suse.com/1222563","tags":["report"]},{"url":"https://bugzilla.suse.com/1223720","tags":["report"]},{"url":"https://bugzilla.suse.com/1225044","tags":["report"]},{"url":"https://bugzilla.suse.com/1229516","tags":["report"]},{"url":"https://bugzilla.suse.com/1232504","tags":["report"]},{"url":"https://bugzilla.suse.com/1232649","tags":["report"]},{"url":"https://bugzilla.suse.com/1232882","tags":["report"]},{"url":"https://bugzilla.suse.com/1234887","tags":["report"]},{"url":"https://bugzilla.suse.com/1235485","tags":["report"]},{"url":"https://bugzilla.suse.com/1235632","tags":["report"]},{"url":"https://bugzilla.suse.com/1236142","tags":["report"]},{"url":"https://bugzilla.suse.com/1237312","tags":["report"]},{"url":"https://bugzilla.suse.com/1237571","tags":["report"]},{"url":"https://bugzilla.suse.com/1238019","tags":["report"]},{"url":"https://bugzilla.suse.com/1238032","tags":["report"]},{"url":"https://bugzilla.suse.com/1238071","tags":["report"]},{"url":"https://bugzilla.suse.com/1238109","tags":["report"]},{"url":"https://bugzilla.suse.com/1238130","tags":["report"]},{"url":"https://bugzilla.suse.com/1238162","tags":["report"]},{"url":"https://bugzilla.suse.com/1238263","tags":["report"]},{"url":"https://bugzilla.suse.com/1238284","tags":["report"]},{"url":"https://bugzilla.suse.com/1238289","tags":["report"]},{"url":"https://bugzilla.suse.com/1238306","tags":["report"]},{"url":"https://bugzilla.suse.com/1238311","tags":["report"]},{"url":"https://bugzilla.suse.com/1238331","tags":["report"]},{"url":"https://bugzilla.suse.com/1238333","tags":["report"]},{"url":"https://bugzilla.suse.com/1238338","tags":["report"]},{"url":"https://bugzilla.suse.com/1238394","tags":["report"]},{"url":"https://bugzilla.suse.com/1238411","tags":["report"]},{"url":"https://bugzilla.suse.com/1238420","tags":["report"]},{"url":"https://bugzilla.suse.com/1238473","tags":["report"]},{"url":"https://bugzilla.suse.com/1238539","tags":["report"]},{"url":"https://bugzilla.suse.com/1238546","tags":["report"]},{"url":"https://bugzilla.suse.com/1238646","tags":["report"]},{"url":"https://bugzilla.suse.com/1238774","tags":["report"]},{"url":"https://bugzilla.suse.com/1238806","tags":["report"]},{"url":"https://bugzilla.suse.com/1238815","tags":["report"]},{"url":"https://bugzilla.suse.com/1238818","tags":["report"]},{"url":"https://bugzilla.suse.com/1238868","tags":["report"]},{"url":"https://bugzilla.suse.com/1238871","tags":["report"]},{"url":"https://bugzilla.suse.com/1238887","tags":["report"]},{"url":"https://bugzilla.suse.com/1238892","tags":["report"]},{"url":"https://bugzilla.suse.com/1239060","tags":["report"]},{"url":"https://bugzilla.suse.com/1239111","tags":["report"]},{"url":"https://bugzilla.suse.com/1240254","tags":["report"]},{"url":"https://bugzilla.suse.com/1240261","tags":["report"]},{"url":"https://bugzilla.suse.com/1240266","tags":["report"]},{"url":"https://bugzilla.suse.com/1240293","tags":["report"]},{"url":"https://bugzilla.suse.com/1240297","tags":["report"]},{"url":"https://bugzilla.suse.com/1240322","tags":["report"]},{"url":"https://bugzilla.suse.com/1240784","tags":["report"]},{"url":"https://bugzilla.suse.com/1241282","tags":["report"]},{"url":"https://bugzilla.suse.com/1241332","tags":["report"]},{"url":"https://bugzilla.suse.com/1241351","tags":["report"]},{"url":"https://bugzilla.suse.com/1241357","tags":["report"]},{"url":"https://bugzilla.suse.com/1241361","tags":["report"]},{"url":"https://bugzilla.suse.com/1241369","tags":["report"]},{"url":"https://bugzilla.suse.com/1241407","tags":["report"]},{"url":"https://bugzilla.suse.com/1241441","tags":["report"]},{"url":"https://bugzilla.suse.com/1241526","tags":["report"]},{"url":"https://bugzilla.suse.com/1241550","tags":["report"]},{"url":"https://bugzilla.suse.com/1241657","tags":["report"]},{"url":"https://bugzilla.suse.com/1242147","tags":["report"]},{"url":"https://bugzilla.suse.com/1242154","tags":["report"]},{"url":"https://bugzilla.suse.com/1242165","tags":["report"]},{"url":"https://bugzilla.suse.com/1242215","tags":["report"]},{"url":"https://bugzilla.suse.com/1242218","tags":["report"]},{"url":"https://bugzilla.suse.com/1242219","tags":["report"]},{"url":"https://bugzilla.suse.com/1242225","tags":["report"]},{"url":"https://bugzilla.suse.com/1242227","tags":["report"]},{"url":"https://bugzilla.suse.com/1242228","tags":["report"]},{"url":"https://bugzilla.suse.com/1242231","tags":["report"]},{"url":"https://bugzilla.suse.com/1242239","tags":["report"]},{"url":"https://bugzilla.suse.com/1242241","tags":["report"]},{"url":"https://bugzilla.suse.com/1242245","tags":["report"]},{"url":"https://bugzilla.suse.com/1242248","tags":["report"]},{"url":"https://bugzilla.suse.com/1242284","tags":["report"]},{"url":"https://bugzilla.suse.com/1242285","tags":["report"]},{"url":"https://bugzilla.suse.com/1242287","tags":["report"]},{"url":"https://bugzilla.suse.com/1242288","tags":["report"]},{"url":"https://bugzilla.suse.com/1242352","tags":["report"]},{"url":"https://bugzilla.suse.com/1242353","tags":["report"]},{"url":"https://bugzilla.suse.com/1242361","tags":["report"]},{"url":"https://bugzilla.suse.com/1242362","tags":["report"]},{"url":"https://bugzilla.suse.com/1242366","tags":["report"]},{"url":"https://bugzilla.suse.com/1242370","tags":["report"]},{"url":"https://bugzilla.suse.com/1242371","tags":["report"]},{"url":"https://bugzilla.suse.com/1242372","tags":["report"]},{"url":"https://bugzilla.suse.com/1242377","tags":["report"]},{"url":"https://bugzilla.suse.com/1242378","tags":["report"]},{"url":"https://bugzilla.suse.com/1242382","tags":["report"]},{"url":"https://bugzilla.suse.com/1242385","tags":["report"]},{"url":"https://bugzilla.suse.com/1242394","tags":["report"]},{"url":"https://bugzilla.suse.com/1242398","tags":["report"]},{"url":"https://bugzilla.suse.com/1242405","tags":["report"]},{"url":"https://bugzilla.suse.com/1242408","tags":["report"]},{"url":"https://bugzilla.suse.com/1242409","tags":["report"]},{"url":"https://bugzilla.suse.com/1242414","tags":["report"]},{"url":"https://bugzilla.suse.com/1242416","tags":["report"]},{"url":"https://bugzilla.suse.com/1242417","tags":["report"]},{"url":"https://bugzilla.suse.com/1242422","tags":["report"]},{"url":"https://bugzilla.suse.com/1242426","tags":["report"]},{"url":"https://bugzilla.suse.com/1242427","tags":["report"]},{"url":"https://bugzilla.suse.com/1242440","tags":["report"]},{"url":"https://bugzilla.suse.com/1242447","tags":["report"]},{"url":"https://bugzilla.suse.com/1242449","tags":["report"]},{"url":"https://bugzilla.suse.com/1242450","tags":["report"]},{"url":"https://bugzilla.suse.com/1242452","tags":["report"]},{"url":"https://bugzilla.suse.com/1242453","tags":["report"]},{"url":"https://bugzilla.suse.com/1242455","tags":["report"]},{"url":"https://bugzilla.suse.com/1242464","tags":["report"]},{"url":"https://bugzilla.suse.com/1242470","tags":["report"]},{"url":"https://bugzilla.suse.com/1242472","tags":["report"]},{"url":"https://bugzilla.suse.com/1242478","tags":["report"]},{"url":"https://bugzilla.suse.com/1242483","tags":["report"]},{"url":"https://bugzilla.suse.com/1242484","tags":["report"]},{"url":"https://bugzilla.suse.com/1242497","tags":["report"]},{"url":"https://bugzilla.suse.com/1242504","tags":["report"]},{"url":"https://bugzilla.suse.com/1242513","tags":["report"]},{"url":"https://bugzilla.suse.com/1242527","tags":["report"]},{"url":"https://bugzilla.suse.com/1242542","tags":["report"]},{"url":"https://bugzilla.suse.com/1242544","tags":["report"]},{"url":"https://bugzilla.suse.com/1242549","tags":["report"]},{"url":"https://bugzilla.suse.com/1242558","tags":["report"]},{"url":"https://bugzilla.suse.com/1242566","tags":["report"]},{"url":"https://bugzilla.suse.com/1242570","tags":["report"]},{"url":"https://bugzilla.suse.com/1242580","tags":["report"]},{"url":"https://bugzilla.suse.com/1242594","tags":["report"]},{"url":"https://bugzilla.suse.com/1242686","tags":["report"]},{"url":"https://bugzilla.suse.com/1242688","tags":["report"]},{"url":"https://bugzilla.suse.com/1242691","tags":["report"]},{"url":"https://bugzilla.suse.com/1242716","tags":["report"]},{"url":"https://bugzilla.suse.com/1242727","tags":["report"]},{"url":"https://bugzilla.suse.com/1242734","tags":["report"]},{"url":"https://bugzilla.suse.com/1242745","tags":["report"]},{"url":"https://bugzilla.suse.com/1242747","tags":["report"]},{"url":"https://bugzilla.suse.com/1242755","tags":["report"]},{"url":"https://bugzilla.suse.com/1242756","tags":["report"]},{"url":"https://bugzilla.suse.com/1242759","tags":["report"]},{"url":"https://bugzilla.suse.com/1242762","tags":["report"]},{"url":"https://bugzilla.suse.com/1242765","tags":["report"]},{"url":"https://bugzilla.suse.com/1242770","tags":["report"]},{"url":"https://bugzilla.suse.com/1242778","tags":["report"]},{"url":"https://bugzilla.suse.com/1242786","tags":["report"]},{"url":"https://bugzilla.suse.com/1242790","tags":["report"]},{"url":"https://bugzilla.suse.com/1242791","tags":["report"]},{"url":"https://bugzilla.suse.com/1242792","tags":["report"]},{"url":"https://bugzilla.suse.com/1242835","tags":["report"]},{"url":"https://bugzilla.suse.com/1242859","tags":["report"]},{"url":"https://bugzilla.suse.com/1242868","tags":["report"]},{"url":"https://bugzilla.suse.com/1242924","tags":["report"]},{"url":"https://bugzilla.suse.com/1242949","tags":["report"]},{"url":"https://bugzilla.suse.com/1243047","tags":["report"]},{"url":"https://bugzilla.suse.com/1243074","tags":["report"]},{"url":"https://bugzilla.suse.com/1243077","tags":["report"]},{"url":"https://bugzilla.suse.com/1243511","tags":["report"]},{"url":"https://bugzilla.suse.com/1243541","tags":["report"]},{"url":"https://bugzilla.suse.com/1243543","tags":["report"]},{"url":"https://bugzilla.suse.com/1243627","tags":["report"]},{"url":"https://bugzilla.suse.com/1243649","tags":["report"]},{"url":"https://bugzilla.suse.com/1243660","tags":["report"]},{"url":"https://bugzilla.suse.com/1243919","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-4159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49592","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56633","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38637","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520073-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520077-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-45021","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45021","tags":["report"]},{"url":"https://git.kernel.org/linus/046667c4d3196938e992fba0dfcde570aa85cd0e","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7088-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7088-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7088-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7088-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7100-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7100-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7088-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7119-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7123-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7144-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7154-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7155-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7156-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7154-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7183-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7184-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7185-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7185-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7194-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7196-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-47212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-36402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43837","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41033","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-41036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41039","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-41045","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-41050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41088","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-41094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42074","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-42079","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-42088","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-42091","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-42100","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-42103","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-42108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42118","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-42128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42151","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-42155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42159","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-42227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2020-12351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2020-12352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2020-24490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-35827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38538","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-38553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50191","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-45021","title":"memcg_write_event_control(): fix a user-triggerable oops","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T15:13:55.211Z","modified":"2026-08-05T11:37:45.912Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"cna"}],"updated_at":"2026-11-02T14:34:07.831255Z"}],"euvd":[{"id":"EUVD-2024-41501","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T15:13:55Z","modified":"2026-08-05T11:37:45Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T18:02:16.228226Z"}],"ghsa":[{"id":"GHSA-5m73-3pch-86m2","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control():...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T18:31:06Z","modified":"2025-11-04T00:31:23Z","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"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T15:04:27.827902Z"}],"nvd":[{"id":"CVE-2024-45021","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T16:15:07.103Z","modified":"2026-08-04T11:20:11.743Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"secondary"},{"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"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T14:10:25.561537Z"}],"osv":[{"id":"AZL-49170","title":"CVE-2024-45021 affecting package kernel for versions less than 5.15.167.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T16:15:07Z","modified":"2026-04-21T04:29:48.040199Z","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:06.032783Z"},{"id":"AZL-49242","title":"CVE-2024-45021 affecting package kernel for versions less than 6.6.51.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T16:15:07Z","modified":"2026-04-21T04:54:58.04268Z","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:06.032783Z"},{"id":"BELL-CVE-2024-45021","status":"published","published":"2024-09-12T05:56:45.48876Z","modified":"2026-01-26T09:37:55.852507Z","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:20.452786Z"},{"id":"CVE-2024-45021","title":"memcg_write_event_control(): fix a user-triggerable oops","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg_write_event_control(): fix a user-triggerable oops\n\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T15:13:55.211Z","modified":"2026-10-28T02:30:22.256704327Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:42.790566Z"},{"id":"DEBIAN-CVE-2024-45021","description":"In the Linux kernel, the following vulnerability has been resolved:  memcg_write_event_control(): fix a user-triggerable oops  we are *not* guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T16:15:07.103Z","modified":"2026-11-02T12:03:00.758041895Z","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:43.473331Z"},{"id":"OESA-2024-2217","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\nALSA: line6: Fix racy access to midibuf\r\n\r\nThere can be concurrent accesses to line6 midibuf from both the URB\ncompletion callback and the rawmidi API access.  This could be a cause\nof KMSAN warning triggered by syzkaller below (so put as reported-by\nhere).\r\n\r\nThis patch protects the midibuf call of the former code path with a\nspinlock for avoiding the possible races.(CVE-2024-44954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched/smt: Fix unbalance sched_smt_present dec/inc\r\n\r\nI got the following warn report while doing stress test:\r\n\r\njump label: negative count!\nWARNING: CPU: 3 PID: 38 at kernel/jump_label.c:263 static_key_slow_try_dec+0x9d/0xb0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __static_key_slow_dec_cpuslocked+0x16/0x70\n sched_cpu_deactivate+0x26e/0x2a0\n cpuhp_invoke_callback+0x3ad/0x10d0\n cpuhp_thread_fun+0x3f5/0x680\n smpboot_thread_fn+0x56d/0x8d0\n kthread+0x309/0x400\n ret_from_fork+0x41/0x70\n ret_from_fork_asm+0x1b/0x30\n \u0026lt;/TASK\u0026gt;\r\n\r\nBecause when cpuset_cpu_inactive() fails in sched_cpu_deactivate(),\nthe cpu offline failed, but sched_smt_present is decremented before\ncalling sched_cpu_deactivate(), it leads to unbalanced dec/inc, so\nfix it by incrementing sched_smt_present in the error path.(CVE-2024-44958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: aacraid: Fix double-free on probe failure\r\n\r\naac_probe_one() calls hardware-specific init functions through the\naac_driver_ident::init pointer, all of which eventually call down to\naac_init_adapter().\r\n\r\nIf aac_init_adapter() fails after allocating memory for aac_dev::queues,\nit frees the memory but does not clear that member.\r\n\r\nAfter the hardware-specific init function returns an error,\naac_probe_one() goes down an error path that frees the memory pointed to\nby aac_dev::queues, resulting.in a double-free.(CVE-2024-46673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: st: fix probed platform device ref count on probe error path\r\n\r\nThe probe function never performs any paltform device allocation, thus\nerror path \u0026quot;undo_platform_dev_alloc\u0026quot; is entirely bogus.  It drops the\nreference count from the platform device being probed.  If error path is\ntriggered, this will lead to unbalanced device reference counts and\npremature release of device resources, thus possible use-after-free when\nreleasing remaining devm-managed resources.(CVE-2024-46674)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\napparmor: fix possible NULL pointer dereference\r\n\r\nprofile-\u0026gt;parent-\u0026gt;dents[AAFS_PROF_DIR] could be NULL only if its parent is made\nfrom __create_missing_ancestors(..) and \u0026apos;ent-\u0026gt;old\u0026apos; is NULL in\naa_replace_profiles(..).\nIn that case, it must return an error code and the code, -ENOENT represents\nits state that the path of its parent is not existed yet.\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000030\nPGD 0 P4D 0\nPREEMPT SMP PTI\nCPU: 4 PID: 3362 Comm: apparmor_parser Not tainted 6.8.0-24-generic #24\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\nRIP: 0010:aafs_create.constprop.0+0x7f/0x130\nCode: 4c 63 e0 48 83 c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 c3 cc cc cc cc \u0026lt;4d\u0026gt; 8b 55 30 4d 8d ba a0 00 00 00 4c 89 55 c0 4c 89 ff e8 7a 6a ae\nRSP: 0018:ffffc9000b2c7c98 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: 00000000000041ed RCX: 0000000000000000\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\nRBP: ffffc9000b2c7cd8 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: ffffffff82baac10\nR13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\nFS:  00007be9f22cf740(0000) GS:ffff88817bc00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000030 CR3: 0000000134b08000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? show_regs+0x6d/0x80\n ? __die+0x24/0x80\n ? page_fault_oops+0x99/0x1b0\n ? kernelmode_fixup_or_oops+0xb2/0x140\n ? __bad_area_nosemaphore+0x1a5/0x2c0\n ? find_vma+0x34/0x60\n ? bad_area_nosemaphore+0x16/0x30\n ? do_user_addr_fault+0x2a2/0x6b0\n ? exc_page_fault+0x83/0x1b0\n ? asm_exc_page_fault+0x27/0x30\n ? aafs_create.constprop.0+0x7f/0x130\n ? aafs_create.constprop.0+0x51/0x130\n __aafs_profile_mkdir+0x3d6/0x480\n aa_replace_profiles+0x83f/0x1270\n policy_update+0xe3/0x180\n profile_load+0xbc/0x150\n ? rw_verify_area+0x47/0x140\n vfs_write+0x100/0x480\n ? __x64_sys_openat+0x55/0xa0\n ? syscall_exit_to_user_mode+0x86/0x260\n ksys_write+0x73/0x100\n __x64_sys_write+0x19/0x30\n x64_sys_call+0x7e/0x25c0\n do_syscall_64+0x7f/0x180\n entry_SYSCALL_64_after_hwframe+0x78/0x80\nRIP: 0033:0x7be9f211c574\nCode: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d d5 ea 0e 00 00 74 13 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89\nRSP: 002b:00007ffd26f2b8c8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 00005d504415e200 RCX: 00007be9f211c574\nRDX: 0000000000001fc1 RSI: 00005d504418bc80 RDI: 0000000000000004\nRBP: 0000000000001fc1 R08: 0000000000001fc1 R09: 0000000080000000\nR10: 0000000000000000 R11: 0000000000000202 R12: 00005d504418bc80\nR13: 0000000000000004 R14: 00007ffd26f2b9b0 R15: 00007ffd26f2ba30\n \u0026lt;/TASK\u0026gt;\nModules linked in: snd_seq_dummy snd_hrtimer qrtr snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device i2c_i801 snd_timer i2c_smbus qxl snd soundcore drm_ttm_helper lpc_ich ttm joydev input_leds serio_raw mac_hid binfmt_misc msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 hid_generic usbhid hid ahci libahci psmouse virtio_rng xhci_pci xhci_pci_renesas\nCR2: 0000000000000030\n---[ end trace 0000000000000000 ]---\nRIP: 0010:aafs_create.constprop.0+0x7f/0x130\nCode: 4c 63 e0 48 83 c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 c3 cc cc cc cc \u0026lt;4d\u0026gt; 8b 55 30 4d 8d ba a0 00 00 00 4c 89 55 c0 4c 89 ff e8 7a 6a ae\nRSP: 0018:ffffc9000b2c7c98 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: 00000000000041ed RCX: 0000000000000000\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\nRBP: ffffc9000b2c7cd8 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000\n---truncated---(CVE-2024-46721)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nVMCI: Fix use-after-free when removing resource in vmci_resource_remove()\r\n\r\nWhen removing a resource from vmci_resource_table in\nvmci_resource_remove(), the search is performed using the resource\nhandle by comparing context and resource fields.\r\n\r\nIt is possible though to create two resources with different types\nbut same handle (same context and resource fields).\r\n\r\nWhen trying to remove one of the resources, vmci_resource_remove()\nmay not remove the intended one, but the object will still be freed\nas in the case of the datagram type in vmci_datagram_destroy_handle().\nvmci_resource_table will still hold a pointer to this freed resource\nleading to a use-after-free vulnerability.\r\n\r\nBUG: KASAN: use-after-free in vmci_handle_is_equal include/linux/vmw_vmci_defs.h:142 [inline]\nBUG: KASAN: use-after-free in vmci_resource_remove+0x3a1/0x410 drivers/misc/vmw_vmci/vmci_resource.c:147\nRead of size 4 at addr ffff88801c16d800 by task syz-executor197/1592\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x82/0xa9 lib/dump_stack.c:106\n print_address_description.constprop.0+0x21/0x366 mm/kasan/report.c:239\n __kasan_report.cold+0x7f/0x132 mm/kasan/report.c:425\n kasan_report+0x38/0x51 mm/kasan/report.c:442\n vmci_handle_is_equal include/linux/vmw_vmci_defs.h:142 [inline]\n vmci_resource_remove+0x3a1/0x410 drivers/misc/vmw_vmci/vmci_resource.c:147\n vmci_qp_broker_detach+0x89a/0x11b9 drivers/misc/vmw_vmci/vmci_queue_pair.c:2182\n ctx_free_ctx+0x473/0xbe1 drivers/misc/vmw_vmci/vmci_context.c:444\n kref_put include/linux/kref.h:65 [inline]\n vmci_ctx_put drivers/misc/vmw_vmci/vmci_context.c:497 [inline]\n vmci_ctx_destroy+0x170/0x1d6 drivers/misc/vmw_vmci/vmci_context.c:195\n vmci_host_close+0x125/0x1ac drivers/misc/vmw_vmci/vmci_host.c:143\n __fput+0x261/0xa34 fs/file_table.c:282\n task_work_run+0xf0/0x194 kernel/task_work.c:164\n tracehook_notify_resume include/linux/tracehook.h:189 [inline]\n exit_to_user_mode_loop+0x184/0x189 kernel/entry/common.c:187\n exit_to_user_mode_prepare+0x11b/0x123 kernel/entry/common.c:220\n __syscall_exit_to_user_mode_work kernel/entry/common.c:302 [inline]\n syscall_exit_to_user_mode+0x18/0x42 kernel/entry/common.c:313\n do_syscall_64+0x41/0x85 arch/x86/entry/common.c:86\n entry_SYSCALL_64_after_hwframe+0x6e/0x0\r\n\r\nThis change ensures the type is also checked when removing\nthe resource from vmci_resource_table in vmci_resource_remove().(CVE-2024-46738)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind\r\n\r\nFor primary VM Bus channels, primary_channel pointer is always NULL. This\npointer is valid only for the secondary channels. Also, rescind callback\nis meant for primary channels only.\r\n\r\nFix NULL pointer dereference by retrieving the device_obj from the parent\nfor the primary channel.(CVE-2024-46739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbinder: fix UAF caused by offsets overwrite\r\n\r\nBinder objects are processed and copied individually into the target\nbuffer during transactions. Any raw data in-between these objects is\ncopied as well. However, this raw data copy lacks an out-of-bounds\ncheck. If the raw data exceeds the data section size then the copy\noverwrites the offsets section. This eventually triggers an error that\nattempts to unwind the processed objects. However, at this point the\noffsets used to index these objects are now corrupted.\r\n\r\nUnwinding with corrupted offsets can result in decrements of arbitrary\nnodes and lead to their premature release. Other users of such nodes are\nleft with a dangling pointer triggering a use-after-free. This issue is\nmade evident by the following KASAN report (trimmed):\r\n\r\n  ==================================================================\n  BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x19c\n  Write of size 4 at addr ffff47fc91598f04 by task binder-util/743\r\n\r\n  CPU: 9 UID: 0 PID: 743 Comm: binder-util Not tainted 6.11.0-rc4 #1\n  Hardware name: linux,dummy-virt (DT)\n  Call trace:\n   _raw_spin_lock+0xe4/0x19c\n   binder_free_buf+0x128/0x434\n   binder_thread_write+0x8a4/0x3260\n   binder_ioctl+0x18f0/0x258c\n  [...]\r\n\r\n  Allocated by task 743:\n   __kmalloc_cache_noprof+0x110/0x270\n   binder_new_node+0x50/0x700\n   binder_transaction+0x413c/0x6da8\n   binder_thread_write+0x978/0x3260\n   binder_ioctl+0x18f0/0x258c\n  [...]\r\n\r\n  Freed by task 745:\n   kfree+0xbc/0x208\n   binder_thread_read+0x1c5c/0x37d4\n   binder_ioctl+0x16d8/0x258c\n  [...]\n  ==================================================================\r\n\r\nTo avoid this issue, let\u0026apos;s check that the raw data copy is within the\nboundaries of the data section.(CVE-2024-46740)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: Add missing bridge lock to pci_bus_lock()\r\n\r\nOne of the true positives that the cfg_access_lock lockdep effort\nidentified is this sequence:\r\n\r\n  WARNING: CPU: 14 PID: 1 at drivers/pci/pci.c:4886 pci_bridge_secondary_bus_reset+0x5d/0x70\n  RIP: 0010:pci_bridge_secondary_bus_reset+0x5d/0x70\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ? __warn+0x8c/0x190\n   ? pci_bridge_secondary_bus_reset+0x5d/0x70\n   ? report_bug+0x1f8/0x200\n   ? handle_bug+0x3c/0x70\n   ? exc_invalid_op+0x18/0x70\n   ? asm_exc_invalid_op+0x1a/0x20\n   ? pci_bridge_secondary_bus_reset+0x5d/0x70\n   pci_reset_bus+0x1d8/0x270\n   vmd_probe+0x778/0xa10\n   pci_device_probe+0x95/0x120\r\n\r\nWhere pci_reset_bus() users are triggering unlocked secondary bus resets.\nIronically pci_bus_reset(), several calls down from pci_reset_bus(), uses\npci_bus_lock() before issuing the reset which locks everything *but* the\nbridge itself.\r\n\r\nFor the same motivation as adding:\r\n\r\n  bridge = pci_upstream_bridge(dev);\n  if (bridge)\n    pci_dev_lock(bridge);\r\n\r\nto pci_reset_function() for the \u0026quot;bus\u0026quot; and \u0026quot;cxl_bus\u0026quot; reset cases, add\npci_dev_lock() for @bus-\u0026gt;self to pci_bus_lock().\r\n\r\n[bhelgaas: squash in recursive locking deadlock fix from Keith Busch:\nhttps://lore.kernel.org/r/20240711193650.701834-1-kbusch@meta.com](CVE-2024-46750)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (w83627ehf) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (lm95234) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46758)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npci/hotplug/pnv_php: Fix hotplug driver crash on Powernv\r\n\r\nThe hotplug driver for powerpc (pci/hotplug/pnv_php.c) causes a kernel\ncrash when we try to hot-unplug/disable the PCIe switch/bridge from\nthe PHB.\r\n\r\nThe crash occurs because although the MSI data structure has been\nreleased during disable/hot-unplug path and it has been assigned\nwith NULL, still during unregistration the code was again trying to\nexplicitly disable the MSI which causes the NULL pointer dereference and\nkernel crash.\r\n\r\nThe patch fixes the check during unregistration path to prevent invoking\npci_disable_msi/msix() since its data structure is already freed.(CVE-2024-46761)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncan: bcm: Remove proc entry when dev is unregistered.\r\n\r\nsyzkaller reported a warning in bcm_connect() below. [0]\r\n\r\nThe repro calls connect() to vxcan1, removes vxcan1, and calls\nconnect() with ifindex == 0.\r\n\r\nCalling connect() for a BCM socket allocates a proc entry.\nThen, bcm_sk(sk)-\u0026gt;bound is set to 1 to prevent further connect().\r\n\r\nHowever, removing the bound device resets bcm_sk(sk)-\u0026gt;bound to 0\nin bcm_notify().\r\n\r\nThe 2nd connect() tries to allocate a proc entry with the same\nname and sets NULL to bcm_sk(sk)-\u0026gt;bcm_proc_read, leaking the\noriginal proc entry.\r\n\r\nSince the proc entry is available only for connect()ed sockets,\nlet\u0026apos;s clean up the entry when the bound netdev is unregistered.\r\n\r\n[0]:\nproc_dir_entry \u0026apos;can-bcm/2456\u0026apos; already registered\nWARNING: CPU: 1 PID: 394 at fs/proc/generic.c:376 proc_register+0x645/0x8f0 fs/proc/generic.c:375\nModules linked in:\nCPU: 1 PID: 394 Comm: syz-executor403 Not tainted 6.10.0-rc7-g852e42cc2dd4\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:proc_register+0x645/0x8f0 fs/proc/generic.c:375\nCode: 00 00 00 00 00 48 85 ed 0f 85 97 02 00 00 4d 85 f6 0f 85 9f 02 00 00 48 c7 c7 9b cb cf 87 48 89 de 4c 89 fa e8 1c 6f eb fe 90 \u0026lt;0f\u0026gt; 0b 90 90 48 c7 c7 98 37 99 89 e8 cb 7e 22 05 bb 00 00 00 10 48\nRSP: 0018:ffa0000000cd7c30 EFLAGS: 00010246\nRAX: 9e129be1950f0200 RBX: ff1100011b51582c RCX: ff1100011857cd80\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002\nRBP: 0000000000000000 R08: ffd400000000000f R09: ff1100013e78cac0\nR10: ffac800000cd7980 R11: ff1100013e12b1f0 R12: 0000000000000000\nR13: 0000000000000000 R14: 0000000000000000 R15: ff1100011a99a2ec\nFS:  00007fbd7086f740(0000) GS:ff1100013fd00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000200071c0 CR3: 0000000118556004 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n proc_create_net_single+0x144/0x210 fs/proc/proc_net.c:220\n bcm_connect+0x472/0x840 net/can/bcm.c:1673\n __sys_connect_file net/socket.c:2049 [inline]\n __sys_connect+0x5d2/0x690 net/socket.c:2066\n __do_sys_connect net/socket.c:2076 [inline]\n __se_sys_connect net/socket.c:2073 [inline]\n __x64_sys_connect+0x8f/0x100 net/socket.c:2073\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd9/0x1c0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\nRIP: 0033:0x7fbd708b0e5d\nCode: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 9f 1b 00 f7 d8 64 89 01 48\nRSP: 002b:00007fff8cd33f08 EFLAGS: 00000246 ORIG_RAX: 000000000000002a\nRAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fbd708b0e5d\nRDX: 0000000000000010 RSI: 0000000020000040 RDI: 0000000000000003\nRBP: 0000000000000000 R08: 0000000000000040 R09: 0000000000000040\nR10: 0000000000000040 R11: 0000000000000246 R12: 00007fff8cd34098\nR13: 0000000000401280 R14: 0000000000406de8 R15: 00007fbd70ab9000\n \u0026lt;/TASK\u0026gt;\nremove_proc_entry: removing non-empty directory \u0026apos;net/can-bcm\u0026apos;, leaking at least \u0026apos;2456\u0026apos;(CVE-2024-46771)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudf: Avoid excessive partition lengths\r\n\r\nAvoid mounting filesystems where the partition would overflow the\n32-bits used for block number. Also refuse to mount filesystems where\nthe partition length is so large we cannot safely index bits in a\nblock bitmap.(CVE-2024-46777)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: protect references to superblock parameters exposed in sysfs\r\n\r\nThe superblock buffers of nilfs2 can not only be overwritten at runtime\nfor modifications/repairs, but they are also regularly swapped, replaced\nduring resizing, and even abandoned when degrading to one side due to\nbacking device issues.  So, accessing them requires mutual exclusion using\nthe reader/writer semaphore \u0026quot;nilfs-\u0026gt;ns_sem\u0026quot;.\r\n\r\nSome sysfs attribute show methods read this superblock buffer without the\nnecessary mutual exclusion, which can cause problems with pointer\ndereferencing and memory access, so fix it.(CVE-2024-46780)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix missing cleanup on rollforward recovery error\r\n\r\nIn an error injection test of a routine for mount-time recovery, KASAN\nfound a use-after-free bug.\r\n\r\nIt turned out that if data recovery was performed using partial logs\ncreated by dsync writes, but an error occurred before starting the log\nwriter to create a recovered checkpoint, the inodes whose data had been\nrecovered were left in the ns_dirty_files list of the nilfs object and\nwere not freed.\r\n\r\nFix this issue by cleaning up inodes that have read the recovery data if\nthe recovery routine fails midway before the log writer starts.(CVE-2024-46781)","status":"published","published":"2024-10-12T11:07:41Z","modified":"2026-08-18T01:17:34.226782885Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2367","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\ndrm/amd/display: Add NULL pointer check for kzalloc\r\n\r\n[Why \u0026amp; How]\nCheck return pointer of kzalloc before using it.(CVE-2024-42122)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm: gup: stop abusing try_grab_folio\r\n\r\nA kernel warning was reported when pinning folio in CMA memory when\nlaunching SEV virtual machine.  The splat looks like:\r\n\r\n[  464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520\n[  464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6\n[  464.325477] RIP: 0010:__get_user_pages+0x423/0x520\n[  464.325515] Call Trace:\n[  464.325520]  \u0026lt;TASK\u0026gt;\n[  464.325523]  ? __get_user_pages+0x423/0x520\n[  464.325528]  ? __warn+0x81/0x130\n[  464.325536]  ? __get_user_pages+0x423/0x520\n[  464.325541]  ? report_bug+0x171/0x1a0\n[  464.325549]  ? handle_bug+0x3c/0x70\n[  464.325554]  ? exc_invalid_op+0x17/0x70\n[  464.325558]  ? asm_exc_invalid_op+0x1a/0x20\n[  464.325567]  ? __get_user_pages+0x423/0x520\n[  464.325575]  __gup_longterm_locked+0x212/0x7a0\n[  464.325583]  internal_get_user_pages_fast+0xfb/0x190\n[  464.325590]  pin_user_pages_fast+0x47/0x60\n[  464.325598]  sev_pin_memory+0xca/0x170 [kvm_amd]\n[  464.325616]  sev_mem_enc_register_region+0x81/0x130 [kvm_amd]\r\n\r\nPer the analysis done by yangge, when starting the SEV virtual machine, it\nwill call pin_user_pages_fast(..., FOLL_LONGTERM, ...) to pin the memory. \nBut the page is in CMA area, so fast GUP will fail then fallback to the\nslow path due to the longterm pinnalbe check in try_grab_folio().\r\n\r\nThe slow path will try to pin the pages then migrate them out of CMA area.\nBut the slow path also uses try_grab_folio() to pin the page, it will\nalso fail due to the same check then the above warning is triggered.\r\n\r\nIn addition, the try_grab_folio() is supposed to be used in fast path and\nit elevates folio refcount by using add ref unless zero.  We are guaranteed\nto have at least one stable reference in slow path, so the simple atomic add\ncould be used.  The performance difference should be trivial, but the\nmisuse may be confusing and misleading.\r\n\r\nRedefined try_grab_folio() to try_grab_folio_fast(), and try_grab_page()\nto try_grab_folio(), and use them in the proper paths.  This solves both\nthe abuse and the kernel warning.\r\n\r\nThe proper naming makes their usecase more clear and should prevent from\nabusing in the future.\r\n\r\npeterx said:\r\n\r\n: The user will see the pin fails, for gpu-slow it further triggers the WARN\n: right below that failure (as in the original report):\n: \n:         folio = try_grab_folio(page, page_increm - 1,\n:                                 foll_flags);\n:         if (WARN_ON_ONCE(!folio)) { \u0026lt;------------------------ here\n:                 /*\n:                         * Release the 1st page ref if the\n:                         * folio is problematic, fail hard.\n:                         */\n:                 gup_put_folio(page_folio(page), 1,\n:                                 foll_flags);\n:                 ret = -EFAULT;\n:                 goto out;\n:         }\r\n\r\n[1] https://lore.kernel.org/linux-mm/1719478388-31917-1-git-send-email-yangge1116@126.com/\r\n\r\n[shy828301@gmail.com: fix implicit declaration of function try_grab_folio_fast]\n  Link: https://lkml.kernel.org/r/CAHbLzkowMSso-4Nufc9hcMehQsK9PNz3OSu-+eniU-2Mm-xjhA@mail.gmail.com(CVE-2024-44943)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: sc16is7xx: fix TX fifo corruption\r\n\r\nSometimes, when a packet is received on channel A at almost the same time\nas a packet is about to be transmitted on channel B, we observe with a\nlogic analyzer that the received packet on channel A is transmitted on\nchannel B. In other words, the Tx buffer data on channel B is corrupted\nwith data from channel A.\r\n\r\nThe problem appeared since commit 4409df5866b7 (\u0026quot;serial: sc16is7xx: change\nEFR lock to operate on each channels\u0026quot;), which changed the EFR locking to\noperate on each channel instead of chip-wise.\r\n\r\nThis commit has introduced a regression, because the EFR lock is used not\nonly to protect the EFR registers access, but also, in a very obscure and\nundocumented way, to protect access to the data buffer, which is shared by\nthe Tx and Rx handlers, but also by each channel of the IC.\r\n\r\nFix this regression first by switching to kfifo_out_linear_ptr() in\nsc16is7xx_handle_tx() to eliminate the need for a shared Rx/Tx buffer.\r\n\r\nSecondly, replace the chip-wise Rx buffer with a separate Rx buffer for\neach channel.(CVE-2024-44951)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npinctrl: single: fix potential NULL dereference in pcs_get_function()\r\n\r\npinmux_generic_get_function() can return NULL and the pointer \u0026apos;function\u0026apos;\nwas dereferenced without checking against NULL. Add checking of pointer\n\u0026apos;function\u0026apos; in pcs_get_function().\r\n\r\nFound by code review.(CVE-2024-46685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nthunderbolt: Mark XDomain as unplugged when router is removed\r\n\r\nI noticed that when we do discrete host router NVM upgrade and it gets\nhot-removed from the PCIe side as a result of NVM firmware authentication,\nif there is another host connected with enabled paths we hang in tearing\nthem down. This is due to fact that the Thunderbolt networking driver\nalso tries to cleanup the paths and ends up blocking in\ntb_disconnect_xdomain_paths() waiting for the domain lock.\r\n\r\nHowever, at this point we already cleaned the paths in tb_stop() so\nthere is really no need for tb_disconnect_xdomain_paths() to do that\nanymore. Furthermore it already checks if the XDomain is unplugged and\nbails out early so take advantage of that and mark the XDomain as\nunplugged when we remove the parent router.(CVE-2024-46702)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery()\r\n\r\nWhen two UBLK_CMD_START_USER_RECOVERY commands are submitted, the\nfirst one sets \u0026apos;ubq-\u0026gt;ubq_daemon\u0026apos; to NULL, and the second one triggers\nWARN in ublk_queue_reinit() and subsequently a NULL pointer dereference\nissue.\r\n\r\nFix it by adding the check in ublk_ctrl_start_recovery() and return\nimmediately in case of zero \u0026apos;ub-\u0026gt;nr_queues_ready\u0026apos;.\r\n\r\n  BUG: kernel NULL pointer dereference, address: 0000000000000028\n  RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ? __die+0x20/0x70\n   ? page_fault_oops+0x75/0x170\n   ? exc_page_fault+0x64/0x140\n   ? asm_exc_page_fault+0x22/0x30\n   ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180\n   ublk_ctrl_uring_cmd+0x4f7/0x6c0\n   ? pick_next_task_idle+0x26/0x40\n   io_uring_cmd+0x9a/0x1b0\n   io_issue_sqe+0x193/0x3f0\n   io_wq_submit_work+0x9b/0x390\n   io_worker_handle_work+0x165/0x360\n   io_wq_worker+0xcb/0x2f0\n   ? finish_task_switch.isra.0+0x203/0x290\n   ? finish_task_switch.isra.0+0x203/0x290\n   ? __pfx_io_wq_worker+0x10/0x10\n   ret_from_fork+0x2d/0x50\n   ? __pfx_io_wq_worker+0x10/0x10\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;(CVE-2024-46735)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof/irq: Prevent device address out-of-bounds read in interrupt map walk\r\n\r\nWhen of_irq_parse_raw() is invoked with a device address smaller than\nthe interrupt parent node (from #address-cells property), KASAN detects\nthe following out-of-bounds read when populating the initial match table\n(dyndbg=\u0026quot;func of_irq_parse_* +p\u0026quot;):\r\n\r\n  OF: of_irq_parse_one: dev=/soc@0/picasso/watchdog, index=0\n  OF:  parent=/soc@0/pci@878000000000/gpio0@17,0, intsize=2\n  OF:  intspec=4\n  OF: of_irq_parse_raw: ipar=/soc@0/pci@878000000000/gpio0@17,0, size=2\n  OF:  -\u0026gt; addrsize=3\n  ==================================================================\n  BUG: KASAN: slab-out-of-bounds in of_irq_parse_raw+0x2b8/0x8d0\n  Read of size 4 at addr ffffff81beca5608 by task bash/764\r\n\r\n  CPU: 1 PID: 764 Comm: bash Tainted: G           O       6.1.67-484c613561-nokia_sm_arm64 #1\n  Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2023.01-12.24.03-dirty 01/01/2023\n  Call trace:\n   dump_backtrace+0xdc/0x130\n   show_stack+0x1c/0x30\n   dump_stack_lvl+0x6c/0x84\n   print_report+0x150/0x448\n   kasan_report+0x98/0x140\n   __asan_load4+0x78/0xa0\n   of_irq_parse_raw+0x2b8/0x8d0\n   of_irq_parse_one+0x24c/0x270\n   parse_interrupts+0xc0/0x120\n   of_fwnode_add_links+0x100/0x2d0\n   fw_devlink_parse_fwtree+0x64/0xc0\n   device_add+0xb38/0xc30\n   of_device_add+0x64/0x90\n   of_platform_device_create_pdata+0xd0/0x170\n   of_platform_bus_create+0x244/0x600\n   of_platform_notify+0x1b0/0x254\n   blocking_notifier_call_chain+0x9c/0xd0\n   __of_changeset_entry_notify+0x1b8/0x230\n   __of_changeset_apply_notify+0x54/0xe4\n   of_overlay_fdt_apply+0xc04/0xd94\n   ...\r\n\r\n  The buggy address belongs to the object at ffffff81beca5600\n   which belongs to the cache kmalloc-128 of size 128\n  The buggy address is located 8 bytes inside of\n   128-byte region [ffffff81beca5600, ffffff81beca5680)\r\n\r\n  The buggy address belongs to the physical page:\n  page:00000000230d3d03 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1beca4\n  head:00000000230d3d03 order:1 compound_mapcount:0 compound_pincount:0\n  flags: 0x8000000000010200(slab|head|zone=2)\n  raw: 8000000000010200 0000000000000000 dead000000000122 ffffff810000c300\n  raw: 0000000000000000 0000000000200020 00000001ffffffff 0000000000000000\n  page dumped because: kasan: bad access detected\r\n\r\n  Memory state around the buggy address:\n   ffffff81beca5500: 04 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n   ffffff81beca5580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffffff81beca5600: 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n                        ^\n   ffffff81beca5680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n   ffffff81beca5700: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc\n  ==================================================================\n  OF:  -\u0026gt; got it !\r\n\r\nPrevent the out-of-bounds read by copying the device address into a\nbuffer of sufficient size.(CVE-2024-46743)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]\r\n\r\n[WHY \u0026amp; HOW]\nnum_valid_sets needs to be checked to avoid a negative index when\naccessing reader_wm_sets[num_valid_sets - 1].\r\n\r\nThis fixes an OVERRUN issue reported by Coverity.(CVE-2024-46815)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommufd: Require drivers to supply the cache_invalidate_user ops\r\n\r\nIf drivers don\u0026apos;t do this then iommufd will oops invalidation ioctls with\nsomething like:\r\n\r\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n  Mem abort info:\n    ESR = 0x0000000086000004\n    EC = 0x21: IABT (current EL), IL = 32 bits\n    SET = 0, FnV = 0\n    EA = 0, S1PTW = 0\n    FSC = 0x04: level 0 translation fault\n  user pgtable: 4k pages, 48-bit VAs, pgdp=0000000101059000\n  [0000000000000000] pgd=0000000000000000, p4d=0000000000000000\n  Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 2 PID: 371 Comm: qemu-system-aar Not tainted 6.8.0-rc7-gde77230ac23a #9\n  Hardware name: linux,dummy-virt (DT)\n  pstate: 81400809 (Nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=-c)\n  pc : 0x0\n  lr : iommufd_hwpt_invalidate+0xa4/0x204\n  sp : ffff800080f3bcc0\n  x29: ffff800080f3bcf0 x28: ffff0000c369b300 x27: 0000000000000000\n  x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000\n  x23: 0000000000000000 x22: 00000000c1e334a0 x21: ffff0000c1e334a0\n  x20: ffff800080f3bd38 x19: ffff800080f3bd58 x18: 0000000000000000\n  x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff8240d6d8\n  x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000\n  x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000\n  x8 : 0000001000000002 x7 : 0000fffeac1ec950 x6 : 0000000000000000\n  x5 : ffff800080f3bd78 x4 : 0000000000000003 x3 : 0000000000000002\n  x2 : 0000000000000000 x1 : ffff800080f3bcc8 x0 : ffff0000c6034d80\n  Call trace:\n   0x0\n   iommufd_fops_ioctl+0x154/0x274\n   __arm64_sys_ioctl+0xac/0xf0\n   invoke_syscall+0x48/0x110\n   el0_svc_common.constprop.0+0x40/0xe0\n   do_el0_svc+0x1c/0x28\n   el0_svc+0x34/0xb4\n   el0t_64_sync_handler+0x120/0x12c\n   el0t_64_sync+0x190/0x194\r\n\r\nAll existing drivers implement this op for nesting, this is mostly a\nbisection aid.(CVE-2024-46824)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: microchip: vcap: Fix use-after-free error in kunit test\r\n\r\nThis is a clear use-after-free error. We remove it, and rely on checking\nthe return code of vcap_del_rule.(CVE-2024-46831)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vfs: fix race between evice_inodes() and find_inode()\u0026amp;iput()  Hi, all  Recently I noticed a bug[1] in btrfs, after digged it into and I believe it\u0026apos;a race in vfs.  Let\u0026apos;s assume there\u0026apos;s a inode (ie ino 261) with i_count 1 is called by iput(), and there\u0026apos;s a concurrent thread calling generic_shutdown_super().  cpu0:                              cpu1: iput() // i_count is 1   -\u0026gt;spin_lock(inode)   -\u0026gt;dec i_count to 0   -\u0026gt;iput_final()                    generic_shutdown_super()     -\u0026gt;__inode_add_lru()               -\u0026gt;evict_inodes()       // cause some reason[2]           -\u0026gt;if (atomic_read(inode-\u0026gt;i_count)) continue;       // return before                  // inode 261 passed the above check       // list_lru_add_obj()             // and then schedule out    -\u0026gt;spin_unlock() // note here: the inode 261 // was still at sb list and hash list, // and I_FREEING|I_WILL_FREE was not been set  btrfs_iget()   // after some function calls   -\u0026gt;find_inode()     // found the above inode 261     -\u0026gt;spin_lock(inode)    // check I_FREEING|I_WILL_FREE    // and passed       -\u0026gt;__iget()     -\u0026gt;spin_unlock(inode)                // schedule back                                         -\u0026gt;spin_lock(inode)                                         // check (I_NEW|I_FREEING|I_WILL_FREE) flags,                                         // passed and set I_FREEING iput()                                  -\u0026gt;spin_unlock(inode)   -\u0026gt;spin_lock(inode)     -\u0026gt;evict()   // dec i_count to 0   -\u0026gt;iput_final()     -\u0026gt;spin_unlock()     -\u0026gt;evict()  Now, we have two threads simultaneously evicting the same inode, which may trigger the BUG(inode-\u0026gt;i_state \u0026amp; I_CLEAR) statement both within clear_inode() and iput().  To fix the bug, recheck the inode-\u0026gt;i_count after holding i_lock. Because in the most scenarios, the first check is valid, and the overhead of spin_lock() can be reduced.  If there is any misunderstanding, please let me know, thanks.  [1]: https://lore.kernel.org/linux-btrfs/000000000000eabe1d0619c48986@google.com/ [2]: The reason might be 1. SB_ACTIVE was removed or 2. mapping_shrinkable() return false when I reproduced the bug.(CVE-2024-47679)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate()  The psc-\u0026gt;div[] array has psc-\u0026gt;num_div elements.  These values come from when we call clk_hw_register_div().  It\u0026apos;s adc_divisors and ARRAY_SIZE(adc_divisors)) and so on.  So this condition needs to be \u0026gt;= instead of \u0026gt; to prevent an out of bounds read.(CVE-2024-47686)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  driver core: Fix a potential null-ptr-deref in module_add_driver()  Inject fault while probing of-fpga-region, if kasprintf() fails in module_add_driver(), the second sysfs_remove_link() in exit path will cause null-ptr-deref as below because kernfs_name_hash() will call strlen() with NULL driver_name.  Fix it by releasing resources based on the exit path sequence.    KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]   Mem abort info:     ESR = 0x0000000096000005     EC = 0x25: DABT (current EL), IL = 32 bits     SET = 0, FnV = 0     EA = 0, S1PTW = 0     FSC = 0x05: level 1 translation fault   Data abort info:     ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000     CM = 0, WnR = 0, TnD = 0, TagAccess = 0     GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0   [dfffffc000000000] address between user and kernel address ranges   Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP   Dumping ftrace buffer:      (ftrace buffer empty)   Modules linked in: of_fpga_region(+) fpga_region fpga_bridge cfg80211 rfkill 8021q garp mrp stp llc ipv6 [last unloaded: of_fpga_region]   CPU: 2 UID: 0 PID: 2036 Comm: modprobe Not tainted 6.11.0-rc2-g6a0e38264012 #295   Hardware name: linux,dummy-virt (DT)   pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)   pc : strlen+0x24/0xb0   lr : kernfs_name_hash+0x1c/0xc4   sp : ffffffc081f97380   x29: ffffffc081f97380 x28: ffffffc081f97b90 x27: ffffff80c821c2a0   x26: ffffffedac0be418 x25: 0000000000000000 x24: ffffff80c09d2000   x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000   x20: 0000000000000000 x19: 0000000000000000 x18: 0000000000001840   x17: 0000000000000000 x16: 0000000000000000 x15: 1ffffff8103f2e42   x14: 00000000f1f1f1f1 x13: 0000000000000004 x12: ffffffb01812d61d   x11: 1ffffff01812d61c x10: ffffffb01812d61c x9 : dfffffc000000000   x8 : 0000004fe7ed29e4 x7 : ffffff80c096b0e7 x6 : 0000000000000001   x5 : ffffff80c096b0e0 x4 : 1ffffffdb990efa2 x3 : 0000000000000000   x2 : 0000000000000000 x1 : dfffffc000000000 x0 : 0000000000000000   Call trace:    strlen+0x24/0xb0    kernfs_name_hash+0x1c/0xc4    kernfs_find_ns+0x118/0x2e8    kernfs_remove_by_name_ns+0x80/0x100    sysfs_remove_link+0x74/0xa8    module_add_driver+0x278/0x394    bus_add_driver+0x1f0/0x43c    driver_register+0xf4/0x3c0    __platform_driver_register+0x60/0x88    of_fpga_region_init+0x20/0x1000 [of_fpga_region]    do_one_initcall+0x110/0x788    do_init_module+0x1dc/0x5c8    load_module+0x3c38/0x4cac    init_module_from_file+0xd4/0x128    idempotent_init_module+0x2cc/0x528    __arm64_sys_finit_module+0xac/0x100    invoke_syscall+0x6c/0x258    el0_svc_common.constprop.0+0x160/0x22c    do_el0_svc+0x44/0x5c    el0_svc+0x48/0xb8    el0t_64_sync_handler+0x13c/0x158    el0t_64_sync+0x190/0x194   Code: f2fbffe1 a90157f4 12000802 aa0003f5 (38e16861)   ---[ end trace 0000000000000000 ]---   Kernel panic - not syncing: Oops: Fatal exception(CVE-2024-47688)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: check stripe size compatibility on remount as well  We disable stripe size in __ext4_fill_super if it is not a multiple of the cluster ratio however this check is missed when trying to remount. This can leave us with cases where stripe \u0026lt; cluster_ratio after remount:set making EXT4_B2C(sbi-\u0026gt;s_stripe) become 0 that can cause some unforeseen bugs like divide by 0.  Fix that by adding the check in remount path as well.(CVE-2024-47700)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check link_res-\u0026gt;hpo_dp_link_enc before using it  [WHAT \u0026amp; HOW] Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res without initializing hpo_dp_link_enc and it is necessary to check for null before dereferencing.  This fixes 2 FORWARD_NULL issues reported by Coverity.(CVE-2024-47704)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iommufd: Protect against overflow of ALIGN() during iova allocation  Userspace can supply an iova and uptr such that the target iova alignment becomes really big and ALIGN() overflows which corrupts the selected area range during allocation. CONFIG_IOMMUFD_TEST can detect this:     WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline]    WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352    Modules linked in:    CPU: 1 PID: 5092 Comm: syz-executor294 Not tainted 6.10.0-rc5-syzkaller-00294-g3ffea9a7a6f7 #0    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024    RIP: 0010:iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline]    RIP: 0010:iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352    Code: fc e9 a4 f3 ff ff e8 1a 8b 4c fc 41 be e4 ff ff ff e9 8a f3 ff ff e8 0a 8b 4c fc 90 0f 0b 90 e9 37 f5 ff ff e8 fc 8a 4c fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 68 f3 ff ff 48 c7 c1 ec 82 ad 8f 80 e1 07 80 c1 03 38    RSP: 0018:ffffc90003ebf9e0 EFLAGS: 00010293    RAX: ffffffff85499fa4 RBX: 00000000ffffffef RCX: ffff888079b49e00    RDX: 0000000000000000 RSI: 00000000ffffffef RDI: 0000000000000000    RBP: ffffc90003ebfc50 R08: ffffffff85499b30 R09: ffffffff85499942    R10: 0000000000000002 R11: ffff888079b49e00 R12: ffff8880228e0010    R13: 0000000000000000 R14: 1ffff920007d7f68 R15: ffffc90003ebfd00    FS:  000055557d760380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033    CR2: 00000000005fdeb8 CR3: 000000007404a000 CR4: 00000000003506f0    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400    Call Trace:     \u0026lt;TASK\u0026gt;     iommufd_ioas_copy+0x610/0x7b0 drivers/iommu/iommufd/ioas.c:274     iommufd_fops_ioctl+0x4d9/0x5a0 drivers/iommu/iommufd/main.c:421     vfs_ioctl fs/ioctl.c:51 [inline]     __do_sys_ioctl fs/ioctl.c:907 [inline]     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893     do_syscall_x64 arch/x86/entry/common.c:52 [inline]     do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83     entry_SYSCALL_64_after_hwframe+0x77/0x7f  Cap the automatic alignment to the huge page size, which is probably a better idea overall. Huge automatic alignments can fragment and chew up the available IOVA space without any reason.(CVE-2024-47719)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/tdx: Fix \u0026quot;in-kernel MMIO\u0026quot; check  TDX only supports kernel-initiated MMIO operations. The handle_mmio() function checks if the #VE exception occurred in the kernel and rejects the operation if it did not.  However, userspace can deceive the kernel into performing MMIO on its behalf. For example, if userspace can point a syscall to an MMIO address, syscall does get_user() or put_user() on it, triggering MMIO #VE. The kernel will treat the #VE as in-kernel MMIO.  Ensure that the target MMIO address is within the kernel before decoding instruction.(CVE-2024-47727)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock  Use a dedicated mutex to guard kvm_usage_count to fix a potential deadlock on x86 due to a chain of locks and SRCU synchronizations.  Translating the below lockdep splat, CPU1 #6 will wait on CPU0 #1, CPU0 #8 will wait on CPU2 #3, and CPU2 #7 will wait on CPU1 #4 (if there\u0026apos;s a writer, due to the fairness of r/w semaphores).      CPU0                     CPU1                     CPU2 1   lock(\u0026amp;kvm-\u0026gt;slots_lock); 2                                                     lock(\u0026amp;vcpu-\u0026gt;mutex); 3                                                     lock(\u0026amp;kvm-\u0026gt;srcu); 4                            lock(cpu_hotplug_lock); 5                            lock(kvm_lock); 6                            lock(\u0026amp;kvm-\u0026gt;slots_lock); 7                                                     lock(cpu_hotplug_lock); 8   sync(\u0026amp;kvm-\u0026gt;srcu);  Note, there are likely more potential deadlocks in KVM x86, e.g. the same pattern of taking cpu_hotplug_lock outside of kvm_lock likely exists with __kvmclock_cpufreq_notifier():    cpuhp_cpufreq_online()   |   -\u0026gt; cpufreq_online()      |      -\u0026gt; cpufreq_gov_performance_limits()         |         -\u0026gt; __cpufreq_driver_target()            |            -\u0026gt; __target_index()               |               -\u0026gt; cpufreq_freq_transition_begin()                  |                  -\u0026gt; cpufreq_notify_transition()                     |                     -\u0026gt; ... __kvmclock_cpufreq_notifier()  But, actually triggering such deadlocks is beyond rare due to the combination of dependencies and timings involved.  E.g. the cpufreq notifier is only used on older CPUs without a constant TSC, mucking with the NX hugepage mitigation while VMs are running is very uncommon, and doing so while also onlining/offlining a CPU (necessary to generate contention on cpu_hotplug_lock) would be even more unusual.  The most robust solution to the general cpu_hotplug_lock issue is likely to switch vm_list to be an RCU-protected list, e.g. so that x86\u0026apos;s cpufreq notifier doesn\u0026apos;t to take kvm_lock.  For now, settle for fixing the most blatant deadlock, as switching to an RCU-protected list is a much more involved change, but add a comment in locking.rst to call out that care needs to be taken when walking holding kvm_lock and walking vm_list.    ======================================================   WARNING: possible circular locking dependency detected   6.10.0-smp--c257535a0c9d-pip #330 Tainted: G S         O   ------------------------------------------------------   tee/35048 is trying to acquire lock:   ff6a80eced71e0a8 (\u0026amp;kvm-\u0026gt;slots_lock){+.+.}-{3:3}, at: set_nx_huge_pages+0x179/0x1e0 [kvm]    but task is already holding lock:   ffffffffc07abb08 (kvm_lock){+.+.}-{3:3}, at: set_nx_huge_pages+0x14a/0x1e0 [kvm]    which lock already depends on the new lock.     the existing dependency chain (in reverse order) is:    -\u0026gt; #3 (kvm_lock){+.+.}-{3:3}:          __mutex_lock+0x6a/0xb40          mutex_lock_nested+0x1f/0x30          kvm_dev_ioctl+0x4fb/0xe50 [kvm]          __se_sys_ioctl+0x7b/0xd0          __x64_sys_ioctl+0x21/0x30          x64_sys_call+0x15d0/0x2e60          do_syscall_64+0x83/0x160          entry_SYSCALL_64_after_hwframe+0x76/0x7e    -\u0026gt; #2 (cpu_hotplug_lock){++++}-{0:0}:          cpus_read_lock+0x2e/0xb0          static_key_slow_inc+0x16/0x30          kvm_lapic_set_base+0x6a/0x1c0 [kvm]          kvm_set_apic_base+0x8f/0xe0 [kvm]          kvm_set_msr_common+0x9ae/0xf80 [kvm]          vmx_set_msr+0xa54/0xbe0 [kvm_intel]          __kvm_set_msr+0xb6/0x1a0 [kvm]          kvm_arch_vcpu_ioctl+0xeca/0x10c0 [kvm]          kvm_vcpu_ioctl+0x485/0x5b0 [kvm]          __se_sys_ioctl+0x7b/0xd0          __x64_sys_ioctl+0x21/0x30          x64_sys_call+0x15d0/0x2e60          do_syscall_64+0x83/0x160          entry_SYSCALL_64_after_hwframe+0x76/0x7e    -\u0026gt; #1 (\u0026amp;kvm-\u0026gt;srcu){.+.+}-{0:0}:          __synchronize_srcu+0x44/0x1a0        ---truncated---(CVE-2024-47744)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port()  Within kirin_pcie_parse_port(), the pcie-\u0026gt;num_slots is compared to pcie-\u0026gt;gpio_id_reset size (MAX_PCI_SLOTS) which is correct and would lead to an overflow.  Thus, fix condition to pcie-\u0026gt;num_slots + 1 \u0026gt;= MAX_PCI_SLOTS and move pcie-\u0026gt;num_slots increment below the if-statement to avoid out-of-bounds array access.  Found by Linux Verification Center (linuxtesting.org) with SVACE.  [kwilczynski: commit log](CVE-2024-47751)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: mediatek: vcodec: Fix H264 stateless decoder smatch warning  Fix a smatch static checker warning on vdec_h264_req_if.c. Which leads to a kernel crash when fb is NULL.(CVE-2024-47752)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: mediatek: vcodec: Fix VP8 stateless decoder smatch warning  Fix a smatch static checker warning on vdec_vp8_req_if.c. Which leads to a kernel crash when fb is NULL.(CVE-2024-47753)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos  In case of malformed relocation record of kind BPF_CORE_TYPE_ID_LOCAL referencing a non-existing BTF type, function bpf_core_calc_relo_insn would cause a null pointer deference.  Fix this by adding a proper check upper in call stack, as malformed relocation records could be passed from user space.  Simplest reproducer is a program:      r0 = 0     exit  With a single relocation record:      .insn_off = 0,          /* patch first instruction */     .type_id = 100500,      /* this type id does not exist */     .access_str_off = 6,    /* offset of string \u0026quot;0\u0026quot; */     .kind = BPF_CORE_TYPE_ID_LOCAL,  See the link for original reproducer or next commit for a test case.(CVE-2024-49850)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: elx: libefc: Fix potential use after free in efc_nport_vport_del()  The kref_put() function will call nport-\u0026gt;release if the refcount drops to zero.  The nport-\u0026gt;release release function is _efc_nport_free() which frees \u0026quot;nport\u0026quot;.  But then we dereference \u0026quot;nport\u0026quot; on the next line which is a use after free.  Re-order these lines to avoid the use after free.(CVE-2024-49852)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to check atomic_file in f2fs ioctl interfaces  Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  powercap: intel_rapl: Fix off by one in get_rpi()  The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements.  Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cachefiles: fix dentry leak in cachefiles_open_file()  A dentry leak may be caused when a lookup cookie and a cull are concurrent:              P1             |             P2 ----------------------------------------------------------- cachefiles_lookup_cookie   cachefiles_look_up_object     lookup_one_positive_unlocked      // get dentry                             cachefiles_cull                               inode-\u0026gt;i_flags |= S_KERNEL_FILE;     cachefiles_open_file       cachefiles_mark_inode_in_use         __cachefiles_mark_inode_in_use           can_use = false           if (!(inode-\u0026gt;i_flags \u0026amp; S_KERNEL_FILE))             can_use = true    return false         return false         // Returns an error but doesn\u0026apos;t put dentry  After that the following WARNING will be triggered when the backend folder is umounted:  ================================================================== BUG: Dentry 000000008ad87947{i=7a,n=Dx_1_1.img}  still in use (1) [unmount of ext4 sda] WARNING: CPU: 4 PID: 359261 at fs/dcache.c:1767 umount_check+0x5d/0x70 CPU: 4 PID: 359261 Comm: umount Not tainted 6.6.0-dirty #25 RIP: 0010:umount_check+0x5d/0x70 Call Trace:  \u0026lt;TASK\u0026gt;  d_walk+0xda/0x2b0  do_one_tree+0x20/0x40  shrink_dcache_for_umount+0x2c/0x90  generic_shutdown_super+0x20/0x160  kill_block_super+0x1a/0x40  ext4_kill_sb+0x22/0x40  deactivate_locked_super+0x35/0x80  cleanup_mnt+0x104/0x160 ==================================================================  Whether cachefiles_open_file() returns true or false, the reference count obtained by lookup_positive_unlocked() in cachefiles_look_up_object() should be released.  Therefore release that reference count in cachefiles_look_up_object() to fix the above issue and simplify the code.(CVE-2024-49870)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Input: adp5589-keys - fix NULL pointer dereference  We register a devm action to call adp5589_clear_config() and then pass the i2c client as argument so that we can call i2c_get_clientdata() in order to get our device object. However, i2c_set_clientdata() is only being set at the end of the probe function which means that we\u0026apos;ll get a NULL pointer dereference in case the probe function fails early.(CVE-2024-49871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition  In the svc_i3c_master_probe function, \u0026amp;master-\u0026gt;hj_work is bound with svc_i3c_master_hj_work, \u0026amp;master-\u0026gt;ibi_work is bound with svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work  can start the hj_work, svc_i3c_master_irq_handler can start the ibi_work.  If we remove the module which will call svc_i3c_master_remove to make cleanup, it will free master-\u0026gt;base through i3c_master_unregister while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                         CPU1                                      | svc_i3c_master_hj_work svc_i3c_master_remove               | i3c_master_unregister(\u0026amp;master-\u0026gt;base)| device_unregister(\u0026amp;master-\u0026gt;dev)     | device_release                      | //free master-\u0026gt;base                 |                                     | i3c_master_do_daa(\u0026amp;master-\u0026gt;base)                                     | //use master-\u0026gt;base  Fix it by ensuring that the work is canceled before proceeding with the cleanup in svc_i3c_master_remove.(CVE-2024-49874)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Initialize get_bytes_per_element\u0026apos;s default to 1  Variables, used as denominators and maybe not assigned to other values, should not be 0. bytes_per_element_y \u0026amp; bytes_per_element_c are initialized by get_bytes_per_element() which should never return 0.  This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check stream before comparing them  [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null-initialized variables  [WHAT \u0026amp; HOW] drr_timing and subvp_pipe are initialized to null and they are not always assigned new values. It is necessary to check for null before dereferencing.  This fixes 2 FORWARD_NULL issues reported by Coverity.(CVE-2024-49898)\r\n\r\n(CVE-2024-49901)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn32_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn32_set_output_transfer_func function. Previously, set_output_gamma was being checked for null, but then it was being dereferenced without any null check. This could lead to a null pointer dereference if set_output_gamma is null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma.(CVE-2024-49909)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Handle null \u0026apos;stream_status\u0026apos; in \u0026apos;planes_changed_for_existing_stream\u0026apos;  This commit adds a null check for \u0026apos;stream_status\u0026apos; in the function \u0026apos;planes_changed_for_existing_stream\u0026apos;. Previously, the code assumed \u0026apos;stream_status\u0026apos; could be null, but did not handle the case where it was actually null. This could lead to a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:3784 planes_changed_for_existing_stream() error: we previously assumed \u0026apos;stream_status\u0026apos; could be null (see line 3774)(CVE-2024-49912)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: ath12k: fix array out-of-bound access in SoC stats  Currently, the ath12k_soc_dp_stats::hal_reo_error array is defined with a maximum size of DP_REO_DST_RING_MAX. However, the ath12k_dp_rx_process() function access ath12k_soc_dp_stats::hal_reo_error using the REO destination SRNG ring ID, which is incorrect. SRNG ring ID differ from normal ring ID, and this usage leads to out-of-bounds array access. To fix this issue, modify ath12k_dp_rx_process() to use the normal ring ID directly instead of the SRNG ring ID to avoid out-of-bounds array access.  Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1(CVE-2024-49931)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: Set correct chandef when starting CAC  When starting CAC in a mode other than AP mode, it return a \u0026quot;WARNING: CPU: 0 PID: 63 at cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]\u0026quot; caused by the chandef.chan being null at the end of CAC.  Solution: Ensure the channel definition is set for the different modes when starting CAC to avoid getting a NULL \u0026apos;chan\u0026apos; at the end of CAC.   Call Trace:   ? show_regs.part.0+0x14/0x16   ? __warn+0x67/0xc0   ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]   ? report_bug+0xa7/0x130   ? exc_overflow+0x30/0x30   ? handle_bug+0x27/0x50   ? exc_invalid_op+0x18/0x60   ? handle_exception+0xf6/0xf6   ? exc_overflow+0x30/0x30   ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]   ? exc_overflow+0x30/0x30   ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]   ? regulatory_propagate_dfs_state.cold+0x1b/0x4c [cfg80211]   ? cfg80211_propagate_cac_done_wk+0x1a/0x30 [cfg80211]   ? process_one_work+0x165/0x280   ? worker_thread+0x120/0x3f0   ? kthread+0xc2/0xf0   ? process_one_work+0x280/0x280   ? kthread_complete_and_exit+0x20/0x20   ? ret_from_fork+0x19/0x24  [shorten subject, remove OCB, reorder cases to match previous list](CVE-2024-49937)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix timer use-after-free on failed mount  Syzbot has found an ODEBUG bug in ext4_fill_super  The del_timer_sync function cancels the s_err_report timer, which reminds about filesystem errors daily. We should guarantee the timer is no longer active before kfree(sbi).  When filesystem mounting fails, the flow goes to failed_mount3, where an error occurs when ext4_stop_mmpd is called, causing a read I/O failure. This triggers the ext4_handle_error function that ultimately re-arms the timer, leaving the s_err_report timer active before kfree(sbi) is called.  Fix the issue by canceling the s_err_report timer after calling ext4_stop_mmpd.(CVE-2024-49960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: i2c: ar0521: Use cansleep version of gpiod_set_value()  If we use GPIO reset from I2C port expander, we must use *_cansleep() variant of GPIO functions. This was not done in ar0521_power_on()/ar0521_power_off() functions. Let\u0026apos;s fix that.  ------------[ cut here ]------------ WARNING: CPU: 0 PID: 11 at drivers/gpio/gpiolib.c:3496 gpiod_set_value+0x74/0x7c Modules linked in: CPU: 0 PID: 11 Comm: kworker/u16:0 Not tainted 6.10.0 #53 Hardware name: Diasom DS-RK3568-SOM-EVB (DT) Workqueue: events_unbound deferred_probe_work_func pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : gpiod_set_value+0x74/0x7c lr : ar0521_power_on+0xcc/0x290 sp : ffffff8001d7ab70 x29: ffffff8001d7ab70 x28: ffffff80027dcc90 x27: ffffff8003c82000 x26: ffffff8003ca9250 x25: ffffffc080a39c60 x24: ffffff8003ca9088 x23: ffffff8002402720 x22: ffffff8003ca9080 x21: ffffff8003ca9088 x20: 0000000000000000 x19: ffffff8001eb2a00 x18: ffffff80efeeac80 x17: 756d2d6332692f30 x16: 0000000000000000 x15: 0000000000000000 x14: ffffff8001d91d40 x13: 0000000000000016 x12: ffffffc080e98930 x11: ffffff8001eb2880 x10: 0000000000000890 x9 : ffffff8001d7a9f0 x8 : ffffff8001d92570 x7 : ffffff80efeeac80 x6 : 000000003fc6e780 x5 : ffffff8001d91c80 x4 : 0000000000000002 x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000001 Call trace:  gpiod_set_value+0x74/0x7c  ar0521_power_on+0xcc/0x290 ...(CVE-2024-49961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: cancel dqi_sync_work before freeing oinfo  ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled:  ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c  This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first.  BTW, return status instead of -1 when .read_file_info fails.(CVE-2024-49966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: no need to continue when the number of entries is 1(CVE-2024-49967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: filesystems without casefold feature cannot be mounted with siphash  When mounting the ext4 filesystem, if the default hash version is set to DX_HASH_SIPHASH but the casefold feature is not set, exit the mounting.(CVE-2024-49968)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free  When calling ext4_force_split_extent_at() in ext4_ext_replay_update_ex(), the \u0026apos;ppath\u0026apos; is updated but it is the \u0026apos;path\u0026apos; that is freed, thus potentially triggering a double-free in the following process:  ext4_ext_replay_update_ex   ppath = path   ext4_force_split_extent_at(\u0026amp;ppath)     ext4_split_extent_at       ext4_ext_insert_extent         ext4_ext_create_new_leaf           ext4_ext_grow_indepth             ext4_find_extent               if (depth \u0026gt; path[0].p_maxdepth)                 kfree(path)                 ---\u0026gt; path First freed                 *orig_path = path = NULL    ---\u0026gt; null ppath   kfree(path)                               ---\u0026gt; path double-free !!!  So drop the unnecessary ppath and use path directly to avoid this problem. And use ext4_find_extent() directly to update path, avoiding unnecessary memory allocation and freeing. Also, propagate the error returned by ext4_find_extent() instead of using strange error codes.(CVE-2024-49983)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: fix double free issue during amdgpu module unload  Flexible endpoints use DIGs from available inflexible endpoints, so only the encoders of inflexible links need to be freed. Otherwise, a double free issue may occur when unloading the amdgpu module.  [  279.190523] RIP: 0010:__slab_free+0x152/0x2f0 [  279.190577] Call Trace: [  279.190580]  \u0026lt;TASK\u0026gt; [  279.190582]  ? show_regs+0x69/0x80 [  279.190590]  ? die+0x3b/0x90 [  279.190595]  ? do_trap+0xc8/0xe0 [  279.190601]  ? do_error_trap+0x73/0xa0 [  279.190605]  ? __slab_free+0x152/0x2f0 [  279.190609]  ? exc_invalid_op+0x56/0x70 [  279.190616]  ? __slab_free+0x152/0x2f0 [  279.190642]  ? asm_exc_invalid_op+0x1f/0x30 [  279.190648]  ? dcn10_link_encoder_destroy+0x19/0x30 [amdgpu] [  279.191096]  ? __slab_free+0x152/0x2f0 [  279.191102]  ? dcn10_link_encoder_destroy+0x19/0x30 [amdgpu] [  279.191469]  kfree+0x260/0x2b0 [  279.191474]  dcn10_link_encoder_destroy+0x19/0x30 [amdgpu] [  279.191821]  link_destroy+0xd7/0x130 [amdgpu] [  279.192248]  dc_destruct+0x90/0x270 [amdgpu] [  279.192666]  dc_destroy+0x19/0x40 [amdgpu] [  279.193020]  amdgpu_dm_fini+0x16e/0x200 [amdgpu] [  279.193432]  dm_hw_fini+0x26/0x40 [amdgpu] [  279.193795]  amdgpu_device_fini_hw+0x24c/0x400 [amdgpu] [  279.194108]  amdgpu_driver_unload_kms+0x4f/0x70 [amdgpu] [  279.194436]  amdgpu_pci_remove+0x40/0x80 [amdgpu] [  279.194632]  pci_device_remove+0x3a/0xa0 [  279.194638]  device_remove+0x40/0x70 [  279.194642]  device_release_driver_internal+0x1ad/0x210 [  279.194647]  driver_detach+0x4e/0xa0 [  279.194650]  bus_remove_driver+0x6f/0xf0 [  279.194653]  driver_unregister+0x33/0x60 [  279.194657]  pci_unregister_driver+0x44/0x90 [  279.194662]  amdgpu_exit+0x19/0x1f0 [amdgpu] [  279.194939]  __do_sys_delete_module.isra.0+0x198/0x2f0 [  279.194946]  __x64_sys_delete_module+0x16/0x20 [  279.194950]  do_syscall_64+0x58/0x120 [  279.194954]  entry_SYSCALL_64_after_hwframe+0x6e/0x76 [  279.194980]  \u0026lt;/TASK\u0026gt;(CVE-2024-49989)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix integer overflow in BLKSECDISCARD  I independently rediscovered   commit 22d24a544b0d49bbcbd61c8c0eaf77d3c9297155  block: fix overflow in blk_ioctl_discard()  but for secure erase.  Same problem:   uint64_t r[2] = {512, 18446744073709551104ULL};  ioctl(fd, BLKSECDISCARD, r);  will enter near infinite loop inside blkdev_issue_secure_erase():   a.out: attempt to access beyond end of device  loop0: rw=5, sector=3399043073, nr_sectors = 1024 limit=2048  bio_check_eod: 3286214 callbacks suppressed(CVE-2024-49994)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc()  In mlx5e_tir_builder_alloc() kvzalloc() may return NULL which is dereferenced on the next line in a reference to the modify field.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-50000)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix system hang while resume with TBT monitor  [Why] Connected with a Thunderbolt monitor and do the suspend and the system may hang while resume.  The TBT monitor HPD will be triggered during the resume procedure and call the drm_client_modeset_probe() while struct drm_connector connector-\u0026gt;dev-\u0026gt;master is NULL.  It will mess up the pipe topology after resume.  [How] Skip the TBT monitor HPD during the resume procedure because we currently will probe the connectors after resume by default.  (cherry picked from commit 453f86a26945207a16b8f66aaed5962dc2b95b85)(CVE-2024-50003)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix i_data_sem unlock order in ext4_ind_migrate()  Fuzzing reports a possible deadlock in jbd2_log_wait_commit.  This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call.  This problem only arises when CONFIG_PROVE_LOCKING is enabled. In this case, the jbd2_might_wait_for_commit macro locks jbd2_handle in the jbd2_journal_stop function while i_data_sem is locked. This triggers lockdep because the jbd2_journal_start function might also lock the same jbd2_handle simultaneously.  Found by Linux Verification Center (linuxtesting.org) with syzkaller.  Rule: add(CVE-2024-50006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cpufreq: amd-pstate: add check for cpufreq_cpu_get\u0026apos;s return value  cpufreq_cpu_get may return NULL. To avoid NULL-dereference check it and return in case of error.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-50009)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  exfat: fix memory leak in exfat_load_bitmap()  If the first directory entry in the root directory is not a bitmap directory entry, \u0026apos;bh\u0026apos; will not be released and reassigned, which will cause a memory leak.(CVE-2024-50013)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix access to uninitialised lock in fc replay path  The following kernel trace can be triggered with fstest generic/629 when executed against a filesystem with fast-commit feature enabled:  INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn\u0026apos;t initialize this object before use? turning off the locking correctness validator. CPU: 0 PID: 866 Comm: mount Not tainted 6.10.0+ #11 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x66/0x90  register_lock_class+0x759/0x7d0  __lock_acquire+0x85/0x2630  ? __find_get_block+0xb4/0x380  lock_acquire+0xd1/0x2d0  ? __ext4_journal_get_write_access+0xd5/0x160  _raw_spin_lock+0x33/0x40  ? __ext4_journal_get_write_access+0xd5/0x160  __ext4_journal_get_write_access+0xd5/0x160  ext4_reserve_inode_write+0x61/0xb0  __ext4_mark_inode_dirty+0x79/0x270  ? ext4_ext_replay_set_iblocks+0x2f8/0x450  ext4_ext_replay_set_iblocks+0x330/0x450  ext4_fc_replay+0x14c8/0x1540  ? jread+0x88/0x2e0  ? rcu_is_watching+0x11/0x40  do_one_pass+0x447/0xd00  jbd2_journal_recover+0x139/0x1b0  jbd2_journal_load+0x96/0x390  ext4_load_and_init_journal+0x253/0xd40  ext4_fill_super+0x2cc6/0x3180 ...  In the replay path there\u0026apos;s an attempt to lock sbi-\u0026gt;s_bdev_wb_lock in function ext4_check_bdev_write_error().  Unfortunately, at this point this spinlock has not been initialized yet.  Moving it\u0026apos;s initialization to an earlier point in __ext4_fill_super() fixes this splat.(CVE-2024-50014)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  kthread: unpark only parked kthread  Calling into kthread unparking unconditionally is mostly harmless when the kthread is already unparked. The wake up is then simply ignored because the target is not in TASK_PARKED state.  However if the kthread is per CPU, the wake up is preceded by a call to kthread_bind() which expects the task to be inactive and in TASK_PARKED state, which obviously isn\u0026apos;t the case if it is unparked.  As a result, calling kthread_stop() on an unparked per-cpu kthread triggers such a warning:   WARNING: CPU: 0 PID: 11 at kernel/kthread.c:525 __kthread_bind_mask kernel/kthread.c:525   \u0026lt;TASK\u0026gt;   kthread_stop+0x17a/0x630 kernel/kthread.c:707   destroy_workqueue+0x136/0xc40 kernel/workqueue.c:5810   wg_destruct+0x1e2/0x2e0 drivers/net/wireguard/device.c:257   netdev_run_todo+0xe1a/0x1000 net/core/dev.c:10693   default_device_exit_batch+0xa14/0xa90 net/core/dev.c:11769   ops_exit_list net/core/net_namespace.c:178 [inline]   cleanup_net+0x89d/0xcc0 net/core/net_namespace.c:640   process_one_work kernel/workqueue.c:3231 [inline]   process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312   worker_thread+0x86d/0xd70 kernel/workqueue.c:3393   kthread+0x2f0/0x390 kernel/kthread.c:389   ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147   ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244   \u0026lt;/TASK\u0026gt;  Fix this with skipping unecessary unparking while stopping a kthread.(CVE-2024-50019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  device-dax: correct pgoff align in dax_set_mapping()  pgoff should be aligned using ALIGN_DOWN() instead of ALIGN().  Otherwise, vmf-\u0026gt;address not aligned to fault_size will be aligned to the next alignment, that can result in memory failure getting the wrong address.  It\u0026apos;s a subtle situation that only can be observed in page_mapped_in_vma() after the page is page fault handled by dev_dax_huge_fault.  Generally, there is little chance to perform page_mapped_in_vma in dev-dax\u0026apos;s page unless in specific error injection to the dax device to trigger an MCE - memory-failure.  In that case, page_mapped_in_vma() will be triggered to determine which task is accessing the failure address and kill that task in the end.   We used self-developed dax device (which is 2M aligned mapping) , to perform error injection to random address.  It turned out that error injected to non-2M-aligned address was causing endless MCE until panic. Because page_mapped_in_vma() kept resulting wrong address and the task accessing the failure address was never killed properly:   [ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3784.049006] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3784.448042] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3784.792026] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3785.162502] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3785.461116] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3785.764730] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3786.042128] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3786.464293] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3786.818090] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3787.085297] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page:  Recovered  It took us several weeks to pinpoint this problem,  but we eventually used bpftrace to trace the page fault and mce address and successfully identified the issue.   Joao added:  ; Likely we never reproduce in production because we always pin : device-dax regions in the region align they provide (Qemu does : similarly with prealloc in hugetlb/file backed memory).  I think this : bug requires that we touch *unpinned* device-dax regions unaligned to : the device-dax selected alignment (page size i.e.  4K/2M/1G)(CVE-2024-50022)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: fnic: Move flush_work initialization out of if block  After commit 379a58caa199 (\u0026quot;scsi: fnic: Move fnic_fnic_flush_tx() to a work queue\u0026quot;), it can happen that a work item is sent to an uninitialized work queue.  This may has the effect that the item being queued is never actually queued, and any further actions depending on it will not proceed.  The following warning is observed while the fnic driver is loaded:  kernel: WARNING: CPU: 11 PID: 0 at ../kernel/workqueue.c:1524 __queue_work+0x373/0x410 kernel:  \u0026lt;IRQ\u0026gt; kernel:  queue_work_on+0x3a/0x50 kernel:  fnic_wq_copy_cmpl_handler+0x54a/0x730 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  fnic_isr_msix_wq_copy+0x2d/0x60 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  __handle_irq_event_percpu+0x36/0x1a0 kernel:  handle_irq_event_percpu+0x30/0x70 kernel:  handle_irq_event+0x34/0x60 kernel:  handle_edge_irq+0x7e/0x1a0 kernel:  __common_interrupt+0x3b/0xb0 kernel:  common_interrupt+0x58/0xa0 kernel:  \u0026lt;/IRQ\u0026gt;  It has been observed that this may break the rediscovery of Fibre Channel devices after a temporary fabric failure.  This patch fixes it by moving the work queue initialization out of an if block in fnic_probe().(CVE-2024-50025)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: wd33c93: Don\u0026apos;t use stale scsi_pointer value  A regression was introduced with commit dbb2da557a6a (\u0026quot;scsi: wd33c93: Move the SCSI pointer to private command data\u0026quot;) which results in an oops in wd33c93_intr(). That commit added the scsi_pointer variable and initialized it from hostdata-\u0026gt;connected. However, during selection, hostdata-\u0026gt;connected is not yet valid. Fix this by getting the current scsi_pointer from hostdata-\u0026gt;selecting.(CVE-2024-50026)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync  This checks if the ACL connection remains valid as it could be destroyed while hci_enhanced_setup_sync is pending on cmd_sync leading to the following trace:  BUG: KASAN: slab-use-after-free in hci_enhanced_setup_sync+0x91b/0xa60 Read of size 1 at addr ffff888002328ffd by task kworker/u5:2/37  CPU: 0 UID: 0 PID: 37 Comm: kworker/u5:2 Not tainted 6.11.0-rc6-01300-g810be445d8d6 #7099 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 Workqueue: hci0 hci_cmd_sync_work Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x5d/0x80  ? hci_enhanced_setup_sync+0x91b/0xa60  print_report+0x152/0x4c0  ? hci_enhanced_setup_sync+0x91b/0xa60  ? __virt_addr_valid+0x1fa/0x420  ? hci_enhanced_setup_sync+0x91b/0xa60  kasan_report+0xda/0x1b0  ? hci_enhanced_setup_sync+0x91b/0xa60  hci_enhanced_setup_sync+0x91b/0xa60  ? __pfx_hci_enhanced_setup_sync+0x10/0x10  ? __pfx___mutex_lock+0x10/0x10  hci_cmd_sync_work+0x1c2/0x330  process_one_work+0x7d9/0x1360  ? __pfx_lock_acquire+0x10/0x10  ? __pfx_process_one_work+0x10/0x10  ? assign_work+0x167/0x240  worker_thread+0x5b7/0xf60  ? __kthread_parkme+0xac/0x1c0  ? __pfx_worker_thread+0x10/0x10  ? __pfx_worker_thread+0x10/0x10  kthread+0x293/0x360  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2f/0x70  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt;  Allocated by task 34:  kasan_save_stack+0x30/0x50  kasan_save_track+0x14/0x30  __kasan_kmalloc+0x8f/0xa0  __hci_conn_add+0x187/0x17d0  hci_connect_sco+0x2e1/0xb90  sco_sock_connect+0x2a2/0xb80  __sys_connect+0x227/0x2a0  __x64_sys_connect+0x6d/0xb0  do_syscall_64+0x71/0x140  entry_SYSCALL_64_after_hwframe+0x76/0x7e  Freed by task 37:  kasan_save_stack+0x30/0x50  kasan_save_track+0x14/0x30  kasan_save_free_info+0x3b/0x60  __kasan_slab_free+0x101/0x160  kfree+0xd0/0x250  device_release+0x9a/0x210  kobject_put+0x151/0x280  hci_conn_del+0x448/0xbf0  hci_abort_conn_sync+0x46f/0x980  hci_cmd_sync_work+0x1c2/0x330  process_one_work+0x7d9/0x1360  worker_thread+0x5b7/0xf60  kthread+0x293/0x360  ret_from_fork+0x2f/0x70  ret_from_fork_asm+0x1a/0x30(CVE-2024-50029)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: do not delay dst_entries_add() in dst_release()  dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy()  Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy()  dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already.  Decrementing the number of dsts must happen sooner.  Notes:  1) in CONFIG_XFRM case, dst_destroy() can call    dst_release_immediate(child), this might also cause UAF    if the child does not have DST_NOCOUNT set.    IPSEC maintainers might take a look and see how to address this.  2) There is also discussion about removing this count of dst,    which might happen in future kernels.(CVE-2024-50036)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  igb: Do not bring the device up after non-fatal error  Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below.  [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [  T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [  T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [  T292] igb 0000:09:00.0:   device [8086:1537] error status/mask=00004000/00000000 [  T292] igb 0000:09:00.0:    [14] CmpltTO [  200.105524,009][  T292] igb 0000:09:00.0: AER:   TLP Header: 00000000 00000000 00000000 00000000 [  T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [  T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [  T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [  T292] pcieport 0000:00:1c.5: AER: broadcast resume message [  T292] ------------[ cut here ]------------ [  T292] kernel BUG at net/core/dev.c:6539! [  T292] invalid opcode: 0000 [#1] PREEMPT SMP [  T292] RIP: 0010:napi_enable+0x37/0x40 [  T292] Call Trace: [  T292]  \u0026lt;TASK\u0026gt; [  T292]  ? die+0x33/0x90 [  T292]  ? do_trap+0xdc/0x110 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? do_error_trap+0x70/0xb0 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? exc_invalid_op+0x4e/0x70 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? asm_exc_invalid_op+0x16/0x20 [  T292]  ? napi_enable+0x37/0x40 [  T292]  igb_up+0x41/0x150 [  T292]  igb_io_resume+0x25/0x70 [  T292]  report_resume+0x54/0x70 [  T292]  ? report_frozen_detected+0x20/0x20 [  T292]  pci_walk_bus+0x6c/0x90 [  T292]  ? aer_print_port_info+0xa0/0xa0 [  T292]  pcie_do_recovery+0x22f/0x380 [  T292]  aer_process_err_devices+0x110/0x160 [  T292]  aer_isr+0x1c1/0x1e0 [  T292]  ? disable_irq_nosync+0x10/0x10 [  T292]  irq_thread_fn+0x1a/0x60 [  T292]  irq_thread+0xe3/0x1a0 [  T292]  ? irq_set_affinity_notifier+0x120/0x120 [  T292]  ? irq_affinity_notify+0x100/0x100 [  T292]  kthread+0xe2/0x110 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork+0x2d/0x50 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork_asm+0x11/0x20 [  T292]  \u0026lt;/TASK\u0026gt;  To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i40e: Fix macvlan leak by synchronizing access to mac_filter_hash  This patch addresses a macvlan leak issue in the i40e driver caused by concurrent access to vsi-\u0026gt;mac_filter_hash. The leak occurs when multiple threads attempt to modify the mac_filter_hash simultaneously, leading to inconsistent state and potential memory leaks.  To fix this, we now wrap the calls to i40e_del_mac_filter() and zeroing vf-\u0026gt;default_lan_addr.addr with spin_lock/unlock_bh(\u0026amp;vsi-\u0026gt;mac_filter_hash_lock), ensuring atomic operations and preventing concurrent access.  Additionally, we add lockdep_assert_held(\u0026amp;vsi-\u0026gt;mac_filter_hash_lock) in i40e_add_mac_filter() to help catch similar issues in the future.  Reproduction steps: 1. Spawn VFs and configure port vlan on them. 2. Trigger concurrent macvlan operations (e.g., adding and deleting  portvlan and/or mac filters). 3. Observe the potential memory leak and inconsistent state in the  mac_filter_hash.  This synchronization ensures the integrity of the mac_filter_hash and prevents the described leak.(CVE-2024-50041)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  driver core: bus: Fix double free in driver API bus_register()  For bus_register(), any error which happens after kset_register() will cause that @priv are freed twice, fixed by setting @priv with NULL after the first free.(CVE-2024-50055)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  zram: free secondary algorithms names  We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.  [senozhatsky@chromium.org: kfree(NULL) is legal]   Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm/mremap: fix move_normal_pmd/retract_page_tables race  In mremap(), move_page_tables() looks at the type of the PMD entry and the specified address range to figure out by which method the next chunk of page table entries should be moved.  At that point, the mmap_lock is held in write mode, but no rmap locks are held yet.  For PMD entries that point to page tables and are fully covered by the source address range, move_pgt_entry(NORMAL_PMD, ...) is called, which first takes rmap locks, then does move_normal_pmd().  move_normal_pmd() takes the necessary page table locks at source and destination, then moves an entire page table from the source to the destination.  The problem is: The rmap locks, which protect against concurrent page table removal by retract_page_tables() in the THP code, are only taken after the PMD entry has been read and it has been decided how to move it.  So we can race as follows (with two processes that have mappings of the same tmpfs file that is stored on a tmpfs mount with huge=advise); note that process A accesses page tables through the MM while process B does it through the file rmap:  process A                      process B =========                      ========= mremap   mremap_to     move_vma       move_page_tables         get_old_pmd         alloc_new_pmd                       *** PREEMPT ***                                madvise(MADV_COLLAPSE)                                  do_madvise                                    madvise_walk_vmas                                      madvise_vma_behavior                                        madvise_collapse                                          hpage_collapse_scan_file                                            collapse_file                                              retract_page_tables                                                i_mmap_lock_read(mapping)                                                pmdp_collapse_flush                                                i_mmap_unlock_read(mapping)         move_pgt_entry(NORMAL_PMD, ...)           take_rmap_locks           move_normal_pmd           drop_rmap_locks  When this happens, move_normal_pmd() can end up creating bogus PMD entries in the line `pmd_populate(mm, new_pmd, pmd_pgtable(pmd))`.  The effect depends on arch-specific and machine-specific details; on x86, you can end up with physical page 0 mapped as a page table, which is likely exploitable for user-\u0026gt;kernel privilege escalation.  Fix the race by letting process B recheck that the PMD still points to a page table after the rmap locks have been taken.  Otherwise, we bail and let the caller fall back to the PTE-level copying path, which will then bail immediately at the pmd_none() check.  Bug reachability: Reaching this bug requires that you can create shmem/file THP mappings - anonymous THP uses different code that doesn\u0026apos;t zap stuff under rmap locks.  File THP is gated on an experimental config flag (CONFIG_READ_ONLY_THP_FOR_FS), so on normal distro kernels you need shmem THP to hit this bug.  As far as I know, getting shmem THP normally requires that you can mount your own tmpfs with the right mount flags, which would require creating your own user+mount namespace; though I don\u0026apos;t know if some distros maybe enable shmem THP by default or something like that.  Bug impact: This issue can likely be used for user-\u0026gt;kernel privilege escalation when it is reachable.(CVE-2024-50066)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  pinctrl: stm32: check devm_kasprintf() returned value  devm_kasprintf() can return a NULL pointer on failure but this returned value is not checked. Fix this lack and check the returned value.  Found by code review.(CVE-2024-50070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/bugs: Use code segment selector for VERW operand  Robert Gill reported below #GP in 32-bit mode when dosemu software was executing vm86() system call:    general protection fault: 0000 [#1] PREEMPT SMP   CPU: 4 PID: 4610 Comm: dosemu.bin Not tainted 6.6.21-gentoo-x86 #1   Hardware name: Dell Inc. PowerEdge 1950/0H723K, BIOS 2.7.0 10/30/2010   EIP: restore_all_switch_stack+0xbe/0xcf   EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000   ESI: 00000000 EDI: 00000000 EBP: 00000000 ESP: ff8affdc   DS: 0000 ES: 0000 FS: 0000 GS: 0033 SS: 0068 EFLAGS: 00010046   CR0: 80050033 CR2: 00c2101c CR3: 04b6d000 CR4: 000406d0   Call Trace:    show_regs+0x70/0x78    die_addr+0x29/0x70    exc_general_protection+0x13c/0x348    exc_bounds+0x98/0x98    handle_exception+0x14d/0x14d    exc_bounds+0x98/0x98    restore_all_switch_stack+0xbe/0xcf    exc_bounds+0x98/0x98    restore_all_switch_stack+0xbe/0xcf  This only happens in 32-bit mode when VERW based mitigations like MDS/RFDS are enabled. This is because segment registers with an arbitrary user value can result in #GP when executing VERW. Intel SDM vol. 2C documents the following behavior for VERW instruction:    #GP(0) - If a memory operand effective address is outside the CS, DS, ES,     FS, or GS segment limit.  CLEAR_CPU_BUFFERS macro executes VERW instruction before returning to user space. Use %cs selector to reference VERW operand. This ensures VERW will not #GP for an arbitrary user %ds.  [ mingo: Fixed the SOB chain. ](CVE-2024-50072)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vt: prevent kernel-infoleak in con_font_get()  font.data may not initialize all memory spaces depending on the implementation of vc-\u0026gt;vc_sw-\u0026gt;con_font_get. This may cause info-leak, so to prevent this, it is safest to modify it to initialize the allocated memory space to 0, and it generally does not affect the overall performance of the system.(CVE-2024-50076)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: microchip: vcap api: Fix memory leaks in vcap_api_encode_rule_test()  Commit a3c1e45156ad (\u0026quot;net: microchip: vcap: Fix use-after-free error in kunit test\u0026quot;) fixed the use-after-free error, but introduced below memory leaks by removing necessary vcap_free_rule(), add it to fix it.   unreferenced object 0xffffff80ca58b700 (size 192):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898264    hex dump (first 32 bytes):      00 12 7a 00 05 00 00 00 0a 00 00 00 64 00 00 00  ..z.........d...      00 00 00 00 00 00 00 00 00 04 0b cc 80 ff ff ff  ................    backtrace (crc 9c09c3fe):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;0000000040a01b8d\u0026gt;] vcap_alloc_rule+0x3cc/0x9c4      [\u0026lt;000000003fe86110\u0026gt;] vcap_api_encode_rule_test+0x1ac/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0400 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898265    hex dump (first 32 bytes):      80 04 0b cc 80 ff ff ff 18 b7 58 ca 80 ff ff ff  ..........X.....      39 00 00 00 02 00 00 00 06 05 04 03 02 01 ff ff  9...............    backtrace (crc daf014e9):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000000ff63fd4\u0026gt;] vcap_rule_add_key+0x2cc/0x528      [\u0026lt;00000000dfdb1e81\u0026gt;] vcap_api_encode_rule_test+0x224/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0700 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898265    hex dump (first 32 bytes):      80 07 0b cc 80 ff ff ff 28 b7 58 ca 80 ff ff ff  ........(.X.....      3c 00 00 00 00 00 00 00 01 2f 03 b3 ec ff ff ff  \u0026lt;......../......    backtrace (crc 8d877792):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000006eadfab7\u0026gt;] vcap_rule_add_action+0x2d0/0x52c      [\u0026lt;00000000323475d1\u0026gt;] vcap_api_encode_rule_test+0x4d4/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0900 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898266    hex dump (first 32 bytes):      80 09 0b cc 80 ff ff ff 80 06 0b cc 80 ff ff ff  ................      7d 00 00 00 01 00 00 00 00 00 00 00 ff 00 00 00  }...............    backtrace (crc 34181e56):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000000ff63fd4\u0026gt;] vcap_rule_add_key+0x2cc/0x528      [\u0026lt;00000000991e3564\u0026gt;] vcap_val_rule+0xcf0/0x13e8      [\u0026lt;00000000fc9868e5\u0026gt;] vcap_api_encode_rule_test+0x678/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0980 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898266    hex dump (first 32 bytes):      18 b7 58 ca 80 ff ff ff 00 09 0b cc 80 ff ff ff  ..X.............      67 00 00 00 00 00 00 00 01 01 74 88 c0 ff ff ff  g.........t.....    backtrace (crc 275fd9be):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000000ff63fd4\u0026gt;] vcap_rule_add_key+0x2cc/0x528      [\u0026lt;000000001396a1a2\u0026gt;] test_add_de ---truncated---(CVE-2024-50084)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix uninitialized pointer free on read_alloc_one_name() error  The function read_alloc_one_name() does not initialize the name field of the passed fscrypt_str struct if kmalloc fails to allocate the corresponding buffer.  Thus, it is not guaranteed that fscrypt_str.name is initialized when freeing it.  This is a follow-up to the linked patch that fixes the remaining instances of the bug introduced by commit e43eec81c516 (\u0026quot;btrfs: use struct qstr instead of name and namelen pairs\u0026quot;).(CVE-2024-50087)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix uninitialized pointer free in add_inode_ref()  The add_inode_ref() function does not initialize the \u0026quot;name\u0026quot; struct when it is declared.  If any of the following calls to \u0026quot;read_one_inode() returns NULL,   dir = read_one_inode(root, parent_objectid);  if (!dir) {   ret = -ENOENT;   goto out;  }   inode = read_one_inode(root, inode_objectid);  if (!inode) {   ret = -EIO;   goto out;  }  then \u0026quot;name.name\u0026quot; would be freed on \u0026quot;out\u0026quot; before being initialized.  out:  ...  kfree(name.name);  This issue was reported by Coverity with CID 1526744.(CVE-2024-50088)","status":"published","published":"2024-11-08T11:07:50Z","modified":"2026-08-18T01:18:38.656170144Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2368","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:  net: mdio: fix unbalanced fwnode reference count in mdio_device_release()  There is warning report about of_node refcount leak while probing mdio device:  OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4  In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly.  After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpiolib: fix memory leak in gpiochip_setup_dev()  Here is a backtrace report about memory leak detected in gpiochip_setup_dev():  unreferenced object 0xffff88810b406400 (size 512):   comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s)   backtrace:     kmalloc_trace     device_add  device_private_init at drivers/base/core.c:3361    (inlined by) device_add at drivers/base/core.c:3411     cdev_device_add     gpiolib_cdev_register     gpiochip_setup_dev     gpiochip_add_data_with_key  gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device.  However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del().  Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path.  Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree().  While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  riscv: Sync efi page table\u0026apos;s kernel mappings before switching  The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic.  Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n   with active Smack in the default state\n   (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n   (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n   that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n   (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n   Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  IB/core: Fix ib_cache_setup_one error flow cleanup  When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below.  Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue.  WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8    3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS:  00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x94/0xa0  ? __warn+0x9e/0x1c0  ? gid_table_release_one+0x181/0x1a0  ? report_bug+0x1f9/0x340  ? gid_table_release_one+0x181/0x1a0  ? handle_bug+0xa2/0x110  ? exc_invalid_op+0x31/0xa0  ? asm_exc_invalid_op+0x16/0x20  ? __warn_printk+0xc7/0x180  ? __warn_printk+0xd4/0x180  ? gid_table_release_one+0x181/0x1a0  ib_device_release+0x71/0xe0  ? __pfx_ib_device_release+0x10/0x10  device_release+0x44/0xd0  kobject_put+0x135/0x3d0  put_device+0x20/0x30  rxe_net_add+0x7d/0xa0  rxe_newlink+0xd7/0x190  nldev_newlink+0x1b0/0x2a0  ? __pfx_nldev_newlink+0x10/0x10  rdma_nl_rcv_msg+0x1ad/0x2e0  rdma_nl_rcv_skb.constprop.0+0x176/0x210  netlink_unicast+0x2de/0x400  netlink_sendmsg+0x306/0x660  __sock_sendmsg+0x110/0x120  ____sys_sendmsg+0x30e/0x390  ___sys_sendmsg+0x9b/0xf0  ? kstrtouint+0x6e/0xa0  ? kstrtouint_from_user+0x7c/0xb0  ? get_pid_task+0xb0/0xd0  ? proc_fail_nth_write+0x5b/0x140  ? __fget_light+0x9a/0x200  ? preempt_count_add+0x47/0xa0  __sys_sendmsg+0x61/0xd0  do_syscall_64+0x50/0x110  entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: fix out-of-bounds in dbNextAG() and diAlloc()  In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount().  And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented.  Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to wait dio completion  It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to check atomic_file in f2fs ioctl interfaces  Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  powercap: intel_rapl: Fix off by one in get_rpi()  The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements.  Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check stream before comparing them  [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: Fix uaf in l2cap_connect  [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54  CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0xc3/0x620 mm/kasan/report.c:488  kasan_report+0xd9/0x110 mm/kasan/report.c:601  l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949  l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline]  l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline]  l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline]  l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825  l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514  hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline]  hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ...  Freed by task 5245:  kasan_save_stack+0x33/0x60 mm/kasan/common.c:47  kasan_save_track+0x14/0x30 mm/kasan/common.c:68  kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579  poison_slab_object+0xf7/0x160 mm/kasan/common.c:240  __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2256 [inline]  slab_free mm/slub.c:4477 [inline]  kfree+0x12a/0x3b0 mm/slub.c:4598  l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline]  kref_put include/linux/kref.h:65 [inline]  l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline]  l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802  l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241  hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline]  hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265  hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583  abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917  hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Handle module init failure correctly in static_call_del_module()  Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain.  If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries.  This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod.  The problem is that key::mods is not a individual struct member of struct static_call_key, it\u0026apos;s part of a union to save space:          union {                 /* bit 0: 0 = mods, 1 = sites */                 unsigned long type;                 struct static_call_mod *mods;                 struct static_call_site *sites;  };  key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set.  As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus.  Cure it by checking whether the key has a sites or a mods pointer.  If it\u0026apos;s a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit.  If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing.  A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can\u0026apos;t match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: asihpi: Fix potential OOB array access  ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware.  We shouldn\u0026apos;t trust it blindly.  This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ppp: fix ppp_async_encode() illegal access  syzbot reported an issue in ppp_async_encode() [1]  In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb.  BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]  BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]   ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634   ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline]   ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4092 [inline]   slab_alloc_node mm/slub.c:4135 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  igb: Do not bring the device up after non-fatal error  Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below.  [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [  T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [  T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [  T292] igb 0000:09:00.0:   device [8086:1537] error status/mask=00004000/00000000 [  T292] igb 0000:09:00.0:    [14] CmpltTO [  200.105524,009][  T292] igb 0000:09:00.0: AER:   TLP Header: 00000000 00000000 00000000 00000000 [  T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [  T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [  T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [  T292] pcieport 0000:00:1c.5: AER: broadcast resume message [  T292] ------------[ cut here ]------------ [  T292] kernel BUG at net/core/dev.c:6539! [  T292] invalid opcode: 0000 [#1] PREEMPT SMP [  T292] RIP: 0010:napi_enable+0x37/0x40 [  T292] Call Trace: [  T292]  \u0026lt;TASK\u0026gt; [  T292]  ? die+0x33/0x90 [  T292]  ? do_trap+0xdc/0x110 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? do_error_trap+0x70/0xb0 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? exc_invalid_op+0x4e/0x70 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? asm_exc_invalid_op+0x16/0x20 [  T292]  ? napi_enable+0x37/0x40 [  T292]  igb_up+0x41/0x150 [  T292]  igb_io_resume+0x25/0x70 [  T292]  report_resume+0x54/0x70 [  T292]  ? report_frozen_detected+0x20/0x20 [  T292]  pci_walk_bus+0x6c/0x90 [  T292]  ? aer_print_port_info+0xa0/0xa0 [  T292]  pcie_do_recovery+0x22f/0x380 [  T292]  aer_process_err_devices+0x110/0x160 [  T292]  aer_isr+0x1c1/0x1e0 [  T292]  ? disable_irq_nosync+0x10/0x10 [  T292]  irq_thread_fn+0x1a/0x60 [  T292]  irq_thread+0xe3/0x1a0 [  T292]  ? irq_set_affinity_notifier+0x120/0x120 [  T292]  ? irq_affinity_notify+0x100/0x100 [  T292]  kthread+0xe2/0x110 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork+0x2d/0x50 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork_asm+0x11/0x20 [  T292]  \u0026lt;/TASK\u0026gt;  To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  zram: free secondary algorithms names  We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.  [senozhatsky@chromium.org: kfree(NULL) is legal]   Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)","status":"published","published":"2024-11-08T11:07:50Z","modified":"2026-08-18T01:18:38.692115173Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2369","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:  net: mdio: fix unbalanced fwnode reference count in mdio_device_release()  There is warning report about of_node refcount leak while probing mdio device:  OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4  In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly.  After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpiolib: fix memory leak in gpiochip_setup_dev()  Here is a backtrace report about memory leak detected in gpiochip_setup_dev():  unreferenced object 0xffff88810b406400 (size 512):   comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s)   backtrace:     kmalloc_trace     device_add  device_private_init at drivers/base/core.c:3361    (inlined by) device_add at drivers/base/core.c:3411     cdev_device_add     gpiolib_cdev_register     gpiochip_setup_dev     gpiochip_add_data_with_key  gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device.  However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del().  Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path.  Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree().  While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  riscv: Sync efi page table\u0026apos;s kernel mappings before switching  The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic.  Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n   with active Smack in the default state\n   (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n   (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n   that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n   (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n   Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  IB/core: Fix ib_cache_setup_one error flow cleanup  When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below.  Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue.  WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8    3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS:  00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x94/0xa0  ? __warn+0x9e/0x1c0  ? gid_table_release_one+0x181/0x1a0  ? report_bug+0x1f9/0x340  ? gid_table_release_one+0x181/0x1a0  ? handle_bug+0xa2/0x110  ? exc_invalid_op+0x31/0xa0  ? asm_exc_invalid_op+0x16/0x20  ? __warn_printk+0xc7/0x180  ? __warn_printk+0xd4/0x180  ? gid_table_release_one+0x181/0x1a0  ib_device_release+0x71/0xe0  ? __pfx_ib_device_release+0x10/0x10  device_release+0x44/0xd0  kobject_put+0x135/0x3d0  put_device+0x20/0x30  rxe_net_add+0x7d/0xa0  rxe_newlink+0xd7/0x190  nldev_newlink+0x1b0/0x2a0  ? __pfx_nldev_newlink+0x10/0x10  rdma_nl_rcv_msg+0x1ad/0x2e0  rdma_nl_rcv_skb.constprop.0+0x176/0x210  netlink_unicast+0x2de/0x400  netlink_sendmsg+0x306/0x660  __sock_sendmsg+0x110/0x120  ____sys_sendmsg+0x30e/0x390  ___sys_sendmsg+0x9b/0xf0  ? kstrtouint+0x6e/0xa0  ? kstrtouint_from_user+0x7c/0xb0  ? get_pid_task+0xb0/0xd0  ? proc_fail_nth_write+0x5b/0x140  ? __fget_light+0x9a/0x200  ? preempt_count_add+0x47/0xa0  __sys_sendmsg+0x61/0xd0  do_syscall_64+0x50/0x110  entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: fix out-of-bounds in dbNextAG() and diAlloc()  In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount().  And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented.  Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to wait dio completion  It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to check atomic_file in f2fs ioctl interfaces  Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  powercap: intel_rapl: Fix off by one in get_rpi()  The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements.  Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check stream before comparing them  [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: Fix uaf in l2cap_connect  [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54  CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0xc3/0x620 mm/kasan/report.c:488  kasan_report+0xd9/0x110 mm/kasan/report.c:601  l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949  l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline]  l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline]  l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline]  l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825  l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514  hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline]  hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ...  Freed by task 5245:  kasan_save_stack+0x33/0x60 mm/kasan/common.c:47  kasan_save_track+0x14/0x30 mm/kasan/common.c:68  kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579  poison_slab_object+0xf7/0x160 mm/kasan/common.c:240  __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2256 [inline]  slab_free mm/slub.c:4477 [inline]  kfree+0x12a/0x3b0 mm/slub.c:4598  l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline]  kref_put include/linux/kref.h:65 [inline]  l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline]  l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802  l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241  hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline]  hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265  hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583  abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917  hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Handle module init failure correctly in static_call_del_module()  Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain.  If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries.  This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod.  The problem is that key::mods is not a individual struct member of struct static_call_key, it\u0026apos;s part of a union to save space:          union {                 /* bit 0: 0 = mods, 1 = sites */                 unsigned long type;                 struct static_call_mod *mods;                 struct static_call_site *sites;  };  key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set.  As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus.  Cure it by checking whether the key has a sites or a mods pointer.  If it\u0026apos;s a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit.  If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing.  A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can\u0026apos;t match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: asihpi: Fix potential OOB array access  ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware.  We shouldn\u0026apos;t trust it blindly.  This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ppp: fix ppp_async_encode() illegal access  syzbot reported an issue in ppp_async_encode() [1]  In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb.  BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]  BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]   ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634   ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline]   ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4092 [inline]   slab_alloc_node mm/slub.c:4135 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  igb: Do not bring the device up after non-fatal error  Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below.  [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [  T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [  T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [  T292] igb 0000:09:00.0:   device [8086:1537] error status/mask=00004000/00000000 [  T292] igb 0000:09:00.0:    [14] CmpltTO [  200.105524,009][  T292] igb 0000:09:00.0: AER:   TLP Header: 00000000 00000000 00000000 00000000 [  T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [  T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [  T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [  T292] pcieport 0000:00:1c.5: AER: broadcast resume message [  T292] ------------[ cut here ]------------ [  T292] kernel BUG at net/core/dev.c:6539! [  T292] invalid opcode: 0000 [#1] PREEMPT SMP [  T292] RIP: 0010:napi_enable+0x37/0x40 [  T292] Call Trace: [  T292]  \u0026lt;TASK\u0026gt; [  T292]  ? die+0x33/0x90 [  T292]  ? do_trap+0xdc/0x110 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? do_error_trap+0x70/0xb0 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? exc_invalid_op+0x4e/0x70 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? asm_exc_invalid_op+0x16/0x20 [  T292]  ? napi_enable+0x37/0x40 [  T292]  igb_up+0x41/0x150 [  T292]  igb_io_resume+0x25/0x70 [  T292]  report_resume+0x54/0x70 [  T292]  ? report_frozen_detected+0x20/0x20 [  T292]  pci_walk_bus+0x6c/0x90 [  T292]  ? aer_print_port_info+0xa0/0xa0 [  T292]  pcie_do_recovery+0x22f/0x380 [  T292]  aer_process_err_devices+0x110/0x160 [  T292]  aer_isr+0x1c1/0x1e0 [  T292]  ? disable_irq_nosync+0x10/0x10 [  T292]  irq_thread_fn+0x1a/0x60 [  T292]  irq_thread+0xe3/0x1a0 [  T292]  ? irq_set_affinity_notifier+0x120/0x120 [  T292]  ? irq_affinity_notify+0x100/0x100 [  T292]  kthread+0xe2/0x110 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork+0x2d/0x50 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork_asm+0x11/0x20 [  T292]  \u0026lt;/TASK\u0026gt;  To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  zram: free secondary algorithms names  We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.  [senozhatsky@chromium.org: kfree(NULL) is legal]   Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)","status":"published","published":"2024-11-08T11:07:50Z","modified":"2026-08-18T01:18:38.732529946Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2371","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:  ipv6: avoid use-after-free in ip6_fragment()  Blamed commit claimed rcu_read_lock() was held by ip6_fragment() callers.  It seems to not be always true, at least for UDP stack.  syzbot reported:  BUG: KASAN: use-after-free in ip6_dst_idev include/net/ip6_fib.h:245 [inline] BUG: KASAN: use-after-free in ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 Read of size 8 at addr ffff88801d403e80 by task syz-executor.3/7618  CPU: 1 PID: 7618 Comm: syz-executor.3 Not tainted 6.1.0-rc6-syzkaller-00012-g4312098baf37 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106  print_address_description mm/kasan/report.c:284 [inline]  print_report+0x15e/0x45d mm/kasan/report.c:395  kasan_report+0xbf/0x1f0 mm/kasan/report.c:495  ip6_dst_idev include/net/ip6_fib.h:245 [inline]  ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951  __ip6_finish_output net/ipv6/ip6_output.c:193 [inline]  ip6_finish_output+0x9a3/0x1170 net/ipv6/ip6_output.c:206  NF_HOOK_COND include/linux/netfilter.h:291 [inline]  ip6_output+0x1f1/0x540 net/ipv6/ip6_output.c:227  dst_output include/net/dst.h:445 [inline]  ip6_local_out+0xb3/0x1a0 net/ipv6/output_core.c:161  ip6_send_skb+0xbb/0x340 net/ipv6/ip6_output.c:1966  udp_v6_send_skb+0x82a/0x18a0 net/ipv6/udp.c:1286  udp_v6_push_pending_frames+0x140/0x200 net/ipv6/udp.c:1313  udpv6_sendmsg+0x18da/0x2c80 net/ipv6/udp.c:1606  inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665  sock_sendmsg_nosec net/socket.c:714 [inline]  sock_sendmsg+0xd3/0x120 net/socket.c:734  sock_write_iter+0x295/0x3d0 net/socket.c:1108  call_write_iter include/linux/fs.h:2191 [inline]  new_sync_write fs/read_write.c:491 [inline]  vfs_write+0x9ed/0xdd0 fs/read_write.c:584  ksys_write+0x1ec/0x250 fs/read_write.c:637  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fde3588c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fde365b6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fde359ac050 RCX: 00007fde3588c0d9 RDX: 000000000000ffdc RSI: 00000000200000c0 RDI: 000000000000000a RBP: 00007fde358e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fde35acfb1f R14: 00007fde365b6300 R15: 0000000000022000  \u0026lt;/TASK\u0026gt;  Allocated by task 7618:  kasan_save_stack+0x22/0x40 mm/kasan/common.c:45  kasan_set_track+0x25/0x30 mm/kasan/common.c:52  __kasan_slab_alloc+0x82/0x90 mm/kasan/common.c:325  kasan_slab_alloc include/linux/kasan.h:201 [inline]  slab_post_alloc_hook mm/slab.h:737 [inline]  slab_alloc_node mm/slub.c:3398 [inline]  slab_alloc mm/slub.c:3406 [inline]  __kmem_cache_alloc_lru mm/slub.c:3413 [inline]  kmem_cache_alloc+0x2b4/0x3d0 mm/slub.c:3422  dst_alloc+0x14a/0x1f0 net/core/dst.c:92  ip6_dst_alloc+0x32/0xa0 net/ipv6/route.c:344  ip6_rt_pcpu_alloc net/ipv6/route.c:1369 [inline]  rt6_make_pcpu_route net/ipv6/route.c:1417 [inline]  ip6_pol_route+0x901/0x1190 net/ipv6/route.c:2254  pol_lookup_func include/net/ip6_fib.h:582 [inline]  fib6_rule_lookup+0x52e/0x6f0 net/ipv6/fib6_rules.c:121  ip6_route_output_flags_noref+0x2e6/0x380 net/ipv6/route.c:2625  ip6_route_output_flags+0x76/0x320 net/ipv6/route.c:2638  ip6_route_output include/net/ip6_route.h:98 [inline]  ip6_dst_lookup_tail+0x5ab/0x1620 net/ipv6/ip6_output.c:1092  ip6_dst_lookup_flow+0x90/0x1d0 net/ipv6/ip6_output.c:1222  ip6_sk_dst_lookup_flow+0x553/0x980 net/ipv6/ip6_output.c:1260  udpv6_sendmsg+0x151d/0x2c80 net/ipv6/udp.c:1554  inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665  sock_sendmsg_nosec n ---truncated---(CVE-2022-48956)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ethernet: aeroflex: fix potential skb leak in greth_init_rings()  The greth_init_rings() function won\u0026apos;t free the newly allocated skb when dma_mapping_error() returns error, so add dev_kfree_skb() to fix it.  Compile tested only.(CVE-2022-48958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: hisilicon: Fix potential use-after-free in hix5hd2_rx()  The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: mdio: fix unbalanced fwnode reference count in mdio_device_release()  There is warning report about of_node refcount leak while probing mdio device:  OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4  In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly.  After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: hisilicon: Fix potential use-after-free in hisi_femac_rx()  The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48962)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: mvneta: Prevent out of bounds read in mvneta_config_rss()  The pp-\u0026gt;indir[0] value comes from the user.  It is passed to:   if (cpu_online(pp-\u0026gt;rxq_def))  inside the mvneta_percpu_elect() function.  It needs bounds checkeding to ensure that it is not beyond the end of the cpu bitmap.(CVE-2022-48966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add()  Kernel fault injection test reports null-ptr-deref as follows:  BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:cfg802154_netdev_notifier_call+0x120/0x310 include/linux/list.h:114 Call Trace:  \u0026lt;TASK\u0026gt;  raw_notifier_call_chain+0x6d/0xa0 kernel/notifier.c:87  call_netdevice_notifiers_info+0x6e/0xc0 net/core/dev.c:1944  unregister_netdevice_many_notify+0x60d/0xcb0 net/core/dev.c:1982  unregister_netdevice_queue+0x154/0x1a0 net/core/dev.c:10879  register_netdevice+0x9a8/0xb90 net/core/dev.c:10083  ieee802154_if_add+0x6ed/0x7e0 net/mac802154/iface.c:659  ieee802154_register_hw+0x29c/0x330 net/mac802154/main.c:229  mcr20a_probe+0xaaa/0xcb1 drivers/net/ieee802154/mcr20a.c:1316  ieee802154_if_add() allocates wpan_dev as netdev\u0026apos;s private data, but not init the list in struct wpan_dev. cfg802154_netdev_notifier_call() manage the list when device register/unregister, and may lead to null-ptr-deref.  Use INIT_LIST_HEAD() on it to initialize it correctly.(CVE-2022-48972)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpiolib: fix memory leak in gpiochip_setup_dev()  Here is a backtrace report about memory leak detected in gpiochip_setup_dev():  unreferenced object 0xffff88810b406400 (size 512):   comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s)   backtrace:     kmalloc_trace     device_add  device_private_init at drivers/base/core.c:3361    (inlined by) device_add at drivers/base/core.c:3411     cdev_device_add     gpiolib_cdev_register     gpiochip_setup_dev     gpiochip_add_data_with_key  gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device.  However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del().  Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path.  Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree().  While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/shmem-helper: Remove errant put in error path  drm_gem_shmem_mmap() doesn\u0026apos;t own this reference, resulting in the GEM object getting prematurely freed leading to a later use-after-free.(CVE-2022-48981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: Fix crash when replugging CSR fake controllers  It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice causing the following kernel panic:  [   71.986122] Call Trace: [   71.986124]  \u0026lt;TASK\u0026gt; [   71.986125]  blocking_notifier_chain_register+0x33/0x60 [   71.986130]  hci_register_dev+0x316/0x3d0 [bluetooth 99b5497ea3d09708fa1366c1dc03288bf3cca8da] [   71.986154]  btusb_probe+0x979/0xd85 [btusb e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [   71.986159]  ? __pm_runtime_set_status+0x1a9/0x300 [   71.986162]  ? ktime_get_mono_fast_ns+0x3e/0x90 [   71.986167]  usb_probe_interface+0xe3/0x2b0 [   71.986171]  really_probe+0xdb/0x380 [   71.986174]  ? pm_runtime_barrier+0x54/0x90 [   71.986177]  __driver_probe_device+0x78/0x170 [   71.986180]  driver_probe_device+0x1f/0x90 [   71.986183]  __device_attach_driver+0x89/0x110 [   71.986186]  ? driver_allows_async_probing+0x70/0x70 [   71.986189]  bus_for_each_drv+0x8c/0xe0 [   71.986192]  __device_attach+0xb2/0x1e0 [   71.986195]  bus_probe_device+0x92/0xb0 [   71.986198]  device_add+0x422/0x9a0 [   71.986201]  ? sysfs_merge_group+0xd4/0x110 [   71.986205]  usb_set_configuration+0x57a/0x820 [   71.986208]  usb_generic_driver_probe+0x4f/0x70 [   71.986211]  usb_probe_device+0x3a/0x110 [   71.986213]  really_probe+0xdb/0x380 [   71.986216]  ? pm_runtime_barrier+0x54/0x90 [   71.986219]  __driver_probe_device+0x78/0x170 [   71.986221]  driver_probe_device+0x1f/0x90 [   71.986224]  __device_attach_driver+0x89/0x110 [   71.986227]  ? driver_allows_async_probing+0x70/0x70 [   71.986230]  bus_for_each_drv+0x8c/0xe0 [   71.986232]  __device_attach+0xb2/0x1e0 [   71.986235]  bus_probe_device+0x92/0xb0 [   71.986237]  device_add+0x422/0x9a0 [   71.986239]  ? _dev_info+0x7d/0x98 [   71.986242]  ? blake2s_update+0x4c/0xc0 [   71.986246]  usb_new_device.cold+0x148/0x36d [   71.986250]  hub_event+0xa8a/0x1910 [   71.986255]  process_one_work+0x1c4/0x380 [   71.986259]  worker_thread+0x51/0x390 [   71.986262]  ? rescuer_thread+0x3b0/0x3b0 [   71.986264]  kthread+0xdb/0x110 [   71.986266]  ? kthread_complete_and_exit+0x20/0x20 [   71.986268]  ret_from_fork+0x1f/0x30 [   71.986273]  \u0026lt;/TASK\u0026gt; [   71.986274] ---[ end trace 0000000000000000 ]--- [   71.986284] btusb: probe of 2-1.6:1.0 failed with error -17(CVE-2022-48982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ASoC: soc-pcm: Add NULL check in BE reparenting  Add NULL check in dpcm_be_reparent API, to handle kernel NULL pointer dereference error. The issue occurred in fuzzing test.(CVE-2022-48992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send()  There is a kmemleak when test the raydium_i2c_ts with bpf mock device:    unreferenced object 0xffff88812d3675a0 (size 8):     comm \u0026quot;python3\u0026quot;, pid 349, jiffies 4294741067 (age 95.695s)     hex dump (first 8 bytes):       11 0e 10 c0 01 00 04 00                          ........     backtrace:       [\u0026lt;0000000068427125\u0026gt;] __kmalloc+0x46/0x1b0       [\u0026lt;0000000090180f91\u0026gt;] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts]       [\u0026lt;000000006e631aee\u0026gt;] raydium_i2c_initialize.cold+0xbc/0x3e4 [raydium_i2c_ts]       [\u0026lt;00000000dc6fcf38\u0026gt;] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts]       [\u0026lt;00000000a310de16\u0026gt;] i2c_device_probe+0x651/0x680       [\u0026lt;00000000f5a96bf3\u0026gt;] really_probe+0x17c/0x3f0       [\u0026lt;00000000096ba499\u0026gt;] __driver_probe_device+0xe3/0x170       [\u0026lt;00000000c5acb4d9\u0026gt;] driver_probe_device+0x49/0x120       [\u0026lt;00000000264fe082\u0026gt;] __device_attach_driver+0xf7/0x150       [\u0026lt;00000000f919423c\u0026gt;] bus_for_each_drv+0x114/0x180       [\u0026lt;00000000e067feca\u0026gt;] __device_attach+0x1e5/0x2d0       [\u0026lt;0000000054301fc2\u0026gt;] bus_probe_device+0x126/0x140       [\u0026lt;00000000aad93b22\u0026gt;] device_add+0x810/0x1130       [\u0026lt;00000000c086a53f\u0026gt;] i2c_new_client_device+0x352/0x4e0       [\u0026lt;000000003c2c248c\u0026gt;] of_i2c_register_device+0xf1/0x110       [\u0026lt;00000000ffec4177\u0026gt;] of_i2c_notify+0x100/0x160   unreferenced object 0xffff88812d3675c8 (size 8):     comm \u0026quot;python3\u0026quot;, pid 349, jiffies 4294741070 (age 95.692s)     hex dump (first 8 bytes):       22 00 36 2d 81 88 ff ff                          \u0026quot;.6-....     backtrace:       [\u0026lt;0000000068427125\u0026gt;] __kmalloc+0x46/0x1b0       [\u0026lt;0000000090180f91\u0026gt;] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts]       [\u0026lt;000000001d5c9620\u0026gt;] raydium_i2c_initialize.cold+0x223/0x3e4 [raydium_i2c_ts]       [\u0026lt;00000000dc6fcf38\u0026gt;] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts]       [\u0026lt;00000000a310de16\u0026gt;] i2c_device_probe+0x651/0x680       [\u0026lt;00000000f5a96bf3\u0026gt;] really_probe+0x17c/0x3f0       [\u0026lt;00000000096ba499\u0026gt;] __driver_probe_device+0xe3/0x170       [\u0026lt;00000000c5acb4d9\u0026gt;] driver_probe_device+0x49/0x120       [\u0026lt;00000000264fe082\u0026gt;] __device_attach_driver+0xf7/0x150       [\u0026lt;00000000f919423c\u0026gt;] bus_for_each_drv+0x114/0x180       [\u0026lt;00000000e067feca\u0026gt;] __device_attach+0x1e5/0x2d0       [\u0026lt;0000000054301fc2\u0026gt;] bus_probe_device+0x126/0x140       [\u0026lt;00000000aad93b22\u0026gt;] device_add+0x810/0x1130       [\u0026lt;00000000c086a53f\u0026gt;] i2c_new_client_device+0x352/0x4e0       [\u0026lt;000000003c2c248c\u0026gt;] of_i2c_register_device+0xf1/0x110       [\u0026lt;00000000ffec4177\u0026gt;] of_i2c_notify+0x100/0x160  After BANK_SWITCH command from i2c BUS, no matter success or error happened, the tx_buf should be freed.(CVE-2022-48995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  riscv: Sync efi page table\u0026apos;s kernel mappings before switching  The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic.  Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ASoC: ops: Fix bounds check for _sx controls  For _sx controls the semantics of the max field is not the usual one, max is the number of steps rather than the maximum value. This means that our check in snd_soc_put_volsw_sx() needs to just check against the maximum value.(CVE-2022-49005)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new()  As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it after using to avoid refcount leak.(CVE-2022-49011)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: re-fetch skb cb after tipc_msg_validate  As the call trace shows, the original skb was freed in tipc_msg_validate(), and dereferencing the old skb cb would cause an use-after-free crash.    BUG: KASAN: use-after-free in tipc_crypto_rcv_complete+0x1835/0x2240 [tipc]   Call Trace:    \u0026lt;IRQ\u0026gt;    tipc_crypto_rcv_complete+0x1835/0x2240 [tipc]    tipc_crypto_rcv+0xd32/0x1ec0 [tipc]    tipc_rcv+0x744/0x1150 [tipc]   ...   Allocated by task 47078:    kmem_cache_alloc_node+0x158/0x4d0    __alloc_skb+0x1c1/0x270    tipc_buf_acquire+0x1e/0xe0 [tipc]    tipc_msg_create+0x33/0x1c0 [tipc]    tipc_link_build_proto_msg+0x38a/0x2100 [tipc]    tipc_link_timeout+0x8b8/0xef0 [tipc]    tipc_node_timeout+0x2a1/0x960 [tipc]    call_timer_fn+0x2d/0x1c0   ...   Freed by task 47078:    tipc_msg_validate+0x7b/0x440 [tipc]    tipc_crypto_rcv_complete+0x4b5/0x2240 [tipc]    tipc_crypto_rcv+0xd32/0x1ec0 [tipc]    tipc_rcv+0x744/0x1150 [tipc]  This patch fixes it by re-fetching the skb cb from the new allocated skb after calling tipc_msg_validate().(CVE-2022-49017)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/9p: Fix a potential socket leak in p9_socket_open  Both p9_fd_create_tcp() and p9_fd_create_unix() will call p9_socket_open(). If the creation of p9_trans_fd fails, p9_fd_create_tcp() and p9_fd_create_unix() will return an error directly instead of releasing the cscoket, which will result in a socket leak.  This patch adds sock_release() to fix the leak issue.(CVE-2022-49020)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: phy: fix null-ptr-deref while probe() failed  I got a null-ptr-deref report as following when doing fault injection test:  BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G    B            N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace:  \u0026lt;TASK\u0026gt;  klist_remove+0xf1/0x1c0  device_release_driver_internal+0x23e/0x2d0  bus_remove_device+0x1bd/0x240  device_del+0x357/0x770  phy_device_remove+0x11/0x30  mdiobus_unregister+0xa5/0x140  release_nodes+0x6a/0xa0  devres_release_all+0xf8/0x150  device_unbind_cleanup+0x19/0xd0  //probe path: phy_device_register()   device_add()  phy_connect   phy_attach_direct() //set device driver     probe() //it\u0026apos;s failed, driver is not bound     device_bind_driver() // probe failed, it\u0026apos;s not called  //remove path: phy_device_remove()   device_del()     device_release_driver_internal()       __device_release_driver() //dev-\u0026gt;drv is not NULL         klist_remove() \u0026lt;- knode_driver is not added yet, cause null-ptr-deref  In phy_attach_direct(), after setting the \u0026apos;dev-\u0026gt;driver\u0026apos;, probe() fails, device_bind_driver() is not called, so the knode_driver-\u0026gt;n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev-\u0026gt;driver to NULL in the error path in phy_attach_direct().(CVE-2022-49021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: fix buffer overflow in elem comparison  For vendor elements, the code here assumes that 5 octets are present without checking. Since the element itself is already checked to fit, we only need to check the length.(CVE-2022-49023)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iio: health: afe4403: Fix oob read in afe4403_read_raw  KASAN report out-of-bounds read as follows:  BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279  Call Trace:  afe4403_read_raw  iio_read_channel_info  dev_attr_show  The buggy address belongs to the variable:  afe4403_channel_leds+0x18/0xffffffffffffe9e0  This issue can be reproduced by singe command:   $ cat /sys/bus/spi/devices/spi0.0/iio\\:device0/in_intensity6_raw  The array size of afe4403_channel_leds is less than channels, so access with chan-\u0026gt;address cause OOB read in afe4403_read_raw. Fix it by moving access before use it.(CVE-2022-49031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw  KASAN report out-of-bounds read as follows:  BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e4658 by task cat/278  Call Trace:  afe4404_read_raw  iio_read_channel_info  dev_attr_show  The buggy address belongs to the variable:  afe4404_channel_leds+0x18/0xffffffffffffe9c0  This issue can be reproduce by singe command:   $ cat /sys/bus/i2c/devices/0-0058/iio\\:device0/in_intensity6_raw  The array size of afe4404_channel_leds and afe4404_channel_offdacs are less than channels, so access with chan-\u0026gt;address cause OOB read in afe4404_[read|write]_raw. Fix it by moving access before use them.(CVE-2022-49032)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n   with active Smack in the default state\n   (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n   (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n   that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n   (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n   Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: return -EINVAL when namelen is 0  When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered.  [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205]  dump_stack+0x9a/0xd0 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  __kasan_report.cold+0x34/0x84 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  kasan_report+0x3a/0x50 [ T1205]  nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  ? nfsd4_release_lockowner+0x410/0x410 [ T1205]  cld_pipe_downcall+0x5ca/0x760 [ T1205]  ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205]  ? down_write_killable_nested+0x170/0x170 [ T1205]  ? avc_policy_seqno+0x28/0x40 [ T1205]  ? selinux_file_permission+0x1b4/0x1e0 [ T1205]  rpc_pipe_write+0x84/0xb0 [ T1205]  vfs_write+0x143/0x520 [ T1205]  ksys_write+0xc9/0x170 [ T1205]  ? __ia32_sys_read+0x50/0x50 [ T1205]  ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205]  ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205]  do_syscall_64+0x33/0x40 [ T1205]  entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ==================================================================  Fix it by checking namelen.(CVE-2024-47692)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  IB/core: Fix ib_cache_setup_one error flow cleanup  When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below.  Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue.  WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8    3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS:  00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x94/0xa0  ? __warn+0x9e/0x1c0  ? gid_table_release_one+0x181/0x1a0  ? report_bug+0x1f9/0x340  ? gid_table_release_one+0x181/0x1a0  ? handle_bug+0xa2/0x110  ? exc_invalid_op+0x31/0xa0  ? asm_exc_invalid_op+0x16/0x20  ? __warn_printk+0xc7/0x180  ? __warn_printk+0xd4/0x180  ? gid_table_release_one+0x181/0x1a0  ib_device_release+0x71/0xe0  ? __pfx_ib_device_release+0x10/0x10  device_release+0x44/0xd0  kobject_put+0x135/0x3d0  put_device+0x20/0x30  rxe_net_add+0x7d/0xa0  rxe_newlink+0xd7/0x190  nldev_newlink+0x1b0/0x2a0  ? __pfx_nldev_newlink+0x10/0x10  rdma_nl_rcv_msg+0x1ad/0x2e0  rdma_nl_rcv_skb.constprop.0+0x176/0x210  netlink_unicast+0x2de/0x400  netlink_sendmsg+0x306/0x660  __sock_sendmsg+0x110/0x120  ____sys_sendmsg+0x30e/0x390  ___sys_sendmsg+0x9b/0xf0  ? kstrtouint+0x6e/0xa0  ? kstrtouint_from_user+0x7c/0xb0  ? get_pid_task+0xb0/0xd0  ? proc_fail_nth_write+0x5b/0x140  ? __fget_light+0x9a/0x200  ? preempt_count_add+0x47/0xa0  __sys_sendmsg+0x61/0xd0  do_syscall_64+0x50/0x110  entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: fix out-of-bounds in dbNextAG() and diAlloc()  In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount().  And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented.  Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost/scsi: null-ptr-dereference in vhost_scsi_get_req()  Since commit 3f8ca2e115e5 (\u0026quot;vhost/scsi: Extract common handling code from control queue handler\u0026quot;) a null pointer dereference bug can be triggered when guest sends an SCSI AN request.  In vhost_scsi_ctl_handle_vq(), `vc.target` is assigned with `\u0026amp;v_req.tmf.lun[1]` within a switch-case block and is then passed to vhost_scsi_get_req() which extracts `vc-\u0026gt;req` and `tpg`. However, for a `VIRTIO_SCSI_T_AN_*` request, tpg is not required, so `vc.target` is set to NULL in this branch. Later, in vhost_scsi_get_req(), `vc-\u0026gt;target` is dereferenced without being checked, leading to a null pointer dereference bug. This bug can be triggered from guest.  When this bug occurs, the vhost_worker process is killed while holding `vq-\u0026gt;mutex` and the corresponding tpg will remain occupied indefinitely.  Below is the KASAN report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 PID: 840 Comm: poc Not tainted 6.10.0+ #1 Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:vhost_scsi_get_req+0x165/0x3a0 Code: 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 2b 02 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b 65 30 4c 89 e2 48 c1 ea 03 \u0026lt;0f\u0026gt; b6 04 02 4c 89 e2 83 e2 07 38 d0 7f 08 84 c0 0f 85 be 01 00 00 RSP: 0018:ffff888017affb50 EFLAGS: 00010246 RAX: dffffc0000000000 RBX: ffff88801b000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888017affcb8 RBP: ffff888017affb80 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff888017affc88 R14: ffff888017affd1c R15: ffff888017993000 FS:  000055556e076500(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200027c0 CR3: 0000000010ed0004 CR4: 0000000000370ef0 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x86/0xa0  ? die_addr+0x4b/0xd0  ? exc_general_protection+0x163/0x260  ? asm_exc_general_protection+0x27/0x30  ? vhost_scsi_get_req+0x165/0x3a0  vhost_scsi_ctl_handle_vq+0x2a4/0xca0  ? __pfx_vhost_scsi_ctl_handle_vq+0x10/0x10  ? __switch_to+0x721/0xeb0  ? __schedule+0xda5/0x5710  ? __kasan_check_write+0x14/0x30  ? _raw_spin_lock+0x82/0xf0  vhost_scsi_ctl_handle_kick+0x52/0x90  vhost_run_work_list+0x134/0x1b0  vhost_task_fn+0x121/0x350 ...  \u0026lt;/TASK\u0026gt; ---[ end trace 0000000000000000 ]---  Let\u0026apos;s add a check in vhost_scsi_get_req.  [whitespace fixes](CVE-2024-49863)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: Fix uaf in l2cap_connect  [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54  CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0xc3/0x620 mm/kasan/report.c:488  kasan_report+0xd9/0x110 mm/kasan/report.c:601  l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949  l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline]  l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline]  l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline]  l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825  l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514  hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline]  hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ...  Freed by task 5245:  kasan_save_stack+0x33/0x60 mm/kasan/common.c:47  kasan_save_track+0x14/0x30 mm/kasan/common.c:68  kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579  poison_slab_object+0xf7/0x160 mm/kasan/common.c:240  __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2256 [inline]  slab_free mm/slub.c:4477 [inline]  kfree+0x12a/0x3b0 mm/slub.c:4598  l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline]  kref_put include/linux/kref.h:65 [inline]  l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline]  l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802  l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241  hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline]  hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265  hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583  abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917  hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: remove unreasonable unlock in ocfs2_read_blocks  Patch series \u0026quot;Misc fixes for ocfs2_read_blocks\u0026quot;, v5.  This series contains 2 fixes for ocfs2_read_blocks().  The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks().  The second patch fixes an issue reported by Heming Zhao when reviewing above fix.   This patch (of 2):  There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ppp: fix ppp_async_encode() illegal access  syzbot reported an issue in ppp_async_encode() [1]  In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb.  BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]  BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]   ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634   ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline]   ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4092 [inline]   slab_alloc_node mm/slub.c:4135 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()  On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog:  [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701]   ESR = 0x0000000096000007 [232066.588862]   EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084]   SET = 0, FnV = 0 [232066.589216]   EA = 0, S1PTW = 0 [232066.589340]   FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683]   ISV = 0, ISS = 0x00000007 [232066.589842]   CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052]  vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\\x93\\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)","status":"published","published":"2024-11-08T11:07:51Z","modified":"2026-08-18T01:18:40.386686868Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"UBUNTU-CVE-2024-45021","description":"In the Linux kernel, the following vulnerability has been resolved: memcg_write_event_control(): fix a user-triggerable oops we are *not* guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).","status":"published","published":"2024-09-11T16:15:00Z","modified":"2026-11-12T17:24:25.479956517Z","cvss":[{"version":"4.0","score":6.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/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"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-12T18:04:07.901897Z"},{"id":"CLSA-2024-1731602566","title":"Fix of 76 CVEs","description":"   * CVE-url: https://ubuntu.com/security/CVE-2024-44946\n     - kcm: Serialise kcm_sendmsg() for the same socket.\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42292\n     - kobject_uevent: Fix OOB access within zap_modalias_env()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41042\n     - netfilter: nf_tables: prefer nft_chain_validate\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42265\n     - protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50036\n     - net: do not delay dst_entries_add() in dst_release()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47663\n     - staging: iio: frequency: ad9833: Load clock using clock framework\n     - staging: iio: frequency: ad9834: Validate frequency parameter value\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47669\n     - nilfs2: fix state management in error path of log writing function\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52918\n     - media: pci: cx23885: check cx23885_vdev_init() return\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44960\n     - usb: gadget: core: Check for unset descriptor\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42297\n     - f2fs: fix to don't dirty inode for readonly filesystem\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46750\n     - PCI: Add missing bridge lock to pci_bus_lock()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46676\n     - nfc: pn533: Add poll mod list filling check\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46761\n     - pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46755\n     - wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46679\n     - ethtool: check device is present when getting link settings\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46721\n     - apparmor: fix possible NULL pointer dereference\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46685\n     - pinctrl: single: fix potential NULL dereference in pcs_get_function()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44947\n     - fuse: Initialize beyond-EOF page contents before setting uptodate\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46675\n     - usb: dwc3: core: Prevent USB core invalid event buffer address access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43893\n     - serial: core: check uartclk for zero to avoid divide by zero\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45021\n     - memcg_write_event_control(): fix a user-triggerable oops\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46677\n     - gtp: fix a potential NULL pointer dereference\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43861\n     - net: usb: qmi_wwan: fix memory leak for not ip packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41063\n     - Bluetooth: hci_core: cancel all works upon hci_unregister_dev()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45006\n     - xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43853\n     - cgroup/cpuset: Prevent UAF in proc_cpuset_show()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42310\n     - drm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42311\n     - hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41012\n     - filelock: Remove locks reliably when fcntl/close race is detected\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45028\n     - mmc: mmc_test: Fix NULL dereference on allocation failure\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43860\n     - remoteproc: imx_rproc: Skip over memory region when node value is NULL\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43914\n     - md/raid5: avoid BUG_ON() while continue reshape after reassembling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45025\n     - fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43856\n     - dma: fix call order in dmam_free_coherent\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42289\n     - scsi: qla2xxx: During vport delete send async logout explicitly\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44995\n     - net: hns3: fix a deadlock problem when config TC during resetting\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43854\n     - block: initialize integrity buffer to zero before writing it to media\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43884\n     - Bluetooth: MGMT: Add error handling to pair_device()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43871\n     - devres: Fix memory leakage caused by driver API devm_free_percpu()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42309\n     - drm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26668\n     - netfilter: nft_limit: reject configurations that cause integer overflow\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50044\n     - Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49967\n     - ext4: no need to continue when the number of entries is 1\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50033\n     - slip: make slhc_remember() more robust against malicious packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47670\n     - ocfs2: add bounds checking to ocfs2_xattr_find_entry()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49950\n     - Bluetooth: L2CAP: Fix uaf in l2cap_connect\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49883\n     - ext4: aovid use-after-free in ext4_ext_insert_extent()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47745\n     - mm: call the security_mmap_file() LSM hook in remap_file_pages()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49860\n     - ACPI: sysfs: validate return type of _STR method\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49882\n     - ext4: fix double brelse() the buffer of the extents path\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49995\n     - tipc: guard against string buffer overrun\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47723\n     - jfs: fix out-of-bounds in dbNextAG() and diAlloc()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50055\n     - driver core: bus: Fix double free in driver API bus_register()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47698\n     - drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49026\n     - e100: Fix possible use after free in e100_xmit_prepare\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47742\n     - firmware_loader: Block path traversal\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50035\n     - ppp: fix ppp_async_encode() illegal access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47757\n     - nilfs2: fix potential oob read in nilfs_btree_check_delete()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49884\n     - ext4: avoid ext4_error()'s caused by ENOMEM in the truncate path\n     - ext4: fix slab-use-after-free in ext4_split_extent_at()\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49006\n     - tracing: Free buffers when a used dynamic event is removed\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49903\n     - jfs: Fix uaf in dbFreeBits\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47701\n     - ext4: avoid OOB when system.data xattr changes underneath the filesystem\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49889\n     - ext4: avoid use-after-free in ext4_ext_show_leaf()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50073\n     - tty: n_gsm: Fix use-after-free in gsm_cleanup_mux\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47747\n     - net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race\n       Condition\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49900\n     - jfs: Fix uninit-value access of new_ea in ea_buffer\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47697\n     - drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48951\n     - ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49981\n     - media: venus: fix use after free bug in venus_remove due to race condition\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43839\n     - bna: adjust 'name' buf size of bna_tcb and bna_ccb structures\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47659\n     - smack: tcp: ipv4, fix incorrect labeling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47685\n     - netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39476\n     - md/raid5: fix deadlock that raid5d() wait for itself to clear\n       MD_SB_CHANGE_PENDING\n   * CVE-url: https://ubuntu.com/security/CVE-2024-27397\n     - netfilter: nf_tables: use timestamp to check for set element timeout\n     - netfilter: nf_tables: annotate data-races around element expiration\n     - netfilter: nf_tables: support timeouts larger than 23 days\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26641\n     - net: Fix unwanted sign extension in netdev_stats_to_stats64()\n     - ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38611\n     - media: i2c: et8ek8: Don't strip remove function when driver is builtin","status":"published","published":"2024-11-14T16:42:51Z","modified":"2026-06-04T10:03:16.76153745Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1731603213","title":"Fix of 76 CVEs","description":"   * CVE-url: https://ubuntu.com/security/CVE-2024-44946\n     - kcm: Serialise kcm_sendmsg() for the same socket.\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42292\n     - kobject_uevent: Fix OOB access within zap_modalias_env()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41042\n     - netfilter: nf_tables: prefer nft_chain_validate\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42265\n     - protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50036\n     - net: do not delay dst_entries_add() in dst_release()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47663\n     - staging: iio: frequency: ad9833: Load clock using clock framework\n     - staging: iio: frequency: ad9834: Validate frequency parameter value\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47669\n     - nilfs2: fix state management in error path of log writing function\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52918\n     - media: pci: cx23885: check cx23885_vdev_init() return\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44960\n     - usb: gadget: core: Check for unset descriptor\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42297\n     - f2fs: fix to don't dirty inode for readonly filesystem\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46750\n     - PCI: Add missing bridge lock to pci_bus_lock()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46676\n     - nfc: pn533: Add poll mod list filling check\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46761\n     - pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46755\n     - wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46679\n     - ethtool: check device is present when getting link settings\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46721\n     - apparmor: fix possible NULL pointer dereference\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46685\n     - pinctrl: single: fix potential NULL dereference in pcs_get_function()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44947\n     - fuse: Initialize beyond-EOF page contents before setting uptodate\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46675\n     - usb: dwc3: core: Prevent USB core invalid event buffer address access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43893\n     - serial: core: check uartclk for zero to avoid divide by zero\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45021\n     - memcg_write_event_control(): fix a user-triggerable oops\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46677\n     - gtp: fix a potential NULL pointer dereference\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43861\n     - net: usb: qmi_wwan: fix memory leak for not ip packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41063\n     - Bluetooth: hci_core: cancel all works upon hci_unregister_dev()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45006\n     - xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43853\n     - cgroup/cpuset: Prevent UAF in proc_cpuset_show()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42310\n     - drm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42311\n     - hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41012\n     - filelock: Remove locks reliably when fcntl/close race is detected\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45028\n     - mmc: mmc_test: Fix NULL dereference on allocation failure\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43860\n     - remoteproc: imx_rproc: Skip over memory region when node value is NULL\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43914\n     - md/raid5: avoid BUG_ON() while continue reshape after reassembling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45025\n     - fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43856\n     - dma: fix call order in dmam_free_coherent\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42289\n     - scsi: qla2xxx: During vport delete send async logout explicitly\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44995\n     - net: hns3: fix a deadlock problem when config TC during resetting\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43854\n     - block: initialize integrity buffer to zero before writing it to media\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43884\n     - Bluetooth: MGMT: Add error handling to pair_device()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43871\n     - devres: Fix memory leakage caused by driver API devm_free_percpu()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42309\n     - drm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26668\n     - netfilter: nft_limit: reject configurations that cause integer overflow\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50044\n     - Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49967\n     - ext4: no need to continue when the number of entries is 1\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50033\n     - slip: make slhc_remember() more robust against malicious packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47670\n     - ocfs2: add bounds checking to ocfs2_xattr_find_entry()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49950\n     - Bluetooth: L2CAP: Fix uaf in l2cap_connect\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49883\n     - ext4: aovid use-after-free in ext4_ext_insert_extent()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47745\n     - mm: call the security_mmap_file() LSM hook in remap_file_pages()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49860\n     - ACPI: sysfs: validate return type of _STR method\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49882\n     - ext4: fix double brelse() the buffer of the extents path\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49995\n     - tipc: guard against string buffer overrun\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47723\n     - jfs: fix out-of-bounds in dbNextAG() and diAlloc()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50055\n     - driver core: bus: Fix double free in driver API bus_register()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47698\n     - drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49026\n     - e100: Fix possible use after free in e100_xmit_prepare\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47742\n     - firmware_loader: Block path traversal\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50035\n     - ppp: fix ppp_async_encode() illegal access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47757\n     - nilfs2: fix potential oob read in nilfs_btree_check_delete()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49884\n     - ext4: avoid ext4_error()'s caused by ENOMEM in the truncate path\n     - ext4: fix slab-use-after-free in ext4_split_extent_at()\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49006\n     - tracing: Free buffers when a used dynamic event is removed\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49903\n     - jfs: Fix uaf in dbFreeBits\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47701\n     - ext4: avoid OOB when system.data xattr changes underneath the filesystem\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49889\n     - ext4: avoid use-after-free in ext4_ext_show_leaf()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50073\n     - tty: n_gsm: Fix use-after-free in gsm_cleanup_mux\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47747\n     - net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race\n       Condition\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49900\n     - jfs: Fix uninit-value access of new_ea in ea_buffer\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47697\n     - drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48951\n     - ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49981\n     - media: venus: fix use after free bug in venus_remove due to race condition\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43839\n     - bna: adjust 'name' buf size of bna_tcb and bna_ccb structures\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47659\n     - smack: tcp: ipv4, fix incorrect labeling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47685\n     - netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39476\n     - md/raid5: fix deadlock that raid5d() wait for itself to clear\n       MD_SB_CHANGE_PENDING\n   * CVE-url: https://ubuntu.com/security/CVE-2024-27397\n     - netfilter: nf_tables: use timestamp to check for set element timeout\n     - netfilter: nf_tables: annotate data-races around element expiration\n     - netfilter: nf_tables: support timeouts larger than 23 days\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26641\n     - net: Fix unwanted sign extension in netdev_stats_to_stats64()\n     - ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38611\n     - media: i2c: et8ek8: Don't strip remove function when driver is builtin","status":"published","published":"2024-11-14T16:53:39Z","modified":"2026-06-04T10:03:51.920526752Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1731605761","title":"Fix of 67 CVEs","description":"   * CVE-url: https://ubuntu.com/security/CVE-2024-42265\n     - protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47669\n     - nilfs2: fix state management in error path of log writing function\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52918\n     - media: pci: cx23885: check cx23885_vdev_init() return\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46750\n     - PCI: Add missing bridge lock to pci_bus_lock()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46676\n     - nfc: pn533: Add poll mod list filling check\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46755\n     - wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46721\n     - apparmor: fix possible NULL pointer dereference\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44947\n     - fuse: Initialize beyond-EOF page contents before setting uptodate\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46675\n     - usb: dwc3: core: Prevent USB core invalid event buffer address access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43893\n     - serial: core: check uartclk for zero to avoid divide by zero\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45021\n     - memcg_write_event_control(): fix a user-triggerable oops\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41012\n     - filelock: Remove locks reliably when fcntl/close race is detected\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42310\n     - drm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42311\n     - hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45028\n     - mmc: mmc_test: Fix NULL dereference on allocation failure\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43914\n     - md/raid5: avoid BUG_ON() while continue reshape after reassembling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43856\n     - dma: fix call order in dmam_free_coherent\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43884\n     - Bluetooth: MGMT: Add error handling to pair_device()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42309\n     - drm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50044\n     - Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49967\n     - ext4: no need to continue when the number of entries is 1\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-49015\n     - net: hsr: Fix potential use-after-free\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50033\n     - slip: make slhc_remember() more robust against malicious packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47670\n     - ocfs2: add bounds checking to ocfs2_xattr_find_entry()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49950\n     - Bluetooth: L2CAP: Fix uaf in l2cap_connect\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49883\n     - ext4: aovid use-after-free in ext4_ext_insert_extent()\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48960\n     - net: hisilicon: Fix potential use-after-free in hix5hd2_rx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47745\n     - mm: call the security_mmap_file() LSM hook in remap_file_pages()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49860\n     - ACPI: sysfs: validate return type of _STR method\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49882\n     - ext4: fix double brelse() the buffer of the extents path\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49995\n     - tipc: guard against string buffer overrun\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47723\n     - jfs: fix out-of-bounds in dbNextAG() and diAlloc()\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48988\n     - memcg: fix possible use-after-free in memcg_write_event_control()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50073\n     - tty: n_gsm: Fix use-after-free in gsm_cleanup_mux\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50055\n     - driver core: bus: Fix double free in driver API bus_register()\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-49029\n     - hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails\n   * Bionic update: upstream stable patchset 2023-02-06 (LP: #2006403) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48948\n     - usb: gadget: uvc: Prevent buffer overflow in setup handler\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47698\n     - drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49026\n     - e100: Fix possible use after free in e100_xmit_prepare\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48967\n     - NFC: nci: Bounds check struct nfc_target arrays\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47742\n     - firmware_loader: Block path traversal\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50035\n     - ppp: fix ppp_async_encode() illegal access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47757\n     - nilfs2: fix potential oob read in nilfs_btree_check_delete()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49884\n     - ext4: avoid ext4_error()'s caused by ENOMEM in the truncate path\n     - ext4: fix slab-use-after-free in ext4_split_extent_at()\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49006\n     - tracing: Only have rmmod clear buffers that its events were active in\n     - tracing: Free buffers when a used dynamic event is removed\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49903\n     - jfs: Fix uaf in dbFreeBits\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47701\n     - ext4: avoid OOB when system.data xattr changes underneath the filesystem\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49889\n     - ext4: avoid use-after-free in ext4_ext_show_leaf()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49900\n     - jfs: Fix uninit-value access of new_ea in ea_buffer\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47697\n     - drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48951\n     - ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43839\n     - bna: adjust 'name' buf size of bna_tcb and bna_ccb structures\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47659\n     - smack: tcp: ipv4, fix incorrect labeling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47685\n     - netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38602\n     - ax25: Fix reference count leak issues of ax25_dev\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26641\n     - net: Fix unwanted sign extension in netdev_stats_to_stats64()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42223\n     - media: dvb-frontends: tda10048: Fix integer overflow\n   * CVE-url: https://ubuntu.com/security/CVE-2021-3759\n     - memcg: enable accounting of ipc resources\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38632\n     - vfio/pci: fix potential memory leak in vfio_intx_enable()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46840\n     - btrfs: clean up our handling of refs == 0 in snapshot delete\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44954\n     - ALSA: line6: Fix racy access to midibuf\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45003\n     - vfs: Don't evict inode under the inode lru traversing context\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46841\n     - btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in\n       walk_down_proc()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44950\n     - serial: sc16is7xx: fix invalid FIFO access with special register set\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26812\n     - Revert \"kernfs: do not account ino_ida allocations to memcg\"\n     - Revert \"gfp: add __GFP_NOACCOUNT\"\n     - memcg: only account kmem allocations marked as __GFP_ACCOUNT\n     - vfio: Introduce interface to flush virqfd inject workqueue\n     - vfio/pci: Create persistent INTx handler\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52528\n     - usbnet/smsc75xx: silence uninitialized variable warning\n     - net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42229\n     - crypto: aead,cipher - zeroize key buffer after use","status":"published","published":"2024-11-14T17:36:06Z","modified":"2026-06-04T10:03:39.319447458Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1731606243","title":"Fix of 67 CVEs","description":"   * CVE-url: https://ubuntu.com/security/CVE-2024-42265\n     - protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47669\n     - nilfs2: fix state management in error path of log writing function\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52918\n     - media: pci: cx23885: check cx23885_vdev_init() return\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46750\n     - PCI: Add missing bridge lock to pci_bus_lock()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46676\n     - nfc: pn533: Add poll mod list filling check\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46755\n     - wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46721\n     - apparmor: fix possible NULL pointer dereference\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44947\n     - fuse: Initialize beyond-EOF page contents before setting uptodate\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46675\n     - usb: dwc3: core: Prevent USB core invalid event buffer address access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43893\n     - serial: core: check uartclk for zero to avoid divide by zero\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45021\n     - memcg_write_event_control(): fix a user-triggerable oops\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41012\n     - filelock: Remove locks reliably when fcntl/close race is detected\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42310\n     - drm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42311\n     - hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45028\n     - mmc: mmc_test: Fix NULL dereference on allocation failure\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43914\n     - md/raid5: avoid BUG_ON() while continue reshape after reassembling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43856\n     - dma: fix call order in dmam_free_coherent\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43884\n     - Bluetooth: MGMT: Add error handling to pair_device()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42309\n     - drm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50044\n     - Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49967\n     - ext4: no need to continue when the number of entries is 1\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-49015\n     - net: hsr: Fix potential use-after-free\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50033\n     - slip: make slhc_remember() more robust against malicious packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47670\n     - ocfs2: add bounds checking to ocfs2_xattr_find_entry()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49950\n     - Bluetooth: L2CAP: Fix uaf in l2cap_connect\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49883\n     - ext4: aovid use-after-free in ext4_ext_insert_extent()\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48960\n     - net: hisilicon: Fix potential use-after-free in hix5hd2_rx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47745\n     - mm: call the security_mmap_file() LSM hook in remap_file_pages()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49860\n     - ACPI: sysfs: validate return type of _STR method\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49882\n     - ext4: fix double brelse() the buffer of the extents path\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49995\n     - tipc: guard against string buffer overrun\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47723\n     - jfs: fix out-of-bounds in dbNextAG() and diAlloc()\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48988\n     - memcg: fix possible use-after-free in memcg_write_event_control()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50073\n     - tty: n_gsm: Fix use-after-free in gsm_cleanup_mux\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50055\n     - driver core: bus: Fix double free in driver API bus_register()\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-49029\n     - hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails\n   * Bionic update: upstream stable patchset 2023-02-06 (LP: #2006403) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48948\n     - usb: gadget: uvc: Prevent buffer overflow in setup handler\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47698\n     - drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49026\n     - e100: Fix possible use after free in e100_xmit_prepare\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596) // CVE-\n     url: https://ubuntu.com/security/CVE-2022-48967\n     - NFC: nci: Bounds check struct nfc_target arrays\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47742\n     - firmware_loader: Block path traversal\n   * CVE-url: https://ubuntu.com/security/CVE-2024-50035\n     - ppp: fix ppp_async_encode() illegal access\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47757\n     - nilfs2: fix potential oob read in nilfs_btree_check_delete()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49884\n     - ext4: avoid ext4_error()'s caused by ENOMEM in the truncate path\n     - ext4: fix slab-use-after-free in ext4_split_extent_at()\n   * CVE-url: https://ubuntu.com/security/CVE-2022-49006\n     - tracing: Only have rmmod clear buffers that its events were active in\n     - tracing: Free buffers when a used dynamic event is removed\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49903\n     - jfs: Fix uaf in dbFreeBits\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47701\n     - ext4: avoid OOB when system.data xattr changes underneath the filesystem\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49889\n     - ext4: avoid use-after-free in ext4_ext_show_leaf()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-49900\n     - jfs: Fix uninit-value access of new_ea in ea_buffer\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47697\n     - drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48951\n     - ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43839\n     - bna: adjust 'name' buf size of bna_tcb and bna_ccb structures\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47659\n     - smack: tcp: ipv4, fix incorrect labeling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-47685\n     - netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38602\n     - ax25: Fix reference count leak issues of ax25_dev\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26641\n     - net: Fix unwanted sign extension in netdev_stats_to_stats64()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42223\n     - media: dvb-frontends: tda10048: Fix integer overflow\n   * CVE-url: https://ubuntu.com/security/CVE-2021-3759\n     - memcg: enable accounting of ipc resources\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38632\n     - vfio/pci: fix potential memory leak in vfio_intx_enable()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46840\n     - btrfs: clean up our handling of refs == 0 in snapshot delete\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44954\n     - ALSA: line6: Fix racy access to midibuf\n   * CVE-url: https://ubuntu.com/security/CVE-2024-45003\n     - vfs: Don't evict inode under the inode lru traversing context\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46841\n     - btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in\n       walk_down_proc()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44950\n     - serial: sc16is7xx: fix invalid FIFO access with special register set\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26812\n     - Revert \"kernfs: do not account ino_ida allocations to memcg\"\n     - Revert \"gfp: add __GFP_NOACCOUNT\"\n     - memcg: only account kmem allocations marked as __GFP_ACCOUNT\n     - vfio: Introduce interface to flush virqfd inject workqueue\n     - vfio/pci: Create persistent INTx handler\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52528\n     - usbnet/smsc75xx: silence uninitialized variable warning\n     - net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42229\n     - crypto: aead,cipher - zeroize key buffer after use","status":"published","published":"2024-11-14T17:44:09Z","modified":"2026-06-04T10:03:39.018055039Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"DLA-3912-1","title":"linux - security update","status":"published","published":"2024-10-07T00:00:00Z","modified":"2026-03-09T01:20:34.748332Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"DLA-4008-1","title":"linux-6.1 - security update","status":"published","published":"2025-01-02T00:00:00Z","modified":"2026-03-09T02:11:41.013831Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"DSA-5782-1","title":"linux - security update","status":"published","published":"2024-10-03T00:00:00Z","modified":"2026-03-09T02:09:56.413752Z","updated_at":"2026-11-02T15:46:17.892347Z"},{"id":"SUSE-SU-2024:3547-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)\n- CVE-2024-41087: Fix double free on error (bsc#1228466).\n- CVE-2024-42301: Fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-46674: usb: dwc3: st: fix probed platform device ref count on probe  error path (bsc#1230507).\n\nThe following non-security bugs were fixed:\n\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223). \n- scsi: smartpqi: Expose SAS address for SATA drives (bsc#1223958).\n- SUNRPC: avoid soft lockup when transmitting UDP to reachable server (bsc#1225272 bsc#1231016).\n","status":"published","published":"2024-10-08T14:06:33Z","modified":"2026-02-04T02:38:17.230105Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3551-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- Drop soundwire patch that caused a regression (bsc#1230350)\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- Move s390 kabi patch into the kabi section\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- Revert 'drm/amdgpu: align pp_power_profile_mode with kernel docs' (stable-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section'  (bsc#1230413)\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage' (bsc#1230413)\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()' (bsc#1230413)\n- Split kabi part of dm_blk_ioctl-implement-path-failover-for-SG_IO.patch\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) Move patch into the sorted section.\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Split kABI out of 'io_uring/kbuf: get rid of bl-\u003eis_ready'\n- kABI: Split kABI out of 'io_uring: Re-add dummy_ubuf for kABI purposes'\n- kABI: Split kABI out of io_uring/kbuf: protect io_buffer_list teardown with a reference\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-08T15:03:16Z","modified":"2026-02-04T03:53:54.665546Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3553-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 CoCo kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46727: Fixed NULL pointer dereference in resource_log_pipe_topology_update (bsc#1230707).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- Drop soundwire patch that caused a regression (bsc#1230350) \n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) \n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section' \n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage' \n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- Squashfs: sanity check symbolic link size (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-08T15:10:23Z","modified":"2026-02-04T02:15:47.571482Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3561-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- Revert 'drm/amdgpu: align pp_power_profile_mode with kernel docs' (stable-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage'\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()'\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-09T08:45:13Z","modified":"2026-02-04T03:42:46.6666Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3563-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)\n- CVE-2024-42301: Fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-46674: usb: dwc3: st: fix probed platform device ref count on probe  error path (bsc#1230507).\n\nThe following non-security bugs were fixed:\n\n- SUNRPC: avoid soft lockup when transmitting UDP to reachable server (bsc#1225272 bsc#1231016).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: smartpqi: Expose SAS address for SATA drives (bsc#1223958).\n","status":"published","published":"2024-10-09T09:04:25Z","modified":"2025-05-02T04:34:03.754517Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3564-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Merge branch 'SLE15-SP6' (ea7c56db3e5d) into 'SLE15-SP6-RT'\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- No -rt specific changes this merge.\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- Revert 'drm/amdgpu: align pp_power_profile_mode with kernel docs' (stable-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage'\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()'\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Split kABI out of 'io_uring/kbuf: get rid of bl-\u003eis_ready'\n- kABI: Split kABI out of 'io_uring: Re-add dummy_ubuf for kABI purposes'\n- kABI: Split kABI out of io_uring/kbuf: protect io_buffer_list teardown with a reference\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-09T09:09:06Z","modified":"2026-02-04T02:58:51.061674Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3565-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP2 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2022-48945: media: vivid: fix compose size exceed boundary (bsc#1230398).\n- CVE-2024-36971: net: fix __dst_negative_advice() race (bsc#1226145).\n- CVE-2024-41087: Fix double free on error (bsc#1228466).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-46695: selinux,smack: do not bypass permissions check in inode_setsecctx  hook (bsc#1230519).\n\nThe following non-security bugs were fixed:\n\n- Revert 'ext4: consolidate checks for resize of bigalloc into ext4_resize_begin' (bsc#1230326).\n- ext4: add check to prevent attempting to resize an fs with sparse_super2 (bsc#1230326).\n- ext4: add reserved GDT blocks check (bsc#1230326).\n- ext4: consolidate checks for resize of bigalloc into ext4_resize_begin (bsc#1230326).\n- ext4: fix bug_on ext4_mb_use_inode_pa (bsc#1230326).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n","status":"published","published":"2024-10-09T09:40:48Z","modified":"2025-05-02T04:32:07.802367Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3567-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48945: media: vivid: fix compose size exceed boundary (bsc#1230398).\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-46695: selinux,smack: do not bypass permissions check in inode_setsecctx  hook (bsc#1230519).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n\nThe following non-security bugs were fixed:\n\n- ext4: add check to prevent attempting to resize an fs with sparse_super2 (bsc#1230326).\n- ext4: add reserved GDT blocks check (bsc#1230326).\n- ext4: consolidate checks for resize of bigalloc into ext4_resize_begin (bsc#1230326).\n- ext4: fix bug_on ext4_mb_use_inode_pa (bsc#1230326).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n- No -rt specific changes this merge.\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- Revert 'ext4: consolidate checks for resize of bigalloc into ext4_resize_begin' (bsc#1230326).\n","status":"published","published":"2024-10-09T09:46:04Z","modified":"2026-02-04T03:03:51.078233Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3569-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48901: btrfs: do not start relocation until in progress drops are done  (bsc#1229607).\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)\n- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26767: drm/amd/display: fixed integer types and null check locations  (bsc#1230339).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-26837: net: bridge: switchdev: race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).\n- CVE-2024-37353: virtio: fixed a double free in vp_del_vqs() (bsc#1226875).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command  (bsc#1228620 CVE-2024-41082).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42259: Fix Virtual Memory mapping boundaries calculation (bsc#1229156)\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43912: wifi: nl80211: disallow setting special AP channel widths (bsc#1229830)\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44952: driver core: Fix uevent_show() vs driver detach race  (bsc#1230178).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44986: ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230230)\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45007: char: xillybus: Refine workqueue handling (bsc#1230175).\n- CVE-2024-45008: Input: MT - limit max slots (bsc#1230248).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45015: drm/msm/dpu: move dpu_encoder's connector assignment to (bsc#1230444)\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46674: usb: dwc3: st: fix probed platform device ref count on probe  error path (bsc#1230507).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46685: pinctrl: single: fix potential NULL dereference in pcs_get_function() (bsc#1230515)\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46689: soc: qcom: cmd-db: Map shared memory as WC, not WB (bsc#1230524)\n- CVE-2024-46702: thunderbolt: Mark XDomain as unplugged when router is removed (bsc#1230589)\n- CVE-2024-46707: KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3  (bsc#1230582).\n- CVE-2024-46715: driver: iio: add missing checks on iio_info's callback access  (bsc#1230700).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46721: pparmor: fix possible NULL pointer dereference (bsc#1230710)\n- CVE-2024-46728: drm/amd/display: Check index for aux_rd_interval before using (bsc#1230703)\n- CVE-2024-46730: drm/amd/display: Ensure array index tg_inst won't be -1 (bsc#1230701)\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n- CVE-2024-46830: KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS  (bsc#1231116).\n\nThe following non-security bugs were fixed:\n\n- ACPI: battery: create alarm sysfs attribute atomically (git-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (git-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- af_unix: annotate lockless accesses to sk-\u003esk_err (bsc#1226846).\n- af_unix: Fix data races around sk-\u003esk_shutdown (bsc#1226846).\n- af_unix: Fix data-races around sk-\u003esk_shutdown (git-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/conexant: Mute speakers at suspend / shutdown (stable-fixes).\n- ALSA: hda/generic: Add a helper to mute speakers at suspend/shutdown (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- apparmor: fix possible NULL pointer dereference (stable-fixes).\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: add number of queue calc helper (bsc#1229034).\n- blk-mq: Build default queue map via group_cpus_evenly() (bsc#1229031).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- blk-mq: introduce blk_mq_dev_map_queues (bsc#1229034).\n- blk-mq: issue warning when offlining hctx with online isolcpus (bsc#1229034).\n- blk-mq: use hk cpus only when isolcpus=io_queue is enabled (bsc#1229034).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231181).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231013).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231180).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: virtio - Handle dataq logic with tasklet (git-fixes).\n- crypto: virtio - Wait for tasklet to complete on device remove (git-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- driver core: Add debug logs when fwnode links are added/deleted (git-fixes).\n- driver core: Add missing parameter description to __fwnode_link_add() (git-fixes).\n- driver core: Create __fwnode_link_del() helper function (git-fixes).\n- driver core: fw_devlink: Allow marking a fwnode link as being part of a cycle (git-fixes).\n- driver core: fw_devlink: Consolidate device link flag computation (git-fixes).\n- driver core: Set deferred probe reason when deferred by driver core (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/disp/dpu: use atomic enable/disable callbacks for encoder (bsc#1230444)\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- filemap: remove use of wait bookmarks (bsc#1224085).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230592).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230130).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230129).\n- genirq/affinity: Do not pass irq_affinity_desc array to irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Move group_cpus_evenly() into lib/ (bsc#1229031).\n- genirq/affinity: Only build SMP-only helper functions on SMP kernels (bsc#1229031).\n- genirq/affinity: Pass affinity managed mask array to irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Remove the 'firstvec' parameter from irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Rename irq_build_affinity_masks as group_cpus_evenly (bsc#1229031).\n- genirq/affinity: Replace cpumask_weight() with cpumask_empty() where appropriate (bsc#1229031).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- IB/hfi1: Fix potential deadlock on \u0026irq_src_lock and \u0026dd-\u003euctxt_lock (git-fixes)\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- Input: ilitek_ts_i2c - add report id message validation (git-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) \n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n- kABI, crypto: virtio - Handle dataq logic with tasklet (git-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1229031).\n- lib/group_cpus.c: honor housekeeping config when grouping CPUs (bsc#1229034).\n- lib/group_cpus: Export group_cpus_evenly() (bsc#1229031).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: aspeed: Fix no complete irq for non-64-aligned width (bsc#1230269)\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Fix ordering of pm_runtime_enable (git-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- nf_conntrack_proto_udp: do not accept packets with IPS_NAT_CLASH (bsc#1199769).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFS: Do not re-read the entire page cache to find the next cookie (bsc#1226662).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFS: Reduce use of uncached readdir (bsc#1226662).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- nilfs2: Constify struct kobj_type (git-fixes).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nilfs2: replace snprintf in show functions with sysfs_emit (git-fixes).\n- nilfs2: use default_groups in kobj_type (git-fixes).\n- nvme: move stopping keep-alive into nvme_uninit_ctrl() (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: use block layer helpers to calculate num of queues (bsc#1229034).\n- nvme: replace blk_mq_pci_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (git-fixes).\n- PCI/ASPM: Move pci_function_0() upward (bsc#1226915)\n- PCI/ASPM: Remove struct aspm_latency (bsc#1226915)\n- PCI/ASPM: Stop caching device L0s, L1 acceptable exit latencies (bsc#1226915)\n- PCI/ASPM: Stop caching link L0s, L1 exit latencies (bsc#1226915)\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: dwc: Restore MSI Receiver mask during resume (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: Support BAR sizes up to 8TB (bsc#1231017)\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PCI: xilinx-nwl: Fix register misspelling (git-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Fix the problem of variable not initialized fully (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (stable-fixes).\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429).\n- scsi: pm8001: do not overwrite PCI queue mapping (bsc#1229034).\n- scsi: replace blk_mq_pci_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- scsi: use block layer helpers to calculate num of queues (bsc#1229034).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- Squashfs: sanity check symbolic link size (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/virtio: fix build (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- udp: fix receiving fraglist GSO packets (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (git-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (git-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: fix cyclical race on disconnect with work queue (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: uas: set host status byte on data completion error (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- usb: xhci: fix loss of data on Cadence xHC (git-fixes).\n- vhost: Add smp_rmb() in vhost_vq_avail_empty() (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- virito: add APIs for retrieving vq affinity (bsc#1229034).\n- virtio-blk: Ensure no requests in virtqueues before deleting vqs (git-fixes).\n- virtio: blk/scsi: use block layer helpers to calculate num of queues (bsc#1229034).\n- virtio: blk/scs: replace blk_mq_virtio_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- virtiofs: forbid newlines in tags (bsc#1230591).\n- virtio_net: checksum offloading handling fix (git-fixes).\n- virtio_net: Fix ''%d' directive writing between 1 and 11 bytes into a region of size 10' warnings (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio/vsock: fix logic which reduces credit update messages (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- vsock/virtio: add support for device suspend/resume (git-fixes).\n- vsock/virtio: factor our the code to initialize and delete VQs (git-fixes).\n- vsock/virtio: initialize the_virtio_vsock before using VQs (git-fixes).\n- vsock/virtio: remove socket from connected/bound list on shutdown (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: do not include bnobt blocks when reserving free block pool (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-09T11:52:12Z","modified":"2026-02-04T02:15:16.708757Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3585-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47069: Fixed a crash due to relying on a stack reference past its expiry in ipc/mqueue, ipc/msg, ipc/sem (bsc#1220826).\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2022-48945: media: vivid: fix compose size exceed boundary (bsc#1230398).\n- CVE-2024-41087: Fix double free on error (bsc#1228466).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-46695: selinux,smack: do not bypass permissions check in inode_setsecctx  hook (bsc#1230519).\n- CVE-2024-36971: Fixed __dst_negative_advice() race (bsc#1226145).\n\nThe following non-security bugs were fixed:\n\n- ext4: add check to prevent attempting to resize an fs with sparse_super2 (bsc#1230326).\n- ext4: add reserved GDT blocks check (bsc#1230326).\n- ext4: consolidate checks for resize of bigalloc into ext4_resize_begin (bsc#1230326).\n- ext4: fix bug_on ext4_mb_use_inode_pa (bsc#1230326).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- Revert 'ext4: consolidate checks for resize of bigalloc into ext4_resize_begin' (bsc#1230326).\n","status":"published","published":"2024-10-10T09:05:14Z","modified":"2026-02-04T02:38:26.149305Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3587-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48901: btrfs: do not start relocation until in progress drops are done  (bsc#1229607).\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)\n- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26767: drm/amd/display: fixed integer types and null check locations  (bsc#1230339).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-26837: net: bridge: switchdev: race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).\n- CVE-2024-37353: virtio: fixed a double free in vp_del_vqs() (bsc#1226875).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command  (bsc#1228620 CVE-2024-41082).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42259: Fix Virtual Memory mapping boundaries calculation (bsc#1229156)\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43912: wifi: nl80211: disallow setting special AP channel widths (bsc#1229830)\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44952: driver core: Fix uevent_show() vs driver detach race  (bsc#1230178).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44986: ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230230)\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45007: char: xillybus: Refine workqueue handling (bsc#1230175).\n- CVE-2024-45008: Input: MT - limit max slots (bsc#1230248).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45015: drm/msm/dpu: move dpu_encoder's connector assignment to (bsc#1230444)\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46674: usb: dwc3: st: fix probed platform device ref count on probe  error path (bsc#1230507).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46678: bonding: change ipsec_lock from spin lock to mutex (bsc#1230550).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46685: pinctrl: single: fix potential NULL dereference in pcs_get_function() (bsc#1230515)\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46689: soc: qcom: cmd-db: Map shared memory as WC, not WB (bsc#1230524)\n- CVE-2024-46702: thunderbolt: Mark XDomain as unplugged when router is removed (bsc#1230589)\n- CVE-2024-46707: KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3  (bsc#1230582).\n- CVE-2024-46715: driver: iio: add missing checks on iio_info's callback access  (bsc#1230700).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46721: pparmor: fix possible NULL pointer dereference (bsc#1230710)\n- CVE-2024-46728: drm/amd/display: Check index for aux_rd_interval before using (bsc#1230703)\n- CVE-2024-46730: drm/amd/display: Ensure array index tg_inst won't be -1 (bsc#1230701)\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46770: ice: Add netif_device_attach/detach into PF reset flow (bsc#1230763).\n- CVE-2024-46775: drm/amd/display: Validate function returns (bsc#1230774).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n- CVE-2024-46826: ELF: fix kernel.randomize_va_space double read (bsc#1231115).\n- CVE-2024-46830: KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS  (bsc#1231116).\n- CVE-2024-46854: net: dpaa: Pad packets to ETH_ZLEN (bsc#1231084).\n- CVE-2024-46855: netfilter: nft_socket: fix sk refcount leaks (bsc#1231085).\n- CVE-2024-46857: net/mlx5: Fix bridge mode operations when there are no VFs (bsc#1231087).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (git-fixes).\n- ACPI: battery: create alarm sysfs attribute atomically (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/conexant: Mute speakers at suspend / shutdown (stable-fixes).\n- ALSA: hda/generic: Add a helper to mute speakers at suspend/shutdown (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- IB/hfi1: Fix potential deadlock on \u0026irq_src_lock and \u0026dd-\u003euctxt_lock (git-fixes)\n- Input: ilitek_ts_i2c - add report id message validation (git-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KVM: s390: Fix SORTL and DFLTCC instruction format error in __insn32_query (git-fixes bsc#1231277).\n- NFS: Do not re-read the entire page cache to find the next cookie (bsc#1226662).\n- NFS: Reduce use of uncached readdir (bsc#1226662).\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- PCI/ASPM: Move pci_function_0() upward (bsc#1226915)\n- PCI/ASPM: Remove struct aspm_latency (bsc#1226915)\n- PCI/ASPM: Stop caching device L0s, L1 acceptable exit latencies (bsc#1226915)\n- PCI/ASPM: Stop caching link L0s, L1 exit latencies (bsc#1226915)\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Support BAR sizes up to 8TB (bsc#1231017)\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (git-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: dwc: Restore MSI Receiver mask during resume (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PCI: xilinx-nwl: Fix register misspelling (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Fix the problem of variable not initialized fully (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (stable-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section'.\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage'.\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()'.\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- af_unix: Fix data races around sk-\u003esk_shutdown (bsc#1226846).\n- af_unix: Fix data-races around sk-\u003esk_shutdown (git-fixes).\n- af_unix: annotate lockless accesses to sk-\u003esk_err (bsc#1226846).\n- apparmor: fix possible NULL pointer dereference (stable-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: Build default queue map via group_cpus_evenly() (bsc#1229031).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: add number of queue calc helper (bsc#1229034).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- blk-mq: introduce blk_mq_dev_map_queues (bsc#1229034).\n- blk-mq: issue warning when offlining hctx with online isolcpus (bsc#1229034).\n- blk-mq: use hk cpus only when isolcpus=io_queue is enabled (bsc#1229034).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231013).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231181).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231180).\n- char: tpm: Fix possible memory leak in tpm_bios_measurements_open() (git-fixes).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: virtio - Handle dataq logic with tasklet (git-fixes).\n- crypto: virtio - Wait for tasklet to complete on device remove (git-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- driver core: Add debug logs when fwnode links are added/deleted (git-fixes).\n- driver core: Add missing parameter description to __fwnode_link_add() (git-fixes).\n- driver core: Create __fwnode_link_del() helper function (git-fixes).\n- driver core: Set deferred probe reason when deferred by driver core (git-fixes).\n- driver core: fw_devlink: Allow marking a fwnode link as being part of a cycle (git-fixes).\n- driver core: fw_devlink: Consolidate device link flag computation (git-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/disp/dpu: use atomic enable/disable callbacks for encoder (bsc#1230444)\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- filemap: remove use of wait bookmarks (bsc#1224085).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230592).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230130).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230129).\n- genirq/affinity: Do not pass irq_affinity_desc array to irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Move group_cpus_evenly() into lib/ (bsc#1229031).\n- genirq/affinity: Only build SMP-only helper functions on SMP kernels (bsc#1229031).\n- genirq/affinity: Pass affinity managed mask array to irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Remove the 'firstvec' parameter from irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Rename irq_build_affinity_masks as group_cpus_evenly (bsc#1229031).\n- genirq/affinity: Replace cpumask_weight() with cpumask_empty() where appropriate (bsc#1229031).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI, crypto: virtio - Handle dataq logic with tasklet (git-fixes).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1229031).\n- lib/group_cpus.c: honor housekeeping config when grouping CPUs (bsc#1229034).\n- lib/group_cpus: Export group_cpus_evenly() (bsc#1229031).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: aspeed: Fix no complete irq for non-64-aligned width (bsc#1230269)\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Fix ordering of pm_runtime_enable (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: mana: Implement get_ringparam/set_ringparam for mana (bsc#1229891).\n- net: mana: Improve mana_set_channels() in low mem conditions (bsc#1230289).\n- net: missing check virtio (git-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- nf_conntrack_proto_udp: do not accept packets with IPS_NAT_CLASH (bsc#1199769).\n- nilfs2: Constify struct kobj_type (git-fixes).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nilfs2: replace snprintf in show functions with sysfs_emit (git-fixes).\n- nilfs2: use default_groups in kobj_type (git-fixes).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: use block layer helpers to calculate num of queues (bsc#1229034).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: move stopping keep-alive into nvme_uninit_ctrl() (git-fixes).\n- nvme: replace blk_mq_pci_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powerpc/64: Convert patch_instruction() to patch_u32() (bsc#1194869).\n- powerpc/boot: Handle allocation failure in simple_realloc() (bsc#1194869).\n- powerpc/boot: Only free if realloc() succeeds (bsc#1194869).\n- powerpc/code-patching: Add generic memory patching (bsc#1194869).\n- powerpc/code-patching: Consolidate and cache per-cpu patching context (bsc#1194869).\n- powerpc/code-patching: Do not call is_vmalloc_or_module_addr() without CONFIG_MODULES (bsc#1194869).\n- powerpc/code-patching: Fix error handling in do_patch_instruction() (bsc#1194869).\n- powerpc/code-patching: Fix oops with DEBUG_VM enabled (bsc#1194869).\n- powerpc/code-patching: Fix unmap_patch_area() error handling (bsc#1194869).\n- powerpc/code-patching: Perform hwsync in __patch_instruction() in case of failure (bsc#1194869).\n- powerpc/code-patching: Pre-map patch area (bsc#1194869).\n- powerpc/code-patching: Remove #ifdef CONFIG_STRICT_KERNEL_RWX (bsc#1194869).\n- powerpc/code-patching: Remove pr_debug()/pr_devel() messages and fix check() (bsc#1194869).\n- powerpc/code-patching: Reorganise do_patch_instruction() to ease error handling (bsc#1194869).\n- powerpc/code-patching: Speed up page mapping/unmapping (bsc#1194869).\n- powerpc/code-patching: Use WARN_ON and fix check in poking_init (bsc#1194869).\n- powerpc/code-patching: Use jump_label to check if poking_init() is done (bsc#1194869).\n- powerpc/code-patching: Use temporary mm for Radix MMU (bsc#1194869).\n- powerpc/code-patching: introduce patch_instructions() (bsc#1194869).\n- powerpc/ftrace: Use patch_instruction() return directly (bsc#1194869).\n- powerpc/imc-pmu: Fix use of mutex in IRQs disabled section (bsc#1054914 git-fixes).\n- powerpc/imc-pmu: Use the correct spinlock initializer (bsc#1054914 git-fixes).\n- powerpc/inst: Refactor ___get_user_instr() (bsc#1194869).\n- powerpc/lib: Add __init attribute to eligible functions (bsc#1194869).\n- powerpc/tlb: Add local flush for page given mm_struct and psize (bsc#1194869).\n- powerpc/vdso: Fix VDSO data access when running in a non-root time namespace (bsc#1194869).\n- powerpc/vdso: Merge vdso64 and vdso32 into a single directory (bsc#1194869).\n- powerpc/vdso: Rework VDSO32 makefile to add a prefix to object files (bsc#1194869).\n- powerpc/vdso: augment VDSO32 functions to support 64 bits build (bsc#1194869).\n- powerpc/xics: Check return value of kasprintf in icp_native_map_one_cpu (bsc#1194869).\n- powerpc/xmon: Fix disassembly CPU feature checks (bsc#1065729).\n- powerpc: Allow clearing and restoring registers independent of saved breakpoint state (bsc#1194869).\n- rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow (bsc#1226631).\n- rcu: Add rcutree.nohz_full_patience_delay to reduce nohz_full (bsc#1231327)\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/mm: Add cond_resched() to cmm_alloc/free_pages() (bsc#1228747).\n- sched/isolation: Prevent boot crash when the boot CPU is (bsc#1231327)\n- scsi: fnic: Move flush_work initialization out of if block (bsc#1230055).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429).\n- scsi: pm8001: do not overwrite PCI queue mapping (bsc#1229034).\n- scsi: replace blk_mq_pci_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- scsi: use block layer helpers to calculate num of queues (bsc#1229034).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/virtio: fix build (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- udp: fix receiving fraglist GSO packets (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (git-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (git-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: uas: set host status byte on data completion error (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usb: xhci: fix loss of data on Cadence xHC (git-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: fix cyclical race on disconnect with work queue (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost: Add smp_rmb() in vhost_vq_avail_empty() (git-fixes).\n- virito: add APIs for retrieving vq affinity (bsc#1229034).\n- virtio-blk: Ensure no requests in virtqueues before deleting vqs (git-fixes).\n- virtio/vsock: fix logic which reduces credit update messages (git-fixes).\n- virtio: blk/scs: replace blk_mq_virtio_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- virtio: blk/scsi: use block layer helpers to calculate num of queues (bsc#1229034).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio_net: Fix ''%d' directive writing between 1 and 11 bytes into a region of size 10' warnings (git-fixes).\n- virtio_net: checksum offloading handling fix (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1230591).\n- vsock/virtio: add support for device suspend/resume (git-fixes).\n- vsock/virtio: factor our the code to initialize and delete VQs (git-fixes).\n- vsock/virtio: initialize the_virtio_vsock before using VQs (git-fixes).\n- vsock/virtio: remove socket from connected/bound list on shutdown (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- workqueue: Avoid using isolated cpus' timers on (bsc#1231327)\n- workqueue: mark power efficient workqueue as unbounded if (bsc#1231327)\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: do not include bnobt blocks when reserving free block pool (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-10T13:29:54Z","modified":"2026-02-04T02:54:15.69694Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3592-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48901: btrfs: do not start relocation until in progress drops are done  (bsc#1229607).\n- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance.  (bsc#1229633).\n- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)\n- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26767: drm/amd/display: fixed integer types and null check locations  (bsc#1230339).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-26837: net: bridge: switchdev: race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).\n- CVE-2024-37353: virtio: fixed a double free in vp_del_vqs() (bsc#1226875).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command  (bsc#1228620 CVE-2024-41082).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42259: Fix Virtual Memory mapping boundaries calculation (bsc#1229156)\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43912: wifi: nl80211: disallow setting special AP channel widths (bsc#1229830)\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44952: driver core: Fix uevent_show() vs driver detach race  (bsc#1230178).\n- CVE-2024-44954: ALSA: line6: Fix racy access to midibuf (bsc#1230176).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44986: ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230230)\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45007: char: xillybus: Refine workqueue handling (bsc#1230175).\n- CVE-2024-45008: Input: MT - limit max slots (bsc#1230248).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45015: drm/msm/dpu: move dpu_encoder's connector assignment to (bsc#1230444)\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46674: usb: dwc3: st: fix probed platform device ref count on probe  error path (bsc#1230507).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46685: pinctrl: single: fix potential NULL dereference in pcs_get_function() (bsc#1230515)\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46689: soc: qcom: cmd-db: Map shared memory as WC, not WB (bsc#1230524)\n- CVE-2024-46702: thunderbolt: Mark XDomain as unplugged when router is removed (bsc#1230589)\n- CVE-2024-46707: KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3  (bsc#1230582).\n- CVE-2024-46715: driver: iio: add missing checks on iio_info's callback access  (bsc#1230700).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46721: pparmor: fix possible NULL pointer dereference (bsc#1230710)\n- CVE-2024-46728: drm/amd/display: Check index for aux_rd_interval before using (bsc#1230703)\n- CVE-2024-46730: drm/amd/display: Ensure array index tg_inst won't be -1 (bsc#1230701)\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46750: PCI: Add missing bridge lock to pci_bus_lock() (bsc#1230783).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n- CVE-2024-46830: KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS  (bsc#1231116).\n\nThe following non-security bugs were fixed:\n\n- ACPI: battery: create alarm sysfs attribute atomically (git-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (git-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- af_unix: annotate lockless accesses to sk-\u003esk_err (bsc#1226846).\n- af_unix: Fix data races around sk-\u003esk_shutdown (bsc#1226846).\n- af_unix: Fix data-races around sk-\u003esk_shutdown (git-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/conexant: Mute speakers at suspend / shutdown (stable-fixes).\n- ALSA: hda/generic: Add a helper to mute speakers at suspend/shutdown (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- apparmor: fix possible NULL pointer dereference (stable-fixes).\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: add number of queue calc helper (bsc#1229034).\n- blk-mq: Build default queue map via group_cpus_evenly() (bsc#1229031).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- blk-mq: introduce blk_mq_dev_map_queues (bsc#1229034).\n- blk-mq: issue warning when offlining hctx with online isolcpus (bsc#1229034).\n- blk-mq: use hk cpus only when isolcpus=io_queue is enabled (bsc#1229034).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231181).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231013).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231180).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: virtio - Handle dataq logic with tasklet (git-fixes).\n- crypto: virtio - Wait for tasklet to complete on device remove (git-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- driver core: Add debug logs when fwnode links are added/deleted (git-fixes).\n- driver core: Add missing parameter description to __fwnode_link_add() (git-fixes).\n- driver core: Create __fwnode_link_del() helper function (git-fixes).\n- driver core: fw_devlink: Allow marking a fwnode link as being part of a cycle (git-fixes).\n- driver core: fw_devlink: Consolidate device link flag computation (git-fixes).\n- driver core: Set deferred probe reason when deferred by driver core (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/disp/dpu: use atomic enable/disable callbacks for encoder (bsc#1230444)\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- filemap: remove use of wait bookmarks (bsc#1224085).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230592).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230130).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230129).\n- genirq/affinity: Do not pass irq_affinity_desc array to irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Move group_cpus_evenly() into lib/ (bsc#1229031).\n- genirq/affinity: Only build SMP-only helper functions on SMP kernels (bsc#1229031).\n- genirq/affinity: Pass affinity managed mask array to irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Remove the 'firstvec' parameter from irq_build_affinity_masks (bsc#1229031).\n- genirq/affinity: Rename irq_build_affinity_masks as group_cpus_evenly (bsc#1229031).\n- genirq/affinity: Replace cpumask_weight() with cpumask_empty() where appropriate (bsc#1229031).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- IB/hfi1: Fix potential deadlock on \u0026irq_src_lock and \u0026dd-\u003euctxt_lock (git-fixes)\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- Input: ilitek_ts_i2c - add report id message validation (git-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) \n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kabi: add __nf_queue_get_refs() for kabi compliance.\n- kABI, crypto: virtio - Handle dataq logic with tasklet (git-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1229031).\n- lib/group_cpus.c: honor housekeeping config when grouping CPUs (bsc#1229034).\n- lib/group_cpus: Export group_cpus_evenly() (bsc#1229031).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: aspeed: Fix no complete irq for non-64-aligned width (bsc#1230269)\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Fix ordering of pm_runtime_enable (git-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- nf_conntrack_proto_udp: do not accept packets with IPS_NAT_CLASH (bsc#1199769).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFS: Do not re-read the entire page cache to find the next cookie (bsc#1226662).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFS: Reduce use of uncached readdir (bsc#1226662).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- nilfs2: Constify struct kobj_type (git-fixes).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nilfs2: replace snprintf in show functions with sysfs_emit (git-fixes).\n- nilfs2: use default_groups in kobj_type (git-fixes).\n- nvme: move stopping keep-alive into nvme_uninit_ctrl() (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: use block layer helpers to calculate num of queues (bsc#1229034).\n- nvme: replace blk_mq_pci_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (git-fixes).\n- PCI/ASPM: Move pci_function_0() upward (bsc#1226915)\n- PCI/ASPM: Remove struct aspm_latency (bsc#1226915)\n- PCI/ASPM: Stop caching device L0s, L1 acceptable exit latencies (bsc#1226915)\n- PCI/ASPM: Stop caching link L0s, L1 exit latencies (bsc#1226915)\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: dwc: Restore MSI Receiver mask during resume (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: Support BAR sizes up to 8TB (bsc#1231017)\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PCI: xilinx-nwl: Fix register misspelling (git-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Fix the problem of variable not initialized fully (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (stable-fixes).\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429).\n- scsi: pm8001: do not overwrite PCI queue mapping (bsc#1229034).\n- scsi: replace blk_mq_pci_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- scsi: use block layer helpers to calculate num of queues (bsc#1229034).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- Squashfs: sanity check symbolic link size (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/virtio: fix build (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- udp: fix receiving fraglist GSO packets (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (git-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (git-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: fix cyclical race on disconnect with work queue (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: uas: set host status byte on data completion error (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- usb: xhci: fix loss of data on Cadence xHC (git-fixes).\n- vhost: Add smp_rmb() in vhost_vq_avail_empty() (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- virito: add APIs for retrieving vq affinity (bsc#1229034).\n- virtio-blk: Ensure no requests in virtqueues before deleting vqs (git-fixes).\n- virtio: blk/scsi: use block layer helpers to calculate num of queues (bsc#1229034).\n- virtio: blk/scs: replace blk_mq_virtio_map_queues with blk_mq_dev_map_queues (bsc#1229034).\n- virtiofs: forbid newlines in tags (bsc#1230591).\n- virtio_net: checksum offloading handling fix (git-fixes).\n- virtio_net: Fix ''%d' directive writing between 1 and 11 bytes into a region of size 10' warnings (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio/vsock: fix logic which reduces credit update messages (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- vsock/virtio: add support for device suspend/resume (git-fixes).\n- vsock/virtio: factor our the code to initialize and delete VQs (git-fixes).\n- vsock/virtio: initialize the_virtio_vsock before using VQs (git-fixes).\n- vsock/virtio: remove socket from connected/bound list on shutdown (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: do not include bnobt blocks when reserving free block pool (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-10T16:03:49Z","modified":"2026-02-04T03:02:41.70324Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3617-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 11 SP4 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-40902: jfs: xattr: fix buffer overflow for invalid xattr (bsc#1227764).\n- CVE-2024-42104: nilfs2: add missing check for inode numbers on directory entries  (bsc#1228654).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n\nThe following non-security bugs were fixed:\n\n- alarmtimer: Lock k_itimer during timer callback (bsc#1214298).\n- alarmtimers: Add alarm_forward functionality (bsc#1214298).\n- alarmtimers: Change alarmtimer functions to return alarmtimer_restart (bsc#1214298).\n- alarmtimers: Push rearming peroidic timers down into alamrtimer (bsc#1214298).\n- alarmtimers: Remove interval cap limit hack (bsc#1214298).\n- kABI fix for alarmtimer_restart functionality (bsc#1214298).\n- kABI fix update for alarm_forward (bsc#1214298).\n","status":"published","published":"2024-10-14T12:07:08Z","modified":"2026-02-04T03:28:38.082827Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2025:01983-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47670: can: peak_usb: fix use after free bugs (bsc#1241407).\n- CVE-2022-49139: Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt (bsc#1238032).\n- CVE-2022-49145: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data (bsc#1238162).\n- CVE-2022-49168: btrfs: do not clean up repair bio if submit fails (bsc#1238109).\n- CVE-2022-49190: kernel/resource: fix kfree() of bootmem memory again (bsc#1238130).\n- CVE-2022-49212: mtd: rawnand: atmel: fix refcount issue in atmel_nand_controller_init (bsc#1238331).\n- CVE-2022-49216: drm/tegra: Fix reference leak in tegra_dsi_ganged_probe (bsc#1238338).\n- CVE-2022-49235: ath9k_htc: fix uninit value bugs (bsc#1238333).\n- CVE-2022-49248: ALSA: firewire-lib: fix uninitialized flag for AV/C deferred transaction (bsc#1238284).\n- CVE-2022-49253: media: usb: go7007: s2250-board: fix leak in probe() (bsc#1238420).\n- CVE-2022-49320: dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type (bsc#1238394).\n- CVE-2022-49326: rtl818x: Prevent using not initialized queues (bsc#1238646).\n- CVE-2022-49371: driver core: fix deadlock in __device_attach (bsc#1238546).\n- CVE-2022-49382: soc: rockchip: Fix refcount leak in rockchip_grf_init (bsc#1238306).\n- CVE-2022-49396: phy: qcom-qmp: fix reset-controller leak on probe errors (bsc#1238289).\n- CVE-2022-49420: net: annotate races around sk-\u003esk_bound_dev_if (bsc#1238887).\n- CVE-2022-49441: tty: fix deadlock caused by calling printk() under tty_port-\u003elock (bsc#1238263).\n- CVE-2022-49445: pinctrl: renesas: core: Fix possible null-ptr-deref in sh_pfc_map_resources() (bsc#1238019).\n- CVE-2022-49460: PM / devfreq: rk3399_dmc: Disable edev on remove() (bsc#1238892).\n- CVE-2022-49467: drm: msm: fix possible memory leak in mdp5_crtc_cursor_set() (bsc#1238815).\n- CVE-2022-49474: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout (bsc#1238071).\n- CVE-2022-49491: drm/rockchip: vop: fix possible null-ptr-deref in vop_bind() (bsc#1238539).\n- CVE-2022-49503: ath9k_htc: fix potential out of bounds access with invalid rxstatus-\u003ers_keyix (bsc#1238868).\n- CVE-2022-49592: net: stmmac: fix dma queue left shift overflow issue (bsc#1238311).\n- CVE-2022-49625: sfc: fix kernel panic when creating VF (bsc#1238411).\n- CVE-2022-49635: drm/i915/selftests: fix subtraction overflow bug (bsc#1238806).\n- CVE-2022-49652: dmaengine: ti: Fix refcount leak in ti_dra7_xbar_route_allocate (bsc#1238871).\n- CVE-2022-49715: irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions (bsc#1238818).\n- CVE-2022-49728: kABI workaround for changeing the variable length type to size_t (bsc#1239111).\n- CVE-2022-49729: nfc: nfcmrvl: Fix memory leak in nfcmrvl_play_deferred (bsc#1239060).\n- CVE-2022-49751: w1: fix WARNING after calling w1_process() (bsc#1240254).\n- CVE-2022-49761: btrfs: always report error in run_one_delayed_ref() (bsc#1240261).\n- CVE-2022-49772: ALSA: usb-audio: Drop snd_BUG_ON() from snd_usbmidi_output_open() (bsc#1242147).\n- CVE-2022-49775: tcp: cdg: allow tcp_cdg_release() to be called multiple times (bsc#1242245).\n- CVE-2022-49776: macvlan: enforce a consistent minimal mtu (bsc#1242248).\n- CVE-2022-49787: mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put() (bsc#1242352).\n- CVE-2022-49788: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (bsc#1242353).\n- CVE-2022-49813: net: ena: Fix error handling in ena_init() (bsc#1242497).\n- CVE-2022-49821: mISDN: fix possible memory leak in mISDN_dsp_element_register() (bsc#1242542).\n- CVE-2022-49826: ata: libata-transport: fix double ata_host_put() in ata_tport_add() (bsc#1242549).\n- CVE-2022-49829: drm/scheduler: fix fence ref counting (bsc#1242691).\n- CVE-2022-49832: pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map (bsc#1242154).\n- CVE-2022-49835: ALSA: hda: fix potential memleak in 'add_widget_node' (bsc#1242385).\n- CVE-2022-49840: bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb() (bsc#1242447).\n- CVE-2022-49842: ASoC: soc-utils: Remove __exit for snd_soc_util_exit() (bsc#1242484).\n- CVE-2022-49853: net: macvlan: fix memory leaks of macvlan_common_newlink (bsc#1242688).\n- CVE-2022-49861: dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove() (bsc#1242580).\n- CVE-2022-49862: tipc: fix the msg-\u003ereq tlv len check in tipc_nl_compat_name_table_dump_header (bsc#1242755).\n- CVE-2022-49865: ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network (bsc#1242570).\n- CVE-2022-49871: net: tun: call napi_schedule_prep() to ensure we own a napi (bsc#1242558).\n- CVE-2022-49872: net: gso: fix panic on frag_list with mixed head alloc types (bsc#1242594).\n- CVE-2022-49874: HID: hyperv: fix possible memory leak in mousevsc_probe() (bsc#1242478).\n- CVE-2022-49898: btrfs: fix tree mod log mishandling of reallocated nodes (bsc#1242472).\n- CVE-2022-49907: net: mdio: fix undefined behavior in bit shift for __mdiobus_register (bsc#1242450).\n- CVE-2022-49913: btrfs: fix inode list leak during backref walking at find_parent_nodes() (bsc#1242470).\n- CVE-2022-49914: btrfs: fix inode list leak during backref walking at resolve_indirect_refs() (bsc#1242427).\n- CVE-2022-49922: nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() (bsc#1242378).\n- CVE-2022-49923: nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() (bsc#1242394).\n- CVE-2022-49924: nfc: fdp: Fix potential memory leak in fdp_nci_send() (bsc#1242426).\n- CVE-2022-49925: RDMA/core: Fix null-ptr-deref in ib_core_cleanup() (bsc#1242371).\n- CVE-2022-49931: IB/hfi1: Correctly move list in sc_disable() (bsc#1242382).\n- CVE-2023-52868: thermal: core: prevent potential string overflow (bsc#1225044).\n- CVE-2023-52975: scsi: iscsi_tcp: Fix UAF during logout when accessing the shost ipaddress (bsc#1240322).\n- CVE-2023-52988: ALSA: hda/via: Avoid potential array out-of-bound in add_secret_dac_path() (bsc#1240293).\n- CVE-2023-52989: firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region (bsc#1240266).\n- CVE-2023-52993: x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL (bsc#1240297).\n- CVE-2023-53039: HID: intel-ish-hid: ipc: Fix potential use-after-free in work function (bsc#1242745).\n- CVE-2023-53045: usb: gadget: u_audio: do not let userspace block driver unbind (bsc#1242756).\n- CVE-2023-53066: qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info (bsc#1242227).\n- CVE-2023-53079: net/mlx5: Fix steering rules cleanup (bsc#1242765).\n- CVE-2023-53080: xsk: Add missing overflow check in xdp_umem_reg (bsc#1242287).\n- CVE-2023-53094: tty: serial: fsl_lpuart: fix race on RX DMA shutdown (bsc#1242288).\n- CVE-2023-53103: bonding: Fix memory leak when changing bond type to Ethernet (bsc#1242408).\n- CVE-2023-53114: i40e: Fix kernel crash during reboot when adapter is in recovery mode (bsc#1242398).\n- CVE-2023-53139: nfc: fdp: add null check of devm_kmalloc_array in fdp_nci_i2c_read_device_properties (bsc#1242361).\n- CVE-2024-26740: Fixed use the backlog for mirred ingress  (bsc#1222563).\n- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-50106: nfsd: fix race between laundromat and free_stateid() (bsc#1232882).\n- CVE-2024-53168: sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (bsc#1234887).\n- CVE-2024-56779: nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur (bsc#1235632).\n- CVE-2025-21648: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (bsc#1236142).\n- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch-\u003elimit == 0 (bsc#1237312).\n- CVE-2025-21704: usb: cdc-acm: Check control transfer buffer size before access (bsc#1237571).\n- CVE-2025-21787: team: better TEAM_OPTION_TYPE_STRING validation (bsc#1238774).\n- CVE-2025-21814: ptp: Ensure info-\u003eenable callback is always set (bsc#1238473).\n- CVE-2025-22021: netfilter: socket: Lookup orig tuple for IPv6 SNAT (bsc#1241282).\n- CVE-2025-22027: media: streamzap: fix race between device disconnection and urb callback (bsc#1241369).\n- CVE-2025-22050: usbnet:fix NPE during rx_complete (bsc#1241441).\n- CVE-2025-22058: udp: Fix memory accounting leak (bsc#1241332).\n- CVE-2025-22060: net: mvpp2: Prevent parser TCAM memory corruption (bsc#1241526).\n- CVE-2025-22063: netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets (bsc#1241351).\n- CVE-2025-22104: ibmvnic: Use kernel helpers for hex dumps (bsc#1241550).\n- CVE-2025-23136: thermal: int340x: Add NULL check for adev (bsc#1241357).\n- CVE-2025-23150: ext4: fix off-by-one error in do_split (bsc#1242513).\n- CVE-2025-23161: PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type (bsc#1242792).\n- CVE-2025-37749: net: ppp: Add bound checking for skb data on ppp_sync_txmung (bsc#1242859).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37780: isofs: Prevent the use of too small fid (bsc#1242786).\n- CVE-2025-37782: hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key (bsc#1242770).\n- CVE-2025-37789: net: openvswitch: fix nested key length validation in the set() action (bsc#1242762).\n- CVE-2025-37794: wifi: mac80211: Purge vif txq in ieee80211_do_stop() (bsc#1242566).\n- CVE-2025-37796: wifi: at76c50x: fix use after free access in at76_disconnect (bsc#1242727).\n- CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).\n- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).\n- CVE-2025-37833: net/niu: Niu requires MSIX ENTRY_DATA fields touch before entry reads (bsc#1242868).\n- CVE-2025-37852: drm/amdgpu: handle amdgpu_cgs_create_device() errors in amd_powerplay_create() (bsc#1243074).\n- CVE-2025-37879: 9p/net: fix improper handling of bogus negative read/write replies (bsc#1243077).\n- CVE-2025-37949: xenbus: Use kref to track req lifetime (bsc#1243541).\n- CVE-2025-37989: net: phy: leds: fix memory leak (bsc#1243511).\n- CVE-2025-38637: net_sched: skbprio: Remove overly strict queue assertions (bsc#1241657).\n\nThe following non-security bugs were fixed:\n\n- HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev-\u003edevc (bsc#1242745).\n- NFC: nxp-nci: remove unnecessary labels (bsc#1242394).\n- arm64: bpf: Add BHB mitigation to the epilogue for cBPF programs (bsc#1242778).\n- arm64: bpf: Only mitigate cBPF programs loaded by unprivileged users (bsc#1242778).\n- arm64: insn: Add N immediate encoding (bsc#1242778).\n- arm64: insn: Add encoder for bitwise operations using literals (bsc#1242778).\n- arm64: insn: Add support for encoding DSB (bsc#1242778).\n- arm64: insn: Fix two bugs in encoding 32-bit logical immediates (bsc#1242778).\n- arm64: proton-pack: Add new CPUs 'k' values for branch mitigation (bsc#1242778).\n- arm64: proton-pack: Expose whether the branchy loop k value (bsc#1242778).\n- arm64: proton-pack: Expose whether the platform is mitigated by firmware (bsc#1242778).\n- devm-helpers: Add resource managed version of work init (bsc#1242745)\n- irqchip: gic-v3: Use of_cpu_node_to_id helper (bsc#1238818)\n- kernel: Remove debug flavor (bsc#1243919). \n- mtd: phram: Add the kernel lock down check (bsc#1232649).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- netfilter: Adjusted the backported patch as it caused a regression (bsc#1218752).\n- ocfs2: fix the issue with discontiguous allocation in the global_bitmap (git-fixes).\n- pinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map() (bsc#1242154)\n- workqueue: Add resource managed version of delayed work init (bsc#1242745)\n- x86/bugs: Cache the value of MSR_IA32_ARCH_CAPABILITIES (git-fixes).\n- x86/bugs: Fix BHI handling of RRSBA (git-fixes).\n- x86/bugs: Fix BHI retpoline check (git-fixes).\n- x86/bugs: Fix return type of spectre_bhi_state() (git-fixes).\n- x86/smpboot: Remove unused phys_id variable (git-commit).\n","status":"published","published":"2025-06-17T15:32:57Z","modified":"2026-02-04T02:45:15.700931Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:20073-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- Drop mm patches that caused regressions (bsc#1230413)\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- Move s390 kabi patch into the kabi section\n- Move upstreamed SCSI patches into sorted section\n- Move upstreamed input patch into sorted section\n- Move upstreamed kaslr patch into sorted section\n- Move upstreamed nvme patches into sorted section\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for \"dra7xx-pcie-main\" IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert \"afs: Hide silly-rename files from userspace\" (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Split kABI out of 'io_uring/kbuf: get rid of bl-\u003eis_ready'\n- kABI: Split kABI out of 'io_uring: Re-add dummy_ubuf for kABI purposes'\n- kABI: Split kABI out of io_uring/kbuf: protect io_buffer_list teardown with a reference \n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for \"/tmp/perf-$PID.map\" files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2025-02-03T09:04:16Z","modified":"2026-03-23T04:50:03.63945Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20077-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- Drop mm patches that caused regressions (bsc#1230413)\n- Enable livepatching related packages on -RT (jsc#PED-1706)\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Merge branch 'ALP-current' (0e26fa94003b) into 'ALP-current-RT'\n- Move fixes into sorted section (bsc#1230119)\n- Move s390 kabi patch into the kabi section\n- Move upstreamed SCSI patches into sorted section\n- Move upstreamed input patch into sorted section\n- Move upstreamed kaslr patch into sorted section\n- Move upstreamed nvme patches into sorted section\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- No -rt specific changes this merge.\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for \"dra7xx-pcie-main\" IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Replace git-fixes tag by bsc#1226507, patches.suse/md-Don-t-wait-for-MD_RECOVERY_NEEDED-for-HOT_REMOVE_DISK-ioctl-a1fd.patch (bsc#1226507).\n- Resort io_uring kABI patches These ended up in the wrong section. Push them to the right place, next to the other io_uring kabi patches.\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert \"Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE\" (git-fixes).\n- Revert \"PCI: Extend ACS configurability (bsc#1228090).\" (bsc#1229019) This reverts commit 571e4310e81312c847a5caee7e45e66aeea2a169. It breaks ACS on certain platforms. Even 6.11 is affected. So drop for now and investigate.\n- Revert \"drm/amdgpu: align pp_power_profile_mode with kernel docs\" (stable-fixes).\n- Revert \"media: tuners: fix error return code of hybrid_tuner_request_state()\" (git-fixes).\n- Revert \"mm, kmsan: fix infinite recursion due to RCU critical section\" This reverts commit 16ad73a9f4c2888f3bc28513f5e9a88d753f8741.\n- Revert \"mm/sparsemem: fix race in accessing memory_section-\u003eusage\" This reverts commit 6aa8957889611fbe7f06353f917cfb3d9620a680.\n- Revert \"mm: prevent derefencing NULL ptr in pfn_section_valid()\" This reverts commit 35f619d3c421219e07bc89d2d6a37fbff25519fe.\n- Split kabi part of dm_blk_ioctl-implement-path-failover-for-SG_IO.patch\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- Update patches.suse/af_unix-Fix-data-races-around-sk-sk_shutdown.patch (git-fixes bsc#1226846).\n- Update patches.suse/gfs2-Fix-NULL-pointer-dereference-in-gfs2_log_flush.patch (bsc#1230948)\n- Update patches.suse/powerpc-pseries-make-max-polling-consistent-for-long.patch (bsc#1215199 jsc#PED-10954).\n- Update patches.suse/security-integrity-fix-pointer-to-ESL-data-and-.patch (bsc#1012628 jsc#PED-5085 jsc#PED-10954).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert \"afs: Hide silly-rename files from userspace\" (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blacklist.conf: (\"KVM: arm64: Use TLBI_TTL_UNKNOWN in __kvm_tlb_flush_vmid_range()\") (bsc#1229585)\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) Move patch into the sorted section.\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Workaround kABI change in patches.suse/iommu-dma-Trace-bounce-buffer-usage-when-mapping-buf.patch (git-fixes).\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for \"/tmp/perf-$PID.map\" files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2025-02-03T09:05:12Z","modified":"2026-03-23T04:48:52.78816Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"USN-7088-1","title":"linux, linux-gcp, linux-gcp-5.4, linux-gkeop, linux-hwe-5.4, linux-ibm, linux-ibm-5.4 vulnerabilities","description":"\nZiming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux\nkernel contained an integer overflow vulnerability. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2022-36402)\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  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - CPU frequency scaling framework;\n  - Device frequency scaling framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB subsystem;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - BPF subsystem;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-43894, CVE-2024-46737, CVE-2024-46828, CVE-2024-42244,\nCVE-2024-46723, CVE-2024-41073, CVE-2024-46756, CVE-2024-42288,\nCVE-2024-46840, CVE-2024-46771, CVE-2024-46757, CVE-2024-43860,\nCVE-2024-46747, CVE-2024-41017, CVE-2024-42246, CVE-2024-44988,\nCVE-2024-42281, CVE-2024-36484, CVE-2024-43856, CVE-2024-47668,\nCVE-2024-46759, CVE-2024-46744, CVE-2024-42289, CVE-2024-42131,\nCVE-2024-46679, CVE-2024-42304, CVE-2024-46818, CVE-2024-43858,\nCVE-2024-44960, CVE-2024-45028, CVE-2024-26885, CVE-2024-46676,\nCVE-2024-46780, CVE-2024-42310, CVE-2024-44987, CVE-2024-41090,\nCVE-2024-44954, CVE-2024-45026, CVE-2024-42285, CVE-2023-52614,\nCVE-2024-27051, CVE-2024-43880, CVE-2024-43839, CVE-2024-43884,\nCVE-2024-42311, CVE-2024-43893, CVE-2024-41072, CVE-2024-41091,\nCVE-2024-46758, CVE-2024-41022, CVE-2024-46745, CVE-2024-42305,\nCVE-2024-46673, CVE-2024-42284, CVE-2024-46844, CVE-2024-46677,\nCVE-2024-45025, CVE-2024-43861, CVE-2024-43914, CVE-2024-46783,\nCVE-2024-41012, CVE-2024-44999, CVE-2024-44946, CVE-2024-42276,\nCVE-2024-46740, CVE-2024-42295, CVE-2024-44947, CVE-2024-41059,\nCVE-2024-26669, CVE-2024-38602, CVE-2024-42306, CVE-2023-52918,\nCVE-2024-42297, CVE-2024-42229, CVE-2024-43853, CVE-2024-45006,\nCVE-2024-44998, CVE-2024-42283, CVE-2024-44952, CVE-2024-46761,\nCVE-2024-43841, CVE-2024-44944, CVE-2024-42313, CVE-2024-45008,\nCVE-2024-46714, CVE-2024-41065, CVE-2024-43883, CVE-2024-43867,\nCVE-2024-42286, CVE-2024-43879, CVE-2024-43846, CVE-2024-42280,\nCVE-2024-43854, CVE-2021-47212, CVE-2024-35848, CVE-2024-41020,\nCVE-2024-41068, CVE-2024-45021, CVE-2024-41098, CVE-2024-44965,\nCVE-2024-43890, CVE-2024-45003, CVE-2024-44969, CVE-2024-41011,\nCVE-2024-46738, CVE-2024-41071, CVE-2024-26800, CVE-2024-46721,\nCVE-2024-42292, CVE-2024-41081, CVE-2024-44948, CVE-2023-52531,\nCVE-2024-26891, CVE-2024-26641, CVE-2024-42287, CVE-2024-46722,\nCVE-2024-41042, CVE-2024-46675, CVE-2024-46743, CVE-2024-42259,\nCVE-2024-41015, CVE-2024-43908, CVE-2024-46719, CVE-2024-43871,\nCVE-2024-46739, CVE-2024-42301, CVE-2024-47659, CVE-2024-42271,\nCVE-2024-26668, CVE-2024-43835, CVE-2024-46829, CVE-2024-47667,\nCVE-2024-44995, CVE-2024-47669, CVE-2024-38611, CVE-2024-40929,\nCVE-2024-46815, CVE-2024-43830, CVE-2024-42309, CVE-2024-41063,\nCVE-2024-46782, CVE-2024-46777, CVE-2024-42265, CVE-2024-46781,\nCVE-2024-26607, CVE-2024-41064, CVE-2024-46685, CVE-2024-43882,\nCVE-2024-44935, CVE-2024-46800, CVE-2024-46822, CVE-2024-46755,\nCVE-2024-46817, CVE-2024-43829, CVE-2024-46798, CVE-2024-46689,\nCVE-2024-42290, CVE-2024-46750, CVE-2024-26640, CVE-2024-47663,\nCVE-2024-41070)\n","status":"published","published":"2024-10-31T15:50:57Z","modified":"2026-10-29T20:03:57.856869293Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7088-2","title":"linux-azure, linux-bluefield vulnerabilities","description":"\nZiming Zhang discovered that the VMware Virtual GPU DRM driver in the\nLinux kernel contained an integer overflow vulnerability. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2022-36402)\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  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - CPU frequency scaling framework;\n  - Device frequency scaling framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - BPF subsystem;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-46714, CVE-2024-42288, CVE-2024-42290, CVE-2024-44987,\nCVE-2024-41090, CVE-2024-42313, CVE-2024-46689, CVE-2024-46737,\nCVE-2024-44946, CVE-2024-44999, CVE-2024-44935, CVE-2024-38602,\nCVE-2024-43883, CVE-2024-26607, CVE-2024-41091, CVE-2024-45025,\nCVE-2024-42305, CVE-2024-26891, CVE-2024-41073, CVE-2024-44969,\nCVE-2024-26641, CVE-2024-46719, CVE-2024-40929, CVE-2024-46721,\nCVE-2024-46740, CVE-2024-41012, CVE-2024-42280, CVE-2024-46738,\nCVE-2024-46722, CVE-2024-42246, CVE-2024-41063, CVE-2024-41072,\nCVE-2024-41068, CVE-2024-43884, CVE-2024-46758, CVE-2024-43861,\nCVE-2024-42306, CVE-2024-42285, CVE-2024-41065, CVE-2024-46818,\nCVE-2024-43894, CVE-2024-44954, CVE-2024-42310, CVE-2024-46829,\nCVE-2023-52614, CVE-2024-47663, CVE-2024-42281, CVE-2024-42297,\nCVE-2024-46800, CVE-2024-44960, CVE-2024-44952, CVE-2024-46747,\nCVE-2024-42286, CVE-2024-41071, CVE-2024-43893, CVE-2023-52531,\nCVE-2024-43860, CVE-2024-46840, CVE-2024-41011, CVE-2024-43890,\nCVE-2024-45026, CVE-2024-42292, CVE-2024-27051, CVE-2024-41015,\nCVE-2024-47668, CVE-2024-46817, CVE-2024-43846, CVE-2024-44988,\nCVE-2024-44944, CVE-2024-43829, CVE-2024-45021, CVE-2024-43914,\nCVE-2024-43856, CVE-2024-46673, CVE-2024-46771, CVE-2024-41081,\nCVE-2024-43830, CVE-2024-43839, CVE-2024-43853, CVE-2024-47669,\nCVE-2024-42244, CVE-2021-47212, CVE-2024-46844, CVE-2024-44965,\nCVE-2024-41059, CVE-2024-46783, CVE-2024-42295, CVE-2024-35848,\nCVE-2024-41017, CVE-2024-47659, CVE-2024-42309, CVE-2024-26800,\nCVE-2024-41064, CVE-2024-43879, CVE-2024-46679, CVE-2024-43854,\nCVE-2024-41022, CVE-2024-43858, CVE-2024-46739, CVE-2024-46685,\nCVE-2024-42289, CVE-2024-44998, CVE-2024-46761, CVE-2024-46677,\nCVE-2024-42131, CVE-2024-46815, CVE-2024-46777, CVE-2024-43880,\nCVE-2024-42276, CVE-2024-42265, CVE-2024-46723, CVE-2024-42259,\nCVE-2024-45028, CVE-2024-42229, CVE-2024-42283, CVE-2024-44948,\nCVE-2024-44995, CVE-2024-46757, CVE-2024-46822, CVE-2024-45006,\nCVE-2024-46780, CVE-2024-26668, CVE-2024-42284, CVE-2024-46782,\nCVE-2024-46781, CVE-2024-43871, CVE-2024-42304, CVE-2024-42311,\nCVE-2024-45003, CVE-2024-46745, CVE-2024-41098, CVE-2024-46750,\nCVE-2024-47667, CVE-2024-41020, CVE-2024-26640, CVE-2024-41070,\nCVE-2024-42301, CVE-2024-43882, CVE-2024-45008, CVE-2024-26885,\nCVE-2024-42287, CVE-2024-46744, CVE-2024-43908, CVE-2024-46798,\nCVE-2023-52918, CVE-2024-36484, CVE-2024-43841, CVE-2024-41042,\nCVE-2024-38611, CVE-2024-43867, CVE-2024-26669, CVE-2024-42271,\nCVE-2024-46756, CVE-2024-44947, CVE-2024-43835, CVE-2024-46676,\nCVE-2024-46743, CVE-2024-46759, CVE-2024-46675, CVE-2024-46828,\nCVE-2024-46755)\n","status":"published","published":"2024-11-04T17:00:57Z","modified":"2026-10-29T20:02:40.032821842Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7088-3","title":"linux-aws-5.4, linux-oracle-5.4 vulnerabilities","description":"Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the\nLinux kernel contained an integer overflow vulnerability. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2022-36402)\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  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - CPU frequency scaling framework;\n  - Device frequency scaling framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - BPF subsystem;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2021-47212, CVE-2024-44965, CVE-2024-46676, CVE-2024-41091,\nCVE-2024-44946, CVE-2024-43894, CVE-2024-26668, CVE-2024-42259,\nCVE-2024-42295, CVE-2024-46685, CVE-2024-46722, CVE-2024-45028,\nCVE-2024-46815, CVE-2024-41081, CVE-2024-41022, CVE-2024-44948,\nCVE-2024-42301, CVE-2024-43914, CVE-2024-46771, CVE-2024-42289,\nCVE-2024-43841, CVE-2024-41042, CVE-2024-44999, CVE-2024-43893,\nCVE-2024-46758, CVE-2024-46828, CVE-2024-36484, CVE-2024-26669,\nCVE-2024-44952, CVE-2024-42265, CVE-2024-42311, CVE-2024-43880,\nCVE-2024-41070, CVE-2024-46829, CVE-2024-42292, CVE-2024-46719,\nCVE-2024-41020, CVE-2024-41015, CVE-2024-42283, CVE-2024-46744,\nCVE-2024-46679, CVE-2024-46800, CVE-2024-46777, CVE-2024-43835,\nCVE-2024-42271, CVE-2024-43882, CVE-2024-41072, CVE-2024-35848,\nCVE-2024-43860, CVE-2024-38611, CVE-2024-26607, CVE-2024-47663,\nCVE-2024-46780, CVE-2024-46675, CVE-2024-45003, CVE-2024-44969,\nCVE-2024-42244, CVE-2024-43856, CVE-2024-46755, CVE-2024-42286,\nCVE-2024-41063, CVE-2024-41068, CVE-2024-46743, CVE-2024-43839,\nCVE-2024-41065, CVE-2023-52531, CVE-2024-41090, CVE-2024-46747,\nCVE-2023-52614, CVE-2024-43853, CVE-2024-46737, CVE-2024-45021,\nCVE-2024-41012, CVE-2024-41064, CVE-2024-26800, CVE-2024-42246,\nCVE-2024-43908, CVE-2024-46723, CVE-2024-42310, CVE-2024-46781,\nCVE-2023-52918, CVE-2024-42313, CVE-2024-45006, CVE-2024-43890,\nCVE-2024-44954, CVE-2024-43858, CVE-2024-41098, CVE-2024-41071,\nCVE-2024-26641, CVE-2024-42280, CVE-2024-46673, CVE-2024-43846,\nCVE-2024-46721, CVE-2024-47667, CVE-2024-26885, CVE-2024-42304,\nCVE-2024-46745, CVE-2024-26640, CVE-2024-43861, CVE-2024-42287,\nCVE-2024-44998, CVE-2024-40929, CVE-2024-41073, CVE-2024-46689,\nCVE-2024-44944, CVE-2024-46756, CVE-2024-42305, CVE-2024-42284,\nCVE-2024-42281, CVE-2024-42288, CVE-2024-41011, CVE-2024-47668,\nCVE-2024-43830, CVE-2024-46740, CVE-2024-46677, CVE-2024-43867,\nCVE-2024-46783, CVE-2024-46844, CVE-2024-43854, CVE-2024-42297,\nCVE-2024-46738, CVE-2024-46739, CVE-2024-44947, CVE-2024-43883,\nCVE-2024-43884, CVE-2024-46798, CVE-2024-46757, CVE-2024-43879,\nCVE-2024-47659, CVE-2024-46817, CVE-2024-45008, CVE-2024-47669,\nCVE-2024-43871, CVE-2024-44960, CVE-2024-27051, CVE-2024-44988,\nCVE-2024-46840, CVE-2024-41059, CVE-2024-46822, CVE-2024-42276,\nCVE-2024-45026, CVE-2024-46761, CVE-2024-44995, CVE-2024-44987,\nCVE-2024-26891, CVE-2024-46782, CVE-2024-42309, CVE-2024-42131,\nCVE-2024-46759, CVE-2024-42229, CVE-2024-46714, CVE-2024-42290,\nCVE-2024-44935, CVE-2024-42285, CVE-2024-38602, CVE-2024-43829,\nCVE-2024-42306, CVE-2024-41017, CVE-2024-45025, CVE-2024-46818,\nCVE-2024-46750)\n","status":"published","published":"2024-11-06T10:52:26Z","modified":"2026-10-29T20:02:41.335133007Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7088-4","title":"linux-aws, linux-azure-5.4, linux-kvm, linux-oracle, linux-xilinx-zynqmp vulnerabilities","description":"\nZiming Zhang discovered that the VMware Virtual GPU DRM driver in the\nLinux kernel contained an integer overflow vulnerability. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2022-36402)\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  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - CPU frequency scaling framework;\n  - Device frequency scaling framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - BPF subsystem;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-35848, CVE-2024-43853, CVE-2024-41017, CVE-2024-26607,\nCVE-2024-43839, CVE-2024-41072, CVE-2024-46815, CVE-2023-52614,\nCVE-2024-46798, CVE-2024-46676, CVE-2024-43914, CVE-2024-43841,\nCVE-2024-41012, CVE-2024-27051, CVE-2024-46738, CVE-2024-47663,\nCVE-2024-46723, CVE-2024-46740, CVE-2024-42287, CVE-2024-46750,\nCVE-2024-43894, CVE-2023-52531, CVE-2024-47668, CVE-2024-47669,\nCVE-2024-46685, CVE-2024-41011, CVE-2024-41064, CVE-2024-42305,\nCVE-2024-41073, CVE-2024-46829, CVE-2024-43860, CVE-2024-46679,\nCVE-2024-44999, CVE-2024-46817, CVE-2024-26800, CVE-2024-46689,\nCVE-2024-43908, CVE-2024-46739, CVE-2024-43893, CVE-2024-46828,\nCVE-2024-46777, CVE-2024-46721, CVE-2024-36484, CVE-2024-46822,\nCVE-2024-46840, CVE-2024-43880, CVE-2024-46781, CVE-2024-46673,\nCVE-2024-26669, CVE-2024-41098, CVE-2024-46737, CVE-2024-43871,\nCVE-2024-42281, CVE-2024-42301, CVE-2024-44995, CVE-2024-43879,\nCVE-2024-26668, CVE-2024-44965, CVE-2024-41068, CVE-2024-41059,\nCVE-2024-42229, CVE-2024-44987, CVE-2024-46745, CVE-2024-26891,\nCVE-2024-46719, CVE-2024-42292, CVE-2024-44952, CVE-2024-46756,\nCVE-2024-45028, CVE-2024-42283, CVE-2024-45025, CVE-2024-46743,\nCVE-2024-43867, CVE-2024-46771, CVE-2024-41081, CVE-2024-42244,\nCVE-2024-42284, CVE-2024-43858, CVE-2024-44998, CVE-2024-46758,\nCVE-2024-46800, CVE-2024-45003, CVE-2024-44935, CVE-2024-38611,\nCVE-2024-46844, CVE-2024-44954, CVE-2024-42313, CVE-2024-46783,\nCVE-2024-42311, CVE-2024-46761, CVE-2024-41022, CVE-2024-43829,\nCVE-2024-43835, CVE-2024-43846, CVE-2024-46755, CVE-2024-47667,\nCVE-2024-42259, CVE-2024-41090, CVE-2024-42310, CVE-2024-42265,\nCVE-2024-42295, CVE-2024-46818, CVE-2024-46780, CVE-2024-44948,\nCVE-2024-44960, CVE-2024-44988, CVE-2024-46757, CVE-2024-45021,\nCVE-2024-46747, CVE-2024-43854, CVE-2024-42304, CVE-2021-47212,\nCVE-2024-42309, CVE-2024-44946, CVE-2024-46744, CVE-2024-42285,\nCVE-2024-46782, CVE-2024-43856, CVE-2024-41091, CVE-2024-42131,\nCVE-2024-43830, CVE-2024-42290, CVE-2024-45008, CVE-2024-42276,\nCVE-2024-47659, CVE-2024-40929, CVE-2024-46714, CVE-2023-52918,\nCVE-2024-44947, CVE-2024-42289, CVE-2024-42246, CVE-2024-41071,\nCVE-2024-43883, CVE-2024-46722, CVE-2024-38602, CVE-2024-43882,\nCVE-2024-42280, CVE-2024-46759, CVE-2024-42271, CVE-2024-44969,\nCVE-2024-44944, CVE-2024-46675, CVE-2024-41020, CVE-2024-41042,\nCVE-2024-42306, CVE-2024-46677, CVE-2024-42288, CVE-2024-41070,\nCVE-2024-45026, CVE-2024-41065, CVE-2024-26885, CVE-2024-42286,\nCVE-2024-41063, CVE-2024-43884, CVE-2024-42297, CVE-2024-43890,\nCVE-2024-43861, CVE-2024-45006, CVE-2024-26640, CVE-2024-26641,\nCVE-2024-41015)\n","status":"published","published":"2024-11-07T11:11:48Z","modified":"2026-10-29T20:03:25.317819196Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7088-5","title":"linux-raspi, linux-raspi-5.4 vulnerabilities","description":"\nZiming Zhang discovered that the VMware Virtual GPU DRM driver in the\nLinux kernel contained an integer overflow vulnerability. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2022-36402)\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  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - CPU frequency scaling framework;\n  - Device frequency scaling framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - BPF subsystem;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-42289, CVE-2024-26640, CVE-2024-42246, CVE-2024-43914,\nCVE-2024-46744, CVE-2024-45026, CVE-2024-41071, CVE-2024-43893,\nCVE-2024-46689, CVE-2024-41073, CVE-2024-42292, CVE-2024-43884,\nCVE-2024-42301, CVE-2024-43856, CVE-2024-46756, CVE-2024-46759,\nCVE-2024-27051, CVE-2024-26668, CVE-2024-46840, CVE-2024-42306,\nCVE-2024-41042, CVE-2024-45006, CVE-2024-42309, CVE-2024-26891,\nCVE-2024-42283, CVE-2024-46782, CVE-2024-44948, CVE-2024-43839,\nCVE-2024-47667, CVE-2024-44965, CVE-2024-42284, CVE-2024-44987,\nCVE-2024-46777, CVE-2024-41017, CVE-2024-46722, CVE-2024-41015,\nCVE-2024-46817, CVE-2024-46740, CVE-2024-43894, CVE-2024-26800,\nCVE-2024-45003, CVE-2024-46822, CVE-2024-26641, CVE-2024-44960,\nCVE-2024-44935, CVE-2024-42229, CVE-2024-42285, CVE-2024-44988,\nCVE-2024-46829, CVE-2024-41012, CVE-2024-46750, CVE-2024-43835,\nCVE-2024-43883, CVE-2024-43882, CVE-2024-46844, CVE-2024-41011,\nCVE-2024-44999, CVE-2024-46757, CVE-2024-42131, CVE-2024-46714,\nCVE-2024-41081, CVE-2024-45021, CVE-2024-46747, CVE-2024-46673,\nCVE-2024-46737, CVE-2024-43841, CVE-2024-42304, CVE-2024-45008,\nCVE-2024-42259, CVE-2024-42276, CVE-2024-46685, CVE-2024-46743,\nCVE-2023-52614, CVE-2024-42313, CVE-2024-41090, CVE-2024-46677,\nCVE-2024-43861, CVE-2024-42288, CVE-2024-43890, CVE-2024-41063,\nCVE-2024-43860, CVE-2024-47669, CVE-2024-42305, CVE-2024-43879,\nCVE-2024-42281, CVE-2024-46798, CVE-2024-42280, CVE-2024-42297,\nCVE-2024-42310, CVE-2024-44947, CVE-2024-40929, CVE-2024-41068,\nCVE-2024-42244, CVE-2024-41059, CVE-2024-47659, CVE-2024-43858,\nCVE-2024-41020, CVE-2024-41064, CVE-2023-52531, CVE-2024-41022,\nCVE-2024-46723, CVE-2024-42311, CVE-2024-44969, CVE-2024-45025,\nCVE-2024-44946, CVE-2024-46755, CVE-2024-46815, CVE-2024-46761,\nCVE-2024-43867, CVE-2024-41070, CVE-2024-43880, CVE-2024-47663,\nCVE-2024-44944, CVE-2024-45028, CVE-2024-43908, CVE-2024-46783,\nCVE-2024-43853, CVE-2024-41091, CVE-2024-46719, CVE-2024-43871,\nCVE-2024-36484, CVE-2024-46771, CVE-2024-42265, CVE-2024-42286,\nCVE-2024-43854, CVE-2024-41072, CVE-2024-43830, CVE-2024-46721,\nCVE-2024-44995, CVE-2024-46828, CVE-2024-46780, CVE-2024-46739,\nCVE-2024-46676, CVE-2024-47668, CVE-2024-42287, CVE-2023-52918,\nCVE-2024-46745, CVE-2024-35848, CVE-2024-42290, CVE-2024-41065,\nCVE-2024-42271, CVE-2024-38611, CVE-2024-41098, CVE-2024-43846,\nCVE-2024-26885, CVE-2021-47212, CVE-2024-46781, CVE-2024-26607,\nCVE-2024-26669, CVE-2024-44954, CVE-2024-42295, CVE-2024-46818,\nCVE-2024-44952, CVE-2024-46738, CVE-2024-44998, CVE-2024-46675,\nCVE-2024-43829, CVE-2024-46758, CVE-2024-38602, CVE-2024-46800,\nCVE-2024-46679)\n","status":"published","published":"2024-11-14T17:24:54Z","modified":"2026-10-29T20:02:42.196723465Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7100-1","title":"linux, linux-aws-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-gkeop-5.15, linux-hwe-5.15, linux-ibm, linux-ibm-5.15, linux-kvm, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-nvidia, linux-oracle, linux-oracle-5.15, linux-raspi, linux-xilinx-zynqmp vulnerabilities","description":"\nSupraja Sridhara, Benedict Schlüter, Mark Kuhne, Andrin Bertschi, and\nShweta Shinde discovered that the Confidential Computing framework in\nthe Linux kernel for x86 platforms did not properly handle 32-bit\nemulation on TDX and SEV. An attacker with access to the VMM could use\nthis to cause a denial of service (guest crash) or possibly execute\narbitrary code. (CVE-2024-25744)\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  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media 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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-43817, CVE-2024-42304, CVE-2024-46756, CVE-2024-42318,\nCVE-2024-41090, CVE-2024-41063, CVE-2024-44987, CVE-2024-46844,\nCVE-2024-46677, CVE-2024-44988, CVE-2024-42297, CVE-2024-26893,\nCVE-2024-46673, CVE-2024-26800, CVE-2024-42305, CVE-2024-46731,\nCVE-2024-41091, CVE-2024-46810, CVE-2024-41072, CVE-2022-48666,\nCVE-2024-38602, CVE-2024-46780, CVE-2024-46750, CVE-2024-43858,\nCVE-2024-41020, CVE-2024-46755, CVE-2024-46829, CVE-2024-41068,\nCVE-2024-45003, CVE-2024-42280, CVE-2024-42283, CVE-2024-43873,\nCVE-2024-46746, CVE-2024-44969, CVE-2024-46807, CVE-2024-41081,\nCVE-2024-44971, CVE-2024-26607, CVE-2024-43880, CVE-2024-42281,\nCVE-2024-42274, CVE-2024-43908, CVE-2024-42267, CVE-2024-47665,\nCVE-2024-45011, CVE-2024-46707, CVE-2024-42310, CVE-2024-42309,\nCVE-2024-44965, CVE-2024-46747, CVE-2024-42259, CVE-2024-46804,\nCVE-2024-46679, CVE-2024-45007, CVE-2024-45009, CVE-2024-46771,\nCVE-2024-46739, CVE-2024-41060, CVE-2024-46676, CVE-2024-46822,\nCVE-2024-42272, CVE-2024-41059, CVE-2024-43839, CVE-2024-46817,\nCVE-2024-47669, CVE-2024-44999, CVE-2024-42285, CVE-2024-44986,\nCVE-2024-43828, CVE-2024-43879, CVE-2024-44998, CVE-2024-46724,\nCVE-2024-41015, CVE-2024-45025, CVE-2024-43849, CVE-2024-46818,\nCVE-2024-43830, CVE-2024-46725, CVE-2024-43834, CVE-2024-42302,\nCVE-2024-36484, CVE-2024-43853, CVE-2024-46782, CVE-2024-46740,\nCVE-2024-46732, CVE-2024-43869, CVE-2024-42312, CVE-2024-42292,\nCVE-2024-43884, CVE-2024-44934, CVE-2024-44995, CVE-2024-43894,\nCVE-2024-46675, CVE-2024-43870, CVE-2024-44990, CVE-2024-42287,\nCVE-2024-41065, CVE-2024-42301, CVE-2024-42290, CVE-2024-46702,\nCVE-2024-46719, CVE-2024-46745, CVE-2024-46758, CVE-2024-46757,\nCVE-2024-44935, CVE-2024-42276, CVE-2024-43890, CVE-2023-52918,\nCVE-2024-41077, CVE-2024-43905, CVE-2024-38611, CVE-2024-42269,\nCVE-2024-42284, CVE-2024-41073, CVE-2024-46722, CVE-2024-41017,\nCVE-2024-47667, CVE-2024-45021, CVE-2024-43867, CVE-2024-41098,\nCVE-2024-43909, CVE-2024-46723, CVE-2024-45026, CVE-2024-42114,\nCVE-2024-44944, CVE-2024-43835, CVE-2024-44982, CVE-2024-43907,\nCVE-2024-46828, CVE-2024-43856, CVE-2024-46832, CVE-2024-44954,\nCVE-2024-43846, CVE-2024-41070, CVE-2024-43892, CVE-2024-44985,\nCVE-2024-42306, CVE-2024-43889, CVE-2024-44958, CVE-2024-46798,\nCVE-2024-44989, CVE-2024-42313, CVE-2024-46737, CVE-2024-42289,\nCVE-2024-43829, CVE-2024-46744, CVE-2023-52889, CVE-2024-46689,\nCVE-2024-47663, CVE-2024-46791, CVE-2024-43863, CVE-2024-43893,\nCVE-2024-43841, CVE-2024-46777, CVE-2024-46800, CVE-2024-45028,\nCVE-2024-44952, CVE-2024-43883, CVE-2024-44946, CVE-2024-43882,\nCVE-2024-44960, CVE-2024-38577, CVE-2024-46814, CVE-2024-42288,\nCVE-2024-44947, CVE-2024-41071, CVE-2024-41042, CVE-2024-41064,\nCVE-2024-42311, CVE-2024-42270, CVE-2024-43861, CVE-2024-46752,\nCVE-2024-42296, CVE-2024-41022, CVE-2024-42246, CVE-2024-43871,\nCVE-2024-42265, CVE-2024-43854, CVE-2024-41019, CVE-2024-46815,\nCVE-2024-46743, CVE-2024-42126, CVE-2024-26661, CVE-2024-41012,\nCVE-2024-46761, CVE-2024-45008, CVE-2024-46805, CVE-2024-45006,\nCVE-2024-42295, CVE-2024-46783, CVE-2024-42286, CVE-2024-46714,\nCVE-2024-42299, CVE-2024-46781, CVE-2024-43914, CVE-2024-44966,\nCVE-2024-44974, CVE-2024-45018, CVE-2024-46840, CVE-2024-46819,\nCVE-2024-40915, CVE-2024-46759, CVE-2024-43860, CVE-2024-47668,\nCVE-2024-39472, CVE-2024-47660, CVE-2024-47659, CVE-2024-46795,\nCVE-2024-43875, CVE-2024-46738, CVE-2024-42271, CVE-2024-26669,\nCVE-2024-44983, CVE-2024-41078, CVE-2024-46685, CVE-2024-46713,\nCVE-2024-46721, CVE-2024-46763, CVE-2024-41011, CVE-2024-43902,\nCVE-2024-42277, CVE-2024-44948)\n","status":"published","published":"2024-11-11T15:11:04Z","modified":"2026-10-29T20:05:34.276242489Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7100-2","title":"linux-aws vulnerabilities","description":"\nSupraja Sridhara, Benedict Schlüter, Mark Kuhne, Andrin Bertschi, and\nShweta Shinde discovered that the Confidential Computing framework in\nthe Linux kernel for x86 platforms did not properly handle 32-bit\nemulation on TDX and SEV. An attacker with access to the VMM could use\nthis to cause a denial of service (guest crash) or possibly execute\narbitrary code. (CVE-2024-25744)\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  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media 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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-42288, CVE-2024-41098, CVE-2024-43849, CVE-2024-46689,\nCVE-2024-44987, CVE-2024-40915, CVE-2024-46844, CVE-2024-45009,\nCVE-2024-46780, CVE-2024-41081, CVE-2024-43817, CVE-2024-44965,\nCVE-2024-46832, CVE-2024-41072, CVE-2024-45011, CVE-2024-46814,\nCVE-2024-45026, CVE-2024-44982, CVE-2024-46723, CVE-2024-46771,\nCVE-2024-46759, CVE-2024-41063, CVE-2024-46673, CVE-2023-52889,\nCVE-2024-41020, CVE-2024-46677, CVE-2024-46798, CVE-2024-45021,\nCVE-2024-46676, CVE-2024-47668, CVE-2024-42289, CVE-2024-45018,\nCVE-2024-46724, CVE-2024-41090, CVE-2024-43853, CVE-2024-42272,\nCVE-2024-43828, CVE-2024-42292, CVE-2024-26800, CVE-2024-43871,\nCVE-2024-46758, CVE-2024-36484, CVE-2024-46755, CVE-2024-46782,\nCVE-2024-43889, CVE-2024-46763, CVE-2024-41015, CVE-2024-43858,\nCVE-2024-41012, CVE-2024-44960, CVE-2024-46747, CVE-2024-42311,\nCVE-2024-47660, CVE-2024-42267, CVE-2024-44998, CVE-2024-43839,\nCVE-2024-43914, CVE-2024-46783, CVE-2024-47659, CVE-2024-46725,\nCVE-2024-46840, CVE-2024-43873, CVE-2024-46737, CVE-2024-44946,\nCVE-2024-43841, CVE-2024-26669, CVE-2024-42306, CVE-2024-26661,\nCVE-2024-42259, CVE-2024-41011, CVE-2024-46822, CVE-2024-42287,\nCVE-2024-46746, CVE-2024-43860, CVE-2024-42246, CVE-2024-46800,\nCVE-2024-45007, CVE-2024-42296, CVE-2024-47669, CVE-2024-44983,\nCVE-2024-43880, CVE-2024-42284, CVE-2022-48666, CVE-2024-44990,\nCVE-2024-43894, CVE-2024-44989, CVE-2023-52918, CVE-2024-42295,\nCVE-2024-43869, CVE-2024-42277, CVE-2024-46818, CVE-2024-42270,\nCVE-2024-45025, CVE-2024-42301, CVE-2024-43883, CVE-2024-46714,\nCVE-2024-46815, CVE-2024-41073, CVE-2024-43905, CVE-2024-43882,\nCVE-2024-46719, CVE-2024-42286, CVE-2024-44952, CVE-2024-42297,\nCVE-2024-41022, CVE-2024-46743, CVE-2024-43829, CVE-2024-43909,\nCVE-2024-42265, CVE-2024-44944, CVE-2024-46807, CVE-2024-46739,\nCVE-2024-43867, CVE-2024-44958, CVE-2024-44969, CVE-2024-42271,\nCVE-2024-46745, CVE-2024-42299, CVE-2024-45006, CVE-2024-43908,\nCVE-2024-44966, CVE-2024-41065, CVE-2024-46777, CVE-2024-42309,\nCVE-2024-38602, CVE-2024-44947, CVE-2024-43884, CVE-2024-43902,\nCVE-2024-47667, CVE-2024-46750, CVE-2024-41070, CVE-2024-26893,\nCVE-2024-41017, CVE-2024-46810, CVE-2024-46828, CVE-2024-43893,\nCVE-2024-41077, CVE-2024-46756, CVE-2024-46740, CVE-2024-42269,\nCVE-2024-43890, CVE-2024-45008, CVE-2024-46795, CVE-2024-43854,\nCVE-2024-46713, CVE-2024-47663, CVE-2024-46702, CVE-2024-46781,\nCVE-2024-46722, CVE-2024-42114, CVE-2024-44948, CVE-2024-44988,\nCVE-2024-42302, CVE-2024-41019, CVE-2024-46731, CVE-2024-46819,\nCVE-2024-44995, CVE-2024-41059, CVE-2024-43856, CVE-2024-44954,\nCVE-2024-43863, CVE-2024-38577, CVE-2024-43870, CVE-2024-41068,\nCVE-2024-41071, CVE-2024-38611, CVE-2024-46761, CVE-2024-42304,\nCVE-2024-42310, CVE-2024-46707, CVE-2024-42290, CVE-2024-42276,\nCVE-2024-44935, CVE-2024-46721, CVE-2024-46817, CVE-2024-46791,\nCVE-2024-44934, CVE-2024-45028, CVE-2024-46757, CVE-2024-43879,\nCVE-2024-43907, CVE-2024-43846, CVE-2024-42280, CVE-2024-44999,\nCVE-2024-43861, CVE-2024-42126, CVE-2024-26607, CVE-2024-46752,\nCVE-2024-42305, CVE-2024-43835, CVE-2024-41042, CVE-2024-46675,\nCVE-2024-46804, CVE-2024-41091, CVE-2024-41060, CVE-2024-46744,\nCVE-2024-47665, CVE-2024-39472, CVE-2024-46829, CVE-2024-42285,\nCVE-2024-42281, CVE-2024-43830, CVE-2024-42274, CVE-2024-46679,\nCVE-2024-44985, CVE-2024-46805, CVE-2024-42312, CVE-2024-42283,\nCVE-2024-45003, CVE-2024-44971, CVE-2024-42313, CVE-2024-46685,\nCVE-2024-46738, CVE-2024-44986, CVE-2024-43834, CVE-2024-46732,\nCVE-2024-43875, CVE-2024-42318, CVE-2024-41064, CVE-2024-44974,\nCVE-2024-43892, CVE-2024-41078)\n","status":"published","published":"2024-11-12T14:54:50Z","modified":"2026-10-29T20:02:38.021605735Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7119-1","title":"linux-iot vulnerabilities","description":"\nZiming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux\nkernel contained an integer overflow vulnerability. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2022-36402)\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  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - CPU frequency scaling framework;\n  - Device frequency scaling framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - Modular ISDN driver;\n  - LED subsystem;\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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - Watchdog drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - Netfilter;\n  - BPF subsystem;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Simplified Mandatory Access Control Kernel framework;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-46750, CVE-2024-43853, CVE-2024-46722, CVE-2024-42311,\nCVE-2024-46679, CVE-2023-52918, CVE-2024-42309, CVE-2024-42160,\nCVE-2024-26668, CVE-2024-42271, CVE-2024-40929, CVE-2024-46747,\nCVE-2024-41064, CVE-2024-43839, CVE-2024-46757, CVE-2024-41059,\nCVE-2024-42301, CVE-2024-46737, CVE-2024-42297, CVE-2024-41015,\nCVE-2024-43854, CVE-2024-42289, CVE-2024-41017, CVE-2024-26787,\nCVE-2024-47667, CVE-2024-46675, CVE-2024-42246, CVE-2024-46723,\nCVE-2024-46817, CVE-2024-43841, CVE-2024-26800, CVE-2024-41098,\nCVE-2022-48863, CVE-2023-52531, CVE-2024-42265, CVE-2024-46828,\nCVE-2024-41020, CVE-2024-42305, CVE-2024-46755, CVE-2024-46744,\nCVE-2024-43871, CVE-2024-43884, CVE-2024-41042, CVE-2024-43914,\nCVE-2024-43856, CVE-2024-27397, CVE-2024-26607, CVE-2024-42228,\nCVE-2024-41091, CVE-2024-26677, CVE-2024-38611, CVE-2024-43867,\nCVE-2024-46829, CVE-2021-47188, CVE-2024-46756, CVE-2024-45025,\nCVE-2024-42313, CVE-2024-44947, CVE-2024-26669, CVE-2024-47668,\nCVE-2024-44987, CVE-2024-42295, CVE-2024-42281, CVE-2024-43880,\nCVE-2024-46777, CVE-2024-46780, CVE-2024-42285, CVE-2024-26891,\nCVE-2024-46714, CVE-2024-44999, CVE-2024-41068, CVE-2024-44944,\nCVE-2024-43882, CVE-2024-27051, CVE-2024-41072, CVE-2024-46783,\nCVE-2024-46781, CVE-2024-26885, CVE-2024-46844, CVE-2024-47669,\nCVE-2024-45008, CVE-2024-46758, CVE-2024-44954, CVE-2024-45021,\nCVE-2024-42304, CVE-2024-41081, CVE-2024-46798, CVE-2024-43890,\nCVE-2024-46840, CVE-2024-44960, CVE-2024-41012, CVE-2022-48791,\nCVE-2024-43908, CVE-2024-46721, CVE-2024-43829, CVE-2024-41073,\nCVE-2024-42306, CVE-2024-46745, CVE-2024-43858, CVE-2024-47663,\nCVE-2024-46782, CVE-2024-42244, CVE-2024-41090, CVE-2024-38602,\nCVE-2024-45003, CVE-2024-35848, CVE-2024-43883, CVE-2024-46677,\nCVE-2024-42280, CVE-2024-43846, CVE-2024-47659, CVE-2024-44965,\nCVE-2024-43893, CVE-2024-26960, CVE-2024-46676, CVE-2024-45016,\nCVE-2024-46689, CVE-2024-44998, CVE-2024-44995, CVE-2024-41022,\nCVE-2024-45026, CVE-2024-46739, CVE-2024-43830, CVE-2024-42286,\nCVE-2024-26640, CVE-2024-27012, CVE-2024-45006, CVE-2024-42276,\nCVE-2024-46818, CVE-2024-39494, CVE-2024-43860, CVE-2024-41070,\nCVE-2023-52614, CVE-2024-42283, CVE-2024-44969, CVE-2024-42229,\nCVE-2024-46740, CVE-2024-44948, CVE-2024-46822, CVE-2024-46738,\nCVE-2024-36484, CVE-2024-41065, CVE-2024-46685, CVE-2024-44935,\nCVE-2024-46759, CVE-2024-42292, CVE-2024-43879, CVE-2024-42287,\nCVE-2024-42288, CVE-2024-41063, CVE-2024-41011, CVE-2024-44946,\nCVE-2024-42290, CVE-2024-38570, CVE-2024-42310, CVE-2024-46743,\nCVE-2024-43861, CVE-2024-42131, CVE-2021-47212, CVE-2024-46719,\nCVE-2024-46815, CVE-2024-26641, CVE-2024-43894, CVE-2024-44988,\nCVE-2024-42259, CVE-2024-46771, CVE-2024-46673, CVE-2024-45028,\nCVE-2024-46761, CVE-2024-41071, CVE-2024-38630, CVE-2024-43835,\nCVE-2024-46800, CVE-2024-42284)\n","status":"published","published":"2024-11-19T22:47:40Z","modified":"2026-10-29T20:02:36.738009052Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7123-1","title":"linux-azure vulnerabilities","description":"It was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly validate certain SMB messages, leading to an\nout-of-bounds read vulnerability. An attacker could use this to cause a\ndenial of service (system crash) or possibly expose sensitive information.\n(CVE-2023-6610)\n\nSupraja Sridhara, Benedict Schlüter, Mark Kuhne, Andrin Bertschi, and\nShweta Shinde discovered that the Confidential Computing framework in the\nLinux kernel for x86 platforms did not properly handle 32-bit emulation on\nTDX and SEV. An attacker with access to the VMM could use this to cause a\ndenial of service (guest crash) or possibly execute arbitrary code.\n(CVE-2024-25744)\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  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media 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  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Core kernel;\n  - DMA mapping infrastructure;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Objagg library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2023-52751, CVE-2024-43902, CVE-2024-46791, CVE-2024-45018,\nCVE-2024-44987, CVE-2024-46763, CVE-2024-46724, CVE-2024-26893,\nCVE-2024-42283, CVE-2024-46738, CVE-2024-46819, CVE-2024-44982,\nCVE-2023-52889, CVE-2024-45025, CVE-2023-52918, CVE-2024-46800,\nCVE-2024-46756, CVE-2024-46719, CVE-2024-39472, CVE-2024-42292,\nCVE-2024-45006, CVE-2024-46675, CVE-2024-44971, CVE-2024-46731,\nCVE-2024-42286, CVE-2024-44954, CVE-2024-42274, CVE-2024-46746,\nCVE-2024-42276, CVE-2024-43869, CVE-2024-43830, CVE-2024-42288,\nCVE-2024-41042, CVE-2024-42126, CVE-2024-43870, CVE-2024-46805,\nCVE-2024-41078, CVE-2024-44966, CVE-2024-44989, CVE-2024-46795,\nCVE-2024-44988, CVE-2024-38577, CVE-2024-43839, CVE-2024-43909,\nCVE-2024-46745, CVE-2024-42285, CVE-2024-43871, CVE-2024-41081,\nCVE-2024-42289, CVE-2024-44965, CVE-2024-42271, CVE-2024-42284,\nCVE-2024-45009, CVE-2024-41068, CVE-2024-44958, CVE-2024-46759,\nCVE-2024-42304, CVE-2024-43890, CVE-2024-41019, CVE-2024-43846,\nCVE-2024-41012, CVE-2024-44983, CVE-2024-41072, CVE-2024-46702,\nCVE-2024-26800, CVE-2024-42302, CVE-2023-52572, CVE-2024-46783,\nCVE-2024-43892, CVE-2024-45028, CVE-2024-44999, CVE-2024-46814,\nCVE-2024-41022, CVE-2024-42281, CVE-2024-46679, CVE-2024-42290,\nCVE-2024-44960, CVE-2024-41071, CVE-2024-41091, CVE-2024-44990,\nCVE-2024-46757, CVE-2024-38611, CVE-2024-47668, CVE-2024-45008,\nCVE-2024-46707, CVE-2024-44935, CVE-2024-42299, CVE-2024-46771,\nCVE-2024-42265, CVE-2024-43883, CVE-2024-46673, CVE-2024-46747,\nCVE-2024-43875, CVE-2024-44985, CVE-2024-42311, CVE-2024-46798,\nCVE-2024-43884, CVE-2024-46725, CVE-2024-42318, CVE-2024-43873,\nCVE-2024-42296, CVE-2024-43907, CVE-2024-43834, CVE-2024-46721,\nCVE-2024-47659, CVE-2024-45026, CVE-2024-47667, CVE-2024-44986,\nCVE-2024-41020, CVE-2024-43849, CVE-2024-46744, CVE-2024-44946,\nCVE-2024-43861, CVE-2024-42269, CVE-2024-46822, CVE-2024-46739,\nCVE-2024-44948, CVE-2024-46804, CVE-2024-41064, CVE-2024-44995,\nCVE-2024-26669, CVE-2024-46781, CVE-2024-46732, CVE-2024-42246,\nCVE-2024-46780, CVE-2024-46743, CVE-2024-44947, CVE-2024-47663,\nCVE-2024-46752, CVE-2024-43893, CVE-2024-45021, CVE-2024-43856,\nCVE-2024-46714, CVE-2024-41011, CVE-2024-41070, CVE-2024-46832,\nCVE-2024-46737, CVE-2024-43867, CVE-2024-42277, CVE-2024-44934,\nCVE-2024-46723, CVE-2024-43880, CVE-2024-43860, CVE-2024-42297,\nCVE-2024-45003, CVE-2024-46810, CVE-2024-43889, CVE-2024-42287,\nCVE-2024-43854, CVE-2024-42313, CVE-2024-42305, CVE-2024-41077,\nCVE-2024-38602, CVE-2024-46758, CVE-2024-46807, CVE-2024-43853,\nCVE-2024-45007, CVE-2024-41090, CVE-2024-42280, CVE-2024-46844,\nCVE-2024-45011, CVE-2024-47660, CVE-2024-47665, CVE-2024-46829,\nCVE-2024-44944, CVE-2024-41015, CVE-2024-42259, CVE-2024-43914,\nCVE-2024-43829, CVE-2022-48666, CVE-2024-43828, CVE-2024-46755,\nCVE-2024-43858, CVE-2024-46740, CVE-2024-46689, CVE-2024-42309,\nCVE-2024-42295, CVE-2024-41098, CVE-2023-52757, CVE-2024-46782,\nCVE-2024-46777, CVE-2024-46685, CVE-2024-44969, CVE-2024-47669,\nCVE-2024-43882, CVE-2024-42310, CVE-2024-43905, CVE-2024-44998,\nCVE-2024-42306, CVE-2024-40915, CVE-2024-46713, CVE-2024-41059,\nCVE-2024-41017, CVE-2024-43879, CVE-2024-46677, CVE-2024-42312,\nCVE-2024-43908, CVE-2024-46750, CVE-2024-46722, CVE-2024-42267,\nCVE-2024-46818, CVE-2024-26661, CVE-2024-43817, CVE-2024-42272,\nCVE-2024-41065, CVE-2024-46828, CVE-2024-46840, CVE-2024-46676,\nCVE-2024-43841, CVE-2024-46815, CVE-2024-26607, CVE-2023-52434,\nCVE-2024-46761, CVE-2024-42114, CVE-2024-41073, CVE-2024-43894,\nCVE-2024-43835, CVE-2024-46817, CVE-2024-41060, CVE-2024-36484,\nCVE-2024-42301, CVE-2024-44974, CVE-2024-43863, CVE-2024-41063)\n","status":"published","published":"2024-11-20T13:30:41Z","modified":"2026-10-29T20:02:38.663579775Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7144-1","title":"linux-intel-iotg, linux-intel-iotg-5.15 vulnerabilities","description":"Supraja Sridhara, Benedict Schlüter, Mark Kuhne, Andrin Bertschi, and\nShweta Shinde discovered that the Confidential Computing framework in the\nLinux kernel for x86 platforms did not properly handle 32-bit emulation on\nTDX and SEV. An attacker with access to the VMM could use this to cause a\ndenial of service (guest crash) or possibly execute arbitrary code.\n(CVE-2024-25744)\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  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - QCOM SoC drivers;\n  - Direct Digital Synthesis drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - Virtio Host (VHOST) subsystem;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Bitmap API;\n  - Objagg library;\n  - Perf events;\n  - Virtio network driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Network traffic control;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-42280, CVE-2024-46759, CVE-2024-42286, CVE-2024-41042,\nCVE-2024-42276, CVE-2024-46732, CVE-2024-43902, CVE-2024-47665,\nCVE-2024-46675, CVE-2024-43873, CVE-2024-46761, CVE-2024-42281,\nCVE-2024-46795, CVE-2024-43869, CVE-2024-39472, CVE-2024-46800,\nCVE-2024-44998, CVE-2024-46746, CVE-2024-46747, CVE-2024-41011,\nCVE-2024-43871, CVE-2024-46737, CVE-2024-42318, CVE-2024-46731,\nCVE-2024-41022, CVE-2024-42285, CVE-2024-46752, CVE-2024-46818,\nCVE-2024-44935, CVE-2024-44946, CVE-2024-44944, CVE-2024-41015,\nCVE-2024-42312, CVE-2024-46676, CVE-2024-43834, CVE-2024-44966,\nCVE-2024-46743, CVE-2024-45026, CVE-2024-46805, CVE-2024-26607,\nCVE-2024-46771, CVE-2024-43905, CVE-2024-43884, CVE-2024-41070,\nCVE-2024-43829, CVE-2024-46725, CVE-2024-45028, CVE-2024-42287,\nCVE-2024-42313, CVE-2024-42277, CVE-2024-42290, CVE-2024-44934,\nCVE-2024-46829, CVE-2024-46707, CVE-2024-46677, CVE-2024-42311,\nCVE-2024-46814, CVE-2024-46815, CVE-2024-46755, CVE-2024-41065,\nCVE-2024-43889, CVE-2024-46780, CVE-2024-43860, CVE-2024-46777,\nCVE-2024-46719, CVE-2024-45009, CVE-2024-42302, CVE-2024-42304,\nCVE-2024-41063, CVE-2024-47659, CVE-2024-46822, CVE-2024-46756,\nCVE-2024-42283, CVE-2024-46757, CVE-2024-43909, CVE-2024-45011,\nCVE-2024-46739, CVE-2024-46750, CVE-2024-46782, CVE-2024-44986,\nCVE-2024-44983, CVE-2024-45021, CVE-2024-44987, CVE-2024-41090,\nCVE-2024-42288, CVE-2024-44969, CVE-2024-42272, CVE-2024-43893,\nCVE-2024-42259, CVE-2024-46781, CVE-2024-43907, CVE-2024-42265,\nCVE-2024-43839, CVE-2024-47663, CVE-2024-46798, CVE-2024-43817,\nCVE-2024-42295, CVE-2024-46840, CVE-2024-45008, CVE-2024-43849,\nCVE-2024-46744, CVE-2024-43879, CVE-2024-43841, CVE-2024-42299,\nCVE-2024-46783, CVE-2024-36484, CVE-2024-47660, CVE-2024-42310,\nCVE-2024-44990, CVE-2024-42270, CVE-2024-43894, CVE-2024-41071,\nCVE-2024-40915, CVE-2024-46810, CVE-2024-44954, CVE-2024-42246,\nCVE-2023-52889, CVE-2024-43892, CVE-2024-43890, CVE-2024-42284,\nCVE-2023-52918, CVE-2024-47669, CVE-2024-41078, CVE-2024-41073,\nCVE-2024-26800, CVE-2024-41091, CVE-2024-46828, CVE-2022-48666,\nCVE-2024-41060, CVE-2024-42114, CVE-2024-46807, CVE-2024-26669,\nCVE-2024-44965, CVE-2024-46758, CVE-2024-44947, CVE-2024-43875,\nCVE-2024-42126, CVE-2024-46685, CVE-2024-43883, CVE-2024-46722,\nCVE-2024-41064, CVE-2024-43882, CVE-2024-46679, CVE-2024-46740,\nCVE-2024-45025, CVE-2024-46721, CVE-2024-38611, CVE-2024-46844,\nCVE-2024-45007, CVE-2024-44960, CVE-2024-42306, CVE-2024-44971,\nCVE-2024-43835, CVE-2024-42305, CVE-2024-43846, CVE-2024-42289,\nCVE-2024-46689, CVE-2024-46724, CVE-2024-43853, CVE-2024-44974,\nCVE-2024-43828, CVE-2024-43914, CVE-2024-44958, CVE-2024-46673,\nCVE-2024-46723, CVE-2024-41081, CVE-2024-46738, CVE-2024-42296,\nCVE-2024-45006, CVE-2024-46714, CVE-2024-43880, CVE-2024-42271,\nCVE-2024-44985, CVE-2024-41072, CVE-2024-43867, CVE-2024-43858,\nCVE-2024-26893, CVE-2024-41059, CVE-2024-38577, CVE-2024-46817,\nCVE-2024-46702, CVE-2024-41019, CVE-2024-44999, CVE-2024-43908,\nCVE-2024-42292, CVE-2024-43856, CVE-2024-45018, CVE-2024-41068,\nCVE-2024-43870, CVE-2024-45003, CVE-2024-42297, CVE-2024-47668,\nCVE-2024-43830, CVE-2024-26661, CVE-2024-41017, CVE-2024-42309,\nCVE-2024-43861, CVE-2024-46791, CVE-2024-44989, CVE-2024-46745,\nCVE-2024-42269, CVE-2024-43863, CVE-2024-43854, CVE-2024-44995,\nCVE-2024-46804, CVE-2024-44948, CVE-2024-46819, CVE-2024-41098,\nCVE-2024-44982, CVE-2024-46763, CVE-2024-46832, CVE-2024-41077,\nCVE-2024-42274, CVE-2024-47667, CVE-2024-41012, CVE-2024-41020,\nCVE-2024-42301, CVE-2024-42267, CVE-2024-46713, CVE-2024-38602,\nCVE-2024-44988)\n","status":"published","published":"2024-12-09T16:46:48Z","modified":"2026-10-29T20:02:46.459720219Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7154-1","title":"linux, linux-aws, linux-aws-6.8, linux-gcp, linux-gcp-6.8, linux-gke, linux-ibm, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-oem-6.8, linux-oracle, linux-oracle-6.8, 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  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Bitmap API;\n  - BPF subsystem;\n  - Memory Management;\n  - Objagg library;\n  - Perf events;\n  - Virtio network driver;\n  - VMware vSockets driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - KUnit for arithmetic overflow checks;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Real-Time Linux Analysis tools;\n(CVE-2024-46783, CVE-2024-44960, CVE-2024-46743, CVE-2024-45009,\nCVE-2024-43820, CVE-2024-43888, CVE-2024-45010, CVE-2024-43839,\nCVE-2024-42304, CVE-2024-43846, CVE-2024-42258, CVE-2024-45005,\nCVE-2024-46709, CVE-2024-46774, CVE-2024-43883, CVE-2024-43859,\nCVE-2024-46721, CVE-2024-44944, CVE-2024-43913, CVE-2024-43843,\nCVE-2024-43845, CVE-2024-45018, CVE-2024-43909, CVE-2024-46755,\nCVE-2024-42284, CVE-2024-42301, CVE-2024-46779, CVE-2024-44971,\nCVE-2024-46711, CVE-2024-43889, CVE-2024-46842, CVE-2024-44978,\nCVE-2024-46803, CVE-2024-42277, CVE-2024-43892, CVE-2024-45019,\nCVE-2024-44988, CVE-2024-46798, CVE-2024-44995, CVE-2024-43860,\nCVE-2024-46762, CVE-2024-43831, CVE-2024-44990, CVE-2024-46845,\nCVE-2024-46765, CVE-2024-45012, CVE-2024-44975, CVE-2024-46770,\nCVE-2024-46802, CVE-2024-44970, CVE-2024-46691, CVE-2024-43833,\nCVE-2024-43876, CVE-2024-42292, CVE-2024-42291, CVE-2024-43891,\nCVE-2024-46788, CVE-2024-44938, CVE-2024-46710, CVE-2024-42272,\nCVE-2024-43868, CVE-2024-43875, CVE-2024-45030, CVE-2024-46689,\nCVE-2024-46859, CVE-2024-46795, CVE-2024-46683, CVE-2024-44999,\nCVE-2024-44942, CVE-2024-47669, CVE-2024-42318, CVE-2024-43911,\nCVE-2024-46693, CVE-2024-42296, CVE-2024-43894, CVE-2024-45002,\nCVE-2024-46673, CVE-2024-46852, CVE-2024-45001, CVE-2024-43907,\nCVE-2024-42319, CVE-2024-44972, CVE-2024-43905, CVE-2024-45028,\nCVE-2024-46816, CVE-2024-46847, CVE-2024-46834, CVE-2024-44982,\nCVE-2024-46807, CVE-2024-44948, CVE-2024-46685, CVE-2024-46811,\nCVE-2024-42317, CVE-2024-43818, CVE-2024-46786, CVE-2024-43881,\nCVE-2024-42294, CVE-2024-46708, CVE-2024-42285, CVE-2024-44941,\nCVE-2024-43823, CVE-2024-46694, CVE-2024-46730, CVE-2024-42259,\nCVE-2024-42270, CVE-2024-47658, CVE-2024-46718, CVE-2024-44947,\nCVE-2024-46701, CVE-2024-43895, CVE-2024-43890, CVE-2024-46826,\nCVE-2024-46687, CVE-2024-46768, CVE-2024-45025, CVE-2024-42267,\nCVE-2024-42263, CVE-2024-44958, CVE-2024-44989, CVE-2024-43906,\nCVE-2024-43869, CVE-2024-43887, CVE-2024-42297, CVE-2024-46702,\nCVE-2024-42320, CVE-2024-42322, CVE-2024-46857, CVE-2024-43861,\nCVE-2024-45008, CVE-2024-44969, CVE-2024-46821, CVE-2024-44967,\nCVE-2024-43914, CVE-2024-46870, CVE-2024-46781, CVE-2024-43842,\nCVE-2024-47665, CVE-2024-46753, CVE-2024-43866, CVE-2024-43886,\nCVE-2024-44939, CVE-2024-42312, CVE-2024-46864, CVE-2024-46695,\nCVE-2024-46818, CVE-2024-45006, CVE-2024-43841, CVE-2024-46703,\nCVE-2024-46749, CVE-2024-44986, CVE-2024-46717, CVE-2024-42273,\nCVE-2024-43856, CVE-2024-46777, CVE-2024-44984, CVE-2024-46719,\nCVE-2024-46858, CVE-2024-43821, CVE-2024-46750, CVE-2024-43829,\nCVE-2024-43817, CVE-2024-42281, CVE-2024-42287, CVE-2024-45007,\nCVE-2024-46793, CVE-2024-45003, CVE-2024-45011, CVE-2024-47683,\nCVE-2024-44934, CVE-2024-46722, CVE-2024-46860, CVE-2024-42314,\nCVE-2024-46675, CVE-2024-43899, CVE-2024-46752, CVE-2024-46851,\nCVE-2024-42310, CVE-2024-46853, CVE-2024-39472, CVE-2024-43837,\nCVE-2024-45021, CVE-2024-46713, CVE-2024-44943, CVE-2024-46787,\nCVE-2024-43893, CVE-2024-44946, CVE-2024-45026, CVE-2024-44996,\nCVE-2024-46761, CVE-2024-46723, CVE-2024-42311, CVE-2024-42316,\nCVE-2024-47663, CVE-2024-44940, CVE-2024-43867, CVE-2024-42265,\nCVE-2024-44950, CVE-2024-46867, CVE-2024-45020, CVE-2024-46707,\nCVE-2024-44966, CVE-2024-42309, CVE-2024-46767, CVE-2024-46758,\nCVE-2024-46732, CVE-2024-42262, CVE-2024-46778, CVE-2024-43884,\nCVE-2024-44991, CVE-2024-47668, CVE-2024-46698, CVE-2024-46825,\nCVE-2024-42302, CVE-2024-46716, CVE-2024-46726, CVE-2024-43870,\nCVE-2024-42307, CVE-2024-46830, CVE-2024-43910, CVE-2024-46735,\nCVE-2024-43828, CVE-2024-43904, CVE-2024-44965, CVE-2024-46831,\nCVE-2024-44979, CVE-2024-44961, CVE-2024-46771, CVE-2024-46844,\nCVE-2024-46871, CVE-2024-43877, CVE-2024-46746, CVE-2024-44987,\nCVE-2024-46676, CVE-2024-46766, CVE-2024-46731, CVE-2024-46810,\nCVE-2024-46806, CVE-2024-45000, CVE-2024-42313, CVE-2024-45015,\nCVE-2024-46784, CVE-2024-43834, CVE-2024-46737, CVE-2024-46797,\nCVE-2024-43908, CVE-2024-46724, CVE-2024-44980, CVE-2024-43847,\nCVE-2024-46679, CVE-2024-46681, CVE-2024-43819, CVE-2024-46776,\nCVE-2024-44954, CVE-2024-45022, CVE-2024-46819, CVE-2024-46775,\nCVE-2024-43824, CVE-2024-44953, CVE-2024-46759, CVE-2024-43873,\nCVE-2024-46756, CVE-2024-42303, CVE-2024-46738, CVE-2024-42290,\nCVE-2024-42295, CVE-2024-43849, CVE-2024-44931, CVE-2024-46741,\nCVE-2024-43863, CVE-2024-44974, CVE-2024-46829, CVE-2024-44959,\nCVE-2024-42315, CVE-2024-44983, CVE-2024-46715, CVE-2024-46697,\nCVE-2024-43850, CVE-2024-46728, CVE-2024-44963, CVE-2024-46823,\nCVE-2024-46692, CVE-2024-46760, CVE-2024-46705, CVE-2024-42261,\nCVE-2024-42321, CVE-2024-46785, CVE-2024-46686, CVE-2024-49984,\nCVE-2024-46706, CVE-2024-45029, CVE-2024-46809, CVE-2024-43827,\nCVE-2024-44998, CVE-2024-47667, CVE-2024-43835, CVE-2024-46866,\nCVE-2024-46841, CVE-2024-42286, CVE-2024-43852, CVE-2024-43832,\nCVE-2024-46773, CVE-2024-46817, CVE-2024-46868, CVE-2024-46812,\nCVE-2024-47660, CVE-2024-46725, CVE-2024-42288, CVE-2024-46824,\nCVE-2024-42269, CVE-2024-44957, CVE-2024-45017, CVE-2024-46747,\nCVE-2024-47662, CVE-2024-46843, CVE-2024-46849, CVE-2024-43879,\nCVE-2024-46751, CVE-2024-42298, CVE-2024-46861, CVE-2024-44993,\nCVE-2024-46729, CVE-2024-46846, CVE-2024-46794, CVE-2024-43826,\nCVE-2024-44973, CVE-2024-46672, CVE-2024-44985, CVE-2024-46815,\nCVE-2024-46822, CVE-2024-46754, CVE-2024-43854, CVE-2024-42278,\nCVE-2024-46720, CVE-2024-46677, CVE-2024-46854, CVE-2024-43840,\nCVE-2024-43830, CVE-2024-46804, CVE-2024-45013, CVE-2024-46782,\nCVE-2024-46840, CVE-2024-44977, CVE-2024-46838, CVE-2024-42264,\nCVE-2024-47661, CVE-2024-43857, CVE-2023-52918, CVE-2024-44935,\nCVE-2024-46739, CVE-2024-43825, CVE-2024-43864, CVE-2024-47659,\nCVE-2024-42260, CVE-2024-44962, CVE-2024-46835, CVE-2024-43871,\nCVE-2024-47674, CVE-2024-46827, CVE-2024-42283, CVE-2024-42299,\nCVE-2024-46714, CVE-2024-46740, CVE-2024-46680, CVE-2024-46791,\nCVE-2024-43912, CVE-2024-46813, CVE-2024-46733, CVE-2024-47664,\nCVE-2024-42279, CVE-2024-46850, CVE-2024-42289, CVE-2024-46808,\nCVE-2024-43880, CVE-2024-46832, CVE-2024-42276, CVE-2024-44937,\nCVE-2024-42274, CVE-2024-46772, CVE-2024-47666, CVE-2024-44956,\nCVE-2024-46763, CVE-2024-46805, CVE-2023-52889, CVE-2024-46678,\nCVE-2024-43902, CVE-2024-46757, CVE-2024-46792, CVE-2024-42268,\nCVE-2024-43853, CVE-2024-45027, CVE-2024-42305, CVE-2024-46828,\nCVE-2024-43900, CVE-2024-46848, CVE-2024-46814, CVE-2024-46855,\nCVE-2024-46727, CVE-2024-46836, CVE-2024-46744, CVE-2024-46780,\nCVE-2024-46745, CVE-2024-42306)\n","status":"published","published":"2024-12-12T17:09:44Z","modified":"2026-10-29T20:04:50.805083723Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7154-2","title":"linux-hwe-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  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Bitmap API;\n  - BPF subsystem;\n  - Memory Management;\n  - Objagg library;\n  - Perf events;\n  - Virtio network driver;\n  - VMware vSockets driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - KUnit for arithmetic overflow checks;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Real-Time Linux Analysis tools;\n(CVE-2024-46783, CVE-2024-44960, CVE-2024-46743, CVE-2024-45009,\nCVE-2024-43820, CVE-2024-43888, CVE-2024-45010, CVE-2024-43839,\nCVE-2024-42304, CVE-2024-43846, CVE-2024-42258, CVE-2024-45005,\nCVE-2024-46709, CVE-2024-46774, CVE-2024-43883, CVE-2024-43859,\nCVE-2024-46721, CVE-2024-44944, CVE-2024-43913, CVE-2024-43843,\nCVE-2024-43845, CVE-2024-45018, CVE-2024-43909, CVE-2024-46755,\nCVE-2024-42284, CVE-2024-42301, CVE-2024-46779, CVE-2024-44971,\nCVE-2024-46711, CVE-2024-43889, CVE-2024-46842, CVE-2024-44978,\nCVE-2024-46803, CVE-2024-42277, CVE-2024-43892, CVE-2024-45019,\nCVE-2024-44988, CVE-2024-46798, CVE-2024-44995, CVE-2024-43860,\nCVE-2024-46762, CVE-2024-43831, CVE-2024-44990, CVE-2024-46845,\nCVE-2024-46765, CVE-2024-45012, CVE-2024-44975, CVE-2024-46770,\nCVE-2024-46802, CVE-2024-44970, CVE-2024-46691, CVE-2024-43833,\nCVE-2024-43876, CVE-2024-42292, CVE-2024-42291, CVE-2024-43891,\nCVE-2024-46788, CVE-2024-44938, CVE-2024-46710, CVE-2024-42272,\nCVE-2024-43868, CVE-2024-43875, CVE-2024-45030, CVE-2024-46689,\nCVE-2024-46859, CVE-2024-46795, CVE-2024-46683, CVE-2024-44999,\nCVE-2024-44942, CVE-2024-47669, CVE-2024-42318, CVE-2024-43911,\nCVE-2024-46693, CVE-2024-42296, CVE-2024-43894, CVE-2024-45002,\nCVE-2024-46673, CVE-2024-46852, CVE-2024-45001, CVE-2024-43907,\nCVE-2024-42319, CVE-2024-44972, CVE-2024-43905, CVE-2024-45028,\nCVE-2024-46816, CVE-2024-46847, CVE-2024-46834, CVE-2024-44982,\nCVE-2024-46807, CVE-2024-44948, CVE-2024-46685, CVE-2024-46811,\nCVE-2024-42317, CVE-2024-43818, CVE-2024-46786, CVE-2024-43881,\nCVE-2024-42294, CVE-2024-46708, CVE-2024-42285, CVE-2024-44941,\nCVE-2024-43823, CVE-2024-46694, CVE-2024-46730, CVE-2024-42259,\nCVE-2024-42270, CVE-2024-47658, CVE-2024-46718, CVE-2024-44947,\nCVE-2024-46701, CVE-2024-43895, CVE-2024-43890, CVE-2024-46826,\nCVE-2024-46687, CVE-2024-46768, CVE-2024-45025, CVE-2024-42267,\nCVE-2024-42263, CVE-2024-44958, CVE-2024-44989, CVE-2024-43906,\nCVE-2024-43869, CVE-2024-43887, CVE-2024-42297, CVE-2024-46702,\nCVE-2024-42320, CVE-2024-42322, CVE-2024-46857, CVE-2024-43861,\nCVE-2024-45008, CVE-2024-44969, CVE-2024-46821, CVE-2024-44967,\nCVE-2024-43914, CVE-2024-46870, CVE-2024-46781, CVE-2024-43842,\nCVE-2024-47665, CVE-2024-46753, CVE-2024-43866, CVE-2024-43886,\nCVE-2024-44939, CVE-2024-42312, CVE-2024-46864, CVE-2024-46695,\nCVE-2024-46818, CVE-2024-45006, CVE-2024-43841, CVE-2024-46703,\nCVE-2024-46749, CVE-2024-44986, CVE-2024-46717, CVE-2024-42273,\nCVE-2024-43856, CVE-2024-46777, CVE-2024-44984, CVE-2024-46719,\nCVE-2024-46858, CVE-2024-43821, CVE-2024-46750, CVE-2024-43829,\nCVE-2024-43817, CVE-2024-42281, CVE-2024-42287, CVE-2024-45007,\nCVE-2024-46793, CVE-2024-45003, CVE-2024-45011, CVE-2024-47683,\nCVE-2024-44934, CVE-2024-46722, CVE-2024-46860, CVE-2024-42314,\nCVE-2024-46675, CVE-2024-43899, CVE-2024-46752, CVE-2024-46851,\nCVE-2024-42310, CVE-2024-46853, CVE-2024-39472, CVE-2024-43837,\nCVE-2024-45021, CVE-2024-46713, CVE-2024-44943, CVE-2024-46787,\nCVE-2024-43893, CVE-2024-44946, CVE-2024-45026, CVE-2024-44996,\nCVE-2024-46761, CVE-2024-46723, CVE-2024-42311, CVE-2024-42316,\nCVE-2024-47663, CVE-2024-44940, CVE-2024-43867, CVE-2024-42265,\nCVE-2024-44950, CVE-2024-46867, CVE-2024-45020, CVE-2024-46707,\nCVE-2024-44966, CVE-2024-42309, CVE-2024-46767, CVE-2024-46758,\nCVE-2024-46732, CVE-2024-42262, CVE-2024-46778, CVE-2024-43884,\nCVE-2024-44991, CVE-2024-47668, CVE-2024-46698, CVE-2024-46825,\nCVE-2024-42302, CVE-2024-46716, CVE-2024-46726, CVE-2024-43870,\nCVE-2024-42307, CVE-2024-46830, CVE-2024-43910, CVE-2024-46735,\nCVE-2024-43828, CVE-2024-43904, CVE-2024-44965, CVE-2024-46831,\nCVE-2024-44979, CVE-2024-44961, CVE-2024-46771, CVE-2024-46844,\nCVE-2024-46871, CVE-2024-43877, CVE-2024-46746, CVE-2024-44987,\nCVE-2024-46676, CVE-2024-46766, CVE-2024-46731, CVE-2024-46810,\nCVE-2024-46806, CVE-2024-45000, CVE-2024-42313, CVE-2024-45015,\nCVE-2024-46784, CVE-2024-43834, CVE-2024-46737, CVE-2024-46797,\nCVE-2024-43908, CVE-2024-46724, CVE-2024-44980, CVE-2024-43847,\nCVE-2024-46679, CVE-2024-46681, CVE-2024-43819, CVE-2024-46776,\nCVE-2024-44954, CVE-2024-45022, CVE-2024-46819, CVE-2024-46775,\nCVE-2024-43824, CVE-2024-44953, CVE-2024-46759, CVE-2024-43873,\nCVE-2024-46756, CVE-2024-42303, CVE-2024-46738, CVE-2024-42290,\nCVE-2024-42295, CVE-2024-43849, CVE-2024-44931, CVE-2024-46741,\nCVE-2024-43863, CVE-2024-44974, CVE-2024-46829, CVE-2024-44959,\nCVE-2024-42315, CVE-2024-44983, CVE-2024-46715, CVE-2024-46697,\nCVE-2024-43850, CVE-2024-46728, CVE-2024-44963, CVE-2024-46823,\nCVE-2024-46692, CVE-2024-46760, CVE-2024-46705, CVE-2024-42261,\nCVE-2024-42321, CVE-2024-46785, CVE-2024-46686, CVE-2024-49984,\nCVE-2024-46706, CVE-2024-45029, CVE-2024-46809, CVE-2024-43827,\nCVE-2024-44998, CVE-2024-47667, CVE-2024-43835, CVE-2024-46866,\nCVE-2024-46841, CVE-2024-42286, CVE-2024-43852, CVE-2024-43832,\nCVE-2024-46773, CVE-2024-46817, CVE-2024-46868, CVE-2024-46812,\nCVE-2024-47660, CVE-2024-46725, CVE-2024-42288, CVE-2024-46824,\nCVE-2024-42269, CVE-2024-44957, CVE-2024-45017, CVE-2024-46747,\nCVE-2024-47662, CVE-2024-46843, CVE-2024-46849, CVE-2024-43879,\nCVE-2024-46751, CVE-2024-42298, CVE-2024-46861, CVE-2024-44993,\nCVE-2024-46729, CVE-2024-46846, CVE-2024-46794, CVE-2024-43826,\nCVE-2024-44973, CVE-2024-46672, CVE-2024-44985, CVE-2024-46815,\nCVE-2024-46822, CVE-2024-46754, CVE-2024-43854, CVE-2024-42278,\nCVE-2024-46720, CVE-2024-46677, CVE-2024-46854, CVE-2024-43840,\nCVE-2024-43830, CVE-2024-46804, CVE-2024-45013, CVE-2024-46782,\nCVE-2024-46840, CVE-2024-44977, CVE-2024-46838, CVE-2024-42264,\nCVE-2024-47661, CVE-2024-43857, CVE-2023-52918, CVE-2024-44935,\nCVE-2024-46739, CVE-2024-43825, CVE-2024-43864, CVE-2024-47659,\nCVE-2024-42260, CVE-2024-44962, CVE-2024-46835, CVE-2024-43871,\nCVE-2024-47674, CVE-2024-46827, CVE-2024-42283, CVE-2024-42299,\nCVE-2024-46714, CVE-2024-46740, CVE-2024-46680, CVE-2024-46791,\nCVE-2024-43912, CVE-2024-46813, CVE-2024-46733, CVE-2024-47664,\nCVE-2024-42279, CVE-2024-46850, CVE-2024-42289, CVE-2024-46808,\nCVE-2024-43880, CVE-2024-46832, CVE-2024-42276, CVE-2024-44937,\nCVE-2024-42274, CVE-2024-46772, CVE-2024-47666, CVE-2024-44956,\nCVE-2024-46763, CVE-2024-46805, CVE-2023-52889, CVE-2024-46678,\nCVE-2024-43902, CVE-2024-46757, CVE-2024-46792, CVE-2024-42268,\nCVE-2024-43853, CVE-2024-45027, CVE-2024-42305, CVE-2024-46828,\nCVE-2024-43900, CVE-2024-46848, CVE-2024-46814, CVE-2024-46855,\nCVE-2024-46727, CVE-2024-46836, CVE-2024-46744, CVE-2024-46780,\nCVE-2024-46745, CVE-2024-42306)\n","status":"published","published":"2025-01-06T14:27:24Z","modified":"2026-10-29T20:02:35.84578781Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7155-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency 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  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Bitmap API;\n  - BPF subsystem;\n  - Memory Management;\n  - Objagg library;\n  - Perf events;\n  - Virtio network driver;\n  - VMware vSockets driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - KUnit for arithmetic overflow checks;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Real-Time Linux Analysis tools;\n(CVE-2024-43845, CVE-2024-42311, CVE-2024-46757, CVE-2024-46738,\nCVE-2024-44961, CVE-2024-44935, CVE-2024-46845, CVE-2024-46783,\nCVE-2024-42315, CVE-2023-52918, CVE-2024-46708, CVE-2024-44934,\nCVE-2024-42298, CVE-2024-46786, CVE-2024-46778, CVE-2024-44960,\nCVE-2024-42295, CVE-2024-43881, CVE-2024-44971, CVE-2024-43849,\nCVE-2024-43914, CVE-2024-44962, CVE-2024-43841, CVE-2024-46794,\nCVE-2024-46752, CVE-2024-46853, CVE-2024-46861, CVE-2024-47664,\nCVE-2024-46717, CVE-2024-46806, CVE-2024-46797, CVE-2024-42261,\nCVE-2024-46828, CVE-2024-45013, CVE-2024-46870, CVE-2024-42258,\nCVE-2024-46689, CVE-2024-43818, CVE-2024-46762, CVE-2024-46825,\nCVE-2024-46698, CVE-2024-46816, CVE-2024-46728, CVE-2024-46726,\nCVE-2024-43835, CVE-2024-45000, CVE-2024-43850, CVE-2024-43840,\nCVE-2024-46846, CVE-2024-43846, CVE-2024-46725, CVE-2024-46867,\nCVE-2024-42310, CVE-2024-42274, CVE-2024-46760, CVE-2024-46683,\nCVE-2024-42304, CVE-2024-43839, CVE-2024-44954, CVE-2024-43895,\nCVE-2024-44967, CVE-2024-43889, CVE-2024-46854, CVE-2024-46860,\nCVE-2024-45029, CVE-2024-44938, CVE-2024-46785, CVE-2024-46713,\nCVE-2024-46715, CVE-2024-46731, CVE-2024-42297, CVE-2024-43912,\nCVE-2024-46751, CVE-2024-46711, CVE-2024-46695, CVE-2024-42317,\nCVE-2024-44957, CVE-2024-46792, CVE-2024-45020, CVE-2024-44985,\nCVE-2024-46746, CVE-2024-43868, CVE-2024-45017, CVE-2024-46824,\nCVE-2024-46787, CVE-2024-42288, CVE-2024-46681, CVE-2024-42306,\nCVE-2024-46755, CVE-2024-46826, CVE-2024-46777, CVE-2024-46844,\nCVE-2024-44972, CVE-2024-43883, CVE-2024-43909, CVE-2024-46676,\nCVE-2024-46798, CVE-2024-42273, CVE-2024-44990, CVE-2024-46744,\nCVE-2024-42305, CVE-2024-45006, CVE-2024-42309, CVE-2024-46722,\nCVE-2024-44956, CVE-2024-46739, CVE-2024-46680, CVE-2024-46765,\nCVE-2024-46714, CVE-2024-46771, CVE-2024-46847, CVE-2024-43879,\nCVE-2024-46703, CVE-2024-46733, CVE-2024-46815, CVE-2024-46802,\nCVE-2024-45027, CVE-2024-42281, CVE-2024-43891, CVE-2024-45030,\nCVE-2024-47662, CVE-2024-43887, CVE-2024-46836, CVE-2024-46782,\nCVE-2024-46835, CVE-2024-43907, CVE-2024-46779, CVE-2024-43869,\nCVE-2024-43821, CVE-2024-44978, CVE-2024-42286, CVE-2023-52889,\nCVE-2024-43852, CVE-2024-42320, CVE-2024-44931, CVE-2024-44993,\nCVE-2024-46829, CVE-2024-46701, CVE-2024-42272, CVE-2024-47660,\nCVE-2024-49984, CVE-2024-44973, CVE-2024-43817, CVE-2024-42322,\nCVE-2024-43830, CVE-2024-42301, CVE-2024-44969, CVE-2024-47674,\nCVE-2024-46702, CVE-2024-45025, CVE-2024-46710, CVE-2024-43866,\nCVE-2024-46718, CVE-2024-46773, CVE-2024-43834, CVE-2024-46754,\nCVE-2024-46871, CVE-2024-44942, CVE-2024-43913, CVE-2024-46818,\nCVE-2024-42318, CVE-2024-43831, CVE-2024-43832, CVE-2024-43908,\nCVE-2024-43827, CVE-2024-46737, CVE-2024-47665, CVE-2024-43854,\nCVE-2024-46707, CVE-2024-42303, CVE-2024-43860, CVE-2024-43824,\nCVE-2024-45019, CVE-2024-44984, CVE-2024-46813, CVE-2024-45022,\nCVE-2024-44970, CVE-2024-46791, CVE-2024-45012, CVE-2024-43829,\nCVE-2024-46850, CVE-2024-44987, CVE-2024-44940, CVE-2024-43864,\nCVE-2024-46723, CVE-2024-44999, CVE-2024-43884, CVE-2024-42287,\nCVE-2024-46675, CVE-2024-44974, CVE-2024-46721, CVE-2024-44937,\nCVE-2024-45008, CVE-2024-43853, CVE-2024-46697, CVE-2024-43899,\nCVE-2024-43823, CVE-2024-46747, CVE-2024-45007, CVE-2024-46822,\nCVE-2024-42262, CVE-2024-47661, CVE-2024-44953, CVE-2024-46859,\nCVE-2024-46694, CVE-2024-42279, CVE-2024-43873, CVE-2024-43828,\nCVE-2024-46851, CVE-2024-42296, CVE-2024-46719, CVE-2024-46677,\nCVE-2024-42259, CVE-2024-44941, CVE-2024-44946, CVE-2024-46745,\nCVE-2024-42299, CVE-2024-46724, CVE-2024-46749, CVE-2024-46706,\nCVE-2024-42267, CVE-2024-46774, CVE-2024-46685, CVE-2024-42292,\nCVE-2024-47667, CVE-2024-42319, CVE-2024-43888, CVE-2024-46729,\nCVE-2024-44947, CVE-2024-45003, CVE-2024-46827, CVE-2024-46693,\nCVE-2024-46705, CVE-2024-46767, CVE-2024-46838, CVE-2024-46805,\nCVE-2024-43904, CVE-2024-43906, CVE-2024-42265, CVE-2024-42278,\nCVE-2024-46750, CVE-2024-46692, CVE-2024-43847, CVE-2024-44995,\nCVE-2024-43825, CVE-2024-46803, CVE-2024-47669, CVE-2024-46830,\nCVE-2024-46784, CVE-2024-46840, CVE-2024-44939, CVE-2024-46848,\nCVE-2024-42313, CVE-2024-46823, CVE-2024-44989, CVE-2024-42270,\nCVE-2024-43856, CVE-2024-46716, CVE-2024-43859, CVE-2024-46841,\nCVE-2024-47658, CVE-2024-46811, CVE-2024-45028, CVE-2024-46781,\nCVE-2024-42290, CVE-2024-44991, CVE-2024-43894, CVE-2024-44979,\nCVE-2024-46804, CVE-2024-43826, CVE-2024-43877, CVE-2024-42284,\nCVE-2024-43876, CVE-2024-45011, CVE-2024-43819, CVE-2024-46709,\nCVE-2024-43867, CVE-2024-44963, CVE-2024-45010, CVE-2024-46753,\nCVE-2024-46759, CVE-2024-43880, CVE-2024-44977, CVE-2024-46772,\nCVE-2024-44950, CVE-2024-46687, CVE-2024-46834, CVE-2024-43911,\nCVE-2024-45015, CVE-2024-46819, CVE-2024-43875, CVE-2024-44996,\nCVE-2024-44988, CVE-2024-46673, CVE-2024-44943, CVE-2024-42316,\nCVE-2024-47683, CVE-2024-42307, CVE-2024-46788, CVE-2024-43892,\nCVE-2024-47659, CVE-2024-46857, CVE-2024-43820, CVE-2024-46832,\nCVE-2024-42312, CVE-2024-43910, CVE-2024-43886, CVE-2024-43905,\nCVE-2024-46766, CVE-2024-42263, CVE-2024-46821, CVE-2024-43842,\nCVE-2024-43857, CVE-2024-42276, CVE-2024-42268, CVE-2024-46740,\nCVE-2024-46843, CVE-2024-46807, CVE-2024-46780, CVE-2024-46678,\nCVE-2024-44944, CVE-2024-42264, CVE-2024-43863, CVE-2024-39472,\nCVE-2024-46691, CVE-2024-44959, CVE-2024-44958, CVE-2024-46679,\nCVE-2024-43843, CVE-2024-43900, CVE-2024-45021, CVE-2024-44982,\nCVE-2024-46793, CVE-2024-42260, CVE-2024-43890, CVE-2024-43871,\nCVE-2024-42269, CVE-2024-42277, CVE-2024-46720, CVE-2024-45005,\nCVE-2024-46727, CVE-2024-46808, CVE-2024-46852, CVE-2024-47668,\nCVE-2024-42321, CVE-2024-46743, CVE-2024-45002, CVE-2024-46763,\nCVE-2024-46817, CVE-2024-42285, CVE-2024-46770, CVE-2024-45026,\nCVE-2024-46768, CVE-2024-42314, CVE-2024-42291, CVE-2024-46756,\nCVE-2024-42283, CVE-2024-45018, CVE-2024-44966, CVE-2024-42289,\nCVE-2024-42294, CVE-2024-46814, CVE-2024-44986, CVE-2024-43870,\nCVE-2024-44980, CVE-2024-43902, CVE-2024-47666, CVE-2024-46864,\nCVE-2024-46761, CVE-2024-46831, CVE-2024-46758, CVE-2024-46735,\nCVE-2024-46858, CVE-2024-46795, CVE-2024-46810, CVE-2024-46849,\nCVE-2024-46775, CVE-2024-46868, CVE-2024-46809, CVE-2024-46776,\nCVE-2024-46866, CVE-2024-44983, CVE-2024-46741, CVE-2024-43837,\nCVE-2024-43833, CVE-2024-46672, CVE-2024-43861, CVE-2024-42302,\nCVE-2024-47663, CVE-2024-46812, CVE-2024-43893, CVE-2024-46686,\nCVE-2024-44948, CVE-2024-46732, CVE-2024-44965, CVE-2024-46855,\nCVE-2024-45009, CVE-2024-46842, CVE-2024-46730, CVE-2024-44975,\nCVE-2024-44998)\n","status":"published","published":"2024-12-12T17:27:40Z","modified":"2026-10-29T20:02:55.939765335Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7156-1","title":"linux-gkeop vulnerabilities","description":"\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\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  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - Cirrus firmware drivers;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - Device tree and open firmware driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Bitmap API;\n  - BPF subsystem;\n  - Syscall compatibility layer;\n  - Memory Management;\n  - Memory management;\n  - Objagg library;\n  - Perf events;\n  - Syscall interfaces;\n  - Virtio network driver;\n  - VMware vSockets driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - Scheduler infrastructure;\n  - Closures library;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - KUnit for arithmetic overflow checks;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n  - USB sound devices;\n  - Real-Time Linux Analysis tools;\n(CVE-2024-43911, CVE-2024-46762, CVE-2024-46794, CVE-2024-43843,\nCVE-2024-42229, CVE-2024-43888, CVE-2024-44978, CVE-2024-46693,\nCVE-2024-46695, CVE-2024-42290, CVE-2024-42067, CVE-2024-45012,\nCVE-2024-42316, CVE-2024-47665, CVE-2024-41052, CVE-2024-42074,\nCVE-2024-41058, CVE-2024-44975, CVE-2024-46709, CVE-2024-46871,\nCVE-2024-42090, CVE-2024-42296, CVE-2024-42096, CVE-2024-42146,\nCVE-2024-46855, CVE-2024-39487, CVE-2024-43825, CVE-2024-42066,\nCVE-2024-42126, CVE-2024-41022, CVE-2024-41025, CVE-2023-52888,\nCVE-2024-46702, CVE-2024-42269, CVE-2024-41082, CVE-2024-42284,\nCVE-2024-42227, CVE-2024-41017, CVE-2024-42250, CVE-2024-46778,\nCVE-2024-47661, CVE-2024-46727, CVE-2024-46845, CVE-2024-44953,\nCVE-2024-47659, CVE-2024-42137, CVE-2024-42245, CVE-2024-41096,\nCVE-2024-46829, CVE-2024-41053, CVE-2024-46782, CVE-2024-44972,\nCVE-2024-41095, CVE-2024-42239, CVE-2024-42127, CVE-2024-42292,\nCVE-2024-46752, CVE-2024-46679, CVE-2024-41076, CVE-2024-46784,\nCVE-2024-46786, CVE-2024-46678, CVE-2024-44957, CVE-2024-46755,\nCVE-2024-47660, CVE-2024-41067, CVE-2024-46838, CVE-2024-43879,\nCVE-2024-45007, CVE-2024-45025, CVE-2024-45001, CVE-2024-41009,\nCVE-2024-41051, CVE-2024-46836, CVE-2024-49984, CVE-2024-45028,\nCVE-2024-43871, CVE-2024-46783, CVE-2024-42272, CVE-2024-42087,\nCVE-2024-46785, CVE-2024-42276, CVE-2024-47658, CVE-2024-46761,\nCVE-2024-46715, CVE-2024-46676, CVE-2024-43824, CVE-2024-42100,\nCVE-2024-46745, CVE-2024-41084, CVE-2024-41086, CVE-2024-45015,\nCVE-2024-46797, CVE-2024-42160, CVE-2024-46706, CVE-2024-46803,\nCVE-2024-46708, CVE-2024-47669, CVE-2024-45009, CVE-2024-41021,\nCVE-2024-42159, CVE-2024-42321, CVE-2024-46868, CVE-2024-41078,\nCVE-2024-42303, CVE-2024-45027, CVE-2024-42309, CVE-2024-43849,\nCVE-2024-43907, CVE-2024-43899, CVE-2024-43823, CVE-2024-42232,\nCVE-2024-44937, CVE-2024-41046, CVE-2024-42237, CVE-2024-42063,\nCVE-2024-42065, CVE-2024-42154, CVE-2024-42259, CVE-2024-46698,\nCVE-2024-46741, CVE-2024-45020, CVE-2024-42151, CVE-2024-41073,\nCVE-2024-46719, CVE-2024-42295, CVE-2024-46859, CVE-2024-41035,\nCVE-2024-46751, CVE-2024-47667, CVE-2024-46728, CVE-2024-46824,\nCVE-2024-42121, CVE-2024-46776, CVE-2024-46768, CVE-2024-43908,\nCVE-2024-43900, CVE-2024-46707, CVE-2024-44934, CVE-2024-41062,\nCVE-2024-42304, CVE-2024-42312, CVE-2024-42157, CVE-2024-41092,\nCVE-2024-41041, CVE-2024-43832, CVE-2024-41039, CVE-2024-44962,\nCVE-2024-46858, CVE-2024-43856, CVE-2024-41060, CVE-2024-45010,\nCVE-2024-41044, CVE-2024-44942, CVE-2024-42307, CVE-2024-44984,\nCVE-2024-41075, CVE-2024-43817, CVE-2024-46791, CVE-2024-46853,\nCVE-2024-42301, CVE-2024-44993, CVE-2024-41094, CVE-2024-27022,\nCVE-2024-41088, CVE-2024-43883, CVE-2024-41087, CVE-2024-46780,\nCVE-2024-42070, CVE-2024-44965, CVE-2024-46823, CVE-2024-46737,\nCVE-2024-44982, CVE-2024-46697, CVE-2024-45021, CVE-2024-44987,\nCVE-2024-41072, CVE-2024-41063, CVE-2024-46757, CVE-2024-46831,\nCVE-2024-44966, CVE-2024-42322, CVE-2024-42231, CVE-2024-46717,\nCVE-2024-41065, CVE-2024-44969, CVE-2023-52887, CVE-2024-42105,\nCVE-2024-44971, CVE-2024-46798, CVE-2024-42262, CVE-2024-44938,\nCVE-2024-42088, CVE-2024-44970, CVE-2024-43876, CVE-2024-46800,\nCVE-2024-42086, CVE-2024-43826, CVE-2024-46729, CVE-2024-46747,\nCVE-2024-46691, CVE-2024-46723, CVE-2024-41018, CVE-2024-42258,\nCVE-2024-41081, CVE-2024-41049, CVE-2024-43837, CVE-2024-45008,\nCVE-2024-41047, CVE-2024-41019, CVE-2024-42152, CVE-2024-41090,\nCVE-2024-46716, CVE-2024-42104, CVE-2024-46804, CVE-2024-43852,\nCVE-2024-42129, CVE-2024-46870, CVE-2024-41093, CVE-2024-45011,\nCVE-2024-41064, CVE-2024-46722, CVE-2024-42286, CVE-2024-45026,\nCVE-2024-46818, CVE-2024-42281, CVE-2024-43854, CVE-2024-41037,\nCVE-2024-44946, CVE-2024-41012, CVE-2024-41098, CVE-2024-42263,\nCVE-2024-42095, CVE-2024-46756, CVE-2024-43913, CVE-2024-46822,\nCVE-2024-44944, CVE-2024-42156, CVE-2024-42073, CVE-2024-42093,\nCVE-2024-44931, CVE-2024-42223, CVE-2024-42264, CVE-2024-42278,\nCVE-2024-46759, CVE-2024-46826, CVE-2024-43828, CVE-2024-42318,\nCVE-2024-42240, CVE-2024-45000, CVE-2024-43909, CVE-2024-46792,\nCVE-2024-42109, CVE-2024-43867, CVE-2024-42130, CVE-2024-42244,\nCVE-2024-44977, CVE-2024-46774, CVE-2024-41030, CVE-2024-42310,\nCVE-2024-42138, CVE-2024-42317, CVE-2024-42224, CVE-2024-46694,\nCVE-2024-46815, CVE-2024-46677, CVE-2024-46763, CVE-2024-46860,\nCVE-2024-46767, CVE-2024-42111, CVE-2024-41020, CVE-2024-46726,\nCVE-2024-42117, CVE-2024-43831, CVE-2024-42285, CVE-2024-46842,\nCVE-2024-43857, CVE-2024-41031, CVE-2024-43834, CVE-2024-42135,\nCVE-2024-42241, CVE-2024-46846, CVE-2024-44988, CVE-2024-43892,\nCVE-2024-44991, CVE-2024-46806, CVE-2024-41015, CVE-2024-43906,\nCVE-2024-42238, CVE-2024-46779, CVE-2024-41010, CVE-2024-41068,\nCVE-2024-46730, CVE-2024-46827, CVE-2024-42120, CVE-2024-41059,\nCVE-2024-46850, CVE-2023-52889, CVE-2024-45017, CVE-2024-45003,\nCVE-2024-46844, CVE-2024-46816, CVE-2024-46811, CVE-2024-41023,\nCVE-2024-44948, CVE-2024-46753, CVE-2024-45002, CVE-2024-42251,\nCVE-2024-46713, CVE-2024-42273, CVE-2024-46733, CVE-2024-46739,\nCVE-2024-42108, CVE-2024-41085, CVE-2024-41033, CVE-2024-42298,\nCVE-2024-46835, CVE-2024-39472, CVE-2024-47663, CVE-2024-43859,\nCVE-2024-43820, CVE-2024-42118, CVE-2024-41036, CVE-2024-47683,\nCVE-2024-42161, CVE-2024-42235, CVE-2024-43861, CVE-2024-43863,\nCVE-2024-47668, CVE-2024-46685, CVE-2024-43864, CVE-2024-46749,\nCVE-2024-44983, CVE-2024-46841, CVE-2024-42082, CVE-2024-43818,\nCVE-2024-41071, CVE-2024-45006, CVE-2024-42080, CVE-2024-46825,\nCVE-2024-46687, CVE-2024-44959, CVE-2024-43835, CVE-2024-43891,\nCVE-2024-46851, CVE-2024-42248, CVE-2024-42103, CVE-2024-42079,\nCVE-2024-42068, CVE-2024-47664, CVE-2024-46854, CVE-2024-44973,\nCVE-2024-42077, CVE-2024-46821, CVE-2024-43886, CVE-2024-41089,\nCVE-2024-43850, CVE-2024-44995, CVE-2024-46809, CVE-2024-42084,\nCVE-2024-46758, CVE-2024-47662, CVE-2024-43839, CVE-2024-46738,\nCVE-2024-41034, CVE-2024-42228, CVE-2024-42147, CVE-2024-43855,\nCVE-2024-41032, CVE-2024-46819, CVE-2024-44989, CVE-2024-42265,\nCVE-2024-42110, CVE-2024-42155, CVE-2024-45005, CVE-2024-45016,\nCVE-2024-42141, CVE-2024-43821, CVE-2024-42299, CVE-2024-44950,\nCVE-2024-42279, CVE-2024-44943, CVE-2024-43904, CVE-2024-42268,\nCVE-2024-42089, CVE-2024-46807, CVE-2024-44996, CVE-2024-42069,\nCVE-2024-46672, CVE-2024-44940, CVE-2024-42270, CVE-2024-46735,\nCVE-2024-42319, CVE-2024-46754, CVE-2024-46861, CVE-2024-42277,\nCVE-2024-41054, CVE-2024-42131, CVE-2024-41056, CVE-2024-44963,\nCVE-2024-42267, CVE-2024-42283, CVE-2024-42320, CVE-2024-46740,\nCVE-2024-46787, CVE-2024-43895, CVE-2024-43881, CVE-2024-44961,\nCVE-2024-43910, CVE-2024-43875, CVE-2024-42289, CVE-2024-43853,\nCVE-2024-42315, CVE-2024-43884, CVE-2024-46867, CVE-2024-43912,\nCVE-2024-41007, CVE-2024-46743, CVE-2024-46675, CVE-2024-43877,\nCVE-2024-39486, CVE-2024-41050, CVE-2024-43858, CVE-2024-45018,\nCVE-2024-46744, CVE-2024-46750, CVE-2024-46840, CVE-2024-42150,\nCVE-2024-41028, CVE-2024-42091, CVE-2024-43894, CVE-2024-43869,\nCVE-2024-42132, CVE-2024-46777, CVE-2024-42106, CVE-2024-46848,\nCVE-2024-41038, CVE-2024-46711, CVE-2024-43833, CVE-2024-46710,\nCVE-2024-46812, CVE-2024-42311, CVE-2024-46701, CVE-2024-46683,\nCVE-2024-45029, CVE-2024-46830, CVE-2024-46857, CVE-2024-44979,\nCVE-2024-44999, CVE-2024-44985, CVE-2024-46773, CVE-2024-45022,\nCVE-2024-46772, CVE-2024-44960, CVE-2024-42243, CVE-2024-42158,\nCVE-2024-43819, CVE-2024-45030, CVE-2024-42085, CVE-2024-42274,\nCVE-2024-44986, CVE-2024-41048, CVE-2024-42098, CVE-2024-46680,\nCVE-2023-52918, CVE-2024-46673, CVE-2024-46834, CVE-2024-42288,\nCVE-2024-44998, CVE-2024-42113, CVE-2024-42094, CVE-2024-42225,\nCVE-2024-42112, CVE-2024-42153, CVE-2024-43880, CVE-2024-43905,\nCVE-2024-43902, CVE-2024-46681, CVE-2024-42236, CVE-2024-42294,\nCVE-2024-46793, CVE-2024-43882, CVE-2024-44947, CVE-2024-46849,\nCVE-2024-44954, CVE-2024-46852, CVE-2024-41070, CVE-2024-41069,\nCVE-2024-46864, CVE-2024-46703, CVE-2024-43829, CVE-2024-46802,\nCVE-2024-42101, CVE-2024-44990, CVE-2024-43830, CVE-2024-41029,\nCVE-2024-43866, CVE-2024-43889, CVE-2024-42230, CVE-2024-46692,\nCVE-2024-42133, CVE-2024-45013, CVE-2024-42076, CVE-2024-46810,\nCVE-2024-42128, CVE-2024-46718, CVE-2024-46814, CVE-2024-43841,\nCVE-2024-43873, CVE-2024-42092, CVE-2024-41074, CVE-2024-41083,\nCVE-2024-46731, CVE-2024-43842, CVE-2024-41077, CVE-2024-46720,\nCVE-2024-46795, CVE-2024-46813, CVE-2024-46805, CVE-2024-42142,\nCVE-2024-42291, CVE-2024-43846, CVE-2024-41057, CVE-2024-43870,\nCVE-2024-44980, CVE-2024-46866, CVE-2024-43827, CVE-2024-43840,\nCVE-2024-42280, CVE-2024-42261, CVE-2024-42246, CVE-2024-42115,\nCVE-2024-46686, CVE-2024-43860, CVE-2024-46808, CVE-2024-42149,\nCVE-2024-46828, CVE-2024-44935, CVE-2024-43847, CVE-2024-44967,\nCVE-2024-46817, CVE-2024-46721, CVE-2024-42305, CVE-2024-46766,\nCVE-2024-43914, CVE-2024-46760, CVE-2024-41061, CVE-2024-41091,\nCVE-2024-43890, CVE-2024-42314, CVE-2024-42064, CVE-2024-42302,\nCVE-2024-43887, CVE-2024-46832, CVE-2024-46765, CVE-2024-46770,\nCVE-2024-41080, CVE-2024-42253, CVE-2024-44941, CVE-2024-42306,\nCVE-2024-41027, CVE-2024-46689, CVE-2024-46781, CVE-2024-42247,\nCVE-2024-41066, CVE-2024-42287, CVE-2024-41097, CVE-2024-44939,\nCVE-2024-45019, CVE-2024-47674, CVE-2024-46705, CVE-2024-42119,\nCVE-2024-46725, CVE-2024-46746, CVE-2024-46732, CVE-2024-41042,\nCVE-2024-44958, CVE-2024-42114, CVE-2024-43893, CVE-2024-47666,\nCVE-2024-46843, CVE-2024-42252, CVE-2024-42102, CVE-2024-42136,\nCVE-2024-41045, CVE-2024-42260, CVE-2024-46771, CVE-2024-42124,\nCVE-2024-42297, CVE-2024-42271, CVE-2024-43845, CVE-2024-46775,\nCVE-2024-41079, CVE-2024-43868, CVE-2024-42140, CVE-2024-42313,\nCVE-2024-42145, CVE-2024-46724, CVE-2024-46788, CVE-2024-42234,\nCVE-2024-42144, CVE-2024-44974, CVE-2024-42097, CVE-2024-46714,\nCVE-2024-41055, CVE-2024-44956)\n","status":"published","published":"2024-12-12T17:47:44Z","modified":"2026-10-29T20:02:38.448595714Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7183-1","title":"linux, linux-lts-xenial vulnerabilities","description":"Andy Nguyen discovered that the Bluetooth L2CAP implementation in the Linux\nkernel contained a type-confusion error. A physically proximate remote\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2020-12351)\n\nAndy Nguyen discovered that the Bluetooth A2MP implementation in the Linux\nkernel did not properly initialize memory in some situations. A physically\nproximate remote attacker could use this to expose sensitive information\n(kernel memory). (CVE-2020-12352)\n\nAndy Nguyen discovered that the Bluetooth HCI event packet parser in the\nLinux kernel did not properly handle event advertisements of certain sizes,\nleading to a heap-based buffer overflow. A physically proximate remote\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2020-24490)\n\nZiming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux\nkernel contained an integer overflow vulnerability. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2022-36402)\n\nZheng Wang discovered a use-after-free in the Renesas Ethernet AVB driver\nin the Linux kernel during device removal. A privileged attacker could use\nthis to cause a denial of service (system crash). (CVE-2023-35827)\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  - GPU drivers;\n  - I2C subsystem;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - TTY drivers;\n  - USB Mass Storage drivers;\n  - Framebuffer layer;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - Bluetooth subsystem;\n  - Kernel init infrastructure;\n  - DMA mapping infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - NFC subsystem;\n  - Phonet protocol;\n  - Network traffic control;\n  - Wireless networking;\n(CVE-2024-44947, CVE-2023-52594, CVE-2024-35886, CVE-2024-38633,\nCVE-2023-52509, CVE-2024-26625, CVE-2024-36946, CVE-2024-45021,\nCVE-2024-36270, CVE-2021-47118, CVE-2024-43884, CVE-2024-36941,\nCVE-2024-38619, CVE-2021-47501, CVE-2024-49967, CVE-2024-42090,\nCVE-2024-40912, CVE-2024-36968, CVE-2024-53057, CVE-2023-52507,\nCVE-2024-42101, CVE-2021-47086, CVE-2024-42153, CVE-2024-40959,\nCVE-2024-26777, CVE-2024-44944, CVE-2024-43856, CVE-2024-39301)\n","status":"published","published":"2025-01-06T19:07:53Z","modified":"2026-10-29T20:03:08.541371653Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7184-1","title":"linux-aws, linux-kvm vulnerabilities","description":"Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux\nkernel contained an integer overflow vulnerability. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2022-36402)\n\nZheng Wang discovered a use-after-free in the Renesas Ethernet AVB driver\nin the Linux kernel during device removal. A privileged attacker could use\nthis to cause a denial of service (system crash). (CVE-2023-35827)\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  - GPU drivers;\n  - I2C subsystem;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - TTY drivers;\n  - USB Mass Storage drivers;\n  - Framebuffer layer;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - Bluetooth subsystem;\n  - Kernel init infrastructure;\n  - DMA mapping infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - NFC subsystem;\n  - Phonet protocol;\n  - Network traffic control;\n  - Wireless networking;\n(CVE-2024-44944, CVE-2023-52507, CVE-2024-42101, CVE-2021-47118,\nCVE-2024-36941, CVE-2024-38633, CVE-2021-47086, CVE-2024-26625,\nCVE-2024-39301, CVE-2024-42090, CVE-2024-53057, CVE-2024-26777,\nCVE-2024-36946, CVE-2024-42153, CVE-2024-40912, CVE-2024-36968,\nCVE-2024-43856, CVE-2024-49967, CVE-2024-43884, CVE-2023-52509,\nCVE-2023-52594, CVE-2024-36270, CVE-2024-44947, CVE-2024-45021,\nCVE-2024-35886, CVE-2024-40959, CVE-2021-47501, CVE-2024-38619)\n","status":"published","published":"2025-01-06T19:14:47Z","modified":"2026-10-29T20:02:33.407583567Z","updated_at":"2026-11-02T16:58:18.876384Z"}]},"sources_more":{"osv":4}}