{"id":"CVE-2024-46724","aliases":["AZL-49368","BELL-CVE-2024-46724","CLSA-2024-1727690025","CLSA-2024-1727690947","CLSA-2024-1727692412","CLSA-2024-1728936982","CLSA-2024-1729874131","CLSA-2026-1775655705","CLSA-2026-1787304608","DEBIAN-CVE-2024-46724","DLA-3912-1","DLA-4008-1","DSA-5782-1","EUVD-2024-41985","GHSA-gxvv-xx83-rmg6","OESA-2024-2321","OESA-2024-2322","OESA-2024-2323","OESA-2024-2324","OESA-2024-2325","RHSA-2025:6966","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:4100-1","SUSE-SU-2025:0034-1","SUSE-SU-2025:20073-1","SUSE-SU-2025:20077-1","UBUNTU-CVE-2024-46724","USN-7100-1","USN-7100-2","USN-7123-1","USN-7144-1","USN-7154-1","USN-7154-2","USN-7155-1","USN-7156-1","USN-7159-1","USN-7159-2","USN-7159-3","USN-7159-4","USN-7159-5","USN-7194-1","USN-7195-1","USN-7195-2","USN-7196-1"],"status":"published","title":"drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\n\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.00242,"percentile":0.15457,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-125"],"published":"2024-09-18T06:32:21Z","modified":"2026-11-02T12:02:49Z","fixes":[{"ecosystem":"Azure Linux:2","package":"kernel","fixed_in":["5.15.167.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.10.226","5.15.167","6.1.109","6.6.50","6.10.9"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.112-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.10.9-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.10.9-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","fixed_in":["5.4.0-1136.146~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","fixed_in":["5.4.0-1142.149~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","fixed_in":["5.4.0-1140.149~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","fixed_in":["5.4.0-202.222~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","fixed_in":["5.4.0-1083.88~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","fixed_in":["5.4.0-1135.144~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","fixed_in":["5.4.0-1120.132~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux","fixed_in":["5.4.0-202.222"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","fixed_in":["5.4.0-1136.146"],"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-1142.149"],"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-1096.103"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","fixed_in":["5.4.0-1140.149"],"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-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-1083.88"],"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-1045.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","fixed_in":["5.4.0-1124.132"],"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-1135.144"],"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-1120.132"],"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-1055.59"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","fixed_in":["5.4.0-1136.146+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","fixed_in":["5.4.0-1142.149+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","fixed_in":["5.4.0-1110.120"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","fixed_in":["5.4.0-1140.149+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":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.106-r0"},{"fixed":"6.1.110-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.100-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els20"}]}],"bundled":80},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.119.1.el7.tuxcare.els8"}]}],"bundled":5},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els4"}]}],"bundled":43},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-container","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-container-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.354.4.el7uek.tuxcare.els1"}]}],"bundled":34},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-container","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-container-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.357.2.el7uek.tuxcare.els1"}]}],"bundled":107},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.2.0"},{"fixed":"5.10.226"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.109"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.50"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.10.9"}]}]},{"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.9-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.10.9-1"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.226-1"}]}],"versions":["5.10.103-1","5.10.103-1~bpo10+1","5.10.106-1","5.10.113-1","5.10.120-1","5.10.120-1~bpo10+1","5.10.127-1","5.10.127-2","5.10.127-2~bpo10+1","5.10.136-1","5.10.140-1","5.10.148-1","5.10.149-1","5.10.149-2","5.10.158-1","5.10.158-2","5.10.162-1","5.10.178-1","5.10.178-2","5.10.178-3","5.10.179-1","5.10.179-2","5.10.179-3","5.10.179-4","5.10.179-5","5.10.191-1","5.10.197-1","5.10.205-1","5.10.205-2","5.10.209-1","5.10.209-2","5.10.216-1","5.10.218-1","5.10.221-1","5.10.223-1","5.10.46-4","5.10.46-5","5.10.70-1","5.10.70-1~bpo10+1","5.10.84-1","5.10.92-1","5.10.92-1~bpo10+1","5.10.92-2"],"bundled":147},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.119-1~deb11u1"}]}],"versions":["6.1.106-3~deb11u1","6.1.106-3~deb11u2","6.1.106-3~deb11u3","6.1.112-1~deb11u1"],"bundled":838},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.112-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"],"bundled":145},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-234.0.0.133.oe2203sp4"}]}],"bundled":62},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-234.0.0.136.oe2203sp3"}]}],"bundled":62},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2411.1.0.0301.oe2003sp4"}]}],"bundled":23},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.99.0.180.oe2203sp1"}]}],"bundled":74},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-48.0.0.53.oe2403"}]}],"bundled":62},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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 Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_62","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"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-1136.146~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","5.4.0-1135.145~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-1142.149~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","5.4.0-1140.147~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-1140.149~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","5.4.0-1139.148~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-202.222~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","5.4.0-200.220~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-1083.88~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","5.4.0-1082.87~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-1135.144~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","5.4.0-1134.143~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-1120.132~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","5.4.0-1119.131~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-202.222"}]}],"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","5.4.0-200.220"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1136.146"}]}],"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","5.4.0-1135.145"]},{"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-1142.149"}]}],"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","5.4.0-1140.147"]},{"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-1096.103"}]}],"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","5.4.0-1095.102"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.149"}]}],"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","5.4.0-1139.148"]},{"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-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-1083.88"}]}],"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","5.4.0-1082.87"]},{"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-1045.46"}]}],"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","5.4.0-1044.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1124.132"}]}],"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","5.4.0-1123.131"]},{"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-1135.144"}]}],"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","5.4.0-1134.143"]},{"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-1120.132"}]}],"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","5.4.0-1119.131"]},{"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-1055.59"}]}],"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","5.4.0-1054.58"]},{"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-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1102.106"]},{"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-1136.146+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","5.4.0-1135.145+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-1142.149+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","5.4.0-1140.147+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1110.120"}]}],"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","5.4.0-1109.119"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.149+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","5.4.0-1139.148+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: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:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.84"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83"],"bundled":226},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1"],"bundled":222},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72"],"bundled":222},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.22~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.18~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.22"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.19"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.17"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.18"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.18"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.18"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-50.51~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1"],"bundled":402},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1"],"bundled":401},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20"],"bundled":401},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.21.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1"],"bundled":401},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1002.4"}]}],"versions":["6.8.0-1001.3"],"bundled":607},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.149~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","5.4.0-1139.148~18.04.1"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-202.222~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","5.4.0-200.220~18.04.1"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1083.88~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","5.4.0-1082.87~18.04.1"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-202.222"}]}],"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","5.4.0-200.220"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.149"}]}],"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","5.4.0-1139.148"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1083.88"}]}],"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","5.4.0-1082.87"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1124.132"}]}],"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","5.4.0-1123.131"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1120.132"}]}],"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","5.4.0-1119.131"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1055.59"}]}],"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","5.4.0-1054.58"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1136.146~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","5.4.0-1135.145~18.04.1"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1136.146"}]}],"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","5.4.0-1135.145"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1135.144~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","5.4.0-1134.143~18.04.1"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1096.103"}]}],"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","5.4.0-1095.102"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1135.144"}]}],"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","5.4.0-1134.143"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1045.46"}]}],"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","5.4.0-1044.45"],"bundled":23},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1120.132~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","5.4.0-1119.131~18.04.1"],"bundled":23},{"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:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1142.149"}]}],"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","5.4.0-1140.147"],"bundled":39},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1142.149~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","5.4.0-1140.147~18.04.1"],"bundled":39},{"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/725b728cc0c8c5fafdfb51cb0937870d33a40fa4","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/45f7b02afc464c208e8f56bcbc672ef5c364c815","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/32915dc909ff502823babfe07d5416c5b6e8a8b1","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/f9267972490f9fcffe146e79828e97acc0da588c","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/db7a86676fd624768a5d907faf34ad7bb4ff25f4","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/d768394fa99467bcf2703bde74ddc96eeb0b71fa","tags":["Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html","tags":["web"]},{"url":"https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46724","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-gxvv-xx83-rmg6"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-46724","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/centos8.5-els/CLSA-2024-1727690025.html","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/centos8.4-els/CLSA-2024-1727690947.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/centos7-els/CLSA-2024-1727692412.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/almalinux9.2-esu/CLSA-2024-1728936982.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos-stream8els/CLSA-2024-1729874131.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-39189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46722","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46723","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46811","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46842","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47661","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/oraclelinux7els/CLSA-2026-1775655705.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-43945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68349","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23273","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/oraclelinux7els/CLSA-2026-1787304608.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-54518","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31504","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31657","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46300","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64266","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64564","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68480","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/46xxx/CVE-2024-46724.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-46724","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42315","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46802","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47695","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47735","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47737","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49868","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49875","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49895","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49985","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50049","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52919","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49855","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50007","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2325","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35949","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46775","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50065","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:6966","tags":["advisory"]},{"url":"https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.6_release_notes/index","tags":["article"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278283","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2280464","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281340","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281687","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281827","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281829","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281905","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281907","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281912","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281914","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282952","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282955","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282959","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284280","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2292324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293458","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297472","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297540","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298411","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300437","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301498","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307840","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307862","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307871","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307883","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307887","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307888","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307889","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307891","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309783","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309789","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309838","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309850","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309852","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309863","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311706","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311707","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311719","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2312061","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2312063","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2312108","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313053","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313054","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313055","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313056","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313091","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313093","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313095","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313098","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313102","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313104","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313106","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313107","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313109","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313131","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313134","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313135","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315156","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315157","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315158","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315171","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315172","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315187","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315191","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315205","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315216","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2317581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2317584","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2317601","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320168","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320169","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320187","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320200","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320209","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320210","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320212","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320213","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320225","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320238","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320239","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320242","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320245","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320246","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320248","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320249","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320274","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320425","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320432","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320443","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320454","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320462","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320475","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320480","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320481","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320484","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320497","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320500","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320501","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320502","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320509","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320510","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320520","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320527","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320529","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320531","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320541","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320546","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320547","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320549","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320550","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320554","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320556","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320557","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320559","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320563","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320565","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320570","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320571","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320574","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320576","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320577","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320586","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320587","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320589","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320590","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320594","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320598","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320601","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320602","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320610","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320611","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320615","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320620","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320625","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320629","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320635","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320636","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320658","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320693","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320707","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320781","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322303","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322308","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322310","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322312","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322320","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322323","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323905","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323918","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323924","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323927","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323929","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323932","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323933","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323938","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323945","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323947","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323950","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323953","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324320","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324321","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324325","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324413","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324419","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324423","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324548","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324566","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324578","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324599","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324610","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324617","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324853","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324865","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324869","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324874","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324875","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324889","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324897","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324899","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324901","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327182","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327189","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327190","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327194","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327332","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327335","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327338","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327343","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327344","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327349","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327361","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327362","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327365","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327369","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327370","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327373","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327383","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327888","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327890","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327893","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2328791","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2328792","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329818","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329919","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329927","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329928","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329929","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329930","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329935","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329936","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329937","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330346","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330357","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330765","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333973","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333974","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333976","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333977","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333982","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334350","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334367","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334373","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334384","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334386","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334388","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334392","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334398","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334399","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334409","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334419","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334426","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334432","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334441","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334458","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334461","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334463","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334469","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334472","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334479","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334483","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334501","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334528","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334538","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334542","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334551","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334561","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334563","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334575","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334577","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334667","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334683","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334809","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2335899","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2335906","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2336546","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2336550","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337104","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337117","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337118","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337136","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337152","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337328","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337333","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338195","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338197","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338199","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338204","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338208","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338830","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338858","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2339126","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2339140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2339143","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2343169","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2343173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2343183","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2344683","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2345243","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2345615","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2362882","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-12439","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-28791","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-58641","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-60028","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-61203","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-62339","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-67304","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-71541","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-8810","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9279","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_6966.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48969","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48969","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102144-CVE-2022-48969-8fe7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102148-CVE-2022-48989-54c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49006","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102151-CVE-2022-49006-83c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102153-CVE-2022-49014-1627@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49029","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49029","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102155-CVE-2022-49029-0ffd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49747","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355435","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49747","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032759-CVE-2022-49747-f361@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49778","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363427","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49778","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050118-CVE-2022-49778-ea15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49804","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363456","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49804","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49804","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050127-CVE-2022-49804-0866@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49815","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363358","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49815","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050131-CVE-2022-49815-ebd2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50112","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50112","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061808-CVE-2022-50112-e37e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50121","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373534","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50121","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061811-CVE-2022-50121-7e33@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50159","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373696","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50159","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061825-CVE-2022-50159-a387@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373513","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50214","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061844-CVE-2022-50214-6569@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50319","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395312","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50319","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091553-CVE-2022-50319-6747@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50421","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400737","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50421","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100155-CVE-2022-50421-8bdc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50491","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401482","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50491","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100417-CVE-2022-50491-7a8b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402295","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50511","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50511","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100701-CVE-2022-50511-5d8d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50614","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419885","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120851-CVE-2022-50614-cc88@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50743","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425151","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50743","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122449-CVE-2022-50743-8e63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50811","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426130","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50811","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50811","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123013-CVE-2022-50811-66f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52672","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52672","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051729-CVE-2023-52672-f30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52917","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52917","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102100-CVE-2023-52917-f16d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53066","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363718","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53066","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050211-CVE-2023-53066-cba3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53117","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363694","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050229-CVE-2023-53117-09c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53196","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395317","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53196","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091559-CVE-2023-53196-c59a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53260","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395374","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53260","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091504-CVE-2023-53260-2323@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53261","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395302","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53261","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091504-CVE-2023-53261-6a1a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53287","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395698","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53287","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091625-CVE-2023-53287-d8cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53510","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400714","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53510","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100130-CVE-2023-53510-9e6a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400734","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53519","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53519","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100132-CVE-2023-53519-de9d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53555","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401465","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53555","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100448-CVE-2023-53555-b949@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53568","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401507","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53568","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53568","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100452-CVE-2023-53568-0020@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53595","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401509","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100428-CVE-2023-53595-91fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53654","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402189","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53654","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53654","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100720-CVE-2023-53654-dcad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53859","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420340","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53859","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120904-CVE-2023-53859-1c16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53989","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122423-CVE-2023-53989-1b3b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54089","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425125","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54089","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122406-CVE-2023-54089-ddc6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54117","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425079","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122415-CVE-2023-54117-e980@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54230","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426148","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54230","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54230","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123030-CVE-2023-54230-914e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54278","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426072","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54278","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123003-CVE-2023-54278-d4b2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54313","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123036-CVE-2023-54313-f889@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54322","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426163","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54322","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123022-CVE-2023-54322-34ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27008","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27008-5964@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27398","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27398","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051355-CVE-2024-27398-08ef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35891","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35891","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051948-CVE-2024-35891-3a56@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051917-CVE-2024-35933-cf34@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051917-CVE-2024-35934-c8af@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35963","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35963","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35963","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35963-7934@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35964","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35964-25e2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35965","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35965-19f1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35966","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35966","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35966-e107@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052022-CVE-2024-35967-d111@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35978","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35978","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052025-CVE-2024-35978-adaa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36011","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36011","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052312-CVE-2024-36011-2a8b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36012","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052314-CVE-2024-36012-3062@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052314-CVE-2024-36013-0c90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36880","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053031-CVE-2024-36880-c961@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36968","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36968","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38541","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38541","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061948-CVE-2024-38541-53d0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39500","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39500-eba6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40956","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40956","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071224-CVE-2024-40956-b65d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41010","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41062","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41062","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072906-CVE-2024-41062-cb85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42094","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300709","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-42133","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42133","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073028-CVE-2024-42133-07c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42253","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303634","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42253","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080835-CVE-2024-42253-0c21@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://lore.kernel.org/linux-cve-announce/2024081737-CVE-2024-42265-a943@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42278","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305423","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42278","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081742-CVE-2024-42278-e639@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305436","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081746-CVE-2024-42291-6f31@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42294","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305439","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42294","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081746-CVE-2024-42294-0145@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42302","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305447","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42302","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081749-CVE-2024-42302-c0d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305449","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42304","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081749-CVE-2024-42304-d0e4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42305","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305450","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42305","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081750-CVE-2024-42305-94ed@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42312","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305457","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42312","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081752-CVE-2024-42312-bddc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42315","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305460","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42315","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081753-CVE-2024-42315-a707@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305461","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42316","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081753-CVE-2024-42316-8b49@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42321","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42321","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081755-CVE-2024-42321-4b46@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43820","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305478","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43820","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081724-CVE-2024-43820-1bd6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43821","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305479","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43821","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081724-CVE-2024-43821-6ffc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43823","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305481","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43823","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081725-CVE-2024-43823-4bdd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43828","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305486","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43828","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081726-CVE-2024-43828-6bcb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43834","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305492","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43834","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081728-CVE-2024-43834-0140@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43846","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305504","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081732-CVE-2024-43846-2bd0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43853","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305511","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43853","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081734-CVE-2024-43853-da5b@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://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43871-c2cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43873","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306367","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43873","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43873","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43873-c547@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43882","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306376","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082152-CVE-2024-43882-4fa4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082621-CVE-2024-43884-43fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43889","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082600-CVE-2024-43889-4d0b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43898","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43898","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082613-CVE-2024-43898-52c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43910","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43910","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43910","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082630-CVE-2024-43910-c6ec@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43914","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43914","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082635-CVE-2024-43914-a664@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082636-CVE-2024-44931-8212@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44932","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44932","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082638-CVE-2024-44932-2659@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082641-CVE-2024-44934-a7fe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44952","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44952","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090411-CVE-2024-44952-6290@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44958","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090413-CVE-2024-44958-80e9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44964","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090414-CVE-2024-44964-ebb1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44975","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44975","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090442-CVE-2024-44975-7c21@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44987","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44987","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090446-CVE-2024-44987-f916@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090446-CVE-2024-44989-8a2d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45000","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45000","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090449-CVE-2024-45000-fd6f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45009","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45009","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091104-CVE-2024-45009-24ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091107-CVE-2024-45010-33ee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45016","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45016","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091108-CVE-2024-45016-fd5a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45022","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091109-CVE-2024-45022-08f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46673","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46673","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091333-CVE-2024-46673-c49c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46675","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46675","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091335-CVE-2024-46675-ba70@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46711","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46711","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46711","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091348-CVE-2024-46711-ab95@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46722","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46722","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091834-CVE-2024-46722-34b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46723","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46723","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091834-CVE-2024-46723-6726@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46724","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46724","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091835-CVE-2024-46724-02f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46725","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46725","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091835-CVE-2024-46725-af49@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46743","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46743","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091835-CVE-2024-46743-f386@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46745","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46745","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091836-CVE-2024-46745-7b05@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46747","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46747","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091837-CVE-2024-46747-f489@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46750","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46750","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46750","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091838-CVE-2024-46750-3be1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46754","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46754","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091840-CVE-2024-46754-7f04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46756","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46756","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091840-CVE-2024-46756-2ca6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46758","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46758","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091841-CVE-2024-46758-6154@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46759","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46759","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091841-CVE-2024-46759-9b86@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46761","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46761","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091842-CVE-2024-46761-289f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46783","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46783","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091850-CVE-2024-46783-edcb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46786","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46786","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091851-CVE-2024-46786-a167@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46787","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46787","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091852-CVE-2024-46787-8b6d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46800","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46800","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091857-CVE-2024-46800-0f62@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46805","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46805","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092709-CVE-2024-46805-b06a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46806","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46806","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46806","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092709-CVE-2024-46806-2cc7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46807","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46807","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092709-CVE-2024-46807-b78e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46819","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46819","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092712-CVE-2024-46819-d958@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46820","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46820","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092712-CVE-2024-46820-6405@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46822","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46822","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092749-CVE-2024-46822-b901@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46828","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46828","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092751-CVE-2024-46828-2184@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46835","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46835","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092753-CVE-2024-46835-4f99@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46839","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46839","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092754-CVE-2024-46839-cfab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46853","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46853","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092742-CVE-2024-46853-ab04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46864","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46864","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092745-CVE-2024-46864-0343@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46871","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46871","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024100958-CVE-2024-46871-15f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011119-CVE-2024-47141-13f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47660","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024100959-CVE-2024-47660-2d61@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47668","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47668","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024100906-CVE-2024-47668-6b53@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47678","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47678","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102106-CVE-2024-47678-0b1b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47685","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47685","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-47685-af1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47687","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47687","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47687","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-47687-9a03@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47692","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47692","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102111-CVE-2024-47692-38d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47700","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47700","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102114-CVE-2024-47700-00ff@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47703","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47703","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102115-CVE-2024-47703-36ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47705","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47705","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-47705-12bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47706","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47706","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47706","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-47706-7312@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47710","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47710","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102118-CVE-2024-47710-3882@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47713","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47713","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102119-CVE-2024-47713-2624@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47715","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47715","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102120-CVE-2024-47715-ff4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47718","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47718","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47718","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102121-CVE-2024-47718-c7cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47719","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47719","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102121-CVE-2024-47719-09a2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47737","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47737","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102108-CVE-2024-47737-b77e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47738","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47738","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102108-CVE-2024-47738-3f0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47739","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47739","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-47739-8bc4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47745","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47745","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102111-CVE-2024-47745-42e6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47748","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47748","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102112-CVE-2024-47748-a134@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-48873","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-48873","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-48873","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011120-CVE-2024-48873-75a9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49569","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49569","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011122-CVE-2024-49569-c532@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49851","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49851","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102152-CVE-2024-49851-edd9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49856","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49856","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102154-CVE-2024-49856-f5f7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49860","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49860","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102124-CVE-2024-49860-2a48@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49861","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320275","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102124-CVE-2024-49861-5288@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49862","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49862","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49862-b995@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49870","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49870","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102114-CVE-2024-49870-44f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49875","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49875","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102115-CVE-2024-49875-02ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102115-CVE-2024-49878-8099@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49881","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49881","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49881-bfd0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49882-4169@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49883","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49883","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49883-ca93@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49884-fa56@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49885","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102117-CVE-2024-49885-d5d0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49886","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49886","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102117-CVE-2024-49886-3477@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49889","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102117-CVE-2024-49889-6140@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49904","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49904","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102120-CVE-2024-49904-121b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49927-86cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49928","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49928-05d6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49929","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49929-1031@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49930-34e8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-49933-f918@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-49934-0ac9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49935","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49935","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-49935-004d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49937","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49937","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102127-CVE-2024-49937-74ee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49938","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49938","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102127-CVE-2024-49938-5a61@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102127-CVE-2024-49939-b39d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49946","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49946","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-49946-762f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49948","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-49948-ba28@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49950","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-49950-bbf4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49951","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49951","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-49951-a620@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49954","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49954","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-49954-cea5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49959","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102131-CVE-2024-49959-ce09@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102131-CVE-2024-49960-f9cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49962","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49962","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-49962-8d16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-49967-a58a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49968","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49968","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-49968-ce10@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49971","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49971","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-49971-ad07@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49973","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-49973-8824@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49974","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49974","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-49974-bda6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49975","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49975","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-49975-4533@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49977","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49977","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102135-CVE-2024-49977-b657@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49983","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49983","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102136-CVE-2024-49983-275e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49991","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49991","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102137-CVE-2024-49991-59d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49993","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49993","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102138-CVE-2024-49993-5b57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49994","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49994","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102138-CVE-2024-49994-de99@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49995","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102138-CVE-2024-49995-ec59@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49999","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49999","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102139-CVE-2024-49999-e815@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50002","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50002","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102139-CVE-2024-50002-bdfd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50006","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102108-CVE-2024-50006-fe44@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50008","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-50008-0152@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50009","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50009","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-50009-1b62@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102110-CVE-2024-50013-05ef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102110-CVE-2024-50014-d684@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50015","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102110-CVE-2024-50015-1eb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50018","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50018","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102111-CVE-2024-50018-65e9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50019","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-50019-5896@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50022","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-50022-0531@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50023","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-50023-0e72@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50024","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50024","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50024","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-50024-a052@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50027","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50027","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50027","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-50027-91e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50028","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50028","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-50028-5655@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50029","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50029","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-50029-8df2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50033","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50033","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102131-CVE-2024-50033-ce5e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50035","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50035","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-50035-82d8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-50038-dc41@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50039","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-50039-41b0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50044","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-50044-2ee1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50046","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50046","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-50046-a9b4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50047","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-50047-7a27@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50055","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-50055-7d1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102135-CVE-2024-50057-d046@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50058","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50058","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102135-CVE-2024-50058-e827@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50064","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102136-CVE-2024-50064-33d1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50067","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50067","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102859-CVE-2024-50067-f7c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50073","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50073","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102935-CVE-2024-50073-307b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50074","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50074","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102935-CVE-2024-50074-d44d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50075","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50075","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102935-CVE-2024-50075-81b7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50077","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50077","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102936-CVE-2024-50077-2940@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50078","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50078","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102936-CVE-2024-50078-cfe9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50081","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50081","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50081","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102937-CVE-2024-50081-f8d6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50082","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50082","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102937-CVE-2024-50082-c5b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50093","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110551-CVE-2024-50093-2811@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110526-CVE-2024-50101-d1bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50102","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50102","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110553-CVE-2024-50102-3d1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50106","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50106","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110553-CVE-2024-50106-c095@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50107","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50107","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110554-CVE-2024-50107-6bdf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50109","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50109","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110554-CVE-2024-50109-b93c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50117","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110555-CVE-2024-50117-83b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50120","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50120","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110556-CVE-2024-50120-07e2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50121","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110556-CVE-2024-50121-2a0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50126","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50126","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110557-CVE-2024-50126-733b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50127","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50127","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50127","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110557-CVE-2024-50127-c0b5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50128","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50128","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50128","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110557-CVE-2024-50128-0fd8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50130","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50130","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110558-CVE-2024-50130-7580@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110742-CVE-2024-50141-a773@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50143","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50143","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110743-CVE-2024-50143-4678@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50150","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50150","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50150-0254@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50151","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50151","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50151-f52b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50152","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50152-535e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50153","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50153","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50153-ecf2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50162","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50162","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110747-CVE-2024-50162-474e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50163","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50163","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110747-CVE-2024-50163-6769@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50169","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50169","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110749-CVE-2024-50169-9df5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50182","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50182","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110833-CVE-2024-50182-0fe4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50186","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50186","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110834-CVE-2024-50186-acb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50189","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50189","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110851-CVE-2024-50189-48c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50191","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50191","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110851-CVE-2024-50191-f31c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50197","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50197","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50197.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50199","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50199","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50199","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50199.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50200","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50200","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50200.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50201","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50201","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110818-CVE-2024-50201-b73d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50215","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50215","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110924-CVE-2024-50215-0155@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50216","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50216","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110924-CVE-2024-50216-a031@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50219","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50219","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110925-CVE-2024-50219-c970@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50228","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110928-CVE-2024-50228-7a2a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50235","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50235","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110931-CVE-2024-50235-14eb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50236","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50236","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110931-CVE-2024-50236-49dc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50237","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110932-CVE-2024-50237-7073@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50256","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50256","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110938-CVE-2024-50256-5b66@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50261","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50261","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110940-CVE-2024-50261-3a20@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50271","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50271","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111929-CVE-2024-50271-9089@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50272","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50272","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111930-CVE-2024-50272-5691@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50278","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50278","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111937-CVE-2024-50278-d6c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50282","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50282","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111943-CVE-2024-50282-1579@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50299","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50299","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111904-CVE-2024-50299-795d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50304","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50304","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111924-CVE-2024-50304-da6d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53042","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111924-CVE-2024-53042-f7e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53044","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111925-CVE-2024-53044-e0d1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53047","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111926-CVE-2024-53047-8214@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53050","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53050","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111927-CVE-2024-53050-b59c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53051","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53051","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111927-CVE-2024-53051-5184@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53055","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111928-CVE-2024-53055-4a64@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111928-CVE-2024-53057-a3a5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53059","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53059","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111928-CVE-2024-53059-4f81@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53060","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111931-CVE-2024-53060-3b94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111933-CVE-2024-53070-6eea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53072","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111934-CVE-2024-53072-f307@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53074","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53074","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111924-CVE-2024-53074-e49b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53082","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53082","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111904-CVE-2024-53082-30c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53085","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111905-CVE-2024-53085-9cf3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53091","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53091","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112151-CVE-2024-53091-7f61@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53093","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112152-CVE-2024-53093-f854@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53095","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53095","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112152-CVE-2024-53095-7ffd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53096","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112506-CVE-2024-53096-5bcc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53097","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112505-CVE-2024-53097-cd93@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53103","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53103","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120230-CVE-2024-53103-b5ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53105","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53105","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120244-CVE-2024-53105-d978@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53110","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53110","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120248-CVE-2024-53110-3bff@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53117","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120250-CVE-2024-53117-145b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53118","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53118","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120251-CVE-2024-53118-c6d7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53120","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53120","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120251-CVE-2024-53120-65fd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53121","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120252-CVE-2024-53121-34da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53123","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53123","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120252-CVE-2024-53123-cd09@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53124","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120253-CVE-2024-53124-91b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53134","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53134","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120451-CVE-2024-53134-cb0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53136","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53136","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120452-CVE-2024-53136-f7f8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330763","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120606-CVE-2024-53141-195b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53142","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53142","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120609-CVE-2024-53142-b75e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53146","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53146","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122426-CVE-2024-53146-c503@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53152","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122428-CVE-2024-53152-ada9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53156","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53156","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122429-CVE-2024-53156-732e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53160","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53160","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122431-CVE-2024-53160-692f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53161","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53161","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122431-CVE-2024-53161-50f6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53164","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53164","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122746-CVE-2024-53164-752a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53166","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53166","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53166","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122714-CVE-2024-53166-8beb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53173","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53173","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122717-CVE-2024-53173-b3c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53174","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53174","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53174","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122717-CVE-2024-53174-d29a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53176","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334355","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53176","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122718-CVE-2024-53176-85e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53190","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122723-CVE-2024-53190-fdeb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53194","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53194","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122724-CVE-2024-53194-9edf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53203","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53203","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53203","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122727-CVE-2024-53203-80fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53208","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53208","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122729-CVE-2024-53208-dff3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53213","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53213","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53213","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122730-CVE-2024-53213-baa6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53216","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334415","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53216","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-53216.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53222","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53222","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122734-CVE-2024-53222-6c79@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53224","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53224","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122734-CVE-2024-53224-2509@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53232","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53232","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122737-CVE-2024-53232-6919@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53237","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122739-CVE-2024-53237-2fa6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53681","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53681","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011532-CVE-2024-53681-e199@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-54460","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-54460","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-54460","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011158-CVE-2024-54460-c8c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-54680","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-54680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-54680","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011145-CVE-2024-54680-db98@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56535","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56535","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56535","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122725-CVE-2024-56535-4683@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334428","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56544","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122728-CVE-2024-56544-42cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56551","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56551","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56551","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122709-CVE-2024-56551-4ad2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56558","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56558","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122712-CVE-2024-56558-9fd9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56562","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56562","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56562","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122713-CVE-2024-56562-9fd5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56566","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56566","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122715-CVE-2024-56566-0a7e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56570","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56570","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122716-CVE-2024-56570-7580@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56590","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56590","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122759-CVE-2024-56590-d4ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56591","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56591","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122759-CVE-2024-56591-eaf9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56600","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122702-CVE-2024-56600-7867@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56601","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56601","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56601","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122703-CVE-2024-56601-2150@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56602","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56602","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122703-CVE-2024-56602-d030@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56604","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56604","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122704-CVE-2024-56604-8494@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56605","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122704-CVE-2024-56605-d424@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56611","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122706-CVE-2024-56611-262a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122707-CVE-2024-56614-17c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56616","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56616","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122708-CVE-2024-56616-ae89@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56623","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56623","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122710-CVE-2024-56623-e4c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56631","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56631","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122731-CVE-2024-56631-548f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56642","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56642","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56642","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122737-CVE-2024-56642-71ee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56644","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56644","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56644","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122737-CVE-2024-56644-83c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56647","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56647","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56647","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122738-CVE-2024-56647-d71f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56653","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56653","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56653","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122749-CVE-2024-56653-bb35@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56654","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56654","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56654","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122749-CVE-2024-56654-66a1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122752-CVE-2024-56663-66d7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56664","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56664","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122752-CVE-2024-56664-9dc6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56667","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56667","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122753-CVE-2024-56667-3c3f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56688","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56688","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122834-CVE-2024-56688-4e02@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56693","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56693","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122835-CVE-2024-56693-b3c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56729","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56729","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56729","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122924-CVE-2024-56729-8f1c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56757","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56757","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010651-CVE-2024-56757-c26b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56760","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56760","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010654-CVE-2024-56760-af6e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56779","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56779","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010812-CVE-2024-56779-74f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56783","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56783","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010807-CVE-2024-56783-4ed9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57798","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57798","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011151-CVE-2024-57798-68b5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57809","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011103-CVE-2024-57809-a6be@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011103-CVE-2024-57843-1c15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57852","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348530","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57852","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022603-CVE-2024-57852-f942@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57879","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57879","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011131-CVE-2024-57879-7fa8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011510-CVE-2024-57884-4cf8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57885","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338198","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011510-CVE-2024-57885-ea46@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57888","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011511-CVE-2024-57888-0b38@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57890","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57890","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/b92667f755749cf10d9ef1088865c555ae83ffb7","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c2f961c46ea0e5274c5c320d007c2dd949cf627a","tags":["article"]},{"url":"https://git.kernel.org/stable/c/d0257e089d1bbd35c69b6c97ff73e3690ab149a9","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57894","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011513-CVE-2024-57894-fbfe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57898","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57898","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011515-CVE-2024-57898-bfde@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57903","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011517-CVE-2024-57903-fd2a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57929","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011945-CVE-2024-57929-2b82@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025012147-CVE-2024-57931-06fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025012128-CVE-2024-57940-e289@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58009","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348526","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58009","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022656-CVE-2024-58009-b2d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58064","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2350354","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025030609-CVE-2024-58064-6aa6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58099","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58099","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025042936-CVE-2024-58099-39c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-1272","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-1272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-1272","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21646","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21646","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21646","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011945-CVE-2025-21646-8f6e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025012135-CVE-2025-21663-7420@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21666","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21666","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025013157-CVE-2025-21666-465a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21668","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21668","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025013158-CVE-2025-21668-f82f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21669","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025013158-CVE-2025-21669-b52c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21689","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21689","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025021055-CVE-2025-21689-7ffe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21694","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21694","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21694","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/649b266606bc413407ce315f710c8ce8a88ee30a","tags":["article"]},{"url":"https://git.kernel.org/stable/c/65c367bd9d4f43513c7f837df5753bea9561b836","tags":["article"]},{"url":"https://git.kernel.org/stable/c/80828540dad0757b6337c6561d49c81038f38d87","tags":["article"]},{"url":"https://git.kernel.org/stable/c/80da29deb88a3a907441fc35bb7bac309f31e713","tags":["article"]},{"url":"https://git.kernel.org/stable/c/84c4ed15626574c9ac6c1039ba9c137a77bcc7f2","tags":["article"]},{"url":"https://git.kernel.org/stable/c/a5a2ee8144c3897d37403a69118c3e3dc5713958","tags":["article"]},{"url":"https://git.kernel.org/stable/c/cbc5dde0a461240046e8a41c43d7c3b76d5db952","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21888","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032714-CVE-2025-21888-0f83@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-22087","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2360217","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-22087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22087","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025041616-CVE-2025-22087-d711@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-68179","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2422662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-68179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68179","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025121631-CVE-2025-68179-6ce9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-71151","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2432362","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-71151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71151","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2026012328-CVE-2025-71151-1a45@gregkh/T","tags":["article"]},{"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-20244100-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1082555","tags":["report"]},{"url":"https://bugzilla.suse.com/1176081","tags":["report"]},{"url":"https://bugzilla.suse.com/1206344","tags":["report"]},{"url":"https://bugzilla.suse.com/1213034","tags":["report"]},{"url":"https://bugzilla.suse.com/1218562","tags":["report"]},{"url":"https://bugzilla.suse.com/1219125","tags":["report"]},{"url":"https://bugzilla.suse.com/1220439","tags":["report"]},{"url":"https://bugzilla.suse.com/1221980","tags":["report"]},{"url":"https://bugzilla.suse.com/1223384","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/1226585","tags":["report"]},{"url":"https://bugzilla.suse.com/1227437","tags":["report"]},{"url":"https://bugzilla.suse.com/1227941","tags":["report"]},{"url":"https://bugzilla.suse.com/1227947","tags":["report"]},{"url":"https://bugzilla.suse.com/1227952","tags":["report"]},{"url":"https://bugzilla.suse.com/1228000","tags":["report"]},{"url":"https://bugzilla.suse.com/1228410","tags":["report"]},{"url":"https://bugzilla.suse.com/1228564","tags":["report"]},{"url":"https://bugzilla.suse.com/1228743","tags":["report"]},{"url":"https://bugzilla.suse.com/1229005","tags":["report"]},{"url":"https://bugzilla.suse.com/1229042","tags":["report"]},{"url":"https://bugzilla.suse.com/1229154","tags":["report"]},{"url":"https://bugzilla.suse.com/1229568","tags":["report"]},{"url":"https://bugzilla.suse.com/1229769","tags":["report"]},{"url":"https://bugzilla.suse.com/1229837","tags":["report"]},{"url":"https://bugzilla.suse.com/1230179","tags":["report"]},{"url":"https://bugzilla.suse.com/1230405","tags":["report"]},{"url":"https://bugzilla.suse.com/1231072","tags":["report"]},{"url":"https://bugzilla.suse.com/1231094","tags":["report"]},{"url":"https://bugzilla.suse.com/1231096","tags":["report"]},{"url":"https://bugzilla.suse.com/1231105","tags":["report"]},{"url":"https://bugzilla.suse.com/1231111","tags":["report"]},{"url":"https://bugzilla.suse.com/1231148","tags":["report"]},{"url":"https://bugzilla.suse.com/1231191","tags":["report"]},{"url":"https://bugzilla.suse.com/1231197","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/1231537","tags":["report"]},{"url":"https://bugzilla.suse.com/1231539","tags":["report"]},{"url":"https://bugzilla.suse.com/1231540","tags":["report"]},{"url":"https://bugzilla.suse.com/1231673","tags":["report"]},{"url":"https://bugzilla.suse.com/1231858","tags":["report"]},{"url":"https://bugzilla.suse.com/1231859","tags":["report"]},{"url":"https://bugzilla.suse.com/1231861","tags":["report"]},{"url":"https://bugzilla.suse.com/1231864","tags":["report"]},{"url":"https://bugzilla.suse.com/1231888","tags":["report"]},{"url":"https://bugzilla.suse.com/1231889","tags":["report"]},{"url":"https://bugzilla.suse.com/1231890","tags":["report"]},{"url":"https://bugzilla.suse.com/1231893","tags":["report"]},{"url":"https://bugzilla.suse.com/1231897","tags":["report"]},{"url":"https://bugzilla.suse.com/1231903","tags":["report"]},{"url":"https://bugzilla.suse.com/1231914","tags":["report"]},{"url":"https://bugzilla.suse.com/1231929","tags":["report"]},{"url":"https://bugzilla.suse.com/1231935","tags":["report"]},{"url":"https://bugzilla.suse.com/1231938","tags":["report"]},{"url":"https://bugzilla.suse.com/1231939","tags":["report"]},{"url":"https://bugzilla.suse.com/1231942","tags":["report"]},{"url":"https://bugzilla.suse.com/1231954","tags":["report"]},{"url":"https://bugzilla.suse.com/1231958","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/1231995","tags":["report"]},{"url":"https://bugzilla.suse.com/1231996","tags":["report"]},{"url":"https://bugzilla.suse.com/1231997","tags":["report"]},{"url":"https://bugzilla.suse.com/1231998","tags":["report"]},{"url":"https://bugzilla.suse.com/1232006","tags":["report"]},{"url":"https://bugzilla.suse.com/1232007","tags":["report"]},{"url":"https://bugzilla.suse.com/1232016","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/1232037","tags":["report"]},{"url":"https://bugzilla.suse.com/1232038","tags":["report"]},{"url":"https://bugzilla.suse.com/1232039","tags":["report"]},{"url":"https://bugzilla.suse.com/1232047","tags":["report"]},{"url":"https://bugzilla.suse.com/1232056","tags":["report"]},{"url":"https://bugzilla.suse.com/1232069","tags":["report"]},{"url":"https://bugzilla.suse.com/1232070","tags":["report"]},{"url":"https://bugzilla.suse.com/1232071","tags":["report"]},{"url":"https://bugzilla.suse.com/1232089","tags":["report"]},{"url":"https://bugzilla.suse.com/1232097","tags":["report"]},{"url":"https://bugzilla.suse.com/1232111","tags":["report"]},{"url":"https://bugzilla.suse.com/1232123","tags":["report"]},{"url":"https://bugzilla.suse.com/1232126","tags":["report"]},{"url":"https://bugzilla.suse.com/1232133","tags":["report"]},{"url":"https://bugzilla.suse.com/1232134","tags":["report"]},{"url":"https://bugzilla.suse.com/1232135","tags":["report"]},{"url":"https://bugzilla.suse.com/1232140","tags":["report"]},{"url":"https://bugzilla.suse.com/1232141","tags":["report"]},{"url":"https://bugzilla.suse.com/1232142","tags":["report"]},{"url":"https://bugzilla.suse.com/1232149","tags":["report"]},{"url":"https://bugzilla.suse.com/1232151","tags":["report"]},{"url":"https://bugzilla.suse.com/1232152","tags":["report"]},{"url":"https://bugzilla.suse.com/1232160","tags":["report"]},{"url":"https://bugzilla.suse.com/1232172","tags":["report"]},{"url":"https://bugzilla.suse.com/1232175","tags":["report"]},{"url":"https://bugzilla.suse.com/1232180","tags":["report"]},{"url":"https://bugzilla.suse.com/1232191","tags":["report"]},{"url":"https://bugzilla.suse.com/1232199","tags":["report"]},{"url":"https://bugzilla.suse.com/1232200","tags":["report"]},{"url":"https://bugzilla.suse.com/1232201","tags":["report"]},{"url":"https://bugzilla.suse.com/1232217","tags":["report"]},{"url":"https://bugzilla.suse.com/1232218","tags":["report"]},{"url":"https://bugzilla.suse.com/1232221","tags":["report"]},{"url":"https://bugzilla.suse.com/1232236","tags":["report"]},{"url":"https://bugzilla.suse.com/1232253","tags":["report"]},{"url":"https://bugzilla.suse.com/1232282","tags":["report"]},{"url":"https://bugzilla.suse.com/1232285","tags":["report"]},{"url":"https://bugzilla.suse.com/1232286","tags":["report"]},{"url":"https://bugzilla.suse.com/1232304","tags":["report"]},{"url":"https://bugzilla.suse.com/1232305","tags":["report"]},{"url":"https://bugzilla.suse.com/1232313","tags":["report"]},{"url":"https://bugzilla.suse.com/1232314","tags":["report"]},{"url":"https://bugzilla.suse.com/1232339","tags":["report"]},{"url":"https://bugzilla.suse.com/1232354","tags":["report"]},{"url":"https://bugzilla.suse.com/1232392","tags":["report"]},{"url":"https://bugzilla.suse.com/1232394","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/1232442","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48946","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-48956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48958","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-48966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48967","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-48978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48985","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-48992","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-49010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49011","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-49020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49021","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-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-52898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52918","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-39476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47673","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-47685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49967","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-49996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50058","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250034-1/","tags":["advisory"]},{"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-46724","tags":["report"]},{"url":"https://git.kernel.org/linus/d768394fa99467bcf2703bde74ddc96eeb0b71fa","tags":["report"]},{"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-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-7159-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7159-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7159-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7159-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7154-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7159-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7194-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7195-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7196-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7195-2","tags":["advisory"]},{"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-2023-52918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26661","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-26893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38577","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-39472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40915","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-41019","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-41060","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-41077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41078","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-42114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42126","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-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-42271","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-42276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42277","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-42296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42302","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-42312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42313","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-43829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43834","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-43849","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-43863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43867","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-43871","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-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-43889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43892","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-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-43908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44934","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-44958","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-44966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44969","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-44987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44988","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-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-45007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45008","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-45021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-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-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-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-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-46746","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-46752","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-46763","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-46791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46795","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-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-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-46819","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-46832","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-47660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47665","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-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-42131","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-42160","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-42228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42229","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-42244","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-2024-45016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26947","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-36938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36953","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-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-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-27072","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-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"]},{"url":"https://ubuntu.com/security/CVE-2021-47001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-38096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38597","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-46724","title":"drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\n\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error","status":"published","published":"2024-09-18T06:32:21.22Z","modified":"2026-05-11T20:35:10.12Z","updated_at":"2026-11-02T14:34:08.500935Z"}],"euvd":[{"id":"EUVD-2024-41985","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\n\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error","status":"published","published":"2024-09-18T06:32:21Z","modified":"2026-05-11T20:35:10Z","updated_at":"2026-11-02T19:04:54.84256Z"}],"ghsa":[{"id":"GHSA-gxvv-xx83-rmg6","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\n\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error","status":"published","published":"2024-09-18T09:30:36Z","modified":"2025-11-04T00:31:28Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T15:04:28.385807Z"}],"nvd":[{"id":"CVE-2024-46724","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\n\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error","status":"published","published":"2024-09-18T07:15:03.673Z","modified":"2026-06-17T07:55:48.15Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:10:27.456509Z"}],"osv":[{"id":"AZL-49368","title":"CVE-2024-46724 affecting package kernel for versions less than 5.15.167.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\n\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error","status":"published","published":"2024-09-18T07:15:03Z","modified":"2026-04-21T04:29:54.661194Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:06.032783Z"},{"id":"BELL-CVE-2024-46724","status":"published","published":"2024-09-19T05:56:48.82597Z","modified":"2026-01-26T09:42:33.976389Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:20.452786Z"},{"id":"DEBIAN-CVE-2024-46724","description":"In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number  Check the fb_channel_number range to avoid the array out-of-bounds read error","status":"published","published":"2024-09-18T07:15:03.673Z","modified":"2026-11-02T12:02:49.856684084Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:43.473331Z"},{"id":"OESA-2024-2321","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\niommu/vt-d: Fix double list_add when enabling VMD in scalable mode\r\n\r\nWhen enabling VMD and IOMMU scalable mode, the following kernel panic\ncall trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids\nCPU) during booting:\r\n\r\npci 0000:59:00.5: Adding to iommu group 42\n...\nvmd 0000:59:00.5: PCI host bridge to bus 10000:80\npci 10000:80:01.0: [8086:352a] type 01 class 0x060400\npci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:01.0: enabling Extended Tags\npci 10000:80:01.0: PME# supported from D0 D3hot D3cold\npci 10000:80:01.0: DMAR: Setup RID2PASID failed\npci 10000:80:01.0: Failed to add to iommu group 42: -16\npci 10000:80:03.0: [8086:352b] type 01 class 0x060400\npci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:03.0: enabling Extended Tags\npci 10000:80:03.0: PME# supported from D0 D3hot D3cold\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:29!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7\nHardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022\nWorkqueue: events work_for_cpu_fn\nRIP: 0010:__list_add_valid.cold+0x26/0x3f\nCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f\n      0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1\n      fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9\n      9e e8 8b b1 fe\nRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8\nRDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20\nRBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888\nR10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0\nR13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70\nFS:  0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n intel_pasid_alloc_table+0x9c/0x1d0\n dmar_insert_one_dev_info+0x423/0x540\n ? device_to_iommu+0x12d/0x2f0\n intel_iommu_attach_device+0x116/0x290\n __iommu_attach_device+0x1a/0x90\n iommu_group_add_device+0x190/0x2c0\n __iommu_probe_device+0x13e/0x250\n iommu_probe_device+0x24/0x150\n iommu_bus_notifier+0x69/0x90\n blocking_notifier_call_chain+0x5a/0x80\n device_add+0x3db/0x7b0\n ? arch_memremap_can_ram_remap+0x19/0x50\n ? memremap+0x75/0x140\n pci_device_add+0x193/0x1d0\n pci_scan_single_device+0xb9/0xf0\n pci_scan_slot+0x4c/0x110\n pci_scan_child_bus_extend+0x3a/0x290\n vmd_enable_domain.constprop.0+0x63e/0x820\n vmd_probe+0x163/0x190\n local_pci_probe+0x42/0x80\n work_for_cpu_fn+0x13/0x20\n process_one_work+0x1e2/0x3b0\n worker_thread+0x1c4/0x3a0\n ? rescuer_thread+0x370/0x370\n kthread+0xc7/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---\n...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n---[ end Kernel panic - not syncing: Fatal exception ]---\r\n\r\nThe following \u0026apos;lspci\u0026apos; output shows devices \u0026apos;10000:80:*\u0026apos; are subdevices of\nthe VMD device 0000:59:00.5:\r\n\r\n  $ lspci\n  ...\n  0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)\n  ...\n  10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)\n  10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)\n  10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)\n  10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)\n  10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]\n  10000:82:00\n---truncated---(CVE-2022-48916)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: mt7621: Add sentinel to quirks table  Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call.  This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in:  commit 7c18b64bba3b (\u0026quot;mips: ralink: mt7621: do not use kzalloc too early\u0026quot;)  Fix it by adding the required sentinel.(CVE-2022-48952)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: module: prevent NULL pointer dereference in vsnprintf()\r\n\r\nIn of_modalias(), we can get passed the str and len parameters which would\ncause a kernel oops in vsnprintf() since it only allows passing a NULL ptr\nwhen the length is also 0. Also, we need to filter out the negative values\nof the len parameter as these will result in a really huge buffer since\nsnprintf() takes size_t parameter while ours is ssize_t...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the Svace static\nanalysis tool.(CVE-2024-35878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: xilinx_dpdma: Fix locking\r\n\r\nThere are several places where either chan-\u0026gt;lock or chan-\u0026gt;vchan.lock was\nnot held. Add appropriate locking. This fixes lockdep warnings like\r\n\r\n[   31.077578] ------------[ cut here ]------------\n[   31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.077953] Modules linked in:\n[   31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98\n[   31.078102] Hardware name: xlnx,zynqmp (DT)\n[   31.078169] Workqueue: events_unbound deferred_probe_work_func\n[   31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0\n[   31.078550] sp : ffffffc083bb2e10\n[   31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168\n[   31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480\n[   31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000\n[   31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000\n[   31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\n[   31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001\n[   31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def\n[   31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516\n[   31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff\n[   31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000\n[   31.080307] Call trace:\n[   31.080340]  xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.080518]  xilinx_dpdma_issue_pending+0x11c/0x120\n[   31.080595]  zynqmp_disp_layer_update+0x180/0x3ac\n[   31.080712]  zynqmp_dpsub_plane_atomic_update+0x11c/0x21c\n[   31.080825]  drm_atomic_helper_commit_planes+0x20c/0x684\n[   31.080951]  drm_atomic_helper_commit_tail+0x5c/0xb0\n[   31.081139]  commit_tail+0x234/0x294\n[   31.081246]  drm_atomic_helper_commit+0x1f8/0x210\n[   31.081363]  drm_atomic_commit+0x100/0x140\n[   31.081477]  drm_client_modeset_commit_atomic+0x318/0x384\n[   31.081634]  drm_client_modeset_commit_locked+0x8c/0x24c\n[   31.081725]  drm_client_modeset_commit+0x34/0x5c\n[   31.081812]  __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168\n[   31.081899]  drm_fb_helper_set_par+0x50/0x70\n[   31.081971]  fbcon_init+0x538/0xc48\n[   31.082047]  visual_init+0x16c/0x23c\n[   31.082207]  do_bind_con_driver.isra.0+0x2d0/0x634\n[   31.082320]  do_take_over_console+0x24c/0x33c\n[   31.082429]  do_fbcon_takeover+0xbc/0x1b0\n[   31.082503]  fbcon_fb_registered+0x2d0/0x34c\n[   31.082663]  register_framebuffer+0x27c/0x38c\n[   31.082767]  __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c\n[   31.082939]  drm_fb_helper_initial_config+0x50/0x74\n[   31.083012]  drm_fbdev_dma_client_hotplug+0xb8/0x108\n[   31.083115]  drm_client_register+0xa0/0xf4\n[   31.083195]  drm_fbdev_dma_setup+0xb0/0x1cc\n[   31.083293]  zynqmp_dpsub_drm_init+0x45c/0x4e0\n[   31.083431]  zynqmp_dpsub_probe+0x444/0x5e0\n[   31.083616]  platform_probe+0x8c/0x13c\n[   31.083713]  really_probe+0x258/0x59c\n[   31.083793]  __driver_probe_device+0xc4/0x224\n[   31.083878]  driver_probe_device+0x70/0x1c0\n[   31.083961]  __device_attach_driver+0x108/0x1e0\n[   31.084052]  bus_for_each_drv+0x9c/0x100\n[   31.084125]  __device_attach+0x100/0x298\n[   31.084207]  device_initial_probe+0x14/0x20\n[   31.084292]  bus_probe_device+0xd8/0xdc\n[   31.084368]  deferred_probe_work_func+0x11c/0x180\n[   31.084451]  process_one_work+0x3ac/0x988\n[   31.084643]  worker_thread+0x398/0x694\n[   31.084752]  kthread+0x1bc/0x1c0\n[   31.084848]  ret_from_fork+0x10/0x20\n[   31.084932] irq event stamp: 64549\n[   31.084970] hardirqs last  enabled at (64548): [\u0026lt;ffffffc081adf35c\u0026gt;] _raw_spin_unlock_irqrestore+0x80/0x90\n[   31.085157]\n---truncated---(CVE-2024-35990)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()\r\n\r\nsyzbot reported that nf_reinject() could be called without rcu_read_lock() :\r\n\r\nWARNING: suspicious RCU usage\n6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted\r\n\r\nnet/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!\r\n\r\nother info that might help us debug this:\r\n\r\nrcu_scheduler_active = 2, debug_locks = 1\n2 locks held by syz-executor.4/13427:\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172\r\n\r\nstack backtrace:\nCPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n  nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]\n  nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397\n  nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]\n  instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172\n  rcu_do_batch kernel/rcu/tree.c:2196 [inline]\n  rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471\n  handle_softirqs+0x2d6/0x990 kernel/softirq.c:554\n  __do_softirq kernel/softirq.c:588 [inline]\n  invoke_softirq kernel/softirq.c:428 [inline]\n  __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637\n  irq_exit_rcu+0x9/0x30 kernel/softirq.c:649\n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;(CVE-2024-36286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: core: Fix NULL module pointer assignment at card init\r\n\r\nThe commit 81033c6b584b (\u0026quot;ALSA: core: Warn on empty module\u0026quot;)\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0026apos;#ifdef\nMODULE\u0026apos;.  This works in most cases, but the devils are always in\ndetails.  \u0026quot;MODULE\u0026quot; is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0026apos;t mean that the caller is\nalso built-in or not.  Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0026apos;s non-NULL, and\ncard-\u0026gt;module remains as NULL.  This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\r\n\r\nFor addressing the bug, move the assignment of card-\u0026gt;module again out\nof ifdef.  The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\r\n\r\nNote that we keep \u0026apos;ifdef MODULE\u0026apos; for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check.  Admittedly it won\u0026apos;t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y.  But, it\u0026apos;s no\nreal problem as it\u0026apos;s only for debugging, and the condition is pretty\nrare.(CVE-2024-38605)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoundwire: cadence: fix invalid PDI offset\r\n\r\nFor some reason, we add an offset to the PDI, presumably to skip the\nPDI0 and PDI1 which are reserved for BPT.\r\n\r\nThis code is however completely wrong and leads to an out-of-bounds\naccess. We were just lucky so far since we used only a couple of PDIs\nand remained within the PDI array bounds.\r\n\r\nA Fixes: tag is not provided since there are no known platforms where\nthe out-of-bounds would be accessed, and the initial code had problems\nas well.\r\n\r\nA follow-up patch completely removes this useless offset.(CVE-2024-38635)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: prevent pt_regs corruption for secondary idle threads\r\n\r\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\r\n\r\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\u0026quot;riscv: prevent stack corruption by reserving task_pt_regs(p) early\u0026quot;).\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.(CVE-2024-38667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexfat: fix potential deadlock on __exfat_get_dentry_set\r\n\r\nWhen accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array\nis allocated in __exfat_get_entry_set. The problem is that the bh-array is\nallocated with GFP_KERNEL. It does not make sense. In the following cases,\na deadlock for sbi-\u0026gt;s_lock between the two processes may occur.\r\n\r\n       CPU0                CPU1\n       ----                ----\n  kswapd\n   balance_pgdat\n    lock(fs_reclaim)\n                      exfat_iterate\n                       lock(\u0026amp;sbi-\u0026gt;s_lock)\n                       exfat_readdir\n                        exfat_get_uniname_from_ext_entry\n                         exfat_get_dentry_set\n                          __exfat_get_dentry_set\n                           kmalloc_array\n                            ...\n                            lock(fs_reclaim)\n    ...\n    evict\n     exfat_evict_inode\n      lock(\u0026amp;sbi-\u0026gt;s_lock)\r\n\r\nTo fix this, let\u0026apos;s allocate bh-array with GFP_NOFS.(CVE-2024-42315)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/client: fix null pointer dereference in drm_client_modeset_probe\r\n\r\nIn drm_client_modeset_probe(), the return value of drm_mode_duplicate() is\nassigned to modeset-\u0026gt;mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: only decrement add_addr_accepted for MPJ req\r\n\r\nAdding the following warning ...\r\n\r\n  WARN_ON_ONCE(msk-\u0026gt;pm.add_addr_accepted == 0)\r\n\r\n... before decrementing the add_addr_accepted counter helped to find a\nbug when running the \u0026quot;remove single subflow\u0026quot; subtest from the\nmptcp_join.sh selftest.\r\n\r\nRemoving a \u0026apos;subflow\u0026apos; endpoint will first trigger a RM_ADDR, then the\nsubflow closure. Before this patch, and upon the reception of the\nRM_ADDR, the other peer will then try to decrement this\nadd_addr_accepted. That\u0026apos;s not correct because the attached subflows have\nnot been created upon the reception of an ADD_ADDR.\r\n\r\nA way to solve that is to decrement the counter only if the attached\nsubflow was an MP_JOIN to a remote id that was not 0, and initiated by\nthe host receiving the RM_ADDR.(CVE-2024-45009)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: cmd-db: Map shared memory as WC, not WB\r\n\r\nLinux does not write into cmd-db region. This region of memory is write\nprotected by XPU. XPU may sometime falsely detect clean cache eviction\nas \u0026quot;write\u0026quot; into the write protected region leading to secure interrupt\nwhich causes an endless loop somewhere in Trust Zone.\r\n\r\nThe only reason it is working right now is because Qualcomm Hypervisor\nmaps the same region as Non-Cacheable memory in Stage 2 translation\ntables. The issue manifests if we want to use another hypervisor (like\nXen or KVM), which does not know anything about those specific mappings.\r\n\r\nChanging the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC\nremoves dependency on correct mappings in Stage 2 tables. This patch\nfixes the issue by updating the mapping to MEMREMAP_WC.\r\n\r\nI tested this on SA8155P with Xen.(CVE-2024-46689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS\r\n\r\nGrab kvm-\u0026gt;srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\r\n\r\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU.  I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems.  Acquiring SRCU isn\u0026apos;t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\r\n\r\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\r\n\r\n other info that might help us debug this:\r\n\r\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n  #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\r\n\r\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x7f/0x90\n  lockdep_rcu_suspicious+0x13f/0x1a0\n  kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n  kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n  nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n  load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n  vmx_leave_nested+0x30/0x40 [kvm_intel]\n  kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n  kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n  ? mark_held_locks+0x49/0x70\n  ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n  ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  ? lock_acquire+0xba/0x2d0\n  ? find_held_lock+0x2b/0x80\n  ? do_user_addr_fault+0x40c/0x6f0\n  ? lock_release+0xb7/0x270\n  __x64_sys_ioctl+0x82/0xb0\n  do_syscall_64+0x6c/0x170\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n  \u0026lt;/TASK\u0026gt;(CVE-2024-46830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[   36.926103] ==================================================================\n[   36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[   36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[   36.946721]\n[   36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[   36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[   36.961260] Call trace:\n[   36.963723]  dump_backtrace+0x90/0xe8\n[   36.967414]  show_stack+0x18/0x24\n[   36.970749]  dump_stack_lvl+0x78/0x90\n[   36.974451]  print_report+0x114/0x5cc\n[   36.978151]  kasan_report+0xa4/0xf0\n[   36.981670]  __asan_report_load_n_noabort+0x1c/0x28\n[   36.986587]  nxp_fspi_exec_op+0x26ec/0x2838\n[   36.990800]  spi_mem_exec_op+0x8ec/0xd30\n[   36.994762]  spi_mem_no_dirmap_read+0x190/0x1e0\n[   36.999323]  spi_mem_dirmap_write+0x238/0x32c\n[   37.003710]  spi_nor_write_data+0x220/0x374\n[   37.007932]  spi_nor_write+0x110/0x2e8\n[   37.011711]  mtd_write_oob_std+0x154/0x1f0\n[   37.015838]  mtd_write_oob+0x104/0x1d0\n[   37.019617]  mtd_write+0xb8/0x12c\n[   37.022953]  mtdchar_write+0x224/0x47c\n[   37.026732]  vfs_write+0x1e4/0x8c8\n[   37.030163]  ksys_write+0xec/0x1d0\n[   37.033586]  __arm64_sys_write+0x6c/0x9c\n[   37.037539]  invoke_syscall+0x6c/0x258\n[   37.041327]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.046244]  do_el0_svc+0x44/0x5c\n[   37.049589]  el0_svc+0x38/0x78\n[   37.052681]  el0t_64_sync_handler+0x13c/0x158\n[   37.057077]  el0t_64_sync+0x190/0x194\n[   37.060775]\n[   37.062274] Allocated by task 455:\n[   37.065701]  kasan_save_stack+0x2c/0x54\n[   37.069570]  kasan_save_track+0x20/0x3c\n[   37.073438]  kasan_save_alloc_info+0x40/0x54\n[   37.077736]  __kasan_kmalloc+0xa0/0xb8\n[   37.081515]  __kmalloc_noprof+0x158/0x2f8\n[   37.085563]  mtd_kmalloc_up_to+0x120/0x154\n[   37.089690]  mtdchar_write+0x130/0x47c\n[   37.093469]  vfs_write+0x1e4/0x8c8\n[   37.096901]  ksys_write+0xec/0x1d0\n[   37.100332]  __arm64_sys_write+0x6c/0x9c\n[   37.104287]  invoke_syscall+0x6c/0x258\n[   37.108064]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.112972]  do_el0_svc+0x44/0x5c\n[   37.116319]  el0_svc+0x38/0x78\n[   37.119401]  el0t_64_sync_handler+0x13c/0x158\n[   37.123788]  el0t_64_sync+0x190/0x194\n[   37.127474]\n[   37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[   37.128977]  which belongs to the cache kmalloc-8 of size 8\n[   37.141177] The buggy address is located 0 bytes inside of\n[   37.141177]  allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[   37.153465]\n[   37.154971] The buggy address belongs to the physical page:\n[   37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[   37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[   37.175149] page_type: 0xfdffffff(slab)\n[   37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[   37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[   37.194553] page dumped because: kasan: bad access detected\n[   37.200144]\n[   37.201647] Memory state around the buggy address:\n[   37.206460]  ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[   37.213701]  ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[   37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[   37.228186]                                ^\n[   37.232473]  ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.239718]  ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix state management in error path of log writing function\r\n\r\nAfter commit a694291a6211 (\u0026quot;nilfs2: separate wait function from\nnilfs_segctor_write\u0026quot;) was applied, the log writing function\nnilfs_segctor_do_construct() was able to issue I/O requests continuously\neven if user data blocks were split into multiple logs across segments,\nbut two potential flaws were introduced in its error handling.\r\n\r\nFirst, if nilfs_segctor_begin_construction() fails while creating the\nsecond or subsequent logs, the log writing function returns without\ncalling nilfs_segctor_abort_construction(), so the writeback flag set on\npages/folios will remain uncleared.  This causes page cache operations to\nhang waiting for the writeback flag.  For example,\ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when\nan inode is evicted from memory, will hang.\r\n\r\nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. \nAs a result, if the next log write involves checkpoint creation, that\u0026apos;s\nfine, but if a partial log write is performed that does not, inodes with\nNILFS_I_COLLECTED set are erroneously removed from the \u0026quot;sc_dirty_files\u0026quot;\nlist, and their data and b-tree blocks may not be written to the device,\ncorrupting the block mapping.\r\n\r\nFix these issues by uniformly calling nilfs_segctor_abort_construction()\non failure of each step in the loop in nilfs_segctor_do_construct(),\nhaving it clean up logs and segment usages according to progress, and\ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure\nthat the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: check skb is non-NULL in tcp_rto_delta_us()  We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases:  Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: return -EINVAL when namelen is 0  When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered.  [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205]  dump_stack+0x9a/0xd0 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  __kasan_report.cold+0x34/0x84 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  kasan_report+0x3a/0x50 [ T1205]  nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  ? nfsd4_release_lockowner+0x410/0x410 [ T1205]  cld_pipe_downcall+0x5ca/0x760 [ T1205]  ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205]  ? down_write_killable_nested+0x170/0x170 [ T1205]  ? avc_policy_seqno+0x28/0x40 [ T1205]  ? selinux_file_permission+0x1b4/0x1e0 [ T1205]  rpc_pipe_write+0x84/0xb0 [ T1205]  vfs_write+0x143/0x520 [ T1205]  ksys_write+0xc9/0x170 [ T1205]  ? __ia32_sys_read+0x50/0x50 [ T1205]  ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205]  ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205]  do_syscall_64+0x33/0x40 [ T1205]  entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ==================================================================  Fix it by checking namelen.(CVE-2024-47692)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds  In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num.  This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sock_map: Add a cond_resched() in sock_hash_free()  Several syzbot soft lockup reports all have in common sock_hash_free()  If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the  dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function.  This fix prevents a potential null pointer dereference error.  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386)  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c     373 bool dcn30_set_output_transfer_func(struct dc *dc,     374                                 struct pipe_ctx *pipe_ctx,     375                                 const struct dc_stream_state *stream)     376 {     377         int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst;     378         struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc;     379         const struct pwl_params *params = NULL;     380         bool ret = false;     381     382         /* program OGAM or 3DLUT only for the top pipe*/     383         if (pipe_ctx-\u0026gt;top_pipe == NULL) {     384                 /*program rmu shaper and 3dlut in MPC*/     385                 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream);     386                 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) {                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL      387                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL)     388                                 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl;     389                         else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type ==     390                                         TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp;     391                                         cm3_helper_translate_curve_to_hw_format(     392                                         \u0026amp;stream-\u0026gt;out_transfer_func,     393                                         \u0026amp;mpc-\u0026gt;blender_params, false))     394                                 params = \u0026amp;mpc-\u0026gt;blender_params;     395                          /* there are no ROM LUTs in OUTGAM */     396                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED)     397                                 BREAK_TO_DEBUGGER();     398                 }     399         }     400 --\u0026gt; 401         mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params);                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash      402         return ret;     403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled  Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold.  This was discovered through the lock debugging, and the corresponding log is as follows:  raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace:  warn_bogus_irq_restore+0x30/0x40  _raw_spin_unlock_irqrestore+0x84/0xc8  add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2]  hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2]  hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2]  create_qp+0x138/0x258  ib_create_qp_kernel+0x50/0xe8  create_mad_qp+0xa8/0x128  ib_mad_port_open+0x218/0x448  ib_mad_init_device+0x70/0x1f8  add_client_context+0xfc/0x220  enable_device_and_get+0xd0/0x140  ib_register_device.part.0+0xf4/0x1c8  ib_register_device+0x34/0x50  hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2]  hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2]  __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2]  hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2](CVE-2024-47735)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: call cache_put if xdr_reserve_space returns NULL  If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get.  Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential oob read in nilfs_btree_check_delete()  The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.  This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself.  However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Fix a race during cpuhp processing  There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally:  ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x7c/0x110  ? debug_print_object+0x7d/0xb0  ? report_bug+0xf1/0x1d0  ? prb_read_valid+0x17/0x20  ? handle_bug+0x3f/0x70  ? exc_invalid_op+0x13/0x60  ? asm_exc_invalid_op+0x16/0x20  ? debug_print_object+0x7d/0xb0  ? debug_print_object+0x7d/0xb0  ? __pfx_timerlat_irq+0x10/0x10  __debug_object_init+0x110/0x150  hrtimer_init+0x1d/0x60  timerlat_main+0xab/0x2d0  ? __pfx_timerlat_main+0x10/0x10  kthread+0xb7/0xe0  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2d/0x40  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt; ```  After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU:  T1                       | T2 [CPUHP_ONLINE]           | cpu_device_down() osnoise_hotplug_workfn() |                          |     cpus_write_lock()                          |     takedown_cpu(1)                          |     cpus_write_unlock() [CPUHP_OFFLINE]          |     cpus_read_lock()     |     start_kthread(1)     |     cpus_read_unlock()   |  To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: wait for fixup workers before stopping cleaner kthread during umount  During unmount, at close_ctree(), we have the following steps in this order:  1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically    halts its execution (wake ups against it work but do nothing);  2) We stop the cleaner kthread - this results in freeing the respective    struct task_struct;  3) We call btrfs_stop_all_workers() which waits for any jobs running in all    the work queues and then free the work queues.  Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources.  Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs.  The stack traces reported by syzbot were the following:    BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065   Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52    CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024   Workqueue: btrfs-fixup btrfs_work_helper   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120    print_address_description mm/kasan/report.c:377 [inline]    print_report+0x169/0x550 mm/kasan/report.c:488    kasan_report+0x143/0x180 mm/kasan/report.c:601    __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065    lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]    _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162    class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]    try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154    btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842    btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314    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;    Allocated by task 2:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    unpoison_slab_object mm/kasan/common.c:319 [inline]    __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345    kasan_slab_alloc include/linux/kasan.h:247 [inline]    slab_post_alloc_hook mm/slub.c:4086 [inline]    slab_alloc_node mm/slub.c:4135 [inline]    kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187    alloc_task_struct_node kernel/fork.c:180 [inline]    dup_task_struct+0x57/0x8c0 kernel/fork.c:1107    copy_process+0x5d1/0x3d50 kernel/fork.c:2206    kernel_clone+0x223/0x880 kernel/fork.c:2787    kernel_thread+0x1bc/0x240 kernel/fork.c:2849    create_kthread kernel/kthread.c:412 [inline]    kthreadd+0x60d/0x810 kernel/kthread.c:765    ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244    Freed by task 61:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579    poison_slab_object mm/kasan/common.c:247 [inline]    __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264    kasan_slab_free include/linux/kasan.h:230 [inline]    slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix a NULL pointer dereference when failed to start a new trasacntion  [BUG] Syzbot reported a NULL pointer dereference with the following crash:    FAULT_INJECTION: forcing a failure.    start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676    prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642    relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678   ...   BTRFS info (device loop0): balance: ended with status: -12   Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI   KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667]   RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926   Call Trace:    \u0026lt;TASK\u0026gt;    commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496    btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430    del_balance_item fs/btrfs/volumes.c:3678 [inline]    reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742    btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574    btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:907 [inline]    __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893    do_syscall_x64 arch/x86/entry/common.c:52 [inline]    do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83    entry_SYSCALL_64_after_hwframe+0x77/0x7f  [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL.  Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree.  However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume.  Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots().  That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference.  [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree.  That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: map the EBADMSG to nfserr_io to avoid warning  Ext4 will throw -EBADMSG through ext4_readdir when a checksum error occurs, resulting in the following WARNING.  Fix it by mapping EBADMSG to nfserr_io.  nfsd_buffered_readdir  iterate_dir // -EBADMSG -74   ext4_readdir // .iterate_shared    ext4_dx_readdir     ext4_htree_fill_tree      htree_dirblock_to_tree       ext4_read_dirblock        __ext4_read_dirblock         ext4_dirblock_csum_verify          warn_no_space_for_csum           __warn_no_space_for_csum         return ERR_PTR(-EFSBADCRC) // -EBADMSG -74  nfserrno // WARNING  [  161.115610] ------------[ cut here ]------------ [  161.116465] nfsd: non-standard errno: -74 [  161.117315] WARNING: CPU: 1 PID: 780 at fs/nfsd/nfsproc.c:878 nfserrno+0x9d/0xd0 [  161.118596] Modules linked in: [  161.119243] CPU: 1 PID: 780 Comm: nfsd Not tainted 5.10.0-00014-g79679361fd5d #138 [  161.120684] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qe mu.org 04/01/2014 [  161.123601] RIP: 0010:nfserrno+0x9d/0xd0 [  161.124676] Code: 0f 87 da 30 dd 00 83 e3 01 b8 00 00 00 05 75 d7 44 89 ee 48 c7 c7 c0 57 24 98 89 44 24 04 c6  05 ce 2b 61 03 01 e8 99 20 d8 00 \u0026lt;0f\u0026gt; 0b 8b 44 24 04 eb b5 4c 89 e6 48 c7 c7 a0 6d a4 99 e8 cc 15 33 [  161.127797] RSP: 0018:ffffc90000e2f9c0 EFLAGS: 00010286 [  161.128794] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [  161.130089] RDX: 1ffff1103ee16f6d RSI: 0000000000000008 RDI: fffff520001c5f2a [  161.131379] RBP: 0000000000000022 R08: 0000000000000001 R09: ffff8881f70c1827 [  161.132664] R10: ffffed103ee18304 R11: 0000000000000001 R12: 0000000000000021 [  161.133949] R13: 00000000ffffffb6 R14: ffff8881317c0000 R15: ffffc90000e2fbd8 [  161.135244] FS:  0000000000000000(0000) GS:ffff8881f7080000(0000) knlGS:0000000000000000 [  161.136695] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [  161.137761] CR2: 00007fcaad70b348 CR3: 0000000144256006 CR4: 0000000000770ee0 [  161.139041] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [  161.140291] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [  161.141519] PKRU: 55555554 [  161.142076] Call Trace: [  161.142575]  ? __warn+0x9b/0x140 [  161.143229]  ? nfserrno+0x9d/0xd0 [  161.143872]  ? report_bug+0x125/0x150 [  161.144595]  ? handle_bug+0x41/0x90 [  161.145284]  ? exc_invalid_op+0x14/0x70 [  161.146009]  ? asm_exc_invalid_op+0x12/0x20 [  161.146816]  ? nfserrno+0x9d/0xd0 [  161.147487]  nfsd_buffered_readdir+0x28b/0x2b0 [  161.148333]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.149258]  ? nfsd_buffered_filldir+0xf0/0xf0 [  161.150093]  ? wait_for_concurrent_writes+0x170/0x170 [  161.151004]  ? generic_file_llseek_size+0x48/0x160 [  161.151895]  nfsd_readdir+0x132/0x190 [  161.152606]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.153516]  ? nfsd_unlink+0x380/0x380 [  161.154256]  ? override_creds+0x45/0x60 [  161.155006]  nfsd4_encode_readdir+0x21a/0x3d0 [  161.155850]  ? nfsd4_encode_readlink+0x210/0x210 [  161.156731]  ? write_bytes_to_xdr_buf+0x97/0xe0 [  161.157598]  ? __write_bytes_to_xdr_buf+0xd0/0xd0 [  161.158494]  ? lock_downgrade+0x90/0x90 [  161.159232]  ? nfs4svc_decode_voidarg+0x10/0x10 [  161.160092]  nfsd4_encode_operation+0x15a/0x440 [  161.160959]  nfsd4_proc_compound+0x718/0xe90 [  161.161818]  nfsd_dispatch+0x18e/0x2c0 [  161.162586]  svc_process_common+0x786/0xc50 [  161.163403]  ? nfsd_svc+0x380/0x380 [  161.164137]  ? svc_printk+0x160/0x160 [  161.164846]  ? svc_xprt_do_enqueue.part.0+0x365/0x380 [  161.165808]  ? nfsd_svc+0x380/0x380 [  161.166523]  ? rcu_is_watching+0x23/0x40 [  161.167309]  svc_process+0x1a5/0x200 [  161.168019]  nfsd+0x1f5/0x380 [  161.168663]  ? nfsd_shutdown_threads+0x260/0x260 [  161.169554]  kthread+0x1c4/0x210 [  161.170224]  ? kthread_insert_work_sanity_check+0x80/0x80 [  161.171246]  ret_from_fork+0x1f/0x30(CVE-2024-49875)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Initialize get_bytes_per_element\u0026apos;s default to 1  Variables, used as denominators and maybe not assigned to other values, should not be 0. bytes_per_element_y \u0026amp; bytes_per_element_c are initialized by get_bytes_per_element() which should never return 0.  This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in degamma hardware format translation  Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color  management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the  number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: check if leafidx greater than num leaves per dmap tree  syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf.  Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uaf in dbFreeBits  [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216  CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  __mutex_lock_common kernel/locking/mutex.c:587 [inline]  __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752  dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390  dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]  dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409  dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650  jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100  jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  Freed by task 5218:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579  poison_slab_object+0xe0/0x150 mm/kasan/common.c:240  __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2252 [inline]  slab_free mm/slub.c:4473 [inline]  kfree+0x149/0x360 mm/slub.c:4594  dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278  jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247  jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454  reconfigure_super+0x445/0x880 fs/super.c:1083  vfs_cmd_reconfigure fs/fsopen.c:263 [inline]  vfs_fsconfig_locked fs/fsopen.c:292 [inline]  __do_sys_fsconfig fs/fsopen.c:473 [inline]  __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf.  Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error if set_output_gamma is null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/ioapic: Handle allocation failures gracefully  Breno observed panics when using failslab under certain conditions during runtime:     can not alloc irq_pin_list (-1,0,20)    Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed     panic+0x4e9/0x590    mp_irqdomain_alloc+0x9ab/0xa80    irq_domain_alloc_irqs_locked+0x25d/0x8d0    __irq_domain_alloc_irqs+0x80/0x110    mp_map_pin_to_irq+0x645/0x890    acpi_register_gsi_ioapic+0xe6/0x150    hpet_open+0x313/0x480  That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed.  The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode.  Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error  In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain:  ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace:  \u0026lt;TASK\u0026gt;  add_transaction_credits+0x5d1/0x5e0  start_this_handle+0x1ef/0x6a0  jbd2__journal_start+0x18b/0x340  ext4_dirty_inode+0x5d/0xb0  __mark_inode_dirty+0xe4/0x5d0  generic_update_time+0x60/0x70 [...] ============================================  So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways.  Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: remove unreasonable unlock in ocfs2_read_blocks  Patch series \u0026quot;Misc fixes for ocfs2_read_blocks\u0026quot;, v5.  This series contains 2 fixes for ocfs2_read_blocks().  The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks().  The second patch fixes an issue reported by Heming Zhao when reviewing above fix.   This patch (of 2):  There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: cancel dqi_sync_work before freeing oinfo  ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled:  ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c  This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first.  BTW, return status instead of -1 when .read_file_info fails.(CVE-2024-49966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 color transformation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Limit the number of concurrent async COPY operations  Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.  Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.  An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.  If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume  In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.  This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks.  Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: fnic: Move flush_work initialization out of if block  After commit 379a58caa199 (\u0026quot;scsi: fnic: Move fnic_fnic_flush_tx() to a work queue\u0026quot;), it can happen that a work item is sent to an uninitialized work queue.  This may has the effect that the item being queued is never actually queued, and any further actions depending on it will not proceed.  The following warning is observed while the fnic driver is loaded:  kernel: WARNING: CPU: 11 PID: 0 at ../kernel/workqueue.c:1524 __queue_work+0x373/0x410 kernel:  \u0026lt;IRQ\u0026gt; kernel:  queue_work_on+0x3a/0x50 kernel:  fnic_wq_copy_cmpl_handler+0x54a/0x730 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  fnic_isr_msix_wq_copy+0x2d/0x60 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  __handle_irq_event_percpu+0x36/0x1a0 kernel:  handle_irq_event_percpu+0x30/0x70 kernel:  handle_irq_event+0x34/0x60 kernel:  handle_edge_irq+0x7e/0x1a0 kernel:  __common_interrupt+0x3b/0xb0 kernel:  common_interrupt+0x58/0xa0 kernel:  \u0026lt;/IRQ\u0026gt;  It has been observed that this may break the rediscovery of Fibre Channel devices after a temporary fabric failure.  This patch fixes it by moving the work queue initialization out of an if block in fnic_probe().(CVE-2024-50025)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: do not delay dst_entries_add() in dst_release()  dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy()  Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy()  dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already.  Decrementing the number of dsts must happen sooner.  Notes:  1) in CONFIG_XFRM case, dst_destroy() can call    dst_release_immediate(child), this might also cause UAF    if the child does not have DST_NOCOUNT set.    IPSEC maintainers might take a look and see how to address this.  2) There is also discussion about removing this count of dst,    which might happen in future kernels.(CVE-2024-50036)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()  On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog:  [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701]   ESR = 0x0000000096000007 [232066.588862]   EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084]   SET = 0, FnV = 0 [232066.589216]   EA = 0, S1PTW = 0 [232066.589340]   FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683]   ISV = 0, ISS = 0x00000007 [232066.589842]   CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052]  vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\\x93\\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointer before dereferencing se  [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)","status":"published","published":"2024-11-01T11:07:47Z","modified":"2026-08-18T01:17:36.529649285Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2322","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\niommu/vt-d: Fix double list_add when enabling VMD in scalable mode\r\n\r\nWhen enabling VMD and IOMMU scalable mode, the following kernel panic\ncall trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids\nCPU) during booting:\r\n\r\npci 0000:59:00.5: Adding to iommu group 42\n...\nvmd 0000:59:00.5: PCI host bridge to bus 10000:80\npci 10000:80:01.0: [8086:352a] type 01 class 0x060400\npci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:01.0: enabling Extended Tags\npci 10000:80:01.0: PME# supported from D0 D3hot D3cold\npci 10000:80:01.0: DMAR: Setup RID2PASID failed\npci 10000:80:01.0: Failed to add to iommu group 42: -16\npci 10000:80:03.0: [8086:352b] type 01 class 0x060400\npci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:03.0: enabling Extended Tags\npci 10000:80:03.0: PME# supported from D0 D3hot D3cold\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:29!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7\nHardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022\nWorkqueue: events work_for_cpu_fn\nRIP: 0010:__list_add_valid.cold+0x26/0x3f\nCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f\n      0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1\n      fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9\n      9e e8 8b b1 fe\nRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8\nRDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20\nRBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888\nR10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0\nR13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70\nFS:  0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n intel_pasid_alloc_table+0x9c/0x1d0\n dmar_insert_one_dev_info+0x423/0x540\n ? device_to_iommu+0x12d/0x2f0\n intel_iommu_attach_device+0x116/0x290\n __iommu_attach_device+0x1a/0x90\n iommu_group_add_device+0x190/0x2c0\n __iommu_probe_device+0x13e/0x250\n iommu_probe_device+0x24/0x150\n iommu_bus_notifier+0x69/0x90\n blocking_notifier_call_chain+0x5a/0x80\n device_add+0x3db/0x7b0\n ? arch_memremap_can_ram_remap+0x19/0x50\n ? memremap+0x75/0x140\n pci_device_add+0x193/0x1d0\n pci_scan_single_device+0xb9/0xf0\n pci_scan_slot+0x4c/0x110\n pci_scan_child_bus_extend+0x3a/0x290\n vmd_enable_domain.constprop.0+0x63e/0x820\n vmd_probe+0x163/0x190\n local_pci_probe+0x42/0x80\n work_for_cpu_fn+0x13/0x20\n process_one_work+0x1e2/0x3b0\n worker_thread+0x1c4/0x3a0\n ? rescuer_thread+0x370/0x370\n kthread+0xc7/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---\n...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n---[ end Kernel panic - not syncing: Fatal exception ]---\r\n\r\nThe following \u0026apos;lspci\u0026apos; output shows devices \u0026apos;10000:80:*\u0026apos; are subdevices of\nthe VMD device 0000:59:00.5:\r\n\r\n  $ lspci\n  ...\n  0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)\n  ...\n  10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)\n  10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)\n  10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)\n  10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)\n  10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]\n  10000:82:00\n---truncated---(CVE-2022-48916)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: mt7621: Add sentinel to quirks table  Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call.  This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in:  commit 7c18b64bba3b (\u0026quot;mips: ralink: mt7621: do not use kzalloc too early\u0026quot;)  Fix it by adding the required sentinel.(CVE-2022-48952)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  memcg: fix possible use-after-free in memcg_write_event_control()  memcg_write_event_control() accesses the dentry-\u0026gt;d_name of the specified control fd to route the write call.  As a cgroup interface file can\u0026apos;t be renamed, it\u0026apos;s safe to access d_name as long as the specified file is a regular cgroup file.  Also, as these cgroup interface files can\u0026apos;t be removed before the directory, it\u0026apos;s safe to access the parent too.  Prior to 347c4a874710 (\u0026quot;memcg: remove cgroup_event-\u0026gt;cft\u0026quot;), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses.  The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through.  With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free\u0026apos;s.  Fix the bug by resurrecting the file type check in __file_cft().  Now that cgroupfs is implemented through kernfs, checking the file operations needs to go through a layer of indirection.  Instead, let\u0026apos;s check the superblock and dentry type.(CVE-2022-48988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()  Handle memory allocation failure from nci_skb_alloc() (calling alloc_skb()) to avoid possible NULL pointer dereference.(CVE-2023-52919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: module: prevent NULL pointer dereference in vsnprintf()\r\n\r\nIn of_modalias(), we can get passed the str and len parameters which would\ncause a kernel oops in vsnprintf() since it only allows passing a NULL ptr\nwhen the length is also 0. Also, we need to filter out the negative values\nof the len parameter as these will result in a really huge buffer since\nsnprintf() takes size_t parameter while ours is ssize_t...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the Svace static\nanalysis tool.(CVE-2024-35878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: xilinx_dpdma: Fix locking\r\n\r\nThere are several places where either chan-\u0026gt;lock or chan-\u0026gt;vchan.lock was\nnot held. Add appropriate locking. This fixes lockdep warnings like\r\n\r\n[   31.077578] ------------[ cut here ]------------\n[   31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.077953] Modules linked in:\n[   31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98\n[   31.078102] Hardware name: xlnx,zynqmp (DT)\n[   31.078169] Workqueue: events_unbound deferred_probe_work_func\n[   31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0\n[   31.078550] sp : ffffffc083bb2e10\n[   31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168\n[   31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480\n[   31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000\n[   31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000\n[   31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\n[   31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001\n[   31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def\n[   31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516\n[   31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff\n[   31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000\n[   31.080307] Call trace:\n[   31.080340]  xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.080518]  xilinx_dpdma_issue_pending+0x11c/0x120\n[   31.080595]  zynqmp_disp_layer_update+0x180/0x3ac\n[   31.080712]  zynqmp_dpsub_plane_atomic_update+0x11c/0x21c\n[   31.080825]  drm_atomic_helper_commit_planes+0x20c/0x684\n[   31.080951]  drm_atomic_helper_commit_tail+0x5c/0xb0\n[   31.081139]  commit_tail+0x234/0x294\n[   31.081246]  drm_atomic_helper_commit+0x1f8/0x210\n[   31.081363]  drm_atomic_commit+0x100/0x140\n[   31.081477]  drm_client_modeset_commit_atomic+0x318/0x384\n[   31.081634]  drm_client_modeset_commit_locked+0x8c/0x24c\n[   31.081725]  drm_client_modeset_commit+0x34/0x5c\n[   31.081812]  __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168\n[   31.081899]  drm_fb_helper_set_par+0x50/0x70\n[   31.081971]  fbcon_init+0x538/0xc48\n[   31.082047]  visual_init+0x16c/0x23c\n[   31.082207]  do_bind_con_driver.isra.0+0x2d0/0x634\n[   31.082320]  do_take_over_console+0x24c/0x33c\n[   31.082429]  do_fbcon_takeover+0xbc/0x1b0\n[   31.082503]  fbcon_fb_registered+0x2d0/0x34c\n[   31.082663]  register_framebuffer+0x27c/0x38c\n[   31.082767]  __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c\n[   31.082939]  drm_fb_helper_initial_config+0x50/0x74\n[   31.083012]  drm_fbdev_dma_client_hotplug+0xb8/0x108\n[   31.083115]  drm_client_register+0xa0/0xf4\n[   31.083195]  drm_fbdev_dma_setup+0xb0/0x1cc\n[   31.083293]  zynqmp_dpsub_drm_init+0x45c/0x4e0\n[   31.083431]  zynqmp_dpsub_probe+0x444/0x5e0\n[   31.083616]  platform_probe+0x8c/0x13c\n[   31.083713]  really_probe+0x258/0x59c\n[   31.083793]  __driver_probe_device+0xc4/0x224\n[   31.083878]  driver_probe_device+0x70/0x1c0\n[   31.083961]  __device_attach_driver+0x108/0x1e0\n[   31.084052]  bus_for_each_drv+0x9c/0x100\n[   31.084125]  __device_attach+0x100/0x298\n[   31.084207]  device_initial_probe+0x14/0x20\n[   31.084292]  bus_probe_device+0xd8/0xdc\n[   31.084368]  deferred_probe_work_func+0x11c/0x180\n[   31.084451]  process_one_work+0x3ac/0x988\n[   31.084643]  worker_thread+0x398/0x694\n[   31.084752]  kthread+0x1bc/0x1c0\n[   31.084848]  ret_from_fork+0x10/0x20\n[   31.084932] irq event stamp: 64549\n[   31.084970] hardirqs last  enabled at (64548): [\u0026lt;ffffffc081adf35c\u0026gt;] _raw_spin_unlock_irqrestore+0x80/0x90\n[   31.085157]\n---truncated---(CVE-2024-35990)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()\r\n\r\nsyzbot reported that nf_reinject() could be called without rcu_read_lock() :\r\n\r\nWARNING: suspicious RCU usage\n6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted\r\n\r\nnet/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!\r\n\r\nother info that might help us debug this:\r\n\r\nrcu_scheduler_active = 2, debug_locks = 1\n2 locks held by syz-executor.4/13427:\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172\r\n\r\nstack backtrace:\nCPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n  nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]\n  nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397\n  nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]\n  instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172\n  rcu_do_batch kernel/rcu/tree.c:2196 [inline]\n  rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471\n  handle_softirqs+0x2d6/0x990 kernel/softirq.c:554\n  __do_softirq kernel/softirq.c:588 [inline]\n  invoke_softirq kernel/softirq.c:428 [inline]\n  __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637\n  irq_exit_rcu+0x9/0x30 kernel/softirq.c:649\n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;(CVE-2024-36286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoundwire: cadence: fix invalid PDI offset\r\n\r\nFor some reason, we add an offset to the PDI, presumably to skip the\nPDI0 and PDI1 which are reserved for BPT.\r\n\r\nThis code is however completely wrong and leads to an out-of-bounds\naccess. We were just lucky so far since we used only a couple of PDIs\nand remained within the PDI array bounds.\r\n\r\nA Fixes: tag is not provided since there are no known platforms where\nthe out-of-bounds would be accessed, and the initial code had problems\nas well.\r\n\r\nA follow-up patch completely removes this useless offset.(CVE-2024-38635)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: prevent pt_regs corruption for secondary idle threads\r\n\r\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\r\n\r\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\u0026quot;riscv: prevent stack corruption by reserving task_pt_regs(p) early\u0026quot;).\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.(CVE-2024-38667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexfat: fix potential deadlock on __exfat_get_dentry_set\r\n\r\nWhen accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array\nis allocated in __exfat_get_entry_set. The problem is that the bh-array is\nallocated with GFP_KERNEL. It does not make sense. In the following cases,\na deadlock for sbi-\u0026gt;s_lock between the two processes may occur.\r\n\r\n       CPU0                CPU1\n       ----                ----\n  kswapd\n   balance_pgdat\n    lock(fs_reclaim)\n                      exfat_iterate\n                       lock(\u0026amp;sbi-\u0026gt;s_lock)\n                       exfat_readdir\n                        exfat_get_uniname_from_ext_entry\n                         exfat_get_dentry_set\n                          __exfat_get_dentry_set\n                           kmalloc_array\n                            ...\n                            lock(fs_reclaim)\n    ...\n    evict\n     exfat_evict_inode\n      lock(\u0026amp;sbi-\u0026gt;s_lock)\r\n\r\nTo fix this, let\u0026apos;s allocate bh-array with GFP_NOFS.(CVE-2024-42315)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/client: fix null pointer dereference in drm_client_modeset_probe\r\n\r\nIn drm_client_modeset_probe(), the return value of drm_mode_duplicate() is\nassigned to modeset-\u0026gt;mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: only decrement add_addr_accepted for MPJ req\r\n\r\nAdding the following warning ...\r\n\r\n  WARN_ON_ONCE(msk-\u0026gt;pm.add_addr_accepted == 0)\r\n\r\n... before decrementing the add_addr_accepted counter helped to find a\nbug when running the \u0026quot;remove single subflow\u0026quot; subtest from the\nmptcp_join.sh selftest.\r\n\r\nRemoving a \u0026apos;subflow\u0026apos; endpoint will first trigger a RM_ADDR, then the\nsubflow closure. Before this patch, and upon the reception of the\nRM_ADDR, the other peer will then try to decrement this\nadd_addr_accepted. That\u0026apos;s not correct because the attached subflows have\nnot been created upon the reception of an ADD_ADDR.\r\n\r\nA way to solve that is to decrement the counter only if the attached\nsubflow was an MP_JOIN to a remote id that was not 0, and initiated by\nthe host receiving the RM_ADDR.(CVE-2024-45009)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: cmd-db: Map shared memory as WC, not WB\r\n\r\nLinux does not write into cmd-db region. This region of memory is write\nprotected by XPU. XPU may sometime falsely detect clean cache eviction\nas \u0026quot;write\u0026quot; into the write protected region leading to secure interrupt\nwhich causes an endless loop somewhere in Trust Zone.\r\n\r\nThe only reason it is working right now is because Qualcomm Hypervisor\nmaps the same region as Non-Cacheable memory in Stage 2 translation\ntables. The issue manifests if we want to use another hypervisor (like\nXen or KVM), which does not know anything about those specific mappings.\r\n\r\nChanging the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC\nremoves dependency on correct mappings in Stage 2 tables. This patch\nfixes the issue by updating the mapping to MEMREMAP_WC.\r\n\r\nI tested this on SA8155P with Xen.(CVE-2024-46689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS\r\n\r\nGrab kvm-\u0026gt;srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\r\n\r\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU.  I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems.  Acquiring SRCU isn\u0026apos;t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\r\n\r\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\r\n\r\n other info that might help us debug this:\r\n\r\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n  #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\r\n\r\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x7f/0x90\n  lockdep_rcu_suspicious+0x13f/0x1a0\n  kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n  kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n  nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n  load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n  vmx_leave_nested+0x30/0x40 [kvm_intel]\n  kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n  kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n  ? mark_held_locks+0x49/0x70\n  ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n  ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  ? lock_acquire+0xba/0x2d0\n  ? find_held_lock+0x2b/0x80\n  ? do_user_addr_fault+0x40c/0x6f0\n  ? lock_release+0xb7/0x270\n  __x64_sys_ioctl+0x82/0xb0\n  do_syscall_64+0x6c/0x170\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n  \u0026lt;/TASK\u0026gt;(CVE-2024-46830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[   36.926103] ==================================================================\n[   36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[   36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[   36.946721]\n[   36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[   36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[   36.961260] Call trace:\n[   36.963723]  dump_backtrace+0x90/0xe8\n[   36.967414]  show_stack+0x18/0x24\n[   36.970749]  dump_stack_lvl+0x78/0x90\n[   36.974451]  print_report+0x114/0x5cc\n[   36.978151]  kasan_report+0xa4/0xf0\n[   36.981670]  __asan_report_load_n_noabort+0x1c/0x28\n[   36.986587]  nxp_fspi_exec_op+0x26ec/0x2838\n[   36.990800]  spi_mem_exec_op+0x8ec/0xd30\n[   36.994762]  spi_mem_no_dirmap_read+0x190/0x1e0\n[   36.999323]  spi_mem_dirmap_write+0x238/0x32c\n[   37.003710]  spi_nor_write_data+0x220/0x374\n[   37.007932]  spi_nor_write+0x110/0x2e8\n[   37.011711]  mtd_write_oob_std+0x154/0x1f0\n[   37.015838]  mtd_write_oob+0x104/0x1d0\n[   37.019617]  mtd_write+0xb8/0x12c\n[   37.022953]  mtdchar_write+0x224/0x47c\n[   37.026732]  vfs_write+0x1e4/0x8c8\n[   37.030163]  ksys_write+0xec/0x1d0\n[   37.033586]  __arm64_sys_write+0x6c/0x9c\n[   37.037539]  invoke_syscall+0x6c/0x258\n[   37.041327]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.046244]  do_el0_svc+0x44/0x5c\n[   37.049589]  el0_svc+0x38/0x78\n[   37.052681]  el0t_64_sync_handler+0x13c/0x158\n[   37.057077]  el0t_64_sync+0x190/0x194\n[   37.060775]\n[   37.062274] Allocated by task 455:\n[   37.065701]  kasan_save_stack+0x2c/0x54\n[   37.069570]  kasan_save_track+0x20/0x3c\n[   37.073438]  kasan_save_alloc_info+0x40/0x54\n[   37.077736]  __kasan_kmalloc+0xa0/0xb8\n[   37.081515]  __kmalloc_noprof+0x158/0x2f8\n[   37.085563]  mtd_kmalloc_up_to+0x120/0x154\n[   37.089690]  mtdchar_write+0x130/0x47c\n[   37.093469]  vfs_write+0x1e4/0x8c8\n[   37.096901]  ksys_write+0xec/0x1d0\n[   37.100332]  __arm64_sys_write+0x6c/0x9c\n[   37.104287]  invoke_syscall+0x6c/0x258\n[   37.108064]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.112972]  do_el0_svc+0x44/0x5c\n[   37.116319]  el0_svc+0x38/0x78\n[   37.119401]  el0t_64_sync_handler+0x13c/0x158\n[   37.123788]  el0t_64_sync+0x190/0x194\n[   37.127474]\n[   37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[   37.128977]  which belongs to the cache kmalloc-8 of size 8\n[   37.141177] The buggy address is located 0 bytes inside of\n[   37.141177]  allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[   37.153465]\n[   37.154971] The buggy address belongs to the physical page:\n[   37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[   37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[   37.175149] page_type: 0xfdffffff(slab)\n[   37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[   37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[   37.194553] page dumped because: kasan: bad access detected\n[   37.200144]\n[   37.201647] Memory state around the buggy address:\n[   37.206460]  ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[   37.213701]  ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[   37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[   37.228186]                                ^\n[   37.232473]  ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.239718]  ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix state management in error path of log writing function\r\n\r\nAfter commit a694291a6211 (\u0026quot;nilfs2: separate wait function from\nnilfs_segctor_write\u0026quot;) was applied, the log writing function\nnilfs_segctor_do_construct() was able to issue I/O requests continuously\neven if user data blocks were split into multiple logs across segments,\nbut two potential flaws were introduced in its error handling.\r\n\r\nFirst, if nilfs_segctor_begin_construction() fails while creating the\nsecond or subsequent logs, the log writing function returns without\ncalling nilfs_segctor_abort_construction(), so the writeback flag set on\npages/folios will remain uncleared.  This causes page cache operations to\nhang waiting for the writeback flag.  For example,\ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when\nan inode is evicted from memory, will hang.\r\n\r\nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. \nAs a result, if the next log write involves checkpoint creation, that\u0026apos;s\nfine, but if a partial log write is performed that does not, inodes with\nNILFS_I_COLLECTED set are erroneously removed from the \u0026quot;sc_dirty_files\u0026quot;\nlist, and their data and b-tree blocks may not be written to the device,\ncorrupting the block mapping.\r\n\r\nFix these issues by uniformly calling nilfs_segctor_abort_construction()\non failure of each step in the loop in nilfs_segctor_do_construct(),\nhaving it clean up logs and segment usages according to progress, and\ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure\nthat the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: check skb is non-NULL in tcp_rto_delta_us()  We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases:  Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: return -EINVAL when namelen is 0  When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered.  [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205]  dump_stack+0x9a/0xd0 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  __kasan_report.cold+0x34/0x84 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  kasan_report+0x3a/0x50 [ T1205]  nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  ? nfsd4_release_lockowner+0x410/0x410 [ T1205]  cld_pipe_downcall+0x5ca/0x760 [ T1205]  ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205]  ? down_write_killable_nested+0x170/0x170 [ T1205]  ? avc_policy_seqno+0x28/0x40 [ T1205]  ? selinux_file_permission+0x1b4/0x1e0 [ T1205]  rpc_pipe_write+0x84/0xb0 [ T1205]  vfs_write+0x143/0x520 [ T1205]  ksys_write+0xc9/0x170 [ T1205]  ? __ia32_sys_read+0x50/0x50 [ T1205]  ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205]  ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205]  do_syscall_64+0x33/0x40 [ T1205]  entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ==================================================================  Fix it by checking namelen.(CVE-2024-47692)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds  In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num.  This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sock_map: Add a cond_resched() in sock_hash_free()  Several syzbot soft lockup reports all have in common sock_hash_free()  If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the  dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function.  This fix prevents a potential null pointer dereference error.  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386)  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c     373 bool dcn30_set_output_transfer_func(struct dc *dc,     374                                 struct pipe_ctx *pipe_ctx,     375                                 const struct dc_stream_state *stream)     376 {     377         int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst;     378         struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc;     379         const struct pwl_params *params = NULL;     380         bool ret = false;     381     382         /* program OGAM or 3DLUT only for the top pipe*/     383         if (pipe_ctx-\u0026gt;top_pipe == NULL) {     384                 /*program rmu shaper and 3dlut in MPC*/     385                 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream);     386                 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) {                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL      387                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL)     388                                 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl;     389                         else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type ==     390                                         TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp;     391                                         cm3_helper_translate_curve_to_hw_format(     392                                         \u0026amp;stream-\u0026gt;out_transfer_func,     393                                         \u0026amp;mpc-\u0026gt;blender_params, false))     394                                 params = \u0026amp;mpc-\u0026gt;blender_params;     395                          /* there are no ROM LUTs in OUTGAM */     396                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED)     397                                 BREAK_TO_DEBUGGER();     398                 }     399         }     400 --\u0026gt; 401         mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params);                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash      402         return ret;     403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled  Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold.  This was discovered through the lock debugging, and the corresponding log is as follows:  raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace:  warn_bogus_irq_restore+0x30/0x40  _raw_spin_unlock_irqrestore+0x84/0xc8  add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2]  hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2]  hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2]  create_qp+0x138/0x258  ib_create_qp_kernel+0x50/0xe8  create_mad_qp+0xa8/0x128  ib_mad_port_open+0x218/0x448  ib_mad_init_device+0x70/0x1f8  add_client_context+0xfc/0x220  enable_device_and_get+0xd0/0x140  ib_register_device.part.0+0xf4/0x1c8  ib_register_device+0x34/0x50  hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2]  hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2]  __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2]  hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2](CVE-2024-47735)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: call cache_put if xdr_reserve_space returns NULL  If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get.  Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential oob read in nilfs_btree_check_delete()  The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.  This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself.  However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Fix a race during cpuhp processing  There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally:  ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x7c/0x110  ? debug_print_object+0x7d/0xb0  ? report_bug+0xf1/0x1d0  ? prb_read_valid+0x17/0x20  ? handle_bug+0x3f/0x70  ? exc_invalid_op+0x13/0x60  ? asm_exc_invalid_op+0x16/0x20  ? debug_print_object+0x7d/0xb0  ? debug_print_object+0x7d/0xb0  ? __pfx_timerlat_irq+0x10/0x10  __debug_object_init+0x110/0x150  hrtimer_init+0x1d/0x60  timerlat_main+0xab/0x2d0  ? __pfx_timerlat_main+0x10/0x10  kthread+0xb7/0xe0  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2d/0x40  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt; ```  After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU:  T1                       | T2 [CPUHP_ONLINE]           | cpu_device_down() osnoise_hotplug_workfn() |                          |     cpus_write_lock()                          |     takedown_cpu(1)                          |     cpus_write_unlock() [CPUHP_OFFLINE]          |     cpus_read_lock()     |     start_kthread(1)     |     cpus_read_unlock()   |  To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: wait for fixup workers before stopping cleaner kthread during umount  During unmount, at close_ctree(), we have the following steps in this order:  1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically    halts its execution (wake ups against it work but do nothing);  2) We stop the cleaner kthread - this results in freeing the respective    struct task_struct;  3) We call btrfs_stop_all_workers() which waits for any jobs running in all    the work queues and then free the work queues.  Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources.  Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs.  The stack traces reported by syzbot were the following:    BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065   Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52    CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024   Workqueue: btrfs-fixup btrfs_work_helper   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120    print_address_description mm/kasan/report.c:377 [inline]    print_report+0x169/0x550 mm/kasan/report.c:488    kasan_report+0x143/0x180 mm/kasan/report.c:601    __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065    lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]    _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162    class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]    try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154    btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842    btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314    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;    Allocated by task 2:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    unpoison_slab_object mm/kasan/common.c:319 [inline]    __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345    kasan_slab_alloc include/linux/kasan.h:247 [inline]    slab_post_alloc_hook mm/slub.c:4086 [inline]    slab_alloc_node mm/slub.c:4135 [inline]    kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187    alloc_task_struct_node kernel/fork.c:180 [inline]    dup_task_struct+0x57/0x8c0 kernel/fork.c:1107    copy_process+0x5d1/0x3d50 kernel/fork.c:2206    kernel_clone+0x223/0x880 kernel/fork.c:2787    kernel_thread+0x1bc/0x240 kernel/fork.c:2849    create_kthread kernel/kthread.c:412 [inline]    kthreadd+0x60d/0x810 kernel/kthread.c:765    ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244    Freed by task 61:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579    poison_slab_object mm/kasan/common.c:247 [inline]    __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264    kasan_slab_free include/linux/kasan.h:230 [inline]    slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix a NULL pointer dereference when failed to start a new trasacntion  [BUG] Syzbot reported a NULL pointer dereference with the following crash:    FAULT_INJECTION: forcing a failure.    start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676    prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642    relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678   ...   BTRFS info (device loop0): balance: ended with status: -12   Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI   KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667]   RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926   Call Trace:    \u0026lt;TASK\u0026gt;    commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496    btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430    del_balance_item fs/btrfs/volumes.c:3678 [inline]    reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742    btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574    btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:907 [inline]    __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893    do_syscall_x64 arch/x86/entry/common.c:52 [inline]    do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83    entry_SYSCALL_64_after_hwframe+0x77/0x7f  [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL.  Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree.  However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume.  Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots().  That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference.  [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree.  That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Initialize get_bytes_per_element\u0026apos;s default to 1  Variables, used as denominators and maybe not assigned to other values, should not be 0. bytes_per_element_y \u0026amp; bytes_per_element_c are initialized by get_bytes_per_element() which should never return 0.  This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in degamma hardware format translation  Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color  management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the  number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: check if leafidx greater than num leaves per dmap tree  syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf.  Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uaf in dbFreeBits  [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216  CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  __mutex_lock_common kernel/locking/mutex.c:587 [inline]  __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752  dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390  dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]  dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409  dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650  jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100  jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  Freed by task 5218:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579  poison_slab_object+0xe0/0x150 mm/kasan/common.c:240  __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2252 [inline]  slab_free mm/slub.c:4473 [inline]  kfree+0x149/0x360 mm/slub.c:4594  dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278  jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247  jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454  reconfigure_super+0x445/0x880 fs/super.c:1083  vfs_cmd_reconfigure fs/fsopen.c:263 [inline]  vfs_fsconfig_locked fs/fsopen.c:292 [inline]  __do_sys_fsconfig fs/fsopen.c:473 [inline]  __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf.  Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error if set_output_gamma is null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/ioapic: Handle allocation failures gracefully  Breno observed panics when using failslab under certain conditions during runtime:     can not alloc irq_pin_list (-1,0,20)    Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed     panic+0x4e9/0x590    mp_irqdomain_alloc+0x9ab/0xa80    irq_domain_alloc_irqs_locked+0x25d/0x8d0    __irq_domain_alloc_irqs+0x80/0x110    mp_map_pin_to_irq+0x645/0x890    acpi_register_gsi_ioapic+0xe6/0x150    hpet_open+0x313/0x480  That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed.  The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode.  Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error  In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain:  ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace:  \u0026lt;TASK\u0026gt;  add_transaction_credits+0x5d1/0x5e0  start_this_handle+0x1ef/0x6a0  jbd2__journal_start+0x18b/0x340  ext4_dirty_inode+0x5d/0xb0  __mark_inode_dirty+0xe4/0x5d0  generic_update_time+0x60/0x70 [...] ============================================  So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways.  Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: remove unreasonable unlock in ocfs2_read_blocks  Patch series \u0026quot;Misc fixes for ocfs2_read_blocks\u0026quot;, v5.  This series contains 2 fixes for ocfs2_read_blocks().  The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks().  The second patch fixes an issue reported by Heming Zhao when reviewing above fix.   This patch (of 2):  There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: cancel dqi_sync_work before freeing oinfo  ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled:  ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c  This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first.  BTW, return status instead of -1 when .read_file_info fails.(CVE-2024-49966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 color transformation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Limit the number of concurrent async COPY operations  Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.  Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.  An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.  If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume  In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.  This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks.  Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: fnic: Move flush_work initialization out of if block  After commit 379a58caa199 (\u0026quot;scsi: fnic: Move fnic_fnic_flush_tx() to a work queue\u0026quot;), it can happen that a work item is sent to an uninitialized work queue.  This may has the effect that the item being queued is never actually queued, and any further actions depending on it will not proceed.  The following warning is observed while the fnic driver is loaded:  kernel: WARNING: CPU: 11 PID: 0 at ../kernel/workqueue.c:1524 __queue_work+0x373/0x410 kernel:  \u0026lt;IRQ\u0026gt; kernel:  queue_work_on+0x3a/0x50 kernel:  fnic_wq_copy_cmpl_handler+0x54a/0x730 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  fnic_isr_msix_wq_copy+0x2d/0x60 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  __handle_irq_event_percpu+0x36/0x1a0 kernel:  handle_irq_event_percpu+0x30/0x70 kernel:  handle_irq_event+0x34/0x60 kernel:  handle_edge_irq+0x7e/0x1a0 kernel:  __common_interrupt+0x3b/0xb0 kernel:  common_interrupt+0x58/0xa0 kernel:  \u0026lt;/IRQ\u0026gt;  It has been observed that this may break the rediscovery of Fibre Channel devices after a temporary fabric failure.  This patch fixes it by moving the work queue initialization out of an if block in fnic_probe().(CVE-2024-50025)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: do not delay dst_entries_add() in dst_release()  dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy()  Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy()  dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already.  Decrementing the number of dsts must happen sooner.  Notes:  1) in CONFIG_XFRM case, dst_destroy() can call    dst_release_immediate(child), this might also cause UAF    if the child does not have DST_NOCOUNT set.    IPSEC maintainers might take a look and see how to address this.  2) There is also discussion about removing this count of dst,    which might happen in future kernels.(CVE-2024-50036)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()  On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog:  [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701]   ESR = 0x0000000096000007 [232066.588862]   EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084]   SET = 0, FnV = 0 [232066.589216]   EA = 0, S1PTW = 0 [232066.589340]   FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683]   ISV = 0, ISS = 0x00000007 [232066.589842]   CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052]  vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\\x93\\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointer before dereferencing se  [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)","status":"published","published":"2024-11-01T11:07:48Z","modified":"2026-08-18T01:18:37.533351967Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2323","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:  udf: Fix preallocation discarding at indirect extent boundary  When preallocation extent is the first one in the extent block, the code would corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid some code duplication.(CVE-2022-48946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFC: nci: Bounds check struct nfc_target arrays  While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported:    memcpy: detected field-spanning write (size 129) of single field \u0026quot;target-\u0026gt;sensf_res\u0026quot; at net/nfc/nci/ntf.c:260 (size 18)  This appears to be a legitimate lack of bounds checking in nci_add_new_protocol(). Add the missing checks.(CVE-2022-48967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpio: amd8111: Fix PCI device reference count leak  for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL.  If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() after the \u0026apos;out\u0026apos; label. Since pci_dev_put() can handle NULL input parameter, there is no problem for the \u0026apos;Device not found\u0026apos; branch. For the normal path, add pci_dev_put() in amd_gpio_exit().(CVE-2022-48973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event  With clang\u0026apos;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed.  seq_copy_in_user() and seq_copy_in_kernel() did not have prototypes matching snd_seq_dump_func_t. Adjust this and remove the casts. There are not resulting binary output differences.  This was found as a result of Clang\u0026apos;s new -Wcast-function-type-strict flag, which is more sensitive than the simpler -Wcast-function-type, which only checks for type width mismatches.(CVE-2022-48994)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()  Syzbot reported a null-ptr-deref bug:   NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP  frequency \u0026lt; 30 seconds  general protection fault, probably for non-canonical address  0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN  KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]  CPU: 1 PID: 3603 Comm: segctord Not tainted  6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0  Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google  10/11/2022  RIP: 0010:nilfs_palloc_commit_free_entry+0xe5/0x6b0  fs/nilfs2/alloc.c:608  Code: 00 00 00 00 fc ff df 80 3c 02 00 0f 85 cd 05 00 00 48 b8 00 00 00  00 00 fc ff df 4c 8b 73 08 49 8d 7e 10 48 89 fa 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02  00 0f 85 26 05 00 00 49 8b 46 10 be a6 00 00 00 48 c7 c7  RSP: 0018:ffffc90003dff830 EFLAGS: 00010212  RAX: dffffc0000000000 RBX: ffff88802594e218 RCX: 000000000000000d  RDX: 0000000000000002 RSI: 0000000000002000 RDI: 0000000000000010  RBP: ffff888071880222 R08: 0000000000000005 R09: 000000000000003f  R10: 000000000000000d R11: 0000000000000000 R12: ffff888071880158  R13: ffff88802594e220 R14: 0000000000000000 R15: 0000000000000004  FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000)  knlGS:0000000000000000  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  CR2: 00007fb1c08316a8 CR3: 0000000018560000 CR4: 0000000000350ee0  Call Trace:   \u0026lt;TASK\u0026gt;   nilfs_dat_commit_free fs/nilfs2/dat.c:114 [inline]   nilfs_dat_commit_end+0x464/0x5f0 fs/nilfs2/dat.c:193   nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236   nilfs_btree_commit_update_v+0x87/0x4a0 fs/nilfs2/btree.c:1940   nilfs_btree_commit_propagate_v fs/nilfs2/btree.c:2016 [inline]   nilfs_btree_propagate_v fs/nilfs2/btree.c:2046 [inline]   nilfs_btree_propagate+0xa00/0xd60 fs/nilfs2/btree.c:2088   nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337   nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:568   nilfs_segctor_apply_buffers+0x14a/0x470 fs/nilfs2/segment.c:1018   nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1067   nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]   nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]   nilfs_segctor_do_construct+0x12fc/0x6af0 fs/nilfs2/segment.c:2045   nilfs_segctor_construct+0x8e3/0xb30 fs/nilfs2/segment.c:2379   nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]   nilfs_segctor_thread+0x3c3/0xf30 fs/nilfs2/segment.c:2570   kthread+0x2e4/0x3a0 kernel/kthread.c:376   ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306   \u0026lt;/TASK\u0026gt;  ...  If DAT metadata file is corrupted on disk, there is a case where req-\u0026gt;pr_desc_bh is NULL and blocknr is 0 at nilfs_dat_commit_end() during a b-tree operation that cascadingly updates ancestor nodes of the b-tree, because nilfs_dat_commit_alloc() for a lower level block can initialize the blocknr on the same DAT entry between nilfs_dat_prepare_end() and nilfs_dat_commit_end().  If this happens, nilfs_dat_commit_end() calls nilfs_dat_commit_free() without valid buffer heads in req-\u0026gt;pr_desc_bh and req-\u0026gt;pr_bitmap_bh, and causes the NULL pointer dereference above in nilfs_palloc_commit_free_entry() function, which leads to a crash.  Fix this by adding a NULL check on req-\u0026gt;pr_desc_bh and req-\u0026gt;pr_bitmap_bh before nilfs_palloc_commit_free_entry() in nilfs_dat_commit_free().  This also calls nilfs_error() in that case to notify that there is a fatal flaw in the filesystem metadata and prevent further operations.(CVE-2022-49007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  hwmon: (coretemp) Check for null before removing sysfs attrs  If coretemp_add_core() gets an error then pdata-\u0026gt;core_data[indx] is already NULL and has been kfreed. Don\u0026apos;t pass that to sysfs_remove_group() as that will crash in sysfs_remove_group().  [Shortened for readability] [91854.020159] sysfs: cannot create duplicate filename \u0026apos;/devices/platform/coretemp.0/hwmon/hwmon2/temp20_label\u0026apos; \u0026lt;cpu offline\u0026gt; [91855.126115] BUG: kernel NULL pointer dereference, address: 0000000000000188 [91855.165103] #PF: supervisor read access in kernel mode [91855.194506] #PF: error_code(0x0000) - not-present page [91855.224445] PGD 0 P4D 0 [91855.238508] Oops: 0000 [#1] PREEMPT SMP PTI ... [91855.342716] RIP: 0010:sysfs_remove_group+0xc/0x80 ... [91855.796571] Call Trace: [91855.810524]  coretemp_cpu_offline+0x12b/0x1dd [coretemp] [91855.841738]  ? coretemp_cpu_online+0x180/0x180 [coretemp] [91855.871107]  cpuhp_invoke_callback+0x105/0x4b0 [91855.893432]  cpuhp_thread_fun+0x8e/0x150 ...  Fix this by checking for NULL first.(CVE-2022-49010)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails  Smatch report warning as follows:  drivers/hwmon/ibmpex.c:509 ibmpex_register_bmc() warn:   \u0026apos;\u0026amp;data-\u0026gt;list\u0026apos; not removed from list  If ibmpex_find_sensors() fails in ibmpex_register_bmc(), data will be freed, but data-\u0026gt;list will not be removed from driver_data.bmc_data, then list traversal may cause UAF.  Fix by removeing it from driver_data.bmc_data before free().(CVE-2022-49029)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: qgroup: fix sleep from invalid context bug in btrfs_qgroup_inherit()  Syzkaller reported BUG as follows:    BUG: sleeping function called from invalid context at        include/linux/sched/mm.h:274   Call Trace:    \u0026lt;TASK\u0026gt;    dump_stack_lvl+0xcd/0x134    __might_resched.cold+0x222/0x26b    kmem_cache_alloc+0x2e7/0x3c0    update_qgroup_limit_item+0xe1/0x390    btrfs_qgroup_inherit+0x147b/0x1ee0    create_subvol+0x4eb/0x1710    btrfs_mksubvol+0xfe5/0x13f0    __btrfs_ioctl_snap_create+0x2b0/0x430    btrfs_ioctl_snap_create_v2+0x25a/0x520    btrfs_ioctl+0x2a1c/0x5ce0    __x64_sys_ioctl+0x193/0x200    do_syscall_64+0x35/0x80  Fix this by calling qgroup_dirty() on @dstqgroup, and update limit item in btrfs_run_qgroups() later outside of the spinlock context.(CVE-2022-49033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()  Handle memory allocation failure from nci_skb_alloc() (calling alloc_skb()) to avoid possible NULL pointer dereference.(CVE-2023-52919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npinctrl: single: fix potential NULL dereference in pcs_get_function()\r\n\r\npinmux_generic_get_function() can return NULL and the pointer \u0026apos;function\u0026apos;\nwas dereferenced without checking against NULL. Add checking of pointer\n\u0026apos;function\u0026apos; in pcs_get_function().\r\n\r\nFound by code review.(CVE-2024-46685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof/irq: Prevent device address out-of-bounds read in interrupt map walk\r\n\r\nWhen of_irq_parse_raw() is invoked with a device address smaller than\nthe interrupt parent node (from #address-cells property), KASAN detects\nthe following out-of-bounds read when populating the initial match table\n(dyndbg=\u0026quot;func of_irq_parse_* +p\u0026quot;):\r\n\r\n  OF: of_irq_parse_one: dev=/soc@0/picasso/watchdog, index=0\n  OF:  parent=/soc@0/pci@878000000000/gpio0@17,0, intsize=2\n  OF:  intspec=4\n  OF: of_irq_parse_raw: ipar=/soc@0/pci@878000000000/gpio0@17,0, size=2\n  OF:  -\u0026gt; addrsize=3\n  ==================================================================\n  BUG: KASAN: slab-out-of-bounds in of_irq_parse_raw+0x2b8/0x8d0\n  Read of size 4 at addr ffffff81beca5608 by task bash/764\r\n\r\n  CPU: 1 PID: 764 Comm: bash Tainted: G           O       6.1.67-484c613561-nokia_sm_arm64 #1\n  Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2023.01-12.24.03-dirty 01/01/2023\n  Call trace:\n   dump_backtrace+0xdc/0x130\n   show_stack+0x1c/0x30\n   dump_stack_lvl+0x6c/0x84\n   print_report+0x150/0x448\n   kasan_report+0x98/0x140\n   __asan_load4+0x78/0xa0\n   of_irq_parse_raw+0x2b8/0x8d0\n   of_irq_parse_one+0x24c/0x270\n   parse_interrupts+0xc0/0x120\n   of_fwnode_add_links+0x100/0x2d0\n   fw_devlink_parse_fwtree+0x64/0xc0\n   device_add+0xb38/0xc30\n   of_device_add+0x64/0x90\n   of_platform_device_create_pdata+0xd0/0x170\n   of_platform_bus_create+0x244/0x600\n   of_platform_notify+0x1b0/0x254\n   blocking_notifier_call_chain+0x9c/0xd0\n   __of_changeset_entry_notify+0x1b8/0x230\n   __of_changeset_apply_notify+0x54/0xe4\n   of_overlay_fdt_apply+0xc04/0xd94\n   ...\r\n\r\n  The buggy address belongs to the object at ffffff81beca5600\n   which belongs to the cache kmalloc-128 of size 128\n  The buggy address is located 8 bytes inside of\n   128-byte region [ffffff81beca5600, ffffff81beca5680)\r\n\r\n  The buggy address belongs to the physical page:\n  page:00000000230d3d03 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1beca4\n  head:00000000230d3d03 order:1 compound_mapcount:0 compound_pincount:0\n  flags: 0x8000000000010200(slab|head|zone=2)\n  raw: 8000000000010200 0000000000000000 dead000000000122 ffffff810000c300\n  raw: 0000000000000000 0000000000200020 00000001ffffffff 0000000000000000\n  page dumped because: kasan: bad access detected\r\n\r\n  Memory state around the buggy address:\n   ffffff81beca5500: 04 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n   ffffff81beca5580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffffff81beca5600: 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n                        ^\n   ffffff81beca5680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n   ffffff81beca5700: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc\n  ==================================================================\n  OF:  -\u0026gt; got it !\r\n\r\nPrevent the out-of-bounds read by copying the device address into a\nbuffer of sufficient size.(CVE-2024-46743)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in degamma hardware format translation  Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error  In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain:  ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace:  \u0026lt;TASK\u0026gt;  add_transaction_credits+0x5d1/0x5e0  start_this_handle+0x1ef/0x6a0  jbd2__journal_start+0x18b/0x340  ext4_dirty_inode+0x5d/0xb0  __mark_inode_dirty+0xe4/0x5d0  generic_update_time+0x60/0x70 [...] ============================================  So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways.  Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: do not delay dst_entries_add() in dst_release()  dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy()  Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy()  dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already.  Decrementing the number of dsts must happen sooner.  Notes:  1) in CONFIG_XFRM case, dst_destroy() can call    dst_release_immediate(child), this might also cause UAF    if the child does not have DST_NOCOUNT set.    IPSEC maintainers might take a look and see how to address this.  2) There is also discussion about removing this count of dst,    which might happen in future kernels.(CVE-2024-50036)","status":"published","published":"2024-11-01T11:07:48Z","modified":"2026-08-18T01:17:36.558467447Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2324","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\niommu/vt-d: Fix double list_add when enabling VMD in scalable mode\r\n\r\nWhen enabling VMD and IOMMU scalable mode, the following kernel panic\ncall trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids\nCPU) during booting:\r\n\r\npci 0000:59:00.5: Adding to iommu group 42\n...\nvmd 0000:59:00.5: PCI host bridge to bus 10000:80\npci 10000:80:01.0: [8086:352a] type 01 class 0x060400\npci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:01.0: enabling Extended Tags\npci 10000:80:01.0: PME# supported from D0 D3hot D3cold\npci 10000:80:01.0: DMAR: Setup RID2PASID failed\npci 10000:80:01.0: Failed to add to iommu group 42: -16\npci 10000:80:03.0: [8086:352b] type 01 class 0x060400\npci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:03.0: enabling Extended Tags\npci 10000:80:03.0: PME# supported from D0 D3hot D3cold\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:29!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7\nHardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022\nWorkqueue: events work_for_cpu_fn\nRIP: 0010:__list_add_valid.cold+0x26/0x3f\nCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f\n      0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1\n      fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9\n      9e e8 8b b1 fe\nRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8\nRDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20\nRBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888\nR10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0\nR13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70\nFS:  0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n intel_pasid_alloc_table+0x9c/0x1d0\n dmar_insert_one_dev_info+0x423/0x540\n ? device_to_iommu+0x12d/0x2f0\n intel_iommu_attach_device+0x116/0x290\n __iommu_attach_device+0x1a/0x90\n iommu_group_add_device+0x190/0x2c0\n __iommu_probe_device+0x13e/0x250\n iommu_probe_device+0x24/0x150\n iommu_bus_notifier+0x69/0x90\n blocking_notifier_call_chain+0x5a/0x80\n device_add+0x3db/0x7b0\n ? arch_memremap_can_ram_remap+0x19/0x50\n ? memremap+0x75/0x140\n pci_device_add+0x193/0x1d0\n pci_scan_single_device+0xb9/0xf0\n pci_scan_slot+0x4c/0x110\n pci_scan_child_bus_extend+0x3a/0x290\n vmd_enable_domain.constprop.0+0x63e/0x820\n vmd_probe+0x163/0x190\n local_pci_probe+0x42/0x80\n work_for_cpu_fn+0x13/0x20\n process_one_work+0x1e2/0x3b0\n worker_thread+0x1c4/0x3a0\n ? rescuer_thread+0x370/0x370\n kthread+0xc7/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---\n...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n---[ end Kernel panic - not syncing: Fatal exception ]---\r\n\r\nThe following \u0026apos;lspci\u0026apos; output shows devices \u0026apos;10000:80:*\u0026apos; are subdevices of\nthe VMD device 0000:59:00.5:\r\n\r\n  $ lspci\n  ...\n  0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)\n  ...\n  10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)\n  10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)\n  10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)\n  10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)\n  10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]\n  10000:82:00\n---truncated---(CVE-2022-48916)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  udf: Fix preallocation discarding at indirect extent boundary  When preallocation extent is the first one in the extent block, the code would corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid some code duplication.(CVE-2022-48946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: mt7621: Add sentinel to quirks table  Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call.  This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in:  commit 7c18b64bba3b (\u0026quot;mips: ralink: mt7621: do not use kzalloc too early\u0026quot;)  Fix it by adding the required sentinel.(CVE-2022-48952)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFC: nci: Bounds check struct nfc_target arrays  While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported:    memcpy: detected field-spanning write (size 129) of single field \u0026quot;target-\u0026gt;sensf_res\u0026quot; at net/nfc/nci/ntf.c:260 (size 18)  This appears to be a legitimate lack of bounds checking in nci_add_new_protocol(). Add the missing checks.(CVE-2022-48967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpio: amd8111: Fix PCI device reference count leak  for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL.  If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() after the \u0026apos;out\u0026apos; label. Since pci_dev_put() can handle NULL input parameter, there is no problem for the \u0026apos;Device not found\u0026apos; branch. For the normal path, add pci_dev_put() in amd_gpio_exit().(CVE-2022-48973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: af_can: fix NULL pointer dereference in can_rcv_filter  Analogue to commit 8aa59e355949 (\u0026quot;can: af_can: fix NULL pointer dereference in can_rx_register()\u0026quot;) we need to check for a missing initialization of ml_priv in the receive path of CAN frames.  Since commit 4e096a18867a (\u0026quot;net: introduce CAN specific pointer in the struct net_device\u0026quot;) the check for dev-\u0026gt;type to be ARPHRD_CAN is not sufficient anymore since bonding or tun netdevices claim to be CAN devices but do not initialize ml_priv accordingly.(CVE-2022-48977)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm/gup: fix gup_pud_range() for dax  For dax pud, pud_huge() returns true on x86. So the function works as long as hugetlb is configured. However, dax doesn\u0026apos;t depend on hugetlb. Commit 414fd080d125 (\u0026quot;mm/gup: fix gup_pmd_range() for dax\u0026quot;) fixed devmap-backed huge PMDs, but missed devmap-backed huge PUDs. Fix this as well.  This fixes the below kernel panic:  general protection fault, probably for non-canonical address 0x69e7c000cc478: 0000 [#1] SMP  \u0026lt; snip \u0026gt; Call Trace: \u0026lt;TASK\u0026gt; get_user_pages_fast+0x1f/0x40 iov_iter_get_pages+0xc6/0x3b0 ? mempool_alloc+0x5d/0x170 bio_iov_iter_get_pages+0x82/0x4e0 ? bvec_alloc+0x91/0xc0 ? bio_alloc_bioset+0x19a/0x2a0 blkdev_direct_IO+0x282/0x480 ? __io_complete_rw_common+0xc0/0xc0 ? filemap_range_has_page+0x82/0xc0 generic_file_direct_write+0x9d/0x1a0 ? inode_update_time+0x24/0x30 __generic_file_write_iter+0xbd/0x1e0 blkdev_write_iter+0xb4/0x150 ? io_import_iovec+0x8d/0x340 io_write+0xf9/0x300 io_issue_sqe+0x3c3/0x1d30 ? sysvec_reschedule_ipi+0x6c/0x80 __io_queue_sqe+0x33/0x240 ? fget+0x76/0xa0 io_submit_sqes+0xe6a/0x18d0 ? __fget_light+0xd1/0x100 __x64_sys_io_uring_enter+0x199/0x880 ? __context_tracking_enter+0x1f/0x70 ? irqentry_exit_to_user_mode+0x24/0x30 ? irqentry_exit+0x1d/0x30 ? __context_tracking_exit+0xe/0x70 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7fc97c11a7be  \u0026lt; snip \u0026gt; \u0026lt;/TASK\u0026gt; ---[ end trace 48b2e0e67debcaeb ]--- RIP: 0010:internal_get_user_pages_fast+0x340/0x990  \u0026lt; snip \u0026gt; Kernel panic - not syncing: Fatal exception Kernel Offset: disabled(CVE-2022-48986)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  memcg: fix possible use-after-free in memcg_write_event_control()  memcg_write_event_control() accesses the dentry-\u0026gt;d_name of the specified control fd to route the write call.  As a cgroup interface file can\u0026apos;t be renamed, it\u0026apos;s safe to access d_name as long as the specified file is a regular cgroup file.  Also, as these cgroup interface files can\u0026apos;t be removed before the directory, it\u0026apos;s safe to access the parent too.  Prior to 347c4a874710 (\u0026quot;memcg: remove cgroup_event-\u0026gt;cft\u0026quot;), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses.  The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through.  With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free\u0026apos;s.  Fix the bug by resurrecting the file type check in __file_cft().  Now that cgroupfs is implemented through kernfs, checking the file operations needs to go through a layer of indirection.  Instead, let\u0026apos;s check the superblock and dentry type.(CVE-2022-48988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths  Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don\u0026apos;t keep accessing pages which aren\u0026apos;t mapped anymore.  Secondary MMUs don\u0026apos;t hold their own references to pages that are mirrored over, so failing to notify them can lead to page use-after-free.  I\u0026apos;m marking this as addressing an issue introduced in commit f3f0e1d2150b (\u0026quot;khugepaged: add support of collapse for tmpfs/shmem pages\u0026quot;), but most of the security impact of this only came in commit 27e1f8273113 (\u0026quot;khugepaged: enable collapse pmd for pte-mapped THP\u0026quot;), which actually omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.(CVE-2022-48991)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event  With clang\u0026apos;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed.  seq_copy_in_user() and seq_copy_in_kernel() did not have prototypes matching snd_seq_dump_func_t. Adjust this and remove the casts. There are not resulting binary output differences.  This was found as a result of Clang\u0026apos;s new -Wcast-function-type-strict flag, which is more sensitive than the simpler -Wcast-function-type, which only checks for type width mismatches.(CVE-2022-48994)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing: Free buffers when a used dynamic event is removed(CVE-2022-49006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()  Syzbot reported a null-ptr-deref bug:   NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP  frequency \u0026lt; 30 seconds  general protection fault, probably for non-canonical address  0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN  KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]  CPU: 1 PID: 3603 Comm: segctord Not tainted  6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0  Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google  10/11/2022  RIP: 0010:nilfs_palloc_commit_free_entry+0xe5/0x6b0  fs/nilfs2/alloc.c:608  Code: 00 00 00 00 fc ff df 80 3c 02 00 0f 85 cd 05 00 00 48 b8 00 00 00  00 00 fc ff df 4c 8b 73 08 49 8d 7e 10 48 89 fa 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02  00 0f 85 26 05 00 00 49 8b 46 10 be a6 00 00 00 48 c7 c7  RSP: 0018:ffffc90003dff830 EFLAGS: 00010212  RAX: dffffc0000000000 RBX: ffff88802594e218 RCX: 000000000000000d  RDX: 0000000000000002 RSI: 0000000000002000 RDI: 0000000000000010  RBP: ffff888071880222 R08: 0000000000000005 R09: 000000000000003f  R10: 000000000000000d R11: 0000000000000000 R12: ffff888071880158  R13: ffff88802594e220 R14: 0000000000000000 R15: 0000000000000004  FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000)  knlGS:0000000000000000  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  CR2: 00007fb1c08316a8 CR3: 0000000018560000 CR4: 0000000000350ee0  Call Trace:   \u0026lt;TASK\u0026gt;   nilfs_dat_commit_free fs/nilfs2/dat.c:114 [inline]   nilfs_dat_commit_end+0x464/0x5f0 fs/nilfs2/dat.c:193   nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236   nilfs_btree_commit_update_v+0x87/0x4a0 fs/nilfs2/btree.c:1940   nilfs_btree_commit_propagate_v fs/nilfs2/btree.c:2016 [inline]   nilfs_btree_propagate_v fs/nilfs2/btree.c:2046 [inline]   nilfs_btree_propagate+0xa00/0xd60 fs/nilfs2/btree.c:2088   nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337   nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:568   nilfs_segctor_apply_buffers+0x14a/0x470 fs/nilfs2/segment.c:1018   nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1067   nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]   nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]   nilfs_segctor_do_construct+0x12fc/0x6af0 fs/nilfs2/segment.c:2045   nilfs_segctor_construct+0x8e3/0xb30 fs/nilfs2/segment.c:2379   nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]   nilfs_segctor_thread+0x3c3/0xf30 fs/nilfs2/segment.c:2570   kthread+0x2e4/0x3a0 kernel/kthread.c:376   ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306   \u0026lt;/TASK\u0026gt;  ...  If DAT metadata file is corrupted on disk, there is a case where req-\u0026gt;pr_desc_bh is NULL and blocknr is 0 at nilfs_dat_commit_end() during a b-tree operation that cascadingly updates ancestor nodes of the b-tree, because nilfs_dat_commit_alloc() for a lower level block can initialize the blocknr on the same DAT entry between nilfs_dat_prepare_end() and nilfs_dat_commit_end().  If this happens, nilfs_dat_commit_end() calls nilfs_dat_commit_free() without valid buffer heads in req-\u0026gt;pr_desc_bh and req-\u0026gt;pr_bitmap_bh, and causes the NULL pointer dereference above in nilfs_palloc_commit_free_entry() function, which leads to a crash.  Fix this by adding a NULL check on req-\u0026gt;pr_desc_bh and req-\u0026gt;pr_bitmap_bh before nilfs_palloc_commit_free_entry() in nilfs_dat_commit_free().  This also calls nilfs_error() in that case to notify that there is a fatal flaw in the filesystem metadata and prevent further operations.(CVE-2022-49007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: ethernet: nixge: fix NULL dereference  In function nixge_hw_dma_bd_release() dereference of NULL pointer priv-\u0026gt;rx_bd_v is possible for the case of its allocation failure in nixge_hw_dma_bd_init().  Move for() loop with priv-\u0026gt;rx_bd_v dereference under the check for its validity.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2022-49019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails  Smatch report warning as follows:  drivers/hwmon/ibmpex.c:509 ibmpex_register_bmc() warn:   \u0026apos;\u0026amp;data-\u0026gt;list\u0026apos; not removed from list  If ibmpex_find_sensors() fails in ibmpex_register_bmc(), data will be freed, but data-\u0026gt;list will not be removed from driver_data.bmc_data, then list traversal may cause UAF.  Fix by removeing it from driver_data.bmc_data before free().(CVE-2022-49029)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  libbpf: Handle size overflow for ringbuf mmap  The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t.  So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.(CVE-2022-49030)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: qgroup: fix sleep from invalid context bug in btrfs_qgroup_inherit()  Syzkaller reported BUG as follows:    BUG: sleeping function called from invalid context at        include/linux/sched/mm.h:274   Call Trace:    \u0026lt;TASK\u0026gt;    dump_stack_lvl+0xcd/0x134    __might_resched.cold+0x222/0x26b    kmem_cache_alloc+0x2e7/0x3c0    update_qgroup_limit_item+0xe1/0x390    btrfs_qgroup_inherit+0x147b/0x1ee0    create_subvol+0x4eb/0x1710    btrfs_mksubvol+0xfe5/0x13f0    __btrfs_ioctl_snap_create+0x2b0/0x430    btrfs_ioctl_snap_create_v2+0x25a/0x520    btrfs_ioctl+0x2a1c/0x5ce0    __x64_sys_ioctl+0x193/0x200    do_syscall_64+0x35/0x80  Fix this by calling qgroup_dirty() on @dstqgroup, and update limit item in btrfs_run_qgroups() later outside of the spinlock context.(CVE-2022-49033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: imon: fix access to invalid resource for the second interface\r\n\r\nimon driver probes two USB interfaces, and at the probe of the second\ninterface, the driver assumes blindly that the first interface got\nbound with the same imon driver.  It\u0026apos;s usually true, but it\u0026apos;s still\npossible that the first interface is bound with another driver via a\nmalformed descriptor.  Then it may lead to a memory corruption, as\nspotted by syzkaller; imon driver accesses the data from drvdata as\nstruct imon_context object although it\u0026apos;s a completely different one\nthat was assigned by another driver.\r\n\r\nThis patch adds a sanity check -- whether the first interface is\nreally bound with the imon driver or not -- for avoiding the problem\nabove at the probe time.(CVE-2023-52754)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc2: fix possible NULL pointer dereference caused by driver concurrency\r\n\r\nIn _dwc2_hcd_urb_enqueue(), \u0026quot;urb-\u0026gt;hcpriv = NULL\u0026quot; is executed without\nholding the lock \u0026quot;hsotg-\u0026gt;lock\u0026quot;. In _dwc2_hcd_urb_dequeue():\r\n\r\n    spin_lock_irqsave(\u0026amp;hsotg-\u0026gt;lock, flags);\n    ...\n\tif (!urb-\u0026gt;hcpriv) {\n\t\tdev_dbg(hsotg-\u0026gt;dev, \u0026quot;## urb-\u0026gt;hcpriv is NULL ##\\n\u0026quot;);\n\t\tgoto out;\n\t}\n    rc = dwc2_hcd_urb_dequeue(hsotg, urb-\u0026gt;hcpriv); // Use urb-\u0026gt;hcpriv\n    ...\nout:\n    spin_unlock_irqrestore(\u0026amp;hsotg-\u0026gt;lock, flags);\r\n\r\nWhen _dwc2_hcd_urb_enqueue() and _dwc2_hcd_urb_dequeue() are\nconcurrently executed, the NULL check of \u0026quot;urb-\u0026gt;hcpriv\u0026quot; can be executed\nbefore \u0026quot;urb-\u0026gt;hcpriv = NULL\u0026quot;. After urb-\u0026gt;hcpriv is NULL, it can be used\nin the function call to dwc2_hcd_urb_dequeue(), which can cause a NULL\npointer dereference.\r\n\r\nThis possible bug is found by an experimental static analysis tool\ndeveloped by myself. This tool analyzes the locking APIs to extract\nfunction pairs that can be concurrently executed, and then analyzes the\ninstructions in the paired functions to identify possible concurrency\nbugs including data races and atomicity violations. The above possible\nbug is reported, when my tool analyzes the source code of Linux 6.5.\r\n\r\nTo fix this possible bug, \u0026quot;urb-\u0026gt;hcpriv = NULL\u0026quot; should be executed with\nholding the lock \u0026quot;hsotg-\u0026gt;lock\u0026quot;. After using this patch, my tool never\nreports the possible bug, with the kernelconfiguration allyesconfig for\nx86_64. Because I have no associated hardware, I cannot test the patch\nin runtime testing, and just verify it according to the code logic.(CVE-2023-52855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()  Handle memory allocation failure from nci_skb_alloc() (calling alloc_skb()) to avoid possible NULL pointer dereference.(CVE-2023-52919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: Revert \u0026quot;scsi: fcoe: Fix potential deadlock on \u0026amp;fip-\u0026gt;ctlr_lock\u0026quot;\r\n\r\nThis reverts commit 1a1975551943f681772720f639ff42fbaa746212.\r\n\r\nThis commit causes interrupts to be lost for FCoE devices, since it changed\nsping locks from \u0026quot;bh\u0026quot; to \u0026quot;irqsave\u0026quot;.\r\n\r\nInstead, a work queue should be used, and will be addressed in a separate\ncommit.(CVE-2024-26917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: module: prevent NULL pointer dereference in vsnprintf()\r\n\r\nIn of_modalias(), we can get passed the str and len parameters which would\ncause a kernel oops in vsnprintf() since it only allows passing a NULL ptr\nwhen the length is also 0. Also, we need to filter out the negative values\nof the len parameter as these will result in a really huge buffer since\nsnprintf() takes size_t parameter while ours is ssize_t...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the Svace static\nanalysis tool.(CVE-2024-35878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: xilinx_dpdma: Fix locking\r\n\r\nThere are several places where either chan-\u0026gt;lock or chan-\u0026gt;vchan.lock was\nnot held. Add appropriate locking. This fixes lockdep warnings like\r\n\r\n[   31.077578] ------------[ cut here ]------------\n[   31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.077953] Modules linked in:\n[   31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98\n[   31.078102] Hardware name: xlnx,zynqmp (DT)\n[   31.078169] Workqueue: events_unbound deferred_probe_work_func\n[   31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0\n[   31.078550] sp : ffffffc083bb2e10\n[   31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168\n[   31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480\n[   31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000\n[   31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000\n[   31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\n[   31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001\n[   31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def\n[   31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516\n[   31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff\n[   31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000\n[   31.080307] Call trace:\n[   31.080340]  xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.080518]  xilinx_dpdma_issue_pending+0x11c/0x120\n[   31.080595]  zynqmp_disp_layer_update+0x180/0x3ac\n[   31.080712]  zynqmp_dpsub_plane_atomic_update+0x11c/0x21c\n[   31.080825]  drm_atomic_helper_commit_planes+0x20c/0x684\n[   31.080951]  drm_atomic_helper_commit_tail+0x5c/0xb0\n[   31.081139]  commit_tail+0x234/0x294\n[   31.081246]  drm_atomic_helper_commit+0x1f8/0x210\n[   31.081363]  drm_atomic_commit+0x100/0x140\n[   31.081477]  drm_client_modeset_commit_atomic+0x318/0x384\n[   31.081634]  drm_client_modeset_commit_locked+0x8c/0x24c\n[   31.081725]  drm_client_modeset_commit+0x34/0x5c\n[   31.081812]  __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168\n[   31.081899]  drm_fb_helper_set_par+0x50/0x70\n[   31.081971]  fbcon_init+0x538/0xc48\n[   31.082047]  visual_init+0x16c/0x23c\n[   31.082207]  do_bind_con_driver.isra.0+0x2d0/0x634\n[   31.082320]  do_take_over_console+0x24c/0x33c\n[   31.082429]  do_fbcon_takeover+0xbc/0x1b0\n[   31.082503]  fbcon_fb_registered+0x2d0/0x34c\n[   31.082663]  register_framebuffer+0x27c/0x38c\n[   31.082767]  __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c\n[   31.082939]  drm_fb_helper_initial_config+0x50/0x74\n[   31.083012]  drm_fbdev_dma_client_hotplug+0xb8/0x108\n[   31.083115]  drm_client_register+0xa0/0xf4\n[   31.083195]  drm_fbdev_dma_setup+0xb0/0x1cc\n[   31.083293]  zynqmp_dpsub_drm_init+0x45c/0x4e0\n[   31.083431]  zynqmp_dpsub_probe+0x444/0x5e0\n[   31.083616]  platform_probe+0x8c/0x13c\n[   31.083713]  really_probe+0x258/0x59c\n[   31.083793]  __driver_probe_device+0xc4/0x224\n[   31.083878]  driver_probe_device+0x70/0x1c0\n[   31.083961]  __device_attach_driver+0x108/0x1e0\n[   31.084052]  bus_for_each_drv+0x9c/0x100\n[   31.084125]  __device_attach+0x100/0x298\n[   31.084207]  device_initial_probe+0x14/0x20\n[   31.084292]  bus_probe_device+0xd8/0xdc\n[   31.084368]  deferred_probe_work_func+0x11c/0x180\n[   31.084451]  process_one_work+0x3ac/0x988\n[   31.084643]  worker_thread+0x398/0x694\n[   31.084752]  kthread+0x1bc/0x1c0\n[   31.084848]  ret_from_fork+0x10/0x20\n[   31.084932] irq event stamp: 64549\n[   31.084970] hardirqs last  enabled at (64548): [\u0026lt;ffffffc081adf35c\u0026gt;] _raw_spin_unlock_irqrestore+0x80/0x90\n[   31.085157]\n---truncated---(CVE-2024-35990)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()\r\n\r\nsyzbot reported that nf_reinject() could be called without rcu_read_lock() :\r\n\r\nWARNING: suspicious RCU usage\n6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted\r\n\r\nnet/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!\r\n\r\nother info that might help us debug this:\r\n\r\nrcu_scheduler_active = 2, debug_locks = 1\n2 locks held by syz-executor.4/13427:\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172\r\n\r\nstack backtrace:\nCPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n  nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]\n  nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397\n  nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]\n  instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172\n  rcu_do_batch kernel/rcu/tree.c:2196 [inline]\n  rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471\n  handle_softirqs+0x2d6/0x990 kernel/softirq.c:554\n  __do_softirq kernel/softirq.c:588 [inline]\n  invoke_softirq kernel/softirq.c:428 [inline]\n  __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637\n  irq_exit_rcu+0x9/0x30 kernel/softirq.c:649\n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;(CVE-2024-36286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoundwire: cadence: fix invalid PDI offset\r\n\r\nFor some reason, we add an offset to the PDI, presumably to skip the\nPDI0 and PDI1 which are reserved for BPT.\r\n\r\nThis code is however completely wrong and leads to an out-of-bounds\naccess. We were just lucky so far since we used only a couple of PDIs\nand remained within the PDI array bounds.\r\n\r\nA Fixes: tag is not provided since there are no known platforms where\nthe out-of-bounds would be accessed, and the initial code had problems\nas well.\r\n\r\nA follow-up patch completely removes this useless offset.(CVE-2024-38635)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: prevent pt_regs corruption for secondary idle threads\r\n\r\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\r\n\r\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\u0026quot;riscv: prevent stack corruption by reserving task_pt_regs(p) early\u0026quot;).\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.(CVE-2024-38667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_check_dir_entry()\r\n\r\nThis adds sanity checks for ocfs2_dir_entry to make sure all members of\nocfs2_dir_entry don\u0026apos;t stray beyond valid memory region.(CVE-2024-41015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/client: fix null pointer dereference in drm_client_modeset_probe\r\n\r\nIn drm_client_modeset_probe(), the return value of drm_mode_duplicate() is\nassigned to modeset-\u0026gt;mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: cmd-db: Map shared memory as WC, not WB\r\n\r\nLinux does not write into cmd-db region. This region of memory is write\nprotected by XPU. XPU may sometime falsely detect clean cache eviction\nas \u0026quot;write\u0026quot; into the write protected region leading to secure interrupt\nwhich causes an endless loop somewhere in Trust Zone.\r\n\r\nThe only reason it is working right now is because Qualcomm Hypervisor\nmaps the same region as Non-Cacheable memory in Stage 2 translation\ntables. The issue manifests if we want to use another hypervisor (like\nXen or KVM), which does not know anything about those specific mappings.\r\n\r\nChanging the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC\nremoves dependency on correct mappings in Stage 2 tables. This patch\nfixes the issue by updating the mapping to MEMREMAP_WC.\r\n\r\nI tested this on SA8155P with Xen.(CVE-2024-46689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS\r\n\r\nGrab kvm-\u0026gt;srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\r\n\r\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU.  I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems.  Acquiring SRCU isn\u0026apos;t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\r\n\r\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\r\n\r\n other info that might help us debug this:\r\n\r\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n  #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\r\n\r\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x7f/0x90\n  lockdep_rcu_suspicious+0x13f/0x1a0\n  kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n  kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n  nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n  load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n  vmx_leave_nested+0x30/0x40 [kvm_intel]\n  kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n  kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n  ? mark_held_locks+0x49/0x70\n  ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n  ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  ? lock_acquire+0xba/0x2d0\n  ? find_held_lock+0x2b/0x80\n  ? do_user_addr_fault+0x40c/0x6f0\n  ? lock_release+0xb7/0x270\n  __x64_sys_ioctl+0x82/0xb0\n  do_syscall_64+0x6c/0x170\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n  \u0026lt;/TASK\u0026gt;(CVE-2024-46830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[   36.926103] ==================================================================\n[   36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[   36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[   36.946721]\n[   36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[   36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[   36.961260] Call trace:\n[   36.963723]  dump_backtrace+0x90/0xe8\n[   36.967414]  show_stack+0x18/0x24\n[   36.970749]  dump_stack_lvl+0x78/0x90\n[   36.974451]  print_report+0x114/0x5cc\n[   36.978151]  kasan_report+0xa4/0xf0\n[   36.981670]  __asan_report_load_n_noabort+0x1c/0x28\n[   36.986587]  nxp_fspi_exec_op+0x26ec/0x2838\n[   36.990800]  spi_mem_exec_op+0x8ec/0xd30\n[   36.994762]  spi_mem_no_dirmap_read+0x190/0x1e0\n[   36.999323]  spi_mem_dirmap_write+0x238/0x32c\n[   37.003710]  spi_nor_write_data+0x220/0x374\n[   37.007932]  spi_nor_write+0x110/0x2e8\n[   37.011711]  mtd_write_oob_std+0x154/0x1f0\n[   37.015838]  mtd_write_oob+0x104/0x1d0\n[   37.019617]  mtd_write+0xb8/0x12c\n[   37.022953]  mtdchar_write+0x224/0x47c\n[   37.026732]  vfs_write+0x1e4/0x8c8\n[   37.030163]  ksys_write+0xec/0x1d0\n[   37.033586]  __arm64_sys_write+0x6c/0x9c\n[   37.037539]  invoke_syscall+0x6c/0x258\n[   37.041327]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.046244]  do_el0_svc+0x44/0x5c\n[   37.049589]  el0_svc+0x38/0x78\n[   37.052681]  el0t_64_sync_handler+0x13c/0x158\n[   37.057077]  el0t_64_sync+0x190/0x194\n[   37.060775]\n[   37.062274] Allocated by task 455:\n[   37.065701]  kasan_save_stack+0x2c/0x54\n[   37.069570]  kasan_save_track+0x20/0x3c\n[   37.073438]  kasan_save_alloc_info+0x40/0x54\n[   37.077736]  __kasan_kmalloc+0xa0/0xb8\n[   37.081515]  __kmalloc_noprof+0x158/0x2f8\n[   37.085563]  mtd_kmalloc_up_to+0x120/0x154\n[   37.089690]  mtdchar_write+0x130/0x47c\n[   37.093469]  vfs_write+0x1e4/0x8c8\n[   37.096901]  ksys_write+0xec/0x1d0\n[   37.100332]  __arm64_sys_write+0x6c/0x9c\n[   37.104287]  invoke_syscall+0x6c/0x258\n[   37.108064]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.112972]  do_el0_svc+0x44/0x5c\n[   37.116319]  el0_svc+0x38/0x78\n[   37.119401]  el0t_64_sync_handler+0x13c/0x158\n[   37.123788]  el0t_64_sync+0x190/0x194\n[   37.127474]\n[   37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[   37.128977]  which belongs to the cache kmalloc-8 of size 8\n[   37.141177] The buggy address is located 0 bytes inside of\n[   37.141177]  allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[   37.153465]\n[   37.154971] The buggy address belongs to the physical page:\n[   37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[   37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[   37.175149] page_type: 0xfdffffff(slab)\n[   37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[   37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[   37.194553] page dumped because: kasan: bad access detected\n[   37.200144]\n[   37.201647] Memory state around the buggy address:\n[   37.206460]  ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[   37.213701]  ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[   37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[   37.228186]                                ^\n[   37.232473]  ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.239718]  ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix state management in error path of log writing function\r\n\r\nAfter commit a694291a6211 (\u0026quot;nilfs2: separate wait function from\nnilfs_segctor_write\u0026quot;) was applied, the log writing function\nnilfs_segctor_do_construct() was able to issue I/O requests continuously\neven if user data blocks were split into multiple logs across segments,\nbut two potential flaws were introduced in its error handling.\r\n\r\nFirst, if nilfs_segctor_begin_construction() fails while creating the\nsecond or subsequent logs, the log writing function returns without\ncalling nilfs_segctor_abort_construction(), so the writeback flag set on\npages/folios will remain uncleared.  This causes page cache operations to\nhang waiting for the writeback flag.  For example,\ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when\nan inode is evicted from memory, will hang.\r\n\r\nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. \nAs a result, if the next log write involves checkpoint creation, that\u0026apos;s\nfine, but if a partial log write is performed that does not, inodes with\nNILFS_I_COLLECTED set are erroneously removed from the \u0026quot;sc_dirty_files\u0026quot;\nlist, and their data and b-tree blocks may not be written to the device,\ncorrupting the block mapping.\r\n\r\nFix these issues by uniformly calling nilfs_segctor_abort_construction()\non failure of each step in the loop in nilfs_segctor_do_construct(),\nhaving it clean up logs and segment usages according to progress, and\ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure\nthat the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: check skb is non-NULL in tcp_rto_delta_us()  We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases:  Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds  In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num.  This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sock_map: Add a cond_resched() in sock_hash_free()  Several syzbot soft lockup reports all have in common sock_hash_free()  If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the  dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function.  This fix prevents a potential null pointer dereference error.  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386)  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c     373 bool dcn30_set_output_transfer_func(struct dc *dc,     374                                 struct pipe_ctx *pipe_ctx,     375                                 const struct dc_stream_state *stream)     376 {     377         int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst;     378         struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc;     379         const struct pwl_params *params = NULL;     380         bool ret = false;     381     382         /* program OGAM or 3DLUT only for the top pipe*/     383         if (pipe_ctx-\u0026gt;top_pipe == NULL) {     384                 /*program rmu shaper and 3dlut in MPC*/     385                 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream);     386                 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) {                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL      387                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL)     388                                 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl;     389                         else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type ==     390                                         TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp;     391                                         cm3_helper_translate_curve_to_hw_format(     392                                         \u0026amp;stream-\u0026gt;out_transfer_func,     393                                         \u0026amp;mpc-\u0026gt;blender_params, false))     394                                 params = \u0026amp;mpc-\u0026gt;blender_params;     395                          /* there are no ROM LUTs in OUTGAM */     396                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED)     397                                 BREAK_TO_DEBUGGER();     398                 }     399         }     400 --\u0026gt; 401         mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params);                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash      402         return ret;     403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: call cache_put if xdr_reserve_space returns NULL  If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get.  Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential oob read in nilfs_btree_check_delete()  The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.  This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself.  However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Fix a race during cpuhp processing  There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally:  ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x7c/0x110  ? debug_print_object+0x7d/0xb0  ? report_bug+0xf1/0x1d0  ? prb_read_valid+0x17/0x20  ? handle_bug+0x3f/0x70  ? exc_invalid_op+0x13/0x60  ? asm_exc_invalid_op+0x16/0x20  ? debug_print_object+0x7d/0xb0  ? debug_print_object+0x7d/0xb0  ? __pfx_timerlat_irq+0x10/0x10  __debug_object_init+0x110/0x150  hrtimer_init+0x1d/0x60  timerlat_main+0xab/0x2d0  ? __pfx_timerlat_main+0x10/0x10  kthread+0xb7/0xe0  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2d/0x40  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt; ```  After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU:  T1                       | T2 [CPUHP_ONLINE]           | cpu_device_down() osnoise_hotplug_workfn() |                          |     cpus_write_lock()                          |     takedown_cpu(1)                          |     cpus_write_unlock() [CPUHP_OFFLINE]          |     cpus_read_lock()     |     start_kthread(1)     |     cpus_read_unlock()   |  To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: wait for fixup workers before stopping cleaner kthread during umount  During unmount, at close_ctree(), we have the following steps in this order:  1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically    halts its execution (wake ups against it work but do nothing);  2) We stop the cleaner kthread - this results in freeing the respective    struct task_struct;  3) We call btrfs_stop_all_workers() which waits for any jobs running in all    the work queues and then free the work queues.  Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources.  Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs.  The stack traces reported by syzbot were the following:    BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065   Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52    CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024   Workqueue: btrfs-fixup btrfs_work_helper   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120    print_address_description mm/kasan/report.c:377 [inline]    print_report+0x169/0x550 mm/kasan/report.c:488    kasan_report+0x143/0x180 mm/kasan/report.c:601    __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065    lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]    _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162    class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]    try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154    btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842    btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314    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;    Allocated by task 2:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    unpoison_slab_object mm/kasan/common.c:319 [inline]    __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345    kasan_slab_alloc include/linux/kasan.h:247 [inline]    slab_post_alloc_hook mm/slub.c:4086 [inline]    slab_alloc_node mm/slub.c:4135 [inline]    kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187    alloc_task_struct_node kernel/fork.c:180 [inline]    dup_task_struct+0x57/0x8c0 kernel/fork.c:1107    copy_process+0x5d1/0x3d50 kernel/fork.c:2206    kernel_clone+0x223/0x880 kernel/fork.c:2787    kernel_thread+0x1bc/0x240 kernel/fork.c:2849    create_kthread kernel/kthread.c:412 [inline]    kthreadd+0x60d/0x810 kernel/kthread.c:765    ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244    Freed by task 61:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579    poison_slab_object mm/kasan/common.c:247 [inline]    __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264    kasan_slab_free include/linux/kasan.h:230 [inline]    slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix a NULL pointer dereference when failed to start a new trasacntion  [BUG] Syzbot reported a NULL pointer dereference with the following crash:    FAULT_INJECTION: forcing a failure.    start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676    prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642    relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678   ...   BTRFS info (device loop0): balance: ended with status: -12   Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI   KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667]   RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926   Call Trace:    \u0026lt;TASK\u0026gt;    commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496    btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430    del_balance_item fs/btrfs/volumes.c:3678 [inline]    reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742    btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574    btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:907 [inline]    __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893    do_syscall_x64 arch/x86/entry/common.c:52 [inline]    do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83    entry_SYSCALL_64_after_hwframe+0x77/0x7f  [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL.  Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree.  However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume.  Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots().  That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference.  [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree.  That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: map the EBADMSG to nfserr_io to avoid warning  Ext4 will throw -EBADMSG through ext4_readdir when a checksum error occurs, resulting in the following WARNING.  Fix it by mapping EBADMSG to nfserr_io.  nfsd_buffered_readdir  iterate_dir // -EBADMSG -74   ext4_readdir // .iterate_shared    ext4_dx_readdir     ext4_htree_fill_tree      htree_dirblock_to_tree       ext4_read_dirblock        __ext4_read_dirblock         ext4_dirblock_csum_verify          warn_no_space_for_csum           __warn_no_space_for_csum         return ERR_PTR(-EFSBADCRC) // -EBADMSG -74  nfserrno // WARNING  [  161.115610] ------------[ cut here ]------------ [  161.116465] nfsd: non-standard errno: -74 [  161.117315] WARNING: CPU: 1 PID: 780 at fs/nfsd/nfsproc.c:878 nfserrno+0x9d/0xd0 [  161.118596] Modules linked in: [  161.119243] CPU: 1 PID: 780 Comm: nfsd Not tainted 5.10.0-00014-g79679361fd5d #138 [  161.120684] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qe mu.org 04/01/2014 [  161.123601] RIP: 0010:nfserrno+0x9d/0xd0 [  161.124676] Code: 0f 87 da 30 dd 00 83 e3 01 b8 00 00 00 05 75 d7 44 89 ee 48 c7 c7 c0 57 24 98 89 44 24 04 c6  05 ce 2b 61 03 01 e8 99 20 d8 00 \u0026lt;0f\u0026gt; 0b 8b 44 24 04 eb b5 4c 89 e6 48 c7 c7 a0 6d a4 99 e8 cc 15 33 [  161.127797] RSP: 0018:ffffc90000e2f9c0 EFLAGS: 00010286 [  161.128794] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [  161.130089] RDX: 1ffff1103ee16f6d RSI: 0000000000000008 RDI: fffff520001c5f2a [  161.131379] RBP: 0000000000000022 R08: 0000000000000001 R09: ffff8881f70c1827 [  161.132664] R10: ffffed103ee18304 R11: 0000000000000001 R12: 0000000000000021 [  161.133949] R13: 00000000ffffffb6 R14: ffff8881317c0000 R15: ffffc90000e2fbd8 [  161.135244] FS:  0000000000000000(0000) GS:ffff8881f7080000(0000) knlGS:0000000000000000 [  161.136695] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [  161.137761] CR2: 00007fcaad70b348 CR3: 0000000144256006 CR4: 0000000000770ee0 [  161.139041] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [  161.140291] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [  161.141519] PKRU: 55555554 [  161.142076] Call Trace: [  161.142575]  ? __warn+0x9b/0x140 [  161.143229]  ? nfserrno+0x9d/0xd0 [  161.143872]  ? report_bug+0x125/0x150 [  161.144595]  ? handle_bug+0x41/0x90 [  161.145284]  ? exc_invalid_op+0x14/0x70 [  161.146009]  ? asm_exc_invalid_op+0x12/0x20 [  161.146816]  ? nfserrno+0x9d/0xd0 [  161.147487]  nfsd_buffered_readdir+0x28b/0x2b0 [  161.148333]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.149258]  ? nfsd_buffered_filldir+0xf0/0xf0 [  161.150093]  ? wait_for_concurrent_writes+0x170/0x170 [  161.151004]  ? generic_file_llseek_size+0x48/0x160 [  161.151895]  nfsd_readdir+0x132/0x190 [  161.152606]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.153516]  ? nfsd_unlink+0x380/0x380 [  161.154256]  ? override_creds+0x45/0x60 [  161.155006]  nfsd4_encode_readdir+0x21a/0x3d0 [  161.155850]  ? nfsd4_encode_readlink+0x210/0x210 [  161.156731]  ? write_bytes_to_xdr_buf+0x97/0xe0 [  161.157598]  ? __write_bytes_to_xdr_buf+0xd0/0xd0 [  161.158494]  ? lock_downgrade+0x90/0x90 [  161.159232]  ? nfs4svc_decode_voidarg+0x10/0x10 [  161.160092]  nfsd4_encode_operation+0x15a/0x440 [  161.160959]  nfsd4_proc_compound+0x718/0xe90 [  161.161818]  nfsd_dispatch+0x18e/0x2c0 [  161.162586]  svc_process_common+0x786/0xc50 [  161.163403]  ? nfsd_svc+0x380/0x380 [  161.164137]  ? svc_printk+0x160/0x160 [  161.164846]  ? svc_xprt_do_enqueue.part.0+0x365/0x380 [  161.165808]  ? nfsd_svc+0x380/0x380 [  161.166523]  ? rcu_is_watching+0x23/0x40 [  161.167309]  svc_process+0x1a5/0x200 [  161.168019]  nfsd+0x1f5/0x380 [  161.168663]  ? nfsd_shutdown_threads+0x260/0x260 [  161.169554]  kthread+0x1c4/0x210 [  161.170224]  ? kthread_insert_work_sanity_check+0x80/0x80 [  161.171246]  ret_from_fork+0x1f/0x30(CVE-2024-49875)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in degamma hardware format translation  Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color  management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the  number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: check if leafidx greater than num leaves per dmap tree  syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf.  Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uaf in dbFreeBits  [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216  CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  __mutex_lock_common kernel/locking/mutex.c:587 [inline]  __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752  dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390  dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]  dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409  dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650  jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100  jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  Freed by task 5218:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579  poison_slab_object+0xe0/0x150 mm/kasan/common.c:240  __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2252 [inline]  slab_free mm/slub.c:4473 [inline]  kfree+0x149/0x360 mm/slub.c:4594  dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278  jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247  jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454  reconfigure_super+0x445/0x880 fs/super.c:1083  vfs_cmd_reconfigure fs/fsopen.c:263 [inline]  vfs_fsconfig_locked fs/fsopen.c:292 [inline]  __do_sys_fsconfig fs/fsopen.c:473 [inline]  __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf.  Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error if set_output_gamma is null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/ioapic: Handle allocation failures gracefully  Breno observed panics when using failslab under certain conditions during runtime:     can not alloc irq_pin_list (-1,0,20)    Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed     panic+0x4e9/0x590    mp_irqdomain_alloc+0x9ab/0xa80    irq_domain_alloc_irqs_locked+0x25d/0x8d0    __irq_domain_alloc_irqs+0x80/0x110    mp_map_pin_to_irq+0x645/0x890    acpi_register_gsi_ioapic+0xe6/0x150    hpet_open+0x313/0x480  That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed.  The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode.  Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error  In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain:  ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace:  \u0026lt;TASK\u0026gt;  add_transaction_credits+0x5d1/0x5e0  start_this_handle+0x1ef/0x6a0  jbd2__journal_start+0x18b/0x340  ext4_dirty_inode+0x5d/0xb0  __mark_inode_dirty+0xe4/0x5d0  generic_update_time+0x60/0x70 [...] ============================================  So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways.  Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: cancel dqi_sync_work before freeing oinfo  ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled:  ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c  This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first.  BTW, return status instead of -1 when .read_file_info fails.(CVE-2024-49966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 color transformation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Limit the number of concurrent async COPY operations  Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.  Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.  An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.  If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume  In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.  This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks.  Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: asihpi: Fix potential OOB array access  ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware.  We shouldn\u0026apos;t trust it blindly.  This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: fnic: Move flush_work initialization out of if block  After commit 379a58caa199 (\u0026quot;scsi: fnic: Move fnic_fnic_flush_tx() to a work queue\u0026quot;), it can happen that a work item is sent to an uninitialized work queue.  This may has the effect that the item being queued is never actually queued, and any further actions depending on it will not proceed.  The following warning is observed while the fnic driver is loaded:  kernel: WARNING: CPU: 11 PID: 0 at ../kernel/workqueue.c:1524 __queue_work+0x373/0x410 kernel:  \u0026lt;IRQ\u0026gt; kernel:  queue_work_on+0x3a/0x50 kernel:  fnic_wq_copy_cmpl_handler+0x54a/0x730 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  fnic_isr_msix_wq_copy+0x2d/0x60 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  __handle_irq_event_percpu+0x36/0x1a0 kernel:  handle_irq_event_percpu+0x30/0x70 kernel:  handle_irq_event+0x34/0x60 kernel:  handle_edge_irq+0x7e/0x1a0 kernel:  __common_interrupt+0x3b/0xb0 kernel:  common_interrupt+0x58/0xa0 kernel:  \u0026lt;/IRQ\u0026gt;  It has been observed that this may break the rediscovery of Fibre Channel devices after a temporary fabric failure.  This patch fixes it by moving the work queue initialization out of an if block in fnic_probe().(CVE-2024-50025)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: do not delay dst_entries_add() in dst_release()  dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy()  Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy()  dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already.  Decrementing the number of dsts must happen sooner.  Notes:  1) in CONFIG_XFRM case, dst_destroy() can call    dst_release_immediate(child), this might also cause UAF    if the child does not have DST_NOCOUNT set.    IPSEC maintainers might take a look and see how to address this.  2) There is also discussion about removing this count of dst,    which might happen in future kernels.(CVE-2024-50036)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointer before dereferencing se  [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)","status":"published","published":"2024-11-01T11:07:48Z","modified":"2026-08-18T01:17:36.430422624Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2325","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:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: make sure that WRITTEN is set on all metadata blocks\r\n\r\nWe previously would call btrfs_check_leaf() if we had the check\nintegrity code enabled, which meant that we could only run the extended\nleaf checks if we had WRITTEN set on the header flags.\r\n\r\nThis leaves a gap in our checking, because we could end up with\ncorruption on disk where WRITTEN isn\u0026apos;t set on the leaf, and then the\nextended leaf checks don\u0026apos;t get run which we rely on to validate all of\nthe item pointers to make sure we don\u0026apos;t access memory outside of the\nextent buffer.\r\n\r\nHowever, since 732fab95abe2 (\u0026quot;btrfs: check-integrity: remove\nCONFIG_BTRFS_FS_CHECK_INTEGRITY option\u0026quot;) we no longer call\nbtrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only\never call it on blocks that are being written out, and thus have WRITTEN\nset, or that are being read in, which should have WRITTEN set.\r\n\r\nAdd checks to make sure we have WRITTEN set appropriately, and then make\nsure __btrfs_check_leaf() always does the item checking.  This will\nprotect us from file systems that have been corrupted and no longer have\nWRITTEN set on some of the blocks.\r\n\r\nThis was hit on a crafted image tweaking the WRITTEN bit and reported by\nKASAN as out-of-bound access in the eb accessors. The example is a dir\nitem at the end of an eb.\r\n\r\n  [2.042] BTRFS warning (device loop1): bad eb member start: ptr 0x3fff start 30572544 member offset 16410 size 2\n  [2.040] general protection fault, probably for non-canonical address 0xe0009d1000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI\n  [2.537] KASAN: maybe wild-memory-access in range [0x0005088000000018-0x000508800000001f]\n  [2.729] CPU: 0 PID: 2587 Comm: mount Not tainted 6.8.2 #1\n  [2.729] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\n  [2.621] RIP: 0010:btrfs_get_16+0x34b/0x6d0\n  [2.621] RSP: 0018:ffff88810871fab8 EFLAGS: 00000206\n  [2.621] RAX: 0000a11000000003 RBX: ffff888104ff8720 RCX: ffff88811b2288c0\n  [2.621] RDX: dffffc0000000000 RSI: ffffffff81dd8aca RDI: ffff88810871f748\n  [2.621] RBP: 000000000000401a R08: 0000000000000001 R09: ffffed10210e3ee9\n  [2.621] R10: ffff88810871f74f R11: 205d323430333737 R12: 000000000000001a\n  [2.621] R13: 000508800000001a R14: 1ffff110210e3f5d R15: ffffffff850011e8\n  [2.621] FS:  00007f56ea275840(0000) GS:ffff88811b200000(0000) knlGS:0000000000000000\n  [2.621] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  [2.621] CR2: 00007febd13b75c0 CR3: 000000010bb50000 CR4: 00000000000006f0\n  [2.621] Call Trace:\n  [2.621]  \u0026lt;TASK\u0026gt;\n  [2.621]  ? show_regs+0x74/0x80\n  [2.621]  ? die_addr+0x46/0xc0\n  [2.621]  ? exc_general_protection+0x161/0x2a0\n  [2.621]  ? asm_exc_general_protection+0x26/0x30\n  [2.621]  ? btrfs_get_16+0x33a/0x6d0\n  [2.621]  ? btrfs_get_16+0x34b/0x6d0\n  [2.621]  ? btrfs_get_16+0x33a/0x6d0\n  [2.621]  ? __pfx_btrfs_get_16+0x10/0x10\n  [2.621]  ? __pfx_mutex_unlock+0x10/0x10\n  [2.621]  btrfs_match_dir_item_name+0x101/0x1a0\n  [2.621]  btrfs_lookup_dir_item+0x1f3/0x280\n  [2.621]  ? __pfx_btrfs_lookup_dir_item+0x10/0x10\n  [2.621]  btrfs_get_tree+0xd25/0x1910\r\n\r\n[ copy more details from report ](CVE-2024-35949)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: ISO: Fix not validating setsockopt user input\r\n\r\nCheck user input length before copying data.(CVE-2024-35964)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommu/arm-smmu: Use the correct type in nvidia_smmu_context_fault()\r\n\r\nThis was missed because of the function pointer indirection.\r\n\r\nnvidia_smmu_context_fault() is also installed as a irq function, and the\n\u0026apos;void *\u0026apos; was changed to a struct arm_smmu_domain. Since the iommu_domain\nis embedded at a non-zero offset this causes nvidia_smmu_context_fault()\nto miscompute the offset. Fixup the types.\r\n\r\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000120\n  Mem abort info:\n    ESR = 0x0000000096000004\n    EC = 0x25: DABT (current EL), IL = 32 bits\n    SET = 0, FnV = 0\n    EA = 0, S1PTW = 0\n    FSC = 0x04: level 0 translation fault\n  Data abort info:\n    ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n    CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n    GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n  user pgtable: 4k pages, 48-bit VAs, pgdp=0000000107c9f000\n  [0000000000000120] pgd=0000000000000000, p4d=0000000000000000\n  Internal error: Oops: 0000000096000004 [#1] SMP\n  Modules linked in:\n  CPU: 1 PID: 47 Comm: kworker/u25:0 Not tainted 6.9.0-0.rc7.58.eln136.aarch64 #1\n  Hardware name: Unknown NVIDIA Jetson Orin NX/NVIDIA Jetson Orin NX, BIOS 3.1-32827747 03/19/2023\n  Workqueue: events_unbound deferred_probe_work_func\n  pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : nvidia_smmu_context_fault+0x1c/0x158\n  lr : __free_irq+0x1d4/0x2e8\n  sp : ffff80008044b6f0\n  x29: ffff80008044b6f0 x28: ffff000080a60b18 x27: ffffd32b5172e970\n  x26: 0000000000000000 x25: ffff0000802f5aac x24: ffff0000802f5a30\n  x23: ffff0000802f5b60 x22: 0000000000000057 x21: 0000000000000000\n  x20: ffff0000802f5a00 x19: ffff000087d4cd80 x18: ffffffffffffffff\n  x17: 6234362066666666 x16: 6630303078302d30 x15: ffff00008156d888\n  x14: 0000000000000000 x13: ffff0000801db910 x12: ffff00008156d6d0\n  x11: 0000000000000003 x10: ffff0000801db918 x9 : ffffd32b50f94d9c\n  x8 : 1fffe0001032fda1 x7 : ffff00008197ed00 x6 : 000000000000000f\n  x5 : 000000000000010e x4 : 000000000000010e x3 : 0000000000000000\n  x2 : ffffd32b51720cd8 x1 : ffff000087e6f700 x0 : 0000000000000057\n  Call trace:\n   nvidia_smmu_context_fault+0x1c/0x158\n   __free_irq+0x1d4/0x2e8\n   free_irq+0x3c/0x80\n   devm_free_irq+0x64/0xa8\n   arm_smmu_domain_free+0xc4/0x158\n   iommu_domain_free+0x44/0xa0\n   iommu_deinit_device+0xd0/0xf8\n   __iommu_group_remove_device+0xcc/0xe0\n   iommu_bus_notifier+0x64/0xa8\n   notifier_call_chain+0x78/0x148\n   blocking_notifier_call_chain+0x4c/0x90\n   bus_notify+0x44/0x70\n   device_del+0x264/0x3e8\n   pci_remove_bus_device+0x84/0x120\n   pci_remove_root_bus+0x5c/0xc0\n   dw_pcie_host_deinit+0x38/0xe0\n   tegra_pcie_config_rp+0xc0/0x1f0\n   tegra_pcie_dw_probe+0x34c/0x700\n   platform_probe+0x70/0xe8\n   really_probe+0xc8/0x3a0\n   __driver_probe_device+0x84/0x160\n   driver_probe_device+0x44/0x130\n   __device_attach_driver+0xc4/0x170\n   bus_for_each_drv+0x90/0x100\n   __device_attach+0xa8/0x1c8\n   device_initial_probe+0x1c/0x30\n   bus_probe_device+0xb0/0xc0\n   deferred_probe_work_func+0xbc/0x120\n   process_one_work+0x194/0x490\n   worker_thread+0x284/0x3b0\n   kthread+0xf4/0x108\n   ret_from_fork+0x10/0x20\n  Code: a9b97bfd 910003fd a9025bf5 f85a0035 (b94122a1)(CVE-2024-36884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/msm/dpu: cleanup FB if dpu_format_populate_layout fails\r\n\r\nIf the dpu_format_populate_layout() fails, then FB is prepared, but not\ncleaned up. This ends up leaking the pin_count on the GEM object and\ncauses a splat during DRM file closure:\r\n\r\nmsm_obj-\u0026gt;pin_count\nWARNING: CPU: 2 PID: 569 at drivers/gpu/drm/msm/msm_gem.c:121 update_lru_locked+0xc4/0xcc\n[...]\nCall trace:\n update_lru_locked+0xc4/0xcc\n put_pages+0xac/0x100\n msm_gem_free_object+0x138/0x180\n drm_gem_object_free+0x1c/0x30\n drm_gem_object_handle_put_unlocked+0x108/0x10c\n drm_gem_object_release_handle+0x58/0x70\n idr_for_each+0x68/0xec\n drm_gem_release+0x28/0x40\n drm_file_free+0x174/0x234\n drm_release+0xb0/0x160\n __fput+0xc0/0x2c8\n __fput_sync+0x50/0x5c\n __arm64_sys_close+0x38/0x7c\n invoke_syscall+0x48/0x118\n el0_svc_common.constprop.0+0x40/0xe0\n do_el0_svc+0x1c/0x28\n el0_svc+0x4c/0x120\n el0t_64_sync_handler+0x100/0x12c\n el0t_64_sync+0x190/0x194\nirq event stamp: 129818\nhardirqs last  enabled at (129817): [\u0026lt;ffffa5f6d953fcc0\u0026gt;] console_unlock+0x118/0x124\nhardirqs last disabled at (129818): [\u0026lt;ffffa5f6da7dcf04\u0026gt;] el1_dbg+0x24/0x8c\nsoftirqs last  enabled at (129808): [\u0026lt;ffffa5f6d94afc18\u0026gt;] handle_softirqs+0x4c8/0x4e8\nsoftirqs last disabled at (129785): [\u0026lt;ffffa5f6d94105e4\u0026gt;] __do_softirq+0x14/0x20\r\n\r\nPatchwork: https://patchwork.freedesktop.org/patch/600714/(CVE-2024-44982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()\r\n\r\nWhen there are multiple ap interfaces on one band and with WED on,\nturning the interface down will cause a kernel panic on MT798X.\r\n\r\nPreviously, cb_priv was freed in mtk_wed_setup_tc_block() without\nmarking NULL,and mtk_wed_setup_tc_block_cb() didn\u0026apos;t check the value, too.\r\n\r\nAssign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL\nin mtk_wed_setup_tc_block_cb().\r\n\r\n----------\nUnable to handle kernel paging request at virtual address 0072460bca32b4f5\nCall trace:\n mtk_wed_setup_tc_block_cb+0x4/0x38\n 0xffffffc0794084bc\n tcf_block_playback_offloads+0x70/0x1e8\n tcf_block_unbind+0x6c/0xc8\n...\n---------(CVE-2024-44997)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush()\r\n\r\nThis adds a check before freeing the rx-\u0026gt;skb in flush and close\nfunctions to handle the kernel crash seen while removing driver after FW\ndownload fails or before FW download completes.\r\n\r\ndmesg log:\n[   54.634586] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000080\n[   54.643398] Mem abort info:\n[   54.646204]   ESR = 0x0000000096000004\n[   54.649964]   EC = 0x25: DABT (current EL), IL = 32 bits\n[   54.655286]   SET = 0, FnV = 0\n[   54.658348]   EA = 0, S1PTW = 0\n[   54.661498]   FSC = 0x04: level 0 translation fault\n[   54.666391] Data abort info:\n[   54.669273]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n[   54.674768]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[   54.674771]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[   54.674775] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000048860000\n[   54.674780] [0000000000000080] pgd=0000000000000000, p4d=0000000000000000\n[   54.703880] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP\n[   54.710152] Modules linked in: btnxpuart(-) overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_micfil snd_soc_fsl_spdif snd_soc_fsl_sai snd_soc_fsl_utils imx_pcm_dma gpio_ir_recv rc_core sch_fq_codel fuse\n[   54.744357] CPU: 3 PID: 72 Comm: kworker/u9:0 Not tainted 6.6.3-otbr-g128004619037 #2\n[   54.744364] Hardware name: FSL i.MX8MM EVK board (DT)\n[   54.744368] Workqueue: hci0 hci_power_on\n[   54.757244] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   54.757249] pc : kfree_skb_reason+0x18/0xb0\n[   54.772299] lr : btnxpuart_flush+0x40/0x58 [btnxpuart]\n[   54.782921] sp : ffff8000805ebca0\n[   54.782923] x29: ffff8000805ebca0 x28: ffffa5c6cf1869c0 x27: ffffa5c6cf186000\n[   54.782931] x26: ffff377b84852400 x25: ffff377b848523c0 x24: ffff377b845e7230\n[   54.782938] x23: ffffa5c6ce8dbe08 x22: ffffa5c6ceb65410 x21: 00000000ffffff92\n[   54.782945] x20: ffffa5c6ce8dbe98 x19: ffffffffffffffac x18: ffffffffffffffff\n[   54.807651] x17: 0000000000000000 x16: ffffa5c6ce2824ec x15: ffff8001005eb857\n[   54.821917] x14: 0000000000000000 x13: ffffa5c6cf1a02e0 x12: 0000000000000642\n[   54.821924] x11: 0000000000000040 x10: ffffa5c6cf19d690 x9 : ffffa5c6cf19d688\n[   54.821931] x8 : ffff377b86000028 x7 : 0000000000000000 x6 : 0000000000000000\n[   54.821938] x5 : ffff377b86000000 x4 : 0000000000000000 x3 : 0000000000000000\n[   54.843331] x2 : 0000000000000000 x1 : 0000000000000002 x0 : ffffffffffffffac\n[   54.857599] Call trace:\n[   54.857601]  kfree_skb_reason+0x18/0xb0\n[   54.863878]  btnxpuart_flush+0x40/0x58 [btnxpuart]\n[   54.863888]  hci_dev_open_sync+0x3a8/0xa04\n[   54.872773]  hci_power_on+0x54/0x2e4\n[   54.881832]  process_one_work+0x138/0x260\n[   54.881842]  worker_thread+0x32c/0x438\n[   54.881847]  kthread+0x118/0x11c\n[   54.881853]  ret_from_fork+0x10/0x20\n[   54.896406] Code: a9be7bfd 910003fd f9000bf3 aa0003f3 (b940d400)\n[   54.896410] ---[ end trace 0000000000000000 ]---(CVE-2024-46749)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Validate function returns\r\n\r\n[WHAT \u0026amp; HOW]\nFunction return values must be checked before data can be used\nin subsequent functions.\r\n\r\nThis fixes 4 CHECKED_RETURN issues reported by Coverity.(CVE-2024-46775)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nila: call nf_unregister_net_hooks() sooner\r\n\r\nsyzbot found an use-after-free Read in ila_nf_input [1]\r\n\r\nIssue here is that ila_xlat_exit_net() frees the rhashtable,\nthen call nf_unregister_net_hooks().\r\n\r\nIt should be done in the reverse way, with a synchronize_rcu().\r\n\r\nThis is a good match for a pre_exit() method.\r\n\r\n[1]\n BUG: KASAN: use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline]\n BUG: KASAN: use-after-free in __rhashtable_lookup include/linux/rhashtable.h:604 [inline]\n BUG: KASAN: use-after-free in rhashtable_lookup include/linux/rhashtable.h:646 [inline]\n BUG: KASAN: use-after-free in rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672\nRead of size 4 at addr ffff888064620008 by task ksoftirqd/0/16\r\n\r\nCPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.11.0-rc4-syzkaller-00238-g2ad6d23f465a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:93 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119\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  rht_key_hashfn include/linux/rhashtable.h:159 [inline]\n  __rhashtable_lookup include/linux/rhashtable.h:604 [inline]\n  rhashtable_lookup include/linux/rhashtable.h:646 [inline]\n  rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672\n  ila_lookup_wildcards net/ipv6/ila/ila_xlat.c:132 [inline]\n  ila_xlat_addr net/ipv6/ila/ila_xlat.c:652 [inline]\n  ila_nf_input+0x1fe/0x3c0 net/ipv6/ila/ila_xlat.c:190\n  nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]\n  nf_hook_slow+0xc3/0x220 net/netfilter/core.c:626\n  nf_hook include/linux/netfilter.h:269 [inline]\n  NF_HOOK+0x29e/0x450 include/linux/netfilter.h:312\n  __netif_receive_skb_one_core net/core/dev.c:5661 [inline]\n  __netif_receive_skb+0x1ea/0x650 net/core/dev.c:5775\n  process_backlog+0x662/0x15b0 net/core/dev.c:6108\n  __napi_poll+0xcb/0x490 net/core/dev.c:6772\n  napi_poll net/core/dev.c:6841 [inline]\n  net_rx_action+0x89b/0x1240 net/core/dev.c:6963\n  handle_softirqs+0x2c4/0x970 kernel/softirq.c:554\n  run_ksoftirqd+0xca/0x130 kernel/softirq.c:928\n  smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164\n  kthread+0x2f0/0x390 kernel/kthread.c:389\n  ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n \u0026lt;/TASK\u0026gt;\r\n\r\nThe buggy address belongs to the physical page:\npage: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x64620\nflags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)\npage_type: 0xbfffffff(buddy)\nraw: 00fff00000000000 ffffea0000959608 ffffea00019d9408 0000000000000000\nraw: 0000000000000000 0000000000000003 00000000bfffffff 0000000000000000\npage dumped because: kasan: bad access detected\npage_owner tracks the page as freed\npage last allocated via order 3, migratetype Unmovable, gfp_mask 0x52dc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_ZERO), pid 5242, tgid 5242 (syz-executor), ts 73611328570, free_ts 618981657187\n  set_page_owner include/linux/page_owner.h:32 [inline]\n  post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1493\n  prep_new_page mm/page_alloc.c:1501 [inline]\n  get_page_from_freelist+0x2e4c/0x2f10 mm/page_alloc.c:3439\n  __alloc_pages_noprof+0x256/0x6c0 mm/page_alloc.c:4695\n  __alloc_pages_node_noprof include/linux/gfp.h:269 [inline]\n  alloc_pages_node_noprof include/linux/gfp.h:296 [inline]\n  ___kmalloc_large_node+0x8b/0x1d0 mm/slub.c:4103\n  __kmalloc_large_node_noprof+0x1a/0x80 mm/slub.c:4130\n  __do_kmalloc_node mm/slub.c:4146 [inline]\n  __kmalloc_node_noprof+0x2d2/0x440 mm/slub.c:4164\n  __kvmalloc_node_noprof+0x72/0x190 mm/util.c:650\n  bucket_table_alloc lib/rhashtable.c:186 [inline]\n  rhashtable_init_noprof+0x534/0xa60 lib/rhashtable.c:1071\n  ila_xlat_init_net+0xa0/0x110 net/ipv6/ila/ila_xlat.c:613\n  ops_ini\n---truncated---(CVE-2024-46782)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[   36.926103] ==================================================================\n[   36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[   36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[   36.946721]\n[   36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[   36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[   36.961260] Call trace:\n[   36.963723]  dump_backtrace+0x90/0xe8\n[   36.967414]  show_stack+0x18/0x24\n[   36.970749]  dump_stack_lvl+0x78/0x90\n[   36.974451]  print_report+0x114/0x5cc\n[   36.978151]  kasan_report+0xa4/0xf0\n[   36.981670]  __asan_report_load_n_noabort+0x1c/0x28\n[   36.986587]  nxp_fspi_exec_op+0x26ec/0x2838\n[   36.990800]  spi_mem_exec_op+0x8ec/0xd30\n[   36.994762]  spi_mem_no_dirmap_read+0x190/0x1e0\n[   36.999323]  spi_mem_dirmap_write+0x238/0x32c\n[   37.003710]  spi_nor_write_data+0x220/0x374\n[   37.007932]  spi_nor_write+0x110/0x2e8\n[   37.011711]  mtd_write_oob_std+0x154/0x1f0\n[   37.015838]  mtd_write_oob+0x104/0x1d0\n[   37.019617]  mtd_write+0xb8/0x12c\n[   37.022953]  mtdchar_write+0x224/0x47c\n[   37.026732]  vfs_write+0x1e4/0x8c8\n[   37.030163]  ksys_write+0xec/0x1d0\n[   37.033586]  __arm64_sys_write+0x6c/0x9c\n[   37.037539]  invoke_syscall+0x6c/0x258\n[   37.041327]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.046244]  do_el0_svc+0x44/0x5c\n[   37.049589]  el0_svc+0x38/0x78\n[   37.052681]  el0t_64_sync_handler+0x13c/0x158\n[   37.057077]  el0t_64_sync+0x190/0x194\n[   37.060775]\n[   37.062274] Allocated by task 455:\n[   37.065701]  kasan_save_stack+0x2c/0x54\n[   37.069570]  kasan_save_track+0x20/0x3c\n[   37.073438]  kasan_save_alloc_info+0x40/0x54\n[   37.077736]  __kasan_kmalloc+0xa0/0xb8\n[   37.081515]  __kmalloc_noprof+0x158/0x2f8\n[   37.085563]  mtd_kmalloc_up_to+0x120/0x154\n[   37.089690]  mtdchar_write+0x130/0x47c\n[   37.093469]  vfs_write+0x1e4/0x8c8\n[   37.096901]  ksys_write+0xec/0x1d0\n[   37.100332]  __arm64_sys_write+0x6c/0x9c\n[   37.104287]  invoke_syscall+0x6c/0x258\n[   37.108064]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.112972]  do_el0_svc+0x44/0x5c\n[   37.116319]  el0_svc+0x38/0x78\n[   37.119401]  el0t_64_sync_handler+0x13c/0x158\n[   37.123788]  el0t_64_sync+0x190/0x194\n[   37.127474]\n[   37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[   37.128977]  which belongs to the cache kmalloc-8 of size 8\n[   37.141177] The buggy address is located 0 bytes inside of\n[   37.141177]  allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[   37.153465]\n[   37.154971] The buggy address belongs to the physical page:\n[   37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[   37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[   37.175149] page_type: 0xfdffffff(slab)\n[   37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[   37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[   37.194553] page dumped because: kasan: bad access detected\n[   37.200144]\n[   37.201647] Memory state around the buggy address:\n[   37.206460]  ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[   37.213701]  ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[   37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[   37.228186]                                ^\n[   37.232473]  ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.239718]  ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX\r\n\r\n[Why \u0026amp; How]\nIt actually exposes \u0026apos;6\u0026apos; types in enum dmub_notification_type. Not 5. Using smaller\nnumber to create array dmub_callback \u0026amp; dmub_thread_offload has potential to access\nitem out of array bound. Fix it.(CVE-2024-46871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n   with active Smack in the default state\n   (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n   (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n   that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n   (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n   Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Avoid overflow from uint32_t to uint8_t\r\n\r\n[WHAT \u0026amp; HOW]\ndmub_rb_cmd\u0026apos;s ramping_boundary has size of uint8_t and it is assigned\n0xFFFF. Fix it by changing it to uint8_t with value of 0xFF.\r\n\r\nThis fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-47661)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he  Fix the NULL pointer dereference in mt7996_mcu_sta_bfer_he routine adding an sta interface to the mt7996 driver.  Found by code review.(CVE-2024-47681)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Skip Recompute DSC Params if no Stream on Link  [why] Encounter NULL pointer dereference uner mst + dsc setup.  BUG: kernel NULL pointer dereference, address: 0000000000000008     PGD 0 P4D 0     Oops: 0000 [#1] PREEMPT SMP NOPTI     CPU: 4 PID: 917 Comm: sway Not tainted 6.3.9-arch1-1 #1 124dc55df4f5272ccb409f39ef4872fc2b3376a2     Hardware name: LENOVO 20NKS01Y00/20NKS01Y00, BIOS R12ET61W(1.31 ) 07/28/2022     RIP: 0010:drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper]     Code: 01 00 00 48 8b 85 60 05 00 00 48 63 80 88 00 00 00 3b 43 28 0f 8d 2e 01 00 00 48 8b 53 30 48 8d 04 80 48 8d 04 c2 48 8b 40 18 \u0026lt;48\u0026gt; 8\u0026gt;     RSP: 0018:ffff960cc2df77d8 EFLAGS: 00010293     RAX: 0000000000000000 RBX: ffff8afb87e81280 RCX: 0000000000000224     RDX: ffff8afb9ee37c00 RSI: ffff8afb8da1a578 RDI: ffff8afb87e81280     RBP: ffff8afb83d67000 R08: 0000000000000001 R09: ffff8afb9652f850     R10: ffff960cc2df7908 R11: 0000000000000002 R12: 0000000000000000     R13: ffff8afb8d7688a0 R14: ffff8afb8da1a578 R15: 0000000000000224     FS:  00007f4dac35ce00(0000) GS:ffff8afe30b00000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 0000000000000008 CR3: 000000010ddc6000 CR4: 00000000003506e0     Call Trace: \u0026lt;TASK\u0026gt;      ? __die+0x23/0x70      ? page_fault_oops+0x171/0x4e0      ? plist_add+0xbe/0x100      ? exc_page_fault+0x7c/0x180      ? asm_exc_page_fault+0x26/0x30      ? drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026]      ? drm_dp_atomic_find_time_slots+0x28/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026]      compute_mst_dsc_configs_for_link+0x2ff/0xa40 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]      ? fill_plane_buffer_attributes+0x419/0x510 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]      compute_mst_dsc_configs_for_state+0x1e1/0x250 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]      amdgpu_dm_atomic_check+0xecd/0x1190 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]      drm_atomic_check_only+0x5c5/0xa40      drm_mode_atomic_ioctl+0x76e/0xbc0  [how] dsc recompute should be skipped if no mode change detected on the new request. If detected, keep checking whether the stream is already on current state or not.(CVE-2024-47683)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: check skb is non-NULL in tcp_rto_delta_us()  We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases:  Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to don\u0026apos;t set SB_RDONLY in f2fs_handle_critical_error()  syzbot reports a f2fs bug as below:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 58 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177 CPU: 1 UID: 0 PID: 58 Comm: kworker/1:2 Not tainted 6.10.0-syzkaller-12562-g1722389b0d86 #0 Workqueue: events destroy_super_work RIP: 0010:rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177 Call Trace:  percpu_free_rwsem+0x41/0x80 kernel/locking/percpu-rwsem.c:42  destroy_super_work+0xec/0x130 fs/super.c:282  process_one_work kernel/workqueue.c:3231 [inline]  process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312  worker_thread+0x86d/0xd40 kernel/workqueue.c:3390  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  As Christian Brauner pointed out [1]: the root cause is f2fs sets SB_RDONLY flag in internal function, rather than setting the flag covered w/ sb-\u0026gt;s_umount semaphore via remount procedure, then below race condition causes this bug:  - freeze_super()  - sb_wait_write(sb, SB_FREEZE_WRITE)  - sb_wait_write(sb, SB_FREEZE_PAGEFAULT)  - sb_wait_write(sb, SB_FREEZE_FS)      - f2fs_handle_critical_error       - sb-\u0026gt;s_flags |= SB_RDONLY - thaw_super  - thaw_super_locked   - sb_rdonly() is true, so it skips     sb_freeze_unlock(sb, SB_FREEZE_FS)   - deactivate_locked_super  Since f2fs has almost the same logic as ext4 [2] when handling critical error in filesystem if it mounts w/ errors=remount-ro option: - set CP_ERROR_FLAG flag which indicates filesystem is stopped - record errors to superblock - set SB_RDONLY falg Once we set CP_ERROR_FLAG flag, all writable interfaces can detect the flag and stop any further updates on filesystem. So, it is safe to not set SB_RDONLY flag, let\u0026apos;s remove the logic and keep in line w/ ext4 [3].  [1] https://lore.kernel.org/all/20240729-himbeeren-funknetz-96e62f9c7aee@brauner [2] https://lore.kernel.org/all/20240729132721.hxih6ehigadqf7wx@quack3 [3] https://lore.kernel.org/linux-ext4/20240805201241.27286-1-jack@suse.cz(CVE-2024-47689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: return -EINVAL when namelen is 0  When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered.  [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205]  dump_stack+0x9a/0xd0 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  __kasan_report.cold+0x34/0x84 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  kasan_report+0x3a/0x50 [ T1205]  nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  ? nfsd4_release_lockowner+0x410/0x410 [ T1205]  cld_pipe_downcall+0x5ca/0x760 [ T1205]  ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205]  ? down_write_killable_nested+0x170/0x170 [ T1205]  ? avc_policy_seqno+0x28/0x40 [ T1205]  ? selinux_file_permission+0x1b4/0x1e0 [ T1205]  rpc_pipe_write+0x84/0xb0 [ T1205]  vfs_write+0x143/0x520 [ T1205]  ksys_write+0xc9/0x170 [ T1205]  ? __ia32_sys_read+0x50/0x50 [ T1205]  ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205]  ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205]  do_syscall_64+0x33/0x40 [ T1205]  entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ==================================================================  Fix it by checking namelen.(CVE-2024-47692)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds  In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num.  This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sock_map: Add a cond_resched() in sock_hash_free()  Several syzbot soft lockup reports all have in common sock_hash_free()  If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the  dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function.  This fix prevents a potential null pointer dereference error.  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386)  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c     373 bool dcn30_set_output_transfer_func(struct dc *dc,     374                                 struct pipe_ctx *pipe_ctx,     375                                 const struct dc_stream_state *stream)     376 {     377         int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst;     378         struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc;     379         const struct pwl_params *params = NULL;     380         bool ret = false;     381     382         /* program OGAM or 3DLUT only for the top pipe*/     383         if (pipe_ctx-\u0026gt;top_pipe == NULL) {     384                 /*program rmu shaper and 3dlut in MPC*/     385                 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream);     386                 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) {                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL      387                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL)     388                                 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl;     389                         else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type ==     390                                         TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp;     391                                         cm3_helper_translate_curve_to_hw_format(     392                                         \u0026amp;stream-\u0026gt;out_transfer_func,     393                                         \u0026amp;mpc-\u0026gt;blender_params, false))     394                                 params = \u0026amp;mpc-\u0026gt;blender_params;     395                          /* there are no ROM LUTs in OUTGAM */     396                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED)     397                                 BREAK_TO_DEBUGGER();     398                 }     399         }     400 --\u0026gt; 401         mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params);                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash      402         return ret;     403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: call cache_put if xdr_reserve_space returns NULL  If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get.  Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  KEYS: prevent NULL pointer dereference in find_asymmetric_key()  In find_asymmetric_key(), if all NULLs are passed in the id_{0,1,2} arguments, the kernel will first emit WARN but then have an oops because id_2 gets dereferenced anyway.  Add the missing id_2 check and move WARN_ON() to the final else branch to avoid duplicate NULL checks.  Found by Linux Verification Center (linuxtesting.org) with Svace static analysis tool.(CVE-2024-47743)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential oob read in nilfs_btree_check_delete()  The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.  This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself.  However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Fix a race during cpuhp processing  There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally:  ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x7c/0x110  ? debug_print_object+0x7d/0xb0  ? report_bug+0xf1/0x1d0  ? prb_read_valid+0x17/0x20  ? handle_bug+0x3f/0x70  ? exc_invalid_op+0x13/0x60  ? asm_exc_invalid_op+0x16/0x20  ? debug_print_object+0x7d/0xb0  ? debug_print_object+0x7d/0xb0  ? __pfx_timerlat_irq+0x10/0x10  __debug_object_init+0x110/0x150  hrtimer_init+0x1d/0x60  timerlat_main+0xab/0x2d0  ? __pfx_timerlat_main+0x10/0x10  kthread+0xb7/0xe0  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2d/0x40  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt; ```  After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU:  T1                       | T2 [CPUHP_ONLINE]           | cpu_device_down() osnoise_hotplug_workfn() |                          |     cpus_write_lock()                          |     takedown_cpu(1)                          |     cpus_write_unlock() [CPUHP_OFFLINE]          |     cpus_read_lock()     |     start_kthread(1)     |     cpus_read_unlock()   |  To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: wait for fixup workers before stopping cleaner kthread during umount  During unmount, at close_ctree(), we have the following steps in this order:  1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically    halts its execution (wake ups against it work but do nothing);  2) We stop the cleaner kthread - this results in freeing the respective    struct task_struct;  3) We call btrfs_stop_all_workers() which waits for any jobs running in all    the work queues and then free the work queues.  Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources.  Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs.  The stack traces reported by syzbot were the following:    BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065   Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52    CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024   Workqueue: btrfs-fixup btrfs_work_helper   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120    print_address_description mm/kasan/report.c:377 [inline]    print_report+0x169/0x550 mm/kasan/report.c:488    kasan_report+0x143/0x180 mm/kasan/report.c:601    __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065    lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]    _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162    class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]    try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154    btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842    btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314    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;    Allocated by task 2:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    unpoison_slab_object mm/kasan/common.c:319 [inline]    __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345    kasan_slab_alloc include/linux/kasan.h:247 [inline]    slab_post_alloc_hook mm/slub.c:4086 [inline]    slab_alloc_node mm/slub.c:4135 [inline]    kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187    alloc_task_struct_node kernel/fork.c:180 [inline]    dup_task_struct+0x57/0x8c0 kernel/fork.c:1107    copy_process+0x5d1/0x3d50 kernel/fork.c:2206    kernel_clone+0x223/0x880 kernel/fork.c:2787    kernel_thread+0x1bc/0x240 kernel/fork.c:2849    create_kthread kernel/kthread.c:412 [inline]    kthreadd+0x60d/0x810 kernel/kthread.c:765    ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244    Freed by task 61:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579    poison_slab_object mm/kasan/common.c:247 [inline]    __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264    kasan_slab_free include/linux/kasan.h:230 [inline]    slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix a NULL pointer dereference when failed to start a new trasacntion  [BUG] Syzbot reported a NULL pointer dereference with the following crash:    FAULT_INJECTION: forcing a failure.    start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676    prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642    relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678   ...   BTRFS info (device loop0): balance: ended with status: -12   Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI   KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667]   RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926   Call Trace:    \u0026lt;TASK\u0026gt;    commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496    btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430    del_balance_item fs/btrfs/volumes.c:3678 [inline]    reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742    btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574    btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:907 [inline]    __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893    do_syscall_x64 arch/x86/entry/common.c:52 [inline]    do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83    entry_SYSCALL_64_after_hwframe+0x77/0x7f  [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL.  Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree.  However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume.  Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots().  That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference.  [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree.  That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color  management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the  number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: check if leafidx greater than num leaves per dmap tree  syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf.  Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uaf in dbFreeBits  [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216  CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  __mutex_lock_common kernel/locking/mutex.c:587 [inline]  __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752  dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390  dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]  dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409  dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650  jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100  jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  Freed by task 5218:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579  poison_slab_object+0xe0/0x150 mm/kasan/common.c:240  __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2252 [inline]  slab_free mm/slub.c:4473 [inline]  kfree+0x149/0x360 mm/slub.c:4594  dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278  jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247  jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454  reconfigure_super+0x445/0x880 fs/super.c:1083  vfs_cmd_reconfigure fs/fsopen.c:263 [inline]  vfs_fsconfig_locked fs/fsopen.c:292 [inline]  __do_sys_fsconfig fs/fsopen.c:473 [inline]  __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf.  Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error if set_output_gamma is null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for head_pipe in dcn32_acquire_idle_pipe_for_head_pipe_in_layer  This commit addresses a potential null pointer dereference issue in the `dcn32_acquire_idle_pipe_for_head_pipe_in_layer` function. The issue could occur when `head_pipe` is null.  The fix adds a check to ensure `head_pipe` is not null before asserting it. If `head_pipe` is null, the function returns NULL to prevent a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn32/dcn32_resource.c:2690 dcn32_acquire_idle_pipe_for_head_pipe_in_layer() error: we previously assumed \u0026apos;head_pipe\u0026apos; could be null (see line 2681)(CVE-2024-49918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for head_pipe in dcn201_acquire_free_pipe_for_layer  This commit addresses a potential null pointer dereference issue in the `dcn201_acquire_free_pipe_for_layer` function. The issue could occur when `head_pipe` is null.  The fix adds a check to ensure `head_pipe` is not null before asserting it. If `head_pipe` is null, the function returns NULL to prevent a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn201/dcn201_resource.c:1016 dcn201_acquire_free_pipe_for_layer() error: we previously assumed \u0026apos;head_pipe\u0026apos; could be null (see line 1010)(CVE-2024-49919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/ioapic: Handle allocation failures gracefully  Breno observed panics when using failslab under certain conditions during runtime:     can not alloc irq_pin_list (-1,0,20)    Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed     panic+0x4e9/0x590    mp_irqdomain_alloc+0x9ab/0xa80    irq_domain_alloc_irqs_locked+0x25d/0x8d0    __irq_domain_alloc_irqs+0x80/0x110    mp_map_pin_to_irq+0x645/0x890    acpi_register_gsi_ioapic+0xe6/0x150    hpet_open+0x313/0x480  That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed.  The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode.  Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: remove unreasonable unlock in ocfs2_read_blocks  Patch series \u0026quot;Misc fixes for ocfs2_read_blocks\u0026quot;, v5.  This series contains 2 fixes for ocfs2_read_blocks().  The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks().  The second patch fixes an issue reported by Heming Zhao when reviewing above fix.   This patch (of 2):  There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 color transformation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Limit the number of concurrent async COPY operations  Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.  Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.  An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.  If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Drop interface_lock in stop_kthread()  stop_kthread() is the offline callback for \u0026quot;trace/osnoise:online\u0026quot;, since commit 5bfbcd1ee57b (\u0026quot;tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread()\u0026quot;), the following ABBA deadlock scenario is introduced:  T1                            | T2 [BP]               | T3 [AP] osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()                               |   _cpu_down()         |   osnoise_cpu_die()   mutex_lock(\u0026amp;interface_lock) |                       |     stop_kthread()                               |     cpus_write_lock() |       mutex_lock(\u0026amp;interface_lock)   cpus_read_lock()            |     cpuhp_kick_ap()   |  As the interface_lock here in just for protecting the \u0026quot;kthread\u0026quot; field of the osn_var, use xchg() instead to fix this issue. Also use for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take cpu_read_lock() again.(CVE-2024-49976)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume  In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.  This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks.  Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: asihpi: Fix potential OOB array access  ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware.  We shouldn\u0026apos;t trust it blindly.  This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cpufreq: Avoid a bad reference count on CPU node  In the parse_perf_domain function, if the call to of_parse_phandle_with_args returns an error, then the reference to the CPU device node that was acquired at the start of the function would not be properly decremented.  Address this by declaring the variable with the __free(device_node) cleanup attribute.(CVE-2024-50012)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()  On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog:  [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701]   ESR = 0x0000000096000007 [232066.588862]   EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084]   SET = 0, FnV = 0 [232066.589216]   EA = 0, S1PTW = 0 [232066.589340]   FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683]   ISV = 0, ISS = 0x00000007 [232066.589842]   CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052]  vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\\x93\\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointer before dereferencing se  [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  usb: typec: tipd: Free IRQ only if it was requested before  In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client-\u0026gt;irq is set. This fixes the warning caused by the tps6598x module removal:  WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace:   devm_free_irq+0x80/0x8c   tps6598x_remove+0x28/0x88 [tps6598x]   i2c_device_remove+0x2c/0x9c   device_remove+0x4c/0x80   device_release_driver_internal+0x1cc/0x228   driver_detach+0x50/0x98   bus_remove_driver+0x6c/0xbc   driver_unregister+0x30/0x60   i2c_del_driver+0x54/0x64   tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x]   __arm64_sys_delete_module+0x184/0x264   invoke_syscall+0x48/0x110   el0_svc_common.constprop.0+0xc8/0xe8   do_el0_svc+0x20/0x2c   el0_svc+0x28/0x98   el0t_64_sync_handler+0x13c/0x158   el0t_64_sync+0x190/0x194(CVE-2024-50057)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntfs3: Change to non-blocking allocation in ntfs_d_hash  d_hash is done while under \u0026quot;rcu-walk\u0026quot; and should not sleep. __get_name() allocates using GFP_KERNEL, having the possibility to sleep when under memory pressure. Change the allocation to GFP_NOWAIT.(CVE-2024-50065)","status":"published","published":"2024-11-01T11:07:48Z","modified":"2026-08-18T01:18:37.647291563Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"RHSA-2025:6966","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2025-05-14T10:05:42Z","modified":"2026-10-17T10:06:54Z","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:17.133041Z"},{"id":"UBUNTU-CVE-2024-46724","description":"In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number Check the fb_channel_number range to avoid the array out-of-bounds read error","status":"published","published":"2024-09-18T07:15:00Z","modified":"2026-10-29T20:04:10.370315015Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T16:55:02.636559Z"},{"id":"CLSA-2024-1727690025","title":"kernel: Fix of 80 CVEs","description":"- sch/netem: fix use after free in netem_dequeue {CVE-2024-46800}\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() {CVE-2024-46738}\n- drm/amdgpu: Fix out-of-bounds write warning {CVE-2024-46725}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- drm/amdgpu: fix ucode out-of-bounds read warning {CVE-2024-46723}\n- drm/amdgpu: fix mc_data out-of-bounds read warning {CVE-2024-46722}\n- scsi: aacraid: Fix double-free on probe failure {CVE-2024-46673}\n- ipv6: prevent UAF in ip6_send_skb() {CVE-2024-44987}\n- exec: Fix ToCToU between perm check and set-uid/gid usage {CVE-2024-43882}\n- dev/parport: fix the array out-of-bounds risk {CVE-2024-42301}\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs {CVE-2024-42285}\n- tipc: Return non-zero value from tipc_udp_addr2str() on error {CVE-2024-42284}\n- mISDN: Fix a use after free in hfcmulti_tx() {CVE-2024-42280}\n- nvme: avoid double free special payload {CVE-2024-41073}\n- wifi: mac80211: Avoid address calculations via out of bounds array indexing {CVE-2024-41071}\n- xfs: don't walk off the end of a directory data block {CVE-2024-41013}\n- tunnels: fix out of bounds access when building IPv6 PMTU error {CVE-2024-26665}\n- KVM: x86/mmu: make apf token non-zero to fix bug {CVE-2022-48943}\n- cifs: fix double free race when mount fails in cifs_get_root() {CVE-2022-48919}\n- netfilter: fix use-after-free in __nf_register_net_hook() {CVE-2022-48912}\n- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() {CVE-2022-48742}\n- selinux: fix double free of cond_list on error paths {CVE-2022-48740}\n- ALSA: hda: Fix UAF of leds class devs at unbinding {CVE-2022-48735}\n- drm/nouveau: fix off by one in BIOS boundary checking {CVE-2022-48732}\n- mm, slub: fix potential memoryleak in kmem_cache_open() {CVE-2021-47466}\n- x86/coco: Disable 32-bit emulation by default on TDX and SEV {CVE-2024-25744}\n- x86: Make IA32_EMULATION boot time configurable {CVE-2024-25744}\n- x86/entry: Make IA32 syscalls' availability depend on ia32_enabled() {CVE-2024-25744}\n- x86/elf: Make loading of 32bit processes depend on ia32_enabled() {CVE-2024-25744}\n- x86/entry: Rename ignore_sysret() {CVE-2024-25744}\n- x86/cpu: Don't write CSTAR MSR on Intel CPUs {CVE-2024-25744}\n- x86: Introduce ia32_enabled() {CVE-2024-25744}\n- scsi: qedf: Make qedf_execute_tmf() non-preemptible {CVE-2024-42124}\n- ftruncate: pass a signed offset {CVE-2024-42084}\n- USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor {CVE-2024-41035}\n- xfs: add bounds checking to xlog_recover_process_data {CVE-2024-41014}\n- drm/radeon: fix UBSAN warning in kv_dpm.c {CVE-2024-40988}\n- ring-buffer: Fix a race between readers and resize checks {CVE-2024-38601}\n- Input: cyapa - add missing input core locking to suspend/resume functions {CVE-2023-52884}\n- Input: synaptics-rmi4 - fix use after free in rmi_unregister_function() {CVE-2023-52840}\n- wifi: ath11k: fix htt pktlog locking {CVE-2023-52800}\n- wifi: ath11k: fix dfs radar event locking {CVE-2023-52798}\n- ACPI: LPIT: Avoid u32 multiplication overflow {CVE-2023-52683}\n- ACPI: extlog: fix NULL pointer dereference check {CVE-2023-52605}\n- HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect {CVE-2023-52478}\n- USB: core: Fix hang in usb_kill_urb by adding memory barriers {CVE-2022-48760}\n- phylib: fix potential use-after-free {CVE-2022-48754}\n- serial: core: fix transmit-buffer reset and memleak {CVE-2021-47527}\n- nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells {CVE-2021-47497}\n- mlxsw: thermal: Fix out-of-bounds memory accesses {CVE-2021-47441}\n- hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs {CVE-2021-47393}\n- hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47386}\n- hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47385}\n- hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47384}\n- virtio-net: Add validation for used length {CVE-2021-47352}\n- watchdog: Fix possible use-after-free by calling del_timer_sync() {CVE-2021-47321}\n- ACPI: fix NULL pointer dereference {CVE-2021-47289}\n- ipv6: prevent possible NULL dereference in rt6_probe() {CVE-2024-40960}\n- xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() {CVE-2024-40959}\n- wifi: iwlwifi: mvm: don't read past the mfuart notifcation {CVE-2024-40941}\n- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}\n- wifi: mac80211: Fix deadlock in ieee80211_sta_ps_deliver_wakeup() {CVE-2024-40912}\n- USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages {CVE-2024-40904}\n- scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory {CVE-2024-40901}\n- liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet {CVE-2024-39506}\n- vmci: prevent speculation leaks by sanitizing event in event_deliver() {CVE-2024-39499}\n- crypto: bcm - Fix pointer arithmetic {CVE-2024-38579}\n- scsi: qedf: Ensure the copied buf is NUL terminated {CVE-2024-38559}\n- net: openvswitch: fix overwriting ct original tuple for ICMPv6 {CVE-2024-38558}\n- scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload {CVE-2024-36919}\n- netfilter: complete validation of user input {CVE-2024-35962}\n- VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() {CVE-2024-35944}\n- ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit() {CVE-2024-26894}\n- dm: call the resume method on internal suspend {CVE-2024-26880}\n- net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink() {CVE-2024-26855}\n- mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again {CVE-2024-26720}\n- tracing: Ensure visibility when inserting an element into tracing_map {CVE-2024-26645}\n- scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() {CVE-2023-52809}\n- drm/radeon: check the alloc_workqueue return value in radeon_crtc_init() {CVE-2023-52470}\n- Input: add bounds checking to input_set_capability() {CVE-2022-48619}\n- tty: Fix out-of-bound vmalloc access in imageblit {CVE-2021-47383}\n- bnx2x: Fix multiple UBSAN array-index-out-of-bounds {CVE-2024-42148}\n- net: do not leave a dangling sk pointer, when socket creation fails {CVE-2024-40954}\n- media: xc2028: avoid use-after-free in load_firmware_cb() {CVE-2024-43900}\n- fou: remove warn in gue_gro_receive on unsupported protocol {CVE-2024-44940}\n- PCI/MSI: Fix UAF in msi_capability_init {CVE-2024-41096}","status":"published","published":"2024-09-30T09:53:48Z","modified":"2026-10-21T10:48:08.155755561Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1727690947","title":"kernel: Fix of 80 CVEs","description":"- sch/netem: fix use after free in netem_dequeue {CVE-2024-46800}\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() {CVE-2024-46738}\n- drm/amdgpu: Fix out-of-bounds write warning {CVE-2024-46725}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- drm/amdgpu: fix ucode out-of-bounds read warning {CVE-2024-46723}\n- drm/amdgpu: fix mc_data out-of-bounds read warning {CVE-2024-46722}\n- scsi: aacraid: Fix double-free on probe failure {CVE-2024-46673}\n- ipv6: prevent UAF in ip6_send_skb() {CVE-2024-44987}\n- exec: Fix ToCToU between perm check and set-uid/gid usage {CVE-2024-43882}\n- dev/parport: fix the array out-of-bounds risk {CVE-2024-42301}\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs {CVE-2024-42285}\n- tipc: Return non-zero value from tipc_udp_addr2str() on error {CVE-2024-42284}\n- mISDN: Fix a use after free in hfcmulti_tx() {CVE-2024-42280}\n- nvme: avoid double free special payload {CVE-2024-41073}\n- wifi: mac80211: Avoid address calculations via out of bounds array indexing {CVE-2024-41071}\n- xfs: don't walk off the end of a directory data block {CVE-2024-41013}\n- tunnels: fix out of bounds access when building IPv6 PMTU error {CVE-2024-26665}\n- KVM: x86/mmu: make apf token non-zero to fix bug {CVE-2022-48943}\n- cifs: fix double free race when mount fails in cifs_get_root() {CVE-2022-48919}\n- netfilter: fix use-after-free in __nf_register_net_hook() {CVE-2022-48912}\n- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() {CVE-2022-48742}\n- selinux: fix double free of cond_list on error paths {CVE-2022-48740}\n- ALSA: hda: Fix UAF of leds class devs at unbinding {CVE-2022-48735}\n- drm/nouveau: fix off by one in BIOS boundary checking {CVE-2022-48732}\n- mm, slub: fix potential memoryleak in kmem_cache_open() {CVE-2021-47466}\n- x86/coco: Disable 32-bit emulation by default on TDX and SEV {CVE-2024-25744}\n- x86: Make IA32_EMULATION boot time configurable {CVE-2024-25744}\n- x86/entry: Make IA32 syscalls' availability depend on ia32_enabled() {CVE-2024-25744}\n- x86/elf: Make loading of 32bit processes depend on ia32_enabled() {CVE-2024-25744}\n- x86/entry: Rename ignore_sysret() {CVE-2024-25744}\n- x86/cpu: Don't write CSTAR MSR on Intel CPUs {CVE-2024-25744}\n- x86: Introduce ia32_enabled() {CVE-2024-25744}\n- x86/asm/64: Change all ENTRY+END to SYM_CODE_* {CVE-2024-25744}\n- x86/head/64: Annotate start_cpu0() as non-callable {CVE-2024-25744}\n- x86/asm: Do not annotate functions with GLOBAL {CVE-2024-25744}\n- kprobes/x86/xen: blacklist non-attachable xen interrupt functions {CVE-2024-25744}\n- x86/asm/64: Add ENDs to some functions and relabel with SYM_CODE_* {CVE-2024-25744}\n- x86/asm: Use SYM_INNER_LABEL instead of GLOBAL {CVE-2024-25744}\n- x86/asm: Annotate aliases {CVE-2024-25744}\n- x86/asm/crypto: Annotate local functions {CVE-2024-25744}\n- scsi: qedf: Make qedf_execute_tmf() non-preemptible {CVE-2024-42124}\n- ftruncate: pass a signed offset {CVE-2024-42084}\n- USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor {CVE-2024-41035}\n- xfs: add bounds checking to xlog_recover_process_data {CVE-2024-41014}\n- drm/radeon: fix UBSAN warning in kv_dpm.c {CVE-2024-40988}\n- ring-buffer: Fix a race between readers and resize checks {CVE-2024-38601}\n- Input: cyapa - add missing input core locking to suspend/resume functions {CVE-2023-52884}\n- Input: synaptics-rmi4 - fix use after free in rmi_unregister_function() {CVE-2023-52840}\n- wifi: ath11k: fix htt pktlog locking {CVE-2023-52800}\n- wifi: ath11k: fix dfs radar event locking {CVE-2023-52798}\n- ACPI: LPIT: Avoid u32 multiplication overflow {CVE-2023-52683}\n- ACPI: extlog: fix NULL pointer dereference check {CVE-2023-52605}\n- HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect {CVE-2023-52478}\n- USB: core: Fix hang in usb_kill_urb by adding memory barriers {CVE-2022-48760}\n- phylib: fix potential use-after-free {CVE-2022-48754}\n- serial: core: fix transmit-buffer reset and memleak {CVE-2021-47527}\n- nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells {CVE-2021-47497}\n- mlxsw: thermal: Fix out-of-bounds memory accesses {CVE-2021-47441}\n- hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs {CVE-2021-47393}\n- hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47386}\n- hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47385}\n- hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field {CVE-2021-47384}\n- virtio-net: Add validation for used length {CVE-2021-47352}\n- watchdog: Fix possible use-after-free by calling del_timer_sync() {CVE-2021-47321}\n- ACPI: fix NULL pointer dereference {CVE-2021-47289}\n- ipv6: prevent possible NULL dereference in rt6_probe() {CVE-2024-40960}\n- xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() {CVE-2024-40959}\n- wifi: iwlwifi: mvm: don't read past the mfuart notifcation {CVE-2024-40941}\n- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}\n- wifi: mac80211: Fix deadlock in ieee80211_sta_ps_deliver_wakeup() {CVE-2024-40912}\n- USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages {CVE-2024-40904}\n- scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory {CVE-2024-40901}\n- liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet {CVE-2024-39506}\n- vmci: prevent speculation leaks by sanitizing event in event_deliver() {CVE-2024-39499}\n- crypto: bcm - Fix pointer arithmetic {CVE-2024-38579}\n- scsi: qedf: Ensure the copied buf is NUL terminated {CVE-2024-38559}\n- net: openvswitch: fix overwriting ct original tuple for ICMPv6 {CVE-2024-38558}\n- scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload {CVE-2024-36919}\n- netfilter: complete validation of user input {CVE-2024-35962}\n- VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() {CVE-2024-35944}\n- ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit() {CVE-2024-26894}\n- dm: call the resume method on internal suspend {CVE-2024-26880}\n- net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink() {CVE-2024-26855}\n- mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again {CVE-2024-26720}\n- tracing: Ensure visibility when inserting an element into tracing_map {CVE-2024-26645}\n- scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() {CVE-2023-52809}\n- drm/radeon: check the alloc_workqueue return value in radeon_crtc_init() {CVE-2023-52470}\n- Input: add bounds checking to input_set_capability() {CVE-2022-48619}\n- tty: Fix out-of-bound vmalloc access in imageblit {CVE-2021-47383}\n- bnx2x: Fix multiple UBSAN array-index-out-of-bounds {CVE-2024-42148}\n- net: do not leave a dangling sk pointer, when socket creation fails {CVE-2024-40954}\n- media: xc2028: avoid use-after-free in load_firmware_cb() {CVE-2024-43900}\n- fou: remove warn in gue_gro_receive on unsupported protocol {CVE-2024-44940}\n- PCI/MSI: Fix UAF in msi_capability_init {CVE-2024-41096}","status":"published","published":"2024-09-30T10:09:11Z","modified":"2026-10-21T10:46:01.716574069Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1727692412","title":"kernel: Fix of 5 CVEs","description":"- sch/netem: fix use after free in netem_dequeue {CVE-2024-46800}\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() {CVE-2024-46738}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- drm/amdgpu: fix ucode out-of-bounds read warning {CVE-2024-46723}\n- drm/amdgpu: fix mc_data out-of-bounds read warning {CVE-2024-46722}","status":"published","published":"2024-09-30T10:33:35Z","modified":"2026-10-21T10:47:54.441173077Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1728936982","title":"kernel: Fix of 86 CVEs","description":"- drm/amd/pm: Fix negative array index read {CVE-2024-46821}\n- drm/amd/display: Check gpio_id before used as array index {CVE-2024-46818}\n- drm/amd/display: Check link_index before accessing dc-\u003elinks[] {CVE-2024-46813}\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box {CVE-2024-46811}\n- Squashfs: sanity check symbolic link size {CVE-2024-46744}\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses {CVE-2024-46859}\n- net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() {CVE-2024-40995}\n- net/sched: act_api: rely on rcu in tcf_idr_check_alloc {CVE-2024-40995}\n- netfilter: bridge: confirm multicast packets before passing them up the stack {CVE-2024-27415}\n- netfilter: let reset rules clean out conntrack entries {CVE-2024-27415}\n- mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray {CVE-2024-42243}\n- gpiolib: cdev: Fix use after free in lineinfo_changed_notify {CVE-2024-36899}\n- bpf, sockmap: Prevent lock inversion deadlock in map delete elem {CVE-2024-35895}\n- bpf, sockmap: Fix preempt_rt splat when using raw_spin_lock_t {CVE-2024-35895}\n- mm/huge_memory: don't unpoison huge_zero_folio {CVE-2024-40914}\n- cxgb4: fix use after free bugs caused by circular dependency problem {CVE-2023-4133}\n- timers: Restore ABI Compatibility with timer_delete Functions {CVE-2023-4133}\n- timers: Provide timer_shutdown[_sync]() {CVE-2023-4133}\n- timers: Add shutdown mechanism to the internal functions {CVE-2023-4133}\n- timers: Split [try_to_]del_timer[_sync]() to prepare for shutdown mode {CVE-2023-4133}\n- timers: Silently ignore timers with a NULL function {CVE-2023-4133}\n- timers: Rename del_timer() to timer_delete() {CVE-2023-4133}\n- timers: Rename del_timer_sync() to timer_delete_sync() {CVE-2023-4133}\n- timers: Use del_timer_sync() even on UP {CVE-2023-4133}\n- timers: Update kernel-doc for various functions {CVE-2023-4133}\n- timers: Replace BUG_ON()s {CVE-2023-4133}\n- timers: Get rid of del_singleshot_timer_sync() {CVE-2023-4133}\n- clocksource/drivers/sp804: Do not use timer namespace for timer_shutdown() function {CVE-2023-4133}\n- clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function {CVE-2023-4133}\n- mm: avoid overflows in dirty throttling logic {CVE-2024-42131}\n- ring-buffer: Fix a race between readers and resize checks {CVE-2024-38601}\n- igc: avoid returning frame twice in XDP_REDIRECT {CVE-2024-26853}\n- igc: Avoid transmit queue timeout for XDP {CVE-2024-26853}\n- nfsd: fix RELEASE_LOCKOWNER {CVE-2024-26629}\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc {CVE-2023-52880}\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment {CVE-2024-42152}\n- net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() {CVE-2024-42110}\n- x86: stop playing stack games in profile_pc() {CVE-2024-42096}\n- xdp: Remove WARN() from __xdp_reg_mem_model() {CVE-2024-42082}\n- NFSv4: Fix memory leak in nfs4_set_security_label {CVE-2024-41076}\n- ppp: reject claimed-as-LCP but actually malformed packets {CVE-2024-41044}\n- udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port(). {CVE-2024-41041}\n- sched/deadline: Fix task_struct reference leak {CVE-2024-41023}\n- tipc: force a dst refcount before doing decryption {CVE-2024-40983}\n- scsi: qedi: Fix crash while reading debugfs attribute {CVE-2024-40978}\n- wifi: iwlwifi: mvm: don't read past the mfuart notifcation {CVE-2024-40941}\n- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}\n- xhci: Handle TD clearing for multiple streams case {CVE-2024-40927}\n- wifi: mac80211: Fix deadlock in ieee80211_sta_ps_deliver_wakeup() {CVE-2024-40912}\n- wifi: cfg80211: Lock wiphy in cfg80211_get_station {CVE-2024-40911}\n- ipv6: fix possible race in __fib6_drop_pcpu_from() {CVE-2024-40905}\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING {CVE-2024-39476}\n- usb-storage: alauda: Check whether the media is initialized {CVE-2024-38619}\n- usb-storage: alauda: Fix uninit-value in alauda_check_media() {CVE-2024-38619}\n- crypto: bcm - Fix pointer arithmetic {CVE-2024-38579}\n- scsi: qedf: Ensure the copied buf is NUL terminated {CVE-2024-38559}\n- wifi: nl80211: don't free NULL coalescing rule {CVE-2024-36941}\n- scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() {CVE-2024-36025}\n- netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() {CVE-2024-35898}\n- mlxsw: spectrum_acl_tcam: Fix memory leak when canceling rehash work {CVE-2024-35852}\n- wifi: iwlwifi: dbg-tlv: ensure NUL termination {CVE-2024-35845}\n- KVM: SVM: Flush pages under kvm-\u003elock to fix UAF in svm_register_enc_region() {CVE-2024-35791}\n- wifi: mac80211: check/clear fast rx for non-4addr sta VLAN changes {CVE-2024-35789}\n- wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work {CVE-2024-27052}\n- nfp: flower: handle acti_netdevs allocation failure {CVE-2024-27046}\n- octeontx2-af: Use separate handlers for interrupts {CVE-2024-27030}\n- netfilter: flowtable: validate pppoe header {CVE-2024-27016}\n- kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address {CVE-2024-26946}\n- scsi: qla2xxx: Fix command flush on cable pull {CVE-2024-26931}\n- net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink() {CVE-2024-26855}\n- bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel {CVE-2024-26737}\n- Input: cyapa - add missing input core locking to suspend/resume functions {CVE-2023-52884}\n- bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself {CVE-2023-52735}\n- wifi: ath10k: fix NULL pointer dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() {CVE-2023-52651}\n- net: tap_open(): set sk_uid from current_fsuid() {CVE-2023-4194}\n- net: tun_chr_open(): set sk_uid from current_fsuid() {CVE-2023-4194}\n- seg6: fix the iif in the IPv6 socket control block {CVE-2021-47515}\n- tty: Fix out-of-bound vmalloc access in imageblit {CVE-2021-47383}\n- bnx2x: Fix multiple UBSAN array-index-out-of-bounds {CVE-2024-42148}\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes {CVE-2024-46759}\n- net: bridge: mst: fix vlan use-after-free {CVE-2024-36979}\n- stm class: Fix a double free in stm_register_device() {CVE-2024-38627}\n- wifi: mac80211: Avoid address calculations via out of bounds array indexing {CVE-2024-41071}\n- of/irq: Prevent device address out-of-bounds read in interrupt map walk {CVE-2024-46743}\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup {CVE-2024-46747}\n- drm/amdgpu: fix mc_data out-of-bounds read warning {CVE-2024-46722}\n- drm/amdgpu: Fix out-of-bounds write warning {CVE-2024-46725}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- wifi: nl80211: Avoid address calculations via out of bounds array indexing {CVE-2024-38562}\n- wifi: nl80211: convert cfg80211_scan_request allocation to *_size macros {CVE-2024-38562}\n- overflow: Implement size_t saturating arithmetic helpers {CVE-2024-38562}\n- cdrom: rearrange last_media_change check to avoid unintentional overflow {CVE-2024-42136}\n- ftrace: Fix possible use-after-free issue in ftrace_location() {CVE-2024-38588}\n- ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() {CVE-2024-38588}\n- drm/amdgpu: fix ucode out-of-bounds read warning {CVE-2024-46723}\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() {CVE-2024-46738}\n- sch/netem: fix use after free in netem_dequeue {CVE-2024-46800}\n- firmware: cs_dsp: Fix overflow checking of wmfw header {CVE-2024-41039}\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes {CVE-2024-46758}\n- HID: amd_sfh: free driver_data after destroying hid device {CVE-2024-46746}\n- xfs: don't walk off the end of a directory data block {CVE-2024-41013}\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes {CVE-2024-46756}\n- tunnels: fix out of bounds access when building IPv6 PMTU error {CVE-2024-26665}\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes {CVE-2024-46757}\n- drm/amd/pm: fix the Out-of-bounds read warning {CVE-2024-46731}\n- drm/amdgpu/mes: fix mes ring buffer overflow {CVE-2024-46700}\n- exec: Fix ToCToU between perm check and set-uid/gid usage {CVE-2024-43882}\n- PCI/MSI: Fix UAF in msi_capability_init {CVE-2024-41096}","status":"published","published":"2024-10-14T20:16:26Z","modified":"2026-10-21T10:45:20.569978861Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1729874131","title":"kernel: Fix of 38 CVEs","description":"- drm/amdgpu: Validate TA binary size {CVE-2024-44977}\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t {CVE-2024-47661}\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info {CVE-2024-46842}\n- ALSA: line6: Fix racy access to midibuf {CVE-2024-44954}\n- exec: Fix ToCToU between perm check and set-uid/gid usage {CVE-2024-43882}\n- drm/amd/display: Check link_index before accessing dc-\u003elinks[] {CVE-2024-46813}\n- drm/amdgpu/mes: fix mes ring buffer overflow {CVE-2024-46700}\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs {CVE-2024-42285}\n- scsi: aacraid: Fix double-free on probe failure {CVE-2024-46673}\n- ipv6: prevent UAF in ip6_send_skb() {CVE-2024-44987}\n- drm/amdgpu: fix mc_data out-of-bounds read warning {CVE-2024-46722}\n- ftrace: Fix possible use-after-free issue in ftrace_location() {CVE-2024-38588}\n- ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() {CVE-2024-38588}\n- ftrace: Store the order of pages allocated in ftrace_page {CVE-2024-38588}\n- ftrace: Check if pages were allocated before calling free_pages() {CVE-2024-38588}\n- x86/ibt,ftrace: Search for __fentry__ location {CVE-2024-38588}\n- drm/amdgpu: fix ucode out-of-bounds read warning {CVE-2024-46723}\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() {CVE-2024-46738}\n- sch/netem: fix use after free in netem_dequeue {CVE-2024-46800}\n- drm/amdgpu: Fix out-of-bounds write warning {CVE-2024-46725}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- Squashfs: sanity check symbolic link size {CVE-2024-46744}\n- drm/amd/pm: Fix negative array index read {CVE-2024-46821}\n- drm/amd/display: Check gpio_id before used as array index {CVE-2024-46818}\n- KVM: x86: do not set st-\u003epreempted when going back to user space {CVE-2022-39189}\n- net: Return errno in sk-\u003esk_prot-\u003eget_port(). {CVE-2023-0461}\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box {CVE-2024-46811}\n- ext4: do not create EA inode under buffer lock {CVE-2024-40972}\n- ext4: fold quota accounting into ext4_xattr_inode_lookup_create() {CVE-2024-40972}\n- ext4: check the return value of ext4_xattr_inode_dec_ref() {CVE-2024-40972}\n- ext4: remove duplicate definition of ext4_xattr_ibody_inline_set() {CVE-2024-40972}\n- nvme: avoid double free special payload {CVE-2024-41073}\n- drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL {CVE-2023-52817}\n- wifi: mac80211: Avoid address calculations via out of bounds array indexing {CVE-2024-41071}\n- mISDN: Fix a use after free in hfcmulti_tx() {CVE-2024-42280}\n- tipc: Return non-zero value from tipc_udp_addr2str() on error {CVE-2024-42284}\n- dev/parport: fix the array out-of-bounds risk {CVE-2024-42301}\n- parport: Standardize use of printmode {CVE-2024-42301}\n- parport: Convert printk(KERN_\u003cLEVEL\u003e to pr_\u003clevel\u003e {CVE-2024-42301}\n- parport: parport_pc: Mark expected switch fall-through {CVE-2024-42301}\n- protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions {CVE-2024-42265}\n- leds: trigger: Unregister sysfs attributes before calling deactivate() {CVE-2024-43830}\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes {CVE-2024-46758}\n- HID: amd_sfh: free driver_data after destroying hid device {CVE-2024-46746}\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes {CVE-2024-46759}\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes {CVE-2024-46756}\n- netns: Make get_net_ns() handle zero refcount net {CVE-2024-40958}\n- net: make get_net_ns return error if NET_NS is disabled {CVE-2024-40958}\n- mm, slub: fix potential memoryleak in kmem_cache_open() {CVE-2021-47466}\n- slub: don't panic for memcg kmem cache creation failure {CVE-2021-47466}\n- tunnels: fix out of bounds access when building IPv6 PMTU error {CVE-2024-26665}\n- xfs: don't walk off the end of a directory data block {CVE-2024-42084}\n- firmware: cs_dsp: Fix overflow checking of wmfw header {CVE-2024-41039}\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes {CVE-2024-46757}\n- drm/amd/pm: fix the Out-of-bounds read warning {CVE-2024-46731}","status":"published","published":"2026-10-18T04:02:36Z","modified":"2026-10-26T09:31:37.233051912Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2026-1775655705","title":"kernel-uek: Fix of 34 CVEs","description":"- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}\n- HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}\n- KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory {CVE-2024-50115}\n- KVM: x86: Reset IRTE to host control if *new* route isn't postable {CVE-2025-37885}\n- NFSD: Protect against send buffer overflow in NFSv2 READ {CVE-2022-43945}\n- NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}\n- Revert \"IB/core: Implement clear counters\"\n- Revert \"IB/mlx5: Implement clear counters\"\n- Revert \"ib/core: add SET_DEVICE_OP call for clear_hw_stats()\"\n- Revert \"perf/x86: Always store regs-\u003eip in perf_callchain_kernel()\"\n- Revert \"xfrm: destroy xfrm_state synchronously on net exit path\"\n- bpf, sockmap: Fix race between element replace and close() {CVE-2024-56664}\n- can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak {CVE-2026-23061}\n- crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec {CVE-2026-23060}\n- crypto: lzo - Fix compression buffer overrun {CVE-2025-38068}\n- drm/amd/pm: fix the Out-of-bounds read warning {CVE-2024-46731}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer {CVE-2024-49991}\n- ext4/jbd2: skip sb flush when EIO happened\n- ext4: save the error code which triggered an\n- fou: remove warn in gue_gro_receive on unsupported protocol {CVE-2024-44940}\n- fs: proc: inode: delay put_pid() by RCU\n- fs: writeback: fix use-after-free in __mark_inode_dirty() {CVE-2025-39866}\n- genirq/cpuhotplug: Notify about affinity changes breaking the affinity mask\n- io_uring: fix filename leak in __io_openat_prep() {CVE-2025-68814}\n- jbd2: store more accurate errno in superblock\n- libceph: fix potential use-after-free in have_mon_and_osd_map() {CVE-2025-68285}\n- libceph: make free_choose_arg_map() resilient to partial allocation {CVE-2026-22991}\n- macvlan: Add nodst option to macvlan type source\n- macvlan: Use 'hash' iterators to simplify code\n- macvlan: fix error recovery in macvlan_common_newlink() {CVE-2026-23209}\n- macvlan: fix possible UAF in macvlan_forward_source() {CVE-2026-23001}\n- macvlan: observe an RCU grace period in macvlan_common_newlink() error path {CVE-2026-23273}\n- media: xc2028: avoid use-after-free in load_firmware_cb() {CVE-2024-43900}\n- mm: call the security_mmap_file() LSM hook in remap_file_pages() {CVE-2024-47745}\n- net/sched: sch_qfq: do not free existing class in qfq_change_class() {CVE-2026-22999}\n- net: sock: fix hardened usercopy panic in sock_recv_errqueue {CVE-2026-22977}\n- net: usb: rtl8150: fix memory leak on usb_submit_urb() failure {CVE-2025-71154}\n- rds: Add state field to RDS trace logs.\n- rds: Drop rds conn in connect worker if not in down state.\n- scsi: mpi3mr: Sanitise num_phys {CVE-2024-42159}\n- scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() {CVE-2026-23193}\n- tty: n_gsm: Fix use-after-free in gsm_cleanup_mux {CVE-2024-50073}\n- usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}\n- vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint {CVE-2025-22083}\n- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}\n- xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added {CVE-2025-40256}\n- xfrm: delete x-\u003etunnel as we delete x {CVE-2025-40215}\n- xfrm: flush all states in xfrm_state_fini","status":"published","published":"2026-10-19T14:13:57Z","modified":"2026-10-26T09:31:20.776454516Z","updated_at":"2026-11-02T15:43:44.009773Z"},{"id":"CLSA-2026-1787304608","title":"kernel-uek: Fix of 34 CVEs","description":"- Rebased onto Oracle UEK base 5.4.17-2136.357.2.el7uek\n- sctp: don't free the ASCONF's own transport in DEL-IP processing {CVE-2026-64564}\n- ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison {CVE-2026-53309}\n- ocfs2/dlm: validate qr_numregions in dlm_match_regions() {CVE-2026-53043}\n- ixgbevf: fix use-after-free in VEPA multicast source pruning {CVE-2026-64113}\n- ipv4: raw: reject IP_HDRINCL packets with ihl \u003c 5 {CVE-2026-64114}\n- NFSv4: include MAY_WRITE in open permission mask for O_TRUNC {CVE-2026-64298}\n- fuse: re-lock request before returning from fuse_ref_folio() {CVE-2026-64266}\n- scsi: isci: Fix use-after-free in device removal path {CVE-2026-64103}\n- crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec {CVE-2026-23060}\n- futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock {CVE-2026-53166}\n- net: af_key: zero aligned sockaddr tail in PF_KEY exports {CVE-2026-43088}\n- scsi: aic94xx: fix use-after-free in device removal path {CVE-2025-71075}\n- i2c: piix4: Fix adapter not be removed in piix4_remove() {CVE-2022-49900}\n- Bluetooth: MGMT: validate LTK enc_size on load {CVE-2026-43020}\n- ext4: convert inline data to extents when truncate exceeds inline size {CVE-2026-31452}\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() {CVE-2026-31532}\n- ALSA: 6fire: fix use-after-free on disconnect {CVE-2026-31581}\n- ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY {CVE-2026-31597}\n- netfilter: nf_conntrack_helper: pass helper to expect cleanup {CVE-2026-43027}\n- drm/amdgpu: Fix use-after-free race in VM acquire {CVE-2026-43370}\n- xfrm_user: fix info leak in build_mapping() {CVE-2026-43089}\n- xfs: fix freemap adjustments when adding xattrs to leaf blocks {CVE-2026-43158}\n- libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}\n- e1000: fix OOB in e1000_tbi_should_accept() {CVE-2025-71093}\n- ALSA: usb-audio: Use correct version for UAC3 header validation {CVE-2026-23318}\n- nfnetlink_osf: validate individual option lengths in fingerprints {CVE-2026-23397}\n- Squashfs: check metadata block offset is within range {CVE-2026-23388}\n- net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled {CVE-2026-23381}\n- wifi: mac80211: fix NULL deref in mesh_matches_local() {CVE-2026-23396}\n- icmp: fix NULL pointer dereference in icmp_tag_validation() {CVE-2026-23398}\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them {CVE-2026-23382}\n- net: usb: kalmia: validate USB endpoints {CVE-2026-23365}\n- wifi: radiotap: reject radiotap with unknown bits {CVE-2026-23367}\n- drbd: fix \"LOGIC BUG\" in drbd_al_begin_io_nonblock() {CVE-2026-23356}\n- batman-adv: reject oversized global TT response buffers {CVE-2026-31659}\n- drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() {CVE-2026-43206}\n- net: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak {CVE-2026-43040}\n- ALSA: ctxfi: Limit PTP to a single page {CVE-2026-31602}\n- nvdimm/bus: Fix potential use after free in asynchronous initialization {CVE-2026-31399}\n- usb: class: cdc-wdm: fix reordering issue in read code path {CVE-2026-43427}\n- media: dvb-net: fix OOB access in ULE extension header tables {CVE-2026-31405}\n- sysctl: Fix data races in proc_douintvec(). {CVE-2022-49641}\n- netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() {CVE-2026-43450}\n- ALSA: caiaq: fix stack out-of-bounds read in init_card {CVE-2026-31778}\n- atm: lec: fix use-after-free in sock_def_readable() {CVE-2026-43050}\n- fs: writeback: fix use-after-free in __mark_inode_dirty() {CVE-2025-39866}\n- usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}\n- crypto: lzo - Fix compression buffer overrun {CVE-2025-38068}\n- KVM: x86: Reset IRTE to host control if *new* route isn't postable {CVE-2025-37885}\n- vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint {CVE-2025-22083}\n- mm: call the security_mmap_file() LSM hook in remap_file_pages() {CVE-2024-47745}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- fou: remove warn in gue_gro_receive on unsupported protocol {CVE-2024-44940}\n- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}\n- NFSD: Protect against send buffer overflow in NFSv2 READ {CVE-2022-43945}\n- drm/amd/pm: fix the Out-of-bounds read warning {CVE-2024-46731}\n- scsi: mpi3mr: Sanitise num_phys {CVE-2024-42159}\n- NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}\n- net: usb: rtl8150: fix memory leak on usb_submit_urb() failure {CVE-2025-71154}\n- net: sock: fix hardened usercopy panic in sock_recv_errqueue {CVE-2026-22977}\n- can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak {CVE-2026-23061}\n- libceph: make free_choose_arg_map() resilient to partial allocation {CVE-2026-22991}\n- net/sched: sch_qfq: do not free existing class in qfq_change_class() {CVE-2026-22999}\n- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}\n- drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer {CVE-2024-49991}\n- HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}\n- bpf, sockmap: Fix race between element replace and close() {CVE-2024-56664}\n- KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory {CVE-2024-50115}\n- tty: n_gsm: Fix use-after-free in gsm_cleanup_mux {CVE-2024-50073}\n- media: xc2028: avoid use-after-free in load_firmware_cb() {CVE-2024-43900}\n- libceph: fix potential use-after-free in have_mon_and_osd_map() {CVE-2025-68285}\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write {CVE-2026-31598}\n- xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete {CVE-2026-46116}\n- net/rds: zero per-item info buffer before handing it to visitors {CVE-2026-52995}\n- KVM: x86: Fix shadow paging use-after-free due to unexpected role {CVE-2026-53359}\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN {CVE-2026-46113}\n- net/sched: fix pedit partial COW leading to page cache corruption {CVE-2026-46331}\n- RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv {CVE-2026-46043}\n- locking/rtmutex: Skip remove_waiter() when waiter is not enqueued {CVE-2026-53163}\n- rtmutex: Use waiter::task instead of current in remove_waiter() {CVE-2026-43499}\n- ipv6: icmp: clear skb2-\u003ecb[] in ip6_err_gen_icmpv6_unreach() {CVE-2026-43038}\n- net: skbuff: fix missing zerocopy reference in pskb_carve helpers {CVE-2026-52943}\n- net: fix fanout UAF in packet_release() via NETDEV_UP race {CVE-2026-31504}\n- net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-\u003edev is null {CVE-2022-50073}\n- ip6_tunnel: clear skb2-\u003ecb[] in ip4ip6_err() {CVE-2026-43037}\n- batman-adv: hold claim backbone gateways by reference {CVE-2026-31657}\n- scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker {CVE-2026-63890}\n- scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() {CVE-2026-63888}\n- scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf {CVE-2026-63887}\n- smb: client: reject userspace cifs.spnego descriptions {CVE-2026-46243}\n- tun: free page on build_skb failure in tun_xdp_one() {CVE-2026-46322}\n- tap: free page on error paths in tap_get_user_xdp() {CVE-2026-46320}\n- tun: free page on short-frame rejection in tun_xdp_one() {CVE-2026-46321}\n- ptrace: slightly saner 'get_dumpable()' logic {CVE-2026-46333}\n- net: skbuff: propagate shared-frag marker through frag-transfer helpers {CVE-2026-43503}\n- net: skbuff: preserve shared-frag marker during coalescing {CVE-2026-46300}\n- nfsd: fix heap overflow in NFSv4.0 LOCK replay cache {CVE-2026-31402}\n- scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() {CVE-2026-23216}\n- scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() {CVE-2026-23193}\n- xfrm: esp: avoid in-place decrypt on shared skb frags {CVE-2026-43284}\n- crypto: algif_aead - Fix minimum RX size check for decryption {CVE-2026-43077}\n- crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl {CVE-2026-43078}\n- crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption {CVE-2026-43033}\n- crypto: algif_aead - snapshot IV for async AEAD requests {CVE-2026-46028}\n- crypto: algif_aead - Revert to operating out-of-place {CVE-2026-31431}\n- SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf {CVE-2025-71120}\n- net/sched: Enforce that teql can only be used as root qdisc {CVE-2026-23074}","status":"published","published":"2026-10-19T14:18:25Z","modified":"2026-10-26T09:43:47.142239854Z","updated_at":"2026-11-02T15:43:47.20725Z"},{"id":"CVE-2024-46724","title":"drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\n\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error","status":"published","published":"2024-09-18T06:32:21.22Z","modified":"2026-10-28T02:30:28.756689274Z","updated_at":"2026-11-02T15:44:42.790566Z"},{"id":"DLA-3912-1","title":"linux - security update","status":"published","published":"2024-10-07T00:00:00Z","modified":"2026-03-09T01:20:34.748332Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"DLA-4008-1","title":"linux-6.1 - security update","status":"published","published":"2025-01-02T00:00:00Z","modified":"2026-03-09T02:11:41.013831Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"DSA-5782-1","title":"linux - security update","status":"published","published":"2024-10-03T00:00:00Z","modified":"2026-03-09T02:09:56.413752Z","updated_at":"2026-11-02T15:46:17.892347Z"},{"id":"SUSE-SU-2024: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:4100-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\nThe Linux Enterprise 12 SP5 kernel turned LTSS (Extended Security)\n\nThe following security bugs were fixed:\n\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47163: kABI fix for tipc: wait and exit until all work queues are done (bsc#1221980).\n- CVE-2021-47612: nfc: fix segfault in nfc_genl_dump_devices_done (bsc#1226585).\n- CVE-2022-48809: net: fix a memleak when uncloning an skb dst and its metadata (bsc#1227947).\n- CVE-2022-48951: ASoC: ops: Correct bounds check for second channel on SX controls (bsc#1231929).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48958: ethernet: aeroflex: fix potential skb leak in greth_init_rings() (bsc#1231889).\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-48966: net: mvneta: Fix an out of bounds check (bsc#1232191).\n- CVE-2022-48967: NFC: nci: Bounds check struct nfc_target arrays (bsc#1232304).\n- CVE-2022-48971: Bluetooth: Fix not cleanup led when bt_init fails (bsc#1232037).\n- CVE-2022-48972: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (bsc#1232025).\n- CVE-2022-48973: gpio: amd8111: Fix PCI device reference count leak (bsc#1232039).\n- CVE-2022-48978: HID: core: fix shift-out-of-bounds in hid_report_raw_event (bsc#1232038).\n- CVE-2022-48991: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (bsc#1232070).\n- CVE-2022-48992: ASoC: soc-pcm: Add NULL check in BE reparenting (bsc#1232071).\n- CVE-2022-49000: iommu/vt-d: Fix PCI device refcount leak in has_external_pci() (bsc#1232123).\n- CVE-2022-49002: iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() (bsc#1232133).\n- CVE-2022-49010: hwmon: (coretemp) Check for null before removing sysfs attrs (bsc#1232172).\n- CVE-2022-49011: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() (bsc#1232006).\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-49020: net/9p: Fix a potential socket leak in p9_socket_open (bsc#1232175).\n- CVE-2022-49021: net: phy: fix null-ptr-deref while probe() failed (bsc#1231939).\n- CVE-2022-49026: e100: Fix possible use after free in e100_xmit_prepare (bsc#1231997).\n- CVE-2022-49027: iavf: Fix error handling in iavf_init_module() (bsc#1232007).\n- CVE-2022-49028: ixgbevf: Fix resource leak in ixgbevf_init_module() (bsc#1231996).\n- CVE-2022-49029: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails (bsc#1231995).\n- CVE-2023-52898: xhci: Fix null pointer dereference when host dies (bsc#1229568).\n- CVE-2023-52918: media: pci: cx23885: check cx23885_vdev_init() return (bsc#1232047).\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-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (bsc#1227437).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command  (bsc#1228620).\n- CVE-2024-42114: netlink: extend policy range validation (bsc#1228564 prerequisite).\n- CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race (bsc#1229005 stable-fixes).\n- CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc() (bsc#1229837 stable-fixes).\n- CVE-2024-44958: sched/smt: Fix unbalance sched_smt_present dec/inc (bsc#1230179).\n- CVE-2024-46724: drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (bsc#1230725).\n- CVE-2024-46755: wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (bsc#1230802).\n- CVE-2024-46802: drm/amd/display: added NULL check at start of dc_validate_stream (bsc#1231111).\n- CVE-2024-46809: drm/amd/display: Check BIOS images before it is used (bsc#1231148).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46826: ELF: fix kernel.randomize_va_space double read (bsc#1231115).\n- CVE-2024-46834: ethtool: fail closed if we can't get max channel used in indirection tables (bsc#1231096).\n- CVE-2024-46840: btrfs: clean up our handling of refs == 0 in snapshot delete (bsc#1231105).\n- CVE-2024-46841: btrfs: do not BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (bsc#1231094).\n- CVE-2024-46848: perf/x86/intel: Limit the period on Haswell (bsc#1231072).\n- CVE-2024-47672: wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (bsc#1231540).\n- CVE-2024-47673: wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (bsc#1231539).\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-47685: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() (bsc#1231998).\n- CVE-2024-47697: drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (bsc#1231858).\n- CVE-2024-47698: drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (bsc#1231859).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47707: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (bsc#1231935).\n- CVE-2024-47713: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (bsc#1232016).\n- CVE-2024-47735: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (bsc#1232111).\n- CVE-2024-47737: nfsd: call cache_put if xdr_reserve_space returns NULL (bsc#1232056).\n- CVE-2024-47742: firmware_loader: Block path traversal (bsc#1232126).\n- CVE-2024-47745: mm: split critical region in remap_file_pages() and invoke LSMs in between (bsc#1232135).\n- CVE-2024-49851: tpm: Clean up TPM space after command failure (bsc#1232134).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49881: ext4: update orig_path in ext4_find_extent() (bsc#1232201).\n- CVE-2024-49882: ext4: fix double brelse() the buffer of the extents path (bsc#1232200).\n- CVE-2024-49883: ext4: aovid use-after-free in ext4_ext_insert_extent() (bsc#1232199).\n- CVE-2024-49890: drm/amd/pm: ensure the fw_info is not null before using it (bsc#1232217).\n- CVE-2024-49891: scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1232218).\n- CVE-2024-49894: drm/amd/display: Fix index out of bounds in degamma hardware format translation (bsc#1232354).\n- CVE-2024-49896: drm/amd/display: Check stream before comparing them (bsc#1232221).\n- CVE-2024-49901: drm/msm/adreno: Assign msm_gpu-\u003epdev earlier to avoid nullptrs (bsc#1232305).\n- CVE-2024-49920: drm/amd/display: Check null pointers before multiple uses (bsc#1232313).\n- CVE-2024-49929: wifi: iwlwifi: mvm: avoid NULL pointer dereference (bsc#1232253).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49949: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (bsc#1232160).\n- CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree (bsc#1232151).\n- CVE-2024-49959: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error (bsc#1232149).\n- CVE-2024-49962: ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (bsc#1232314).\n- CVE-2024-49966: ocfs2: cancel dqi_sync_work before freeing oinfo (bsc#1232141).\n- CVE-2024-49967: ext4: no need to continue when the number of entries is 1 (bsc#1232140).\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-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate() (bsc#1232442).\n- CVE-2024-50007: ALSA: asihpi: Fix potential OOB array access (bsc#1232394).\n- CVE-2024-50024: net: Fix an unsafe loop on the list (bsc#1231954).\n- CVE-2024-50033: slip: make slhc_remember() more robust against malicious packets (bsc#1231914).\n- CVE-2024-50035: ppp: fix ppp_async_encode() illegal access (bsc#1232392).\n- CVE-2024-50045: netfilter: br_netfilter: fix panic with metadata_dst skb (bsc#1231903).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n- CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too (bsc#1232285).\n\nThe following non-security bugs were fixed:\n\n- arm64: esr: Define ESR_ELx_EC_* constants as UL (git-fixes)\n- arm64: probes: Fix simulate_ldr*_literal() (git-fixes)\n- arm64: probes: Fix uprobes for big-endian kernels (git-fixes)\n- arm64: probes: Remove broken LDR (literal) uprobe support (git-fixes)\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- drbd: Add NULL check for net_conf to prevent dereference in state validation (git-fixes).\n- drbd: Fix atomicity violation in drbd_uuid_set_bm() (git-fixes).\n- ext4: fix slab-use-after-free in ext4_split_extent_at() (bsc#1232201)\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- net: usb: usbnet: fix name regression (get-fixes).\n- nfs: fix memory leak in error path of nfs4_do_reclaim (git-fixes).\n- nfsd: fix delegation_blocked() to block correctly for at least 30 seconds (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1230405).\n","status":"published","published":"2024-11-28T12:42:12Z","modified":"2026-02-04T02:21:54.049545Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2025:0034-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\nThe Linux Enterprise 12 SP5 kernel turned LTSS (Extended Security)\n\nThe following security bugs were fixed:\n\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47163: kABI fix for tipc: wait and exit until all work queues are done (bsc#1221980).\n- CVE-2021-47612: nfc: fix segfault in nfc_genl_dump_devices_done (bsc#1226585).\n- CVE-2022-48809: net: fix a memleak when uncloning an skb dst and its metadata (bsc#1227947).\n- CVE-2022-48951: ASoC: ops: Correct bounds check for second channel on SX controls (bsc#1231929).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48958: ethernet: aeroflex: fix potential skb leak in greth_init_rings() (bsc#1231889).\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-48966: net: mvneta: Fix an out of bounds check (bsc#1232191).\n- CVE-2022-48967: NFC: nci: Bounds check struct nfc_target arrays (bsc#1232304).\n- CVE-2022-48971: Bluetooth: Fix not cleanup led when bt_init fails (bsc#1232037).\n- CVE-2022-48972: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (bsc#1232025).\n- CVE-2022-48973: gpio: amd8111: Fix PCI device reference count leak (bsc#1232039).\n- CVE-2022-48978: HID: core: fix shift-out-of-bounds in hid_report_raw_event (bsc#1232038).\n- CVE-2022-48991: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (bsc#1232070).\n- CVE-2022-48992: ASoC: soc-pcm: Add NULL check in BE reparenting (bsc#1232071).\n- CVE-2022-49000: iommu/vt-d: Fix PCI device refcount leak in has_external_pci() (bsc#1232123).\n- CVE-2022-49002: iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() (bsc#1232133).\n- CVE-2022-49010: hwmon: (coretemp) Check for null before removing sysfs attrs (bsc#1232172).\n- CVE-2022-49011: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() (bsc#1232006).\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-49020: net/9p: Fix a potential socket leak in p9_socket_open (bsc#1232175).\n- CVE-2022-49021: net: phy: fix null-ptr-deref while probe() failed (bsc#1231939).\n- CVE-2022-49026: e100: Fix possible use after free in e100_xmit_prepare (bsc#1231997).\n- CVE-2022-49027: iavf: Fix error handling in iavf_init_module() (bsc#1232007).\n- CVE-2022-49028: ixgbevf: Fix resource leak in ixgbevf_init_module() (bsc#1231996).\n- CVE-2022-49029: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails (bsc#1231995).\n- CVE-2023-52898: xhci: Fix null pointer dereference when host dies (bsc#1229568).\n- CVE-2023-52918: media: pci: cx23885: check cx23885_vdev_init() return (bsc#1232047).\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-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (bsc#1227437).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command  (bsc#1228620).\n- CVE-2024-42114: netlink: extend policy range validation (bsc#1228564 prerequisite).\n- CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race (bsc#1229005 stable-fixes).\n- CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc() (bsc#1229837 stable-fixes).\n- CVE-2024-44958: sched/smt: Fix unbalance sched_smt_present dec/inc (bsc#1230179).\n- CVE-2024-46724: drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (bsc#1230725).\n- CVE-2024-46755: wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (bsc#1230802).\n- CVE-2024-46802: drm/amd/display: added NULL check at start of dc_validate_stream (bsc#1231111).\n- CVE-2024-46809: drm/amd/display: Check BIOS images before it is used (bsc#1231148).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46826: ELF: fix kernel.randomize_va_space double read (bsc#1231115).\n- CVE-2024-46834: ethtool: fail closed if we can't get max channel used in indirection tables (bsc#1231096).\n- CVE-2024-46840: btrfs: clean up our handling of refs == 0 in snapshot delete (bsc#1231105).\n- CVE-2024-46841: btrfs: do not BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (bsc#1231094).\n- CVE-2024-46848: perf/x86/intel: Limit the period on Haswell (bsc#1231072).\n- CVE-2024-47672: wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (bsc#1231540).\n- CVE-2024-47673: wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (bsc#1231539).\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-47685: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() (bsc#1231998).\n- CVE-2024-47697: drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (bsc#1231858).\n- CVE-2024-47698: drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (bsc#1231859).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47707: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (bsc#1231935).\n- CVE-2024-47713: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (bsc#1232016).\n- CVE-2024-47735: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (bsc#1232111).\n- CVE-2024-47737: nfsd: call cache_put if xdr_reserve_space returns NULL (bsc#1232056).\n- CVE-2024-47742: firmware_loader: Block path traversal (bsc#1232126).\n- CVE-2024-47745: mm: split critical region in remap_file_pages() and invoke LSMs in between (bsc#1232135).\n- CVE-2024-49851: tpm: Clean up TPM space after command failure (bsc#1232134).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49881: ext4: update orig_path in ext4_find_extent() (bsc#1232201).\n- CVE-2024-49882: ext4: fix double brelse() the buffer of the extents path (bsc#1232200).\n- CVE-2024-49883: ext4: aovid use-after-free in ext4_ext_insert_extent() (bsc#1232199).\n- CVE-2024-49890: drm/amd/pm: ensure the fw_info is not null before using it (bsc#1232217).\n- CVE-2024-49891: scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1232218).\n- CVE-2024-49894: drm/amd/display: Fix index out of bounds in degamma hardware format translation (bsc#1232354).\n- CVE-2024-49896: drm/amd/display: Check stream before comparing them (bsc#1232221).\n- CVE-2024-49901: drm/msm/adreno: Assign msm_gpu-\u003epdev earlier to avoid nullptrs (bsc#1232305).\n- CVE-2024-49920: drm/amd/display: Check null pointers before multiple uses (bsc#1232313).\n- CVE-2024-49929: wifi: iwlwifi: mvm: avoid NULL pointer dereference (bsc#1232253).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49949: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (bsc#1232160).\n- CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree (bsc#1232151).\n- CVE-2024-49959: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error (bsc#1232149).\n- CVE-2024-49962: ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (bsc#1232314).\n- CVE-2024-49966: ocfs2: cancel dqi_sync_work before freeing oinfo (bsc#1232141).\n- CVE-2024-49967: ext4: no need to continue when the number of entries is 1 (bsc#1232140).\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-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate() (bsc#1232442).\n- CVE-2024-50007: ALSA: asihpi: Fix potential OOB array access (bsc#1232394).\n- CVE-2024-50024: net: Fix an unsafe loop on the list (bsc#1231954).\n- CVE-2024-50033: slip: make slhc_remember() more robust against malicious packets (bsc#1231914).\n- CVE-2024-50035: ppp: fix ppp_async_encode() illegal access (bsc#1232392).\n- CVE-2024-50045: netfilter: br_netfilter: fix panic with metadata_dst skb (bsc#1231903).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n- CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too (bsc#1232285).\n\nThe following non-security bugs were fixed:\n\n- arm64: esr: Define ESR_ELx_EC_* constants as UL (git-fixes)\n- arm64: probes: Fix simulate_ldr*_literal() (git-fixes)\n- arm64: probes: Fix uprobes for big-endian kernels (git-fixes)\n- arm64: probes: Remove broken LDR (literal) uprobe support (git-fixes)\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- drbd: Add NULL check for net_conf to prevent dereference in state validation (git-fixes).\n- drbd: Fix atomicity violation in drbd_uuid_set_bm() (git-fixes).\n- ext4: fix slab-use-after-free in ext4_split_extent_at() (bsc#1232201)\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- net: usb: usbnet: fix name regression (get-fixes).\n- nfs: fix memory leak in error path of nfs4_do_reclaim (git-fixes).\n- nfsd: fix delegation_blocked() to block correctly for at least 30 seconds (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1230405).\n","status":"published","published":"2025-01-08T09:47:28Z","modified":"2026-02-04T04:37:46.913821Z","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-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-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-7159-1","title":"linux, linux-gcp, linux-gcp-5.4, linux-hwe-5.4, linux-ibm, linux-ibm-5.4, linux-kvm, linux-raspi, linux-xilinx-zynqmp vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Power management core;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - S/390 drivers;\n  - TTY drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - BPF subsystem;\n  - Socket messages infrastructure;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - SELinux security module;\n(CVE-2022-48938, CVE-2024-42156, CVE-2024-36953, CVE-2024-38538,\nCVE-2021-47501, CVE-2024-42068, CVE-2024-26947, CVE-2024-46724,\nCVE-2024-36968, CVE-2023-52497, CVE-2024-35951, CVE-2023-52488,\nCVE-2024-44940, CVE-2022-48733, CVE-2023-52498, CVE-2022-48943,\nCVE-2024-35904, CVE-2024-42077, CVE-2024-36938, CVE-2023-52639,\nCVE-2024-42240, CVE-2024-44942, CVE-2021-47076)\n","status":"published","published":"2024-12-12T20:26:07Z","modified":"2026-10-29T20:02:37.004183547Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7159-2","title":"linux-aws, linux-aws-5.4 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Power management core;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - S/390 drivers;\n  - TTY drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - BPF subsystem;\n  - Socket messages infrastructure;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - SELinux security module;\n(CVE-2022-48938, CVE-2024-42156, CVE-2024-36953, CVE-2024-38538,\nCVE-2021-47501, CVE-2024-42068, CVE-2024-26947, CVE-2024-46724,\nCVE-2024-36968, CVE-2023-52497, CVE-2024-35951, CVE-2023-52488,\nCVE-2024-44940, CVE-2022-48733, CVE-2023-52498, CVE-2022-48943,\nCVE-2024-35904, CVE-2024-42077, CVE-2024-36938, CVE-2023-52639,\nCVE-2024-42240, CVE-2024-44942, CVE-2021-47076)\n","status":"published","published":"2024-12-17T13:52:15Z","modified":"2026-10-29T20:02:32.516900676Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7159-3","title":"linux-bluefield, linux-oracle, linux-oracle-5.4 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Power management core;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - S/390 drivers;\n  - TTY drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - BPF subsystem;\n  - Socket messages infrastructure;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - SELinux security module;\n(CVE-2022-48938, CVE-2024-42156, CVE-2024-36953, CVE-2024-38538,\nCVE-2021-47501, CVE-2024-42068, CVE-2024-26947, CVE-2024-46724,\nCVE-2024-36968, CVE-2023-52497, CVE-2024-35951, CVE-2023-52488,\nCVE-2024-44940, CVE-2022-48733, CVE-2023-52498, CVE-2022-48943,\nCVE-2024-35904, CVE-2024-42077, CVE-2024-36938, CVE-2023-52639,\nCVE-2024-42240, CVE-2024-44942, CVE-2021-47076)\n","status":"published","published":"2024-12-17T23:40:32Z","modified":"2026-10-29T20:03:07.700116227Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7159-4","title":"linux-iot vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Power management core;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - S/390 drivers;\n  - TTY drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - BPF subsystem;\n  - Socket messages infrastructure;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - SELinux security module;\n(CVE-2022-48938, CVE-2024-42156, CVE-2024-36953, CVE-2024-38538,\nCVE-2021-47501, CVE-2024-42068, CVE-2024-26947, CVE-2024-46724,\nCVE-2024-36968, CVE-2023-52497, CVE-2024-35951, CVE-2023-52488,\nCVE-2024-44940, CVE-2022-48733, CVE-2023-52498, CVE-2022-48943,\nCVE-2024-35904, CVE-2024-42077, CVE-2024-36938, CVE-2023-52639,\nCVE-2024-42240, CVE-2024-44942, CVE-2021-47076)\n","status":"published","published":"2024-12-20T12:33:31Z","modified":"2026-10-29T20:02:32.315577428Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7159-5","title":"linux-raspi-5.4 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Power management core;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - S/390 drivers;\n  - TTY drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - BPF subsystem;\n  - Socket messages infrastructure;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - SELinux security module;\n(CVE-2022-48938, CVE-2024-42156, CVE-2024-36953, CVE-2024-38538,\nCVE-2021-47501, CVE-2024-42068, CVE-2024-26947, CVE-2024-46724,\nCVE-2024-36968, CVE-2023-52497, CVE-2024-35951, CVE-2023-52488,\nCVE-2024-44940, CVE-2022-48733, CVE-2023-52498, CVE-2022-48943,\nCVE-2024-35904, CVE-2024-42077, CVE-2024-36938, CVE-2023-52639,\nCVE-2024-42240, CVE-2024-44942, CVE-2021-47076)\n","status":"published","published":"2025-01-06T14:44:20Z","modified":"2026-10-29T20:02:32.038929828Z","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-7195-1","title":"linux-azure vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\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  - S390 architecture;\n  - x86 architecture;\n  - Power management core;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - TTY drivers;\n  - BTRFS file system;\n  - Ext4 file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - BPF subsystem;\n  - Socket messages infrastructure;\n  - Bluetooth subsystem;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - VMware vSockets driver;\n  - SELinux security module;\n(CVE-2024-42240, CVE-2024-36938, CVE-2024-35967, CVE-2024-36953,\nCVE-2022-48938, CVE-2024-38553, CVE-2024-35904, CVE-2024-35965,\nCVE-2024-26947, CVE-2024-36968, CVE-2024-43892, CVE-2024-38597,\nCVE-2023-52498, CVE-2021-47501, CVE-2024-44942, CVE-2024-42077,\nCVE-2024-53057, CVE-2024-46724, CVE-2024-35963, CVE-2022-48943,\nCVE-2024-42068, CVE-2024-42156, CVE-2022-48733, CVE-2023-52639,\nCVE-2021-47101, CVE-2023-52821, CVE-2024-44940, CVE-2024-36952,\nCVE-2021-47001, CVE-2024-38538, CVE-2024-40910, CVE-2021-47076,\nCVE-2024-35966, CVE-2024-50264, CVE-2024-35951, CVE-2023-52488,\nCVE-2023-52497, CVE-2024-49967)\n","status":"published","published":"2025-01-09T12:19:02Z","modified":"2026-10-29T20:02:32.673664608Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7195-2","title":"linux-azure-5.4 vulnerabilities","description":"Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\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  - S390 architecture;\n  - x86 architecture;\n  - Power management core;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - TTY drivers;\n  - BTRFS file system;\n  - Ext4 file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - BPF subsystem;\n  - Socket messages infrastructure;\n  - Bluetooth subsystem;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - VMware vSockets driver;\n  - SELinux security module;\n(CVE-2024-42240, CVE-2024-36938, CVE-2024-35967, CVE-2024-36953,\nCVE-2022-48938, CVE-2024-38553, CVE-2024-35904, CVE-2024-35965,\nCVE-2024-26947, CVE-2024-36968, CVE-2024-43892, CVE-2024-38597,\nCVE-2023-52498, CVE-2021-47501, CVE-2024-44942, CVE-2024-42077,\nCVE-2024-53057, CVE-2024-46724, CVE-2024-35963, CVE-2022-48943,\nCVE-2024-42068, CVE-2024-42156, CVE-2022-48733, CVE-2023-52639,\nCVE-2021-47101, CVE-2023-52821, CVE-2024-44940, CVE-2024-36952,\nCVE-2021-47001, CVE-2024-38538, CVE-2024-40910, CVE-2021-47076,\nCVE-2024-35966, CVE-2024-50264, CVE-2024-35951, CVE-2023-52488,\nCVE-2023-52497, CVE-2024-49967)\n","status":"published","published":"2025-01-14T17:27:31Z","modified":"2026-10-29T20:03:08.862470349Z","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"}]}}