{"id":"CVE-2024-45026","aliases":["AZL-49187","AZL-49266","BELL-CVE-2024-45026","DEBIAN-CVE-2024-45026","DLA-4008-1","DSA-5782-1","EUVD-2024-41506","GHSA-66cw-5j4x-3r2w","OESA-2024-2255","OESA-2024-2257","OESA-2024-2258","OESA-2024-2522","RHSA-2024:10941","RHSA-2024:7000","RLSA-2024:7000","ROOT-OS-DEBIAN-11-CVE-2024-45026","SUSE-SU-2024:3551-1","SUSE-SU-2024:3553-1","SUSE-SU-2024:3561-1","SUSE-SU-2024:3564-1","SUSE-SU-2024:3569-1","SUSE-SU-2024:3587-1","SUSE-SU-2024:3592-1","SUSE-SU-2024:4081-1","SUSE-SU-2024:4082-1","SUSE-SU-2024:4131-1","SUSE-SU-2024:4140-1","SUSE-SU-2025:20073-1","SUSE-SU-2025:20077-1","UBUNTU-CVE-2024-45026","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-7194-1","USN-7196-1"],"status":"published","title":"s390/dasd: fix error recovery leading to data corruption on ESE devices","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","severity":{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00239,"percentile":0.15062,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-787"],"published":"2024-09-11T15:13:58Z","modified":"2026-11-11T09:38:28Z","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":["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":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"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-5.4","fixed_in":["5.4.0-1140.147~18.04.1"],"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-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: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":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.3.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-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:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-232.0.0.134.oe2203sp3"}]}],"bundled":46},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.97.0.178.oe2203sp1"}]}],"bundled":46},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-232.0.0.131.oe2203sp4"}]}],"bundled":72},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-61.0.0.60.oe2403"}]}],"bundled":66},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-477.83.1.el8_8"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Rocky Linux:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":147},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"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 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 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 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 Micro 5.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.191.1"}]}],"bundled":50},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.191.1"}]}],"bundled":50},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.191.1"}]}],"bundled":50},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.191.1"}]}],"bundled":50},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.100.1"}]}],"bundled":101},{"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.100.1"}]}],"bundled":101},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.100.1"}]}],"bundled":101},{"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.100.1"}]}],"bundled":101},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"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.141.1.150400.24.68.2"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"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.141.1.150400.24.68.2"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-livepatch-SLE15-SP4_Update_33","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150400.9.5.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1.150400.24.68.2"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1.150400.24.68.2"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1.150400.24.68.2"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1.150400.24.68.2"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"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.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1.150400.24.68.2"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1.150400.24.68.2"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.141.1"}]}],"bundled":105},{"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.182.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-livepatch-SLE15-SP3_Update_50","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150300.7.3.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1.150300.18.107.1"}]}],"bundled":49},{"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.182.2"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1.150300.18.107.1"}]}],"bundled":49},{"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.182.2"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1.150300.18.107.1"}]}],"bundled":49},{"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.182.2"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"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.182.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"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.182.1.150300.18.107.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"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.182.1.150300.18.107.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1.150300.18.107.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.2"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.182.1"}]}],"bundled":49},{"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:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu: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: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: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:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu: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: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:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"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: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/19f60a55b2fda49bc4f6134a5f6356ef62ee69d8","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/e245a18281c252c8dbc467492e09bb5d4b012118","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/a665e3b7ac7d5cdc26e00e3d0fc8fd490e00316a","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/0a228896a1b3654cd461ff654f6a64e97a9c3246","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/93a7e2856951680cd7fe6ebd705ac10c8a8a5efd","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/5d4a304338daf83ace2887aaacafd66fe99ed5cc","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/7db4042336580dfd75cb5faa82c12cd51098c90b","tags":["Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45026","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-66cw-5j4x-3r2w"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-45026","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/45xxx/CVE-2024-45026.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-45026","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52444","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52463","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52482","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42290","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42306","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47658","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47672","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2257","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-4134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52707","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36031","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47382","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35825","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38613","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42228","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46825","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47706","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47714","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47718","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47750","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50127","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50128","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50187","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50218","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50300","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53090","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2024:10941","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2256822","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275596","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_10941.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-51779","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-51779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-51779","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/2e07e8348ea454615e268222ae3fc240421be768","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26830","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26830","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041703-CVE-2024-26830-5bc0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45026","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311723","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45026","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091110-CVE-2024-45026-eaa8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2024:7000","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258012","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258013","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2260038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265799","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265838","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266750","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267036","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267041","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267925","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268295","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271796","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272793","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275558","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275661","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275690","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275742","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277171","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278447","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281217","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281704","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281807","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282345","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282354","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282355","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282357","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282366","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282401","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282422","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282508","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282669","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282676","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282757","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282764","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282851","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282890","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282918","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283389","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283424","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284545","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284630","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293247","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293377","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293414","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293423","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293441","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293658","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297473","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297478","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297513","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297525","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297538","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297542","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297556","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297561","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297579","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297582","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297589","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297706","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298079","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298177","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298640","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299336","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299452","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300296","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300297","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300402","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300407","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300409","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300414","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300429","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300434","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300439","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300448","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300453","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300492","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300533","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300709","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301477","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301522","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303077","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-31515","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_7000.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-46984","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-46984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-46984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022824-CVE-2021-46984-e55e@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47097","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47097-e7f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47101-f3fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47287","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47287","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052121-CVE-2021-47287-6345@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47289","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47289","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052122-CVE-2021-47289-7cbb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47321","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47321","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052132-CVE-2021-47321-1b9b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47338","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47338","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47338","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052137-CVE-2021-47338-cd10@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47352","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47352","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052141-CVE-2021-47352-df50@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47383","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47383","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47383-a8f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47384","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47384","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47384-f311@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47385","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47385","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47385-a7e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47386","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47386","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052145-CVE-2021-47386-2701@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47393","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47393","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052147-CVE-2021-47393-ea1c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47412","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47412","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052152-CVE-2021-47412-b362@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47432","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47432","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052143-CVE-2021-47432-5e69@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47441","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47441","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47455","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47455","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052244-CVE-2021-47455-c4a1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47466","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052227-CVE-2021-47466-ff03@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47497","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47497","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052242-CVE-2021-47497-449e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47527","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47527","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052435-CVE-2021-47527-e6f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47560","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47560","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052451-CVE-2021-47560-4a52@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47582","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47582","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061916-CVE-2021-47582-69aa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47609","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47609","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061907-CVE-2021-47609-5ebf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48619","tags":["advisory"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.17.10","tags":["article"]},{"url":"https://github.com/torvalds/linux/commit/409353cbe9fe48f6bc196114c442b1cff05a39bc","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48754","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48754","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062006-CVE-2022-48754-4012@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48760","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48760","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062008-CVE-2022-48760-b80e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48804","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48804","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48804","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071645-CVE-2022-48804-f191@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48836","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48836","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48836","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071620-CVE-2022-48836-fb3d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48866","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071629-CVE-2022-48866-93bd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49226","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022622-CVE-2022-49226-b30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347650","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49316","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022636-CVE-2022-49316-3e10@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373562","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061853-CVE-2022-50072-de2b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6040","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6040","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2024/01/12/1","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52470","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52470","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/0b813a6a0087451cb702b6eb841f10856f49d088","tags":["article"]},{"url":"https://git.kernel.org/stable/c/14bbfaa5df273b26cde6707f6e655585700e6fe1","tags":["article"]},{"url":"https://git.kernel.org/stable/c/21b1645660717d6126dd4866c850fcc5c4703a41","tags":["article"]},{"url":"https://git.kernel.org/stable/c/57ca7984806d79b38af528de88fd803babf27feb","tags":["article"]},{"url":"https://git.kernel.org/stable/c/5d12c5d75f7c78b83a738025947651ec5c95b4d4","tags":["article"]},{"url":"https://git.kernel.org/stable/c/7a2464fac80d42f6f8819fed97a553e9c2f43310","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c4ff55408187f2595066967047363ca84e76db85","tags":["article"]},{"url":"https://git.kernel.org/stable/c/fb2d8bc9b5e55848b8a7c3c028e2ee8d49f28f97","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52476","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52476","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52476-e307@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52478","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52478","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52478-c0a1@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52522","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52522","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52522-6abd@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52605","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52605-292a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52683","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52683","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051751-CVE-2023-52683-f280@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52798","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52798","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52798-374e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52800","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52800","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052159-CVE-2023-52800-63da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52809","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052102-CVE-2023-52809-f07c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52817","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052104-CVE-2023-52817-ba29@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052111-CVE-2023-52840-8a3d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420349","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53847","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120959-CVE-2023-53847-1f94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54269","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54269","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123000-CVE-2023-54269-6fd7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-23848","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-23848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-23848","tags":["advisory"]},{"url":"https://lore.kernel.org/lkml/e9f42704-2f99-4f2c-ade5-f952e5fd53e5%40xs4all.nl/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26595","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2024-26595-9a8d@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26600","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022405-CVE-2024-26600-44a2@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26638","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26638","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-16-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26645","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26645","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326151722.1258576-4-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26649","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26649","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-17-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26665","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26665","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26665-5daa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26717","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26717","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26717-0d01@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26720","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26720","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26720-06fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26769","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26769","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26769","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040307-CVE-2024-26769-e9cc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26846","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041717-CVE-2024-26846-9593@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26855","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26855","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26855-ac0d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26880","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26880-25d6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26894","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26894-53ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26923","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26923","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042418-CVE-2024-26923-f7f6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26939-5314@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27013-2c26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27042","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27042-e812@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35809","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35809-4a4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35877","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35877","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35877-39e6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051946-CVE-2024-35884-d4a4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35944","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35944","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051920-CVE-2024-35944-a860@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052020-CVE-2024-35989-c5da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36883","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36883","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36883-b892@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053035-CVE-2024-36901-fb16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36902","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36902","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36919","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36919","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36920","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36920","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36920-b4a7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36922","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36922","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36922-f0df@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053043-CVE-2024-36939-8453@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36953","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36953","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36953-fc12@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-37356","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-37356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37356","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062137-CVE-2024-37356-cc7b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38558","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38558","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061953-CVE-2024-38558-ddfd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38559","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38559","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061953-CVE-2024-38559-3e03@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38570","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38570","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061956-CVE-2024-38570-a8ef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38579","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38579","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38579","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061947-CVE-2024-38579-e96a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38581","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38581","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061948-CVE-2024-38581-592d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38619","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062035-CVE-2024-38619-97c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39471","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062501-CVE-2024-39471-3dee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39499","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39499","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39499-ed0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071204-CVE-2024-39501-058b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39506","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39506","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39506","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071205-CVE-2024-39506-b0cc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071207-CVE-2024-40901-05c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40904","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40904","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071208-CVE-2024-40904-48b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40911","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40911","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40911-2382@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40912","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40912","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40912-7286@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40929","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071215-CVE-2024-40929-e1cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071216-CVE-2024-40931-77b2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40941","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40941","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071219-CVE-2024-40941-9e5c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40954","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40954","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071223-CVE-2024-40954-093b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40958","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40958-8ed5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40959","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40959-228e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40960-d46f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40972","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40972","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071229-CVE-2024-40972-1569@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40977","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40977","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071230-CVE-2024-40977-07c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40978","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40978","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071231-CVE-2024-40978-d135@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40988","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40988","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40988-490e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40989-c8da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40995","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071251-CVE-2024-40995-2a5c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40997","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40997","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071251-CVE-2024-40997-df97@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40998","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40998","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071252-CVE-2024-40998-90d6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41005","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41005","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071244-CVE-2024-41005-b2a5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41007","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41007","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071513-CVE-2024-41007-777c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41008","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240716080357.2696435-2-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41012","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072314-CVE-2024-41012-a1cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072908-CVE-2024-41013-2996@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41014-9186@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41023","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072917-CVE-2024-41023-32a0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41035","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41035","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072922-CVE-2024-41035-5e6b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072923-CVE-2024-41038-41ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41039","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41039-b3bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41040","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41040","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41040-63d5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41041","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41041","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41041-ae0c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41044","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072925-CVE-2024-41044-5b26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41055","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072928-CVE-2024-41055-5764@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41056","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41056","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072930-CVE-2024-41056-c324@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41060","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072905-CVE-2024-41060-b7de@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41064","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072907-CVE-2024-41064-6ecb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41065","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41065","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072907-CVE-2024-41065-2501@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41071","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41071","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072909-CVE-2024-41071-4eb6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41076","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41076","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41076-6124@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41090","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072916-CVE-2024-41090-9830@gregkh","tags":["article"]},{"url":"https://www.openwall.com/lists/oss-security/2024/07/24/4","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41091","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41091","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072918-CVE-2024-41091-35b7@gregkh","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41097","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072954-CVE-2024-41097-248c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42084","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42084","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072942-CVE-2024-42084-9283@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42090","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072946-CVE-2024-42090-5687@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42094","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42094","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072911-CVE-2024-42094-135f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42096","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072911-CVE-2024-42096-67f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42114","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42114","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073022-CVE-2024-42114-4585@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42124","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073025-CVE-2024-42124-e4ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42131","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42131","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073027-CVE-2024-42131-2f7f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42152","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073034-CVE-2024-42152-c248@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42154","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42154","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073034-CVE-2024-42154-cf82@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42225","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42225","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42225-bdfa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42226","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42226-fa39@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42228","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42228-86f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42237","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42237-eba4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42238","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303506","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42238","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42238-a5fd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42240","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080741-CVE-2024-42240-3d04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42246","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42246","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080742-CVE-2024-42246-0777@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42265","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42265","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081737-CVE-2024-42265-a943@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42322","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305467","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42322","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081755-CVE-2024-42322-e2ef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43830","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43830","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081727-CVE-2024-43830-3b85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43871","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306365","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43871","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43871-c2cd@gregkh/T","tags":["article"]},{"url":"https://errata.rockylinux.org/RLSA-2024:7000","tags":["advisory"]},{"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/1216223","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/1223600","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/1227487","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/1230015","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/1230434","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/1230507","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/1230767","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-44946","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-45021","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-46674","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-46774","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-20243564-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/1229633","tags":["report"]},{"url":"https://bugzilla.suse.com/1229662","tags":["report"]},{"url":"https://bugzilla.suse.com/1229830","tags":["report"]},{"url":"https://bugzilla.suse.com/1229947","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/1230398","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-48911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48935","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-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-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-20244081-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1195775","tags":["report"]},{"url":"https://bugzilla.suse.com/1204171","tags":["report"]},{"url":"https://bugzilla.suse.com/1205796","tags":["report"]},{"url":"https://bugzilla.suse.com/1209290","tags":["report"]},{"url":"https://bugzilla.suse.com/1218562","tags":["report"]},{"url":"https://bugzilla.suse.com/1219125","tags":["report"]},{"url":"https://bugzilla.suse.com/1223384","tags":["report"]},{"url":"https://bugzilla.suse.com/1223524","tags":["report"]},{"url":"https://bugzilla.suse.com/1223824","tags":["report"]},{"url":"https://bugzilla.suse.com/1225189","tags":["report"]},{"url":"https://bugzilla.suse.com/1225336","tags":["report"]},{"url":"https://bugzilla.suse.com/1225611","tags":["report"]},{"url":"https://bugzilla.suse.com/1226145","tags":["report"]},{"url":"https://bugzilla.suse.com/1226211","tags":["report"]},{"url":"https://bugzilla.suse.com/1226212","tags":["report"]},{"url":"https://bugzilla.suse.com/1228743","tags":["report"]},{"url":"https://bugzilla.suse.com/1229042","tags":["report"]},{"url":"https://bugzilla.suse.com/1229454","tags":["report"]},{"url":"https://bugzilla.suse.com/1230429","tags":["report"]},{"url":"https://bugzilla.suse.com/1231073","tags":["report"]},{"url":"https://bugzilla.suse.com/1231191","tags":["report"]},{"url":"https://bugzilla.suse.com/1231193","tags":["report"]},{"url":"https://bugzilla.suse.com/1231195","tags":["report"]},{"url":"https://bugzilla.suse.com/1231197","tags":["report"]},{"url":"https://bugzilla.suse.com/1231200","tags":["report"]},{"url":"https://bugzilla.suse.com/1231203","tags":["report"]},{"url":"https://bugzilla.suse.com/1231293","tags":["report"]},{"url":"https://bugzilla.suse.com/1231375","tags":["report"]},{"url":"https://bugzilla.suse.com/1231502","tags":["report"]},{"url":"https://bugzilla.suse.com/1231673","tags":["report"]},{"url":"https://bugzilla.suse.com/1231861","tags":["report"]},{"url":"https://bugzilla.suse.com/1231887","tags":["report"]},{"url":"https://bugzilla.suse.com/1231890","tags":["report"]},{"url":"https://bugzilla.suse.com/1231893","tags":["report"]},{"url":"https://bugzilla.suse.com/1231895","tags":["report"]},{"url":"https://bugzilla.suse.com/1231936","tags":["report"]},{"url":"https://bugzilla.suse.com/1231938","tags":["report"]},{"url":"https://bugzilla.suse.com/1231942","tags":["report"]},{"url":"https://bugzilla.suse.com/1231960","tags":["report"]},{"url":"https://bugzilla.suse.com/1231961","tags":["report"]},{"url":"https://bugzilla.suse.com/1231979","tags":["report"]},{"url":"https://bugzilla.suse.com/1231987","tags":["report"]},{"url":"https://bugzilla.suse.com/1231988","tags":["report"]},{"url":"https://bugzilla.suse.com/1232033","tags":["report"]},{"url":"https://bugzilla.suse.com/1232069","tags":["report"]},{"url":"https://bugzilla.suse.com/1232070","tags":["report"]},{"url":"https://bugzilla.suse.com/1232097","tags":["report"]},{"url":"https://bugzilla.suse.com/1232136","tags":["report"]},{"url":"https://bugzilla.suse.com/1232145","tags":["report"]},{"url":"https://bugzilla.suse.com/1232262","tags":["report"]},{"url":"https://bugzilla.suse.com/1232282","tags":["report"]},{"url":"https://bugzilla.suse.com/1232286","tags":["report"]},{"url":"https://bugzilla.suse.com/1232304","tags":["report"]},{"url":"https://bugzilla.suse.com/1232383","tags":["report"]},{"url":"https://bugzilla.suse.com/1232418","tags":["report"]},{"url":"https://bugzilla.suse.com/1232424","tags":["report"]},{"url":"https://bugzilla.suse.com/1232432","tags":["report"]},{"url":"https://bugzilla.suse.com/1232519","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-46343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50047","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244082-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1206188","tags":["report"]},{"url":"https://bugzilla.suse.com/1206344","tags":["report"]},{"url":"https://bugzilla.suse.com/1210449","tags":["report"]},{"url":"https://bugzilla.suse.com/1210627","tags":["report"]},{"url":"https://bugzilla.suse.com/1213034","tags":["report"]},{"url":"https://bugzilla.suse.com/1216813","tags":["report"]},{"url":"https://bugzilla.suse.com/1229556","tags":["report"]},{"url":"https://bugzilla.suse.com/1230600","tags":["report"]},{"url":"https://bugzilla.suse.com/1230620","tags":["report"]},{"url":"https://bugzilla.suse.com/1230903","tags":["report"]},{"url":"https://bugzilla.suse.com/1231016","tags":["report"]},{"url":"https://bugzilla.suse.com/1231883","tags":["report"]},{"url":"https://bugzilla.suse.com/1231885","tags":["report"]},{"url":"https://bugzilla.suse.com/1231888","tags":["report"]},{"url":"https://bugzilla.suse.com/1231892","tags":["report"]},{"url":"https://bugzilla.suse.com/1231896","tags":["report"]},{"url":"https://bugzilla.suse.com/1231897","tags":["report"]},{"url":"https://bugzilla.suse.com/1231929","tags":["report"]},{"url":"https://bugzilla.suse.com/1231937","tags":["report"]},{"url":"https://bugzilla.suse.com/1231939","tags":["report"]},{"url":"https://bugzilla.suse.com/1231940","tags":["report"]},{"url":"https://bugzilla.suse.com/1231941","tags":["report"]},{"url":"https://bugzilla.suse.com/1231958","tags":["report"]},{"url":"https://bugzilla.suse.com/1231962","tags":["report"]},{"url":"https://bugzilla.suse.com/1231972","tags":["report"]},{"url":"https://bugzilla.suse.com/1231976","tags":["report"]},{"url":"https://bugzilla.suse.com/1231991","tags":["report"]},{"url":"https://bugzilla.suse.com/1231992","tags":["report"]},{"url":"https://bugzilla.suse.com/1231995","tags":["report"]},{"url":"https://bugzilla.suse.com/1231996","tags":["report"]},{"url":"https://bugzilla.suse.com/1231997","tags":["report"]},{"url":"https://bugzilla.suse.com/1232001","tags":["report"]},{"url":"https://bugzilla.suse.com/1232005","tags":["report"]},{"url":"https://bugzilla.suse.com/1232006","tags":["report"]},{"url":"https://bugzilla.suse.com/1232007","tags":["report"]},{"url":"https://bugzilla.suse.com/1232025","tags":["report"]},{"url":"https://bugzilla.suse.com/1232026","tags":["report"]},{"url":"https://bugzilla.suse.com/1232035","tags":["report"]},{"url":"https://bugzilla.suse.com/1232036","tags":["report"]},{"url":"https://bugzilla.suse.com/1232037","tags":["report"]},{"url":"https://bugzilla.suse.com/1232038","tags":["report"]},{"url":"https://bugzilla.suse.com/1232039","tags":["report"]},{"url":"https://bugzilla.suse.com/1232067","tags":["report"]},{"url":"https://bugzilla.suse.com/1232071","tags":["report"]},{"url":"https://bugzilla.suse.com/1232108","tags":["report"]},{"url":"https://bugzilla.suse.com/1232119","tags":["report"]},{"url":"https://bugzilla.suse.com/1232120","tags":["report"]},{"url":"https://bugzilla.suse.com/1232123","tags":["report"]},{"url":"https://bugzilla.suse.com/1232133","tags":["report"]},{"url":"https://bugzilla.suse.com/1232150","tags":["report"]},{"url":"https://bugzilla.suse.com/1232163","tags":["report"]},{"url":"https://bugzilla.suse.com/1232170","tags":["report"]},{"url":"https://bugzilla.suse.com/1232172","tags":["report"]},{"url":"https://bugzilla.suse.com/1232174","tags":["report"]},{"url":"https://bugzilla.suse.com/1232229","tags":["report"]},{"url":"https://bugzilla.suse.com/1232237","tags":["report"]},{"url":"https://bugzilla.suse.com/1232260","tags":["report"]},{"url":"https://bugzilla.suse.com/1232395","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49960","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244131-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1229345","tags":["report"]},{"url":"https://bugzilla.suse.com/1232165","tags":["report"]},{"url":"https://bugzilla.suse.com/1232224","tags":["report"]},{"url":"https://bugzilla.suse.com/1232281","tags":["report"]},{"url":"https://bugzilla.suse.com/1232436","tags":["report"]},{"url":"https://bugzilla.suse.com/1233117","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50208","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244140-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1226557","tags":["report"]},{"url":"https://bugzilla.suse.com/1232280","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47589","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-45026","tags":["report"]},{"url":"https://git.kernel.org/linus/7db4042336580dfd75cb5faa82c12cd51098c90b","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-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-45021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45025","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-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-36968","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-49967","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"]},{"url":"https://ubuntu.com/security/CVE-2024-50264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53057","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-45026","title":"s390/dasd: fix error recovery leading to data corruption on ESE devices","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","status":"published","published":"2024-09-11T15:13:58.396Z","modified":"2026-08-05T11:37:50.213Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna"}],"updated_at":"2026-11-02T14:34:08.16279Z"}],"euvd":[{"id":"EUVD-2024-41506","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","status":"published","published":"2024-09-11T15:13:58Z","modified":"2026-08-05T11:37:50Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T18:02:16.228226Z"}],"ghsa":[{"id":"GHSA-66cw-5j4x-3r2w","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","status":"published","published":"2024-09-11T18:31:06Z","modified":"2025-11-04T00:32:28Z","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"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T15:04:31.727217Z"}],"nvd":[{"id":"CVE-2024-45026","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","status":"published","published":"2024-09-11T16:15:07.507Z","modified":"2026-08-04T11:20:12.987Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"secondary"},{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T14:10:25.561537Z"}],"osv":[{"id":"AZL-49187","title":"CVE-2024-45026 affecting package kernel for versions less than 5.15.167.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","status":"published","published":"2024-09-11T16:15:07Z","modified":"2026-04-21T04:29:48.7585Z","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:28:06.032783Z"},{"id":"AZL-49266","title":"CVE-2024-45026 affecting package kernel for versions less than 6.6.51.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","status":"published","published":"2024-09-11T16:15:07Z","modified":"2026-04-21T04:53:08.494024Z","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:28:06.032783Z"},{"id":"BELL-CVE-2024-45026","status":"published","published":"2024-09-12T05:56:47.211036Z","modified":"2026-01-26T09:37:56.162566Z","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:28:20.452786Z"},{"id":"CVE-2024-45026","title":"s390/dasd: fix error recovery leading to data corruption on ESE devices","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/dasd: fix error recovery leading to data corruption on ESE devices\n\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\n\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\n\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\n\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\n\nAlso remove the check for file protected since this is not a valid\nESE handling case.","status":"published","published":"2024-09-11T15:13:58.396Z","modified":"2026-10-28T02:30:30.345235373Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:42.790566Z"},{"id":"DEBIAN-CVE-2024-45026","description":"In the Linux kernel, the following vulnerability has been resolved:  s390/dasd: fix error recovery leading to data corruption on ESE devices  Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing.  The dasd_ese_needs_format function checks for error codes that signal the non existence of a proper track format.  The check for incorrect length is to imprecise since other error cases leading to transport of insufficient data also have this flag set. This might lead to data corruption in certain error cases for example during a storage server warmstart.  Fix by removing the check for incorrect length and replacing by explicitly checking for invalid track format in transport mode.  Also remove the check for file protected since this is not a valid ESE handling case.","status":"published","published":"2024-09-11T16:15:07.507Z","modified":"2026-11-02T12:02:48.567086269Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:43.473331Z"},{"id":"OESA-2024-2255","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/i915/gt: Cleanup partial engine discovery failures\r\n\r\nIf we abort driver initialisation in the middle of gt/engine discovery,\nsome engines will be fully setup and some not. Those incompletely setup\nengines only have \u0026apos;engine-\u0026gt;release == NULL\u0026apos; and so will leak any of the\ncommon objects allocated.\r\n\r\nv2:\n - Drop the destroy_pinned_context() helper for now.  It\u0026apos;s not really\n   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to avoid dirent corruption\r\n\r\nAs Al reported in link[1]:\r\n\r\nf2fs_rename()\n...\n\tif (old_dir != new_dir \u0026amp;\u0026amp; !whiteout)\n\t\tf2fs_set_link(old_inode, old_dir_entry,\n\t\t\t\t\told_dir_page, new_dir);\n\telse\n\t\tf2fs_put_page(old_dir_page, 0);\r\n\r\nYou want correct inumber in the \u0026quot;..\u0026quot; link.  And cross-directory\nrename does move the source to new parent, even if you\u0026apos;d been asked\nto leave a whiteout in the old place.\r\n\r\n[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/\r\n\r\nWith below testcase, it may cause dirent corruption, due to it missed\nto call f2fs_set_link() to update \u0026quot;..\u0026quot; link to new directory.\n- mkdir -p dir/foo\n- renameat2 -w dir/foo bar\r\n\r\n[ASSERT] (__chk_dots_dentries:1421)  --\u0026gt; Bad inode number[0x4] for \u0026apos;..\u0026apos;, parent parent ino is [0x3]\n[FSCK] other corrupted bugs                           [Fail](CVE-2023-52444)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nefivarfs: force RO when remounting if SetVariable is not supported\r\n\r\nIf SetVariable at runtime is not supported by the firmware we never assign\na callback for that function. At the same time mount the efivarfs as\nRO so no one can call that.  However, we never check the permission flags\nwhen someone remounts the filesystem as RW. As a result this leads to a\ncrash looking like this:\r\n\r\n$ mount -o remount,rw /sys/firmware/efi/efivars\n$ efi-updatevar -f PK.auth PK\r\n\r\n[  303.279166] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n[  303.280482] Mem abort info:\n[  303.280854]   ESR = 0x0000000086000004\n[  303.281338]   EC = 0x21: IABT (current EL), IL = 32 bits\n[  303.282016]   SET = 0, FnV = 0\n[  303.282414]   EA = 0, S1PTW = 0\n[  303.282821]   FSC = 0x04: level 0 translation fault\n[  303.283771] user pgtable: 4k pages, 48-bit VAs, pgdp=000000004258c000\n[  303.284913] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000\n[  303.286076] Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP\n[  303.286936] Modules linked in: qrtr tpm_tis tpm_tis_core crct10dif_ce arm_smccc_trng rng_core drm fuse ip_tables x_tables ipv6\n[  303.288586] CPU: 1 PID: 755 Comm: efi-updatevar Not tainted 6.3.0-rc1-00108-gc7d0c4695c68 #1\n[  303.289748] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2023.04-00627-g88336918701d 04/01/2023\n[  303.291150] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[  303.292123] pc : 0x0\n[  303.292443] lr : efivar_set_variable_locked+0x74/0xec\n[  303.293156] sp : ffff800008673c10\n[  303.293619] x29: ffff800008673c10 x28: ffff0000037e8000 x27: 0000000000000000\n[  303.294592] x26: 0000000000000800 x25: ffff000002467400 x24: 0000000000000027\n[  303.295572] x23: ffffd49ea9832000 x22: ffff0000020c9800 x21: ffff000002467000\n[  303.296566] x20: 0000000000000001 x19: 00000000000007fc x18: 0000000000000000\n[  303.297531] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaac807ab54\n[  303.298495] x14: ed37489f673633c0 x13: 71c45c606de13f80 x12: 47464259e219acf4\n[  303.299453] x11: ffff000002af7b01 x10: 0000000000000003 x9 : 0000000000000002\n[  303.300431] x8 : 0000000000000010 x7 : ffffd49ea8973230 x6 : 0000000000a85201\n[  303.301412] x5 : 0000000000000000 x4 : ffff0000020c9800 x3 : 00000000000007fc\n[  303.302370] x2 : 0000000000000027 x1 : ffff000002467400 x0 : ffff000002467000\n[  303.303341] Call trace:\n[  303.303679]  0x0\n[  303.303938]  efivar_entry_set_get_size+0x98/0x16c\n[  303.304585]  efivarfs_file_write+0xd0/0x1a4\n[  303.305148]  vfs_write+0xc4/0x2e4\n[  303.305601]  ksys_write+0x70/0x104\n[  303.306073]  __arm64_sys_write+0x1c/0x28\n[  303.306622]  invoke_syscall+0x48/0x114\n[  303.307156]  el0_svc_common.constprop.0+0x44/0xec\n[  303.307803]  do_el0_svc+0x38/0x98\n[  303.308268]  el0_svc+0x2c/0x84\n[  303.308702]  el0t_64_sync_handler+0xf4/0x120\n[  303.309293]  el0t_64_sync+0x190/0x194\n[  303.309794] Code: ???????? ???????? ???????? ???????? (????????)\n[  303.310612] ---[ end trace 0000000000000000 ]---\r\n\r\nFix this by adding a .reconfigure() function to the fs operations which\nwe can use to check the requested flags and deny anything that\u0026apos;s not RO\nif the firmware doesn\u0026apos;t implement SetVariable at runtime.(CVE-2023-52463)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nx86/srso: Add SRSO mitigation for Hygon processors\r\n\r\nAdd mitigation for the speculative return stack overflow vulnerability\nwhich exists on Hygon processors too.(CVE-2023-52482)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: scomp - fix req-\u0026gt;dst buffer overflow\r\n\r\nThe req-\u0026gt;dst buffer size should be checked before copying from the\nscomp_scratch-\u0026gt;dst to avoid req-\u0026gt;dst buffer overflow problem.(CVE-2023-52612)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nllc: verify mac len before reading mac header\r\n\r\nLLC reads the mac header with eth_hdr without verifying that the skb\nhas an Ethernet header.\r\n\r\nSyzbot was able to enter llc_rcv on a tun device. Tun can insert\npackets without mac len and with user configurable skb-\u0026gt;protocol\n(passing a tun_pi header when not configuring IFF_NO_PI).\r\n\r\n    BUG: KMSAN: uninit-value in llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline]\n    BUG: KMSAN: uninit-value in llc_station_rcv+0x6fb/0x1290 net/llc/llc_station.c:111\n    llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline]\n    llc_station_rcv+0x6fb/0x1290 net/llc/llc_station.c:111\n    llc_rcv+0xc5d/0x14a0 net/llc/llc_input.c:218\n    __netif_receive_skb_one_core net/core/dev.c:5523 [inline]\n    __netif_receive_skb+0x1a6/0x5a0 net/core/dev.c:5637\n    netif_receive_skb_internal net/core/dev.c:5723 [inline]\n    netif_receive_skb+0x58/0x660 net/core/dev.c:5782\n    tun_rx_batched+0x3ee/0x980 drivers/net/tun.c:1555\n    tun_get_user+0x54c5/0x69c0 drivers/net/tun.c:2002\r\n\r\nAdd a mac_len test before all three eth_hdr(skb) calls under net/llc.\r\n\r\nThere are further uses in include/net/llc_pdu.h. All these are\nprotected by a test skb-\u0026gt;protocol == ETH_P_802_2. Which does not\nprotect against this tun scenario.\r\n\r\nBut the mac_len test added in this patch in llc_fixup_skb will\nindirectly protect those too. That is called from llc_rcv before any\nother LLC code.\r\n\r\nIt is tempting to just add a blanket mac_len check in llc_rcv, but\nnot sure whether that could break valid LLC paths that do not assume\nan Ethernet header. 802.2 LLC may be used on top of non-802.3\nprotocols in principle. The below referenced commit shows that used\nto, on top of Token Ring.\r\n\r\nAt least one of the three eth_hdr uses goes back to before the start\nof git history. But the one that syzbot exercises is introduced in\nthis commit. That commit is old enough (2008), that effectively all\nstable kernels should receive this.(CVE-2023-52843)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed\r\n\r\nIf hv_netvsc driver is unloaded and reloaded, the NET_DEVICE_REGISTER\nhandler cannot perform VF register successfully as the register call\nis received before netvsc_probe is finished. This is because we\nregister register_netdevice_notifier() very early( even before\nvmbus_driver_register()).\nTo fix this, we try to register each such matching VF( if it is visible\nas a netdevice) at the end of netvsc_probe.(CVE-2024-26820)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: honor table dormant flag from netdev release event path\r\n\r\nCheck for table dormant flag otherwise netdev release event path tries\nto unregister an already unregistered hook.\r\n\r\n[524854.857999] ------------[ cut here ]------------\n[524854.858010] WARNING: CPU: 0 PID: 3386599 at net/netfilter/core.c:501 __nf_unregister_net_hook+0x21a/0x260\n[...]\n[524854.858848] CPU: 0 PID: 3386599 Comm: kworker/u32:2 Not tainted 6.9.0-rc3+ #365\n[524854.858869] Workqueue: netns cleanup_net\n[524854.858886] RIP: 0010:__nf_unregister_net_hook+0x21a/0x260\n[524854.858903] Code: 24 e8 aa 73 83 ff 48 63 43 1c 83 f8 01 0f 85 3d ff ff ff e8 98 d1 f0 ff 48 8b 3c 24 e8 8f 73 83 ff 48 63 43 1c e9 26 ff ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 18 48 c7 c7 00 68 e9 82 5b 5d 41 5c 41 5d 41 5e 41\n[524854.858914] RSP: 0018:ffff8881e36d79e0 EFLAGS: 00010246\n[524854.858926] RAX: 0000000000000000 RBX: ffff8881339ae790 RCX: ffffffff81ba524a\n[524854.858936] RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff8881c8a16438\n[524854.858945] RBP: ffff8881c8a16438 R08: 0000000000000001 R09: ffffed103c6daf34\n[524854.858954] R10: ffff8881e36d79a7 R11: 0000000000000000 R12: 0000000000000005\n[524854.858962] R13: ffff8881c8a16000 R14: 0000000000000000 R15: ffff8881351b5a00\n[524854.858971] FS:  0000000000000000(0000) GS:ffff888390800000(0000) knlGS:0000000000000000\n[524854.858982] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[524854.858991] CR2: 00007fc9be0f16f4 CR3: 00000001437cc004 CR4: 00000000001706f0\n[524854.859000] Call Trace:\n[524854.859006]  \u0026lt;TASK\u0026gt;\n[524854.859013]  ? __warn+0x9f/0x1a0\n[524854.859027]  ? __nf_unregister_net_hook+0x21a/0x260\n[524854.859044]  ? report_bug+0x1b1/0x1e0\n[524854.859060]  ? handle_bug+0x3c/0x70\n[524854.859071]  ? exc_invalid_op+0x17/0x40\n[524854.859083]  ? asm_exc_invalid_op+0x1a/0x20\n[524854.859100]  ? __nf_unregister_net_hook+0x6a/0x260\n[524854.859116]  ? __nf_unregister_net_hook+0x21a/0x260\n[524854.859135]  nf_tables_netdev_event+0x337/0x390 [nf_tables]\n[524854.859304]  ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables]\n[524854.859461]  ? packet_notifier+0xb3/0x360\n[524854.859476]  ? _raw_spin_unlock_irqrestore+0x11/0x40\n[524854.859489]  ? dcbnl_netdevice_event+0x35/0x140\n[524854.859507]  ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables]\n[524854.859661]  notifier_call_chain+0x7d/0x140\n[524854.859677]  unregister_netdevice_many_notify+0x5e1/0xae0(CVE-2024-36005)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: fix uninitialized ratelimit_state-\u0026gt;lock access in __ext4_fill_super()\r\n\r\nIn the following concurrency we will access the uninitialized rs-\u0026gt;lock:\r\n\r\next4_fill_super\n  ext4_register_sysfs\n   // sysfs registered msg_ratelimit_interval_ms\n                             // Other processes modify rs-\u0026gt;interval to\n                             // non-zero via msg_ratelimit_interval_ms\n  ext4_orphan_cleanup\n    ext4_msg(sb, KERN_INFO, \u0026quot;Errors on filesystem, \u0026quot;\n      __ext4_msg\n        ___ratelimit(\u0026amp;(EXT4_SB(sb)-\u0026gt;s_msg_ratelimit_state)\n          if (!rs-\u0026gt;interval)  // do nothing if interval is 0\n            return 1;\n          raw_spin_trylock_irqsave(\u0026amp;rs-\u0026gt;lock, flags)\n            raw_spin_trylock(lock)\n              _raw_spin_trylock\n                __raw_spin_trylock\n                  spin_acquire(\u0026amp;lock-\u0026gt;dep_map, 0, 1, _RET_IP_)\n                    lock_acquire\n                      __lock_acquire\n                        register_lock_class\n                          assign_lock_key\n                            dump_stack();\n  ratelimit_state_init(\u0026amp;sbi-\u0026gt;s_msg_ratelimit_state, 5 * HZ, 10);\n    raw_spin_lock_init(\u0026amp;rs-\u0026gt;lock);\n    // init rs-\u0026gt;lock here\r\n\r\nand get the following dump_stack:\r\n\r\n=========================================================\nINFO: trying to register non-static key.\nThe code is fine but needs lockdep annotation, or maybe\nyou didn\u0026apos;t initialize this object before use?\nturning off the locking correctness validator.\nCPU: 12 PID: 753 Comm: mount Tainted: G E 6.7.0-rc6-next-20231222 #504\n[...]\nCall Trace:\n dump_stack_lvl+0xc5/0x170\n dump_stack+0x18/0x30\n register_lock_class+0x740/0x7c0\n __lock_acquire+0x69/0x13a0\n lock_acquire+0x120/0x450\n _raw_spin_trylock+0x98/0xd0\n ___ratelimit+0xf6/0x220\n __ext4_msg+0x7f/0x160 [ext4]\n ext4_orphan_cleanup+0x665/0x740 [ext4]\n __ext4_fill_super+0x21ea/0x2b10 [ext4]\n ext4_fill_super+0x14d/0x360 [ext4]\n[...]\n=========================================================\r\n\r\nNormally interval is 0 until s_msg_ratelimit_state is initialized, so\n___ratelimit() does nothing. But registering sysfs precedes initializing\nrs-\u0026gt;lock, so it is possible to change rs-\u0026gt;interval to a non-zero value\nvia the msg_ratelimit_interval_ms interface of sysfs while rs-\u0026gt;lock is\nuninitialized, and then a call to ext4_msg triggers the problem by\naccessing an uninitialized rs-\u0026gt;lock. Therefore register sysfs after all\ninitializations are complete to avoid such problems.(CVE-2024-40998)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()\r\n\r\nset_memory_rox() can fail, leaving memory unprotected.\r\n\r\nCheck return and bail out when bpf_jit_binary_lock_ro() returns\nan error.(CVE-2024-42067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: nexthop: Initialize all fields in dumped nexthops\r\n\r\nstruct nexthop_grp contains two reserved fields that are not initialized by\nnla_put_nh_group(), and carry garbage. This can be observed e.g. with\nstrace (edited for clarity):\r\n\r\n    # ip nexthop add id 1 dev lo\n    # ip nexthop add id 101 group 1\n    # strace -e recvmsg ip nexthop get id 101\n    ...\n    recvmsg(... [{nla_len=12, nla_type=NHA_GROUP},\n                 [{id=1, weight=0, resvd1=0x69, resvd2=0x67}]] ...) = 52\r\n\r\nThe fields are reserved and therefore not currently used. But as they are, they\nleak kernel memory, and the fact they are not just zero complicates repurposing\nof the fields for new ends. Initialize the full structure.(CVE-2024-42283)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nirqchip/imx-irqsteer: Handle runtime power management correctly\r\n\r\nThe power domain is automatically activated from clk_prepare(). However, on\ncertain platforms like i.MX8QM and i.MX8QXP, the power-on handling invokes\nsleeping functions, which triggers the \u0026apos;scheduling while atomic\u0026apos; bug in the\ncontext switch path during device probing:\r\n\r\n BUG: scheduling while atomic: kworker/u13:1/48/0x00000002\n Call trace:\n  __schedule_bug+0x54/0x6c\n  __schedule+0x7f0/0xa94\n  schedule+0x5c/0xc4\n  schedule_preempt_disabled+0x24/0x40\n  __mutex_lock.constprop.0+0x2c0/0x540\n  __mutex_lock_slowpath+0x14/0x20\n  mutex_lock+0x48/0x54\n  clk_prepare_lock+0x44/0xa0\n  clk_prepare+0x20/0x44\n  imx_irqsteer_resume+0x28/0xe0\n  pm_generic_runtime_resume+0x2c/0x44\n  __genpd_runtime_resume+0x30/0x80\n  genpd_runtime_resume+0xc8/0x2c0\n  __rpm_callback+0x48/0x1d8\n  rpm_callback+0x6c/0x78\n  rpm_resume+0x490/0x6b4\n  __pm_runtime_resume+0x50/0x94\n  irq_chip_pm_get+0x2c/0xa0\n  __irq_do_set_handler+0x178/0x24c\n  irq_set_chained_handler_and_data+0x60/0xa4\n  mxc_gpio_probe+0x160/0x4b0\r\n\r\nCure this by implementing the irq_bus_lock/sync_unlock() interrupt chip\ncallbacks and handle power management in them as they are invoked from\nnon-atomic context.\r\n\r\n[ tglx: Rewrote change log, added Fixes tag ](CVE-2024-42290)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudf: Avoid using corrupted block bitmap buffer\r\n\r\nWhen the filesystem block bitmap is corrupted, we detect the corruption\nwhile loading the bitmap and fail the allocation with error. However the\nnext allocation from the same bitmap will notice the bitmap buffer is\nalready loaded and tries to allocate from the bitmap with mixed results\n(depending on the exact nature of the bitmap corruption). Fix the\nproblem by using BH_verified bit to indicate whether the bitmap is valid\nor not.(CVE-2024-42306)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\r\n\r\nIn psb_intel_lvds_get_modes(), the return value of drm_mode_duplicate() is\nassigned to mode, which will lead to a possible NULL pointer dereference\non failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42309)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: venus: fix use after free in vdec_close\r\n\r\nThere appears to be a possible use after free with vdec_close().\nThe firmware will add buffer release work to the work queue through\nHFI callbacks as a normal part of decoding. Randomly closing the\ndecoder device from userspace during normal decoding can incur\na read after free for inst.\r\n\r\nFix it by cancelling the work in vdec_close.(CVE-2024-42313)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipvs: properly dereference pe in ip_vs_add_service\r\n\r\nUse pe directly to resolve sparse warning:\r\n\r\n  net/netfilter/ipvs/ip_vs_ctl.c:1471:27: warning: dereference of noderef expression(CVE-2024-42322)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Fix NULL pointer dereference in case of DT error in ks_pcie_setup_rc_app_regs()\r\n\r\nIf IORESOURCE_MEM is not provided in Device Tree due to\nany error, resource_list_first_type() will return NULL and\npci_parse_request_of_pci_ranges() will just emit a warning.\r\n\r\nThis will cause a NULL pointer dereference. Fix this bug by adding NULL\nreturn check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-43823)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: trigger: Unregister sysfs attributes before calling deactivate()\r\n\r\nTriggers which have trigger specific sysfs attributes typically store\nrelated data in trigger-data allocated by the activate() callback and\nfreed by the deactivate() callback.\r\n\r\nCalling device_remove_groups() after calling deactivate() leaves a window\nwhere the sysfs attributes show/store functions could be called after\ndeactivation and then operate on the just freed trigger-data.\r\n\r\nMove the device_remove_groups() call to before deactivate() to close\nthis race window.\r\n\r\nThis also makes the deactivation path properly do things in reverse order\nof the activation path which calls the activate() callback before calling\ndevice_add_groups().(CVE-2024-43830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG\r\n\r\nWhen BPF_TRAMP_F_CALL_ORIG is set, the trampoline calls\n__bpf_tramp_enter() and __bpf_tramp_exit() functions, passing them\nthe struct bpf_tramp_image *im pointer as an argument in R0.\r\n\r\nThe trampoline generation code uses emit_addr_mov_i64() to emit\ninstructions for moving the bpf_tramp_image address into R0, but\nemit_addr_mov_i64() assumes the address to be in the vmalloc() space\nand uses only 48 bits. Because bpf_tramp_image is allocated using\nkzalloc(), its address can use more than 48-bits, in this case the\ntrampoline will pass an invalid address to __bpf_tramp_enter/exit()\ncausing a kernel crash.\r\n\r\nFix this by using emit_a64_mov_i64() in place of emit_addr_mov_i64()\nas it can work with addresses that are greater than 48-bits.(CVE-2024-43840)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd: fix deadlock between mddev_suspend and flush bio\r\n\r\nDeadlock occurs when mddev is being suspended while some flush bio is in\nprogress. It is a complex issue.\r\n\r\nT1. the first flush is at the ending stage, it clears \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;\n    and tries to submit data, but is blocked because mddev is suspended\n    by T4.\nT2. the second flush sets \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;, and attempts to queue\n    md_submit_flush_data(), which is already running (T1) and won\u0026apos;t\n    execute again if on the same CPU as T1.\nT3. the third flush inc active_io and tries to flush, but is blocked because\n    \u0026apos;mddev-\u0026gt;flush_bio\u0026apos; is not NULL (set by T2).\nT4. mddev_suspend() is called and waits for active_io dec to 0 which is inc\n    by T3.\r\n\r\n  T1\t\tT2\t\tT3\t\tT4\n  (flush 1)\t(flush 2)\t(third 3)\t(suspend)\n  md_submit_flush_data\n   mddev-\u0026gt;flush_bio = NULL;\n   .\n   .\t \tmd_flush_request\n   .\t  \t mddev-\u0026gt;flush_bio = bio\n   .\t  \t queue submit_flushes\n   .\t\t .\n   .\t\t .\t\tmd_handle_request\n   .\t\t .\t\t active_io + 1\n   .\t\t .\t\t md_flush_request\n   .\t\t .\t\t  wait !mddev-\u0026gt;flush_bio\n   .\t\t .\n   .\t\t .\t\t\t\tmddev_suspend\n   .\t\t .\t\t\t\t wait !active_io\n   .\t\t .\n   .\t\t submit_flushes\n   .\t\t queue_work md_submit_flush_data\n   .\t\t //md_submit_flush_data is already running (T1)\n   .\n   md_handle_request\n    wait resume\r\n\r\nThe root issue is non-atomic inc/dec of active_io during flush process.\nactive_io is dec before md_submit_flush_data is queued, and inc soon\nafter md_submit_flush_data() run.\n  md_flush_request\n    active_io + 1\n    submit_flushes\n      active_io - 1\n      md_submit_flush_data\n        md_handle_request\n        active_io + 1\n          make_request\n        active_io - 1\r\n\r\nIf active_io is dec after md_handle_request() instead of within\nsubmit_flushes(), make_request() can be called directly intead of\nmd_handle_request() in md_submit_flush_data(), and active_io will\nonly inc and dec once in the whole flush process. Deadlock will be\nfixed.\r\n\r\nAdditionally, the only difference between fixing the issue and before is\nthat there is no return error handling of make_request(). But after\nprevious patch cleaned md_write_start(), make_requst() only return error\nin raid5_make_request() by dm-raid, see commit 41425f96d7aa (\u0026quot;dm-raid456,\nmd/raid456: fix a deadlock for dm-raid456 while io concurrent with\nreshape)\u0026quot;. Since dm always splits data and flush operation into two\nseparate io, io size of flush submitted by dm always is 0, make_request()\nwill not be called in md_submit_flush_data(). To prevent future\nmodifications from introducing issues, add WARN_ON to ensure\nmake_request() no error is returned in this context.(CVE-2024-43855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/hns: Fix soft lockup under heavy CEQE load\r\n\r\nCEQEs are handled in interrupt handler currently. This may cause the\nCPU core staying in interrupt context too long and lead to soft lockup\nunder heavy load.\r\n\r\nHandle CEQEs in BH workqueue and set an upper limit for the number of\nCEQE handled by a single call of work handler.(CVE-2024-43872)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg: protect concurrent access to mem_cgroup_idr\r\n\r\nCommit 73f576c04b94 (\u0026quot;mm: memcontrol: fix cgroup creation failure after\nmany small jobs\u0026quot;) decoupled the memcg IDs from the CSS ID space to fix the\ncgroup creation failures.  It introduced IDR to maintain the memcg ID\nspace.  The IDR depends on external synchronization mechanisms for\nmodifications.  For the mem_cgroup_idr, the idr_alloc() and idr_replace()\nhappen within css callback and thus are protected through cgroup_mutex\nfrom concurrent modifications.  However idr_remove() for mem_cgroup_idr\nwas not protected against concurrency and can be run concurrently for\ndifferent memcgs when they hit their refcnt to zero.  Fix that.\r\n\r\nWe have been seeing list_lru based kernel crashes at a low frequency in\nour fleet for a long time.  These crashes were in different part of\nlist_lru code including list_lru_add(), list_lru_del() and reparenting\ncode.  Upon further inspection, it looked like for a given object (dentry\nand inode), the super_block\u0026apos;s list_lru didn\u0026apos;t have list_lru_one for the\nmemcg of that object.  The initial suspicions were either the object is\nnot allocated through kmem_cache_alloc_lru() or somehow\nmemcg_list_lru_alloc() failed to allocate list_lru_one() for a memcg but\nreturned success.  No evidence were found for these cases.\r\n\r\nLooking more deeply, we started seeing situations where valid memcg\u0026apos;s id\nis not present in mem_cgroup_idr and in some cases multiple valid memcgs\nhave same id and mem_cgroup_idr is pointing to one of them.  So, the most\nreasonable explanation is that these situations can happen due to race\nbetween multiple idr_remove() calls or race between\nidr_alloc()/idr_replace() and idr_remove().  These races are causing\nmultiple memcgs to acquire the same ID and then offlining of one of them\nwould cleanup list_lrus on the system for all of them.  Later access from\nother memcgs to the list_lru cause crashes due to missing list_lru_one.(CVE-2024-43892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: core: check uartclk for zero to avoid divide by zero\r\n\r\nCalling ioctl TIOCSSERIAL with an invalid baud_base can\nresult in uartclk being zero, which will result in a\ndivide by zero error in uart_get_divisor(). The check for\nuartclk being zero in uart_set_info() needs to be done\nbefore other settings are made as subsequent calls to\nioctl TIOCSSERIAL for the same port would be impacted if\nthe uartclk check was done where uartclk gets set.\r\n\r\nOops: divide error: 0000  PREEMPT SMP KASAN PTI\nRIP: 0010:uart_get_divisor (drivers/tty/serial/serial_core.c:580)\nCall Trace:\n \u0026lt;TASK\u0026gt;\nserial8250_get_divisor (drivers/tty/serial/8250/8250_port.c:2576\n    drivers/tty/serial/8250/8250_port.c:2589)\nserial8250_do_set_termios (drivers/tty/serial/8250/8250_port.c:502\n    drivers/tty/serial/8250/8250_port.c:2741)\nserial8250_set_termios (drivers/tty/serial/8250/8250_port.c:2862)\nuart_change_line_settings (./include/linux/spinlock.h:376\n    ./include/linux/serial_core.h:608 drivers/tty/serial/serial_core.c:222)\nuart_port_startup (drivers/tty/serial/serial_core.c:342)\nuart_startup (drivers/tty/serial/serial_core.c:368)\nuart_set_info (drivers/tty/serial/serial_core.c:1034)\nuart_set_info_user (drivers/tty/serial/serial_core.c:1059)\ntty_set_serial (drivers/tty/tty_io.c:2637)\ntty_ioctl (drivers/tty/tty_io.c:2647 drivers/tty/tty_io.c:2791)\n__x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:907\n    fs/ioctl.c:893 fs/ioctl.c:893)\ndo_syscall_64 (arch/x86/entry/common.c:52\n    (discriminator 1) arch/x86/entry/common.c:83 (discriminator 1))\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nRule: add(CVE-2024-43893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfou: remove warn in gue_gro_receive on unsupported protocol\r\n\r\nDrop the WARN_ON_ONCE inn gue_gro_receive if the encapsulated type is\nnot known or does not have a GRO handler.\r\n\r\nSuch a packet is easily constructed. Syzbot generates them and sets\noff this warning.\r\n\r\nRemove the warning as it is expected and not actionable.\r\n\r\nThe warning was previously reduced from WARN_ON to WARN_ON_ONCE in\ncommit 270136613bf7 (\u0026quot;fou: Do WARN_ON_ONCE in gue_gro_receive for bad\nproto callbacks\u0026quot;).(CVE-2024-44940)\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\natm: idt77252: prevent use after free in dequeue_rx()\r\n\r\nWe can\u0026apos;t dereference \u0026quot;skb\u0026quot; after calling vcc-\u0026gt;push() because the skb\nis released.(CVE-2024-44998)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxhci: Fix Panther point NULL pointer deref at full-speed re-enumeration\r\n\r\nre-enumerating full-speed devices after a failed address device command\ncan trigger a NULL pointer dereference.\r\n\r\nFull-speed devices may need to reconfigure the endpoint 0 Max Packet Size\nvalue during enumeration. Usb core calls usb_ep0_reinit() in this case,\nwhich ends up calling xhci_configure_endpoint().\r\n\r\nOn Panther point xHC the xhci_configure_endpoint() function will\nadditionally check and reserve bandwidth in software. Other hosts do\nthis in hardware\r\n\r\nIf xHC address device command fails then a new xhci_virt_device structure\nis allocated as part of re-enabling the slot, but the bandwidth table\npointers are not set up properly here.\nThis triggers the NULL pointer dereference the next time usb_ep0_reinit()\nis called and xhci_configure_endpoint() tries to check and reserve\nbandwidth\r\n\r\n[46710.713538] usb 3-1: new full-speed USB device number 5 using xhci_hcd\n[46710.713699] usb 3-1: Device not responding to setup address.\n[46710.917684] usb 3-1: Device not responding to setup address.\n[46711.125536] usb 3-1: device not accepting address 5, error -71\n[46711.125594] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[46711.125600] #PF: supervisor read access in kernel mode\n[46711.125603] #PF: error_code(0x0000) - not-present page\n[46711.125606] PGD 0 P4D 0\n[46711.125610] Oops: Oops: 0000 [#1] PREEMPT SMP PTI\n[46711.125615] CPU: 1 PID: 25760 Comm: kworker/1:2 Not tainted 6.10.3_2 #1\n[46711.125620] Hardware name: Gigabyte Technology Co., Ltd.\n[46711.125623] Workqueue: usb_hub_wq hub_event [usbcore]\n[46711.125668] RIP: 0010:xhci_reserve_bandwidth (drivers/usb/host/xhci.c\r\n\r\nFix this by making sure bandwidth table pointers are set up correctly\nafter a failed address device command, and additionally by avoiding\nchecking for bandwidth in cases like this where no actual endpoints are\nadded or removed, i.e. only context for default control endpoint 0 is\nevaluated.(CVE-2024-45006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/dasd: fix error recovery leading to data corruption on ESE devices\r\n\r\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\r\n\r\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\r\n\r\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\r\n\r\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\r\n\r\nAlso remove the check for file protected since this is not a valid\nESE handling case.(CVE-2024-45026)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: pn533: Add poll mod list filling check\r\n\r\nIn case of im_protocols value is 1 and tm_protocols value is 0 this\ncombination successfully passes the check\n\u0026apos;if (!im_protocols \u0026amp;\u0026amp; !tm_protocols)\u0026apos; in the nfc_start_poll().\nBut then after pn533_poll_create_mod_list() call in pn533_start_poll()\npoll mod list will remain empty and dev-\u0026gt;poll_mod_count will remain 0\nwhich lead to division by zero.\r\n\r\nNormally no im protocol has value 1 in the mask, so this combination is\nnot expected by driver. But these protocol values actually come from\nuserspace via Netlink interface (NFC_CMD_START_POLL operation). So a\nbroken or malicious program may pass a message containing a \u0026quot;bad\u0026quot;\ncombination of protocol parameter values so that dev-\u0026gt;poll_mod_count\nis not incremented inside pn533_poll_create_mod_list(), thus leading\nto division by zero.\nCall trace looks like:\nnfc_genl_start_poll()\n  nfc_start_poll()\n    -\u0026gt;start_poll()\n    pn533_start_poll()\r\n\r\nAdd poll mod list filling check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-46676)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: typec: ucsi: Fix null pointer dereference in trace\r\n\r\nucsi_register_altmode checks IS_ERR for the alt pointer and treats\nNULL as valid. When CONFIG_TYPEC_DP_ALTMODE is not enabled,\nucsi_register_displayport returns NULL which causes a NULL pointer\ndereference in trace. Rather than return NULL, call\ntypec_port_register_altmode to register DisplayPort alternate mode\nas a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled.(CVE-2024-46719)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Remove tst_run from lwt_seg6local_prog_ops.\r\n\r\nThe syzbot reported that the lwt_seg6 related BPF ops can be invoked\nvia bpf_test_run() without without entering input_action_end_bpf()\nfirst.\r\n\r\nMartin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL\nprobably didn\u0026apos;t work since it was introduced in commit 04d4b274e2a\n(\u0026quot;ipv6: sr: Add seg6local action End.BPF\u0026quot;). The reason is that the\nper-CPU variable seg6_bpf_srh_states::srh is never assigned in the self\ntest case but each BPF function expects it.\r\n\r\nRemove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.(CVE-2024-46754)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: Add netif_device_attach/detach into PF reset flow\r\n\r\nEthtool callbacks can be executed while reset is in progress and try to\naccess deleted resources, e.g. getting coalesce settings can result in a\nNULL pointer dereference seen below.\r\n\r\nReproduction steps:\nOnce the driver is fully initialized, trigger reset:\n\t# echo 1 \u0026gt; /sys/class/net/\u0026lt;interface\u0026gt;/device/reset\nwhen reset is in progress try to get coalesce settings using ethtool:\n\t# ethtool -c \u0026lt;interface\u0026gt;\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000020\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] PREEMPT SMP PTI\nCPU: 11 PID: 19713 Comm: ethtool Tainted: G S                 6.10.0-rc7+ #7\nRIP: 0010:ice_get_q_coalesce+0x2e/0xa0 [ice]\nRSP: 0018:ffffbab1e9bcf6a8 EFLAGS: 00010206\nRAX: 000000000000000c RBX: ffff94512305b028 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: ffff9451c3f2e588 RDI: ffff9451c3f2e588\nRBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\nR10: ffff9451c3f2e580 R11: 000000000000001f R12: ffff945121fa9000\nR13: ffffbab1e9bcf760 R14: 0000000000000013 R15: ffffffff9e65dd40\nFS:  00007faee5fbe740(0000) GS:ffff94546fd80000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000020 CR3: 0000000106c2e005 CR4: 00000000001706f0\nCall Trace:\n\u0026lt;TASK\u0026gt;\nice_get_coalesce+0x17/0x30 [ice]\ncoalesce_prepare_data+0x61/0x80\nethnl_default_doit+0xde/0x340\ngenl_family_rcv_msg_doit+0xf2/0x150\ngenl_rcv_msg+0x1b3/0x2c0\nnetlink_rcv_skb+0x5b/0x110\ngenl_rcv+0x28/0x40\nnetlink_unicast+0x19c/0x290\nnetlink_sendmsg+0x222/0x490\n__sys_sendto+0x1df/0x1f0\n__x64_sys_sendto+0x24/0x30\ndo_syscall_64+0x82/0x160\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7faee60d8e27\r\n\r\nCalling netif_device_detach() before reset makes the net core not call\nthe driver when ethtool command is issued, the attempt to execute an\nethtool command during reset will result in the following message:\r\n\r\n    netlink error: No such device\r\n\r\ninstead of NULL pointer dereference. Once reset is done and\nice_rebuild() is executing, the netif_device_attach() is called to allow\nfor ethtool operations to occur again in a safe manner.(CVE-2024-46770)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nksmbd: unset the binding mark of a reused connection\r\n\r\nSteve French reported null pointer dereference error from sha256 lib.\ncifs.ko can send session setup requests on reused connection.\nIf reused connection is used for binding session, conn-\u0026gt;binding can\nstill remain true and generate_preauth_hash() will not set\nsess-\u0026gt;Preauth_HashValue and it will be NULL.\nIt is used as a material to create an encryption key in\nksmbd_gen_smb311_encryptionkey. -\u0026gt;Preauth_HashValue cause null pointer\ndereference error from crypto_shash_update().\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000000\n#PF: supervisor read access in kernel mode\n#PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 8 PID: 429254 Comm: kworker/8:39\nHardware name: LENOVO 20MAS08500/20MAS08500, BIOS N2CET69W (1.52 )\nWorkqueue: ksmbd-io handle_ksmbd_work [ksmbd]\nRIP: 0010:lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n\u0026lt;TASK\u0026gt;\n? show_regs+0x6d/0x80\n? __die+0x24/0x80\n? page_fault_oops+0x99/0x1b0\n? do_user_addr_fault+0x2ee/0x6b0\n? exc_page_fault+0x83/0x1b0\n? asm_exc_page_fault+0x27/0x30\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n_sha256_update+0x77/0xa0 [sha256_ssse3]\nsha256_avx2_update+0x15/0x30 [sha256_ssse3]\ncrypto_shash_update+0x1e/0x40\nhmac_update+0x12/0x20\ncrypto_shash_update+0x1e/0x40\ngenerate_key+0x234/0x380 [ksmbd]\ngenerate_smb3encryptionkey+0x40/0x1c0 [ksmbd]\nksmbd_gen_smb311_encryptionkey+0x72/0xa0 [ksmbd]\nntlm_authenticate.isra.0+0x423/0x5d0 [ksmbd]\nsmb2_sess_setup+0x952/0xaa0 [ksmbd]\n__process_request+0xa3/0x1d0 [ksmbd]\n__handle_ksmbd_work+0x1c4/0x2f0 [ksmbd]\nhandle_ksmbd_work+0x2d/0xa0 [ksmbd]\nprocess_one_work+0x16c/0x350\nworker_thread+0x306/0x440\n? __pfx_worker_thread+0x10/0x10\nkthread+0xef/0x120\n? __pfx_kthread+0x10/0x10\nret_from_fork+0x44/0x70\n? __pfx_kthread+0x10/0x10\nret_from_fork_asm+0x1b/0x30\n\u0026lt;/TASK\u0026gt;(CVE-2024-46795)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: the warning dereferencing obj for nbio_v7_4\r\n\r\nif ras_manager obj null, don\u0026apos;t print NBIO err data(CVE-2024-46819)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nELF: fix kernel.randomize_va_space double read\r\n\r\nELF loader uses \u0026quot;randomize_va_space\u0026quot; twice. It is sysctl and can change\nat any moment, so 2 loads could see 2 different values in theory with\nunpredictable consequences.\r\n\r\nIssue exactly one load for consistent value across one exec.(CVE-2024-46826)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched: sch_cake: fix bulk flow accounting logic for host fairness\r\n\r\nIn sch_cake, we keep track of the count of active bulk flows per host,\nwhen running in dst/src host fairness mode, which is used as the\nround-robin weight when iterating through flows. The count of active\nbulk flows is updated whenever a flow changes state.\r\n\r\nThis has a peculiar interaction with the hash collision handling: when a\nhash collision occurs (after the set-associative hashing), the state of\nthe hash bucket is simply updated to match the new packet that collided,\nand if host fairness is enabled, that also means assigning new per-host\nstate to the flow. For this reason, the bulk flow counters of the\nhost(s) assigned to the flow are decremented, before new state is\nassigned (and the counters, which may not belong to the same host\nanymore, are incremented again).\r\n\r\nBack when this code was introduced, the host fairness mode was always\nenabled, so the decrement was unconditional. When the configuration\nflags were introduced the *increment* was made conditional, but\nthe *decrement* was not. Which of course can lead to a spurious\ndecrement (and associated wrap-around to U16_MAX).\r\n\r\nAFAICT, when host fairness is disabled, the decrement and wrap-around\nhappens as soon as a hash collision occurs (which is not that common in\nitself, due to the set-associative hashing). However, in most cases this\nis harmless, as the value is only used when host fairness mode is\nenabled. So in order to trigger an array overflow, sch_cake has to first\nbe configured with host fairness disabled, and while running in this\nmode, a hash collision has to occur to cause the overflow. Then, the\nqdisc has to be reconfigured to enable host fairness, which leads to the\narray out-of-bounds because the wrapped-around value is retained and\nused as an array index. It seems that syzbot managed to trigger this,\nwhich is quite impressive in its own right.\r\n\r\nThis patch fixes the issue by introducing the same conditional check on\ndecrement as is used on increment.\r\n\r\nThe original bug predates the upstreaming of cake, but the commit listed\nin the Fixes tag touched that code, meaning that this patch won\u0026apos;t apply\nbefore that.(CVE-2024-46828)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: clean up our handling of refs == 0 in snapshot delete\r\n\r\nIn reada we BUG_ON(refs == 0), which could be unkind since we aren\u0026apos;t\nholding a lock on the extent leaf and thus could get a transient\nincorrect answer.  In walk_down_proc we also BUG_ON(refs == 0), which\ncould happen if we have extent tree corruption.  Change that to return\n-EUCLEAN.  In do_walk_down() we catch this case and handle it correctly,\nhowever we return -EIO, which -EUCLEAN is a more appropriate error code.\nFinally in walk_up_proc we have the same BUG_ON(refs == 0), so convert\nthat to proper error handling.  Also adjust the error message so we can\nactually do something with the information.(CVE-2024-46840)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nperf/x86/intel: Limit the period on Haswell\r\n\r\nRunning the ltp test cve-2015-3290 concurrently reports the following\nwarnings.\r\n\r\nperfevents: irq loop stuck!\n  WARNING: CPU: 31 PID: 32438 at arch/x86/events/intel/core.c:3174\n  intel_pmu_handle_irq+0x285/0x370\n  Call Trace:\n   \u0026lt;NMI\u0026gt;\n   ? __warn+0xa4/0x220\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? report_bug+0x3e/0xa0\n   ? handle_bug+0x3c/0x70\n   ? exc_invalid_op+0x18/0x50\n   ? asm_exc_invalid_op+0x1a/0x20\n   ? irq_work_claim+0x1e/0x40\n   ? intel_pmu_handle_irq+0x285/0x370\n   perf_event_nmi_handler+0x3d/0x60\n   nmi_handle+0x104/0x330\r\n\r\nThanks to Thomas Gleixner\u0026apos;s analysis, the issue is caused by the low\ninitial period (1) of the frequency estimation algorithm, which triggers\nthe defects of the HW, specifically erratum HSW11 and HSW143. (For the\ndetails, please refer https://lore.kernel.org/lkml/87plq9l5d2.ffs@tglx/)\r\n\r\nThe HSW11 requires a period larger than 100 for the INST_RETIRED.ALL\nevent, but the initial period in the freq mode is 1. The erratum is the\nsame as the BDM11, which has been supported in the kernel. A minimum\nperiod of 128 is enforced as well on HSW.\r\n\r\nHSW143 is regarding that the fixed counter 1 may overcount 32 with the\nHyper-Threading is enabled. However, based on the test, the hardware\nhas more issues than it tells. Besides the fixed counter 1, the message\n\u0026apos;interrupt took too long\u0026apos; can be observed on any counter which was armed\nwith a period \u0026lt; 32 and two events expired in the same NMI. A minimum\nperiod of 32 is enforced for the rest of the events.\nThe recommended workaround code of the HSW143 is not implemented.\nBecause it only addresses the issue for the fixed counter. It brings\nextra overhead through extra MSR writing. No related overcounting issue\nhas been reported so far.(CVE-2024-46848)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dpaa: Pad packets to ETH_ZLEN\r\n\r\nWhen sending packets under 60 bytes, up to three bytes of the buffer\nfollowing the data may be leaked. Avoid this by extending all packets to\nETH_ZLEN, ensuring nothing is leaked in the padding. This bug can be\nreproduced by running\r\n\r\n\t$ ping -s 11 destination(CVE-2024-46854)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nft_socket: fix sk refcount leaks\r\n\r\nWe must put \u0026apos;sk\u0026apos; reference before returning.(CVE-2024-46855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: Fix uaf in __timer_delete_sync\r\n\r\nThere are two paths to access mptcp_pm_del_add_timer, result in a race\ncondition:\r\n\r\n     CPU1\t\t\t\tCPU2\n     ====                               ====\n     net_rx_action\n     napi_poll                          netlink_sendmsg\n     __napi_poll                        netlink_unicast\n     process_backlog                    netlink_unicast_kernel\n     __netif_receive_skb                genl_rcv\n     __netif_receive_skb_one_core       netlink_rcv_skb\n     NF_HOOK                            genl_rcv_msg\n     ip_local_deliver_finish            genl_family_rcv_msg\n     ip_protocol_deliver_rcu            genl_family_rcv_msg_doit\n     tcp_v4_rcv                         mptcp_pm_nl_flush_addrs_doit\n     tcp_v4_do_rcv                      mptcp_nl_remove_addrs_list\n     tcp_rcv_established                mptcp_pm_remove_addrs_and_subflows\n     tcp_data_queue                     remove_anno_list_by_saddr\n     mptcp_incoming_options             mptcp_pm_del_add_timer\n     mptcp_pm_del_add_timer             kfree(entry)\r\n\r\nIn remove_anno_list_by_saddr(running on CPU2), after leaving the critical\nzone protected by \u0026quot;pm.lock\u0026quot;, the entry will be released, which leads to the\noccurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1).\r\n\r\nKeeping a reference to add_timer inside the lock, and calling\nsk_stop_timer_sync() with this reference, instead of \u0026quot;entry-\u0026gt;add_timer\u0026quot;.\r\n\r\nMove list_del(\u0026amp;entry-\u0026gt;list) to mptcp_pm_del_add_timer and inside the pm lock,\ndo not directly access any members of the entry outside the pm lock, which\ncan avoid similar \u0026quot;entry-\u0026gt;x\u0026quot; uaf.(CVE-2024-46858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: stm32/cryp - call finalize with bh disabled\r\n\r\nThe finalize operation in interrupt mode produce a produces a spinlock\nrecursion warning. The reason is the fact that BH must be disabled\nduring this process.(CVE-2024-47658)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware\r\n\r\nIf the value of max_speed_hz is 0, it may cause a division by zero\nerror in hisi_calc_effective_speed().\nThe value of max_speed_hz is provided by firmware.\nFirmware is generally considered as a trusted domain. However, as\ndivision by zero errors can cause system failure, for defense measure,\nthe value of max_speed is validated here. So 0 is regarded as invalid\nand an error code is returned.(CVE-2024-47664)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_xattr_find_entry()\r\n\r\nAdd a paranoia check to make sure it doesn\u0026apos;t stray beyond valid memory\nregion containing ocfs2 xattr entries when scanning for a match.  It will\nprevent out-of-bound access in case of crafted images.(CVE-2024-47670)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbtmc: prevent kernel-usb-infoleak\r\n\r\nThe syzbot reported a kernel-usb-infoleak in usbtmc_write,\nwe need to clear the structure before filling fields.(CVE-2024-47671)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: don\u0026apos;t wait for tx queues if firmware is dead\r\n\r\nThere is a WARNING in iwl_trans_wait_tx_queues_empty() (that was\nrecently converted from just a message), that can be hit if we\nwait for TX queues to become empty after firmware died. Clearly,\nwe can\u0026apos;t expect anything from the firmware after it\u0026apos;s declared dead.\r\n\r\nDon\u0026apos;t call iwl_trans_wait_tx_queues_empty() in this case. While it could\nbe a good idea to stop the flow earlier, the flush functions do some\nmaintenance work that is not related to the firmware, so keep that part\nof the code running even when the firmware is not running.\r\n\r\n[edit commit message](CVE-2024-47672)","status":"published","published":"2024-10-18T11:07:43Z","modified":"2026-08-18T01:18:37.568583109Z","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-2257","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\ni40e: Fix kernel crash during module removal\r\n\r\nThe driver incorrectly frees client instance and subsequent\ni40e module removal leads to kernel crash.\r\n\r\nReproducer:\n1. Do ethtool offline test followed immediately by another one\nhost# ethtool -t eth0 offline; ethtool -t eth0 offline\n2. Remove recursively irdma module that also removes i40e module\nhost# modprobe -r irdma\r\n\r\nResult:\n[ 8675.035651] i40e 0000:3d:00.0 eno1: offline testing starting\n[ 8675.193774] i40e 0000:3d:00.0 eno1: testing finished\n[ 8675.201316] i40e 0000:3d:00.0 eno1: offline testing starting\n[ 8675.358921] i40e 0000:3d:00.0 eno1: testing finished\n[ 8675.496921] i40e 0000:3d:00.0: IRDMA hardware initialization FAILED init_state=2 status=-110\n[ 8686.188955] i40e 0000:3d:00.1: i40e_ptp_stop: removed PHC on eno2\n[ 8686.943890] i40e 0000:3d:00.1: Deleted LAN device PF1 bus=0x3d dev=0x00 func=0x01\n[ 8686.952669] i40e 0000:3d:00.0: i40e_ptp_stop: removed PHC on eno1\n[ 8687.761787] BUG: kernel NULL pointer dereference, address: 0000000000000030\n[ 8687.768755] #PF: supervisor read access in kernel mode\n[ 8687.773895] #PF: error_code(0x0000) - not-present page\n[ 8687.779034] PGD 0 P4D 0\n[ 8687.781575] Oops: 0000 [#1] PREEMPT SMP NOPTI\n[ 8687.785935] CPU: 51 PID: 172891 Comm: rmmod Kdump: loaded Tainted: G        W I        5.19.0+ #2\n[ 8687.794800] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0X.02.0001.051420190324 05/14/2019\n[ 8687.805222] RIP: 0010:i40e_lan_del_device+0x13/0xb0 [i40e]\n[ 8687.810719] Code: d4 84 c0 0f 84 b8 25 01 00 e9 9c 25 01 00 41 bc f4 ff ff ff eb 91 90 0f 1f 44 00 00 41 54 55 53 48 8b 87 58 08 00 00 48 89 fb \u0026lt;48\u0026gt; 8b 68 30 48 89 ef e8 21 8a 0f d5 48 89 ef e8 a9 78 0f d5 48 8b\n[ 8687.829462] RSP: 0018:ffffa604072efce0 EFLAGS: 00010202\n[ 8687.834689] RAX: 0000000000000000 RBX: ffff8f43833b2000 RCX: 0000000000000000\n[ 8687.841821] RDX: 0000000000000000 RSI: ffff8f4b0545b298 RDI: ffff8f43833b2000\n[ 8687.848955] RBP: ffff8f43833b2000 R08: 0000000000000001 R09: 0000000000000000\n[ 8687.856086] R10: 0000000000000000 R11: 000ffffffffff000 R12: ffff8f43833b2ef0\n[ 8687.863218] R13: ffff8f43833b2ef0 R14: ffff915103966000 R15: ffff8f43833b2008\n[ 8687.870342] FS:  00007f79501c3740(0000) GS:ffff8f4adffc0000(0000) knlGS:0000000000000000\n[ 8687.878427] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 8687.884174] CR2: 0000000000000030 CR3: 000000014276e004 CR4: 00000000007706e0\n[ 8687.891306] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 8687.898441] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[ 8687.905572] PKRU: 55555554\n[ 8687.908286] Call Trace:\n[ 8687.910737]  \u0026lt;TASK\u0026gt;\n[ 8687.912843]  i40e_remove+0x2c0/0x330 [i40e]\n[ 8687.917040]  pci_device_remove+0x33/0xa0\n[ 8687.920962]  device_release_driver_internal+0x1aa/0x230\n[ 8687.926188]  driver_detach+0x44/0x90\n[ 8687.929770]  bus_remove_driver+0x55/0xe0\n[ 8687.933693]  pci_unregister_driver+0x2a/0xb0\n[ 8687.937967]  i40e_exit_module+0xc/0xf48 [i40e]\r\n\r\nTwo offline tests cause IRDMA driver failure (ETIMEDOUT) and this\nfailure is indicated back to i40e_client_subtask() that calls\ni40e_client_del_instance() to free client instance referenced\nby pf-\u0026gt;cinst and sets this pointer to NULL. During the module\nremoval i40e_remove() calls i40e_lan_del_device() that dereferences\npf-\u0026gt;cinst that is NULL -\u0026gt; crash.\nDo not remove client instance when client open callbacks fails and\njust clear __I40E_CLIENT_INSTANCE_OPENED bit. The driver also needs\nto take care about this situation (when netdev is up and client\nis NOT opened) in i40e_notify_client_of_netdev_close() and\ncalls client close callback only when __I40E_CLIENT_INSTANCE_OPENED\nis set.(CVE-2022-48688)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntracing/osnoise: Do not unregister events twice\r\n\r\nNicolas reported that using:\r\n\r\n # trace-cmd record -e all -M 10 -p osnoise --poll\r\n\r\nResulted in the following kernel warning:\r\n\r\n ------------[ cut here ]------------\n WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370\n [...]\n CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19\n RIP: 0010:tracepoint_probe_unregister+0x280/0x370\n [...]\n CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  osnoise_workload_stop+0x36/0x90\n  tracing_set_tracer+0x108/0x260\n  tracing_set_trace_write+0x94/0xd0\n  ? __check_object_size.part.0+0x10a/0x150\n  ? selinux_file_permission+0x104/0x150\n  vfs_write+0xb5/0x290\n  ksys_write+0x5f/0xe0\n  do_syscall_64+0x3b/0x90\n  entry_SYSCALL_64_after_hwframe+0x44/0xae\n RIP: 0033:0x7ff919a18127\n [...]\n ---[ end trace 0000000000000000 ]---\r\n\r\nThe warning complains about an attempt to unregister an\nunregistered tracepoint.\r\n\r\nThis happens on trace-cmd because it first stops tracing, and\nthen switches the tracer to nop. Which is equivalent to:\r\n\r\n  # cd /sys/kernel/tracing/\n  # echo osnoise \u0026gt; current_tracer\n  # echo 0 \u0026gt; tracing_on\n  # echo nop \u0026gt; current_tracer\r\n\r\nThe osnoise tracer stops the workload when no trace instance\nis actually collecting data. This can be caused both by\ndisabling tracing or disabling the tracer itself.\r\n\r\nTo avoid unregistering events twice, use the existing\ntrace_osnoise_callback_enabled variable to check if the events\n(and the workload) are actually active before trying to\ndeactivate them.(CVE-2022-48848)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: gadgetfs: Fix race between mounting and unmounting\r\n\r\nThe syzbot fuzzer and Gerald Lee have identified a use-after-free bug\nin the gadgetfs driver, involving processes concurrently mounting and\nunmounting the gadgetfs filesystem.  In particular, gadgetfs_fill_super()\ncan race with gadgetfs_kill_sb(), causing the latter to deallocate\nthe_device while the former is using it.  The output from KASAN says,\nin part:\r\n\r\nBUG: KASAN: use-after-free in instrument_atomic_read_write include/linux/instrumented.h:102 [inline]\nBUG: KASAN: use-after-free in atomic_fetch_sub_release include/linux/atomic/atomic-instrumented.h:176 [inline]\nBUG: KASAN: use-after-free in __refcount_sub_and_test include/linux/refcount.h:272 [inline]\nBUG: KASAN: use-after-free in __refcount_dec_and_test include/linux/refcount.h:315 [inline]\nBUG: KASAN: use-after-free in refcount_dec_and_test include/linux/refcount.h:333 [inline]\nBUG: KASAN: use-after-free in put_dev drivers/usb/gadget/legacy/inode.c:159 [inline]\nBUG: KASAN: use-after-free in gadgetfs_kill_sb+0x33/0x100 drivers/usb/gadget/legacy/inode.c:2086\nWrite of size 4 at addr ffff8880276d7840 by task syz-executor126/18689\r\n\r\nCPU: 0 PID: 18689 Comm: syz-executor126 Not tainted 6.1.0-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022\nCall Trace:\n \u0026lt;TASK\u0026gt;\n...\n atomic_fetch_sub_release include/linux/atomic/atomic-instrumented.h:176 [inline]\n __refcount_sub_and_test include/linux/refcount.h:272 [inline]\n __refcount_dec_and_test include/linux/refcount.h:315 [inline]\n refcount_dec_and_test include/linux/refcount.h:333 [inline]\n put_dev drivers/usb/gadget/legacy/inode.c:159 [inline]\n gadgetfs_kill_sb+0x33/0x100 drivers/usb/gadget/legacy/inode.c:2086\n deactivate_locked_super+0xa7/0xf0 fs/super.c:332\n vfs_get_super fs/super.c:1190 [inline]\n get_tree_single+0xd0/0x160 fs/super.c:1207\n vfs_get_tree+0x88/0x270 fs/super.c:1531\n vfs_fsconfig_locked fs/fsopen.c:232 [inline]\r\n\r\nThe simplest solution is to ensure that gadgetfs_fill_super() and\ngadgetfs_kill_sb() are serialized by making them both acquire a new\nmutex.(CVE-2022-48869)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nefi: fix NULL-deref in init error path\r\n\r\nIn cases where runtime services are not supported or have been disabled,\nthe runtime services workqueue will never have been allocated.\r\n\r\nDo not try to destroy the workqueue unconditionally in the unlikely\nevent that EFI initialisation fails to avoid dereferencing a NULL\npointer.(CVE-2022-48879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/i915/gt: Cleanup partial engine discovery failures\r\n\r\nIf we abort driver initialisation in the middle of gt/engine discovery,\nsome engines will be fully setup and some not. Those incompletely setup\nengines only have \u0026apos;engine-\u0026gt;release == NULL\u0026apos; and so will leak any of the\ncommon objects allocated.\r\n\r\nv2:\n - Drop the destroy_pinned_context() helper for now.  It\u0026apos;s not really\n   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: vivid: fix compose size exceed boundary\r\n\r\nsyzkaller found a bug:\r\n\r\n BUG: unable to handle page fault for address: ffffc9000a3b1000\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 100000067 P4D 100000067 PUD 10015f067 PMD 1121ca067 PTE 0\n Oops: 0002 [#1] PREEMPT SMP\n CPU: 0 PID: 23489 Comm: vivid-000-vid-c Not tainted 6.1.0-rc1+ #512\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014\n RIP: 0010:memcpy_erms+0x6/0x10\n[...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? tpg_fill_plane_buffer+0x856/0x15b0\n  vivid_fillbuff+0x8ac/0x1110\n  vivid_thread_vid_cap_tick+0x361/0xc90\n  vivid_thread_vid_cap+0x21a/0x3a0\n  kthread+0x143/0x180\n  ret_from_fork+0x1f/0x30\n  \u0026lt;/TASK\u0026gt;\r\n\r\nThis is because we forget to check boundary after adjust compose-\u0026gt;height\nint V4L2_SEL_TGT_CROP case. Add v4l2_rect_map_inside() to fix this problem\nfor this case.(CVE-2022-48945)\r\n\r\nA flaw possibility of memory leak in the Linux kernel cpu_entry_area mapping of X86 CPU data to memory was found in the way user can guess location of exception stack(s) or other important data. A local user could use this flaw to get access to some important data with expected location in memory.(CVE-2023-0597)\r\n\r\nFrom the upstream fix below: The watchdog_timer can schedule tx_timeout_task and watchdog_work can also arm watchdog_timer [..] Although del_timer_sync() and cancel_work_sync() are called in cyttsp4_remove(), the timer and workqueue could still be rearmed. As a result, the possible use after free bugs could happen.\r\n\r\nUpstream commit:\nhttps://github.com/torvalds/linux/commit/dbe836576f12743a7d2d170ad4ad4fd324c4d47a(CVE-2023-4134)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nefivarfs: force RO when remounting if SetVariable is not supported\r\n\r\nIf SetVariable at runtime is not supported by the firmware we never assign\na callback for that function. At the same time mount the efivarfs as\nRO so no one can call that.  However, we never check the permission flags\nwhen someone remounts the filesystem as RW. As a result this leads to a\ncrash looking like this:\r\n\r\n$ mount -o remount,rw /sys/firmware/efi/efivars\n$ efi-updatevar -f PK.auth PK\r\n\r\n[  303.279166] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n[  303.280482] Mem abort info:\n[  303.280854]   ESR = 0x0000000086000004\n[  303.281338]   EC = 0x21: IABT (current EL), IL = 32 bits\n[  303.282016]   SET = 0, FnV = 0\n[  303.282414]   EA = 0, S1PTW = 0\n[  303.282821]   FSC = 0x04: level 0 translation fault\n[  303.283771] user pgtable: 4k pages, 48-bit VAs, pgdp=000000004258c000\n[  303.284913] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000\n[  303.286076] Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP\n[  303.286936] Modules linked in: qrtr tpm_tis tpm_tis_core crct10dif_ce arm_smccc_trng rng_core drm fuse ip_tables x_tables ipv6\n[  303.288586] CPU: 1 PID: 755 Comm: efi-updatevar Not tainted 6.3.0-rc1-00108-gc7d0c4695c68 #1\n[  303.289748] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2023.04-00627-g88336918701d 04/01/2023\n[  303.291150] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[  303.292123] pc : 0x0\n[  303.292443] lr : efivar_set_variable_locked+0x74/0xec\n[  303.293156] sp : ffff800008673c10\n[  303.293619] x29: ffff800008673c10 x28: ffff0000037e8000 x27: 0000000000000000\n[  303.294592] x26: 0000000000000800 x25: ffff000002467400 x24: 0000000000000027\n[  303.295572] x23: ffffd49ea9832000 x22: ffff0000020c9800 x21: ffff000002467000\n[  303.296566] x20: 0000000000000001 x19: 00000000000007fc x18: 0000000000000000\n[  303.297531] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaac807ab54\n[  303.298495] x14: ed37489f673633c0 x13: 71c45c606de13f80 x12: 47464259e219acf4\n[  303.299453] x11: ffff000002af7b01 x10: 0000000000000003 x9 : 0000000000000002\n[  303.300431] x8 : 0000000000000010 x7 : ffffd49ea8973230 x6 : 0000000000a85201\n[  303.301412] x5 : 0000000000000000 x4 : ffff0000020c9800 x3 : 00000000000007fc\n[  303.302370] x2 : 0000000000000027 x1 : ffff000002467400 x0 : ffff000002467000\n[  303.303341] Call trace:\n[  303.303679]  0x0\n[  303.303938]  efivar_entry_set_get_size+0x98/0x16c\n[  303.304585]  efivarfs_file_write+0xd0/0x1a4\n[  303.305148]  vfs_write+0xc4/0x2e4\n[  303.305601]  ksys_write+0x70/0x104\n[  303.306073]  __arm64_sys_write+0x1c/0x28\n[  303.306622]  invoke_syscall+0x48/0x114\n[  303.307156]  el0_svc_common.constprop.0+0x44/0xec\n[  303.307803]  do_el0_svc+0x38/0x98\n[  303.308268]  el0_svc+0x2c/0x84\n[  303.308702]  el0t_64_sync_handler+0xf4/0x120\n[  303.309293]  el0t_64_sync+0x190/0x194\n[  303.309794] Code: ???????? ???????? ???????? ???????? (????????)\n[  303.310612] ---[ end trace 0000000000000000 ]---\r\n\r\nFix this by adding a .reconfigure() function to the fs operations which\nwe can use to check the requested flags and deny anything that\u0026apos;s not RO\nif the firmware doesn\u0026apos;t implement SetVariable at runtime.(CVE-2023-52463)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched/psi: Fix use-after-free in ep_remove_wait_queue()\r\n\r\nIf a non-root cgroup gets removed when there is a thread that registered\ntrigger and is polling on a pressure file within the cgroup, the polling\nwaitqueue gets freed in the following path:\r\n\r\n do_rmdir\n   cgroup_rmdir\n     kernfs_drain_open_files\n       cgroup_file_release\n         cgroup_pressure_release\n           psi_trigger_destroy\r\n\r\nHowever, the polling thread still has a reference to the pressure file and\nwill access the freed waitqueue when the file is closed or upon exit:\r\n\r\n fput\n   ep_eventpoll_release\n     ep_free\n       ep_remove_wait_queue\n         remove_wait_queue\r\n\r\nThis results in use-after-free as pasted below.\r\n\r\nThe fundamental problem here is that cgroup_file_release() (and\nconsequently waitqueue\u0026apos;s lifetime) is not tied to the file\u0026apos;s real lifetime.\nUsing wake_up_pollfree() here might be less than ideal, but it is in line\nwith the comment at commit 42288cb44c4b (\u0026quot;wait: add wake_up_pollfree()\u0026quot;)\nsince the waitqueue\u0026apos;s lifetime is not tied to file\u0026apos;s one and can be\nconsidered as another special case. While this would be fixable by somehow\nmaking cgroup_file_release() be tied to the fput(), it would require\nsizable refactoring at cgroups or higher layer which might be more\njustifiable if we identify more cases like this.\r\n\r\n  BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0\n  Write of size 4 at addr ffff88810e625328 by task a.out/4404\r\n\r\n\tCPU: 19 PID: 4404 Comm: a.out Not tainted 6.2.0-rc6 #38\n\tHardware name: Amazon EC2 c5a.8xlarge/, BIOS 1.0 10/16/2017\n\tCall Trace:\n\t\u0026lt;TASK\u0026gt;\n\tdump_stack_lvl+0x73/0xa0\n\tprint_report+0x16c/0x4e0\n\tkasan_report+0xc3/0xf0\n\tkasan_check_range+0x2d2/0x310\n\t_raw_spin_lock_irqsave+0x60/0xc0\n\tremove_wait_queue+0x1a/0xa0\n\tep_free+0x12c/0x170\n\tep_eventpoll_release+0x26/0x30\n\t__fput+0x202/0x400\n\ttask_work_run+0x11d/0x170\n\tdo_exit+0x495/0x1130\n\tdo_group_exit+0x100/0x100\n\tget_signal+0xd67/0xde0\n\tarch_do_signal_or_restart+0x2a/0x2b0\n\texit_to_user_mode_prepare+0x94/0x100\n\tsyscall_exit_to_user_mode+0x20/0x40\n\tdo_syscall_64+0x52/0x90\n\tentry_SYSCALL_64_after_hwframe+0x63/0xcd\n\t\u0026lt;/TASK\u0026gt;\r\n\r\n Allocated by task 4404:\r\n\r\n\tkasan_set_track+0x3d/0x60\n\t__kasan_kmalloc+0x85/0x90\n\tpsi_trigger_create+0x113/0x3e0\n\tpressure_write+0x146/0x2e0\n\tcgroup_file_write+0x11c/0x250\n\tkernfs_fop_write_iter+0x186/0x220\n\tvfs_write+0x3d8/0x5c0\n\tksys_write+0x90/0x110\n\tdo_syscall_64+0x43/0x90\n\tentry_SYSCALL_64_after_hwframe+0x63/0xcd\r\n\r\n Freed by task 4407:\r\n\r\n\tkasan_set_track+0x3d/0x60\n\tkasan_save_free_info+0x27/0x40\n\t____kasan_slab_free+0x11d/0x170\n\tslab_free_freelist_hook+0x87/0x150\n\t__kmem_cache_free+0xcb/0x180\n\tpsi_trigger_destroy+0x2e8/0x310\n\tcgroup_file_release+0x4f/0xb0\n\tkernfs_drain_open_files+0x165/0x1f0\n\tkernfs_drain+0x162/0x1a0\n\t__kernfs_remove+0x1fb/0x310\n\tkernfs_remove_by_name_ns+0x95/0xe0\n\tcgroup_addrm_files+0x67f/0x700\n\tcgroup_destroy_locked+0x283/0x3c0\n\tcgroup_rmdir+0x29/0x100\n\tkernfs_iop_rmdir+0xd1/0x140\n\tvfs_rmdir+0xfe/0x240\n\tdo_rmdir+0x13d/0x280\n\t__x64_sys_rmdir+0x2c/0x30\n\tdo_syscall_64+0x43/0x90\n\tentry_SYSCALL_64_after_hwframe+0x63/0xcd(CVE-2023-52707)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncifs: Fix use-after-free in rdata-\u0026gt;read_into_pages()\r\n\r\nWhen the network status is unstable, use-after-free may occur when\nread data from the server.\r\n\r\n  BUG: KASAN: use-after-free in readpages_fill_pages+0x14c/0x7e0\r\n\r\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x38/0x4c\n   print_report+0x16f/0x4a6\n   kasan_report+0xb7/0x130\n   readpages_fill_pages+0x14c/0x7e0\n   cifs_readv_receive+0x46d/0xa40\n   cifs_demultiplex_thread+0x121c/0x1490\n   kthread+0x16b/0x1a0\n   ret_from_fork+0x2c/0x50\n   \u0026lt;/TASK\u0026gt;\r\n\r\n  Allocated by task 2535:\n   kasan_save_stack+0x22/0x50\n   kasan_set_track+0x25/0x30\n   __kasan_kmalloc+0x82/0x90\n   cifs_readdata_direct_alloc+0x2c/0x110\n   cifs_readdata_alloc+0x2d/0x60\n   cifs_readahead+0x393/0xfe0\n   read_pages+0x12f/0x470\n   page_cache_ra_unbounded+0x1b1/0x240\n   filemap_get_pages+0x1c8/0x9a0\n   filemap_read+0x1c0/0x540\n   cifs_strict_readv+0x21b/0x240\n   vfs_read+0x395/0x4b0\n   ksys_read+0xb8/0x150\n   do_syscall_64+0x3f/0x90\n   entry_SYSCALL_64_after_hwframe+0x72/0xdc\r\n\r\n  Freed by task 79:\n   kasan_save_stack+0x22/0x50\n   kasan_set_track+0x25/0x30\n   kasan_save_free_info+0x2e/0x50\n   __kasan_slab_free+0x10e/0x1a0\n   __kmem_cache_free+0x7a/0x1a0\n   cifs_readdata_release+0x49/0x60\n   process_one_work+0x46c/0x760\n   worker_thread+0x2a4/0x6f0\n   kthread+0x16b/0x1a0\n   ret_from_fork+0x2c/0x50\r\n\r\n  Last potentially related work creation:\n   kasan_save_stack+0x22/0x50\n   __kasan_record_aux_stack+0x95/0xb0\n   insert_work+0x2b/0x130\n   __queue_work+0x1fe/0x660\n   queue_work_on+0x4b/0x60\n   smb2_readv_callback+0x396/0x800\n   cifs_abort_connection+0x474/0x6a0\n   cifs_reconnect+0x5cb/0xa50\n   cifs_readv_from_socket.cold+0x22/0x6c\n   cifs_read_page_from_socket+0xc1/0x100\n   readpages_fill_pages.cold+0x2f/0x46\n   cifs_readv_receive+0x46d/0xa40\n   cifs_demultiplex_thread+0x121c/0x1490\n   kthread+0x16b/0x1a0\n   ret_from_fork+0x2c/0x50\r\n\r\nThe following function calls will cause UAF of the rdata pointer.\r\n\r\nreadpages_fill_pages\n cifs_read_page_from_socket\n  cifs_readv_from_socket\n   cifs_reconnect\n    __cifs_reconnect\n     cifs_abort_connection\n      mid-\u0026gt;callback() --\u0026gt; smb2_readv_callback\n       queue_work(\u0026amp;rdata-\u0026gt;work)  # if the worker completes first,\n                                 # the rdata is freed\n          cifs_readv_complete\n            kref_put\n              cifs_readdata_release\n                kfree(rdata)\n return rdata-\u0026gt;...               # UAF in readpages_fill_pages()\r\n\r\nSimilarly, this problem also occurs in the uncache_fill_pages().\r\n\r\nFix this by adjusts the order of condition judgment in the return\nstatement.(CVE-2023-52741)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc\r\n\r\nAny unprivileged user can attach N_GSM0710 ldisc, but it requires\nCAP_NET_ADMIN to create a GSM network anyway.\r\n\r\nRequire initial namespace CAP_NET_ADMIN to do that.(CVE-2023-52880)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkeys: Fix overwrite of key expiration on instantiation\r\n\r\nThe expiry time of a key is unconditionally overwritten during\ninstantiation, defaulting to turn it permanent. This causes a problem\nfor DNS resolution as the expiration set by user-space is overwritten to\nTIME64_MAX, disabling further DNS updates. Fix this by restoring the\ncondition that key_set_expiry is only called when the pre-parser sets a\nspecific expiry.(CVE-2024-36031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: fix uninitialized ratelimit_state-\u0026gt;lock access in __ext4_fill_super()\r\n\r\nIn the following concurrency we will access the uninitialized rs-\u0026gt;lock:\r\n\r\next4_fill_super\n  ext4_register_sysfs\n   // sysfs registered msg_ratelimit_interval_ms\n                             // Other processes modify rs-\u0026gt;interval to\n                             // non-zero via msg_ratelimit_interval_ms\n  ext4_orphan_cleanup\n    ext4_msg(sb, KERN_INFO, \u0026quot;Errors on filesystem, \u0026quot;\n      __ext4_msg\n        ___ratelimit(\u0026amp;(EXT4_SB(sb)-\u0026gt;s_msg_ratelimit_state)\n          if (!rs-\u0026gt;interval)  // do nothing if interval is 0\n            return 1;\n          raw_spin_trylock_irqsave(\u0026amp;rs-\u0026gt;lock, flags)\n            raw_spin_trylock(lock)\n              _raw_spin_trylock\n                __raw_spin_trylock\n                  spin_acquire(\u0026amp;lock-\u0026gt;dep_map, 0, 1, _RET_IP_)\n                    lock_acquire\n                      __lock_acquire\n                        register_lock_class\n                          assign_lock_key\n                            dump_stack();\n  ratelimit_state_init(\u0026amp;sbi-\u0026gt;s_msg_ratelimit_state, 5 * HZ, 10);\n    raw_spin_lock_init(\u0026amp;rs-\u0026gt;lock);\n    // init rs-\u0026gt;lock here\r\n\r\nand get the following dump_stack:\r\n\r\n=========================================================\nINFO: trying to register non-static key.\nThe code is fine but needs lockdep annotation, or maybe\nyou didn\u0026apos;t initialize this object before use?\nturning off the locking correctness validator.\nCPU: 12 PID: 753 Comm: mount Tainted: G E 6.7.0-rc6-next-20231222 #504\n[...]\nCall Trace:\n dump_stack_lvl+0xc5/0x170\n dump_stack+0x18/0x30\n register_lock_class+0x740/0x7c0\n __lock_acquire+0x69/0x13a0\n lock_acquire+0x120/0x450\n _raw_spin_trylock+0x98/0xd0\n ___ratelimit+0xf6/0x220\n __ext4_msg+0x7f/0x160 [ext4]\n ext4_orphan_cleanup+0x665/0x740 [ext4]\n __ext4_fill_super+0x21ea/0x2b10 [ext4]\n ext4_fill_super+0x14d/0x360 [ext4]\n[...]\n=========================================================\r\n\r\nNormally interval is 0 until s_msg_ratelimit_state is initialized, so\n___ratelimit() does nothing. But registering sysfs precedes initializing\nrs-\u0026gt;lock, so it is possible to change rs-\u0026gt;interval to a non-zero value\nvia the msg_ratelimit_interval_ms interface of sysfs while rs-\u0026gt;lock is\nuninitialized, and then a call to ext4_msg triggers the problem by\naccessing an uninitialized rs-\u0026gt;lock. Therefore register sysfs after all\ninitializations are complete to avoid such problems.(CVE-2024-40998)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()\r\n\r\nset_memory_rox() can fail, leaving memory unprotected.\r\n\r\nCheck return and bail out when bpf_jit_binary_lock_ro() returns\nan error.(CVE-2024-42067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: nexthop: Initialize all fields in dumped nexthops\r\n\r\nstruct nexthop_grp contains two reserved fields that are not initialized by\nnla_put_nh_group(), and carry garbage. This can be observed e.g. with\nstrace (edited for clarity):\r\n\r\n    # ip nexthop add id 1 dev lo\n    # ip nexthop add id 101 group 1\n    # strace -e recvmsg ip nexthop get id 101\n    ...\n    recvmsg(... [{nla_len=12, nla_type=NHA_GROUP},\n                 [{id=1, weight=0, resvd1=0x69, resvd2=0x67}]] ...) = 52\r\n\r\nThe fields are reserved and therefore not currently used. But as they are, they\nleak kernel memory, and the fact they are not just zero complicates repurposing\nof the fields for new ends. Initialize the full structure.(CVE-2024-42283)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nirqchip/imx-irqsteer: Handle runtime power management correctly\r\n\r\nThe power domain is automatically activated from clk_prepare(). However, on\ncertain platforms like i.MX8QM and i.MX8QXP, the power-on handling invokes\nsleeping functions, which triggers the \u0026apos;scheduling while atomic\u0026apos; bug in the\ncontext switch path during device probing:\r\n\r\n BUG: scheduling while atomic: kworker/u13:1/48/0x00000002\n Call trace:\n  __schedule_bug+0x54/0x6c\n  __schedule+0x7f0/0xa94\n  schedule+0x5c/0xc4\n  schedule_preempt_disabled+0x24/0x40\n  __mutex_lock.constprop.0+0x2c0/0x540\n  __mutex_lock_slowpath+0x14/0x20\n  mutex_lock+0x48/0x54\n  clk_prepare_lock+0x44/0xa0\n  clk_prepare+0x20/0x44\n  imx_irqsteer_resume+0x28/0xe0\n  pm_generic_runtime_resume+0x2c/0x44\n  __genpd_runtime_resume+0x30/0x80\n  genpd_runtime_resume+0xc8/0x2c0\n  __rpm_callback+0x48/0x1d8\n  rpm_callback+0x6c/0x78\n  rpm_resume+0x490/0x6b4\n  __pm_runtime_resume+0x50/0x94\n  irq_chip_pm_get+0x2c/0xa0\n  __irq_do_set_handler+0x178/0x24c\n  irq_set_chained_handler_and_data+0x60/0xa4\n  mxc_gpio_probe+0x160/0x4b0\r\n\r\nCure this by implementing the irq_bus_lock/sync_unlock() interrupt chip\ncallbacks and handle power management in them as they are invoked from\nnon-atomic context.\r\n\r\n[ tglx: Rewrote change log, added Fixes tag ](CVE-2024-42290)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\r\n\r\nIn psb_intel_lvds_get_modes(), the return value of drm_mode_duplicate() is\nassigned to mode, which will lead to a possible NULL pointer dereference\non failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42309)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: venus: fix use after free in vdec_close\r\n\r\nThere appears to be a possible use after free with vdec_close().\nThe firmware will add buffer release work to the work queue through\nHFI callbacks as a normal part of decoding. Randomly closing the\ndecoder device from userspace during normal decoding can incur\na read after free for inst.\r\n\r\nFix it by cancelling the work in vdec_close.(CVE-2024-42313)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipvs: properly dereference pe in ip_vs_add_service\r\n\r\nUse pe directly to resolve sparse warning:\r\n\r\n  net/netfilter/ipvs/ip_vs_ctl.c:1471:27: warning: dereference of noderef expression(CVE-2024-42322)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Fix NULL pointer dereference in case of DT error in ks_pcie_setup_rc_app_regs()\r\n\r\nIf IORESOURCE_MEM is not provided in Device Tree due to\nany error, resource_list_first_type() will return NULL and\npci_parse_request_of_pci_ranges() will just emit a warning.\r\n\r\nThis will cause a NULL pointer dereference. Fix this bug by adding NULL\nreturn check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-43823)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: trigger: Unregister sysfs attributes before calling deactivate()\r\n\r\nTriggers which have trigger specific sysfs attributes typically store\nrelated data in trigger-data allocated by the activate() callback and\nfreed by the deactivate() callback.\r\n\r\nCalling device_remove_groups() after calling deactivate() leaves a window\nwhere the sysfs attributes show/store functions could be called after\ndeactivation and then operate on the just freed trigger-data.\r\n\r\nMove the device_remove_groups() call to before deactivate() to close\nthis race window.\r\n\r\nThis also makes the deactivation path properly do things in reverse order\nof the activation path which calls the activate() callback before calling\ndevice_add_groups().(CVE-2024-43830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd: fix deadlock between mddev_suspend and flush bio\r\n\r\nDeadlock occurs when mddev is being suspended while some flush bio is in\nprogress. It is a complex issue.\r\n\r\nT1. the first flush is at the ending stage, it clears \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;\n    and tries to submit data, but is blocked because mddev is suspended\n    by T4.\nT2. the second flush sets \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;, and attempts to queue\n    md_submit_flush_data(), which is already running (T1) and won\u0026apos;t\n    execute again if on the same CPU as T1.\nT3. the third flush inc active_io and tries to flush, but is blocked because\n    \u0026apos;mddev-\u0026gt;flush_bio\u0026apos; is not NULL (set by T2).\nT4. mddev_suspend() is called and waits for active_io dec to 0 which is inc\n    by T3.\r\n\r\n  T1\t\tT2\t\tT3\t\tT4\n  (flush 1)\t(flush 2)\t(third 3)\t(suspend)\n  md_submit_flush_data\n   mddev-\u0026gt;flush_bio = NULL;\n   .\n   .\t \tmd_flush_request\n   .\t  \t mddev-\u0026gt;flush_bio = bio\n   .\t  \t queue submit_flushes\n   .\t\t .\n   .\t\t .\t\tmd_handle_request\n   .\t\t .\t\t active_io + 1\n   .\t\t .\t\t md_flush_request\n   .\t\t .\t\t  wait !mddev-\u0026gt;flush_bio\n   .\t\t .\n   .\t\t .\t\t\t\tmddev_suspend\n   .\t\t .\t\t\t\t wait !active_io\n   .\t\t .\n   .\t\t submit_flushes\n   .\t\t queue_work md_submit_flush_data\n   .\t\t //md_submit_flush_data is already running (T1)\n   .\n   md_handle_request\n    wait resume\r\n\r\nThe root issue is non-atomic inc/dec of active_io during flush process.\nactive_io is dec before md_submit_flush_data is queued, and inc soon\nafter md_submit_flush_data() run.\n  md_flush_request\n    active_io + 1\n    submit_flushes\n      active_io - 1\n      md_submit_flush_data\n        md_handle_request\n        active_io + 1\n          make_request\n        active_io - 1\r\n\r\nIf active_io is dec after md_handle_request() instead of within\nsubmit_flushes(), make_request() can be called directly intead of\nmd_handle_request() in md_submit_flush_data(), and active_io will\nonly inc and dec once in the whole flush process. Deadlock will be\nfixed.\r\n\r\nAdditionally, the only difference between fixing the issue and before is\nthat there is no return error handling of make_request(). But after\nprevious patch cleaned md_write_start(), make_requst() only return error\nin raid5_make_request() by dm-raid, see commit 41425f96d7aa (\u0026quot;dm-raid456,\nmd/raid456: fix a deadlock for dm-raid456 while io concurrent with\nreshape)\u0026quot;. Since dm always splits data and flush operation into two\nseparate io, io size of flush submitted by dm always is 0, make_request()\nwill not be called in md_submit_flush_data(). To prevent future\nmodifications from introducing issues, add WARN_ON to ensure\nmake_request() no error is returned in this context.(CVE-2024-43855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg: protect concurrent access to mem_cgroup_idr\r\n\r\nCommit 73f576c04b94 (\u0026quot;mm: memcontrol: fix cgroup creation failure after\nmany small jobs\u0026quot;) decoupled the memcg IDs from the CSS ID space to fix the\ncgroup creation failures.  It introduced IDR to maintain the memcg ID\nspace.  The IDR depends on external synchronization mechanisms for\nmodifications.  For the mem_cgroup_idr, the idr_alloc() and idr_replace()\nhappen within css callback and thus are protected through cgroup_mutex\nfrom concurrent modifications.  However idr_remove() for mem_cgroup_idr\nwas not protected against concurrency and can be run concurrently for\ndifferent memcgs when they hit their refcnt to zero.  Fix that.\r\n\r\nWe have been seeing list_lru based kernel crashes at a low frequency in\nour fleet for a long time.  These crashes were in different part of\nlist_lru code including list_lru_add(), list_lru_del() and reparenting\ncode.  Upon further inspection, it looked like for a given object (dentry\nand inode), the super_block\u0026apos;s list_lru didn\u0026apos;t have list_lru_one for the\nmemcg of that object.  The initial suspicions were either the object is\nnot allocated through kmem_cache_alloc_lru() or somehow\nmemcg_list_lru_alloc() failed to allocate list_lru_one() for a memcg but\nreturned success.  No evidence were found for these cases.\r\n\r\nLooking more deeply, we started seeing situations where valid memcg\u0026apos;s id\nis not present in mem_cgroup_idr and in some cases multiple valid memcgs\nhave same id and mem_cgroup_idr is pointing to one of them.  So, the most\nreasonable explanation is that these situations can happen due to race\nbetween multiple idr_remove() calls or race between\nidr_alloc()/idr_replace() and idr_remove().  These races are causing\nmultiple memcgs to acquire the same ID and then offlining of one of them\nwould cleanup list_lrus on the system for all of them.  Later access from\nother memcgs to the list_lru cause crashes due to missing list_lru_one.(CVE-2024-43892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: core: check uartclk for zero to avoid divide by zero\r\n\r\nCalling ioctl TIOCSSERIAL with an invalid baud_base can\nresult in uartclk being zero, which will result in a\ndivide by zero error in uart_get_divisor(). The check for\nuartclk being zero in uart_set_info() needs to be done\nbefore other settings are made as subsequent calls to\nioctl TIOCSSERIAL for the same port would be impacted if\nthe uartclk check was done where uartclk gets set.\r\n\r\nOops: divide error: 0000  PREEMPT SMP KASAN PTI\nRIP: 0010:uart_get_divisor (drivers/tty/serial/serial_core.c:580)\nCall Trace:\n \u0026lt;TASK\u0026gt;\nserial8250_get_divisor (drivers/tty/serial/8250/8250_port.c:2576\n    drivers/tty/serial/8250/8250_port.c:2589)\nserial8250_do_set_termios (drivers/tty/serial/8250/8250_port.c:502\n    drivers/tty/serial/8250/8250_port.c:2741)\nserial8250_set_termios (drivers/tty/serial/8250/8250_port.c:2862)\nuart_change_line_settings (./include/linux/spinlock.h:376\n    ./include/linux/serial_core.h:608 drivers/tty/serial/serial_core.c:222)\nuart_port_startup (drivers/tty/serial/serial_core.c:342)\nuart_startup (drivers/tty/serial/serial_core.c:368)\nuart_set_info (drivers/tty/serial/serial_core.c:1034)\nuart_set_info_user (drivers/tty/serial/serial_core.c:1059)\ntty_set_serial (drivers/tty/tty_io.c:2637)\ntty_ioctl (drivers/tty/tty_io.c:2647 drivers/tty/tty_io.c:2791)\n__x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:907\n    fs/ioctl.c:893 fs/ioctl.c:893)\ndo_syscall_64 (arch/x86/entry/common.c:52\n    (discriminator 1) arch/x86/entry/common.c:83 (discriminator 1))\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nRule: add(CVE-2024-43893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfou: remove warn in gue_gro_receive on unsupported protocol\r\n\r\nDrop the WARN_ON_ONCE inn gue_gro_receive if the encapsulated type is\nnot known or does not have a GRO handler.\r\n\r\nSuch a packet is easily constructed. Syzbot generates them and sets\noff this warning.\r\n\r\nRemove the warning as it is expected and not actionable.\r\n\r\nThe warning was previously reduced from WARN_ON to WARN_ON_ONCE in\ncommit 270136613bf7 (\u0026quot;fou: Do WARN_ON_ONCE in gue_gro_receive for bad\nproto callbacks\u0026quot;).(CVE-2024-44940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\natm: idt77252: prevent use after free in dequeue_rx()\r\n\r\nWe can\u0026apos;t dereference \u0026quot;skb\u0026quot; after calling vcc-\u0026gt;push() because the skb\nis released.(CVE-2024-44998)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxhci: Fix Panther point NULL pointer deref at full-speed re-enumeration\r\n\r\nre-enumerating full-speed devices after a failed address device command\ncan trigger a NULL pointer dereference.\r\n\r\nFull-speed devices may need to reconfigure the endpoint 0 Max Packet Size\nvalue during enumeration. Usb core calls usb_ep0_reinit() in this case,\nwhich ends up calling xhci_configure_endpoint().\r\n\r\nOn Panther point xHC the xhci_configure_endpoint() function will\nadditionally check and reserve bandwidth in software. Other hosts do\nthis in hardware\r\n\r\nIf xHC address device command fails then a new xhci_virt_device structure\nis allocated as part of re-enabling the slot, but the bandwidth table\npointers are not set up properly here.\nThis triggers the NULL pointer dereference the next time usb_ep0_reinit()\nis called and xhci_configure_endpoint() tries to check and reserve\nbandwidth\r\n\r\n[46710.713538] usb 3-1: new full-speed USB device number 5 using xhci_hcd\n[46710.713699] usb 3-1: Device not responding to setup address.\n[46710.917684] usb 3-1: Device not responding to setup address.\n[46711.125536] usb 3-1: device not accepting address 5, error -71\n[46711.125594] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[46711.125600] #PF: supervisor read access in kernel mode\n[46711.125603] #PF: error_code(0x0000) - not-present page\n[46711.125606] PGD 0 P4D 0\n[46711.125610] Oops: Oops: 0000 [#1] PREEMPT SMP PTI\n[46711.125615] CPU: 1 PID: 25760 Comm: kworker/1:2 Not tainted 6.10.3_2 #1\n[46711.125620] Hardware name: Gigabyte Technology Co., Ltd.\n[46711.125623] Workqueue: usb_hub_wq hub_event [usbcore]\n[46711.125668] RIP: 0010:xhci_reserve_bandwidth (drivers/usb/host/xhci.c\r\n\r\nFix this by making sure bandwidth table pointers are set up correctly\nafter a failed address device command, and additionally by avoiding\nchecking for bandwidth in cases like this where no actual endpoints are\nadded or removed, i.e. only context for default control endpoint 0 is\nevaluated.(CVE-2024-45006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/dasd: fix error recovery leading to data corruption on ESE devices\r\n\r\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\r\n\r\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\r\n\r\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\r\n\r\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\r\n\r\nAlso remove the check for file protected since this is not a valid\nESE handling case.(CVE-2024-45026)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: pn533: Add poll mod list filling check\r\n\r\nIn case of im_protocols value is 1 and tm_protocols value is 0 this\ncombination successfully passes the check\n\u0026apos;if (!im_protocols \u0026amp;\u0026amp; !tm_protocols)\u0026apos; in the nfc_start_poll().\nBut then after pn533_poll_create_mod_list() call in pn533_start_poll()\npoll mod list will remain empty and dev-\u0026gt;poll_mod_count will remain 0\nwhich lead to division by zero.\r\n\r\nNormally no im protocol has value 1 in the mask, so this combination is\nnot expected by driver. But these protocol values actually come from\nuserspace via Netlink interface (NFC_CMD_START_POLL operation). So a\nbroken or malicious program may pass a message containing a \u0026quot;bad\u0026quot;\ncombination of protocol parameter values so that dev-\u0026gt;poll_mod_count\nis not incremented inside pn533_poll_create_mod_list(), thus leading\nto division by zero.\nCall trace looks like:\nnfc_genl_start_poll()\n  nfc_start_poll()\n    -\u0026gt;start_poll()\n    pn533_start_poll()\r\n\r\nAdd poll mod list filling check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-46676)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: typec: ucsi: Fix null pointer dereference in trace\r\n\r\nucsi_register_altmode checks IS_ERR for the alt pointer and treats\nNULL as valid. When CONFIG_TYPEC_DP_ALTMODE is not enabled,\nucsi_register_displayport returns NULL which causes a NULL pointer\ndereference in trace. Rather than return NULL, call\ntypec_port_register_altmode to register DisplayPort alternate mode\nas a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled.(CVE-2024-46719)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Remove tst_run from lwt_seg6local_prog_ops.\r\n\r\nThe syzbot reported that the lwt_seg6 related BPF ops can be invoked\nvia bpf_test_run() without without entering input_action_end_bpf()\nfirst.\r\n\r\nMartin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL\nprobably didn\u0026apos;t work since it was introduced in commit 04d4b274e2a\n(\u0026quot;ipv6: sr: Add seg6local action End.BPF\u0026quot;). The reason is that the\nper-CPU variable seg6_bpf_srh_states::srh is never assigned in the self\ntest case but each BPF function expects it.\r\n\r\nRemove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.(CVE-2024-46754)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: Add netif_device_attach/detach into PF reset flow\r\n\r\nEthtool callbacks can be executed while reset is in progress and try to\naccess deleted resources, e.g. getting coalesce settings can result in a\nNULL pointer dereference seen below.\r\n\r\nReproduction steps:\nOnce the driver is fully initialized, trigger reset:\n\t# echo 1 \u0026gt; /sys/class/net/\u0026lt;interface\u0026gt;/device/reset\nwhen reset is in progress try to get coalesce settings using ethtool:\n\t# ethtool -c \u0026lt;interface\u0026gt;\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000020\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] PREEMPT SMP PTI\nCPU: 11 PID: 19713 Comm: ethtool Tainted: G S                 6.10.0-rc7+ #7\nRIP: 0010:ice_get_q_coalesce+0x2e/0xa0 [ice]\nRSP: 0018:ffffbab1e9bcf6a8 EFLAGS: 00010206\nRAX: 000000000000000c RBX: ffff94512305b028 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: ffff9451c3f2e588 RDI: ffff9451c3f2e588\nRBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\nR10: ffff9451c3f2e580 R11: 000000000000001f R12: ffff945121fa9000\nR13: ffffbab1e9bcf760 R14: 0000000000000013 R15: ffffffff9e65dd40\nFS:  00007faee5fbe740(0000) GS:ffff94546fd80000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000020 CR3: 0000000106c2e005 CR4: 00000000001706f0\nCall Trace:\n\u0026lt;TASK\u0026gt;\nice_get_coalesce+0x17/0x30 [ice]\ncoalesce_prepare_data+0x61/0x80\nethnl_default_doit+0xde/0x340\ngenl_family_rcv_msg_doit+0xf2/0x150\ngenl_rcv_msg+0x1b3/0x2c0\nnetlink_rcv_skb+0x5b/0x110\ngenl_rcv+0x28/0x40\nnetlink_unicast+0x19c/0x290\nnetlink_sendmsg+0x222/0x490\n__sys_sendto+0x1df/0x1f0\n__x64_sys_sendto+0x24/0x30\ndo_syscall_64+0x82/0x160\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7faee60d8e27\r\n\r\nCalling netif_device_detach() before reset makes the net core not call\nthe driver when ethtool command is issued, the attempt to execute an\nethtool command during reset will result in the following message:\r\n\r\n    netlink error: No such device\r\n\r\ninstead of NULL pointer dereference. Once reset is done and\nice_rebuild() is executing, the netif_device_attach() is called to allow\nfor ethtool operations to occur again in a safe manner.(CVE-2024-46770)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nksmbd: unset the binding mark of a reused connection\r\n\r\nSteve French reported null pointer dereference error from sha256 lib.\ncifs.ko can send session setup requests on reused connection.\nIf reused connection is used for binding session, conn-\u0026gt;binding can\nstill remain true and generate_preauth_hash() will not set\nsess-\u0026gt;Preauth_HashValue and it will be NULL.\nIt is used as a material to create an encryption key in\nksmbd_gen_smb311_encryptionkey. -\u0026gt;Preauth_HashValue cause null pointer\ndereference error from crypto_shash_update().\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000000\n#PF: supervisor read access in kernel mode\n#PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 8 PID: 429254 Comm: kworker/8:39\nHardware name: LENOVO 20MAS08500/20MAS08500, BIOS N2CET69W (1.52 )\nWorkqueue: ksmbd-io handle_ksmbd_work [ksmbd]\nRIP: 0010:lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n\u0026lt;TASK\u0026gt;\n? show_regs+0x6d/0x80\n? __die+0x24/0x80\n? page_fault_oops+0x99/0x1b0\n? do_user_addr_fault+0x2ee/0x6b0\n? exc_page_fault+0x83/0x1b0\n? asm_exc_page_fault+0x27/0x30\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n_sha256_update+0x77/0xa0 [sha256_ssse3]\nsha256_avx2_update+0x15/0x30 [sha256_ssse3]\ncrypto_shash_update+0x1e/0x40\nhmac_update+0x12/0x20\ncrypto_shash_update+0x1e/0x40\ngenerate_key+0x234/0x380 [ksmbd]\ngenerate_smb3encryptionkey+0x40/0x1c0 [ksmbd]\nksmbd_gen_smb311_encryptionkey+0x72/0xa0 [ksmbd]\nntlm_authenticate.isra.0+0x423/0x5d0 [ksmbd]\nsmb2_sess_setup+0x952/0xaa0 [ksmbd]\n__process_request+0xa3/0x1d0 [ksmbd]\n__handle_ksmbd_work+0x1c4/0x2f0 [ksmbd]\nhandle_ksmbd_work+0x2d/0xa0 [ksmbd]\nprocess_one_work+0x16c/0x350\nworker_thread+0x306/0x440\n? __pfx_worker_thread+0x10/0x10\nkthread+0xef/0x120\n? __pfx_kthread+0x10/0x10\nret_from_fork+0x44/0x70\n? __pfx_kthread+0x10/0x10\nret_from_fork_asm+0x1b/0x30\n\u0026lt;/TASK\u0026gt;(CVE-2024-46795)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: the warning dereferencing obj for nbio_v7_4\r\n\r\nif ras_manager obj null, don\u0026apos;t print NBIO err data(CVE-2024-46819)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched: sch_cake: fix bulk flow accounting logic for host fairness\r\n\r\nIn sch_cake, we keep track of the count of active bulk flows per host,\nwhen running in dst/src host fairness mode, which is used as the\nround-robin weight when iterating through flows. The count of active\nbulk flows is updated whenever a flow changes state.\r\n\r\nThis has a peculiar interaction with the hash collision handling: when a\nhash collision occurs (after the set-associative hashing), the state of\nthe hash bucket is simply updated to match the new packet that collided,\nand if host fairness is enabled, that also means assigning new per-host\nstate to the flow. For this reason, the bulk flow counters of the\nhost(s) assigned to the flow are decremented, before new state is\nassigned (and the counters, which may not belong to the same host\nanymore, are incremented again).\r\n\r\nBack when this code was introduced, the host fairness mode was always\nenabled, so the decrement was unconditional. When the configuration\nflags were introduced the *increment* was made conditional, but\nthe *decrement* was not. Which of course can lead to a spurious\ndecrement (and associated wrap-around to U16_MAX).\r\n\r\nAFAICT, when host fairness is disabled, the decrement and wrap-around\nhappens as soon as a hash collision occurs (which is not that common in\nitself, due to the set-associative hashing). However, in most cases this\nis harmless, as the value is only used when host fairness mode is\nenabled. So in order to trigger an array overflow, sch_cake has to first\nbe configured with host fairness disabled, and while running in this\nmode, a hash collision has to occur to cause the overflow. Then, the\nqdisc has to be reconfigured to enable host fairness, which leads to the\narray out-of-bounds because the wrapped-around value is retained and\nused as an array index. It seems that syzbot managed to trigger this,\nwhich is quite impressive in its own right.\r\n\r\nThis patch fixes the issue by introducing the same conditional check on\ndecrement as is used on increment.\r\n\r\nThe original bug predates the upstreaming of cake, but the commit listed\nin the Fixes tag touched that code, meaning that this patch won\u0026apos;t apply\nbefore that.(CVE-2024-46828)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: clean up our handling of refs == 0 in snapshot delete\r\n\r\nIn reada we BUG_ON(refs == 0), which could be unkind since we aren\u0026apos;t\nholding a lock on the extent leaf and thus could get a transient\nincorrect answer.  In walk_down_proc we also BUG_ON(refs == 0), which\ncould happen if we have extent tree corruption.  Change that to return\n-EUCLEAN.  In do_walk_down() we catch this case and handle it correctly,\nhowever we return -EIO, which -EUCLEAN is a more appropriate error code.\nFinally in walk_up_proc we have the same BUG_ON(refs == 0), so convert\nthat to proper error handling.  Also adjust the error message so we can\nactually do something with the information.(CVE-2024-46840)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nperf/x86/intel: Limit the period on Haswell\r\n\r\nRunning the ltp test cve-2015-3290 concurrently reports the following\nwarnings.\r\n\r\nperfevents: irq loop stuck!\n  WARNING: CPU: 31 PID: 32438 at arch/x86/events/intel/core.c:3174\n  intel_pmu_handle_irq+0x285/0x370\n  Call Trace:\n   \u0026lt;NMI\u0026gt;\n   ? __warn+0xa4/0x220\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? report_bug+0x3e/0xa0\n   ? handle_bug+0x3c/0x70\n   ? exc_invalid_op+0x18/0x50\n   ? asm_exc_invalid_op+0x1a/0x20\n   ? irq_work_claim+0x1e/0x40\n   ? intel_pmu_handle_irq+0x285/0x370\n   perf_event_nmi_handler+0x3d/0x60\n   nmi_handle+0x104/0x330\r\n\r\nThanks to Thomas Gleixner\u0026apos;s analysis, the issue is caused by the low\ninitial period (1) of the frequency estimation algorithm, which triggers\nthe defects of the HW, specifically erratum HSW11 and HSW143. (For the\ndetails, please refer https://lore.kernel.org/lkml/87plq9l5d2.ffs@tglx/)\r\n\r\nThe HSW11 requires a period larger than 100 for the INST_RETIRED.ALL\nevent, but the initial period in the freq mode is 1. The erratum is the\nsame as the BDM11, which has been supported in the kernel. A minimum\nperiod of 128 is enforced as well on HSW.\r\n\r\nHSW143 is regarding that the fixed counter 1 may overcount 32 with the\nHyper-Threading is enabled. However, based on the test, the hardware\nhas more issues than it tells. Besides the fixed counter 1, the message\n\u0026apos;interrupt took too long\u0026apos; can be observed on any counter which was armed\nwith a period \u0026lt; 32 and two events expired in the same NMI. A minimum\nperiod of 32 is enforced for the rest of the events.\nThe recommended workaround code of the HSW143 is not implemented.\nBecause it only addresses the issue for the fixed counter. It brings\nextra overhead through extra MSR writing. No related overcounting issue\nhas been reported so far.(CVE-2024-46848)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dpaa: Pad packets to ETH_ZLEN\r\n\r\nWhen sending packets under 60 bytes, up to three bytes of the buffer\nfollowing the data may be leaked. Avoid this by extending all packets to\nETH_ZLEN, ensuring nothing is leaked in the padding. This bug can be\nreproduced by running\r\n\r\n\t$ ping -s 11 destination(CVE-2024-46854)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nft_socket: fix sk refcount leaks\r\n\r\nWe must put \u0026apos;sk\u0026apos; reference before returning.(CVE-2024-46855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: Fix uaf in __timer_delete_sync\r\n\r\nThere are two paths to access mptcp_pm_del_add_timer, result in a race\ncondition:\r\n\r\n     CPU1\t\t\t\tCPU2\n     ====                               ====\n     net_rx_action\n     napi_poll                          netlink_sendmsg\n     __napi_poll                        netlink_unicast\n     process_backlog                    netlink_unicast_kernel\n     __netif_receive_skb                genl_rcv\n     __netif_receive_skb_one_core       netlink_rcv_skb\n     NF_HOOK                            genl_rcv_msg\n     ip_local_deliver_finish            genl_family_rcv_msg\n     ip_protocol_deliver_rcu            genl_family_rcv_msg_doit\n     tcp_v4_rcv                         mptcp_pm_nl_flush_addrs_doit\n     tcp_v4_do_rcv                      mptcp_nl_remove_addrs_list\n     tcp_rcv_established                mptcp_pm_remove_addrs_and_subflows\n     tcp_data_queue                     remove_anno_list_by_saddr\n     mptcp_incoming_options             mptcp_pm_del_add_timer\n     mptcp_pm_del_add_timer             kfree(entry)\r\n\r\nIn remove_anno_list_by_saddr(running on CPU2), after leaving the critical\nzone protected by \u0026quot;pm.lock\u0026quot;, the entry will be released, which leads to the\noccurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1).\r\n\r\nKeeping a reference to add_timer inside the lock, and calling\nsk_stop_timer_sync() with this reference, instead of \u0026quot;entry-\u0026gt;add_timer\u0026quot;.\r\n\r\nMove list_del(\u0026amp;entry-\u0026gt;list) to mptcp_pm_del_add_timer and inside the pm lock,\ndo not directly access any members of the entry outside the pm lock, which\ncan avoid similar \u0026quot;entry-\u0026gt;x\u0026quot; uaf.(CVE-2024-46858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: stm32/cryp - call finalize with bh disabled\r\n\r\nThe finalize operation in interrupt mode produce a produces a spinlock\nrecursion warning. The reason is the fact that BH must be disabled\nduring this process.(CVE-2024-47658)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware\r\n\r\nIf the value of max_speed_hz is 0, it may cause a division by zero\nerror in hisi_calc_effective_speed().\nThe value of max_speed_hz is provided by firmware.\nFirmware is generally considered as a trusted domain. However, as\ndivision by zero errors can cause system failure, for defense measure,\nthe value of max_speed is validated here. So 0 is regarded as invalid\nand an error code is returned.(CVE-2024-47664)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_xattr_find_entry()\r\n\r\nAdd a paranoia check to make sure it doesn\u0026apos;t stray beyond valid memory\nregion containing ocfs2 xattr entries when scanning for a match.  It will\nprevent out-of-bound access in case of crafted images.(CVE-2024-47670)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbtmc: prevent kernel-usb-infoleak\r\n\r\nThe syzbot reported a kernel-usb-infoleak in usbtmc_write,\nwe need to clear the structure before filling fields.(CVE-2024-47671)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: don\u0026apos;t wait for tx queues if firmware is dead\r\n\r\nThere is a WARNING in iwl_trans_wait_tx_queues_empty() (that was\nrecently converted from just a message), that can be hit if we\nwait for TX queues to become empty after firmware died. Clearly,\nwe can\u0026apos;t expect anything from the firmware after it\u0026apos;s declared dead.\r\n\r\nDon\u0026apos;t call iwl_trans_wait_tx_queues_empty() in this case. While it could\nbe a good idea to stop the flow earlier, the flush functions do some\nmaintenance work that is not related to the firmware, so keep that part\nof the code running even when the firmware is not running.\r\n\r\n[edit commit message](CVE-2024-47672)","status":"published","published":"2024-10-18T11:07:44Z","modified":"2026-08-18T01:17:35.636859842Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2258","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\ns390/qeth: fix deadlock during failing recovery\r\n\r\nCommit 0b9902c1fcc5 (\u0026quot;s390/qeth: fix deadlock during recovery\u0026quot;) removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\r\n\r\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.(CVE-2021-47382)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/i915/gt: Cleanup partial engine discovery failures\r\n\r\nIf we abort driver initialisation in the middle of gt/engine discovery,\nsome engines will be fully setup and some not. Those incompletely setup\nengines only have \u0026apos;engine-\u0026gt;release == NULL\u0026apos; and so will leak any of the\ncommon objects allocated.\r\n\r\nv2:\n - Drop the destroy_pinned_context() helper for now.  It\u0026apos;s not really\n   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: gadget: ncm: Fix handling of zero block length packets\r\n\r\nWhile connecting to a Linux host with CDC_NCM_NTB_DEF_SIZE_TX\nset to 65536, it has been observed that we receive short packets,\nwhich come at interval of 5-10 seconds sometimes and have block\nlength zero but still contain 1-2 valid datagrams present.\r\n\r\nAccording to the NCM spec:\r\n\r\n\u0026quot;If wBlockLength = 0x0000, the block is terminated by a\nshort packet. In this case, the USB transfer must still\nbe shorter than dwNtbInMaxSize or dwNtbOutMaxSize. If\nexactly dwNtbInMaxSize or dwNtbOutMaxSize bytes are sent,\nand the size is a multiple of wMaxPacketSize for the\ngiven pipe, then no ZLP shall be sent.\r\n\r\nwBlockLength= 0x0000 must be used with extreme care, because\nof the possibility that the host and device may get out of\nsync, and because of test issues.\r\n\r\nwBlockLength = 0x0000 allows the sender to reduce latency by\nstarting to send a very large NTB, and then shortening it when\nthe sender discovers that there’s not sufficient data to justify\nsending a large NTB\u0026quot;\r\n\r\nHowever, there is a potential issue with the current implementation,\nas it checks for the occurrence of multiple NTBs in a single\ngiveback by verifying if the leftover bytes to be processed is zero\nor not. If the block length reads zero, we would process the same\nNTB infintely because the leftover bytes is never zero and it leads\nto a crash. Fix this by bailing out if block length reads zero.(CVE-2024-35825)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr\r\n\r\nAlthough ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it\nstill means hlist_for_each_entry_rcu can return an item that got removed\nfrom the list. The memory itself of such item is not freed thanks to RCU\nbut nothing guarantees the actual content of the memory is sane.\r\n\r\nIn particular, the reference count can be zero. This can happen if\nipv6_del_addr is called in parallel. ipv6_del_addr removes the entry\nfrom inet6_addr_lst (hlist_del_init_rcu(\u0026amp;ifp-\u0026gt;addr_lst)) and drops all\nreferences (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough\ntiming, this can happen:\r\n\r\n1. In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry.\r\n\r\n2. Then, the whole ipv6_del_addr is executed for the given entry. The\n   reference count drops to zero and kfree_rcu is scheduled.\r\n\r\n3. ipv6_get_ifaddr continues and tries to increments the reference count\n   (in6_ifa_hold).\r\n\r\n4. The rcu is unlocked and the entry is freed.\r\n\r\n5. The freed entry is returned.\r\n\r\nPrevent increasing of the reference count in such case. The name\nin6_ifa_hold_safe is chosen to mimic the existing fib6_info_hold_safe.\r\n\r\n[   41.506330] refcount_t: addition on 0; use-after-free.\n[   41.506760] WARNING: CPU: 0 PID: 595 at lib/refcount.c:25 refcount_warn_saturate+0xa5/0x130\n[   41.507413] Modules linked in: veth bridge stp llc\n[   41.507821] CPU: 0 PID: 595 Comm: python3 Not tainted 6.9.0-rc2.main-00208-g49563be82afa #14\n[   41.508479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)\n[   41.509163] RIP: 0010:refcount_warn_saturate+0xa5/0x130\n[   41.509586] Code: ad ff 90 0f 0b 90 90 c3 cc cc cc cc 80 3d c0 30 ad 01 00 75 a0 c6 05 b7 30 ad 01 01 90 48 c7 c7 38 cc 7a 8c e8 cc 18 ad ff 90 \u0026lt;0f\u0026gt; 0b 90 90 c3 cc cc cc cc 80 3d 98 30 ad 01 00 0f 85 75 ff ff ff\n[   41.510956] RSP: 0018:ffffbda3c026baf0 EFLAGS: 00010282\n[   41.511368] RAX: 0000000000000000 RBX: ffff9e9c46914800 RCX: 0000000000000000\n[   41.511910] RDX: ffff9e9c7ec29c00 RSI: ffff9e9c7ec1c900 RDI: ffff9e9c7ec1c900\n[   41.512445] RBP: ffff9e9c43660c9c R08: 0000000000009ffb R09: 00000000ffffdfff\n[   41.512998] R10: 00000000ffffdfff R11: ffffffff8ca58a40 R12: ffff9e9c4339a000\n[   41.513534] R13: 0000000000000001 R14: ffff9e9c438a0000 R15: ffffbda3c026bb48\n[   41.514086] FS:  00007fbc4cda1740(0000) GS:ffff9e9c7ec00000(0000) knlGS:0000000000000000\n[   41.514726] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   41.515176] CR2: 000056233b337d88 CR3: 000000000376e006 CR4: 0000000000370ef0\n[   41.515713] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[   41.516252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[   41.516799] Call Trace:\n[   41.517037]  \u0026lt;TASK\u0026gt;\n[   41.517249]  ? __warn+0x7b/0x120\n[   41.517535]  ? refcount_warn_saturate+0xa5/0x130\n[   41.517923]  ? report_bug+0x164/0x190\n[   41.518240]  ? handle_bug+0x3d/0x70\n[   41.518541]  ? exc_invalid_op+0x17/0x70\n[   41.520972]  ? asm_exc_invalid_op+0x1a/0x20\n[   41.521325]  ? refcount_warn_saturate+0xa5/0x130\n[   41.521708]  ipv6_get_ifaddr+0xda/0xe0\n[   41.522035]  inet6_rtm_getaddr+0x342/0x3f0\n[   41.522376]  ? __pfx_inet6_rtm_getaddr+0x10/0x10\n[   41.522758]  rtnetlink_rcv_msg+0x334/0x3d0\n[   41.523102]  ? netlink_unicast+0x30f/0x390\n[   41.523445]  ? __pfx_rtnetlink_rcv_msg+0x10/0x10\n[   41.523832]  netlink_rcv_skb+0x53/0x100\n[   41.524157]  netlink_unicast+0x23b/0x390\n[   41.524484]  netlink_sendmsg+0x1f2/0x440\n[   41.524826]  __sys_sendto+0x1d8/0x1f0\n[   41.525145]  __x64_sys_sendto+0x1f/0x30\n[   41.525467]  do_syscall_64+0xa5/0x1b0\n[   41.525794]  entry_SYSCALL_64_after_hwframe+0x72/0x7a\n[   41.526213] RIP: 0033:0x7fbc4cfcea9a\n[   41.526528] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89\n[   41.527942] RSP: 002b:00007f\n---truncated---(CVE-2024-35969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: honor table dormant flag from netdev release event path\r\n\r\nCheck for table dormant flag otherwise netdev release event path tries\nto unregister an already unregistered hook.\r\n\r\n[524854.857999] ------------[ cut here ]------------\n[524854.858010] WARNING: CPU: 0 PID: 3386599 at net/netfilter/core.c:501 __nf_unregister_net_hook+0x21a/0x260\n[...]\n[524854.858848] CPU: 0 PID: 3386599 Comm: kworker/u32:2 Not tainted 6.9.0-rc3+ #365\n[524854.858869] Workqueue: netns cleanup_net\n[524854.858886] RIP: 0010:__nf_unregister_net_hook+0x21a/0x260\n[524854.858903] Code: 24 e8 aa 73 83 ff 48 63 43 1c 83 f8 01 0f 85 3d ff ff ff e8 98 d1 f0 ff 48 8b 3c 24 e8 8f 73 83 ff 48 63 43 1c e9 26 ff ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 18 48 c7 c7 00 68 e9 82 5b 5d 41 5c 41 5d 41 5e 41\n[524854.858914] RSP: 0018:ffff8881e36d79e0 EFLAGS: 00010246\n[524854.858926] RAX: 0000000000000000 RBX: ffff8881339ae790 RCX: ffffffff81ba524a\n[524854.858936] RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff8881c8a16438\n[524854.858945] RBP: ffff8881c8a16438 R08: 0000000000000001 R09: ffffed103c6daf34\n[524854.858954] R10: ffff8881e36d79a7 R11: 0000000000000000 R12: 0000000000000005\n[524854.858962] R13: ffff8881c8a16000 R14: 0000000000000000 R15: ffff8881351b5a00\n[524854.858971] FS:  0000000000000000(0000) GS:ffff888390800000(0000) knlGS:0000000000000000\n[524854.858982] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[524854.858991] CR2: 00007fc9be0f16f4 CR3: 00000001437cc004 CR4: 00000000001706f0\n[524854.859000] Call Trace:\n[524854.859006]  \u0026lt;TASK\u0026gt;\n[524854.859013]  ? __warn+0x9f/0x1a0\n[524854.859027]  ? __nf_unregister_net_hook+0x21a/0x260\n[524854.859044]  ? report_bug+0x1b1/0x1e0\n[524854.859060]  ? handle_bug+0x3c/0x70\n[524854.859071]  ? exc_invalid_op+0x17/0x40\n[524854.859083]  ? asm_exc_invalid_op+0x1a/0x20\n[524854.859100]  ? __nf_unregister_net_hook+0x6a/0x260\n[524854.859116]  ? __nf_unregister_net_hook+0x21a/0x260\n[524854.859135]  nf_tables_netdev_event+0x337/0x390 [nf_tables]\n[524854.859304]  ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables]\n[524854.859461]  ? packet_notifier+0xb3/0x360\n[524854.859476]  ? _raw_spin_unlock_irqrestore+0x11/0x40\n[524854.859489]  ? dcbnl_netdevice_event+0x35/0x140\n[524854.859507]  ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables]\n[524854.859661]  notifier_call_chain+0x7d/0x140\n[524854.859677]  unregister_netdevice_many_notify+0x5e1/0xae0(CVE-2024-36005)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkeys: Fix overwrite of key expiration on instantiation\r\n\r\nThe expiry time of a key is unconditionally overwritten during\ninstantiation, defaulting to turn it permanent. This causes a problem\nfor DNS resolution as the expiration set by user-space is overwritten to\nTIME64_MAX, disabling further DNS updates. Fix this by restoring the\ncondition that key_set_expiry is only called when the pre-parser sets a\nspecific expiry.(CVE-2024-36031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: tproxy: bail out if IP has been disabled on the device\r\n\r\nsyzbot reports:\ngeneral protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]\n[..]\nRIP: 0010:nf_tproxy_laddr4+0xb7/0x340 net/ipv4/netfilter/nf_tproxy_ipv4.c:62\nCall Trace:\n nft_tproxy_eval_v4 net/netfilter/nft_tproxy.c:56 [inline]\n nft_tproxy_eval+0xa9a/0x1a00 net/netfilter/nft_tproxy.c:168\r\n\r\n__in_dev_get_rcu() can return NULL, so check for this.(CVE-2024-36270)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: qca: add missing firmware sanity checks\r\n\r\nAdd the missing sanity checks when parsing the firmware files before\ndownloading them to avoid accessing and corrupting memory beyond the\nvmalloced buffer.(CVE-2024-36880)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: llcp: fix nfc_llcp_setsockopt() unsafe copies\r\n\r\nsyzbot reported unsafe calls to copy_from_sockptr() [1]\r\n\r\nUse copy_safe_from_sockptr() instead.\r\n\r\n[1]\r\n\r\nBUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline]\n BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline]\n BUG: KASAN: slab-out-of-bounds in nfc_llcp_setsockopt+0x6c2/0x850 net/nfc/llcp_sock.c:255\nRead of size 4 at addr ffff88801caa1ec3 by task syz-executor459/5078\r\n\r\nCPU: 0 PID: 5078 Comm: syz-executor459 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  print_address_description mm/kasan/report.c:377 [inline]\n  print_report+0x169/0x550 mm/kasan/report.c:488\n  kasan_report+0x143/0x180 mm/kasan/report.c:601\n  copy_from_sockptr_offset include/linux/sockptr.h:49 [inline]\n  copy_from_sockptr include/linux/sockptr.h:55 [inline]\n  nfc_llcp_setsockopt+0x6c2/0x850 net/nfc/llcp_sock.c:255\n  do_sock_setsockopt+0x3b1/0x720 net/socket.c:2311\n  __sys_setsockopt+0x1ae/0x250 net/socket.c:2334\n  __do_sys_setsockopt net/socket.c:2343 [inline]\n  __se_sys_setsockopt net/socket.c:2340 [inline]\n  __x64_sys_setsockopt+0xb5/0xd0 net/socket.c:2340\n do_syscall_64+0xfd/0x240\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\nRIP: 0033:0x7f7fac07fd89\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 91 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\nRSP: 002b:00007fff660eb788 EFLAGS: 00000246 ORIG_RAX: 0000000000000036\nRAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f7fac07fd89\nRDX: 0000000000000000 RSI: 0000000000000118 RDI: 0000000000000004\nRBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000000000\nR10: 0000000020000a80 R11: 0000000000000246 R12: 0000000000000000\nR13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000(CVE-2024-36915)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbna: ensure the copied buf is NUL terminated\r\n\r\nCurrently, we allocate a nbytes-sized kernel buffer and copy nbytes from\nuserspace to that buffer. Later, we use sscanf on this buffer but we don\u0026apos;t\nensure that the string is terminated inside the buffer, this can lead to\nOOB read when using sscanf. Fix this issue by using memdup_user_nul\ninstead of memdup_user.(CVE-2024-36934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nphonet: fix rtm_phonet_notify() skb allocation\r\n\r\nfill_route() stores three components in the skb:\r\n\r\n- struct rtmsg\n- RTA_DST (u8)\n- RTA_OIF (u32)\r\n\r\nTherefore, rtm_phonet_notify() should use\r\n\r\nNLMSG_ALIGN(sizeof(struct rtmsg)) +\nnla_total_size(1) +\nnla_total_size(4)(CVE-2024-36946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: vc4: Fix possible null pointer dereference\r\n\r\nIn vc4_hdmi_audio_init() of_get_address() may return\nNULL which is later dereferenced. Fix this bug by adding NULL check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38546)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: bfa: Ensure the copied buf is NUL terminated\r\n\r\nCurrently, we allocate a nbytes-sized kernel buffer and copy nbytes from\nuserspace to that buffer. Later, we use sscanf on this buffer but we don\u0026apos;t\nensure that the string is terminated inside the buffer, this can lead to\nOOB read when using sscanf. Fix this issue by using memdup_user_nul instead\nof memdup_user.(CVE-2024-38560)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: i2c: et8ek8: Don\u0026apos;t strip remove function when driver is builtin\r\n\r\nUsing __exit for the remove function results in the remove callback\nbeing discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets\nunbound (e.g. using sysfs or hotplug), the driver is just removed\nwithout the cleanup being performed. This results in resource leaks. Fix\nit by compiling in the remove callback unconditionally.\r\n\r\nThis also fixes a W=1 modpost warning:\r\n\r\n\tWARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -\u0026gt; et8ek8_remove (section: .exit.text)(CVE-2024-38611)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nm68k: Fix spinlock race in kernel thread creation\r\n\r\nContext switching does take care to retain the correct lock owner across\nthe switch from \u0026apos;prev\u0026apos; to \u0026apos;next\u0026apos; tasks.  This does rely on interrupts\nremaining disabled for the entire duration of the switch.\r\n\r\nThis condition is guaranteed for normal process creation and context\nswitching between already running processes, because both \u0026apos;prev\u0026apos; and\n\u0026apos;next\u0026apos; already have interrupts disabled in their saved copies of the\nstatus register.\r\n\r\nThe situation is different for newly created kernel threads.  The status\nregister is set to PS_S in copy_thread(), which does leave the IPL at 0.\nUpon restoring the \u0026apos;next\u0026apos; thread\u0026apos;s status register in switch_to() aka\nresume(), interrupts then become enabled prematurely.  resume() then\nreturns via ret_from_kernel_thread() and schedule_tail() where run queue\nlock is released (see finish_task_switch() and finish_lock_switch()).\r\n\r\nA timer interrupt calling scheduler_tick() before the lock is released\nin finish_task_switch() will find the lock already taken, with the\ncurrent task as lock owner.  This causes a spinlock recursion warning as\nreported by Guenter Roeck.\r\n\r\nAs far as I can ascertain, this race has been opened in commit\n533e6903bea0 (\u0026quot;m68k: split ret_from_fork(), simplify kernel_thread()\u0026quot;)\nbut I haven\u0026apos;t done a detailed study of kernel history so it may well\npredate that commit.\r\n\r\nInterrupts cannot be disabled in the saved status register copy for\nkernel threads (init will complain about interrupts disabled when\nfinally starting user space).  Disable interrupts temporarily when\nswitching the tasks\u0026apos; register sets in resume().\r\n\r\nNote that a simple oriw 0x700,%sr after restoring sr is not enough here\n- this leaves enough of a race for the \u0026apos;spinlock recursion\u0026apos; warning to\nstill be observed.\r\n\r\nTested on ARAnyM and qemu (Quadra 800 emulation).(CVE-2024-38613)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nenic: Validate length of nl attributes in enic_set_vf_port\r\n\r\nenic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE\nis of length PORT_PROFILE_MAX and that the nl attributes\nIFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX.\nThese attributes are validated (in the function do_setlink in rtnetlink.c)\nusing the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE\nas NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and\nIFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation\nusing the policy is for the max size of the attributes and not on exact\nsize so the length of these attributes might be less than the sizes that\nenic_set_vf_port expects. This might cause an out of bands\nread access in the memcpys of the data of these\nattributes in enic_set_vf_port.(CVE-2024-38659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\num: Add winch to winch_handlers before registering winch IRQ\r\n\r\nRegistering a winch IRQ is racy, an interrupt may occur before the winch is\nadded to the winch_handlers list.\r\n\r\nIf that happens, register_winch_irq() adds to that list a winch that is\nscheduled to be (or has already been) freed, causing a panic later in\nwinch_cleanup().\r\n\r\nAvoid the race by adding the winch to the winch_handlers list before\nregistering the IRQ, and rolling back if um_request_irq() fails.(CVE-2024-39292)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nima: Fix use-after-free on a dentry\u0026apos;s dname.name\r\n\r\n-\u0026gt;d_name.name can change on rename and the earlier value can be freed;\nthere are conditions sufficient to stabilize it (-\u0026gt;d_lock on dentry,\n-\u0026gt;d_lock on its parent, -\u0026gt;i_rwsem exclusive on the parent\u0026apos;s inode,\nrename_lock), but none of those are met at any of the sites. Take a stable\nsnapshot of the name instead.(CVE-2024-39494)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/exynos/vidi: fix memory leak in .get_modes()\r\n\r\nThe duplicated EDID is never freed. Fix it.(CVE-2024-40932)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/radeon: fix UBSAN warning in kv_dpm.c\r\n\r\nAdds bounds check for sumo_vid_mapping_entry.(CVE-2024-40988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Validate ff offset\r\n\r\nThis adds sanity checks for ff offset. There is a check\non rt-\u0026gt;first_free at first, but walking through by ff\nwithout any check. If the second ff is a large offset.\nWe may encounter an out-of-bound read.(CVE-2024-41019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: Fix UAF when resolving a clash\r\n\r\nKASAN reports the following UAF:\r\n\r\n BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n Read of size 1 at addr ffff888c07603600 by task handler130/6469\r\n\r\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  dump_stack_lvl+0x48/0x70\n  print_address_description.constprop.0+0x33/0x3d0\n  print_report+0xc0/0x2b0\n  kasan_report+0xd0/0x120\n  __asan_load1+0x6c/0x80\n  tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n  tcf_ct_act+0x886/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\n  __irq_exit_rcu+0x82/0xc0\n  irq_exit_rcu+0xe/0x20\n  common_interrupt+0xa1/0xb0\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n  asm_common_interrupt+0x27/0x40\r\n\r\n Allocated by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_alloc_info+0x1e/0x40\n  __kasan_krealloc+0x133/0x190\n  krealloc+0xaa/0x130\n  nf_ct_ext_add+0xed/0x230 [nf_conntrack]\n  tcf_ct_act+0x1095/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\n Freed by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_free_info+0x2b/0x60\n  ____kasan_slab_free+0x180/0x1f0\n  __kasan_slab_free+0x12/0x30\n  slab_free_freelist_hook+0xd2/0x1a0\n  __kmem_cache_free+0x1a2/0x2f0\n  kfree+0x78/0x120\n  nf_conntrack_free+0x74/0x130 [nf_conntrack]\n  nf_ct_destroy+0xb2/0x140 [nf_conntrack]\n  __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack]\n  nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack]\n  __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack]\n  tcf_ct_act+0x12ad/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\nThe ct may be dropped if a clash has been resolved but is still passed to\nthe tcf_ct_flow_table_process_conn function for further usage. This issue\ncan be fixed by retrieving ct from skb again after confirming conntrack.(CVE-2024-41040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().\r\n\r\nsyzkaller triggered the warning [0] in udp_v4_early_demux().\r\n\r\nIn udp_v[46]_early_demux() and sk_lookup(), we do not touch the refcount\nof the looked-up sk and use sock_pfree() as skb-\u0026gt;destructor, so we check\nSOCK_RCU_FREE to ensure that the sk is safe to access during the RCU grace\nperiod.\r\n\r\nCurrently, SOCK_RCU_FREE is flagged for a bound socket after being put\ninto the hash table.  Moreover, the SOCK_RCU_FREE check is done too early\nin udp_v[46]_early_demux() and sk_lookup(), so there could be a small race\nwindow:\r\n\r\n  CPU1                                 CPU2\n  ----                                 ----\n  udp_v4_early_demux()                 udp_lib_get_port()\n  |                                    |- hlist_add_head_rcu()\n  |- sk = __udp4_lib_demux_lookup()    |\n  |- DEBUG_NET_WARN_ON_ONCE(sk_is_refcounted(sk));\n                                       `- sock_set_flag(sk, SOCK_RCU_FREE)\r\n\r\nWe had the same bug in TCP and fixed it in commit 871019b22d1b (\u0026quot;net:\nset SOCK_RCU_FREE before inserting socket into hashtable\u0026quot;).\r\n\r\nLet\u0026apos;s apply the same fix for UDP.\r\n\r\n[0]:\nWARNING: CPU: 0 PID: 11198 at net/ipv4/udp.c:2599 udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nModules linked in:\nCPU: 0 PID: 11198 Comm: syz-executor.1 Not tainted 6.9.0-g93bda33046e7 #13\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nCode: c5 7a 15 fe bb 01 00 00 00 44 89 e9 31 ff d3 e3 81 e3 bf ef ff ff 89 de e8 2c 74 15 fe 85 db 0f 85 02 06 00 00 e8 9f 7a 15 fe \u0026lt;0f\u0026gt; 0b e8 98 7a 15 fe 49 8d 7e 60 e8 4f 39 2f fe 49 c7 46 60 20 52\nRSP: 0018:ffffc9000ce3fa58 EFLAGS: 00010293\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8318c92c\nRDX: ffff888036ccde00 RSI: ffffffff8318c2f1 RDI: 0000000000000001\nRBP: ffff88805a2dd6e0 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0001ffffffffffff R12: ffff88805a2dd680\nR13: 0000000000000007 R14: ffff88800923f900 R15: ffff88805456004e\nFS:  00007fc449127640(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fc449126e38 CR3: 000000003de4b002 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ip_rcv_finish_core.constprop.0+0xbdd/0xd20 net/ipv4/ip_input.c:349\n ip_rcv_finish+0xda/0x150 net/ipv4/ip_input.c:447\n NF_HOOK include/linux/netfilter.h:314 [inline]\n NF_HOOK include/linux/netfilter.h:308 [inline]\n ip_rcv+0x16c/0x180 net/ipv4/ip_input.c:569\n __netif_receive_skb_one_core+0xb3/0xe0 net/core/dev.c:5624\n __netif_receive_skb+0x21/0xd0 net/core/dev.c:5738\n netif_receive_skb_internal net/core/dev.c:5824 [inline]\n netif_receive_skb+0x271/0x300 net/core/dev.c:5884\n tun_rx_batched drivers/net/tun.c:1549 [inline]\n tun_get_user+0x24db/0x2c50 drivers/net/tun.c:2002\n tun_chr_write_iter+0x107/0x1a0 drivers/net/tun.c:2048\n new_sync_write fs/read_write.c:497 [inline]\n vfs_write+0x76f/0x8d0 fs/read_write.c:590\n ksys_write+0xbf/0x190 fs/read_write.c:643\n __do_sys_write fs/read_write.c:655 [inline]\n __se_sys_write fs/read_write.c:652 [inline]\n __x64_sys_write+0x41/0x50 fs/read_write.c:652\n x64_sys_call+0xe66/0x1990 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x4b/0x110 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\nRIP: 0033:0x7fc44a68bc1f\nCode: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 e9 cf f5 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 3c d0 f5 ff 48\nRSP: 002b:00007fc449126c90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 00000000004bc050 RCX: 00007fc44a68bc1f\nR\n---truncated---(CVE-2024-41041)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nskmsg: Skip zero length skb in sk_msg_recvmsg\r\n\r\nWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarch\nplatform, the following kernel panic occurs:\r\n\r\n  [...]\n  Oops[#1]:\n  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18\n  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018\n     ... ...\n     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560\n    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0\n   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)\n   PRMD: 0000000c (PPLV0 +PIE +PWE)\n   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)\n   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)\n  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)\n   BADV: 0000000000000040\n   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)\n  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack\n  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)\n  Stack : ...\n  Call Trace:\n  [\u0026lt;9000000004162774\u0026gt;] copy_page_to_iter+0x74/0x1c0\n  [\u0026lt;90000000048bf6c0\u0026gt;] sk_msg_recvmsg+0x120/0x560\n  [\u0026lt;90000000049f2b90\u0026gt;] tcp_bpf_recvmsg_parser+0x170/0x4e0\n  [\u0026lt;90000000049aae34\u0026gt;] inet_recvmsg+0x54/0x100\n  [\u0026lt;900000000481ad5c\u0026gt;] sock_recvmsg+0x7c/0xe0\n  [\u0026lt;900000000481e1a8\u0026gt;] __sys_recvfrom+0x108/0x1c0\n  [\u0026lt;900000000481e27c\u0026gt;] sys_recvfrom+0x1c/0x40\n  [\u0026lt;9000000004c076ec\u0026gt;] do_syscall+0x8c/0xc0\n  [\u0026lt;9000000003731da4\u0026gt;] handle_syscall+0xc4/0x160\n  Code: ...\n  ---[ end trace 0000000000000000 ]---\n  Kernel panic - not syncing: Fatal exception\n  Kernel relocated by 0x3510000\n   .text @ 0x9000000003710000\n   .data @ 0x9000000004d70000\n   .bss  @ 0x9000000006469400\n  ---[ end Kernel panic - not syncing: Fatal exception ]---\n  [...]\r\n\r\nThis crash happens every time when running sockmap_skb_verdict_shutdown\nsubtest in sockmap_basic.\r\n\r\nThis crash is because a NULL pointer is passed to page_address() in the\nsk_msg_recvmsg(). Due to the different implementations depending on the\narchitecture, page_address(NULL) will trigger a panic on Loongarch\nplatform but not on x86 platform. So this bug was hidden on x86 platform\nfor a while, but now it is exposed on Loongarch platform. The root cause\nis that a zero length skb (skb-\u0026gt;len == 0) was put on the queue.\r\n\r\nThis zero length skb is a TCP FIN packet, which was sent by shutdown(),\ninvoked in test_sockmap_skb_verdict_shutdown():\r\n\r\n\tshutdown(p1, SHUT_WR);\r\n\r\nIn this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and no\npage is put to this sge (see sg_set_page in sg_set_page), but this empty\nsge is queued into ingress_msg list.\r\n\r\nAnd in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got by\nsg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes it\nto kmap_local_page() and to page_address(), then kernel panics.\r\n\r\nTo solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),\nif copy is zero, that means it\u0026apos;s a zero length skb, skip invoking\ncopy_page_to_iter(). We are using the EFAULT return triggered by\ncopy_page_to_iter to check for is_fin in tcp_bpf.c.(CVE-2024-41048)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: fix potential use-after-free in posix_lock_inode\r\n\r\nLight Hsieh reported a KASAN UAF warning in trace_posix_lock_inode().\nThe request pointer had been changed earlier to point to a lock entry\nthat was added to the inode\u0026apos;s list. However, before the tracepoint could\nfire, another task raced in and freed that lock.\r\n\r\nFix this by moving the tracepoint inside the spinlock, which should\nensure that this doesn\u0026apos;t happen.(CVE-2024-41049)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: hci_core: cancel all works upon hci_unregister_dev()\r\n\r\nsyzbot is reporting that calling hci_release_dev() from hci_error_reset()\ndue to hci_dev_put() from hci_error_reset() can cause deadlock at\ndestroy_workqueue(), for hci_error_reset() is called from\nhdev-\u0026gt;req_workqueue which destroy_workqueue() needs to flush.\r\n\r\nWe need to make sure that hdev-\u0026gt;{rx_work,cmd_work,tx_work} which are\nqueued into hdev-\u0026gt;workqueue and hdev-\u0026gt;{power_on,error_reset} which are\nqueued into hdev-\u0026gt;req_workqueue are no longer running by the moment\r\n\r\n       destroy_workqueue(hdev-\u0026gt;workqueue);\n       destroy_workqueue(hdev-\u0026gt;req_workqueue);\r\n\r\nare called from hci_release_dev().\r\n\r\nCall cancel_work_sync() on these work items from hci_unregister_dev()\nas soon as hdev-\u0026gt;list is removed from hci_dev_list.(CVE-2024-41063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: topology: Fix references to freed memory\r\n\r\nMost users after parsing a topology file, release memory used by it, so\nhaving pointer references directly into topology file contents is wrong.\nUse devm_kmemdup(), to allocate memory as needed.(CVE-2024-41069)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring: fix possible deadlock in io_register_iowq_max_workers()\r\n\r\nThe io_register_iowq_max_workers() function calls io_put_sq_data(),\nwhich acquires the sqd-\u0026gt;lock without releasing the uring_lock.\nSimilar to the commit 009ad9f0c6ee (\u0026quot;io_uring: drop ctx-\u0026gt;uring_lock\nbefore acquiring sqd-\u0026gt;lock\u0026quot;), this can lead to a potential deadlock\nsituation.\r\n\r\nTo resolve this issue, the uring_lock is released before calling\nio_put_sq_data(), and then it is re-acquired after the function call.\r\n\r\nThis change ensures that the locks are acquired in the correct\norder, preventing the possibility of a deadlock.(CVE-2024-41080)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntap: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tap_get_user_xdp() path, which could cause a corrupted skb to be\nsent downstack. Even before the skb is transmitted, the\ntap_get_user_xdp()--\u0026gt;skb_set_network_header() may assume the size is more\nthan ETH_HLEN. Once transmitted, this could either cause out-of-bound\naccess beyond the actual length, or confuse the underlayer with incorrect\nor inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tap_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tap_get_user() does.\r\n\r\nCVE: CVE-2024-41090(CVE-2024-41090)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntun: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tun_xdp_one() path, which could cause a corrupted skb to be sent\ndownstack. Even before the skb is transmitted, the\ntun_xdp_one--\u0026gt;eth_type_trans() may access the Ethernet header although it\ncan be less than ETH_HLEN. Once transmitted, this could either cause\nout-of-bound access beyond the actual length, or confuse the underlayer\nwith incorrect or inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tun_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted for\nIFF_TAP.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tun_get_user() does.\r\n\r\nCVE: CVE-2024-41091(CVE-2024-41091)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()\r\n\r\nset_memory_rox() can fail, leaving memory unprotected.\r\n\r\nCheck return and bail out when bpf_jit_binary_lock_ro() returns\nan error.(CVE-2024-42067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niio: chemical: bme680: Fix overflows in compensate() functions\r\n\r\nThere are cases in the compensate functions of the driver that\nthere could be overflows of variables due to bit shifting ops.\nThese implications were initially discussed here [1] and they\nwere mentioned in log message of Commit 1b3bd8592780 (\u0026quot;iio:\nchemical: Add support for Bosch BME680 sensor\u0026quot;).\r\n\r\n[1]: https://lore.kernel.org/linux-iio/20180728114028.3c1bbe81@archlinux/(CVE-2024-42086)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: emux: improve patch ioctl data validation\r\n\r\nIn load_data(), make the validation of and skipping over the main info\nblock match that in load_guspatch().\r\n\r\nIn load_guspatch(), add checking that the specified patch length matches\nthe actually supplied data, like load_data() already did.(CVE-2024-42097)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njffs2: Fix potential illegal address access in jffs2_free_inode\r\n\r\nDuring the stress testing of the jffs2 file system,the following\nabnormal printouts were found:\n[ 2430.649000] Unable to handle kernel paging request at virtual address 0069696969696948\n[ 2430.649622] Mem abort info:\n[ 2430.649829]   ESR = 0x96000004\n[ 2430.650115]   EC = 0x25: DABT (current EL), IL = 32 bits\n[ 2430.650564]   SET = 0, FnV = 0\n[ 2430.650795]   EA = 0, S1PTW = 0\n[ 2430.651032]   FSC = 0x04: level 0 translation fault\n[ 2430.651446] Data abort info:\n[ 2430.651683]   ISV = 0, ISS = 0x00000004\n[ 2430.652001]   CM = 0, WnR = 0\n[ 2430.652558] [0069696969696948] address between user and kernel address ranges\n[ 2430.653265] Internal error: Oops: 96000004 [#1] PREEMPT SMP\n[ 2430.654512] CPU: 2 PID: 20919 Comm: cat Not tainted 5.15.25-g512f31242bf6 #33\n[ 2430.655008] Hardware name: linux,dummy-virt (DT)\n[ 2430.655517] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 2430.656142] pc : kfree+0x78/0x348\n[ 2430.656630] lr : jffs2_free_inode+0x24/0x48\n[ 2430.657051] sp : ffff800009eebd10\n[ 2430.657355] x29: ffff800009eebd10 x28: 0000000000000001 x27: 0000000000000000\n[ 2430.658327] x26: ffff000038f09d80 x25: 0080000000000000 x24: ffff800009d38000\n[ 2430.658919] x23: 5a5a5a5a5a5a5a5a x22: ffff000038f09d80 x21: ffff8000084f0d14\n[ 2430.659434] x20: ffff0000bf9a6ac0 x19: 0169696969696940 x18: 0000000000000000\n[ 2430.659969] x17: ffff8000b6506000 x16: ffff800009eec000 x15: 0000000000004000\n[ 2430.660637] x14: 0000000000000000 x13: 00000001000820a1 x12: 00000000000d1b19\n[ 2430.661345] x11: 0004000800000000 x10: 0000000000000001 x9 : ffff8000084f0d14\n[ 2430.662025] x8 : ffff0000bf9a6b40 x7 : ffff0000bf9a6b48 x6 : 0000000003470302\n[ 2430.662695] x5 : ffff00002e41dcc0 x4 : ffff0000bf9aa3b0 x3 : 0000000003470342\n[ 2430.663486] x2 : 0000000000000000 x1 : ffff8000084f0d14 x0 : fffffc0000000000\n[ 2430.664217] Call trace:\n[ 2430.664528]  kfree+0x78/0x348\n[ 2430.664855]  jffs2_free_inode+0x24/0x48\n[ 2430.665233]  i_callback+0x24/0x50\n[ 2430.665528]  rcu_do_batch+0x1ac/0x448\n[ 2430.665892]  rcu_core+0x28c/0x3c8\n[ 2430.666151]  rcu_core_si+0x18/0x28\n[ 2430.666473]  __do_softirq+0x138/0x3cc\n[ 2430.666781]  irq_exit+0xf0/0x110\n[ 2430.667065]  handle_domain_irq+0x6c/0x98\n[ 2430.667447]  gic_handle_irq+0xac/0xe8\n[ 2430.667739]  call_on_irq_stack+0x28/0x54\nThe parameter passed to kfree was 5a5a5a5a, which corresponds to the target field of\nthe jffs_inode_info structure. It was found that all variables in the jffs_inode_info\nstructure were 5a5a5a5a, except for the first member sem. It is suspected that these\nvariables are not initialized because they were set to 5a5a5a5a during memory testing,\nwhich is meant to detect uninitialized memory.The sem variable is initialized in the\nfunction jffs2_i_init_once, while other members are initialized in\nthe function jffs2_init_inode_info.\r\n\r\nThe function jffs2_init_inode_info is called after iget_locked,\nbut in the iget_locked function, the destroy_inode process is triggered,\nwhich releases the inode and consequently, the target member of the inode\nis not initialized.In concurrent high pressure scenarios, iget_locked\nmay enter the destroy_inode branch as described in the code.\r\n\r\nSince the destroy_inode functionality of jffs2 only releases the target,\nthe fix method is to set target to NULL in jffs2_i_init_once.(CVE-2024-42115)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: mlxreg: Use devm_mutex_init() for mutex initialization\r\n\r\nIn this driver LEDs are registered using devm_led_classdev_register()\nso they are automatically unregistered after module\u0026apos;s remove() is done.\nled_classdev_unregister() calls module\u0026apos;s led_set_brightness() to turn off\nthe LEDs and that callback uses mutex which was destroyed already\nin module\u0026apos;s remove() so use devm API instead.(CVE-2024-42129)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc\r\n\r\nInitialize the size before calling amdgpu_vce_cs_reloc, such as case 0x03000001.\nV2: To really improve the handling we would actually\n   need to have a separate value of 0xffffffff.(Christian)(CVE-2024-42228)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: nexthop: Initialize all fields in dumped nexthops\r\n\r\nstruct nexthop_grp contains two reserved fields that are not initialized by\nnla_put_nh_group(), and carry garbage. This can be observed e.g. with\nstrace (edited for clarity):\r\n\r\n    # ip nexthop add id 1 dev lo\n    # ip nexthop add id 101 group 1\n    # strace -e recvmsg ip nexthop get id 101\n    ...\n    recvmsg(... [{nla_len=12, nla_type=NHA_GROUP},\n                 [{id=1, weight=0, resvd1=0x69, resvd2=0x67}]] ...) = 52\r\n\r\nThe fields are reserved and therefore not currently used. But as they are, they\nleak kernel memory, and the fact they are not just zero complicates repurposing\nof the fields for new ends. Initialize the full structure.(CVE-2024-42283)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nirqchip/imx-irqsteer: Handle runtime power management correctly\r\n\r\nThe power domain is automatically activated from clk_prepare(). However, on\ncertain platforms like i.MX8QM and i.MX8QXP, the power-on handling invokes\nsleeping functions, which triggers the \u0026apos;scheduling while atomic\u0026apos; bug in the\ncontext switch path during device probing:\r\n\r\n BUG: scheduling while atomic: kworker/u13:1/48/0x00000002\n Call trace:\n  __schedule_bug+0x54/0x6c\n  __schedule+0x7f0/0xa94\n  schedule+0x5c/0xc4\n  schedule_preempt_disabled+0x24/0x40\n  __mutex_lock.constprop.0+0x2c0/0x540\n  __mutex_lock_slowpath+0x14/0x20\n  mutex_lock+0x48/0x54\n  clk_prepare_lock+0x44/0xa0\n  clk_prepare+0x20/0x44\n  imx_irqsteer_resume+0x28/0xe0\n  pm_generic_runtime_resume+0x2c/0x44\n  __genpd_runtime_resume+0x30/0x80\n  genpd_runtime_resume+0xc8/0x2c0\n  __rpm_callback+0x48/0x1d8\n  rpm_callback+0x6c/0x78\n  rpm_resume+0x490/0x6b4\n  __pm_runtime_resume+0x50/0x94\n  irq_chip_pm_get+0x2c/0xa0\n  __irq_do_set_handler+0x178/0x24c\n  irq_set_chained_handler_and_data+0x60/0xa4\n  mxc_gpio_probe+0x160/0x4b0\r\n\r\nCure this by implementing the irq_bus_lock/sync_unlock() interrupt chip\ncallbacks and handle power management in them as they are invoked from\nnon-atomic context.\r\n\r\n[ tglx: Rewrote change log, added Fixes tag ](CVE-2024-42290)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudf: Avoid using corrupted block bitmap buffer\r\n\r\nWhen the filesystem block bitmap is corrupted, we detect the corruption\nwhile loading the bitmap and fail the allocation with error. However the\nnext allocation from the same bitmap will notice the bitmap buffer is\nalready loaded and tries to allocate from the bitmap with mixed results\n(depending on the exact nature of the bitmap corruption). Fix the\nproblem by using BH_verified bit to indicate whether the bitmap is valid\nor not.(CVE-2024-42306)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\r\n\r\nIn psb_intel_lvds_get_modes(), the return value of drm_mode_duplicate() is\nassigned to mode, which will lead to a possible NULL pointer dereference\non failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42309)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: venus: fix use after free in vdec_close\r\n\r\nThere appears to be a possible use after free with vdec_close().\nThe firmware will add buffer release work to the work queue through\nHFI callbacks as a normal part of decoding. Randomly closing the\ndecoder device from userspace during normal decoding can incur\na read after free for inst.\r\n\r\nFix it by cancelling the work in vdec_close.(CVE-2024-42313)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipvs: properly dereference pe in ip_vs_add_service\r\n\r\nUse pe directly to resolve sparse warning:\r\n\r\n  net/netfilter/ipvs/ip_vs_ctl.c:1471:27: warning: dereference of noderef expression(CVE-2024-42322)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Fix NULL pointer dereference in case of DT error in ks_pcie_setup_rc_app_regs()\r\n\r\nIf IORESOURCE_MEM is not provided in Device Tree due to\nany error, resource_list_first_type() will return NULL and\npci_parse_request_of_pci_ranges() will just emit a warning.\r\n\r\nThis will cause a NULL pointer dereference. Fix this bug by adding NULL\nreturn check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-43823)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: trigger: Unregister sysfs attributes before calling deactivate()\r\n\r\nTriggers which have trigger specific sysfs attributes typically store\nrelated data in trigger-data allocated by the activate() callback and\nfreed by the deactivate() callback.\r\n\r\nCalling device_remove_groups() after calling deactivate() leaves a window\nwhere the sysfs attributes show/store functions could be called after\ndeactivation and then operate on the just freed trigger-data.\r\n\r\nMove the device_remove_groups() call to before deactivate() to close\nthis race window.\r\n\r\nThis also makes the deactivation path properly do things in reverse order\nof the activation path which calls the activate() callback before calling\ndevice_add_groups().(CVE-2024-43830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG\r\n\r\nWhen BPF_TRAMP_F_CALL_ORIG is set, the trampoline calls\n__bpf_tramp_enter() and __bpf_tramp_exit() functions, passing them\nthe struct bpf_tramp_image *im pointer as an argument in R0.\r\n\r\nThe trampoline generation code uses emit_addr_mov_i64() to emit\ninstructions for moving the bpf_tramp_image address into R0, but\nemit_addr_mov_i64() assumes the address to be in the vmalloc() space\nand uses only 48 bits. Because bpf_tramp_image is allocated using\nkzalloc(), its address can use more than 48-bits, in this case the\ntrampoline will pass an invalid address to __bpf_tramp_enter/exit()\ncausing a kernel crash.\r\n\r\nFix this by using emit_a64_mov_i64() in place of emit_addr_mov_i64()\nas it can work with addresses that are greater than 48-bits.(CVE-2024-43840)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd: fix deadlock between mddev_suspend and flush bio\r\n\r\nDeadlock occurs when mddev is being suspended while some flush bio is in\nprogress. It is a complex issue.\r\n\r\nT1. the first flush is at the ending stage, it clears \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;\n    and tries to submit data, but is blocked because mddev is suspended\n    by T4.\nT2. the second flush sets \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;, and attempts to queue\n    md_submit_flush_data(), which is already running (T1) and won\u0026apos;t\n    execute again if on the same CPU as T1.\nT3. the third flush inc active_io and tries to flush, but is blocked because\n    \u0026apos;mddev-\u0026gt;flush_bio\u0026apos; is not NULL (set by T2).\nT4. mddev_suspend() is called and waits for active_io dec to 0 which is inc\n    by T3.\r\n\r\n  T1\t\tT2\t\tT3\t\tT4\n  (flush 1)\t(flush 2)\t(third 3)\t(suspend)\n  md_submit_flush_data\n   mddev-\u0026gt;flush_bio = NULL;\n   .\n   .\t \tmd_flush_request\n   .\t  \t mddev-\u0026gt;flush_bio = bio\n   .\t  \t queue submit_flushes\n   .\t\t .\n   .\t\t .\t\tmd_handle_request\n   .\t\t .\t\t active_io + 1\n   .\t\t .\t\t md_flush_request\n   .\t\t .\t\t  wait !mddev-\u0026gt;flush_bio\n   .\t\t .\n   .\t\t .\t\t\t\tmddev_suspend\n   .\t\t .\t\t\t\t wait !active_io\n   .\t\t .\n   .\t\t submit_flushes\n   .\t\t queue_work md_submit_flush_data\n   .\t\t //md_submit_flush_data is already running (T1)\n   .\n   md_handle_request\n    wait resume\r\n\r\nThe root issue is non-atomic inc/dec of active_io during flush process.\nactive_io is dec before md_submit_flush_data is queued, and inc soon\nafter md_submit_flush_data() run.\n  md_flush_request\n    active_io + 1\n    submit_flushes\n      active_io - 1\n      md_submit_flush_data\n        md_handle_request\n        active_io + 1\n          make_request\n        active_io - 1\r\n\r\nIf active_io is dec after md_handle_request() instead of within\nsubmit_flushes(), make_request() can be called directly intead of\nmd_handle_request() in md_submit_flush_data(), and active_io will\nonly inc and dec once in the whole flush process. Deadlock will be\nfixed.\r\n\r\nAdditionally, the only difference between fixing the issue and before is\nthat there is no return error handling of make_request(). But after\nprevious patch cleaned md_write_start(), make_requst() only return error\nin raid5_make_request() by dm-raid, see commit 41425f96d7aa (\u0026quot;dm-raid456,\nmd/raid456: fix a deadlock for dm-raid456 while io concurrent with\nreshape)\u0026quot;. Since dm always splits data and flush operation into two\nseparate io, io size of flush submitted by dm always is 0, make_request()\nwill not be called in md_submit_flush_data(). To prevent future\nmodifications from introducing issues, add WARN_ON to ensure\nmake_request() no error is returned in this context.(CVE-2024-43855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/hns: Fix soft lockup under heavy CEQE load\r\n\r\nCEQEs are handled in interrupt handler currently. This may cause the\nCPU core staying in interrupt context too long and lead to soft lockup\nunder heavy load.\r\n\r\nHandle CEQEs in BH workqueue and set an upper limit for the number of\nCEQE handled by a single call of work handler.(CVE-2024-43872)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg: protect concurrent access to mem_cgroup_idr\r\n\r\nCommit 73f576c04b94 (\u0026quot;mm: memcontrol: fix cgroup creation failure after\nmany small jobs\u0026quot;) decoupled the memcg IDs from the CSS ID space to fix the\ncgroup creation failures.  It introduced IDR to maintain the memcg ID\nspace.  The IDR depends on external synchronization mechanisms for\nmodifications.  For the mem_cgroup_idr, the idr_alloc() and idr_replace()\nhappen within css callback and thus are protected through cgroup_mutex\nfrom concurrent modifications.  However idr_remove() for mem_cgroup_idr\nwas not protected against concurrency and can be run concurrently for\ndifferent memcgs when they hit their refcnt to zero.  Fix that.\r\n\r\nWe have been seeing list_lru based kernel crashes at a low frequency in\nour fleet for a long time.  These crashes were in different part of\nlist_lru code including list_lru_add(), list_lru_del() and reparenting\ncode.  Upon further inspection, it looked like for a given object (dentry\nand inode), the super_block\u0026apos;s list_lru didn\u0026apos;t have list_lru_one for the\nmemcg of that object.  The initial suspicions were either the object is\nnot allocated through kmem_cache_alloc_lru() or somehow\nmemcg_list_lru_alloc() failed to allocate list_lru_one() for a memcg but\nreturned success.  No evidence were found for these cases.\r\n\r\nLooking more deeply, we started seeing situations where valid memcg\u0026apos;s id\nis not present in mem_cgroup_idr and in some cases multiple valid memcgs\nhave same id and mem_cgroup_idr is pointing to one of them.  So, the most\nreasonable explanation is that these situations can happen due to race\nbetween multiple idr_remove() calls or race between\nidr_alloc()/idr_replace() and idr_remove().  These races are causing\nmultiple memcgs to acquire the same ID and then offlining of one of them\nwould cleanup list_lrus on the system for all of them.  Later access from\nother memcgs to the list_lru cause crashes due to missing list_lru_one.(CVE-2024-43892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: core: check uartclk for zero to avoid divide by zero\r\n\r\nCalling ioctl TIOCSSERIAL with an invalid baud_base can\nresult in uartclk being zero, which will result in a\ndivide by zero error in uart_get_divisor(). The check for\nuartclk being zero in uart_set_info() needs to be done\nbefore other settings are made as subsequent calls to\nioctl TIOCSSERIAL for the same port would be impacted if\nthe uartclk check was done where uartclk gets set.\r\n\r\nOops: divide error: 0000  PREEMPT SMP KASAN PTI\nRIP: 0010:uart_get_divisor (drivers/tty/serial/serial_core.c:580)\nCall Trace:\n \u0026lt;TASK\u0026gt;\nserial8250_get_divisor (drivers/tty/serial/8250/8250_port.c:2576\n    drivers/tty/serial/8250/8250_port.c:2589)\nserial8250_do_set_termios (drivers/tty/serial/8250/8250_port.c:502\n    drivers/tty/serial/8250/8250_port.c:2741)\nserial8250_set_termios (drivers/tty/serial/8250/8250_port.c:2862)\nuart_change_line_settings (./include/linux/spinlock.h:376\n    ./include/linux/serial_core.h:608 drivers/tty/serial/serial_core.c:222)\nuart_port_startup (drivers/tty/serial/serial_core.c:342)\nuart_startup (drivers/tty/serial/serial_core.c:368)\nuart_set_info (drivers/tty/serial/serial_core.c:1034)\nuart_set_info_user (drivers/tty/serial/serial_core.c:1059)\ntty_set_serial (drivers/tty/tty_io.c:2637)\ntty_ioctl (drivers/tty/tty_io.c:2647 drivers/tty/tty_io.c:2791)\n__x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:907\n    fs/ioctl.c:893 fs/ioctl.c:893)\ndo_syscall_64 (arch/x86/entry/common.c:52\n    (discriminator 1) arch/x86/entry/common.c:83 (discriminator 1))\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nRule: add(CVE-2024-43893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfou: remove warn in gue_gro_receive on unsupported protocol\r\n\r\nDrop the WARN_ON_ONCE inn gue_gro_receive if the encapsulated type is\nnot known or does not have a GRO handler.\r\n\r\nSuch a packet is easily constructed. Syzbot generates them and sets\noff this warning.\r\n\r\nRemove the warning as it is expected and not actionable.\r\n\r\nThe warning was previously reduced from WARN_ON to WARN_ON_ONCE in\ncommit 270136613bf7 (\u0026quot;fou: Do WARN_ON_ONCE in gue_gro_receive for bad\nproto callbacks\u0026quot;).(CVE-2024-44940)\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\natm: idt77252: prevent use after free in dequeue_rx()\r\n\r\nWe can\u0026apos;t dereference \u0026quot;skb\u0026quot; after calling vcc-\u0026gt;push() because the skb\nis released.(CVE-2024-44998)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxhci: Fix Panther point NULL pointer deref at full-speed re-enumeration\r\n\r\nre-enumerating full-speed devices after a failed address device command\ncan trigger a NULL pointer dereference.\r\n\r\nFull-speed devices may need to reconfigure the endpoint 0 Max Packet Size\nvalue during enumeration. Usb core calls usb_ep0_reinit() in this case,\nwhich ends up calling xhci_configure_endpoint().\r\n\r\nOn Panther point xHC the xhci_configure_endpoint() function will\nadditionally check and reserve bandwidth in software. Other hosts do\nthis in hardware\r\n\r\nIf xHC address device command fails then a new xhci_virt_device structure\nis allocated as part of re-enabling the slot, but the bandwidth table\npointers are not set up properly here.\nThis triggers the NULL pointer dereference the next time usb_ep0_reinit()\nis called and xhci_configure_endpoint() tries to check and reserve\nbandwidth\r\n\r\n[46710.713538] usb 3-1: new full-speed USB device number 5 using xhci_hcd\n[46710.713699] usb 3-1: Device not responding to setup address.\n[46710.917684] usb 3-1: Device not responding to setup address.\n[46711.125536] usb 3-1: device not accepting address 5, error -71\n[46711.125594] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[46711.125600] #PF: supervisor read access in kernel mode\n[46711.125603] #PF: error_code(0x0000) - not-present page\n[46711.125606] PGD 0 P4D 0\n[46711.125610] Oops: Oops: 0000 [#1] PREEMPT SMP PTI\n[46711.125615] CPU: 1 PID: 25760 Comm: kworker/1:2 Not tainted 6.10.3_2 #1\n[46711.125620] Hardware name: Gigabyte Technology Co., Ltd.\n[46711.125623] Workqueue: usb_hub_wq hub_event [usbcore]\n[46711.125668] RIP: 0010:xhci_reserve_bandwidth (drivers/usb/host/xhci.c\r\n\r\nFix this by making sure bandwidth table pointers are set up correctly\nafter a failed address device command, and additionally by avoiding\nchecking for bandwidth in cases like this where no actual endpoints are\nadded or removed, i.e. only context for default control endpoint 0 is\nevaluated.(CVE-2024-45006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/dasd: fix error recovery leading to data corruption on ESE devices\r\n\r\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\r\n\r\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\r\n\r\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\r\n\r\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\r\n\r\nAlso remove the check for file protected since this is not a valid\nESE handling case.(CVE-2024-45026)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: pn533: Add poll mod list filling check\r\n\r\nIn case of im_protocols value is 1 and tm_protocols value is 0 this\ncombination successfully passes the check\n\u0026apos;if (!im_protocols \u0026amp;\u0026amp; !tm_protocols)\u0026apos; in the nfc_start_poll().\nBut then after pn533_poll_create_mod_list() call in pn533_start_poll()\npoll mod list will remain empty and dev-\u0026gt;poll_mod_count will remain 0\nwhich lead to division by zero.\r\n\r\nNormally no im protocol has value 1 in the mask, so this combination is\nnot expected by driver. But these protocol values actually come from\nuserspace via Netlink interface (NFC_CMD_START_POLL operation). So a\nbroken or malicious program may pass a message containing a \u0026quot;bad\u0026quot;\ncombination of protocol parameter values so that dev-\u0026gt;poll_mod_count\nis not incremented inside pn533_poll_create_mod_list(), thus leading\nto division by zero.\nCall trace looks like:\nnfc_genl_start_poll()\n  nfc_start_poll()\n    -\u0026gt;start_poll()\n    pn533_start_poll()\r\n\r\nAdd poll mod list filling check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-46676)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: typec: ucsi: Fix null pointer dereference in trace\r\n\r\nucsi_register_altmode checks IS_ERR for the alt pointer and treats\nNULL as valid. When CONFIG_TYPEC_DP_ALTMODE is not enabled,\nucsi_register_displayport returns NULL which causes a NULL pointer\ndereference in trace. Rather than return NULL, call\ntypec_port_register_altmode to register DisplayPort alternate mode\nas a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled.(CVE-2024-46719)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Remove tst_run from lwt_seg6local_prog_ops.\r\n\r\nThe syzbot reported that the lwt_seg6 related BPF ops can be invoked\nvia bpf_test_run() without without entering input_action_end_bpf()\nfirst.\r\n\r\nMartin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL\nprobably didn\u0026apos;t work since it was introduced in commit 04d4b274e2a\n(\u0026quot;ipv6: sr: Add seg6local action End.BPF\u0026quot;). The reason is that the\nper-CPU variable seg6_bpf_srh_states::srh is never assigned in the self\ntest case but each BPF function expects it.\r\n\r\nRemove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.(CVE-2024-46754)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: Add netif_device_attach/detach into PF reset flow\r\n\r\nEthtool callbacks can be executed while reset is in progress and try to\naccess deleted resources, e.g. getting coalesce settings can result in a\nNULL pointer dereference seen below.\r\n\r\nReproduction steps:\nOnce the driver is fully initialized, trigger reset:\n\t# echo 1 \u0026gt; /sys/class/net/\u0026lt;interface\u0026gt;/device/reset\nwhen reset is in progress try to get coalesce settings using ethtool:\n\t# ethtool -c \u0026lt;interface\u0026gt;\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000020\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] PREEMPT SMP PTI\nCPU: 11 PID: 19713 Comm: ethtool Tainted: G S                 6.10.0-rc7+ #7\nRIP: 0010:ice_get_q_coalesce+0x2e/0xa0 [ice]\nRSP: 0018:ffffbab1e9bcf6a8 EFLAGS: 00010206\nRAX: 000000000000000c RBX: ffff94512305b028 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: ffff9451c3f2e588 RDI: ffff9451c3f2e588\nRBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\nR10: ffff9451c3f2e580 R11: 000000000000001f R12: ffff945121fa9000\nR13: ffffbab1e9bcf760 R14: 0000000000000013 R15: ffffffff9e65dd40\nFS:  00007faee5fbe740(0000) GS:ffff94546fd80000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000020 CR3: 0000000106c2e005 CR4: 00000000001706f0\nCall Trace:\n\u0026lt;TASK\u0026gt;\nice_get_coalesce+0x17/0x30 [ice]\ncoalesce_prepare_data+0x61/0x80\nethnl_default_doit+0xde/0x340\ngenl_family_rcv_msg_doit+0xf2/0x150\ngenl_rcv_msg+0x1b3/0x2c0\nnetlink_rcv_skb+0x5b/0x110\ngenl_rcv+0x28/0x40\nnetlink_unicast+0x19c/0x290\nnetlink_sendmsg+0x222/0x490\n__sys_sendto+0x1df/0x1f0\n__x64_sys_sendto+0x24/0x30\ndo_syscall_64+0x82/0x160\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7faee60d8e27\r\n\r\nCalling netif_device_detach() before reset makes the net core not call\nthe driver when ethtool command is issued, the attempt to execute an\nethtool command during reset will result in the following message:\r\n\r\n    netlink error: No such device\r\n\r\ninstead of NULL pointer dereference. Once reset is done and\nice_rebuild() is executing, the netif_device_attach() is called to allow\nfor ethtool operations to occur again in a safe manner.(CVE-2024-46770)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nksmbd: unset the binding mark of a reused connection\r\n\r\nSteve French reported null pointer dereference error from sha256 lib.\ncifs.ko can send session setup requests on reused connection.\nIf reused connection is used for binding session, conn-\u0026gt;binding can\nstill remain true and generate_preauth_hash() will not set\nsess-\u0026gt;Preauth_HashValue and it will be NULL.\nIt is used as a material to create an encryption key in\nksmbd_gen_smb311_encryptionkey. -\u0026gt;Preauth_HashValue cause null pointer\ndereference error from crypto_shash_update().\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000000\n#PF: supervisor read access in kernel mode\n#PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 8 PID: 429254 Comm: kworker/8:39\nHardware name: LENOVO 20MAS08500/20MAS08500, BIOS N2CET69W (1.52 )\nWorkqueue: ksmbd-io handle_ksmbd_work [ksmbd]\nRIP: 0010:lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n\u0026lt;TASK\u0026gt;\n? show_regs+0x6d/0x80\n? __die+0x24/0x80\n? page_fault_oops+0x99/0x1b0\n? do_user_addr_fault+0x2ee/0x6b0\n? exc_page_fault+0x83/0x1b0\n? asm_exc_page_fault+0x27/0x30\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n_sha256_update+0x77/0xa0 [sha256_ssse3]\nsha256_avx2_update+0x15/0x30 [sha256_ssse3]\ncrypto_shash_update+0x1e/0x40\nhmac_update+0x12/0x20\ncrypto_shash_update+0x1e/0x40\ngenerate_key+0x234/0x380 [ksmbd]\ngenerate_smb3encryptionkey+0x40/0x1c0 [ksmbd]\nksmbd_gen_smb311_encryptionkey+0x72/0xa0 [ksmbd]\nntlm_authenticate.isra.0+0x423/0x5d0 [ksmbd]\nsmb2_sess_setup+0x952/0xaa0 [ksmbd]\n__process_request+0xa3/0x1d0 [ksmbd]\n__handle_ksmbd_work+0x1c4/0x2f0 [ksmbd]\nhandle_ksmbd_work+0x2d/0xa0 [ksmbd]\nprocess_one_work+0x16c/0x350\nworker_thread+0x306/0x440\n? __pfx_worker_thread+0x10/0x10\nkthread+0xef/0x120\n? __pfx_kthread+0x10/0x10\nret_from_fork+0x44/0x70\n? __pfx_kthread+0x10/0x10\nret_from_fork_asm+0x1b/0x30\n\u0026lt;/TASK\u0026gt;(CVE-2024-46795)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: the warning dereferencing obj for nbio_v7_4\r\n\r\nif ras_manager obj null, don\u0026apos;t print NBIO err data(CVE-2024-46819)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nELF: fix kernel.randomize_va_space double read\r\n\r\nELF loader uses \u0026quot;randomize_va_space\u0026quot; twice. It is sysctl and can change\nat any moment, so 2 loads could see 2 different values in theory with\nunpredictable consequences.\r\n\r\nIssue exactly one load for consistent value across one exec.(CVE-2024-46826)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched: sch_cake: fix bulk flow accounting logic for host fairness\r\n\r\nIn sch_cake, we keep track of the count of active bulk flows per host,\nwhen running in dst/src host fairness mode, which is used as the\nround-robin weight when iterating through flows. The count of active\nbulk flows is updated whenever a flow changes state.\r\n\r\nThis has a peculiar interaction with the hash collision handling: when a\nhash collision occurs (after the set-associative hashing), the state of\nthe hash bucket is simply updated to match the new packet that collided,\nand if host fairness is enabled, that also means assigning new per-host\nstate to the flow. For this reason, the bulk flow counters of the\nhost(s) assigned to the flow are decremented, before new state is\nassigned (and the counters, which may not belong to the same host\nanymore, are incremented again).\r\n\r\nBack when this code was introduced, the host fairness mode was always\nenabled, so the decrement was unconditional. When the configuration\nflags were introduced the *increment* was made conditional, but\nthe *decrement* was not. Which of course can lead to a spurious\ndecrement (and associated wrap-around to U16_MAX).\r\n\r\nAFAICT, when host fairness is disabled, the decrement and wrap-around\nhappens as soon as a hash collision occurs (which is not that common in\nitself, due to the set-associative hashing). However, in most cases this\nis harmless, as the value is only used when host fairness mode is\nenabled. So in order to trigger an array overflow, sch_cake has to first\nbe configured with host fairness disabled, and while running in this\nmode, a hash collision has to occur to cause the overflow. Then, the\nqdisc has to be reconfigured to enable host fairness, which leads to the\narray out-of-bounds because the wrapped-around value is retained and\nused as an array index. It seems that syzbot managed to trigger this,\nwhich is quite impressive in its own right.\r\n\r\nThis patch fixes the issue by introducing the same conditional check on\ndecrement as is used on increment.\r\n\r\nThe original bug predates the upstreaming of cake, but the commit listed\nin the Fixes tag touched that code, meaning that this patch won\u0026apos;t apply\nbefore that.(CVE-2024-46828)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: clean up our handling of refs == 0 in snapshot delete\r\n\r\nIn reada we BUG_ON(refs == 0), which could be unkind since we aren\u0026apos;t\nholding a lock on the extent leaf and thus could get a transient\nincorrect answer.  In walk_down_proc we also BUG_ON(refs == 0), which\ncould happen if we have extent tree corruption.  Change that to return\n-EUCLEAN.  In do_walk_down() we catch this case and handle it correctly,\nhowever we return -EIO, which -EUCLEAN is a more appropriate error code.\nFinally in walk_up_proc we have the same BUG_ON(refs == 0), so convert\nthat to proper error handling.  Also adjust the error message so we can\nactually do something with the information.(CVE-2024-46840)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nperf/x86/intel: Limit the period on Haswell\r\n\r\nRunning the ltp test cve-2015-3290 concurrently reports the following\nwarnings.\r\n\r\nperfevents: irq loop stuck!\n  WARNING: CPU: 31 PID: 32438 at arch/x86/events/intel/core.c:3174\n  intel_pmu_handle_irq+0x285/0x370\n  Call Trace:\n   \u0026lt;NMI\u0026gt;\n   ? __warn+0xa4/0x220\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? report_bug+0x3e/0xa0\n   ? handle_bug+0x3c/0x70\n   ? exc_invalid_op+0x18/0x50\n   ? asm_exc_invalid_op+0x1a/0x20\n   ? irq_work_claim+0x1e/0x40\n   ? intel_pmu_handle_irq+0x285/0x370\n   perf_event_nmi_handler+0x3d/0x60\n   nmi_handle+0x104/0x330\r\n\r\nThanks to Thomas Gleixner\u0026apos;s analysis, the issue is caused by the low\ninitial period (1) of the frequency estimation algorithm, which triggers\nthe defects of the HW, specifically erratum HSW11 and HSW143. (For the\ndetails, please refer https://lore.kernel.org/lkml/87plq9l5d2.ffs@tglx/)\r\n\r\nThe HSW11 requires a period larger than 100 for the INST_RETIRED.ALL\nevent, but the initial period in the freq mode is 1. The erratum is the\nsame as the BDM11, which has been supported in the kernel. A minimum\nperiod of 128 is enforced as well on HSW.\r\n\r\nHSW143 is regarding that the fixed counter 1 may overcount 32 with the\nHyper-Threading is enabled. However, based on the test, the hardware\nhas more issues than it tells. Besides the fixed counter 1, the message\n\u0026apos;interrupt took too long\u0026apos; can be observed on any counter which was armed\nwith a period \u0026lt; 32 and two events expired in the same NMI. A minimum\nperiod of 32 is enforced for the rest of the events.\nThe recommended workaround code of the HSW143 is not implemented.\nBecause it only addresses the issue for the fixed counter. It brings\nextra overhead through extra MSR writing. No related overcounting issue\nhas been reported so far.(CVE-2024-46848)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dpaa: Pad packets to ETH_ZLEN\r\n\r\nWhen sending packets under 60 bytes, up to three bytes of the buffer\nfollowing the data may be leaked. Avoid this by extending all packets to\nETH_ZLEN, ensuring nothing is leaked in the padding. This bug can be\nreproduced by running\r\n\r\n\t$ ping -s 11 destination(CVE-2024-46854)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nft_socket: fix sk refcount leaks\r\n\r\nWe must put \u0026apos;sk\u0026apos; reference before returning.(CVE-2024-46855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: Fix uaf in __timer_delete_sync\r\n\r\nThere are two paths to access mptcp_pm_del_add_timer, result in a race\ncondition:\r\n\r\n     CPU1\t\t\t\tCPU2\n     ====                               ====\n     net_rx_action\n     napi_poll                          netlink_sendmsg\n     __napi_poll                        netlink_unicast\n     process_backlog                    netlink_unicast_kernel\n     __netif_receive_skb                genl_rcv\n     __netif_receive_skb_one_core       netlink_rcv_skb\n     NF_HOOK                            genl_rcv_msg\n     ip_local_deliver_finish            genl_family_rcv_msg\n     ip_protocol_deliver_rcu            genl_family_rcv_msg_doit\n     tcp_v4_rcv                         mptcp_pm_nl_flush_addrs_doit\n     tcp_v4_do_rcv                      mptcp_nl_remove_addrs_list\n     tcp_rcv_established                mptcp_pm_remove_addrs_and_subflows\n     tcp_data_queue                     remove_anno_list_by_saddr\n     mptcp_incoming_options             mptcp_pm_del_add_timer\n     mptcp_pm_del_add_timer             kfree(entry)\r\n\r\nIn remove_anno_list_by_saddr(running on CPU2), after leaving the critical\nzone protected by \u0026quot;pm.lock\u0026quot;, the entry will be released, which leads to the\noccurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1).\r\n\r\nKeeping a reference to add_timer inside the lock, and calling\nsk_stop_timer_sync() with this reference, instead of \u0026quot;entry-\u0026gt;add_timer\u0026quot;.\r\n\r\nMove list_del(\u0026amp;entry-\u0026gt;list) to mptcp_pm_del_add_timer and inside the pm lock,\ndo not directly access any members of the entry outside the pm lock, which\ncan avoid similar \u0026quot;entry-\u0026gt;x\u0026quot; uaf.(CVE-2024-46858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: stm32/cryp - call finalize with bh disabled\r\n\r\nThe finalize operation in interrupt mode produce a produces a spinlock\nrecursion warning. The reason is the fact that BH must be disabled\nduring this process.(CVE-2024-47658)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware\r\n\r\nIf the value of max_speed_hz is 0, it may cause a division by zero\nerror in hisi_calc_effective_speed().\nThe value of max_speed_hz is provided by firmware.\nFirmware is generally considered as a trusted domain. However, as\ndivision by zero errors can cause system failure, for defense measure,\nthe value of max_speed is validated here. So 0 is regarded as invalid\nand an error code is returned.(CVE-2024-47664)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_xattr_find_entry()\r\n\r\nAdd a paranoia check to make sure it doesn\u0026apos;t stray beyond valid memory\nregion containing ocfs2 xattr entries when scanning for a match.  It will\nprevent out-of-bound access in case of crafted images.(CVE-2024-47670)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbtmc: prevent kernel-usb-infoleak\r\n\r\nThe syzbot reported a kernel-usb-infoleak in usbtmc_write,\nwe need to clear the structure before filling fields.(CVE-2024-47671)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: don\u0026apos;t wait for tx queues if firmware is dead\r\n\r\nThere is a WARNING in iwl_trans_wait_tx_queues_empty() (that was\nrecently converted from just a message), that can be hit if we\nwait for TX queues to become empty after firmware died. Clearly,\nwe can\u0026apos;t expect anything from the firmware after it\u0026apos;s declared dead.\r\n\r\nDon\u0026apos;t call iwl_trans_wait_tx_queues_empty() in this case. While it could\nbe a good idea to stop the flow earlier, the flush functions do some\nmaintenance work that is not related to the firmware, so keep that part\nof the code running even when the firmware is not running.\r\n\r\n[edit commit message](CVE-2024-47672)","status":"published","published":"2024-10-18T11:07:44Z","modified":"2026-08-18T01:17:34.647251189Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2522","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\nKVM: SVM: WARN on vNMI + NMI window iff NMIs are outright masked\r\n\r\nWhen requesting an NMI window, WARN on vNMI support being enabled if and\nonly if NMIs are actually masked, i.e. if the vCPU is already handling an\nNMI.  KVM\u0026apos;s ABI for NMIs that arrive simultanesouly (from KVM\u0026apos;s point of\nview) is to inject one NMI and pend the other.  When using vNMI, KVM pends\nthe second NMI simply by setting V_NMI_PENDING, and lets the CPU do the\nrest (hardware automatically sets V_NMI_BLOCKING when an NMI is injected).\r\n\r\nHowever, if KVM can\u0026apos;t immediately inject an NMI, e.g. because the vCPU is\nin an STI shadow or is running with GIF=0, then KVM will request an NMI\nwindow and trigger the WARN (but still function correctly).\r\n\r\nWhether or not the GIF=0 case makes sense is debatable, as the intent of\nKVM\u0026apos;s behavior is to provide functionality that is as close to real\nhardware as possible.  E.g. if two NMIs are sent in quick succession, the\nprobability of both NMIs arriving in an STI shadow is infinitesimally low\non real hardware, but significantly larger in a virtual environment, e.g.\nif the vCPU is preempted in the STI shadow.  For GIF=0, the argument isn\u0026apos;t\nas clear cut, because the window where two NMIs can collide is much larger\nin bare metal (though still small).\r\n\r\nThat said, KVM should not have divergent behavior for the GIF=0 case based\non whether or not vNMI support is enabled.  And KVM has allowed\nsimultaneous NMIs with GIF=0 for over a decade, since commit 7460fb4a3400\n(\u0026quot;KVM: Fix simultaneous NMIs\u0026quot;).  I.e. KVM\u0026apos;s GIF=0 handling shouldn\u0026apos;t be\nmodified without a *really* good reason to do so, and if KVM\u0026apos;s behavior\nwere to be modified, it should be done irrespective of vNMI support.(CVE-2024-39483)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: sc16is7xx: fix invalid FIFO access with special register set\r\n\r\nWhen enabling access to the special register set, Receiver time-out and\nRHR interrupts can happen. In this case, the IRQ handler will try to read\nfrom the FIFO thru the RHR register at address 0x00, but address 0x00 is\nmapped to DLL register, resulting in erroneous FIFO reading.\r\n\r\nCall graph example:\n    sc16is7xx_startup(): entry\n    sc16is7xx_ms_proc(): entry\n    sc16is7xx_set_termios(): entry\n    sc16is7xx_set_baud(): DLH/DLL = $009C --\u0026gt; access special register set\n    sc16is7xx_port_irq() entry            --\u0026gt; IIR is 0x0C\n    sc16is7xx_handle_rx() entry\n    sc16is7xx_fifo_read(): --\u0026gt; unable to access FIFO (RHR) because it is\n                               mapped to DLL (LCR=LCR_CONF_MODE_A)\n    sc16is7xx_set_baud(): exit --\u0026gt; Restore access to general register set\r\n\r\nFix the problem by claiming the efr_lock mutex when accessing the Special\nregister set.(CVE-2024-44950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/dasd: fix error recovery leading to data corruption on ESE devices\r\n\r\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\r\n\r\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\r\n\r\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\r\n\r\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\r\n\r\nAlso remove the check for file protected since this is not a valid\nESE handling case.(CVE-2024-45026)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Add missing NULL pointer check within dpcd_extend_address_range\r\n\r\n[Why \u0026amp; How]\nASSERT if return NULL from kcalloc.(CVE-2024-46808)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check link_index before accessing dc-\u0026gt;links[]\r\n\r\n[WHY \u0026amp; HOW]\ndc-\u0026gt;links[] has max size of MAX_LINKS and NULL is return when trying to\naccess with out-of-bound index.\r\n\r\nThis fixes 3 OVERRUN and 1 RESOURCE_LEAK issues reported by Coverity.(CVE-2024-46813)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check\r\n\r\nThe lookup function iwl_mvm_rcu_fw_link_id_to_link_conf() is\nnormally called with input from the firmware, so it should use\nIWL_FW_CHECK() instead of WARN_ON().(CVE-2024-46825)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: sd: Fix off-by-one error in sd_read_block_characteristics()  Ff the device returns page 0xb1 with length 8 (happens with qemu v2.x, for example), sd_read_block_characteristics() may attempt an out-of-bounds memory access when accessing the zoned field at offset 8.(CVE-2024-47682)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block, bfq: fix possible UAF for bfqq-\u0026gt;bic with merge chain  1) initial state, three tasks:    Process 1       Process 2 Process 3    (BIC1)          (BIC2)   (BIC3)     |  Λ            |  Λ    |  Λ     |  |            |  |    |  |     V  |            V  |    V  |     bfqq1           bfqq2    bfqq3 process ref:    1      1      1  2) bfqq1 merged to bfqq2:    Process 1       Process 2 Process 3    (BIC1)          (BIC2)   (BIC3)     |               |    |  Λ     \\--------------\\|    |  |                     V    V  |     bfqq1---------\u0026gt;bfqq2    bfqq3 process ref:    0      2      1  3) bfqq2 merged to bfqq3:    Process 1       Process 2 Process 3    (BIC1)          (BIC2)   (BIC3)   here -\u0026gt; Λ                |    |     \\--------------\\ \\-------------\\|                     V    V     bfqq1---------\u0026gt;bfqq2----------\u0026gt;bfqq3 process ref:    0      1      3  In this case, IO from Process 1 will get bfqq2 from BIC1 first, and then get bfqq3 through merge chain, and finially handle IO by bfqq3. Howerver, current code will think bfqq2 is owned by BIC1, like initial state, and set bfqq2-\u0026gt;bic to BIC1.  bfq_insert_request -\u0026gt; by Process 1  bfqq = bfq_init_rq(rq)   bfqq = bfq_get_bfqq_handle_split    bfqq = bic_to_bfqq    -\u0026gt; get bfqq2 from BIC1  bfqq-\u0026gt;ref++  rq-\u0026gt;elv.priv[0] = bic  rq-\u0026gt;elv.priv[1] = bfqq  if (bfqq_process_refs(bfqq) == 1)   bfqq-\u0026gt;bic = bic   -\u0026gt; record BIC1 to bfqq2    __bfq_insert_request    new_bfqq = bfq_setup_cooperator    -\u0026gt; get bfqq3 from bfqq2-\u0026gt;new_bfqq    bfqq_request_freed(bfqq)    new_bfqq-\u0026gt;ref++    rq-\u0026gt;elv.priv[1] = new_bfqq    -\u0026gt; handle IO by bfqq3  Fix the problem by checking bfqq is from merge chain fist. And this might fix a following problem reported by our syzkaller(unreproducible):  ================================================================== BUG: KASAN: slab-use-after-free in bfq_do_early_stable_merge block/bfq-iosched.c:5692 [inline] BUG: KASAN: slab-use-after-free in bfq_do_or_sched_stable_merge block/bfq-iosched.c:5805 [inline] BUG: KASAN: slab-use-after-free in bfq_get_queue+0x25b0/0x2610 block/bfq-iosched.c:5889 Write of size 1 at addr ffff888123839eb8 by task kworker/0:1H/18595  CPU: 0 PID: 18595 Comm: kworker/0:1H Tainted: G             L     6.6.0-07439-gba2303cacfda #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Workqueue: kblockd blk_mq_requeue_work Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x91/0xf0 lib/dump_stack.c:106  print_address_description mm/kasan/report.c:364 [inline]  print_report+0x10d/0x610 mm/kasan/report.c:475  kasan_report+0x8e/0xc0 mm/kasan/report.c:588  bfq_do_early_stable_merge block/bfq-iosched.c:5692 [inline]  bfq_do_or_sched_stable_merge block/bfq-iosched.c:5805 [inline]  bfq_get_queue+0x25b0/0x2610 block/bfq-iosched.c:5889  bfq_get_bfqq_handle_split+0x169/0x5d0 block/bfq-iosched.c:6757  bfq_init_rq block/bfq-iosched.c:6876 [inline]  bfq_insert_request block/bfq-iosched.c:6254 [inline]  bfq_insert_requests+0x1112/0x5cf0 block/bfq-iosched.c:6304  blk_mq_insert_request+0x290/0x8d0 block/blk-mq.c:2593  blk_mq_requeue_work+0x6bc/0xa70 block/blk-mq.c:1502  process_one_work kernel/workqueue.c:2627 [inline]  process_scheduled_works+0x432/0x13f0 kernel/workqueue.c:2700  worker_thread+0x6f2/0x1160 kernel/workqueue.c:2781  kthread+0x33c/0x440 kernel/kthread.c:388  ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:305  \u0026lt;/TASK\u0026gt;  Allocated by task 20776:  kasan_save_stack+0x20/0x40 mm/kasan/common.c:45  kasan_set_track+0x25/0x30 mm/kasan/common.c:52  __kasan_slab_alloc+0x87/0x90 mm/kasan/common.c:328  kasan_slab_alloc include/linux/kasan.h:188 [inline]  slab_post_alloc_hook mm/slab.h:763 [inline]  slab_alloc_node mm/slub.c:3458 [inline]  kmem_cache_alloc_node+0x1a4/0x6f0 mm/slub.c:3503  ioc_create_icq block/blk-ioc.c:370 [inline] ---truncated---(CVE-2024-47706)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mt76: mt7996: use hweight16 to get correct tx antenna  The chainmask is u16 so using hweight8 cannot get correct tx_ant. Without this patch, the tx_ant of band 2 would be -1 and lead to the following issue: BUG: KASAN: stack-out-of-bounds in mt7996_mcu_add_sta+0x12e0/0x16e0 [mt7996e](CVE-2024-47714)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mt76: mt7915: fix oops on non-dbdc mt7986  mt7915_band_config() sets band_idx = 1 on the main phy for mt7986 with MT7975_ONE_ADIE or MT7976_ONE_ADIE.  Commit 0335c034e726 (\u0026quot;wifi: mt76: fix race condition related to checking tx queue fill status\u0026quot;) introduced a dereference of the phys array indirectly indexed by band_idx via wcid-\u0026gt;phy_idx in mt76_wcid_cleanup(). This caused the following Oops on affected mt7986 devices:   Unable to handle kernel read from unreadable memory at virtual address 0000000000000024  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    CM = 0, WnR = 0  user pgtable: 4k pages, 39-bit VAs, pgdp=0000000042545000  [0000000000000024] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000  Internal error: Oops: 0000000096000005 [#1] SMP  Modules linked in: ... mt7915e mt76_connac_lib mt76 mac80211 cfg80211 ...  CPU: 2 PID: 1631 Comm: hostapd Not tainted 5.15.150 #0  Hardware name: ZyXEL EX5700 (Telenor) (DT)  pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  pc : mt76_wcid_cleanup+0x84/0x22c [mt76]  lr : mt76_wcid_cleanup+0x64/0x22c [mt76]  sp : ffffffc00a803700  x29: ffffffc00a803700 x28: ffffff80008f7300 x27: ffffff80003f3c00  x26: ffffff80000a7880 x25: ffffffc008c26e00 x24: 0000000000000001  x23: ffffffc000a68114 x22: 0000000000000000 x21: ffffff8004172cc8  x20: ffffffc00a803748 x19: ffffff8004152020 x18: 0000000000000000  x17: 00000000000017c0 x16: ffffffc008ef5000 x15: 0000000000000be0  x14: ffffff8004172e28 x13: ffffff8004172e28 x12: 0000000000000000  x11: 0000000000000000 x10: ffffff8004172e30 x9 : ffffff8004172e28  x8 : 0000000000000000 x7 : ffffff8004156020 x6 : 0000000000000000  x5 : 0000000000000031 x4 : 0000000000000000 x3 : 0000000000000001  x2 : 0000000000000000 x1 : ffffff80008f7300 x0 : 0000000000000024  Call trace:   mt76_wcid_cleanup+0x84/0x22c [mt76]   __mt76_sta_remove+0x70/0xbc [mt76]   mt76_sta_state+0x8c/0x1a4 [mt76]   mt7915_eeprom_get_power_delta+0x11e4/0x23a0 [mt7915e]   drv_sta_state+0x144/0x274 [mac80211]   sta_info_move_state+0x1cc/0x2a4 [mac80211]   sta_set_sinfo+0xaf8/0xc24 [mac80211]   sta_info_destroy_addr_bss+0x4c/0x6c [mac80211]    ieee80211_color_change_finish+0x1c08/0x1e70 [mac80211]   cfg80211_check_station_change+0x1360/0x4710 [cfg80211]   genl_family_rcv_msg_doit+0xb4/0x110   genl_rcv_msg+0xd0/0x1bc   netlink_rcv_skb+0x58/0x120   genl_rcv+0x34/0x50   netlink_unicast+0x1f0/0x2ec   netlink_sendmsg+0x198/0x3d0   ____sys_sendmsg+0x1b0/0x210   ___sys_sendmsg+0x80/0xf0   __sys_sendmsg+0x44/0xa0   __arm64_sys_sendmsg+0x20/0x30   invoke_syscall.constprop.0+0x4c/0xe0   do_el0_svc+0x40/0xd0   el0_svc+0x14/0x4c   el0t_64_sync_handler+0x100/0x110   el0t_64_sync+0x15c/0x160  Code: d2800002 910092c0 52800023 f9800011 (885f7c01)  ---[ end trace 7e42dd9a39ed2281 ]---  Fix by using mt76_dev_phy() which will map band_idx to the correct phy for all hardware combinations.(CVE-2024-47715)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: rtw88: always wait for both firmware loading attempts  In \u0026apos;rtw_wait_firmware_completion()\u0026apos;, always wait for both (regular and wowlan) firmware loading attempts. Otherwise if \u0026apos;rtw_usb_intf_init()\u0026apos; has failed in \u0026apos;rtw_usb_probe()\u0026apos;, \u0026apos;rtw_usb_disconnect()\u0026apos; may issue \u0026apos;ieee80211_free_hw()\u0026apos; when one of \u0026apos;rtw_load_firmware_cb()\u0026apos; (usually the wowlan one) is still in progress, causing UAF detected by KASAN.(CVE-2024-47718)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bonding: Fix unnecessary warnings and logs from bond_xdp_get_xmit_slave()  syzbot reported a WARNING in bond_xdp_get_xmit_slave. To reproduce this[1], one bond device (bond1) has xdpdrv, which increases bpf_master_redirect_enabled_key. Another bond device (bond0) which is unsupported by XDP but its slave (veth3) has xdpgeneric that returns XDP_TX. This triggers WARN_ON_ONCE() from the xdp_master_redirect(). To reduce unnecessary warnings and improve log management, we need to delete the WARN_ON_ONCE() and add ratelimit to the netdev_err().  [1] Steps to reproduce:     # Needs tx_xdp with return XDP_TX;     ip l add veth0 type veth peer veth1     ip l add veth3 type veth peer veth4     ip l add bond0 type bond mode 6 # BOND_MODE_ALB, unsupported by XDP     ip l add bond1 type bond # BOND_MODE_ROUNDROBIN by default     ip l set veth0 master bond1     ip l set bond1 up     # Increases bpf_master_redirect_enabled_key     ip l set dev bond1 xdpdrv object tx_xdp.o section xdp_tx     ip l set veth3 master bond0     ip l set bond0 up     ip l set veth4 up     # Triggers WARN_ON_ONCE() from the xdp_master_redirect()     ip l set veth3 xdpgeneric object tx_xdp.o section xdp_tx(CVE-2024-47734)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: Require FMODE_WRITE for atomic write ioctls  The F2FS ioctls for starting and committing atomic writes check for inode_owner_or_capable(), but this does not give LSMs like SELinux or Landlock an opportunity to deny the write access - if the caller\u0026apos;s FSUID matches the inode\u0026apos;s UID, inode_owner_or_capable() immediately returns true.  There are scenarios where LSMs want to deny a process the ability to write particular files, even files that the FSUID of the process owns; but this can currently partially be bypassed using atomic write ioctls in two ways:   - F2FS_IOC_START_ATOMIC_REPLACE + F2FS_IOC_COMMIT_ATOMIC_WRITE can    truncate an inode to size 0  - F2FS_IOC_START_ATOMIC_WRITE + F2FS_IOC_ABORT_ATOMIC_WRITE can revert    changes another process concurrently made to a file  Fix it by requiring FMODE_WRITE for these operations, just like for F2FS_IOC_MOVE_RANGE. Since any legitimate caller should only be using these ioctls when intending to write into the file, that seems unlikely to break anything.(CVE-2024-47740)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08  Currently rsv_qp is freed before ib_unregister_device() is called on HIP08. During the time interval, users can still dereg MR and rsv_qp will be used in this process, leading to a UAF. Move the release of rsv_qp after calling ib_unregister_device() to fix it.(CVE-2024-47750)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: mediatek: vcodec: Fix H264 multi stateless decoder smatch warning  Fix a smatch static checker warning on vdec_h264_req_multi_if.c. Which leads to a kernel crash when fb is NULL.(CVE-2024-47754)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tpm: Clean up TPM space after command failure  tpm_dev_transmit prepares the TPM space before attempting command transmission. However if the command fails no rollback of this preparation is done. This can result in transient handles being leaked if the device is subsequently closed with no further commands performed.  Fix this by flushing the space in the event of command transmission failure.(CVE-2024-49851)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Fix helper writes to read-only maps  Lonial found an issue that despite user- and BPF-side frozen BPF map (like in case of .rodata), it was still possible to write into it from a BPF program side through specific helpers having ARG_PTR_TO_{LONG,INT} as arguments.  In check_func_arg() when the argument is as mentioned, the meta-\u0026gt;raw_mode is never set. Later, check_helper_mem_access(), under the case of PTR_TO_MAP_VALUE as register base type, it assumes BPF_READ for the subsequent call to check_map_access_type() and given the BPF map is read-only it succeeds.  The helpers really need to be annotated as ARG_PTR_TO_{LONG,INT} | MEM_UNINIT when results are written into them as opposed to read out of them. The latter indicates that it\u0026apos;s okay to pass a pointer to uninitialized memory as the memory is written to anyway.  However, ARG_PTR_TO_{LONG,INT} is a special case of ARG_PTR_TO_FIXED_SIZE_MEM just with additional alignment requirement. So it is better to just get rid of the ARG_PTR_TO_{LONG,INT} special cases altogether and reuse the fixed size memory types. For this, add MEM_ALIGNED to additionally ensure alignment given these helpers write directly into the args via *\u0026lt;ptr\u0026gt; = val. The .arg*_size has been initialized reflecting the actual sizeof(*\u0026lt;ptr\u0026gt;).  MEM_ALIGNED can only be used in combination with MEM_FIXED_SIZE annotated argument types, since in !MEM_FIXED_SIZE cases the verifier does not know the buffer size a priori and therefore cannot blindly write *\u0026lt;ptr\u0026gt; = val.(CVE-2024-49861)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/pm: ensure the fw_info is not null before using it  This resolves the dereference null return value warning reported by Coverity.(CVE-2024-49890)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths  When the HBA is undergoing a reset or is handling an errata event, NULL ptr dereference crashes may occur in routines such as lpfc_sli_flush_io_rings(), lpfc_dev_loss_tmo_callbk(), or lpfc_abort_handler().  Add NULL ptr checks before dereferencing hdwq pointers that may have been freed due to operations colliding with a reset or errata event handler.(CVE-2024-49891)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using dc-\u0026gt;clk_mgr  [WHY \u0026amp; HOW] dc-\u0026gt;clk_mgr is null checked previously in the same function, indicating it might be null.  Passing \u0026quot;dc\u0026quot; to \u0026quot;dc-\u0026gt;hwss.apply_idle_power_optimizations\u0026quot;, which dereferences null \u0026quot;dc-\u0026gt;clk_mgr\u0026quot;. (The function pointer resolves to \u0026quot;dcn35_apply_idle_power_optimizations\u0026quot;.)  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49907)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: iwlwifi: mvm: avoid NULL pointer dereference  iwl_mvm_tx_skb_sta() and iwl_mvm_tx_mpdu() verify that the mvmvsta pointer is not NULL. It retrieves this pointer using iwl_mvm_sta_from_mac80211, which is dereferencing the ieee80211_sta pointer. If sta is NULL, iwl_mvm_sta_from_mac80211 will dereference a NULL pointer. Fix this by checking the sta pointer before retrieving the mvmsta from it. If sta is not NULL, then mvmsta isn\u0026apos;t either.(CVE-2024-49929)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  aoe: fix the potential use-after-free problem in more places  For fixing CVE-2023-6270, f98364e92662 (\u0026quot;aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts\u0026quot;) makes tx() calling dev_put() instead of doing in aoecmd_cfg_pkts(). It avoids that the tx() runs into use-after-free.  Then Nicolai Stange found more places in aoe have potential use-after-free problem with tx(). e.g. revalidate(), aoecmd_ata_rw(), resend(), probe() and aoecmd_cfg_rsp(). Those functions also use aoenet_xmit() to push packet to tx queue. So they should also use dev_hold() to increase the refcnt of skb-\u0026gt;dev.  On the other hand, moving dev_put() to tx() causes that the refcnt of skb-\u0026gt;dev be reduced to a negative value, because corresponding dev_hold() are not called in revalidate(), aoecmd_ata_rw(), resend(), probe(), and aoecmd_cfg_rsp(). This patch fixed this issue.(CVE-2024-49982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/mlx5: Fix error path in multi-packet WQE transmit  Remove the erroneous unmap in case no DMA mapping was established  The multi-packet WQE transmit code attempts to obtain a DMA mapping for the skb. This could fail, e.g. under memory pressure, when the IOMMU driver just can\u0026apos;t allocate more memory for page tables. While the code tries to handle this in the path below the err_unmap label it erroneously unmaps one entry from the sq\u0026apos;s FIFO list of active mappings. Since the current map attempt failed this unmap is removing some random DMA mapping that might still be required. If the PCI function now presents that IOVA, the IOMMU may assumes a rogue DMA access and e.g. on s390 puts the PCI function in error state.  The erroneous behavior was seen in a stress-test environment that created memory pressure.(CVE-2024-50001)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  exec: don\u0026apos;t WARN for racy path_noexec check  Both i_mode and noexec checks wrapped in WARN_ON stem from an artifact of the previous implementation. They used to legitimately check for the condition, but that got moved up in two commits: 633fb6ac3980 (\u0026quot;exec: move S_ISREG() check earlier\u0026quot;) 0fd338b2d2cd (\u0026quot;exec: move path_noexec() check earlier\u0026quot;)  Instead of being removed said checks are WARN_ON\u0026apos;ed instead, which has some debug value.  However, the spurious path_noexec check is racy, resulting in unwarranted warnings should someone race with setting the noexec flag.  One can note there is more to perm-checking whether execve is allowed and none of the conditions are guaranteed to still hold after they were tested for.  Additionally this does not validate whether the code path did any perm checking to begin with -- it will pass if the inode happens to be regular.  Keep the redundant path_noexec() check even though it\u0026apos;s mindless nonsense checking for guarantee that isn\u0026apos;t given so drop the WARN.  Reword the commentary and do small tidy ups while here.  [brauner: keep redundant path_noexec() check](CVE-2024-50010)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: phy: Remove LED entry from LEDs list on unregister  Commit c938ab4da0eb (\u0026quot;net: phy: Manual remove LEDs to ensure correct ordering\u0026quot;) correctly fixed a problem with using devm_ but missed removing the LED entry from the LEDs list.  This cause kernel panic on specific scenario where the port for the PHY is torn down and up and the kmod for the PHY is removed.  On setting the port down the first time, the assosiacted LEDs are correctly unregistered. The associated kmod for the PHY is now removed. The kmod is now added again and the port is now put up, the associated LED are registered again. On putting the port down again for the second time after these step, the LED list now have 4 elements. With the first 2 already unregistered previously and the 2 new one registered again.  This cause a kernel panic as the first 2 element should have been removed.  Fix this by correctly removing the element when LED is unregistered.(CVE-2024-50023)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change  rfcomm_sk_state_change attempts to use sock_lock so it must never be called with it locked but rfcomm_sock_ioctl always attempt to lock it causing the following trace:  ====================================================== WARNING: possible circular locking dependency detected 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted ------------------------------------------------------ syz-executor386/5093 is trying to acquire lock: ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline] ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73  but task is already holding lock: ffff88807badfd28 (\u0026amp;d-\u0026gt;lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491(CVE-2024-50044)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbcon: Fix a NULL pointer dereference issue in fbcon_putcs  syzbot has found a NULL pointer dereference bug in fbcon. Here is the simplified C reproducer:  struct param {  uint8_t type;  struct tiocl_selection ts; };  int main() {  struct fb_con2fbmap con2fb;  struct param param;   int fd = open(\u0026quot;/dev/fb1\u0026quot;, 0, 0);   con2fb.console = 0x19;  con2fb.framebuffer = 0;  ioctl(fd, FBIOPUT_CON2FBMAP, \u0026amp;con2fb);   param.type = 2;  param.ts.xs = 0; param.ts.ys = 0;  param.ts.xe = 0; param.ts.ye = 0;  param.ts.sel_mode = 0;   int fd1 = open(\u0026quot;/dev/tty1\u0026quot;, O_RDWR, 0);  ioctl(fd1, TIOCLINUX, \u0026amp;param);   con2fb.console = 1;  con2fb.framebuffer = 0;  ioctl(fd, FBIOPUT_CON2FBMAP, \u0026amp;con2fb);   return 0; }  After calling ioctl(fd1, TIOCLINUX, \u0026amp;param), the subsequent ioctl(fd, FBIOPUT_CON2FBMAP, \u0026amp;con2fb) causes the kernel to follow a different execution path:   set_con2fb_map   -\u0026gt; con2fb_init_display    -\u0026gt; fbcon_set_disp     -\u0026gt; redraw_screen      -\u0026gt; hide_cursor       -\u0026gt; clear_selection        -\u0026gt; highlight         -\u0026gt; invert_screen          -\u0026gt; do_update_region           -\u0026gt; fbcon_putcs            -\u0026gt; ops-\u0026gt;putcs  Since ops-\u0026gt;putcs is a NULL pointer, this leads to a kernel panic. To prevent this, we need to call set_blitting_type() within set_con2fb_map() to properly initialize ops-\u0026gt;putcs.(CVE-2024-50048)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: Call iso_exit() on module unload  If iso_init() has been called, iso_exit() must be called on module unload. Without that, the struct proto that iso_init() registered with proto_register() becomes invalid, which could cause unpredictable problems later. In my case, with CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, loading the module again usually triggers this BUG():    list_add corruption. next-\u0026gt;prev should be prev (ffffffffb5355fd0),     but was 0000000000000068. (next=ffffffffc0a010d0).   ------------[ cut here ]------------   kernel BUG at lib/list_debug.c:29!   Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI   CPU: 1 PID: 4159 Comm: modprobe Not tainted 6.10.11-4+bt2-ao-desktop #1   RIP: 0010:__list_add_valid_or_report+0x61/0xa0   ...     __list_add_valid_or_report+0x61/0xa0     proto_register+0x299/0x320     hci_sock_init+0x16/0xc0 [bluetooth]     bt_init+0x68/0xd0 [bluetooth]     __pfx_bt_init+0x10/0x10 [bluetooth]     do_one_initcall+0x80/0x2f0     do_init_module+0x8b/0x230     __do_sys_init_module+0x15f/0x190     do_syscall_64+0x68/0x110   ...(CVE-2024-50078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix user-after-free from session log off  There is racy issue between smb2 session log off and smb2 session setup. It will cause user-after-free from session log off. This add session_lock when setting SMB2_SESSION_EXPIRED and referece count to session struct not to free session while it is being used.(CVE-2024-50086)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iommu/vt-d: Fix incorrect pci_for_each_dma_alias() for non-PCI devices  Previously, the domain_context_clear() function incorrectly called pci_for_each_dma_alias() to set up context entries for non-PCI devices. This could lead to kernel hangs or other unexpected behavior.  Add a check to only call pci_for_each_dma_alias() for PCI devices. For non-PCI devices, domain_context_clear_one() is called directly.(CVE-2024-50101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Disable PSR-SU on Parade 08-01 TCON too  Stuart Hayhurst has found that both at bootup and fullscreen VA-API video is leading to black screens for around 1 second and kernel WARNING [1] traces when calling dmub_psr_enable() with Parade 08-01 TCON.  These symptoms all go away with PSR-SU disabled for this TCON, so disable it for now while DMUB traces [2] from the failure can be analyzed and the failure state properly root caused.  (cherry picked from commit afb634a6823d8d9db23c5fb04f79c5549349628b)(CVE-2024-50108)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: sched: use RCU read-side critical section in taprio_dump()  Fix possible use-after-free in \u0026apos;taprio_dump()\u0026apos; by adding RCU read-side critical section there. Never seen on x86 but found on a KASAN-enabled arm64 system when investigating https://syzkaller.appspot.com/bug?extid=b65e0af58423fc8a73aa:  [T15862] BUG: KASAN: slab-use-after-free in taprio_dump+0xa0c/0xbb0 [T15862] Read of size 4 at addr ffff0000d4bb88f8 by task repro/15862 [T15862] [T15862] CPU: 0 UID: 0 PID: 15862 Comm: repro Not tainted 6.11.0-rc1-00293-gdefaf1a2113a-dirty #2 [T15862] Hardware name: QEMU QEMU Virtual Machine, BIOS edk2-20240524-5.fc40 05/24/2024 [T15862] Call trace: [T15862]  dump_backtrace+0x20c/0x220 [T15862]  show_stack+0x2c/0x40 [T15862]  dump_stack_lvl+0xf8/0x174 [T15862]  print_report+0x170/0x4d8 [T15862]  kasan_report+0xb8/0x1d4 [T15862]  __asan_report_load4_noabort+0x20/0x2c [T15862]  taprio_dump+0xa0c/0xbb0 [T15862]  tc_fill_qdisc+0x540/0x1020 [T15862]  qdisc_notify.isra.0+0x330/0x3a0 [T15862]  tc_modify_qdisc+0x7b8/0x1838 [T15862]  rtnetlink_rcv_msg+0x3c8/0xc20 [T15862]  netlink_rcv_skb+0x1f8/0x3d4 [T15862]  rtnetlink_rcv+0x28/0x40 [T15862]  netlink_unicast+0x51c/0x790 [T15862]  netlink_sendmsg+0x79c/0xc20 [T15862]  __sock_sendmsg+0xe0/0x1a0 [T15862]  ____sys_sendmsg+0x6c0/0x840 [T15862]  ___sys_sendmsg+0x1ac/0x1f0 [T15862]  __sys_sendmsg+0x110/0x1d0 [T15862]  __arm64_sys_sendmsg+0x74/0xb0 [T15862]  invoke_syscall+0x88/0x2e0 [T15862]  el0_svc_common.constprop.0+0xe4/0x2a0 [T15862]  do_el0_svc+0x44/0x60 [T15862]  el0_svc+0x50/0x184 [T15862]  el0t_64_sync_handler+0x120/0x12c [T15862]  el0t_64_sync+0x190/0x194 [T15862] [T15862] Allocated by task 15857: [T15862]  kasan_save_stack+0x3c/0x70 [T15862]  kasan_save_track+0x20/0x3c [T15862]  kasan_save_alloc_info+0x40/0x60 [T15862]  __kasan_kmalloc+0xd4/0xe0 [T15862]  __kmalloc_cache_noprof+0x194/0x334 [T15862]  taprio_change+0x45c/0x2fe0 [T15862]  tc_modify_qdisc+0x6a8/0x1838 [T15862]  rtnetlink_rcv_msg+0x3c8/0xc20 [T15862]  netlink_rcv_skb+0x1f8/0x3d4 [T15862]  rtnetlink_rcv+0x28/0x40 [T15862]  netlink_unicast+0x51c/0x790 [T15862]  netlink_sendmsg+0x79c/0xc20 [T15862]  __sock_sendmsg+0xe0/0x1a0 [T15862]  ____sys_sendmsg+0x6c0/0x840 [T15862]  ___sys_sendmsg+0x1ac/0x1f0 [T15862]  __sys_sendmsg+0x110/0x1d0 [T15862]  __arm64_sys_sendmsg+0x74/0xb0 [T15862]  invoke_syscall+0x88/0x2e0 [T15862]  el0_svc_common.constprop.0+0xe4/0x2a0 [T15862]  do_el0_svc+0x44/0x60 [T15862]  el0_svc+0x50/0x184 [T15862]  el0t_64_sync_handler+0x120/0x12c [T15862]  el0t_64_sync+0x190/0x194 [T15862] [T15862] Freed by task 6192: [T15862]  kasan_save_stack+0x3c/0x70 [T15862]  kasan_save_track+0x20/0x3c [T15862]  kasan_save_free_info+0x4c/0x80 [T15862]  poison_slab_object+0x110/0x160 [T15862]  __kasan_slab_free+0x3c/0x74 [T15862]  kfree+0x134/0x3c0 [T15862]  taprio_free_sched_cb+0x18c/0x220 [T15862]  rcu_core+0x920/0x1b7c [T15862]  rcu_core_si+0x10/0x1c [T15862]  handle_softirqs+0x2e8/0xd64 [T15862]  __do_softirq+0x14/0x20(CVE-2024-50126)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: sched: fix use-after-free in taprio_change()  In \u0026apos;taprio_change()\u0026apos;, \u0026apos;admin\u0026apos; pointer may become dangling due to sched switch / removal caused by \u0026apos;advance_sched()\u0026apos;, and critical section protected by \u0026apos;q-\u0026gt;current_entry_lock\u0026apos; is too small to prevent from such a scenario (which causes use-after-free detected by KASAN). Fix this by prefer \u0026apos;rcu_replace_pointer()\u0026apos; over \u0026apos;rcu_assign_pointer()\u0026apos; to update \u0026apos;admin\u0026apos; immediately before an attempt to schedule freeing.(CVE-2024-50127)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: wwan: fix global oob in wwan_rtnl_policy  The variable wwan_rtnl_link_ops assign a *bigger* maxtype which leads to a global out-of-bounds read when parsing the netlink attributes. Exactly same bug cause as the oob fixed in commit b33fb5b801c6 (\u0026quot;net: qualcomm: rmnet: fix global oob in rmnet_policy\u0026quot;).  ================================================================== BUG: KASAN: global-out-of-bounds in validate_nla lib/nlattr.c:388 [inline] BUG: KASAN: global-out-of-bounds in __nla_validate_parse+0x19d7/0x29a0 lib/nlattr.c:603 Read of size 1 at addr ffffffff8b09cb60 by task syz.1.66276/323862  CPU: 0 PID: 323862 Comm: syz.1.66276 Not tainted 6.1.70 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x177/0x231 lib/dump_stack.c:106  print_address_description mm/kasan/report.c:284 [inline]  print_report+0x14f/0x750 mm/kasan/report.c:395  kasan_report+0x139/0x170 mm/kasan/report.c:495  validate_nla lib/nlattr.c:388 [inline]  __nla_validate_parse+0x19d7/0x29a0 lib/nlattr.c:603  __nla_parse+0x3c/0x50 lib/nlattr.c:700  nla_parse_nested_deprecated include/net/netlink.h:1269 [inline]  __rtnl_newlink net/core/rtnetlink.c:3514 [inline]  rtnl_newlink+0x7bc/0x1fd0 net/core/rtnetlink.c:3623  rtnetlink_rcv_msg+0x794/0xef0 net/core/rtnetlink.c:6122  netlink_rcv_skb+0x1de/0x420 net/netlink/af_netlink.c:2508  netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline]  netlink_unicast+0x74b/0x8c0 net/netlink/af_netlink.c:1352  netlink_sendmsg+0x882/0xb90 net/netlink/af_netlink.c:1874  sock_sendmsg_nosec net/socket.c:716 [inline]  __sock_sendmsg net/socket.c:728 [inline]  ____sys_sendmsg+0x5cc/0x8f0 net/socket.c:2499  ___sys_sendmsg+0x21c/0x290 net/socket.c:2553  __sys_sendmsg net/socket.c:2582 [inline]  __do_sys_sendmsg net/socket.c:2591 [inline]  __se_sys_sendmsg+0x19e/0x270 net/socket.c:2589  do_syscall_x64 arch/x86/entry/common.c:51 [inline]  do_syscall_64+0x45/0x90 arch/x86/entry/common.c:81  entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f67b19a24ad RSP: 002b:00007f67b17febb8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f67b1b45f80 RCX: 00007f67b19a24ad RDX: 0000000000000000 RSI: 0000000020005e40 RDI: 0000000000000004 RBP: 00007f67b1a1e01d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd2513764f R14: 00007ffd251376e0 R15: 00007f67b17fed40  \u0026lt;/TASK\u0026gt;  The buggy address belongs to the variable:  wwan_rtnl_policy+0x20/0x40  The buggy address belongs to the physical page: page:ffffea00002c2700 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xb09c flags: 0xfff00000001000(reserved|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000001000 ffffea00002c2708 ffffea00002c2708 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?)  Memory state around the buggy address:  ffffffff8b09ca00: 05 f9 f9 f9 05 f9 f9 f9 00 01 f9 f9 00 01 f9 f9  ffffffff8b09ca80: 00 00 00 05 f9 f9 f9 f9 00 00 03 f9 f9 f9 f9 f9 \u0026gt;ffffffff8b09cb00: 00 00 00 00 05 f9 f9 f9 00 00 00 00 f9 f9 f9 f9                                                        ^  ffffffff8b09cb80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================  According to the comment of `nla_parse_nested_deprecated`, use correct size `IFLA_WWAN_MAX` here to fix this issue.(CVE-2024-50128)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: bpf: must hold reference on net namespace  BUG: KASAN: slab-use-after-free in __nf_unregister_net_hook+0x640/0x6b0 Read of size 8 at addr ffff8880106fe400 by task repro/72= bpf_nf_link_release+0xda/0x1e0 bpf_link_free+0x139/0x2d0 bpf_link_release+0x68/0x80 __fput+0x414/0xb60  Eric says:  It seems that bpf was able to defer the __nf_unregister_net_hook()  after exit()/close() time.  Perhaps a netns reference is missing, because the netns has been  dismantled/freed already.  bpf_nf_link_attach() does :  link-\u0026gt;net = net;  But I do not see a reference being taken on net.  Add such a reference and release it after hook unreg. Note that I was unable to get syzbot reproducer to work, so I do not know if this resolves this splat.(CVE-2024-50130)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nvme-pci: fix race condition between reset and nvme_dev_disable()  nvme_dev_disable() modifies the dev-\u0026gt;online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues().   WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347           pci_irq_get_affinity+0x187/0x210  Workqueue: nvme-reset-wq nvme_reset_work [nvme]  RIP: 0010:pci_irq_get_affinity+0x187/0x210  Call Trace:   \u0026lt;TASK\u0026gt;   ? blk_mq_pci_map_queues+0x87/0x3c0   ? pci_irq_get_affinity+0x187/0x210   blk_mq_pci_map_queues+0x87/0x3c0   nvme_pci_map_queues+0x189/0x460 [nvme]   blk_mq_update_nr_hw_queues+0x2a/0x40   nvme_reset_work+0x1be/0x2a0 [nvme]  Fix the bug by locking the shutdown_lock mutex before using dev-\u0026gt;online_queues. Give up if nvme_dev_disable() is running or if it has been executed already.(CVE-2024-50135)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  reset: starfive: jh71x0: Fix accessing the empty member on JH7110 SoC  data-\u0026gt;asserted will be NULL on JH7110 SoC since commit 82327b127d41 (\u0026quot;reset: starfive: Add StarFive JH7110 reset driver\u0026quot;) was added. Add the judgment condition to avoid errors when calling reset_control_status on JH7110 SoC.(CVE-2024-50137)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: Fix shift-out-of-bounds bug  Fix a shift-out-of-bounds bug reported by UBSAN when running VM with MTE enabled host kernel.  UBSAN: shift-out-of-bounds in arch/arm64/kvm/sys_regs.c:1988:14 shift exponent 33 is too large for 32-bit type \u0026apos;int\u0026apos; CPU: 26 UID: 0 PID: 7629 Comm: qemu-kvm Not tainted 6.12.0-rc2 #34 Hardware name: IEI NF5280R7/Mitchell MB, BIOS 00.00. 2024-10-12 09:28:54 10/14/2024 Call trace:  dump_backtrace+0xa0/0x128  show_stack+0x20/0x38  dump_stack_lvl+0x74/0x90  dump_stack+0x18/0x28  __ubsan_handle_shift_out_of_bounds+0xf8/0x1e0  reset_clidr+0x10c/0x1c8  kvm_reset_sys_regs+0x50/0x1c8  kvm_reset_vcpu+0xec/0x2b0  __kvm_vcpu_set_target+0x84/0x158  kvm_vcpu_set_target+0x138/0x168  kvm_arch_vcpu_ioctl_vcpu_init+0x40/0x2b0  kvm_arch_vcpu_ioctl+0x28c/0x4b8  kvm_vcpu_ioctl+0x4bc/0x7a8  __arm64_sys_ioctl+0xb4/0x100  invoke_syscall+0x70/0x100  el0_svc_common.constprop.0+0x48/0xf0  do_el0_svc+0x24/0x38  el0_svc+0x3c/0x158  el0t_64_sync_handler+0x120/0x130  el0t_64_sync+0x194/0x198(CVE-2024-50139)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  usb: typec: altmode should keep reference to parent  The altmode device release refers to its parent device, but without keeping a reference to it.  When registering the altmode, get a reference to the parent and put it in the release function.  Before this fix, when using CONFIG_DEBUG_KOBJECT_RELEASE, we see issues like this:  [   43.572860] kobject: \u0026apos;port0.0\u0026apos; (ffff8880057ba008): kobject_release, parent 0000000000000000 (delayed 3000) [   43.573532] kobject: \u0026apos;port0.1\u0026apos; (ffff8880057bd008): kobject_release, parent 0000000000000000 (delayed 1000) [   43.574407] kobject: \u0026apos;port0\u0026apos; (ffff8880057b9008): kobject_release, parent 0000000000000000 (delayed 3000) [   43.575059] kobject: \u0026apos;port1.0\u0026apos; (ffff8880057ca008): kobject_release, parent 0000000000000000 (delayed 4000) [   43.575908] kobject: \u0026apos;port1.1\u0026apos; (ffff8880057c9008): kobject_release, parent 0000000000000000 (delayed 4000) [   43.576908] kobject: \u0026apos;typec\u0026apos; (ffff8880062dbc00): kobject_release, parent 0000000000000000 (delayed 4000) [   43.577769] kobject: \u0026apos;port1\u0026apos; (ffff8880057bf008): kobject_release, parent 0000000000000000 (delayed 3000) [   46.612867] ================================================================== [   46.613402] BUG: KASAN: slab-use-after-free in typec_altmode_release+0x38/0x129 [   46.614003] Read of size 8 at addr ffff8880057b9118 by task kworker/2:1/48 [   46.614538] [   46.614668] CPU: 2 UID: 0 PID: 48 Comm: kworker/2:1 Not tainted 6.12.0-rc1-00138-gedbae730ad31 #535 [   46.615391] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [   46.616042] Workqueue: events kobject_delayed_cleanup [   46.616446] Call Trace: [   46.616648]  \u0026lt;TASK\u0026gt; [   46.616820]  dump_stack_lvl+0x5b/0x7c [   46.617112]  ? typec_altmode_release+0x38/0x129 [   46.617470]  print_report+0x14c/0x49e [   46.617769]  ? rcu_read_unlock_sched+0x56/0x69 [   46.618117]  ? __virt_addr_valid+0x19a/0x1ab [   46.618456]  ? kmem_cache_debug_flags+0xc/0x1d [   46.618807]  ? typec_altmode_release+0x38/0x129 [   46.619161]  kasan_report+0x8d/0xb4 [   46.619447]  ? typec_altmode_release+0x38/0x129 [   46.619809]  ? process_scheduled_works+0x3cb/0x85f [   46.620185]  typec_altmode_release+0x38/0x129 [   46.620537]  ? process_scheduled_works+0x3cb/0x85f [   46.620907]  device_release+0xaf/0xf2 [   46.621206]  kobject_delayed_cleanup+0x13b/0x17a [   46.621584]  process_scheduled_works+0x4f6/0x85f [   46.621955]  ? __pfx_process_scheduled_works+0x10/0x10 [   46.622353]  ? hlock_class+0x31/0x9a [   46.622647]  ? lock_acquired+0x361/0x3c3 [   46.622956]  ? move_linked_works+0x46/0x7d [   46.623277]  worker_thread+0x1ce/0x291 [   46.623582]  ? __kthread_parkme+0xc8/0xdf [   46.623900]  ? __pfx_worker_thread+0x10/0x10 [   46.624236]  kthread+0x17e/0x190 [   46.624501]  ? kthread+0xfb/0x190 [   46.624756]  ? __pfx_kthread+0x10/0x10 [   46.625015]  ret_from_fork+0x20/0x40 [   46.625268]  ? __pfx_kthread+0x10/0x10 [   46.625532]  ret_from_fork_asm+0x1a/0x30 [   46.625805]  \u0026lt;/TASK\u0026gt; [   46.625953] [   46.626056] Allocated by task 678: [   46.626287]  kasan_save_stack+0x24/0x44 [   46.626555]  kasan_save_track+0x14/0x2d [   46.626811]  __kasan_kmalloc+0x3f/0x4d [   46.627049]  __kmalloc_noprof+0x1bf/0x1f0 [   46.627362]  typec_register_port+0x23/0x491 [   46.627698]  cros_typec_probe+0x634/0xbb6 [   46.628026]  platform_probe+0x47/0x8c [   46.628311]  really_probe+0x20a/0x47d [   46.628605]  device_driver_attach+0x39/0x72 [   46.628940]  bind_store+0x87/0xd7 [   46.629213]  kernfs_fop_write_iter+0x1aa/0x218 [   46.629574]  vfs_write+0x1d6/0x29b [   46.629856]  ksys_write+0xcd/0x13b [   46.630128]  do_syscall_64+0xd4/0x139 [   46.630420]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   46.630820] [   46.630946] Freed by task 48: [   46.631182]  kasan_save_stack+0x24/0x44 [   46.631493]  kasan_save_track+0x14/0x2d [   46.631799]  kasan_save_free_info+0x3f/0x4d [   46.632144]  __kasan_slab_free+0x37/0x45 [   46.632474] ---truncated---(CVE-2024-50150)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netdevsim: use cond_resched() in nsim_dev_trap_report_work()  I am still seeing many syzbot reports hinting that syzbot might fool nsim_dev_trap_report_work() with hundreds of ports [1]  Lets use cond_resched(), and system_unbound_wq instead of implicit system_wq.  [1] INFO: task syz-executor:20633 blocked for more than 143 seconds.       Not tainted 6.12.0-rc2-syzkaller-00205-g1d227fcc7222 #0 \u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message. task:syz-executor    state:D stack:25856 pid:20633 tgid:20633 ppid:1      flags:0x00004006 ... NMI backtrace for cpu 1 CPU: 1 UID: 0 PID: 16760 Comm: kworker/1:0 Not tainted 6.12.0-rc2-syzkaller-00205-g1d227fcc7222 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events nsim_dev_trap_report_work  RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x70 kernel/kcov.c:210 Code: 89 fb e8 23 00 00 00 48 8b 3d 04 fb 9c 0c 48 89 de 5b e9 c3 c7 5d 00 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 \u0026lt;f3\u0026gt; 0f 1e fa 48 8b 04 24 65 48 8b 0c 25 c0 d7 03 00 65 8b 15 60 f0 RSP: 0018:ffffc90000a187e8 EFLAGS: 00000246 RAX: 0000000000000100 RBX: ffffc90000a188e0 RCX: ffff888027d3bc00 RDX: ffff888027d3bc00 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffff88804a2e6000 R08: ffffffff8a4bc495 R09: ffffffff89da3577 R10: 0000000000000004 R11: ffffffff8a4bc2b0 R12: dffffc0000000000 R13: ffff88806573b503 R14: dffffc0000000000 R15: ffff8880663cca00 FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fc90a747f98 CR3: 000000000e734000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 000000000000002b DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;NMI\u0026gt;  \u0026lt;/NMI\u0026gt;  \u0026lt;TASK\u0026gt;   __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382   spin_unlock_bh include/linux/spinlock.h:396 [inline]   nsim_dev_trap_report drivers/net/netdevsim/dev.c:820 [inline]   nsim_dev_trap_report_work+0x75d/0xaa0 drivers/net/netdevsim/dev.c:850   process_one_work kernel/workqueue.c:3229 [inline]   process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310   worker_thread+0x870/0xd30 kernel/workqueue.c:3391   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;(CVE-2024-50155)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/bnxt_re: Fix out of bound check  Driver exports pacing stats only on GenP5 and P7 adapters. But while parsing the pacing stats, driver has a check for \u0026quot;rdev-\u0026gt;dbr_pacing\u0026quot;.  This caused a trace when KASAN is enabled.  BUG: KASAN: slab-out-of-bounds in bnxt_re_get_hw_stats+0x2b6a/0x2e00 [bnxt_re] Write of size 8 at addr ffff8885942a6340 by task modprobe/4809(CVE-2024-50158)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Make sure internal and UAPI bpf_redirect flags don\u0026apos;t overlap  The bpf_redirect_info is shared between the SKB and XDP redirect paths, and the two paths use the same numeric flag values in the ri-\u0026gt;flags field (specifically, BPF_F_BROADCAST == BPF_F_NEXTHOP). This means that if skb bpf_redirect_neigh() is used with a non-NULL params argument and, subsequently, an XDP redirect is performed using the same bpf_redirect_info struct, the XDP path will get confused and end up crashing, which syzbot managed to trigger.  With the stack-allocated bpf_redirect_info, the structure is no longer shared between the SKB and XDP paths, so the crash doesn\u0026apos;t happen anymore. However, different code paths using identically-numbered flag values in the same struct field still seems like a bit of a mess, so this patch cleans that up by moving the flag definitions together and redefining the three flags in BPF_F_REDIRECT_INTERNAL to not overlap with the flags used for XDP. It also adds a BUILD_BUG_ON() check to make sure the overlap is not re-introduced by mistake.(CVE-2024-50163)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Fix overloading of MEM_UNINIT\u0026apos;s meaning  Lonial reported an issue in the BPF verifier where check_mem_size_reg() has the following code:      if (!tnum_is_const(reg-\u0026gt;var_off))         /* For unprivileged variable accesses, disable raw          * mode so that the program is required to          * initialize all the memory that the helper could          * just partially fill up.          */          meta = NULL;  This means that writes are not checked when the register containing the size of the passed buffer has not a fixed size. Through this bug, a BPF program can write to a map which is marked as read-only, for example, .rodata global maps.  The problem is that MEM_UNINIT\u0026apos;s initial meaning that \u0026quot;the passed buffer to the BPF helper does not need to be initialized\u0026quot; which was added back in commit 435faee1aae9 (\u0026quot;bpf, verifier: add ARG_PTR_TO_RAW_STACK type\u0026quot;) got overloaded over time with \u0026quot;the passed buffer is being written to\u0026quot;.  The problem however is that checks such as the above which were added later via 06c1c049721a (\u0026quot;bpf: allow helpers access to variable memory\u0026quot;) set meta to NULL in order force the user to always initialize the passed buffer to the helper. Due to the current double meaning of MEM_UNINIT, this bypasses verifier write checks to the memory (not boundary checks though) and only assumes the latter memory is read instead.  Fix this by reverting MEM_UNINIT back to its original meaning, and having MEM_WRITE as an annotation to BPF helpers in order to then trigger the BPF verifier checks for writing to memory.  Some notes: check_arg_pair_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO} we can access fn-\u0026gt;arg_type[arg - 1] since it must contain a preceding ARG_PTR_TO_MEM. For check_mem_reg() the meta argument can be removed altogether since we do check both BPF_READ and BPF_WRITE. Same for the equivalent check_kfunc_mem_size_reg().(CVE-2024-50164)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/vc4: Stop the active perfmon before being destroyed  Upon closing the file descriptor, the active performance monitor is not stopped. Although all perfmons are destroyed in `vc4_perfmon_close_file()`, the active performance monitor\u0026apos;s pointer (`vc4-\u0026gt;active_perfmon`) is still retained.  If we open a new file descriptor and submit a few jobs with performance monitors, the driver will attempt to stop the active performance monitor using the stale pointer in `vc4-\u0026gt;active_perfmon`. However, this pointer is no longer valid because the previous process has already terminated, and all performance monitors associated with it have been destroyed and freed.  To fix this, when the active performance monitor belongs to a given process, explicitly stop it before destroying and freeing it.(CVE-2024-50187)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: phy: dp83869: fix memory corruption when enabling fiber  When configuring the fiber port, the DP83869 PHY driver incorrectly calls linkmode_set_bit() with a bit mask (1 \u0026lt;\u0026lt; 10) rather than a bit number (10). This corrupts some other memory location -- in case of arm64 the priv pointer in the same structure.  Since the advertising flags are updated from supported at the end of the function the incorrect line isn\u0026apos;t needed at all and can be removed.(CVE-2024-50188)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  pinctrl: ocelot: fix system hang on level based interrupts  The current implementation only calls chained_irq_enter() and chained_irq_exit() if it detects pending interrupts.  ``` for (i = 0; i \u0026lt; info-\u0026gt;stride; i++) {  uregmap_read(info-\u0026gt;map, id_reg + 4 * i, \u0026amp;reg);  if (!reg)   continue;   chained_irq_enter(parent_chip, desc); ```  However, in case of GPIO pin configured in level mode and the parent controller configured in edge mode, GPIO interrupt might be lowered by the hardware. In the result, if the interrupt is short enough, the parent interrupt is still pending while the GPIO interrupt is cleared; chained_irq_enter() never gets called and the system hangs trying to service the parent interrupt.  Moving chained_irq_enter() and chained_irq_exit() outside the for loop ensures that they are called even when GPIO interrupt is lowered by the hardware.  The similar code with chained_irq_enter() / chained_irq_exit() functions wrapping interrupt checking loop may be found in many other drivers: ``` grep -r -A 10 chained_irq_enter drivers/pinctrl ```(CVE-2024-50196)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/radeon: Fix encoder-\u0026gt;possible_clones  Include the encoder itself in its possible_clones bitmask. In the past nothing validated that drivers were populating possible_clones correctly, but that changed in commit 74d2aacbe840 (\u0026quot;drm: Validate encoder-\u0026gt;possible_clones\u0026quot;). Looks like radeon never got the memo and is still not following the rules 100% correctly.  This results in some warnings during driver initialization: Bogus possible_clones: [ENCODER:46:TV-46] possible_clones=0x4 (full encoder mask=0x7) WARNING: CPU: 0 PID: 170 at drivers/gpu/drm/drm_mode_config.c:615 drm_mode_config_validate+0x113/0x39c ...  (cherry picked from commit 3b6e7d40649c0d75572039aff9d0911864c689db)(CVE-2024-50201)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  udf: refactor inode_bmap() to handle error  Refactor inode_bmap() to handle error since udf_next_aext() can return error now. On situations like ftruncate, udf_extend_file() can now detect errors and bail out early without resorting to checking for particular offsets and assuming internal behavior of these functions.(CVE-2024-50211)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow  Syzbot reported a kernel BUG in ocfs2_truncate_inline.  There are two reasons for this: first, the parameter value passed is greater than ocfs2_max_inline_data_with_xattr, second, the start and end parameters of ocfs2_truncate_inline are \u0026quot;unsigned int\u0026quot;.  So, we need to add a sanity check for byte_start and byte_len right before ocfs2_truncate_inline() in ocfs2_remove_inode_range(), if they are greater than ocfs2_max_inline_data_with_xattr return -EINVAL.(CVE-2024-50218)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP  generic/077 on x86_32 CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP=y with highmem, on huge=always tmpfs, issues a warning and then hangs (interruptibly):  WARNING: CPU: 5 PID: 3517 at mm/highmem.c:622 kunmap_local_indexed+0x62/0xc9 CPU: 5 UID: 0 PID: 3517 Comm: cp Not tainted 6.12.0-rc4 #2 ... copy_page_from_iter_atomic+0xa6/0x5ec generic_perform_write+0xf6/0x1b4 shmem_file_write_iter+0x54/0x67  Fix copy_page_from_iter_atomic() by limiting it in that case (include/linux/skbuff.h skb_frag_must_loop() does similar).  But going forward, perhaps CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP is too surprising, has outlived its usefulness, and should just be removed?(CVE-2024-50222)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cxl/port: Fix use-after-free, permit out-of-order decoder shutdown  In support of investigating an initialization failure report [1], cxl_test was updated to register mock memory-devices after the mock root-port/bus device had been registered. That led to cxl_test crashing with a use-after-free bug with the following signature:      cxl_port_attach_region: cxl region3: cxl_host_bridge.0:port3 decoder3.0 add: mem0:decoder7.0 @ 0 next: cxl_switch_uport.0 nr_eps: 1 nr_targets: 1     cxl_port_attach_region: cxl region3: cxl_host_bridge.0:port3 decoder3.0 add: mem4:decoder14.0 @ 1 next: cxl_switch_uport.0 nr_eps: 2 nr_targets: 1     cxl_port_setup_targets: cxl region3: cxl_switch_uport.0:port6 target[0] = cxl_switch_dport.0 for mem0:decoder7.0 @ 0 1)  cxl_port_setup_targets: cxl region3: cxl_switch_uport.0:port6 target[1] = cxl_switch_dport.4 for mem4:decoder14.0 @ 1     [..]     cxld_unregister: cxl decoder14.0:     cxl_region_decode_reset: cxl_region region3:     mock_decoder_reset: cxl_port port3: decoder3.0 reset 2)  mock_decoder_reset: cxl_port port3: decoder3.0: out of order reset, expected decoder3.1     cxl_endpoint_decoder_release: cxl decoder14.0:     [..]     cxld_unregister: cxl decoder7.0: 3)  cxl_region_decode_reset: cxl_region region3:     Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6bc3: 0000 [#1] PREEMPT SMP PTI     [..]     RIP: 0010:to_cxl_port+0x8/0x60 [cxl_core]     [..]     Call Trace:      \u0026lt;TASK\u0026gt;      cxl_region_decode_reset+0x69/0x190 [cxl_core]      cxl_region_detach+0xe8/0x210 [cxl_core]      cxl_decoder_kill_region+0x27/0x40 [cxl_core]      cxld_unregister+0x5d/0x60 [cxl_core]  At 1) a region has been established with 2 endpoint decoders (7.0 and 14.0). Those endpoints share a common switch-decoder in the topology (3.0). At teardown, 2), decoder14.0 is the first to be removed and hits the \u0026quot;out of order reset case\u0026quot; in the switch decoder. The effect though is that region3 cleanup is aborted leaving it in-tact and referencing decoder14.0. At 3) the second attempt to teardown region3 trips over the stale decoder14.0 object which has long since been deleted.  The fix here is to recognize that the CXL specification places no mandate on in-order shutdown of switch-decoders, the driver enforces in-order allocation, and hardware enforces in-order commit. So, rather than fail and leave objects dangling, always remove them.  In support of making cxl_region_decode_reset() always succeed, cxl_region_invalidate_memregion() failures are turned into warnings. Crashing the kernel is ok there since system integrity is at risk if caches cannot be managed around physical address mutation events like CXL region destruction.  A new device_for_each_child_reverse_from() is added to cleanup port-\u0026gt;commit_end after all dependent decoders have been disabled. In other words if decoders are allocated 0-\u0026gt;1-\u0026gt;2 and disabled 1-\u0026gt;2-\u0026gt;0 then port-\u0026gt;commit_end only decrements from 2 after 2 has been disabled, and it decrements all the way to zero since 1 was disabled previously.(CVE-2024-50226)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential deadlock with newly created symlinks  Syzbot reported that page_symlink(), called by nilfs_symlink(), triggers memory reclamation involving the filesystem layer, which can result in circular lock dependencies among the reader/writer semaphore nilfs-\u0026gt;ns_segctor_sem, s_writers percpu_rwsem (intwrite) and the fs_reclaim pseudo lock.  This is because after commit 21fc61c73c39 (\u0026quot;don\u0026apos;t put symlink bodies in pagecache into highmem\u0026quot;), the gfp flags of the page cache for symbolic links are overwritten to GFP_KERNEL via inode_nohighmem().  This is not a problem for symlinks read from the backing device, because the __GFP_FS flag is dropped after inode_nohighmem() is called.  However, when a new symlink is created with nilfs_symlink(), the gfp flags remain overwritten to GFP_KERNEL.  Then, memory allocation called from page_symlink() etc.  triggers memory reclamation including the FS layer, which may call nilfs_evict_inode() or nilfs_dirty_inode().  And these can cause a deadlock if they are called while nilfs-\u0026gt;ns_segctor_sem is held:  Fix this issue by dropping the __GFP_FS flag from the page cache GFP flags of newly created symlinks in the same way that nilfs_new_inode() and __nilfs_read_inode() do, as a workaround until we adopt nofs allocation scope consistently or improve the locking constraints.(CVE-2024-50229)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: clear wdev-\u0026gt;cqm_config pointer on free  When we free wdev-\u0026gt;cqm_config when unregistering, we also need to clear out the pointer since the same wdev/netdev may get re-registered in another network namespace, then destroyed later, running this code again, which results in a double-free.(CVE-2024-50235)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netdevsim: Add trailing zero to terminate the string in nsim_nexthop_bucket_activity_write()  This was found by a static analyzer. We should not forget the trailing zero after copy_from_user() if we will further do some string operations, sscanf() in this case. Adding a trailing zero will ensure that the function performs properly.(CVE-2024-50259)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  macsec: Fix use-after-free while sending the offloading packet  KASAN reports the following UAF. The metadata_dst, which is used to store the SCI value for macsec offload, is already freed by metadata_dst_free() in macsec_free_netdev(), while driver still use it for sending the packet.  To fix this issue, dst_release() is used instead to release metadata_dst. So it is not freed instantly in macsec_free_netdev() if still referenced by skb.   BUG: KASAN: slab-use-after-free in mlx5e_xmit+0x1e8f/0x4190 [mlx5_core]  Read of size 2 at addr ffff88813e42e038 by task kworker/7:2/714  [...]  Workqueue: mld mld_ifc_work  Call Trace:   \u0026lt;TASK\u0026gt;   dump_stack_lvl+0x51/0x60   print_report+0xc1/0x600   kasan_report+0xab/0xe0   mlx5e_xmit+0x1e8f/0x4190 [mlx5_core]   dev_hard_start_xmit+0x120/0x530   sch_direct_xmit+0x149/0x11e0   __qdisc_run+0x3ad/0x1730   __dev_queue_xmit+0x1196/0x2ed0   vlan_dev_hard_start_xmit+0x32e/0x510 [8021q]   dev_hard_start_xmit+0x120/0x530   __dev_queue_xmit+0x14a7/0x2ed0   macsec_start_xmit+0x13e9/0x2340   dev_hard_start_xmit+0x120/0x530   __dev_queue_xmit+0x14a7/0x2ed0   ip6_finish_output2+0x923/0x1a70   ip6_finish_output+0x2d7/0x970   ip6_output+0x1ce/0x3a0   NF_HOOK.constprop.0+0x15f/0x190   mld_sendpack+0x59a/0xbd0   mld_ifc_work+0x48a/0xa80   process_one_work+0x5aa/0xe50   worker_thread+0x79c/0x1290   kthread+0x28f/0x350   ret_from_fork+0x2d/0x70   ret_from_fork_asm+0x11/0x20   \u0026lt;/TASK\u0026gt;   Allocated by task 3922:   kasan_save_stack+0x20/0x40   kasan_save_track+0x10/0x30   __kasan_kmalloc+0x77/0x90   __kmalloc_noprof+0x188/0x400   metadata_dst_alloc+0x1f/0x4e0   macsec_newlink+0x914/0x1410   __rtnl_newlink+0xe08/0x15b0   rtnl_newlink+0x5f/0x90   rtnetlink_rcv_msg+0x667/0xa80   netlink_rcv_skb+0x12c/0x360   netlink_unicast+0x551/0x770   netlink_sendmsg+0x72d/0xbd0   __sock_sendmsg+0xc5/0x190   ____sys_sendmsg+0x52e/0x6a0   ___sys_sendmsg+0xeb/0x170   __sys_sendmsg+0xb5/0x140   do_syscall_64+0x4c/0x100   entry_SYSCALL_64_after_hwframe+0x4b/0x53   Freed by task 4011:   kasan_save_stack+0x20/0x40   kasan_save_track+0x10/0x30   kasan_save_free_info+0x37/0x50   poison_slab_object+0x10c/0x190   __kasan_slab_free+0x11/0x30   kfree+0xe0/0x290   macsec_free_netdev+0x3f/0x140   netdev_run_todo+0x450/0xc70   rtnetlink_rcv_msg+0x66f/0xa80   netlink_rcv_skb+0x12c/0x360   netlink_unicast+0x551/0x770   netlink_sendmsg+0x72d/0xbd0   __sock_sendmsg+0xc5/0x190   ____sys_sendmsg+0x52e/0x6a0   ___sys_sendmsg+0xeb/0x170   __sys_sendmsg+0xb5/0x140   do_syscall_64+0x4c/0x100   entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2024-50261)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vsock/virtio: Initialization of the dangling pointer occurring in vsk-\u0026gt;trans  During loopback communication, a dangling pointer can be created in vsk-\u0026gt;trans, potentially leading to a Use-After-Free condition.  This issue is resolved by initializing vsk-\u0026gt;trans to NULL.(CVE-2024-50264)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  dm cache: fix potential out-of-bounds access on the first resume  Out-of-bounds access occurs if the fast device is expanded unexpectedly before the first-time resume of the cache table. This happens because expanding the fast device requires reloading the cache table for cache_create to allocate new in-core data structures that fit the new size, and the check in cache_preresume is not performed during the first resume, leading to the issue.  Reproduce steps:  1. prepare component devices:  dmsetup create cmeta --table \u0026quot;0 8192 linear /dev/sdc 0\u0026quot; dmsetup create cdata --table \u0026quot;0 65536 linear /dev/sdc 8192\u0026quot; dmsetup create corig --table \u0026quot;0 524288 linear /dev/sdc 262144\u0026quot; dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct  2. load a cache table of 512 cache blocks, and deliberately expand the    fast device before resuming the cache, making the in-core data    structures inadequate.  dmsetup create cache --notable dmsetup reload cache --table \u0026quot;0 524288 cache /dev/mapper/cmeta \\ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\u0026quot; dmsetup reload cdata --table \u0026quot;0 131072 linear /dev/sdc 8192\u0026quot; dmsetup resume cdata dmsetup resume cache  3. suspend the cache to write out the in-core dirty bitset and hint    array, leading to out-of-bounds access to the dirty bitset at offset    0x40:  dmsetup suspend cache  KASAN reports:    BUG: KASAN: vmalloc-out-of-bounds in is_dirty_callback+0x2b/0x80   Read of size 8 at addr ffffc90000085040 by task dmsetup/90    (...snip...)   The buggy address belongs to the virtual mapping at    [ffffc90000085000, ffffc90000087000) created by:    cache_ctr+0x176a/0x35f0    (...snip...)   Memory state around the buggy address:    ffffc90000084f00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8    ffffc90000084f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8   \u0026gt;ffffc90000085000: 00 00 00 00 00 00 00 00 f8 f8 f8 f8 f8 f8 f8 f8                                              ^    ffffc90000085080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8    ffffc90000085100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8  Fix by checking the size change on the first resume.(CVE-2024-50278)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: add missing size check in amdgpu_debugfs_gprwave_read()  Avoid a possible buffer overflow if size is larger than 4K.  (cherry picked from commit f5d873f5825b40d886d03bd2aede91d4cf002434)(CVE-2024-50282)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ksmbd: check outstanding simultaneous SMB operations  If Client send simultaneous SMB operations to ksmbd, It exhausts too much memory through the \u0026quot;ksmbd_work_cache”. It will cause OOM issue. ksmbd has a credit mechanism but it can\u0026apos;t handle this problem. This patch add the check if it exceeds max credits to prevent this problem by assuming that one smb request consumes at least one credit.(CVE-2024-50285)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix slab-use-after-free in ksmbd_smb2_session_create  There is a race condition between ksmbd_smb2_session_create and ksmbd_expire_session. This patch add missing sessions_table_lock while adding/deleting session from global session table.(CVE-2024-50286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  regulator: rtq2208: Fix uninitialized use of regulator_config  Fix rtq2208 driver uninitialized use to cause kernel error.(CVE-2024-50300)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_init_flow()  There are code paths from which the function is called without holding the RCU read lock, resulting in a suspicious RCU usage warning [1].  Fix by using l3mdev_master_upper_ifindex_by_index() which will acquire the RCU read lock before calling l3mdev_master_upper_ifindex_by_index_rcu().  [1] WARNING: suspicious RCU usage 6.12.0-rc3-custom-gac8f72681cf2 #141 Not tainted ----------------------------- net/core/dev.c:876 RCU-list traversed in non-reader section!!  other info that might help us debug this:  rcu_scheduler_active = 2, debug_locks = 1 1 lock held by ip/361:  #0: ffffffff86fc7cb0 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x377/0xf60  stack backtrace: CPU: 3 UID: 0 PID: 361 Comm: ip Not tainted 6.12.0-rc3-custom-gac8f72681cf2 #141 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0xba/0x110  lockdep_rcu_suspicious.cold+0x4f/0xd6  dev_get_by_index_rcu+0x1d3/0x210  l3mdev_master_upper_ifindex_by_index_rcu+0x2b/0xf0  ip_tunnel_bind_dev+0x72f/0xa00  ip_tunnel_newlink+0x368/0x7a0  ipgre_newlink+0x14c/0x170  __rtnl_newlink+0x1173/0x19c0  rtnl_newlink+0x6c/0xa0  rtnetlink_rcv_msg+0x3cc/0xf60  netlink_rcv_skb+0x171/0x450  netlink_unicast+0x539/0x7f0  netlink_sendmsg+0x8c1/0xd80  ____sys_sendmsg+0x8f9/0xc20  ___sys_sendmsg+0x197/0x1e0  __sys_sendmsg+0x122/0x1f0  do_syscall_64+0xbb/0x1d0  entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-53042)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: iwlwifi: mvm: Fix response handling in iwl_mvm_send_recovery_cmd()  1. The size of the response packet is not validated. 2. The response buffer is not freed.  Resolve these issues by switching to iwl_mvm_send_cmd_status(), which handles both size validation and frees the buffer.(CVE-2024-53059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: prevent NULL pointer dereference if ATIF is not supported  acpi_evaluate_object() may return AE_NOT_FOUND (failure), which would result in dereferencing buffer.pointer (obj) while being NULL.  Although this case may be unrealistic for the current code, it is still better to protect against possible bugs.  Bail out also when status is AE_NOT_FOUND.  This fixes 1 FORWARD_NULL issue reported by Coverity Report: CID 1600951:  Null pointer dereferences  (FORWARD_NULL)  (cherry picked from commit 91c9e221fe2553edf2db71627d8453f083de87a1)(CVE-2024-53060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Never decrement pending_async_copies on error  The error flow in nfsd4_copy() calls cleanup_async_copy(), which already decrements nn-\u0026gt;pending_async_copies.(CVE-2024-53073)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  afs: Fix lock recursion  afs_wake_up_async_call() can incur lock recursion.  The problem is that it is called from AF_RXRPC whilst holding the -\u0026gt;notify_lock, but it tries to take a ref on the afs_call struct in order to pass it to a work queue - but if the afs_call is already queued, we then have an extraneous ref that must be put... calling afs_put_call() may call back down into AF_RXRPC through rxrpc_kernel_shutdown_call(), however, which might try taking the -\u0026gt;notify_lock again.  This case isn\u0026apos;t very common, however, so defer it to a workqueue.  The oops looks something like:    BUG: spinlock recursion on CPU#0, krxrpcio/7001/1646    lock: 0xffff888141399b30, .magic: dead4ead, .owner: krxrpcio/7001/1646, .owner_cpu: 0   CPU: 0 UID: 0 PID: 1646 Comm: krxrpcio/7001 Not tainted 6.12.0-rc2-build3+ #4351   Hardware name: ASUS All Series/H97-PLUS, BIOS 2306 10/09/2014   Call Trace:    \u0026lt;TASK\u0026gt;    dump_stack_lvl+0x47/0x70    do_raw_spin_lock+0x3c/0x90    rxrpc_kernel_shutdown_call+0x83/0xb0    afs_put_call+0xd7/0x180    rxrpc_notify_socket+0xa0/0x190    rxrpc_input_split_jumbo+0x198/0x1d0    rxrpc_input_data+0x14b/0x1e0    ? rxrpc_input_call_packet+0xc2/0x1f0    rxrpc_input_call_event+0xad/0x6b0    rxrpc_input_packet_on_conn+0x1e1/0x210    rxrpc_input_packet+0x3f2/0x4d0    rxrpc_io_thread+0x243/0x410    ? __pfx_rxrpc_io_thread+0x10/0x10    kthread+0xcf/0xe0    ? __pfx_kthread+0x10/0x10    ret_from_fork+0x24/0x40    ? __pfx_kthread+0x10/0x10    ret_from_fork_asm+0x1a/0x30    \u0026lt;/TASK\u0026gt;(CVE-2024-53090)","status":"published","published":"2024-12-06T11:08:00Z","modified":"2026-08-18T01:18:42.676431453Z","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":"RHSA-2024:10941","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-12-12T10:02:21Z","modified":"2026-09-13T10:01:54Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:12.787505Z"},{"id":"RHSA-2024:7000","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-10-02T05:07:40Z","modified":"2026-10-17T10:04:01Z","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:53:14.610978Z"},{"id":"RLSA-2024:7000","title":"Important: kernel security update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41023  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41064  CVE-2024-41065  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42094  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42225  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43830  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2025-05-07T19:11:34.309952Z","modified":"2025-05-07T19:38:05.008508Z","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:53:24.923365Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2024-45026","title":"CVE-2024-45026 in linux - Patched by Root","description":"Root has patched CVE-2024-45026 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:15:20.212502961Z","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:53:29.077857Z"},{"id":"UBUNTU-CVE-2024-45026","description":"In the Linux kernel, the following vulnerability has been resolved: s390/dasd: fix error recovery leading to data corruption on ESE devices Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing. The dasd_ese_needs_format function checks for error codes that signal the non existence of a proper track format. The check for incorrect length is to imprecise since other error cases leading to transport of insufficient data also have this flag set. This might lead to data corruption in certain error cases for example during a storage server warmstart. Fix by removing the check for incorrect length and replacing by explicitly checking for invalid track format in transport mode. Also remove the check for file protected since this is not a valid ESE handling case.","status":"published","published":"2024-09-11T16:15:00Z","modified":"2026-11-11T09:38:28.926597466Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"},{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-11T10:00:09.541251Z"},{"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: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: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: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: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:4081-1","title":"Security update for the Linux Kernel","description":"The 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-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48967: NFC: nci: Bounds check struct nfc_target arrays (bsc#1232304).\n- CVE-2022-48988: memcg: Fix possible use-after-free in memcg_write_event_control() (bsc#1232069).\n- CVE-2022-48991: mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma (bsc#1232070).\n- CVE-2022-49003: nvme: fix SRCU protection of nvme_ns_head list (bsc#1232136).\n- CVE-2022-49014: net: tun: Fix use-after-free in tun_detach() (bsc#1231890).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2022-49023: wifi: cfg80211: fix buffer overflow in elem comparison (bsc#1231961).\n- CVE-2022-49025: net/mlx5e: Fix use-after-free when reverting termination table (bsc#1231960).\n- CVE-2024-36971: Fixed __dst_negative_advice() race (bsc#1226145).\n- CVE-2024-45016: netem: fix return value if duplicate enqueue fails (bsc#1230429).\n- CVE-2024-45026: s390/dasd: fix error recovery leading to data corruption on ESE devices (bsc#1230454).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46814: drm/amd/display: Check msg_id before processing transcation (bsc#1231193).\n- CVE-2024-46815: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets (bsc#1231195).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46817: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (bsc#1231200).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46849: ASoC: meson: axg-card: fix 'use-after-free' (bsc#1231073).\n- CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (bsc#1231502).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition (bsc#1232145).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49969: drm/amd/display: Fix index out of bounds in DCN30 color transformation (bsc#1232519).\n- CVE-2024-49974: NFSD: Force all NFSv4.2 COPY requests to be synchronous (bsc#1232383).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n\nThe following non-security bugs were fixed:\n\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- kernel-binary: vdso: Own module_dir\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- mkspec-dtb: add toplevel symlinks also on arm\n- net: mana: Fix the extra HZ in mana_hwc_send_request (bsc#1232033).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n","status":"published","published":"2024-11-27T14:22:35Z","modified":"2026-02-04T04:27:53.063098Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4082-1","title":"Security update for the Linux Kernel","description":"The 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-48879: efi: fix NULL-deref in init error path (bsc#1229556).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48959: net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions() (bsc#1231976).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48991: mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma (bsc#1232070).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45016: netem: fix return value if duplicate enqueue fails (bsc#1230429).\n- CVE-2024-45026: s390/dasd: fix error recovery leading to data corruption on ESE devices (bsc#1230454).\n- CVE-2024-46716: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (bsc#1230715).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46814: drm/amd/display: Check msg_id before processing transcation (bsc#1231193).\n- CVE-2024-46815: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets (bsc#1231195).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46817: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (bsc#1231200).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46849: ASoC: meson: axg-card: fix 'use-after-free' (bsc#1231073).\n- CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (bsc#1231502).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition (bsc#1232145).\n- CVE-2024-47748: vhost_vdpa: assign irq bypass producer token correctly (bsc#1232174).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49930: wifi: ath11k: fix array out-of-bound access in SoC stats (bsc#1232260).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49960: ext4: fix timer use-after-free on failed mount (bsc#1232395).\n- CVE-2024-49969: drm/amd/display: Fix index out of bounds in DCN30 color transformation (bsc#1232519).\n- CVE-2024-49974: NFSD: Force all NFSv4.2 COPY requests to be synchronous (bsc#1232383).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n\nThe following non-security bugs were fixed:\n\n- NFSv3: only use NFS timeout for MOUNT when protocols are compatible (bsc#1231016).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/mana_ib: use the correct page size for mapping user-mode doorbell page (bsc#1232036).\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- dn_route: set rt neigh to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- ipv6: blackhole_netdev needs snmp6 counters (bsc#1216813).\n- ipv6: give an IPv6 dev to blackhole_netdev (bsc#1216813).\n- net: mana: Fix the extra HZ in mana_hwc_send_request (bsc#1232033).\n- xfrm: set dst dev to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n","status":"published","published":"2024-11-27T14:23:31Z","modified":"2026-02-04T03:02:23.859809Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4131-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-49925: fbdev: efifb: Register sysfs groups through driver core (bsc#1232224)\n- CVE-2024-49945: net/ncsi: Disable the ncsi work before freeing the associated structure (bsc#1232165).\n- CVE-2024-50208: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages (bsc#1233117).\n- CVE-2022-48879: efi: fix NULL-deref in init error path (bsc#1229556).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48959: net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions() (bsc#1231976).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48991: mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma (bsc#1232070).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45016: netem: fix return value if duplicate enqueue fails (bsc#1230429).\n- CVE-2024-45026: s390/dasd: fix error recovery leading to data corruption on ESE devices (bsc#1230454).\n- CVE-2024-46716: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (bsc#1230715).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46814: drm/amd/display: Check msg_id before processing transcation (bsc#1231193).\n- CVE-2024-46815: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets (bsc#1231195).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46817: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (bsc#1231200).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46849: ASoC: meson: axg-card: fix 'use-after-free' (bsc#1231073).\n- CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (bsc#1231502).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition (bsc#1232145).\n- CVE-2024-47748: vhost_vdpa: assign irq bypass producer token correctly (bsc#1232174).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49930: wifi: ath11k: fix array out-of-bound access in SoC stats (bsc#1232260).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49960: ext4: fix timer use-after-free on failed mount (bsc#1232395).\n- CVE-2024-49969: drm/amd/display: Fix index out of bounds in DCN30 color transformation (bsc#1232519).\n- CVE-2024-49974: NFSD: Force all NFSv4.2 COPY requests to be synchronous (bsc#1232383).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n\nThe following non-security bugs were fixed:\n\n- NFSv3: only use NFS timeout for MOUNT when protocols are compatible (bsc#1231016).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/mana_ib: use the correct page size for mapping user-mode doorbell page (bsc#1232036).\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- dn_route: set rt neigh to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- initramfs: avoid filename buffer overrun (bsc#1232436).\n- ipv6: blackhole_netdev needs snmp6 counters (bsc#1216813).\n- ipv6: give an IPv6 dev to blackhole_netdev (bsc#1216813).\n- net: mana: Fix the extra HZ in mana_hwc_send_request (bsc#1232033).\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- xfrm: set dst dev to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n","status":"published","published":"2024-12-02T10:00:24Z","modified":"2026-02-04T03:53:31.97673Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2024:4140-1","title":"Security update for the Linux Kernel","description":"The 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-47589: igbvf: fix double free in `igbvf_probe` (bsc#1226557).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48967: NFC: nci: Bounds check struct nfc_target arrays (bsc#1232304).\n- CVE-2022-48988: memcg: Fix possible use-after-free in memcg_write_event_control() (bsc#1232069).\n- CVE-2022-48991: khugepaged: retract_page_tables() remember to test exit (bsc#1232070 prerequisity).\n- CVE-2022-49003: nvme: fix SRCU protection of nvme_ns_head list (bsc#1232136).\n- CVE-2022-49014: net: tun: Fix use-after-free in tun_detach() (bsc#1231890).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2022-49023: wifi: cfg80211: fix buffer overflow in elem comparison (bsc#1231961).\n- CVE-2022-49025: net/mlx5e: Fix use-after-free when reverting termination table (bsc#1231960).\n- CVE-2024-45016: netem: fix return value if duplicate enqueue fails (bsc#1230429).\n- CVE-2024-45026: s390/dasd: fix error recovery leading to data corruption on ESE devices (bsc#1230454).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46814: drm/amd/display: Check msg_id before processing transcation (bsc#1231193).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46817: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (bsc#1231200).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46849: ASoC: meson: axg-card: fix 'use-after-free' (bsc#1231073).\n- CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (bsc#1231502).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition (bsc#1232145).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49969: drm/amd/display: Fix index out of bounds in DCN30 color transformation (bsc#1232519).\n- CVE-2024-49974: NFSD: Force all NFSv4.2 COPY requests to be synchronous (bsc#1232383).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n\nThe following non-security bugs were fixed:\n\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- kernel-binary: vdso: Own module_dir\n- mkspec-dtb: add toplevel symlinks also on arm\n- net: mana: Fix the extra HZ in mana_hwc_send_request (bsc#1232033).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n","status":"published","published":"2024-12-02T14:37:24Z","modified":"2026-02-04T03:54:12.712342Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"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-7194-1","title":"linux-azure-5.15 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\nIt 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  - ARM32 architecture;\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  - ACPI drivers;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Null block device driver;\n  - TPM device driver;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Buffer Sharing and Synchronization framework;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\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  - Mailbox framework;\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  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - Virtio pmem driver;\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  - 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  - Userspace I/O drivers;\n  - USB Device Class drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Type-C Port Controller Manager driver;\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  - 9P distributed file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\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  - Bitmap API;\n  - Network file system (NFS) superblock;\n  - Objagg library;\n  - Perf events;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Kernel thread helper (kthread);\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Static call mechanism;\n  - Tracing infrastructure;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - Memory management;\n  - Amateur Radio drivers;\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  - Netlink;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\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  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2024-41091, CVE-2024-46800, CVE-2024-49924, CVE-2024-47659,\nCVE-2024-42295, CVE-2024-42284, CVE-2024-38577, CVE-2024-49902,\nCVE-2024-45011, CVE-2024-47673, CVE-2024-38538, CVE-2024-45008,\nCVE-2024-47667, CVE-2024-46832, CVE-2024-43879, CVE-2024-41059,\nCVE-2024-43853, CVE-2024-44940, CVE-2024-44947, CVE-2024-43828,\nCVE-2024-41090, CVE-2024-44944, CVE-2024-43834, CVE-2024-46777,\nCVE-2024-46689, CVE-2024-35965, CVE-2024-42276, CVE-2024-50264,\nCVE-2024-44965, CVE-2024-49977, CVE-2024-42079, CVE-2024-46744,\nCVE-2024-42299, CVE-2024-43909, CVE-2024-41098, CVE-2024-46731,\nCVE-2024-44946, CVE-2024-50024, CVE-2024-49858, CVE-2024-49892,\nCVE-2024-44989, CVE-2024-47663, CVE-2024-49983, CVE-2024-42286,\nCVE-2024-42310, CVE-2024-44974, CVE-2024-43892, CVE-2024-46840,\nCVE-2024-47695, CVE-2024-46780, CVE-2024-46757, CVE-2024-46707,\nCVE-2024-49894, CVE-2024-50007, CVE-2024-47705, CVE-2024-49890,\nCVE-2024-46815, CVE-2024-36968, CVE-2024-40915, CVE-2024-44995,\nCVE-2024-49871, CVE-2024-42265, CVE-2024-42283, CVE-2024-50000,\nCVE-2024-42309, CVE-2024-47748, CVE-2024-35967, CVE-2023-52904,\nCVE-2024-46745, CVE-2024-41016, CVE-2024-49868, CVE-2024-41011,\nCVE-2024-50186, CVE-2024-50033, CVE-2024-38545, CVE-2024-42267,\nCVE-2024-46852, CVE-2024-44987, CVE-2024-46783, CVE-2024-47671,\nCVE-2024-46721, CVE-2024-46853, CVE-2024-43914, CVE-2024-43907,\nCVE-2024-47734, CVE-2024-36484, CVE-2024-46781, CVE-2024-47693,\nCVE-2024-46791, CVE-2024-49913, CVE-2024-49900, CVE-2024-50191,\nCVE-2024-43860, CVE-2024-45018, CVE-2024-46854, CVE-2024-42246,\nCVE-2024-42156, CVE-2024-47660, CVE-2024-49878, CVE-2024-44982,\nCVE-2024-43867, CVE-2024-49938, CVE-2024-47737, CVE-2024-46743,\nCVE-2024-42292, CVE-2024-50181, CVE-2024-41020, CVE-2024-43863,\nCVE-2024-46817, CVE-2024-42281, CVE-2023-52621, CVE-2024-47749,\nCVE-2024-46804, CVE-2024-47747, CVE-2024-50045, CVE-2024-41065,\nCVE-2023-52434, CVE-2024-50095, CVE-2024-45025, CVE-2024-50179,\nCVE-2024-49946, CVE-2024-46782, CVE-2024-43839, CVE-2024-43904,\nCVE-2024-44958, CVE-2024-44934, CVE-2024-45006, CVE-2024-49969,\nCVE-2024-44986, CVE-2024-46752, CVE-2024-35966, CVE-2024-39463,\nCVE-2024-49883, CVE-2024-46805, CVE-2024-44935, CVE-2023-52532,\nCVE-2024-41071, CVE-2024-46807, CVE-2024-43846, CVE-2024-50015,\nCVE-2024-26661, CVE-2024-43841, CVE-2024-46819, CVE-2024-44931,\nCVE-2024-53057, CVE-2024-49982, CVE-2023-52757, CVE-2024-47735,\nCVE-2024-49866, CVE-2024-46763, CVE-2024-45021, CVE-2024-46814,\nCVE-2024-46673, CVE-2024-43873, CVE-2024-49997, CVE-2024-38602,\nCVE-2024-46795, CVE-2024-26822, CVE-2024-47670, CVE-2024-46755,\nCVE-2024-43902, CVE-2024-46859, CVE-2024-43883, CVE-2024-49966,\nCVE-2024-42305, CVE-2024-49959, CVE-2024-42280, CVE-2024-49965,\nCVE-2024-47674, CVE-2024-46723, CVE-2024-50031, CVE-2024-50184,\nCVE-2024-36893, CVE-2024-43875, CVE-2023-52918, CVE-2024-49867,\nCVE-2024-49981, CVE-2024-43861, CVE-2024-49895, CVE-2024-26669,\nCVE-2024-38544, CVE-2024-49973, CVE-2024-41015, CVE-2024-42296,\nCVE-2024-46722, CVE-2024-42158, CVE-2024-49881, CVE-2024-27072,\nCVE-2024-47739, CVE-2024-46828, CVE-2024-46724, CVE-2024-44999,\nCVE-2024-44971, CVE-2024-40973, CVE-2023-52572, CVE-2024-47709,\nCVE-2024-47742, CVE-2024-46818, CVE-2024-50035, CVE-2024-50188,\nCVE-2024-47679, CVE-2024-38667, CVE-2024-41078, CVE-2024-46844,\nCVE-2024-47672, CVE-2024-42306, CVE-2024-46758, CVE-2024-43869,\nCVE-2024-50062, CVE-2024-49875, CVE-2024-41017, CVE-2024-41077,\nCVE-2024-50038, CVE-2024-50013, CVE-2024-46746, CVE-2024-49962,\nCVE-2024-50049, CVE-2023-52751, CVE-2024-47684, CVE-2024-47701,\nCVE-2024-41070, CVE-2024-44942, CVE-2024-35904, CVE-2024-26607,\nCVE-2024-50019, CVE-2024-46714, CVE-2024-46738, CVE-2024-42312,\nCVE-2024-44948, CVE-2024-43890, CVE-2024-43893, CVE-2024-26800,\nCVE-2024-35963, CVE-2024-49884, CVE-2024-49930, CVE-2024-46829,\nCVE-2024-50046, CVE-2024-49985, CVE-2024-41022, CVE-2024-43894,\nCVE-2024-43830, CVE-2024-45009, CVE-2024-35951, CVE-2024-49889,\nCVE-2024-42301, CVE-2024-38632, CVE-2024-42114, CVE-2024-42290,\nCVE-2024-43858, CVE-2024-50002, CVE-2024-41060, CVE-2024-47696,\nCVE-2024-43870, CVE-2024-49948, CVE-2024-46759, CVE-2024-26947,\nCVE-2024-46713, CVE-2024-47740, CVE-2024-44960, CVE-2024-46756,\nCVE-2024-46737, CVE-2024-41068, CVE-2024-46677, CVE-2024-41063,\nCVE-2024-41019, CVE-2023-52917, CVE-2024-38611, CVE-2024-49852,\nCVE-2024-49863, CVE-2024-46739, CVE-2024-43908, CVE-2024-47697,\nCVE-2024-46810, CVE-2024-41072, CVE-2024-42302, CVE-2024-50003,\nCVE-2024-45026, CVE-2024-45028, CVE-2024-42259, CVE-2022-48666,\nCVE-2024-49995, CVE-2024-50093, CVE-2024-46865, CVE-2024-49886,\nCVE-2024-43889, CVE-2024-42285, CVE-2024-50006, CVE-2024-42271,\nCVE-2024-42274, CVE-2024-49957, CVE-2024-42289, CVE-2024-46719,\nCVE-2024-46858, CVE-2024-49958, CVE-2024-50041, CVE-2024-46675,\nCVE-2024-41064, CVE-2024-39472, CVE-2024-42287, CVE-2024-46822,\nCVE-2024-49877, CVE-2024-43849, CVE-2024-50040, CVE-2024-49879,\nCVE-2024-46798, CVE-2024-46855, CVE-2024-49944, CVE-2024-46676,\nCVE-2024-26893, CVE-2024-43835, CVE-2024-47665, CVE-2024-47669,\nCVE-2024-43882, CVE-2024-46740, CVE-2024-49851, CVE-2024-46849,\nCVE-2024-42311, CVE-2024-44985, CVE-2024-47757, CVE-2024-50001,\nCVE-2024-46750, CVE-2024-47706, CVE-2024-50039, CVE-2024-46702,\nCVE-2024-46725, CVE-2024-43817, CVE-2024-49907, CVE-2024-46695,\nCVE-2024-38553, CVE-2024-42272, CVE-2024-49882, CVE-2024-42269,\nCVE-2024-44954, CVE-2024-42318, CVE-2024-42297, CVE-2024-49975,\nCVE-2024-44988, CVE-2024-49963, CVE-2024-47692, CVE-2024-41042,\nCVE-2024-41081, CVE-2024-43854, CVE-2024-46771, CVE-2024-46732,\nCVE-2024-47712, CVE-2024-47699, CVE-2024-49927, CVE-2024-49860,\nCVE-2024-45003, CVE-2024-49954, CVE-2024-42304, CVE-2024-49933,\nCVE-2024-42277, CVE-2024-49955, CVE-2024-47710, CVE-2024-43905,\nCVE-2024-49903, CVE-2024-43856, CVE-2024-50180, CVE-2024-44966,\nCVE-2024-46685, CVE-2024-49935, CVE-2024-44990, CVE-2023-52889,\nCVE-2024-49896, CVE-2024-44969, CVE-2024-50189, CVE-2024-50008,\nCVE-2024-47720, CVE-2024-42313, CVE-2024-44983, CVE-2024-49949,\nCVE-2024-46761, CVE-2024-47690, CVE-2024-50059, CVE-2024-41073,\nCVE-2024-47723, CVE-2024-46747, CVE-2024-49952, CVE-2024-50096,\nCVE-2024-42288, CVE-2024-43871, CVE-2024-42126, CVE-2024-44998,\nCVE-2024-47685, CVE-2024-46679, CVE-2024-43884, CVE-2024-47668,\nCVE-2024-49936, CVE-2024-43829, CVE-2024-47756, CVE-2024-43880,\nCVE-2024-45007, CVE-2024-40910, CVE-2024-50044, CVE-2023-52639,\nCVE-2024-47698, CVE-2024-41012, CVE-2024-49856, CVE-2024-47713,\nCVE-2024-47718, CVE-2024-49967)\n","status":"published","published":"2025-01-09T11:58:43Z","modified":"2026-10-29T20:02:44.581678587Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7196-1","title":"linux-azure, linux-azure-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-44979, CVE-2024-47658, CVE-2024-44970, CVE-2024-43913,\nCVE-2024-46816, CVE-2024-46738, CVE-2024-46777, CVE-2024-46730,\nCVE-2024-46811, CVE-2024-44954, CVE-2024-42317, CVE-2024-42279,\nCVE-2024-45002, CVE-2024-43826, CVE-2024-44967, CVE-2024-46721,\nCVE-2024-46763, CVE-2024-43856, CVE-2024-42284, CVE-2024-42289,\nCVE-2024-46806, CVE-2024-46776, CVE-2024-43843, CVE-2024-42298,\nCVE-2024-43832, CVE-2024-42321, CVE-2024-42292, CVE-2024-44982,\nCVE-2024-43842, CVE-2024-46772, CVE-2024-46702, CVE-2024-45017,\nCVE-2024-43888, CVE-2024-47683, CVE-2024-46714, CVE-2024-43899,\nCVE-2024-45025, CVE-2024-46751, CVE-2024-45020, CVE-2024-44977,\nCVE-2024-46853, CVE-2024-46753, CVE-2024-46792, CVE-2024-46675,\nCVE-2024-46805, CVE-2024-43890, CVE-2024-46703, CVE-2024-43841,\nCVE-2024-44960, CVE-2024-46846, CVE-2024-46798, CVE-2024-44965,\nCVE-2024-46812, CVE-2024-43835, CVE-2024-43839, CVE-2024-43886,\nCVE-2024-46843, CVE-2024-50264, CVE-2024-46706, CVE-2024-46851,\nCVE-2024-46758, CVE-2024-45027, CVE-2024-43887, CVE-2024-42278,\nCVE-2024-46701, CVE-2024-46708, CVE-2024-46817, CVE-2024-46871,\nCVE-2024-46771, CVE-2024-42304, CVE-2024-43877, CVE-2024-44996,\nCVE-2024-46741, CVE-2024-46842, CVE-2024-43902, CVE-2024-43818,\nCVE-2024-47662, CVE-2024-44931, CVE-2024-46793, CVE-2024-46746,\nCVE-2024-46782, CVE-2024-43914, CVE-2024-43824, CVE-2024-46767,\nCVE-2024-43871, CVE-2024-44971, CVE-2024-47666, CVE-2024-45008,\nCVE-2024-42263, CVE-2024-46815, CVE-2024-46824, CVE-2024-45015,\nCVE-2024-45000, CVE-2024-46841, CVE-2024-46770, CVE-2024-44942,\nCVE-2024-46679, CVE-2024-46724, CVE-2024-46759, CVE-2024-43845,\nCVE-2024-46795, CVE-2024-46818, CVE-2024-44988, CVE-2024-46807,\nCVE-2024-46787, CVE-2024-43894, CVE-2024-46803, CVE-2024-44947,\nCVE-2024-46786, CVE-2024-46689, CVE-2024-46686, CVE-2024-42290,\nCVE-2024-46868, CVE-2024-43857, CVE-2024-43909, CVE-2023-52889,\nCVE-2024-44944, CVE-2024-44973, CVE-2024-43905, CVE-2024-44938,\nCVE-2024-43864, CVE-2024-46850, CVE-2024-43867, CVE-2024-43819,\nCVE-2024-46691, CVE-2024-47664, CVE-2024-46821, CVE-2024-46867,\nCVE-2024-46716, CVE-2024-43881, CVE-2024-46788, CVE-2024-43912,\nCVE-2024-43904, CVE-2024-46727, CVE-2024-46680, CVE-2024-44985,\nCVE-2024-46813, CVE-2024-47668, CVE-2024-42277, CVE-2024-42291,\nCVE-2024-45003, CVE-2024-42309, CVE-2024-44937, CVE-2024-44953,\nCVE-2024-46718, CVE-2024-42276, CVE-2024-45028, CVE-2024-43863,\nCVE-2024-46866, CVE-2024-42258, CVE-2024-42273, CVE-2024-46717,\nCVE-2024-46797, CVE-2024-46854, CVE-2024-44972, CVE-2024-46791,\nCVE-2024-45010, CVE-2024-43825, CVE-2024-46775, CVE-2024-46745,\nCVE-2024-46808, CVE-2024-46831, CVE-2024-45018, CVE-2024-42319,\nCVE-2024-46822, CVE-2024-43883, CVE-2024-46722, CVE-2024-46694,\nCVE-2024-45009, CVE-2024-42320, CVE-2024-46825, CVE-2024-43821,\nCVE-2024-46749, CVE-2024-45006, CVE-2024-43895, CVE-2024-44950,\nCVE-2024-43827, CVE-2024-43876, CVE-2024-47659, CVE-2024-44989,\nCVE-2024-46804, CVE-2024-46754, CVE-2024-46766, CVE-2024-46728,\nCVE-2024-46828, CVE-2024-46826, CVE-2024-46810, CVE-2024-44963,\nCVE-2024-44934, CVE-2024-43829, CVE-2024-42268, CVE-2024-43850,\nCVE-2024-43853, CVE-2024-43854, CVE-2024-43892, CVE-2024-43859,\nCVE-2024-42285, CVE-2024-44962, CVE-2024-46725, CVE-2024-46814,\nCVE-2024-44935, CVE-2024-42264, CVE-2024-42260, CVE-2024-46858,\nCVE-2024-46778, CVE-2024-46774, CVE-2024-46848, CVE-2024-45013,\nCVE-2024-43837, CVE-2024-46683, CVE-2024-46757, CVE-2024-46726,\nCVE-2024-43831, CVE-2024-46737, CVE-2024-43893, CVE-2024-46823,\nCVE-2024-42302, CVE-2024-44990, CVE-2024-46755, CVE-2024-46707,\nCVE-2024-43833, CVE-2024-44940, CVE-2024-42259, CVE-2024-46855,\nCVE-2024-46827, CVE-2024-46809, CVE-2024-46836, CVE-2024-43907,\nCVE-2024-42312, CVE-2024-46692, CVE-2024-42297, CVE-2024-46864,\nCVE-2024-42299, CVE-2024-45011, CVE-2024-46838, CVE-2024-44993,\nCVE-2024-46802, CVE-2024-44966, CVE-2024-46739, CVE-2024-46780,\nCVE-2024-44961, CVE-2024-42316, CVE-2024-47660, CVE-2024-46859,\nCVE-2024-46762, CVE-2024-43861, CVE-2024-45012, CVE-2024-46784,\nCVE-2024-43908, CVE-2024-46832, CVE-2024-44969, CVE-2024-46750,\nCVE-2024-44958, CVE-2024-46740, CVE-2024-46829, CVE-2024-43873,\nCVE-2024-49984, CVE-2024-44983, CVE-2024-42288, CVE-2024-46735,\nCVE-2024-46676, CVE-2024-43823, CVE-2024-46779, CVE-2024-46744,\nCVE-2024-42310, CVE-2024-44980, CVE-2024-46870, CVE-2024-42307,\nCVE-2024-46768, CVE-2024-44984, CVE-2024-45007, CVE-2024-46710,\nCVE-2024-44978, CVE-2024-46723, CVE-2024-46845, CVE-2024-44999,\nCVE-2024-42311, CVE-2024-43884, CVE-2024-44939, CVE-2024-44974,\nCVE-2024-42314, CVE-2024-42318, CVE-2024-39472, CVE-2024-46693,\nCVE-2024-46794, CVE-2024-46844, CVE-2024-46695, CVE-2024-46720,\nCVE-2024-46860, CVE-2024-46835, CVE-2024-47665, CVE-2024-46715,\nCVE-2024-42305, CVE-2024-46773, CVE-2024-45030, CVE-2024-46697,\nCVE-2024-46705, CVE-2024-42286, CVE-2024-46834, CVE-2024-46681,\nCVE-2024-53057, CVE-2024-42303, CVE-2024-46678, CVE-2024-46756,\nCVE-2023-52918, CVE-2024-43860, CVE-2024-43911, CVE-2024-43880,\nCVE-2024-43910, CVE-2024-44975, CVE-2024-44959, CVE-2024-46747,\nCVE-2024-43846, CVE-2024-42274, CVE-2024-46672, CVE-2024-43852,\nCVE-2024-46709, CVE-2024-42306, CVE-2024-42281, CVE-2024-46849,\nCVE-2024-46719, CVE-2024-43830, CVE-2024-46685, CVE-2024-44998,\nCVE-2024-42313, CVE-2024-43820, CVE-2024-44991, CVE-2024-47674,\nCVE-2024-46785, CVE-2024-45021, CVE-2024-46677, CVE-2024-43870,\nCVE-2024-46698, CVE-2024-43900, CVE-2024-44956, CVE-2024-43849,\nCVE-2024-46687, CVE-2024-42296, CVE-2024-46830, CVE-2024-47669,\nCVE-2024-46732, CVE-2024-46733, CVE-2024-46852, CVE-2024-43906,\nCVE-2024-43847, CVE-2024-42294, CVE-2024-46731, CVE-2024-45029,\nCVE-2024-47667, CVE-2024-42272, CVE-2024-45022, CVE-2024-43879,\nCVE-2024-46765, CVE-2024-45026, CVE-2024-44986, CVE-2024-44995,\nCVE-2024-47663, CVE-2024-42262, CVE-2024-43889, CVE-2024-44987,\nCVE-2024-43866, CVE-2024-42265, CVE-2024-46847, CVE-2024-46673,\nCVE-2024-46783, CVE-2024-46761, CVE-2024-46840, CVE-2024-42301,\nCVE-2024-43868, CVE-2024-45005, CVE-2024-42322, CVE-2024-43828,\nCVE-2024-43834, CVE-2024-43891, CVE-2024-46861, CVE-2024-42261,\nCVE-2024-43875, CVE-2024-43840, CVE-2024-42287, CVE-2024-46752,\nCVE-2024-46711, CVE-2024-46713, CVE-2024-44943, CVE-2024-46743,\nCVE-2024-43869, CVE-2024-46781, CVE-2024-44946, CVE-2024-42283,\nCVE-2024-47661, CVE-2024-43817, CVE-2024-46819, CVE-2024-42267,\nCVE-2024-46729, CVE-2024-46857, CVE-2024-42295, CVE-2024-46760,\nCVE-2024-42315, CVE-2024-45019, CVE-2024-44948, CVE-2024-44941,\nCVE-2024-42269, CVE-2024-44957, CVE-2024-49967)\n","status":"published","published":"2025-01-09T12:34:21Z","modified":"2026-10-29T20:02:42.46990263Z","updated_at":"2026-11-02T16:58:18.876384Z"}]}}