{"id":"CVE-2024-40945","aliases":["BELL-CVE-2024-40945","CLSA-2024-1727817133","CLSA-2024-1727817159","CLSA-2024-1727817758","DEBIAN-CVE-2024-40945","DLA-4102-1","DSA-5730-1","EUVD-2024-38833","GHSA-fh5c-w77m-vmmm","OESA-2024-1941","OESA-2024-1942","OESA-2024-2028","OESA-2024-2076","RHSA-2024:9315","SUSE-SU-2024:2894-1","SUSE-SU-2024:2939-1","SUSE-SU-2024:2947-1","SUSE-SU-2024:3194-1","SUSE-SU-2024:3195-1","SUSE-SU-2024:3383-1","SUSE-SU-2025:20044-1","SUSE-SU-2025:20047-1","UBUNTU-CVE-2024-40945","USN-6999-1","USN-6999-2","USN-7003-1","USN-7003-2","USN-7003-3","USN-7003-4","USN-7003-5","USN-7004-1","USN-7005-1","USN-7005-2","USN-7006-1","USN-7007-1","USN-7007-2","USN-7007-3","USN-7008-1","USN-7009-1","USN-7009-2","USN-7019-1","USN-7029-1"],"status":"published","title":"iommu: Return right value in iommu_sva_bind_device()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00257,"percentile":0.17467,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-476"],"published":"2024-07-12T12:25:19Z","modified":"2026-11-02T12:02:57Z","fixes":[{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.130-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.4.279","5.10.221","5.15.162","6.1.129","6.6.35","6.9.6"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.129-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.9.7-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.9.7-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","fixed_in":["5.4.0-1132.142~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","fixed_in":["5.4.0-1137.144~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","fixed_in":["5.4.0-1136.145~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","fixed_in":["5.4.0-195.215~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","fixed_in":["5.4.0-1079.84~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","fixed_in":["5.4.0-1131.140~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","fixed_in":["5.4.0-1116.128~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux","fixed_in":["5.4.0-195.215"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","fixed_in":["5.4.0-1132.142"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1069.75~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","fixed_in":["5.4.0-1137.144"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1072.81~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","fixed_in":["5.4.0-1092.99"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","fixed_in":["5.4.0-1136.145"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1068.76~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","fixed_in":["5.4.0-1099.103"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","fixed_in":["5.15.0-1052.59~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-121.131~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","fixed_in":["5.4.0-1079.84"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1062.65~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1064.70~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","fixed_in":["5.4.0-1043.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","fixed_in":["5.4.0-1120.128"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-121.131~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1030.30~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","fixed_in":["5.4.0-1131.140"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1067.73~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","fixed_in":["5.4.0-1116.128"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1065.69~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.4.0-1051.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","fixed_in":["5.4.0-1132.142+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","fixed_in":["5.4.0-1137.144+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","fixed_in":["5.4.0-1106.116"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","fixed_in":["5.4.0-1136.145+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-121.131"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1069.75"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1015.16~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1072.81"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1014.16~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","fixed_in":["5.15.0-1072.81.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1068.76"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1014.16~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1066.72"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1052.59"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-45.45~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1062.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1012.12~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1064.70"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1066.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-121.131"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-44.44.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1064.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1013.14~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1028.28"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1016.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1067.73"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1012.12~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1062.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-44.44.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1035.39"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1052.54"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1063.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1070.78"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1008.8~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1069.75+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1072.81+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-121.131+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1068.76+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-44.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1015.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1014.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1014.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1010.13"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1012.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-44.44.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1013.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1013.14.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1012.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1012.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1011.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","fixed_in":["6.8.0-44.44.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2010.10"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-78.78+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.127-r0"},{"fixed":"6.1.130-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.100-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els25","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-237-tuxcare.els25","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-extra-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-237-tuxcare.els25","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.15.0-237-tuxcare.els35-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.15.0-237-tuxcare.els35-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els35-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els35-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-237-tuxcare.els35","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-237-tuxcare.els35-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-237-tuxcare.els35-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-hwe-cloud-tools-4.15.0-237-tuxcare.els35","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-hwe-tools-4.15.0-237-tuxcare.els35","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.15.0-237-tuxcare.els35-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.15.0-237-tuxcare.els35-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.15.0-237-tuxcare.els35-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.15.0-237-tuxcare.els35-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-extra-4.15.0-237-tuxcare.els35-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.15.0-237-tuxcare.els35-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.15.0-237-tuxcare.els35-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248~16.04.1"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els25","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-crashdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-237-tuxcare.els25","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-extra-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-237-tuxcare.els25","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-237-tuxcare.els25-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-237-tuxcare.els25-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0.237.248"}]}],"bundled":74},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.2.0"},{"fixed":"5.4.279"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.221"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.162"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.129"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.35"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.9.6"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.129-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","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.9.7-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.7-1"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.129-1~deb11u1"}]}],"versions":["6.1.106-3~deb11u1","6.1.106-3~deb11u2","6.1.106-3~deb11u3","6.1.112-1~deb11u1","6.1.119-1~deb11u1","6.1.128-1~deb11u1"],"bundled":121},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.221-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.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":124},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.87.0.168.oe2203sp1"}]}],"bundled":36},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-221.0.0.124.oe2203sp3"}]}],"bundled":42},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-224.0.0.123.oe2203sp4"}]}],"bundled":19},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-39.0.0.47.oe2403"}]}],"bundled":134},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"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-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.64.1"}]}],"bundled":310},{"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.64.1"}]}],"bundled":310},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5-RT_Update_18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":310},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.64.1"}]}],"bundled":310},{"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.64.1"}]}],"bundled":310},{"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.64.1"}]}],"bundled":310},{"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.64.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.64.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.64.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.64.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.64.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.64.1"}]}],"bundled":310},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"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.73.1.150500.6.33.8"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1.150500.6.33.8"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.2"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"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.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1.150500.6.33.8"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1.150500.6.33.8"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.2"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.73.1"}]}],"bundled":531},{"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.63.1"}]}],"bundled":310},{"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.63.1"}]}],"bundled":310},{"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.63.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.63.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.63.1"}]}],"bundled":310},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.63.1"}]}],"bundled":310},{"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.11.1"}]}],"bundled":394},{"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.11.1"}]}],"bundled":394},{"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.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.3.2"}]}],"bundled":393},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"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.8.3"}]}],"bundled":393},{"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.8.3"}]}],"bundled":393},{"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.8.1"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.1"}]}],"bundled":393},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1.150600.12.8.3"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.3"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1.150600.12.8.3"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-19.1"}]}],"bundled":383},{"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":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-19.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-19.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0-RT_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-10.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-10.1"}]}],"bundled":383},{"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-1132.142~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"]},{"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-1137.144~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"]},{"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-1136.145~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"]},{"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-195.215~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"]},{"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-1079.84~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"]},{"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-1131.140~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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1116.128~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-195.215"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1132.142"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1137.144"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1092.99"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1136.145"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1099.103"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1079.84"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1043.44"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1120.128"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1030.30~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1131.140"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1116.128"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.69~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1051.55"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1132.142+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1137.144+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1106.116"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1136.145+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"]},{"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-121.131"}]}],"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"]},{"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-1069.75"}]}],"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"]},{"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-1015.16~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81"}]}],"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"]},{"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-1014.16~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81.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"]},{"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-1068.76"}]}],"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"]},{"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-1014.16~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.72"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59"}]}],"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"]},{"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-45.45~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.12~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.71"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131"}]}],"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"]},{"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-44.44.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.65"}]}],"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"]},{"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-1013.14~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1028.28"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1016.16"}]}],"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"]},{"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-1067.73"}]}],"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"]},{"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-1012.12~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"]},{"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-44.44.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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1035.39"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.54"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.65"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1070.78"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1008.8~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"]},{"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-1069.75+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76+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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-44.44"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.16"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.13"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.12"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-44.44.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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.12"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.12"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.12"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-44.44.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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2010.10"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1008.8"}]}],"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"]},{"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:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-44.44"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.16"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.13"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.12"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-44.44.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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.12"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.12"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1011.12"}]}],"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"],"bundled":220},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-195.215"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1132.142"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1137.144"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1092.99"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1136.145"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1099.103"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1079.84"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1120.128"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1131.140"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1132.142~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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1137.144~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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1136.145~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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-195.215~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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1079.84~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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1131.140~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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1051.55"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1116.128"}]}],"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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1116.128~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"],"bundled":85},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"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"],"bundled":221},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.14~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1043.44"}]}],"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"],"bundled":94},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.72"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.71"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.65"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-44.44.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1"],"bundled":222},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81~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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81.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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81~20.04.1.1"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1","5.15.0-1063.72~20.04.1.1","5.15.0-1064.73~20.04.1.1","5.15.0-1065.74~20.04.1.1","5.15.0-1067.76~20.04.1.1","5.15.0-1068.77~20.04.1.1","5.15.0-1070.79~20.04.1.1","5.15.0-1071.80~20.04.1.1"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1035.39"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35"],"bundled":429},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-45.45~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"],"bundled":227}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"},{"vendor":"siemens","product":"ruggedcom rst2428p"},{"vendor":"siemens","product":"scalance xc-300/xr-300/xc-400/xr-500wg/xr-500 family"},{"vendor":"siemens","product":"scalance xcm-/xrm-/xch-/xrh-300 family"},{"vendor":"siemens","product":"simatic s7-1500 tm mfp - gnu/linux subsystem"}],"references":[{"url":"https://git.kernel.org/stable/c/700f564758882db7c039dfba9443fe762561a3f8","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/cf34f8f66982a36e5cba0d05781b21ec9606b91e","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/2973b8e7d127754de9013177c41c0b5547406998","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/6325eab6c108fed27f60ff51852e3eac0ba23f3f","tags":["web"]},{"url":"https://git.kernel.org/stable/c/7388ae6f26c0ba95f70cc96bf9c5d5cb06c908b6","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/61a96da9649a6b6a1a5d5bde9374b045fdb5c12e","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/89e8a2366e3bce584b6c01549d5019c5cda1205e","tags":["x_transferred","Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-265688.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-613116.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-355557.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-784472.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40945","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-fh5c-w77m-vmmm"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-40945","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu18.04els/CLSA-2024-1727817133.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52629","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38538","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38630","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39506","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39509","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42104","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42271","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-42313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43882","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-44942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43414","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu16.04els/CLSA-2024-1727817159.html","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/ubuntu18-els/CLSA-2024-1727817758.html","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/40xxx/CVE-2024-40945.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-40945","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/security-bulletins/detail?id=openEuler-SA-2024-1941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47205","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-34777","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35899","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38567","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38607","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39484","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39508","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41011","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/security-bulletins/detail?id=openEuler-SA-2024-1942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40963","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40982","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-33621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42127","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42310","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43839","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-33847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36281","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36484","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38390","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38539","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38543","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38550","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38557","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38561","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38593","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38613","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39490","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39504","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40910","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41092","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42132","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42140","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42144","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42230","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42267","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42274","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43868","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44941","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2024:9315","tags":["advisory"]},{"url":"https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.5_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=1832397","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2257406","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2260038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2262241","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2263879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265654","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265657","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265793","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265798","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265800","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265831","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265833","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265836","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266210","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266212","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266247","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266249","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266296","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267028","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267701","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267705","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267724","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267730","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267782","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267789","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267797","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267804","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267920","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268293","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268315","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268335","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269063","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269183","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269192","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269201","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269203","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269211","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270071","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270084","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270093","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270097","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270133","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271682","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271684","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271688","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271690","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271788","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272692","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272782","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272784","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272786","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272788","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272791","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272800","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272804","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272806","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272808","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272814","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272818","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272829","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272836","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272839","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272842","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273085","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273098","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273109","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273130","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273143","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273158","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273166","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273168","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273185","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273200","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273204","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273206","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273208","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273234","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273242","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273247","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273260","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273262","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273425","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273461","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273657","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274478","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274624","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275558","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275565","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275578","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275580","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275584","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275624","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275633","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275635","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275641","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275647","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275661","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275666","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275672","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275686","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275694","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275707","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275711","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275725","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275727","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275729","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275737","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275775","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275790","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275928","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2276665","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277168","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277844","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277937","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278169","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278178","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278182","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278193","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278197","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278200","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278218","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278229","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278231","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278237","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278262","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278266","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278275","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278277","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278279","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278293","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278320","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278322","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278327","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278333","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278350","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278352","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278387","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278406","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278431","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278447","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278456","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278484","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278492","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278522","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278524","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278532","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278537","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278939","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278960","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2280440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2280444","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281045","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281061","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281069","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281125","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281145","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281155","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281157","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281165","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281183","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281189","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281192","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281202","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281207","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281211","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281215","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281217","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281219","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281221","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281225","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281243","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281251","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281253","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281255","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281276","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281282","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281286","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281288","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281290","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281303","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281305","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281311","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281326","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281332","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281336","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281360","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281362","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281510","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281517","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281523","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281526","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281636","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281651","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281655","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281664","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281679","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281684","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281693","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281697","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281718","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281725","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281736","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281742","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281752","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281754","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281758","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281760","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281762","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281763","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281769","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281773","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281781","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281783","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281786","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281807","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281811","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281819","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281833","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281843","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281863","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281872","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281884","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281891","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281923","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281927","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281933","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281938","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281942","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281989","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282088","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282302","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282354","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282366","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282622","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282623","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282637","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282640","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282641","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282646","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282652","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282653","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282655","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282676","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282679","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282680","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282690","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282740","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282741","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282742","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282743","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282745","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282746","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282748","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282757","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282762","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282763","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282772","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282787","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282901","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282904","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282918","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282920","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282950","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283448","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283786","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284265","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284269","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284277","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284295","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284413","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284427","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284465","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284477","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284494","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284500","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284502","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284545","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284556","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284567","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284583","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284586","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2290407","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2290408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2292329","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293000","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293003","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293329","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293359","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293361","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293365","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293367","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293371","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293444","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293639","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293656","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293684","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293693","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293696","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293698","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293700","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294223","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294274","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296059","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296064","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296066","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296278","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296383","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297057","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297061","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297469","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297470","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297473","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297475","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297480","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297491","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297497","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297507","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297508","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297509","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297514","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297524","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297529","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297532","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297549","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297550","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297551","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297585","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297702","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297706","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298079","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299452","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300398","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300407","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300412","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300422","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300431","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300432","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300434","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300438","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300454","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300456","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300480","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300481","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300508","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300516","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300533","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301464","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301477","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301497","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301522","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301530","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303077","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2304187","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305446","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307861","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307865","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307884","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309791","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309796","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309801","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309868","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-17714","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-23575","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-26081","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-29437","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-31876","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-32199","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-35853","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-36182","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-36224","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-45158","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-7990","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9096","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9148","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9429","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_9315.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-25162","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-25162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-25162","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022602-CVE-2019-25162-70ae@gregkh/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2020-10135","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-10135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-10135","tags":["advisory"]},{"url":"https://francozappa.github.io/about-bias/","tags":["article"]},{"url":"https://kb.cert.org/vuls/id/647177/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47098","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47098","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47098-e11f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47101-f3fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47185","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47185","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041033-CVE-2021-47185-c363@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47384","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47384","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47384-f311@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47386","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47386","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052145-CVE-2021-47386-2701@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47428","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47428","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052157-CVE-2021-47428-f3c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47429","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47429","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47429","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052157-CVE-2021-47429-e386@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47432","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47432","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052143-CVE-2021-47432-5e69@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47454","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47454","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052243-CVE-2021-47454-e852@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47457","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47457","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47457","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052244-CVE-2021-47457-d807@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47495","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47495","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052242-CVE-2021-47495-a5f8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47497","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47497","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052242-CVE-2021-47497-449e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47505","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052452-CVE-2021-47505-427f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48669","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2022-48669-15cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48672","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48672","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050318-CVE-2022-48672-b6d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48703","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48703","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050351-CVE-2022-48703-3099@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48804","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48804","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48804","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071645-CVE-2022-48804-f191@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48929","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307185","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082222-CVE-2022-48929-857d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49078","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348091","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49078","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022656-CVE-2022-49078-df00@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49124","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347834","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022604-CVE-2022-49124-b593@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49197","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49197","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022617-CVE-2022-49197-494d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49226","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022622-CVE-2022-49226-b30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49267","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347734","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49267","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49267","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022629-CVE-2022-49267-b3ac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49308","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348348","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49308","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49308","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022635-CVE-2022-49308-23f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49329","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348087","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49329","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022639-CVE-2022-49329-ed73@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347819","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49430","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022655-CVE-2022-49430-3b17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49549","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348127","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49549","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49549","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022615-CVE-2022-49549-db30@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49675","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348124","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49675","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022624-CVE-2022-49675-17aa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49787","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363396","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49787","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050121-CVE-2022-49787-7fb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49860","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363384","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49860","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050147-CVE-2022-49860-75f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49941","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373403","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49941","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061849-CVE-2022-49941-b536@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50019","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061834-CVE-2022-50019-181a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50073","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373494","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50073","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061854-CVE-2022-50073-7199@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50096","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373541","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061802-CVE-2022-50096-0220@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061818-CVE-2022-50141-fd0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50177","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373568","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50177","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50177","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061831-CVE-2022-50177-1d63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50251","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395251","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50251","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091549-CVE-2022-50251-c216@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395281","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50268","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091504-CVE-2022-50268-bcdf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50284","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395425","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50284","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091507-CVE-2022-50284-b5c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50312","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395391","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50312","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091500-CVE-2022-50312-105d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50347","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50347","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50347","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091640-CVE-2022-50347-33c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50353","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396104","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50353","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50353","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091711-CVE-2022-50353-2f1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400820","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50468","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100122-CVE-2022-50468-3196@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401477","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50486","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50486","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100441-CVE-2022-50486-da3d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401512","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50495","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100419-CVE-2022-50495-fdee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50541","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402260","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50541","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100756-CVE-2022-50541-e1fe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50625","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50625","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120853-CVE-2022-50625-a1e2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50640","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420263","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50640","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120935-CVE-2022-50640-324c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50653","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420261","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50653","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50653","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120938-CVE-2022-50653-6da2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50663","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420360","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120943-CVE-2022-50663-5606@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420313","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50670","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120946-CVE-2022-50670-feb4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50720","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122417-CVE-2022-50720-0297@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50748","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425140","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50748","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122451-CVE-2022-50748-0136@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50761","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425106","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50761","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122455-CVE-2022-50761-0e67@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50769","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425084","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50769","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50769","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122457-CVE-2022-50769-f4db@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50846","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426137","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2022-50846-caa2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50858","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426081","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50858","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123047-CVE-2022-50858-f41c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50886","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50886","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2022-50886-a081@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52445","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52445","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52445","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022253-CVE-2023-52445-07a6@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52451","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52451","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022257-CVE-2023-52451-7bdb@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52455","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52455","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022331-CVE-2023-52455-a28f@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52462","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52462","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022335-CVE-2023-52462-b663@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52464","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52464","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52464","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2023-52464-b17c@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52466","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/3171e46d677a668eed3086da78671f1e4f5b8405","tags":["article"]},{"url":"https://git.kernel.org/stable/c/5b3e25efe16e06779a9a7c7610217c1b921ec179","tags":["article"]},{"url":"https://git.kernel.org/stable/c/bd26159dcaaa3e9a927070efd348e7ce7e5ee933","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52467","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52467","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52467","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/3ef1130deee98997275904d9bfc37af75e1e906c","tags":["article"]},{"url":"https://git.kernel.org/stable/c/41673c66b3d0c09915698fec5c13b24336f18dd1","tags":["article"]},{"url":"https://git.kernel.org/stable/c/527e8c5f3d00299822612c495d5adf1f8f43c001","tags":["article"]},{"url":"https://git.kernel.org/stable/c/7f2c410ac470959b88e03dadd94b7a0b71df7973","tags":["article"]},{"url":"https://git.kernel.org/stable/c/927626a2073887ee30ba00633260d4d203f8e875","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c3e3a2144bf50877551138ffce9f7aa6ddfe385b","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52473","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52473","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022547-CVE-2023-52473-c3cc@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52475","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52475","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022918-CVE-2023-52475-442e@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52477","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52477","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52477-6f20@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52482","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52482","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52482","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022922-CVE-2023-52482-9375@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52486","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52486","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-27-lee@kernel.org/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52492","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52492","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52492","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-33-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52498","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-39-lee@kernel.org/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030248-CVE-2023-52501-75ba@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52513","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52513","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52513","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52513-5224@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52520","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52520","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52520","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52520-0a4e@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52528","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52528","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52528","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52528-c33b@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52560","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52560","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52560-c3de@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52565","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52565","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52565-07ce@gregkh/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52585","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52585","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030643-CVE-2023-52585-7dbc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52594","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52594","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52594-9b84@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52595","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52595-d018@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52606","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52606","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52606","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52606-fdcc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-9-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52615","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52615","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-10-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52619","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-9-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52621","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52621","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-4-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52622","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52622","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-5-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52624","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52624","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52624","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-10-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52625","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52625","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-11-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52632","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52632","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040218-CVE-2023-52632-f7bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52634","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52634","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52634","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52634-27e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52635","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52635","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52635-8b18@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52637","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52637","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040332-CVE-2023-52637-5e37@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52643","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52643","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52643","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041701-CVE-2023-52643-8834@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52648","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52648","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52648","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050122-CVE-2023-52648-4e0d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52649","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52649","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050109-CVE-2023-52649-4614@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52650","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52650","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52650","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050109-CVE-2023-52650-e2d1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52656","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52656","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051338-CVE-2023-52656-6545@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52659","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52659","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051755-CVE-2023-52659-6f51@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52661","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52661","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52661","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2023-52661-5539@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52662","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2023-52662-1536@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2023-52663-1045@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52664","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52664","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2023-52664-dea1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52674","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051747-CVE-2023-52674-2aec@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52676","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52676","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051749-CVE-2023-52676-e224@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52679","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52679","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051750-CVE-2023-52679-948f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52680","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52680","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051750-CVE-2023-52680-1f4a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52683","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52683","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051751-CVE-2023-52683-f280@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52686","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051752-CVE-2023-52686-4a08@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52689","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52689","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051753-CVE-2023-52689-f657@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52690","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52690","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52690","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051753-CVE-2023-52690-f225@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52696","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52696","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051755-CVE-2023-52696-d4ab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52697","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52697","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051755-CVE-2023-52697-1b7f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52698","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52698","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2023-52698-bbc2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52703","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52703","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052157-CVE-2023-52703-abcb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52730","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52730","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52730-1c8f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52731","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52731","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052159-CVE-2023-52731-29ab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52740","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52740","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052101-CVE-2023-52740-3265@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52749","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52749","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2023-52749-684e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52751","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52751","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52751","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2023-52751-69df@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52756","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52756","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052146-CVE-2023-52756-f694@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52757","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52757","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052146-CVE-2023-52757-5028@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52758","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52758","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052146-CVE-2023-52758-9b23@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52762","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52762","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52762","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052147-CVE-2023-52762-fe90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52775","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52775","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52775","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052151-CVE-2023-52775-38a8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52784","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52784","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52784","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052154-CVE-2023-52784-80ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52788","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52788","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052155-CVE-2023-52788-9cb4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52791","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52791","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052156-CVE-2023-52791-f2b9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52811","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52811","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52811","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052102-CVE-2023-52811-2a5f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52813","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52813","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052103-CVE-2023-52813-0704@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52814","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52814","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052103-CVE-2023-52814-1cae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52817","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052104-CVE-2023-52817-ba29@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52819","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52819","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052105-CVE-2023-52819-98d5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52831","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52831","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052108-CVE-2023-52831-ce31@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52833","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52833","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52834","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52834","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052109-CVE-2023-52834-4c46@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52837","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52837","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052110-CVE-2023-52837-6490@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052111-CVE-2023-52840-8a3d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52859","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52859","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052117-CVE-2023-52859-ad0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52867","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52867","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052119-CVE-2023-52867-3f26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52869","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52869","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052120-CVE-2023-52869-6f57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052122-CVE-2023-52878-d433@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52902","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306430","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52902","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082113-CVE-2023-52902-d3fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52932","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355470","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52932","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032720-CVE-2023-52932-434b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52935","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355450","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52935","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032720-CVE-2023-52935-1c3c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53059","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363701","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53059","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050209-CVE-2023-53059-47f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53068","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363687","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53068","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050212-CVE-2023-53068-0127@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395244","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53173","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091555-CVE-2023-53173-4180@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53176","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395382","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53176","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091555-CVE-2023-53176-4194@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53178","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395358","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53178","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091555-CVE-2023-53178-9d27@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53182","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395248","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53182","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091556-CVE-2023-53182-dcdb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395338","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53220","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091512-CVE-2023-53220-e514@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53230","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395266","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53230","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53230","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091514-CVE-2023-53230-6c94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53249","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395320","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53249","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53249","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091502-CVE-2023-53249-aab7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53264","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395687","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53264","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091602-CVE-2023-53264-9c17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091626-CVE-2023-53291-9fe7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53391","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396423","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53391","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091858-CVE-2023-53391-cea3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53395","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396416","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53395","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53395-939e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53397","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396385","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53397","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53397","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53397-2076@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53401","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396417","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53401","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091800-CVE-2023-53401-b668@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53402","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396465","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53402","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091800-CVE-2023-53402-4b40@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53470","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400755","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53470","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100109-CVE-2023-53470-8c6a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53483","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400788","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53483","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100113-CVE-2023-53483-cf50@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400765","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53503","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100127-CVE-2023-53503-d86c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53505","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400785","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53505","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100128-CVE-2023-53505-69f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53531","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400691","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53531","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100136-CVE-2023-53531-3c7c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53558","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401543","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53558","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100449-CVE-2023-53558-e6f7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401503","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53572","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53572","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100453-CVE-2023-53572-ab85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53596","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53596","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100429-CVE-2023-53596-dbfb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53597","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53597","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100429-CVE-2023-53597-e30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53613","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401518","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53613","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53613","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100434-CVE-2023-53613-bba8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53662","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53662","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100703-CVE-2023-53662-475f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53674","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402263","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53674","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100706-CVE-2023-53674-af85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53687","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402288","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53687","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53687","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100710-CVE-2023-53687-c50c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53697","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405771","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53697","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102211-CVE-2023-53697-3078@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53702","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405762","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53702","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102211-CVE-2023-53702-a6b6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53704","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405725","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53704","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102212-CVE-2023-53704-9f42@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53708","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405783","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53708","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102212-CVE-2023-53708-0bf0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53719","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405740","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53719","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102214-CVE-2023-53719-ad4c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53731","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405719","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53731","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102216-CVE-2023-53731-aef7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419846","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53744","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120841-CVE-2023-53744-c66e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53747","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419903","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53747","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120842-CVE-2023-53747-ae4a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53752","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419915","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53752","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120843-CVE-2023-53752-339f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53768","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419848","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53768","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120846-CVE-2023-53768-2b71@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53858","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420332","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53858","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120904-CVE-2023-53858-87d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53861","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420351","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120905-CVE-2023-53861-22c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53997","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53997","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122426-CVE-2023-53997-8776@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54010","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122430-CVE-2023-54010-9ff1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54019","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424987","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122433-CVE-2023-54019-95e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54066","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54066","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122430-CVE-2023-54066-8ff7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54083","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425134","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54083","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122404-CVE-2023-54083-fc0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54093","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425122","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122407-CVE-2023-54093-fcea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54095","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425107","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54095","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122408-CVE-2023-54095-7fe0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425156","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54113","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122414-CVE-2023-54113-de5f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54114","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425196","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54114","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122414-CVE-2023-54114-8362@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54118","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425126","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54118","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122415-CVE-2023-54118-d92b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54136","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54136","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122421-CVE-2023-54136-b58d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54146","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425157","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54146","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122425-CVE-2023-54146-1510@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54153","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425153","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54153","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122427-CVE-2023-54153-63a8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54165","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426209","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54165","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54165","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123019-CVE-2023-54165-1362@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54172","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426166","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54172","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54172","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2023-54172-bcdc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54194","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426196","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54194","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123028-CVE-2023-54194-a396@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54198","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426177","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54198","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54198-1df4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54227","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426105","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54227","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54227","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54227-5c6c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54244","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426096","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54244","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123052-CVE-2023-54244-9a1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54246","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426152","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54246","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123052-CVE-2023-54246-8abc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54267","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426174","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54267","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54267","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123059-CVE-2023-54267-6736@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426091","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54268","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123000-CVE-2023-54268-3ba2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426240","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54271","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123001-CVE-2023-54271-d75a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426074","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54291-2983@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54298","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54298","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123031-CVE-2023-54298-d33d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54299","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426249","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54299","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123032-CVE-2023-54299-ec86@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54301","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426231","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54301","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123032-CVE-2023-54301-630e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54323","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426157","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54323","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123015-CVE-2023-54323-423a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-0340","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-0340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-0340","tags":["advisory"]},{"url":"https://lore.kernel.org/lkml/5kn47peabxjrptkqa6dwtyus35ahf4pcj4qm4pumse33kxqpjw@mec4se5relrc/T/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-1151","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-1151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-1151","tags":["advisory"]},{"url":"https://lore.kernel.org/all/20240207132416.1488485-1-aconole@redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-22099","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-22099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-22099","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=6ec00b0737fe","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-23307","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-23307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-23307","tags":["advisory"]},{"url":"https://bugzilla.openanolis.cn/show_bug.cgi?id=7975","tags":["article"]},{"url":"https://lore.kernel.org/linux-raid/20240112071017.16313-1-2045gemini@gmail.com/#r","tags":["article"]},{"url":"https://patchwork.kernel.org/project/linux-raid/patch/20240112071017.16313-1-2045gemini@gmail.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-23848","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-23848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-23848","tags":["advisory"]},{"url":"https://lore.kernel.org/lkml/e9f42704-2f99-4f2c-ade5-f952e5fd53e5%40xs4all.nl/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-24857","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-24857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24857","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-24858","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-24858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24858","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-24859","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-24859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24859","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-25739","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-25739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-25739","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26589","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26589","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022257-CVE-2024-26589-0ee1@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26591","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26591","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022258-CVE-2024-26591-8b42@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26601","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26601","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26601","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022411-CVE-2024-26601-b6ac@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26603","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26603","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26603","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022415-CVE-2024-26603-42c2@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26605","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022419-CVE-2024-26605-7b06@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26611","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26611","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-43-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26612","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26612","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-44-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-46-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26618","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26618","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-50-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26631","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26631","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26638","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26638","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-16-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26641","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26641","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26641","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-12-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26645","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26645","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326151722.1258576-4-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26646","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26646","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26646","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-14-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26650","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26650","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26656","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26656","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040247-CVE-2024-26656-ffaa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26660","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26660-3f40@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26661","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26661","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26661","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26661-bef6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26662","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26662-863c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26663-9705@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26664","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26664","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26664-03db@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26669","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040237-CVE-2024-26669-ca3c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26670","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26670","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040238-CVE-2024-26670-ecbd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26672","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26672","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26672-e96e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26674","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26674-4ff9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26675","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26675","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26675-5b19@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26678","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26678","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26678-2cf0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26679","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26679","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26679-d520@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26680","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26680","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26680-d16c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26686","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040335-CVE-2024-26686-b22f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26691","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26691","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26691","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040336-CVE-2024-26691-fff7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26700","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26700","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040339-CVE-2024-26700-a2b8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26704","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26704","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040340-CVE-2024-26704-a082@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26707","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26707","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26707","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26707-1153@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26708","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26708","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26708-c98a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26712","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26712","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26712","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040342-CVE-2024-26712-d713@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26717","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26717","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26717-0d01@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26719","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26719","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26719-b66e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26725","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26725","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040346-CVE-2024-26725-d16b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26733","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26733","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040358-CVE-2024-26733-617f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26734","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273244","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26734","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040359-CVE-2024-26734-277b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26740","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26740","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040300-CVE-2024-26740-4d6f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26743","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26743","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26743-6034@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26744","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26744","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26744-d344@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26746","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26746","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040457-CVE-2024-26746-8aa9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26757","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26757","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26757-7f96@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26758","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26758","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26758-dcc3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26759","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26759","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26759-45f1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26761","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26761","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040305-CVE-2024-26761-0646@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26767","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26767","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26767","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040306-CVE-2024-26767-bdac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26772","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26772","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26772","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040308-CVE-2024-26772-5168@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26774","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26774","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26774","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040308-CVE-2024-26774-52d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26782","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26782","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040458-CVE-2024-26782-71ca@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26785","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26785","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26785-857d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26786","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26786","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26786-802f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26803","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26803","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040404-CVE-2024-26803-9985@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26812","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26812","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040550-CVE-2024-26812-1e08@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26815","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26815","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041006-CVE-2024-26815-7f4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26835","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26835","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041714-CVE-2024-26835-083d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26837","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26837","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26837-753c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26838","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26838","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26838-2fdb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26840-057d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041716-CVE-2024-26843-51a0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26846","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041717-CVE-2024-26846-9593@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26857","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26857","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26857-75ac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26861","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26861-3a78@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26862","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26862","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26862-2605@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26863","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26863","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26863-b742@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26870","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26870","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26870-7aea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26872","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26872","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26872-2d38@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26878-5748@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041741-CVE-2024-26882-be35@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26889","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041742-CVE-2024-26889-edfc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26890","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26890","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26892","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26892","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26892-809e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26894","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26894-53ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26899","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26899","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26899","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26899-3f41@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26900","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26900","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26900-70a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26901-34e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26903","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26903","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26903-de5c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26906","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26906","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26906-bb35@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26907","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26907","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26907-a02d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26915","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26915","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26915-112b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26920","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26920","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26920-a681@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26921","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26921","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041819-CVE-2024-26921-e3b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26922","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26922","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042317-CVE-2024-26922-896d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26924","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042420-CVE-2024-26924-4d1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042844-CVE-2024-26927-3374@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26928","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042849-CVE-2024-26928-e543@gregkh/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26933-c18d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26934-e2fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26937","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26937","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26937-3d21@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26938","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26938","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26938-b3f9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26939-5314@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050125-CVE-2024-26940-1785@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26950","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26950-4424@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26951","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26951","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26951-5cbe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26953","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26953","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050128-CVE-2024-26953-8304@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26958","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26958-6c15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26960-ad6b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26962","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26962","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26962-cbb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26964","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26964-54c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26973","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-26973-54a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26975","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26975","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26975-d184@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26976","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26976","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26976-60d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26984","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050142-CVE-2024-26984-3028@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26987","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26987","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26987-507c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26988","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26988","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26988-c304@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26989-851d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26990","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26990","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26990-0a1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26992","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26992","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050144-CVE-2024-26992-4f0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27003","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27003","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050146-CVE-2024-27003-c862@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27004","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27004","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050147-CVE-2024-27004-c429@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27010-5a68@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27011","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27011","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27011-2c70@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27012","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27012-5564@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27013-2c26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27014-d2dc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27015","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27015-9ce1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27017","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27017","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27017-d867@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27023","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050105-CVE-2024-27023-4810@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27025","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27025","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050107-CVE-2024-27025-babd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050112-CVE-2024-27038-3af3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27042","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27042-e812@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27048","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27048","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050114-CVE-2024-27048-016f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050116-CVE-2024-27057-c0fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27062","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27062","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-27062-3291@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27079","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27079","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27079-f478@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27389","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27389","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050135-CVE-2024-27389-fb3a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27395","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27395","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050836-CVE-2024-27395-573e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27404","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27404","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-27404-ab54@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27410","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051701-CVE-2024-27410-874a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27414","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27414","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051702-CVE-2024-27414-5c5d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27431","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27431","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27431","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051723-CVE-2024-27431-30ae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27436","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27436","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051711-CVE-2024-27436-2227@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27437","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27437","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27437","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040551-CVE-2024-27437-cc07@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-31076","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-31076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-31076","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062134-CVE-2024-31076-786e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35787","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35787","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051707-CVE-2024-35787-dede@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35794","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35794","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051709-CVE-2024-35794-f42d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35795","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35795","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051734-CVE-2024-35795-ee3e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35801","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35801","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-35801-8038@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35805","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35805","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051739-CVE-2024-35805-179f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35807","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35807","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35807-2a9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35808","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35808","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35808-2bf6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35809","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35809-4a4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35810","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35810","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35810","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35810-1b33@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35812","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35812","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35812-c804@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35814","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35814","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051742-CVE-2024-35814-98c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35817","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051743-CVE-2024-35817-d29b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35822","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35822","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051744-CVE-2024-35822-410b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35824","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35824","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051737-CVE-2024-35824-7302@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35827","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35827","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35827","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35827-822c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35831","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35831","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051742-CVE-2024-35831-abcc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35835","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35835","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051730-CVE-2024-35835-d75f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35838","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35838","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051731-CVE-2024-35838-d072@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2024-35840-99fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051717-CVE-2024-35843-516e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35847","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35847","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-35847-7e4b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35853","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35853","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35853-869a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35854","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35854","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35854-d17b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35855","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35855","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35855-c1fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35859","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35859","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051742-CVE-2024-35859-23c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35861","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051937-CVE-2024-35861-dcfe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35862","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35862","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051937-CVE-2024-35862-eda2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35863","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35863","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051938-CVE-2024-35863-7c05@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35864","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35864","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051938-CVE-2024-35864-3536@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35865","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35865","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051939-CVE-2024-35865-c095@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35866","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051939-CVE-2024-35866-97e5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35867","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35867","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051939-CVE-2024-35867-15e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35869","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35869","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051940-CVE-2024-35869-73f8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35872","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35872","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051941-CVE-2024-35872-4632@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35876","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35876","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35876","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35876-d9b5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35877","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35877","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35877-39e6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35878-5af8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35880","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051944-CVE-2024-35880-6ffb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35886","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35886","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051946-CVE-2024-35886-19d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35888","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051947-CVE-2024-35888-1e04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35892","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35892","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051949-CVE-2024-35892-0f0c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35894","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051949-CVE-2024-35894-fd19@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35900","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35900","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051952-CVE-2024-35900-c2c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35904","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35904","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051953-CVE-2024-35904-7f85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35905","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35905","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051954-CVE-2024-35905-d079@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35908","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35908","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051955-CVE-2024-35908-e78a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35912","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35912","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051956-CVE-2024-35912-b093@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35913","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35913","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051956-CVE-2024-35913-72a4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35918","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35918","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051912-CVE-2024-35918-3fed@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35923","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35923","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051914-CVE-2024-35923-ddae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35924","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051914-CVE-2024-35924-90f6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35925","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35925","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051914-CVE-2024-35925-fa17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051915-CVE-2024-35927-2100@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35928","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051915-CVE-2024-35928-ead3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051916-CVE-2024-35930-5571@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051916-CVE-2024-35931-430d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35938","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35938","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051918-CVE-2024-35938-0100@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051919-CVE-2024-35939-f877@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35942","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35942","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051919-CVE-2024-35942-af72@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35944","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35944","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051920-CVE-2024-35944-a860@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35946","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35946","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051921-CVE-2024-35946-c2c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35947","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35947","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051952-CVE-2024-35947-09bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35950","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052015-CVE-2024-35950-41bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35952","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35952","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052017-CVE-2024-35952-645b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35954","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35954","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052018-CVE-2024-35954-cdbf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35957","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35957","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052019-CVE-2024-35957-8c83@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35959","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052019-CVE-2024-35959-6e06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35973","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052024-CVE-2024-35973-1b5b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35976","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35976","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052024-CVE-2024-35976-339b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35979","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35979","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052025-CVE-2024-35979-2618@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35983","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35983","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052018-CVE-2024-35983-a607@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35991","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35991","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052020-CVE-2024-35991-5f06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35995","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35995-abbc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36002","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281961","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36002","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052023-CVE-2024-36002-c5bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36006","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052025-CVE-2024-36006-c032@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052237-CVE-2024-36010-c98b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36015","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052957-CVE-2024-36015-3c7c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36022","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053013-CVE-2024-36022-fe0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36028","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36028","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053057-CVE-2024-36028-e4a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36030","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36030","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053057-CVE-2024-36030-51dc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36031","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36031","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053000-CVE-2024-36031-46f2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36477","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36477","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062150-CVE-2024-36477-7063@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36881","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36881","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36881-24d0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36882-79ff@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36884-c00b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36885","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36885-cb0b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36891","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36891","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36896","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36896","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36896","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053034-CVE-2024-36896-783f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053035-CVE-2024-36901-fb16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36902","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36902","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36905","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36905","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053036-CVE-2024-36905-5884@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36917","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36917","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36917-f9e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36920","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36920","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36920-b4a7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36926","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36926","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36926","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36926-c3a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36927-976e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36928","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36928-845b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36930-8906@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36932","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36932","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36932-c22d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053042-CVE-2024-36933-444e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36936","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36936","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053042-CVE-2024-36936-3116@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053043-CVE-2024-36939-8453@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053043-CVE-2024-36940-0c83@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36944","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36944","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053038-CVE-2024-36944-9d15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36945","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36945","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36945-18ae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36955","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36955","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36955-312f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36956","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36956","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36956-59d8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024060341-CVE-2024-36960-d1bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36961","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36961","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024060344-CVE-2024-36961-58bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024060804-CVE-2024-36967-b73d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36974","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36974","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061810-CVE-2024-36974-a482@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36977","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36977","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38388","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38388","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062137-CVE-2024-38388-fb75@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38555","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38555","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061952-CVE-2024-38555-aefb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38581","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38581","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061948-CVE-2024-38581-592d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38596","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38596","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38596","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061956-CVE-2024-38596-f660@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38598","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38598","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061956-CVE-2024-38598-8629@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38600","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061957-CVE-2024-38600-aa7e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38604","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38604","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061924-CVE-2024-38604-a738@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38605","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061925-CVE-2024-38605-3dc4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293351","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38612","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061922-CVE-2024-38612-7fc1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38618","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38618","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061923-CVE-2024-38618-35a9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38627","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38627","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062140-CVE-2024-38627-9b57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38629","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38629","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38629","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062141-CVE-2024-38629-47c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38632","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38632","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062142-CVE-2024-38632-eaf6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38635","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38635","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062143-CVE-2024-38635-a3b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39276","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39276","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39291","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062432-CVE-2024-39291-be2c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39298","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39298","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062549-CVE-2024-39298-53e8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39471","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062501-CVE-2024-39471-3dee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39473","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39473","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070516-CVE-2024-39473-d28c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39474","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39474","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39474","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070518-CVE-2024-39474-97cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39479","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39479","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39479","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070519-CVE-2024-39479-5bd1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39486","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39486","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39486","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070628-CVE-2024-39486-1ea1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39488","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071013-CVE-2024-39488-f796@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39491","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39491","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071016-CVE-2024-39491-fb62@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39497","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39497","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071202-CVE-2024-39497-834c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39498","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39498-8421@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39499","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39499","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39499-ed0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071204-CVE-2024-39501-058b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39503","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39503","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071204-CVE-2024-39503-e604@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39507","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39507","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39507","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071205-CVE-2024-39507-cbc6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39508","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071206-CVE-2024-39508-20c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071207-CVE-2024-40901-05c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40903","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40903","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071208-CVE-2024-40903-8fd1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40906","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40906","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071209-CVE-2024-40906-b9e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40907","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40907","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071209-CVE-2024-40907-5305@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40913","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40913","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40913-5952@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40919","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40919","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071212-CVE-2024-40919-2997@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40922","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40922","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071213-CVE-2024-40922-461c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40923","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40923","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071213-CVE-2024-40923-5e9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40924","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071213-CVE-2024-40924-9b9b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40925","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40925","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071214-CVE-2024-40925-d411@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071215-CVE-2024-40930-f6bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071218-CVE-2024-40940-5b9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40945","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40945","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071220-CVE-2024-40945-79e6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40948","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071222-CVE-2024-40948-e1a6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40965","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071227-CVE-2024-40965-d9b9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40966","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40966","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071227-CVE-2024-40966-cea6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071227-CVE-2024-40967-665f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40988","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40988","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40988-490e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40989-c8da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40997","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40997","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071251-CVE-2024-40997-df97@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41001","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41001","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071253-CVE-2024-41001-7879@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41007","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41007","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071513-CVE-2024-41007-777c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41008","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240716080357.2696435-2-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41012","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072314-CVE-2024-41012-a1cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41020","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41020","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072927-CVE-2024-41020-52c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41032","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41032","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072922-CVE-2024-41032-6284@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072923-CVE-2024-41038-41ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41039","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41039-b3bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41042","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41042-c338@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41049","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41049","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072927-CVE-2024-41049-bf28@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41056","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41056","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072930-CVE-2024-41056-c324@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072902-CVE-2024-41057-1d06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41058","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41058","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072905-CVE-2024-41058-4593@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41060","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072905-CVE-2024-41060-b7de@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41063","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41063","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072906-CVE-2024-41063-b9bd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41065","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41065","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072907-CVE-2024-41065-2501@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41077","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41077","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41077-9c88@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41079","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41079","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072925-CVE-2024-41079-09c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41082","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41082","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072926-CVE-2024-41082-6e0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41084","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41084","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072951-CVE-2024-41084-c144@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41085","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072951-CVE-2024-41085-9bbd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41089","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41089","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072952-CVE-2024-41089-5d63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41092","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41092","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072953-CVE-2024-41092-8bd7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41093","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072953-CVE-2024-41093-9d6c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41094","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41094","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072953-CVE-2024-41094-374d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41095","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41095","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072954-CVE-2024-41095-7b63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072952-CVE-2024-42070-b271@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42078","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42078","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072954-CVE-2024-42078-bd37@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42084","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42084","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072942-CVE-2024-42084-9283@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42090","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072946-CVE-2024-42090-5687@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073018-CVE-2024-42101-f246@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42114","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42114","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073022-CVE-2024-42114-4585@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42123","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42123","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073025-CVE-2024-42123-056d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42124","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073025-CVE-2024-42124-e4ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42125","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42125","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073026-CVE-2024-42125-b515@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42132","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42132","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073028-CVE-2024-42132-49bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073030-CVE-2024-42141-9017@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42154","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42154","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073034-CVE-2024-42154-cf82@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42159","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42159","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073036-CVE-2024-42159-c19e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42226","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42226-fa39@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42228","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42228-86f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42237","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42237-eba4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42238","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303506","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42238","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42238-a5fd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42240","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080741-CVE-2024-42240-3d04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42245","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303513","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42245","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080742-CVE-2024-42245-1413@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42258","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42258","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081216-CVE-2024-42258-e3f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305413","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42268","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081738-CVE-2024-42268-2084@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305416","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42271","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081739-CVE-2024-42271-c501@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42276","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305421","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42276","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081741-CVE-2024-42276-cb0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42301","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42301","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081749-CVE-2024-42301-4026@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305475","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081723-CVE-2024-43817-2e95@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43826","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305484","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43826","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081726-CVE-2024-43826-2a5f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43830","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43830","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081727-CVE-2024-43830-3b85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43842","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43842","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43842","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081730-CVE-2024-43842-31e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43856","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43856","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081732-CVE-2024-43856-9087@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43865","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306357","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43865","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082156-CVE-2024-43865-743d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43866","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306358","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082157-CVE-2024-43866-66ed@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43869","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43869","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082133-CVE-2024-43869-26aa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43870","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306364","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43870","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082135-CVE-2024-43870-2b6f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306373","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43879","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082137-CVE-2024-43879-95cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43888","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082659-CVE-2024-43888-5beb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43892","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43892","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082604-CVE-2024-43892-584a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43911","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43911","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082631-CVE-2024-43911-96bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44947","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44947","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090219-CVE-2024-44947-f49c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090413-CVE-2024-44960-039b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44965","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090415-CVE-2024-44965-d41d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44970","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44970","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090456-CVE-2024-44970-f687@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44984","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090445-CVE-2024-44984-43ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45005","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45005","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090451-CVE-2024-45005-2297@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58239","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2390320","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58239","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025082210-CVE-2024-58239-dd4f@gregkh/T","tags":["article"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242894-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1082555","tags":["report"]},{"url":"https://bugzilla.suse.com/1193454","tags":["report"]},{"url":"https://bugzilla.suse.com/1193554","tags":["report"]},{"url":"https://bugzilla.suse.com/1193787","tags":["report"]},{"url":"https://bugzilla.suse.com/1194324","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1195357","tags":["report"]},{"url":"https://bugzilla.suse.com/1195668","tags":["report"]},{"url":"https://bugzilla.suse.com/1195927","tags":["report"]},{"url":"https://bugzilla.suse.com/1195957","tags":["report"]},{"url":"https://bugzilla.suse.com/1196018","tags":["report"]},{"url":"https://bugzilla.suse.com/1196823","tags":["report"]},{"url":"https://bugzilla.suse.com/1197146","tags":["report"]},{"url":"https://bugzilla.suse.com/1197246","tags":["report"]},{"url":"https://bugzilla.suse.com/1197762","tags":["report"]},{"url":"https://bugzilla.suse.com/1202346","tags":["report"]},{"url":"https://bugzilla.suse.com/1202686","tags":["report"]},{"url":"https://bugzilla.suse.com/1208783","tags":["report"]},{"url":"https://bugzilla.suse.com/1209636","tags":["report"]},{"url":"https://bugzilla.suse.com/1213123","tags":["report"]},{"url":"https://bugzilla.suse.com/1215492","tags":["report"]},{"url":"https://bugzilla.suse.com/1215587","tags":["report"]},{"url":"https://bugzilla.suse.com/1216834","tags":["report"]},{"url":"https://bugzilla.suse.com/1219832","tags":["report"]},{"url":"https://bugzilla.suse.com/1220138","tags":["report"]},{"url":"https://bugzilla.suse.com/1220185","tags":["report"]},{"url":"https://bugzilla.suse.com/1220186","tags":["report"]},{"url":"https://bugzilla.suse.com/1220187","tags":["report"]},{"url":"https://bugzilla.suse.com/1220869","tags":["report"]},{"url":"https://bugzilla.suse.com/1220876","tags":["report"]},{"url":"https://bugzilla.suse.com/1220942","tags":["report"]},{"url":"https://bugzilla.suse.com/1220952","tags":["report"]},{"url":"https://bugzilla.suse.com/1221010","tags":["report"]},{"url":"https://bugzilla.suse.com/1221044","tags":["report"]},{"url":"https://bugzilla.suse.com/1221647","tags":["report"]},{"url":"https://bugzilla.suse.com/1221654","tags":["report"]},{"url":"https://bugzilla.suse.com/1221656","tags":["report"]},{"url":"https://bugzilla.suse.com/1221659","tags":["report"]},{"url":"https://bugzilla.suse.com/1221777","tags":["report"]},{"url":"https://bugzilla.suse.com/1222011","tags":["report"]},{"url":"https://bugzilla.suse.com/1222323","tags":["report"]},{"url":"https://bugzilla.suse.com/1222326","tags":["report"]},{"url":"https://bugzilla.suse.com/1222328","tags":["report"]},{"url":"https://bugzilla.suse.com/1222625","tags":["report"]},{"url":"https://bugzilla.suse.com/1222702","tags":["report"]},{"url":"https://bugzilla.suse.com/1222728","tags":["report"]},{"url":"https://bugzilla.suse.com/1222799","tags":["report"]},{"url":"https://bugzilla.suse.com/1222809","tags":["report"]},{"url":"https://bugzilla.suse.com/1222810","tags":["report"]},{"url":"https://bugzilla.suse.com/1223021","tags":["report"]},{"url":"https://bugzilla.suse.com/1223180","tags":["report"]},{"url":"https://bugzilla.suse.com/1223635","tags":["report"]},{"url":"https://bugzilla.suse.com/1223652","tags":["report"]},{"url":"https://bugzilla.suse.com/1223675","tags":["report"]},{"url":"https://bugzilla.suse.com/1223778","tags":["report"]},{"url":"https://bugzilla.suse.com/1223806","tags":["report"]},{"url":"https://bugzilla.suse.com/1223813","tags":["report"]},{"url":"https://bugzilla.suse.com/1223815","tags":["report"]},{"url":"https://bugzilla.suse.com/1223836","tags":["report"]},{"url":"https://bugzilla.suse.com/1223863","tags":["report"]},{"url":"https://bugzilla.suse.com/1224414","tags":["report"]},{"url":"https://bugzilla.suse.com/1224499","tags":["report"]},{"url":"https://bugzilla.suse.com/1224500","tags":["report"]},{"url":"https://bugzilla.suse.com/1224512","tags":["report"]},{"url":"https://bugzilla.suse.com/1224516","tags":["report"]},{"url":"https://bugzilla.suse.com/1224517","tags":["report"]},{"url":"https://bugzilla.suse.com/1224545","tags":["report"]},{"url":"https://bugzilla.suse.com/1224548","tags":["report"]},{"url":"https://bugzilla.suse.com/1224557","tags":["report"]},{"url":"https://bugzilla.suse.com/1224572","tags":["report"]},{"url":"https://bugzilla.suse.com/1224573","tags":["report"]},{"url":"https://bugzilla.suse.com/1224585","tags":["report"]},{"url":"https://bugzilla.suse.com/1224604","tags":["report"]},{"url":"https://bugzilla.suse.com/1224636","tags":["report"]},{"url":"https://bugzilla.suse.com/1224641","tags":["report"]},{"url":"https://bugzilla.suse.com/1224683","tags":["report"]},{"url":"https://bugzilla.suse.com/1224694","tags":["report"]},{"url":"https://bugzilla.suse.com/1224700","tags":["report"]},{"url":"https://bugzilla.suse.com/1224743","tags":["report"]},{"url":"https://bugzilla.suse.com/1225088","tags":["report"]},{"url":"https://bugzilla.suse.com/1225272","tags":["report"]},{"url":"https://bugzilla.suse.com/1225301","tags":["report"]},{"url":"https://bugzilla.suse.com/1225475","tags":["report"]},{"url":"https://bugzilla.suse.com/1225489","tags":["report"]},{"url":"https://bugzilla.suse.com/1225504","tags":["report"]},{"url":"https://bugzilla.suse.com/1225505","tags":["report"]},{"url":"https://bugzilla.suse.com/1225564","tags":["report"]},{"url":"https://bugzilla.suse.com/1225573","tags":["report"]},{"url":"https://bugzilla.suse.com/1225581","tags":["report"]},{"url":"https://bugzilla.suse.com/1225586","tags":["report"]},{"url":"https://bugzilla.suse.com/1225711","tags":["report"]},{"url":"https://bugzilla.suse.com/1225717","tags":["report"]},{"url":"https://bugzilla.suse.com/1225719","tags":["report"]},{"url":"https://bugzilla.suse.com/1225744","tags":["report"]},{"url":"https://bugzilla.suse.com/1225745","tags":["report"]},{"url":"https://bugzilla.suse.com/1225746","tags":["report"]},{"url":"https://bugzilla.suse.com/1225752","tags":["report"]},{"url":"https://bugzilla.suse.com/1225753","tags":["report"]},{"url":"https://bugzilla.suse.com/1225757","tags":["report"]},{"url":"https://bugzilla.suse.com/1225767","tags":["report"]},{"url":"https://bugzilla.suse.com/1225810","tags":["report"]},{"url":"https://bugzilla.suse.com/1225815","tags":["report"]},{"url":"https://bugzilla.suse.com/1225820","tags":["report"]},{"url":"https://bugzilla.suse.com/1225829","tags":["report"]},{"url":"https://bugzilla.suse.com/1225835","tags":["report"]},{"url":"https://bugzilla.suse.com/1225838","tags":["report"]},{"url":"https://bugzilla.suse.com/1225839","tags":["report"]},{"url":"https://bugzilla.suse.com/1225843","tags":["report"]},{"url":"https://bugzilla.suse.com/1225847","tags":["report"]},{"url":"https://bugzilla.suse.com/1225851","tags":["report"]},{"url":"https://bugzilla.suse.com/1225856","tags":["report"]},{"url":"https://bugzilla.suse.com/1225895","tags":["report"]},{"url":"https://bugzilla.suse.com/1225898","tags":["report"]},{"url":"https://bugzilla.suse.com/1225903","tags":["report"]},{"url":"https://bugzilla.suse.com/1226202","tags":["report"]},{"url":"https://bugzilla.suse.com/1226502","tags":["report"]},{"url":"https://bugzilla.suse.com/1226519","tags":["report"]},{"url":"https://bugzilla.suse.com/1226551","tags":["report"]},{"url":"https://bugzilla.suse.com/1226555","tags":["report"]},{"url":"https://bugzilla.suse.com/1226565","tags":["report"]},{"url":"https://bugzilla.suse.com/1226568","tags":["report"]},{"url":"https://bugzilla.suse.com/1226570","tags":["report"]},{"url":"https://bugzilla.suse.com/1226571","tags":["report"]},{"url":"https://bugzilla.suse.com/1226574","tags":["report"]},{"url":"https://bugzilla.suse.com/1226588","tags":["report"]},{"url":"https://bugzilla.suse.com/1226607","tags":["report"]},{"url":"https://bugzilla.suse.com/1226650","tags":["report"]},{"url":"https://bugzilla.suse.com/1226698","tags":["report"]},{"url":"https://bugzilla.suse.com/1226713","tags":["report"]},{"url":"https://bugzilla.suse.com/1226716","tags":["report"]},{"url":"https://bugzilla.suse.com/1226750","tags":["report"]},{"url":"https://bugzilla.suse.com/1226757","tags":["report"]},{"url":"https://bugzilla.suse.com/1226758","tags":["report"]},{"url":"https://bugzilla.suse.com/1226775","tags":["report"]},{"url":"https://bugzilla.suse.com/1226783","tags":["report"]},{"url":"https://bugzilla.suse.com/1226785","tags":["report"]},{"url":"https://bugzilla.suse.com/1226834","tags":["report"]},{"url":"https://bugzilla.suse.com/1226837","tags":["report"]},{"url":"https://bugzilla.suse.com/1226911","tags":["report"]},{"url":"https://bugzilla.suse.com/1226990","tags":["report"]},{"url":"https://bugzilla.suse.com/1226993","tags":["report"]},{"url":"https://bugzilla.suse.com/1227090","tags":["report"]},{"url":"https://bugzilla.suse.com/1227121","tags":["report"]},{"url":"https://bugzilla.suse.com/1227157","tags":["report"]},{"url":"https://bugzilla.suse.com/1227162","tags":["report"]},{"url":"https://bugzilla.suse.com/1227362","tags":["report"]},{"url":"https://bugzilla.suse.com/1227383","tags":["report"]},{"url":"https://bugzilla.suse.com/1227432","tags":["report"]},{"url":"https://bugzilla.suse.com/1227435","tags":["report"]},{"url":"https://bugzilla.suse.com/1227447","tags":["report"]},{"url":"https://bugzilla.suse.com/1227487","tags":["report"]},{"url":"https://bugzilla.suse.com/1227549","tags":["report"]},{"url":"https://bugzilla.suse.com/1227573","tags":["report"]},{"url":"https://bugzilla.suse.com/1227618","tags":["report"]},{"url":"https://bugzilla.suse.com/1227620","tags":["report"]},{"url":"https://bugzilla.suse.com/1227626","tags":["report"]},{"url":"https://bugzilla.suse.com/1227635","tags":["report"]},{"url":"https://bugzilla.suse.com/1227661","tags":["report"]},{"url":"https://bugzilla.suse.com/1227716","tags":["report"]},{"url":"https://bugzilla.suse.com/1227722","tags":["report"]},{"url":"https://bugzilla.suse.com/1227724","tags":["report"]},{"url":"https://bugzilla.suse.com/1227725","tags":["report"]},{"url":"https://bugzilla.suse.com/1227728","tags":["report"]},{"url":"https://bugzilla.suse.com/1227729","tags":["report"]},{"url":"https://bugzilla.suse.com/1227730","tags":["report"]},{"url":"https://bugzilla.suse.com/1227732","tags":["report"]},{"url":"https://bugzilla.suse.com/1227733","tags":["report"]},{"url":"https://bugzilla.suse.com/1227750","tags":["report"]},{"url":"https://bugzilla.suse.com/1227754","tags":["report"]},{"url":"https://bugzilla.suse.com/1227755","tags":["report"]},{"url":"https://bugzilla.suse.com/1227760","tags":["report"]},{"url":"https://bugzilla.suse.com/1227762","tags":["report"]},{"url":"https://bugzilla.suse.com/1227763","tags":["report"]},{"url":"https://bugzilla.suse.com/1227764","tags":["report"]},{"url":"https://bugzilla.suse.com/1227766","tags":["report"]},{"url":"https://bugzilla.suse.com/1227770","tags":["report"]},{"url":"https://bugzilla.suse.com/1227771","tags":["report"]},{"url":"https://bugzilla.suse.com/1227772","tags":["report"]},{"url":"https://bugzilla.suse.com/1227774","tags":["report"]},{"url":"https://bugzilla.suse.com/1227779","tags":["report"]},{"url":"https://bugzilla.suse.com/1227780","tags":["report"]},{"url":"https://bugzilla.suse.com/1227783","tags":["report"]},{"url":"https://bugzilla.suse.com/1227786","tags":["report"]},{"url":"https://bugzilla.suse.com/1227787","tags":["report"]},{"url":"https://bugzilla.suse.com/1227790","tags":["report"]},{"url":"https://bugzilla.suse.com/1227792","tags":["report"]},{"url":"https://bugzilla.suse.com/1227796","tags":["report"]},{"url":"https://bugzilla.suse.com/1227797","tags":["report"]},{"url":"https://bugzilla.suse.com/1227798","tags":["report"]},{"url":"https://bugzilla.suse.com/1227800","tags":["report"]},{"url":"https://bugzilla.suse.com/1227802","tags":["report"]},{"url":"https://bugzilla.suse.com/1227806","tags":["report"]},{"url":"https://bugzilla.suse.com/1227808","tags":["report"]},{"url":"https://bugzilla.suse.com/1227810","tags":["report"]},{"url":"https://bugzilla.suse.com/1227812","tags":["report"]},{"url":"https://bugzilla.suse.com/1227813","tags":["report"]},{"url":"https://bugzilla.suse.com/1227814","tags":["report"]},{"url":"https://bugzilla.suse.com/1227816","tags":["report"]},{"url":"https://bugzilla.suse.com/1227820","tags":["report"]},{"url":"https://bugzilla.suse.com/1227823","tags":["report"]},{"url":"https://bugzilla.suse.com/1227824","tags":["report"]},{"url":"https://bugzilla.suse.com/1227828","tags":["report"]},{"url":"https://bugzilla.suse.com/1227829","tags":["report"]},{"url":"https://bugzilla.suse.com/1227836","tags":["report"]},{"url":"https://bugzilla.suse.com/1227846","tags":["report"]},{"url":"https://bugzilla.suse.com/1227849","tags":["report"]},{"url":"https://bugzilla.suse.com/1227851","tags":["report"]},{"url":"https://bugzilla.suse.com/1227862","tags":["report"]},{"url":"https://bugzilla.suse.com/1227864","tags":["report"]},{"url":"https://bugzilla.suse.com/1227865","tags":["report"]},{"url":"https://bugzilla.suse.com/1227866","tags":["report"]},{"url":"https://bugzilla.suse.com/1227870","tags":["report"]},{"url":"https://bugzilla.suse.com/1227884","tags":["report"]},{"url":"https://bugzilla.suse.com/1227886","tags":["report"]},{"url":"https://bugzilla.suse.com/1227891","tags":["report"]},{"url":"https://bugzilla.suse.com/1227893","tags":["report"]},{"url":"https://bugzilla.suse.com/1227899","tags":["report"]},{"url":"https://bugzilla.suse.com/1227900","tags":["report"]},{"url":"https://bugzilla.suse.com/1227910","tags":["report"]},{"url":"https://bugzilla.suse.com/1227913","tags":["report"]},{"url":"https://bugzilla.suse.com/1227917","tags":["report"]},{"url":"https://bugzilla.suse.com/1227919","tags":["report"]},{"url":"https://bugzilla.suse.com/1227920","tags":["report"]},{"url":"https://bugzilla.suse.com/1227921","tags":["report"]},{"url":"https://bugzilla.suse.com/1227922","tags":["report"]},{"url":"https://bugzilla.suse.com/1227923","tags":["report"]},{"url":"https://bugzilla.suse.com/1227924","tags":["report"]},{"url":"https://bugzilla.suse.com/1227925","tags":["report"]},{"url":"https://bugzilla.suse.com/1227927","tags":["report"]},{"url":"https://bugzilla.suse.com/1227928","tags":["report"]},{"url":"https://bugzilla.suse.com/1227931","tags":["report"]},{"url":"https://bugzilla.suse.com/1227932","tags":["report"]},{"url":"https://bugzilla.suse.com/1227933","tags":["report"]},{"url":"https://bugzilla.suse.com/1227935","tags":["report"]},{"url":"https://bugzilla.suse.com/1227936","tags":["report"]},{"url":"https://bugzilla.suse.com/1227938","tags":["report"]},{"url":"https://bugzilla.suse.com/1227941","tags":["report"]},{"url":"https://bugzilla.suse.com/1227942","tags":["report"]},{"url":"https://bugzilla.suse.com/1227944","tags":["report"]},{"url":"https://bugzilla.suse.com/1227945","tags":["report"]},{"url":"https://bugzilla.suse.com/1227947","tags":["report"]},{"url":"https://bugzilla.suse.com/1227948","tags":["report"]},{"url":"https://bugzilla.suse.com/1227949","tags":["report"]},{"url":"https://bugzilla.suse.com/1227950","tags":["report"]},{"url":"https://bugzilla.suse.com/1227952","tags":["report"]},{"url":"https://bugzilla.suse.com/1227953","tags":["report"]},{"url":"https://bugzilla.suse.com/1227954","tags":["report"]},{"url":"https://bugzilla.suse.com/1227956","tags":["report"]},{"url":"https://bugzilla.suse.com/1227957","tags":["report"]},{"url":"https://bugzilla.suse.com/1227963","tags":["report"]},{"url":"https://bugzilla.suse.com/1227964","tags":["report"]},{"url":"https://bugzilla.suse.com/1227965","tags":["report"]},{"url":"https://bugzilla.suse.com/1227968","tags":["report"]},{"url":"https://bugzilla.suse.com/1227969","tags":["report"]},{"url":"https://bugzilla.suse.com/1227970","tags":["report"]},{"url":"https://bugzilla.suse.com/1227971","tags":["report"]},{"url":"https://bugzilla.suse.com/1227972","tags":["report"]},{"url":"https://bugzilla.suse.com/1227975","tags":["report"]},{"url":"https://bugzilla.suse.com/1227976","tags":["report"]},{"url":"https://bugzilla.suse.com/1227981","tags":["report"]},{"url":"https://bugzilla.suse.com/1227982","tags":["report"]},{"url":"https://bugzilla.suse.com/1227985","tags":["report"]},{"url":"https://bugzilla.suse.com/1227986","tags":["report"]},{"url":"https://bugzilla.suse.com/1227987","tags":["report"]},{"url":"https://bugzilla.suse.com/1227988","tags":["report"]},{"url":"https://bugzilla.suse.com/1227989","tags":["report"]},{"url":"https://bugzilla.suse.com/1227990","tags":["report"]},{"url":"https://bugzilla.suse.com/1227991","tags":["report"]},{"url":"https://bugzilla.suse.com/1227992","tags":["report"]},{"url":"https://bugzilla.suse.com/1227993","tags":["report"]},{"url":"https://bugzilla.suse.com/1227995","tags":["report"]},{"url":"https://bugzilla.suse.com/1227996","tags":["report"]},{"url":"https://bugzilla.suse.com/1227997","tags":["report"]},{"url":"https://bugzilla.suse.com/1228000","tags":["report"]},{"url":"https://bugzilla.suse.com/1228002","tags":["report"]},{"url":"https://bugzilla.suse.com/1228003","tags":["report"]},{"url":"https://bugzilla.suse.com/1228004","tags":["report"]},{"url":"https://bugzilla.suse.com/1228005","tags":["report"]},{"url":"https://bugzilla.suse.com/1228006","tags":["report"]},{"url":"https://bugzilla.suse.com/1228007","tags":["report"]},{"url":"https://bugzilla.suse.com/1228008","tags":["report"]},{"url":"https://bugzilla.suse.com/1228009","tags":["report"]},{"url":"https://bugzilla.suse.com/1228010","tags":["report"]},{"url":"https://bugzilla.suse.com/1228011","tags":["report"]},{"url":"https://bugzilla.suse.com/1228013","tags":["report"]},{"url":"https://bugzilla.suse.com/1228014","tags":["report"]},{"url":"https://bugzilla.suse.com/1228015","tags":["report"]},{"url":"https://bugzilla.suse.com/1228019","tags":["report"]},{"url":"https://bugzilla.suse.com/1228020","tags":["report"]},{"url":"https://bugzilla.suse.com/1228025","tags":["report"]},{"url":"https://bugzilla.suse.com/1228028","tags":["report"]},{"url":"https://bugzilla.suse.com/1228035","tags":["report"]},{"url":"https://bugzilla.suse.com/1228037","tags":["report"]},{"url":"https://bugzilla.suse.com/1228038","tags":["report"]},{"url":"https://bugzilla.suse.com/1228039","tags":["report"]},{"url":"https://bugzilla.suse.com/1228040","tags":["report"]},{"url":"https://bugzilla.suse.com/1228045","tags":["report"]},{"url":"https://bugzilla.suse.com/1228054","tags":["report"]},{"url":"https://bugzilla.suse.com/1228055","tags":["report"]},{"url":"https://bugzilla.suse.com/1228056","tags":["report"]},{"url":"https://bugzilla.suse.com/1228060","tags":["report"]},{"url":"https://bugzilla.suse.com/1228061","tags":["report"]},{"url":"https://bugzilla.suse.com/1228062","tags":["report"]},{"url":"https://bugzilla.suse.com/1228063","tags":["report"]},{"url":"https://bugzilla.suse.com/1228064","tags":["report"]},{"url":"https://bugzilla.suse.com/1228066","tags":["report"]},{"url":"https://bugzilla.suse.com/1228067","tags":["report"]},{"url":"https://bugzilla.suse.com/1228068","tags":["report"]},{"url":"https://bugzilla.suse.com/1228071","tags":["report"]},{"url":"https://bugzilla.suse.com/1228079","tags":["report"]},{"url":"https://bugzilla.suse.com/1228090","tags":["report"]},{"url":"https://bugzilla.suse.com/1228114","tags":["report"]},{"url":"https://bugzilla.suse.com/1228140","tags":["report"]},{"url":"https://bugzilla.suse.com/1228190","tags":["report"]},{"url":"https://bugzilla.suse.com/1228191","tags":["report"]},{"url":"https://bugzilla.suse.com/1228195","tags":["report"]},{"url":"https://bugzilla.suse.com/1228202","tags":["report"]},{"url":"https://bugzilla.suse.com/1228226","tags":["report"]},{"url":"https://bugzilla.suse.com/1228235","tags":["report"]},{"url":"https://bugzilla.suse.com/1228237","tags":["report"]},{"url":"https://bugzilla.suse.com/1228247","tags":["report"]},{"url":"https://bugzilla.suse.com/1228327","tags":["report"]},{"url":"https://bugzilla.suse.com/1228328","tags":["report"]},{"url":"https://bugzilla.suse.com/1228330","tags":["report"]},{"url":"https://bugzilla.suse.com/1228403","tags":["report"]},{"url":"https://bugzilla.suse.com/1228405","tags":["report"]},{"url":"https://bugzilla.suse.com/1228408","tags":["report"]},{"url":"https://bugzilla.suse.com/1228409","tags":["report"]},{"url":"https://bugzilla.suse.com/1228410","tags":["report"]},{"url":"https://bugzilla.suse.com/1228418","tags":["report"]},{"url":"https://bugzilla.suse.com/1228440","tags":["report"]},{"url":"https://bugzilla.suse.com/1228459","tags":["report"]},{"url":"https://bugzilla.suse.com/1228462","tags":["report"]},{"url":"https://bugzilla.suse.com/1228470","tags":["report"]},{"url":"https://bugzilla.suse.com/1228518","tags":["report"]},{"url":"https://bugzilla.suse.com/1228520","tags":["report"]},{"url":"https://bugzilla.suse.com/1228530","tags":["report"]},{"url":"https://bugzilla.suse.com/1228561","tags":["report"]},{"url":"https://bugzilla.suse.com/1228565","tags":["report"]},{"url":"https://bugzilla.suse.com/1228580","tags":["report"]},{"url":"https://bugzilla.suse.com/1228581","tags":["report"]},{"url":"https://bugzilla.suse.com/1228591","tags":["report"]},{"url":"https://bugzilla.suse.com/1228599","tags":["report"]},{"url":"https://bugzilla.suse.com/1228617","tags":["report"]},{"url":"https://bugzilla.suse.com/1228625","tags":["report"]},{"url":"https://bugzilla.suse.com/1228626","tags":["report"]},{"url":"https://bugzilla.suse.com/1228633","tags":["report"]},{"url":"https://bugzilla.suse.com/1228640","tags":["report"]},{"url":"https://bugzilla.suse.com/1228644","tags":["report"]},{"url":"https://bugzilla.suse.com/1228649","tags":["report"]},{"url":"https://bugzilla.suse.com/1228655","tags":["report"]},{"url":"https://bugzilla.suse.com/1228665","tags":["report"]},{"url":"https://bugzilla.suse.com/1228672","tags":["report"]},{"url":"https://bugzilla.suse.com/1228680","tags":["report"]},{"url":"https://bugzilla.suse.com/1228705","tags":["report"]},{"url":"https://bugzilla.suse.com/1228723","tags":["report"]},{"url":"https://bugzilla.suse.com/1228743","tags":["report"]},{"url":"https://bugzilla.suse.com/1228756","tags":["report"]},{"url":"https://bugzilla.suse.com/1228801","tags":["report"]},{"url":"https://bugzilla.suse.com/1228850","tags":["report"]},{"url":"https://bugzilla.suse.com/1228857","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47624","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48774","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48787","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-48791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48820","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48827","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48843","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-37453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52762","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-25741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26633","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26641","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42230","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242939-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1156395","tags":["report"]},{"url":"https://bugzilla.suse.com/1190336","tags":["report"]},{"url":"https://bugzilla.suse.com/1191958","tags":["report"]},{"url":"https://bugzilla.suse.com/1193883","tags":["report"]},{"url":"https://bugzilla.suse.com/1194826","tags":["report"]},{"url":"https://bugzilla.suse.com/1195065","tags":["report"]},{"url":"https://bugzilla.suse.com/1195254","tags":["report"]},{"url":"https://bugzilla.suse.com/1195341","tags":["report"]},{"url":"https://bugzilla.suse.com/1195349","tags":["report"]},{"url":"https://bugzilla.suse.com/1195775","tags":["report"]},{"url":"https://bugzilla.suse.com/1196746","tags":["report"]},{"url":"https://bugzilla.suse.com/1197915","tags":["report"]},{"url":"https://bugzilla.suse.com/1198014","tags":["report"]},{"url":"https://bugzilla.suse.com/1199295","tags":["report"]},{"url":"https://bugzilla.suse.com/1202767","tags":["report"]},{"url":"https://bugzilla.suse.com/1202780","tags":["report"]},{"url":"https://bugzilla.suse.com/1205205","tags":["report"]},{"url":"https://bugzilla.suse.com/1207361","tags":["report"]},{"url":"https://bugzilla.suse.com/1217912","tags":["report"]},{"url":"https://bugzilla.suse.com/1218148","tags":["report"]},{"url":"https://bugzilla.suse.com/1218570","tags":["report"]},{"url":"https://bugzilla.suse.com/1218820","tags":["report"]},{"url":"https://bugzilla.suse.com/1219224","tags":["report"]},{"url":"https://bugzilla.suse.com/1219633","tags":["report"]},{"url":"https://bugzilla.suse.com/1219847","tags":["report"]},{"url":"https://bugzilla.suse.com/1220368","tags":["report"]},{"url":"https://bugzilla.suse.com/1220812","tags":["report"]},{"url":"https://bugzilla.suse.com/1220958","tags":["report"]},{"url":"https://bugzilla.suse.com/1221086","tags":["report"]},{"url":"https://bugzilla.suse.com/1221282","tags":["report"]},{"url":"https://bugzilla.suse.com/1221958","tags":["report"]},{"url":"https://bugzilla.suse.com/1222015","tags":["report"]},{"url":"https://bugzilla.suse.com/1222072","tags":["report"]},{"url":"https://bugzilla.suse.com/1222080","tags":["report"]},{"url":"https://bugzilla.suse.com/1222241","tags":["report"]},{"url":"https://bugzilla.suse.com/1222254","tags":["report"]},{"url":"https://bugzilla.suse.com/1222364","tags":["report"]},{"url":"https://bugzilla.suse.com/1222893","tags":["report"]},{"url":"https://bugzilla.suse.com/1223013","tags":["report"]},{"url":"https://bugzilla.suse.com/1223018","tags":["report"]},{"url":"https://bugzilla.suse.com/1223265","tags":["report"]},{"url":"https://bugzilla.suse.com/1223384","tags":["report"]},{"url":"https://bugzilla.suse.com/1223641","tags":["report"]},{"url":"https://bugzilla.suse.com/1224020","tags":["report"]},{"url":"https://bugzilla.suse.com/1224331","tags":["report"]},{"url":"https://bugzilla.suse.com/1224488","tags":["report"]},{"url":"https://bugzilla.suse.com/1224497","tags":["report"]},{"url":"https://bugzilla.suse.com/1224498","tags":["report"]},{"url":"https://bugzilla.suse.com/1224504","tags":["report"]},{"url":"https://bugzilla.suse.com/1224520","tags":["report"]},{"url":"https://bugzilla.suse.com/1224539","tags":["report"]},{"url":"https://bugzilla.suse.com/1224540","tags":["report"]},{"url":"https://bugzilla.suse.com/1224552","tags":["report"]},{"url":"https://bugzilla.suse.com/1224583","tags":["report"]},{"url":"https://bugzilla.suse.com/1224588","tags":["report"]},{"url":"https://bugzilla.suse.com/1224602","tags":["report"]},{"url":"https://bugzilla.suse.com/1224603","tags":["report"]},{"url":"https://bugzilla.suse.com/1224605","tags":["report"]},{"url":"https://bugzilla.suse.com/1224612","tags":["report"]},{"url":"https://bugzilla.suse.com/1224614","tags":["report"]},{"url":"https://bugzilla.suse.com/1224619","tags":["report"]},{"url":"https://bugzilla.suse.com/1224661","tags":["report"]},{"url":"https://bugzilla.suse.com/1224662","tags":["report"]},{"url":"https://bugzilla.suse.com/1224670","tags":["report"]},{"url":"https://bugzilla.suse.com/1224671","tags":["report"]},{"url":"https://bugzilla.suse.com/1224674","tags":["report"]},{"url":"https://bugzilla.suse.com/1224677","tags":["report"]},{"url":"https://bugzilla.suse.com/1224679","tags":["report"]},{"url":"https://bugzilla.suse.com/1224696","tags":["report"]},{"url":"https://bugzilla.suse.com/1224703","tags":["report"]},{"url":"https://bugzilla.suse.com/1224712","tags":["report"]},{"url":"https://bugzilla.suse.com/1224716","tags":["report"]},{"url":"https://bugzilla.suse.com/1224719","tags":["report"]},{"url":"https://bugzilla.suse.com/1224735","tags":["report"]},{"url":"https://bugzilla.suse.com/1224749","tags":["report"]},{"url":"https://bugzilla.suse.com/1224764","tags":["report"]},{"url":"https://bugzilla.suse.com/1224765","tags":["report"]},{"url":"https://bugzilla.suse.com/1224766","tags":["report"]},{"url":"https://bugzilla.suse.com/1224935","tags":["report"]},{"url":"https://bugzilla.suse.com/1224946","tags":["report"]},{"url":"https://bugzilla.suse.com/1224951","tags":["report"]},{"url":"https://bugzilla.suse.com/1225050","tags":["report"]},{"url":"https://bugzilla.suse.com/1225098","tags":["report"]},{"url":"https://bugzilla.suse.com/1225105","tags":["report"]},{"url":"https://bugzilla.suse.com/1225300","tags":["report"]},{"url":"https://bugzilla.suse.com/1225389","tags":["report"]},{"url":"https://bugzilla.suse.com/1225391","tags":["report"]},{"url":"https://bugzilla.suse.com/1225419","tags":["report"]},{"url":"https://bugzilla.suse.com/1225426","tags":["report"]},{"url":"https://bugzilla.suse.com/1225448","tags":["report"]},{"url":"https://bugzilla.suse.com/1225452","tags":["report"]},{"url":"https://bugzilla.suse.com/1225467","tags":["report"]},{"url":"https://bugzilla.suse.com/1225484","tags":["report"]},{"url":"https://bugzilla.suse.com/1225487","tags":["report"]},{"url":"https://bugzilla.suse.com/1225514","tags":["report"]},{"url":"https://bugzilla.suse.com/1225518","tags":["report"]},{"url":"https://bugzilla.suse.com/1225535","tags":["report"]},{"url":"https://bugzilla.suse.com/1225585","tags":["report"]},{"url":"https://bugzilla.suse.com/1225602","tags":["report"]},{"url":"https://bugzilla.suse.com/1225611","tags":["report"]},{"url":"https://bugzilla.suse.com/1225681","tags":["report"]},{"url":"https://bugzilla.suse.com/1225692","tags":["report"]},{"url":"https://bugzilla.suse.com/1225698","tags":["report"]},{"url":"https://bugzilla.suse.com/1225699","tags":["report"]},{"url":"https://bugzilla.suse.com/1225704","tags":["report"]},{"url":"https://bugzilla.suse.com/1225714","tags":["report"]},{"url":"https://bugzilla.suse.com/1225726","tags":["report"]},{"url":"https://bugzilla.suse.com/1225732","tags":["report"]},{"url":"https://bugzilla.suse.com/1225737","tags":["report"]},{"url":"https://bugzilla.suse.com/1225749","tags":["report"]},{"url":"https://bugzilla.suse.com/1225758","tags":["report"]},{"url":"https://bugzilla.suse.com/1225759","tags":["report"]},{"url":"https://bugzilla.suse.com/1225760","tags":["report"]},{"url":"https://bugzilla.suse.com/1225770","tags":["report"]},{"url":"https://bugzilla.suse.com/1225823","tags":["report"]},{"url":"https://bugzilla.suse.com/1225834","tags":["report"]},{"url":"https://bugzilla.suse.com/1225840","tags":["report"]},{"url":"https://bugzilla.suse.com/1225866","tags":["report"]},{"url":"https://bugzilla.suse.com/1225872","tags":["report"]},{"url":"https://bugzilla.suse.com/1225894","tags":["report"]},{"url":"https://bugzilla.suse.com/1226022","tags":["report"]},{"url":"https://bugzilla.suse.com/1226131","tags":["report"]},{"url":"https://bugzilla.suse.com/1226145","tags":["report"]},{"url":"https://bugzilla.suse.com/1226149","tags":["report"]},{"url":"https://bugzilla.suse.com/1226155","tags":["report"]},{"url":"https://bugzilla.suse.com/1226211","tags":["report"]},{"url":"https://bugzilla.suse.com/1226212","tags":["report"]},{"url":"https://bugzilla.suse.com/1226226","tags":["report"]},{"url":"https://bugzilla.suse.com/1226514","tags":["report"]},{"url":"https://bugzilla.suse.com/1226520","tags":["report"]},{"url":"https://bugzilla.suse.com/1226537","tags":["report"]},{"url":"https://bugzilla.suse.com/1226538","tags":["report"]},{"url":"https://bugzilla.suse.com/1226539","tags":["report"]},{"url":"https://bugzilla.suse.com/1226550","tags":["report"]},{"url":"https://bugzilla.suse.com/1226552","tags":["report"]},{"url":"https://bugzilla.suse.com/1226553","tags":["report"]},{"url":"https://bugzilla.suse.com/1226554","tags":["report"]},{"url":"https://bugzilla.suse.com/1226556","tags":["report"]},{"url":"https://bugzilla.suse.com/1226557","tags":["report"]},{"url":"https://bugzilla.suse.com/1226558","tags":["report"]},{"url":"https://bugzilla.suse.com/1226559","tags":["report"]},{"url":"https://bugzilla.suse.com/1226561","tags":["report"]},{"url":"https://bugzilla.suse.com/1226562","tags":["report"]},{"url":"https://bugzilla.suse.com/1226563","tags":["report"]},{"url":"https://bugzilla.suse.com/1226564","tags":["report"]},{"url":"https://bugzilla.suse.com/1226566","tags":["report"]},{"url":"https://bugzilla.suse.com/1226567","tags":["report"]},{"url":"https://bugzilla.suse.com/1226569","tags":["report"]},{"url":"https://bugzilla.suse.com/1226572","tags":["report"]},{"url":"https://bugzilla.suse.com/1226575","tags":["report"]},{"url":"https://bugzilla.suse.com/1226576","tags":["report"]},{"url":"https://bugzilla.suse.com/1226577","tags":["report"]},{"url":"https://bugzilla.suse.com/1226579","tags":["report"]},{"url":"https://bugzilla.suse.com/1226580","tags":["report"]},{"url":"https://bugzilla.suse.com/1226581","tags":["report"]},{"url":"https://bugzilla.suse.com/1226582","tags":["report"]},{"url":"https://bugzilla.suse.com/1226583","tags":["report"]},{"url":"https://bugzilla.suse.com/1226585","tags":["report"]},{"url":"https://bugzilla.suse.com/1226587","tags":["report"]},{"url":"https://bugzilla.suse.com/1226593","tags":["report"]},{"url":"https://bugzilla.suse.com/1226595","tags":["report"]},{"url":"https://bugzilla.suse.com/1226597","tags":["report"]},{"url":"https://bugzilla.suse.com/1226601","tags":["report"]},{"url":"https://bugzilla.suse.com/1226602","tags":["report"]},{"url":"https://bugzilla.suse.com/1226603","tags":["report"]},{"url":"https://bugzilla.suse.com/1226610","tags":["report"]},{"url":"https://bugzilla.suse.com/1226614","tags":["report"]},{"url":"https://bugzilla.suse.com/1226616","tags":["report"]},{"url":"https://bugzilla.suse.com/1226617","tags":["report"]},{"url":"https://bugzilla.suse.com/1226618","tags":["report"]},{"url":"https://bugzilla.suse.com/1226619","tags":["report"]},{"url":"https://bugzilla.suse.com/1226621","tags":["report"]},{"url":"https://bugzilla.suse.com/1226622","tags":["report"]},{"url":"https://bugzilla.suse.com/1226624","tags":["report"]},{"url":"https://bugzilla.suse.com/1226626","tags":["report"]},{"url":"https://bugzilla.suse.com/1226628","tags":["report"]},{"url":"https://bugzilla.suse.com/1226629","tags":["report"]},{"url":"https://bugzilla.suse.com/1226632","tags":["report"]},{"url":"https://bugzilla.suse.com/1226633","tags":["report"]},{"url":"https://bugzilla.suse.com/1226634","tags":["report"]},{"url":"https://bugzilla.suse.com/1226637","tags":["report"]},{"url":"https://bugzilla.suse.com/1226643","tags":["report"]},{"url":"https://bugzilla.suse.com/1226644","tags":["report"]},{"url":"https://bugzilla.suse.com/1226645","tags":["report"]},{"url":"https://bugzilla.suse.com/1226647","tags":["report"]},{"url":"https://bugzilla.suse.com/1226653","tags":["report"]},{"url":"https://bugzilla.suse.com/1226657","tags":["report"]},{"url":"https://bugzilla.suse.com/1226658","tags":["report"]},{"url":"https://bugzilla.suse.com/1226669","tags":["report"]},{"url":"https://bugzilla.suse.com/1226670","tags":["report"]},{"url":"https://bugzilla.suse.com/1226672","tags":["report"]},{"url":"https://bugzilla.suse.com/1226673","tags":["report"]},{"url":"https://bugzilla.suse.com/1226674","tags":["report"]},{"url":"https://bugzilla.suse.com/1226675","tags":["report"]},{"url":"https://bugzilla.suse.com/1226678","tags":["report"]},{"url":"https://bugzilla.suse.com/1226679","tags":["report"]},{"url":"https://bugzilla.suse.com/1226683","tags":["report"]},{"url":"https://bugzilla.suse.com/1226685","tags":["report"]},{"url":"https://bugzilla.suse.com/1226686","tags":["report"]},{"url":"https://bugzilla.suse.com/1226690","tags":["report"]},{"url":"https://bugzilla.suse.com/1226691","tags":["report"]},{"url":"https://bugzilla.suse.com/1226692","tags":["report"]},{"url":"https://bugzilla.suse.com/1226693","tags":["report"]},{"url":"https://bugzilla.suse.com/1226696","tags":["report"]},{"url":"https://bugzilla.suse.com/1226697","tags":["report"]},{"url":"https://bugzilla.suse.com/1226699","tags":["report"]},{"url":"https://bugzilla.suse.com/1226701","tags":["report"]},{"url":"https://bugzilla.suse.com/1226702","tags":["report"]},{"url":"https://bugzilla.suse.com/1226703","tags":["report"]},{"url":"https://bugzilla.suse.com/1226704","tags":["report"]},{"url":"https://bugzilla.suse.com/1226705","tags":["report"]},{"url":"https://bugzilla.suse.com/1226706","tags":["report"]},{"url":"https://bugzilla.suse.com/1226708","tags":["report"]},{"url":"https://bugzilla.suse.com/1226709","tags":["report"]},{"url":"https://bugzilla.suse.com/1226710","tags":["report"]},{"url":"https://bugzilla.suse.com/1226711","tags":["report"]},{"url":"https://bugzilla.suse.com/1226712","tags":["report"]},{"url":"https://bugzilla.suse.com/1226715","tags":["report"]},{"url":"https://bugzilla.suse.com/1226718","tags":["report"]},{"url":"https://bugzilla.suse.com/1226719","tags":["report"]},{"url":"https://bugzilla.suse.com/1226720","tags":["report"]},{"url":"https://bugzilla.suse.com/1226721","tags":["report"]},{"url":"https://bugzilla.suse.com/1226730","tags":["report"]},{"url":"https://bugzilla.suse.com/1226732","tags":["report"]},{"url":"https://bugzilla.suse.com/1226734","tags":["report"]},{"url":"https://bugzilla.suse.com/1226735","tags":["report"]},{"url":"https://bugzilla.suse.com/1226737","tags":["report"]},{"url":"https://bugzilla.suse.com/1226738","tags":["report"]},{"url":"https://bugzilla.suse.com/1226739","tags":["report"]},{"url":"https://bugzilla.suse.com/1226740","tags":["report"]},{"url":"https://bugzilla.suse.com/1226744","tags":["report"]},{"url":"https://bugzilla.suse.com/1226746","tags":["report"]},{"url":"https://bugzilla.suse.com/1226747","tags":["report"]},{"url":"https://bugzilla.suse.com/1226749","tags":["report"]},{"url":"https://bugzilla.suse.com/1226754","tags":["report"]},{"url":"https://bugzilla.suse.com/1226762","tags":["report"]},{"url":"https://bugzilla.suse.com/1226764","tags":["report"]},{"url":"https://bugzilla.suse.com/1226767","tags":["report"]},{"url":"https://bugzilla.suse.com/1226768","tags":["report"]},{"url":"https://bugzilla.suse.com/1226769","tags":["report"]},{"url":"https://bugzilla.suse.com/1226771","tags":["report"]},{"url":"https://bugzilla.suse.com/1226774","tags":["report"]},{"url":"https://bugzilla.suse.com/1226777","tags":["report"]},{"url":"https://bugzilla.suse.com/1226780","tags":["report"]},{"url":"https://bugzilla.suse.com/1226781","tags":["report"]},{"url":"https://bugzilla.suse.com/1226786","tags":["report"]},{"url":"https://bugzilla.suse.com/1226789","tags":["report"]},{"url":"https://bugzilla.suse.com/1226791","tags":["report"]},{"url":"https://bugzilla.suse.com/1226839","tags":["report"]},{"url":"https://bugzilla.suse.com/1226840","tags":["report"]},{"url":"https://bugzilla.suse.com/1226841","tags":["report"]},{"url":"https://bugzilla.suse.com/1226842","tags":["report"]},{"url":"https://bugzilla.suse.com/1226848","tags":["report"]},{"url":"https://bugzilla.suse.com/1226852","tags":["report"]},{"url":"https://bugzilla.suse.com/1226857","tags":["report"]},{"url":"https://bugzilla.suse.com/1226861","tags":["report"]},{"url":"https://bugzilla.suse.com/1226863","tags":["report"]},{"url":"https://bugzilla.suse.com/1226864","tags":["report"]},{"url":"https://bugzilla.suse.com/1226867","tags":["report"]},{"url":"https://bugzilla.suse.com/1226868","tags":["report"]},{"url":"https://bugzilla.suse.com/1226876","tags":["report"]},{"url":"https://bugzilla.suse.com/1226878","tags":["report"]},{"url":"https://bugzilla.suse.com/1226883","tags":["report"]},{"url":"https://bugzilla.suse.com/1226886","tags":["report"]},{"url":"https://bugzilla.suse.com/1226890","tags":["report"]},{"url":"https://bugzilla.suse.com/1226891","tags":["report"]},{"url":"https://bugzilla.suse.com/1226895","tags":["report"]},{"url":"https://bugzilla.suse.com/1226908","tags":["report"]},{"url":"https://bugzilla.suse.com/1226915","tags":["report"]},{"url":"https://bugzilla.suse.com/1226928","tags":["report"]},{"url":"https://bugzilla.suse.com/1226948","tags":["report"]},{"url":"https://bugzilla.suse.com/1226949","tags":["report"]},{"url":"https://bugzilla.suse.com/1226950","tags":["report"]},{"url":"https://bugzilla.suse.com/1226953","tags":["report"]},{"url":"https://bugzilla.suse.com/1226962","tags":["report"]},{"url":"https://bugzilla.suse.com/1226976","tags":["report"]},{"url":"https://bugzilla.suse.com/1226992","tags":["report"]},{"url":"https://bugzilla.suse.com/1226994","tags":["report"]},{"url":"https://bugzilla.suse.com/1226996","tags":["report"]},{"url":"https://bugzilla.suse.com/1227066","tags":["report"]},{"url":"https://bugzilla.suse.com/1227096","tags":["report"]},{"url":"https://bugzilla.suse.com/1227101","tags":["report"]},{"url":"https://bugzilla.suse.com/1227103","tags":["report"]},{"url":"https://bugzilla.suse.com/1227274","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-4439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47592","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47610","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47611","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47614","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47616","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47617","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-24023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52843","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-33619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-37021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-37078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-37354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38545","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38616","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38621","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38633","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38634","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39471","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242947-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243194-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1205462","tags":["report"]},{"url":"https://bugzilla.suse.com/1214285","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1220066","tags":["report"]},{"url":"https://bugzilla.suse.com/1220252","tags":["report"]},{"url":"https://bugzilla.suse.com/1220877","tags":["report"]},{"url":"https://bugzilla.suse.com/1221326","tags":["report"]},{"url":"https://bugzilla.suse.com/1221630","tags":["report"]},{"url":"https://bugzilla.suse.com/1221645","tags":["report"]},{"url":"https://bugzilla.suse.com/1221652","tags":["report"]},{"url":"https://bugzilla.suse.com/1221857","tags":["report"]},{"url":"https://bugzilla.suse.com/1222335","tags":["report"]},{"url":"https://bugzilla.suse.com/1222350","tags":["report"]},{"url":"https://bugzilla.suse.com/1222372","tags":["report"]},{"url":"https://bugzilla.suse.com/1222387","tags":["report"]},{"url":"https://bugzilla.suse.com/1222433","tags":["report"]},{"url":"https://bugzilla.suse.com/1222434","tags":["report"]},{"url":"https://bugzilla.suse.com/1222463","tags":["report"]},{"url":"https://bugzilla.suse.com/1222633","tags":["report"]},{"url":"https://bugzilla.suse.com/1222634","tags":["report"]},{"url":"https://bugzilla.suse.com/1222808","tags":["report"]},{"url":"https://bugzilla.suse.com/1222967","tags":["report"]},{"url":"https://bugzilla.suse.com/1222973","tags":["report"]},{"url":"https://bugzilla.suse.com/1223053","tags":["report"]},{"url":"https://bugzilla.suse.com/1223074","tags":["report"]},{"url":"https://bugzilla.suse.com/1223191","tags":["report"]},{"url":"https://bugzilla.suse.com/1223395","tags":["report"]},{"url":"https://bugzilla.suse.com/1223720","tags":["report"]},{"url":"https://bugzilla.suse.com/1223731","tags":["report"]},{"url":"https://bugzilla.suse.com/1223742","tags":["report"]},{"url":"https://bugzilla.suse.com/1223763","tags":["report"]},{"url":"https://bugzilla.suse.com/1223767","tags":["report"]},{"url":"https://bugzilla.suse.com/1223777","tags":["report"]},{"url":"https://bugzilla.suse.com/1223803","tags":["report"]},{"url":"https://bugzilla.suse.com/1224105","tags":["report"]},{"url":"https://bugzilla.suse.com/1224415","tags":["report"]},{"url":"https://bugzilla.suse.com/1224485","tags":["report"]},{"url":"https://bugzilla.suse.com/1224496","tags":["report"]},{"url":"https://bugzilla.suse.com/1224510","tags":["report"]},{"url":"https://bugzilla.suse.com/1224535","tags":["report"]},{"url":"https://bugzilla.suse.com/1224631","tags":["report"]},{"url":"https://bugzilla.suse.com/1224690","tags":["report"]},{"url":"https://bugzilla.suse.com/1224711","tags":["report"]},{"url":"https://bugzilla.suse.com/1225582","tags":["report"]},{"url":"https://bugzilla.suse.com/1225607","tags":["report"]},{"url":"https://bugzilla.suse.com/1225718","tags":["report"]},{"url":"https://bugzilla.suse.com/1225751","tags":["report"]},{"url":"https://bugzilla.suse.com/1225814","tags":["report"]},{"url":"https://bugzilla.suse.com/1225832","tags":["report"]},{"url":"https://bugzilla.suse.com/1226031","tags":["report"]},{"url":"https://bugzilla.suse.com/1226127","tags":["report"]},{"url":"https://bugzilla.suse.com/1226530","tags":["report"]},{"url":"https://bugzilla.suse.com/1226604","tags":["report"]},{"url":"https://bugzilla.suse.com/1226743","tags":["report"]},{"url":"https://bugzilla.suse.com/1226751","tags":["report"]},{"url":"https://bugzilla.suse.com/1226765","tags":["report"]},{"url":"https://bugzilla.suse.com/1226798","tags":["report"]},{"url":"https://bugzilla.suse.com/1226801","tags":["report"]},{"url":"https://bugzilla.suse.com/1226874","tags":["report"]},{"url":"https://bugzilla.suse.com/1226885","tags":["report"]},{"url":"https://bugzilla.suse.com/1226920","tags":["report"]},{"url":"https://bugzilla.suse.com/1227149","tags":["report"]},{"url":"https://bugzilla.suse.com/1227182","tags":["report"]},{"url":"https://bugzilla.suse.com/1227437","tags":["report"]},{"url":"https://bugzilla.suse.com/1227492","tags":["report"]},{"url":"https://bugzilla.suse.com/1227493","tags":["report"]},{"url":"https://bugzilla.suse.com/1227494","tags":["report"]},{"url":"https://bugzilla.suse.com/1227623","tags":["report"]},{"url":"https://bugzilla.suse.com/1227627","tags":["report"]},{"url":"https://bugzilla.suse.com/1227634","tags":["report"]},{"url":"https://bugzilla.suse.com/1227706","tags":["report"]},{"url":"https://bugzilla.suse.com/1227734","tags":["report"]},{"url":"https://bugzilla.suse.com/1227747","tags":["report"]},{"url":"https://bugzilla.suse.com/1227758","tags":["report"]},{"url":"https://bugzilla.suse.com/1227761","tags":["report"]},{"url":"https://bugzilla.suse.com/1227781","tags":["report"]},{"url":"https://bugzilla.suse.com/1227784","tags":["report"]},{"url":"https://bugzilla.suse.com/1227785","tags":["report"]},{"url":"https://bugzilla.suse.com/1227791","tags":["report"]},{"url":"https://bugzilla.suse.com/1227799","tags":["report"]},{"url":"https://bugzilla.suse.com/1227811","tags":["report"]},{"url":"https://bugzilla.suse.com/1227815","tags":["report"]},{"url":"https://bugzilla.suse.com/1227818","tags":["report"]},{"url":"https://bugzilla.suse.com/1227826","tags":["report"]},{"url":"https://bugzilla.suse.com/1227830","tags":["report"]},{"url":"https://bugzilla.suse.com/1227832","tags":["report"]},{"url":"https://bugzilla.suse.com/1227833","tags":["report"]},{"url":"https://bugzilla.suse.com/1227834","tags":["report"]},{"url":"https://bugzilla.suse.com/1227839","tags":["report"]},{"url":"https://bugzilla.suse.com/1227840","tags":["report"]},{"url":"https://bugzilla.suse.com/1227853","tags":["report"]},{"url":"https://bugzilla.suse.com/1227863","tags":["report"]},{"url":"https://bugzilla.suse.com/1227867","tags":["report"]},{"url":"https://bugzilla.suse.com/1227869","tags":["report"]},{"url":"https://bugzilla.suse.com/1227883","tags":["report"]},{"url":"https://bugzilla.suse.com/1227929","tags":["report"]},{"url":"https://bugzilla.suse.com/1228021","tags":["report"]},{"url":"https://bugzilla.suse.com/1228192","tags":["report"]},{"url":"https://bugzilla.suse.com/1228236","tags":["report"]},{"url":"https://bugzilla.suse.com/1228321","tags":["report"]},{"url":"https://bugzilla.suse.com/1228426","tags":["report"]},{"url":"https://bugzilla.suse.com/1228427","tags":["report"]},{"url":"https://bugzilla.suse.com/1228429","tags":["report"]},{"url":"https://bugzilla.suse.com/1228446","tags":["report"]},{"url":"https://bugzilla.suse.com/1228447","tags":["report"]},{"url":"https://bugzilla.suse.com/1228449","tags":["report"]},{"url":"https://bugzilla.suse.com/1228450","tags":["report"]},{"url":"https://bugzilla.suse.com/1228452","tags":["report"]},{"url":"https://bugzilla.suse.com/1228456","tags":["report"]},{"url":"https://bugzilla.suse.com/1228457","tags":["report"]},{"url":"https://bugzilla.suse.com/1228458","tags":["report"]},{"url":"https://bugzilla.suse.com/1228460","tags":["report"]},{"url":"https://bugzilla.suse.com/1228463","tags":["report"]},{"url":"https://bugzilla.suse.com/1228466","tags":["report"]},{"url":"https://bugzilla.suse.com/1228467","tags":["report"]},{"url":"https://bugzilla.suse.com/1228468","tags":["report"]},{"url":"https://bugzilla.suse.com/1228469","tags":["report"]},{"url":"https://bugzilla.suse.com/1228472","tags":["report"]},{"url":"https://bugzilla.suse.com/1228479","tags":["report"]},{"url":"https://bugzilla.suse.com/1228480","tags":["report"]},{"url":"https://bugzilla.suse.com/1228481","tags":["report"]},{"url":"https://bugzilla.suse.com/1228482","tags":["report"]},{"url":"https://bugzilla.suse.com/1228483","tags":["report"]},{"url":"https://bugzilla.suse.com/1228484","tags":["report"]},{"url":"https://bugzilla.suse.com/1228485","tags":["report"]},{"url":"https://bugzilla.suse.com/1228486","tags":["report"]},{"url":"https://bugzilla.suse.com/1228487","tags":["report"]},{"url":"https://bugzilla.suse.com/1228489","tags":["report"]},{"url":"https://bugzilla.suse.com/1228491","tags":["report"]},{"url":"https://bugzilla.suse.com/1228492","tags":["report"]},{"url":"https://bugzilla.suse.com/1228493","tags":["report"]},{"url":"https://bugzilla.suse.com/1228494","tags":["report"]},{"url":"https://bugzilla.suse.com/1228495","tags":["report"]},{"url":"https://bugzilla.suse.com/1228496","tags":["report"]},{"url":"https://bugzilla.suse.com/1228499","tags":["report"]},{"url":"https://bugzilla.suse.com/1228500","tags":["report"]},{"url":"https://bugzilla.suse.com/1228501","tags":["report"]},{"url":"https://bugzilla.suse.com/1228502","tags":["report"]},{"url":"https://bugzilla.suse.com/1228503","tags":["report"]},{"url":"https://bugzilla.suse.com/1228505","tags":["report"]},{"url":"https://bugzilla.suse.com/1228508","tags":["report"]},{"url":"https://bugzilla.suse.com/1228509","tags":["report"]},{"url":"https://bugzilla.suse.com/1228510","tags":["report"]},{"url":"https://bugzilla.suse.com/1228511","tags":["report"]},{"url":"https://bugzilla.suse.com/1228513","tags":["report"]},{"url":"https://bugzilla.suse.com/1228515","tags":["report"]},{"url":"https://bugzilla.suse.com/1228516","tags":["report"]},{"url":"https://bugzilla.suse.com/1228525","tags":["report"]},{"url":"https://bugzilla.suse.com/1228527","tags":["report"]},{"url":"https://bugzilla.suse.com/1228531","tags":["report"]},{"url":"https://bugzilla.suse.com/1228539","tags":["report"]},{"url":"https://bugzilla.suse.com/1228563","tags":["report"]},{"url":"https://bugzilla.suse.com/1228564","tags":["report"]},{"url":"https://bugzilla.suse.com/1228567","tags":["report"]},{"url":"https://bugzilla.suse.com/1228568","tags":["report"]},{"url":"https://bugzilla.suse.com/1228572","tags":["report"]},{"url":"https://bugzilla.suse.com/1228576","tags":["report"]},{"url":"https://bugzilla.suse.com/1228579","tags":["report"]},{"url":"https://bugzilla.suse.com/1228582","tags":["report"]},{"url":"https://bugzilla.suse.com/1228584","tags":["report"]},{"url":"https://bugzilla.suse.com/1228586","tags":["report"]},{"url":"https://bugzilla.suse.com/1228588","tags":["report"]},{"url":"https://bugzilla.suse.com/1228590","tags":["report"]},{"url":"https://bugzilla.suse.com/1228615","tags":["report"]},{"url":"https://bugzilla.suse.com/1228616","tags":["report"]},{"url":"https://bugzilla.suse.com/1228635","tags":["report"]},{"url":"https://bugzilla.suse.com/1228636","tags":["report"]},{"url":"https://bugzilla.suse.com/1228643","tags":["report"]},{"url":"https://bugzilla.suse.com/1228646","tags":["report"]},{"url":"https://bugzilla.suse.com/1228650","tags":["report"]},{"url":"https://bugzilla.suse.com/1228654","tags":["report"]},{"url":"https://bugzilla.suse.com/1228656","tags":["report"]},{"url":"https://bugzilla.suse.com/1228658","tags":["report"]},{"url":"https://bugzilla.suse.com/1228660","tags":["report"]},{"url":"https://bugzilla.suse.com/1228662","tags":["report"]},{"url":"https://bugzilla.suse.com/1228666","tags":["report"]},{"url":"https://bugzilla.suse.com/1228667","tags":["report"]},{"url":"https://bugzilla.suse.com/1228673","tags":["report"]},{"url":"https://bugzilla.suse.com/1228674","tags":["report"]},{"url":"https://bugzilla.suse.com/1228677","tags":["report"]},{"url":"https://bugzilla.suse.com/1228687","tags":["report"]},{"url":"https://bugzilla.suse.com/1228706","tags":["report"]},{"url":"https://bugzilla.suse.com/1228707","tags":["report"]},{"url":"https://bugzilla.suse.com/1228708","tags":["report"]},{"url":"https://bugzilla.suse.com/1228709","tags":["report"]},{"url":"https://bugzilla.suse.com/1228710","tags":["report"]},{"url":"https://bugzilla.suse.com/1228718","tags":["report"]},{"url":"https://bugzilla.suse.com/1228720","tags":["report"]},{"url":"https://bugzilla.suse.com/1228721","tags":["report"]},{"url":"https://bugzilla.suse.com/1228722","tags":["report"]},{"url":"https://bugzilla.suse.com/1228724","tags":["report"]},{"url":"https://bugzilla.suse.com/1228726","tags":["report"]},{"url":"https://bugzilla.suse.com/1228727","tags":["report"]},{"url":"https://bugzilla.suse.com/1228733","tags":["report"]},{"url":"https://bugzilla.suse.com/1228737","tags":["report"]},{"url":"https://bugzilla.suse.com/1228748","tags":["report"]},{"url":"https://bugzilla.suse.com/1228754","tags":["report"]},{"url":"https://bugzilla.suse.com/1228757","tags":["report"]},{"url":"https://bugzilla.suse.com/1228758","tags":["report"]},{"url":"https://bugzilla.suse.com/1228764","tags":["report"]},{"url":"https://bugzilla.suse.com/1228766","tags":["report"]},{"url":"https://bugzilla.suse.com/1228779","tags":["report"]},{"url":"https://bugzilla.suse.com/1228849","tags":["report"]},{"url":"https://bugzilla.suse.com/1228959","tags":["report"]},{"url":"https://bugzilla.suse.com/1228964","tags":["report"]},{"url":"https://bugzilla.suse.com/1228966","tags":["report"]},{"url":"https://bugzilla.suse.com/1228967","tags":["report"]},{"url":"https://bugzilla.suse.com/1228973","tags":["report"]},{"url":"https://bugzilla.suse.com/1228977","tags":["report"]},{"url":"https://bugzilla.suse.com/1228978","tags":["report"]},{"url":"https://bugzilla.suse.com/1228979","tags":["report"]},{"url":"https://bugzilla.suse.com/1228986","tags":["report"]},{"url":"https://bugzilla.suse.com/1228988","tags":["report"]},{"url":"https://bugzilla.suse.com/1228989","tags":["report"]},{"url":"https://bugzilla.suse.com/1228991","tags":["report"]},{"url":"https://bugzilla.suse.com/1228992","tags":["report"]},{"url":"https://bugzilla.suse.com/1229005","tags":["report"]},{"url":"https://bugzilla.suse.com/1229024","tags":["report"]},{"url":"https://bugzilla.suse.com/1229042","tags":["report"]},{"url":"https://bugzilla.suse.com/1229045","tags":["report"]},{"url":"https://bugzilla.suse.com/1229046","tags":["report"]},{"url":"https://bugzilla.suse.com/1229054","tags":["report"]},{"url":"https://bugzilla.suse.com/1229056","tags":["report"]},{"url":"https://bugzilla.suse.com/1229086","tags":["report"]},{"url":"https://bugzilla.suse.com/1229134","tags":["report"]},{"url":"https://bugzilla.suse.com/1229136","tags":["report"]},{"url":"https://bugzilla.suse.com/1229154","tags":["report"]},{"url":"https://bugzilla.suse.com/1229156","tags":["report"]},{"url":"https://bugzilla.suse.com/1229160","tags":["report"]},{"url":"https://bugzilla.suse.com/1229167","tags":["report"]},{"url":"https://bugzilla.suse.com/1229168","tags":["report"]},{"url":"https://bugzilla.suse.com/1229169","tags":["report"]},{"url":"https://bugzilla.suse.com/1229170","tags":["report"]},{"url":"https://bugzilla.suse.com/1229171","tags":["report"]},{"url":"https://bugzilla.suse.com/1229172","tags":["report"]},{"url":"https://bugzilla.suse.com/1229173","tags":["report"]},{"url":"https://bugzilla.suse.com/1229174","tags":["report"]},{"url":"https://bugzilla.suse.com/1229239","tags":["report"]},{"url":"https://bugzilla.suse.com/1229240","tags":["report"]},{"url":"https://bugzilla.suse.com/1229241","tags":["report"]},{"url":"https://bugzilla.suse.com/1229243","tags":["report"]},{"url":"https://bugzilla.suse.com/1229244","tags":["report"]},{"url":"https://bugzilla.suse.com/1229245","tags":["report"]},{"url":"https://bugzilla.suse.com/1229246","tags":["report"]},{"url":"https://bugzilla.suse.com/1229247","tags":["report"]},{"url":"https://bugzilla.suse.com/1229248","tags":["report"]},{"url":"https://bugzilla.suse.com/1229249","tags":["report"]},{"url":"https://bugzilla.suse.com/1229250","tags":["report"]},{"url":"https://bugzilla.suse.com/1229251","tags":["report"]},{"url":"https://bugzilla.suse.com/1229252","tags":["report"]},{"url":"https://bugzilla.suse.com/1229253","tags":["report"]},{"url":"https://bugzilla.suse.com/1229254","tags":["report"]},{"url":"https://bugzilla.suse.com/1229255","tags":["report"]},{"url":"https://bugzilla.suse.com/1229256","tags":["report"]},{"url":"https://bugzilla.suse.com/1229287","tags":["report"]},{"url":"https://bugzilla.suse.com/1229290","tags":["report"]},{"url":"https://bugzilla.suse.com/1229291","tags":["report"]},{"url":"https://bugzilla.suse.com/1229292","tags":["report"]},{"url":"https://bugzilla.suse.com/1229294","tags":["report"]},{"url":"https://bugzilla.suse.com/1229296","tags":["report"]},{"url":"https://bugzilla.suse.com/1229297","tags":["report"]},{"url":"https://bugzilla.suse.com/1229298","tags":["report"]},{"url":"https://bugzilla.suse.com/1229299","tags":["report"]},{"url":"https://bugzilla.suse.com/1229301","tags":["report"]},{"url":"https://bugzilla.suse.com/1229303","tags":["report"]},{"url":"https://bugzilla.suse.com/1229304","tags":["report"]},{"url":"https://bugzilla.suse.com/1229305","tags":["report"]},{"url":"https://bugzilla.suse.com/1229307","tags":["report"]},{"url":"https://bugzilla.suse.com/1229309","tags":["report"]},{"url":"https://bugzilla.suse.com/1229312","tags":["report"]},{"url":"https://bugzilla.suse.com/1229313","tags":["report"]},{"url":"https://bugzilla.suse.com/1229314","tags":["report"]},{"url":"https://bugzilla.suse.com/1229315","tags":["report"]},{"url":"https://bugzilla.suse.com/1229316","tags":["report"]},{"url":"https://bugzilla.suse.com/1229317","tags":["report"]},{"url":"https://bugzilla.suse.com/1229318","tags":["report"]},{"url":"https://bugzilla.suse.com/1229319","tags":["report"]},{"url":"https://bugzilla.suse.com/1229320","tags":["report"]},{"url":"https://bugzilla.suse.com/1229327","tags":["report"]},{"url":"https://bugzilla.suse.com/1229341","tags":["report"]},{"url":"https://bugzilla.suse.com/1229342","tags":["report"]},{"url":"https://bugzilla.suse.com/1229344","tags":["report"]},{"url":"https://bugzilla.suse.com/1229345","tags":["report"]},{"url":"https://bugzilla.suse.com/1229346","tags":["report"]},{"url":"https://bugzilla.suse.com/1229347","tags":["report"]},{"url":"https://bugzilla.suse.com/1229349","tags":["report"]},{"url":"https://bugzilla.suse.com/1229350","tags":["report"]},{"url":"https://bugzilla.suse.com/1229351","tags":["report"]},{"url":"https://bugzilla.suse.com/1229353","tags":["report"]},{"url":"https://bugzilla.suse.com/1229354","tags":["report"]},{"url":"https://bugzilla.suse.com/1229355","tags":["report"]},{"url":"https://bugzilla.suse.com/1229356","tags":["report"]},{"url":"https://bugzilla.suse.com/1229357","tags":["report"]},{"url":"https://bugzilla.suse.com/1229358","tags":["report"]},{"url":"https://bugzilla.suse.com/1229359","tags":["report"]},{"url":"https://bugzilla.suse.com/1229360","tags":["report"]},{"url":"https://bugzilla.suse.com/1229365","tags":["report"]},{"url":"https://bugzilla.suse.com/1229366","tags":["report"]},{"url":"https://bugzilla.suse.com/1229369","tags":["report"]},{"url":"https://bugzilla.suse.com/1229370","tags":["report"]},{"url":"https://bugzilla.suse.com/1229373","tags":["report"]},{"url":"https://bugzilla.suse.com/1229374","tags":["report"]},{"url":"https://bugzilla.suse.com/1229379","tags":["report"]},{"url":"https://bugzilla.suse.com/1229381","tags":["report"]},{"url":"https://bugzilla.suse.com/1229382","tags":["report"]},{"url":"https://bugzilla.suse.com/1229383","tags":["report"]},{"url":"https://bugzilla.suse.com/1229386","tags":["report"]},{"url":"https://bugzilla.suse.com/1229388","tags":["report"]},{"url":"https://bugzilla.suse.com/1229390","tags":["report"]},{"url":"https://bugzilla.suse.com/1229391","tags":["report"]},{"url":"https://bugzilla.suse.com/1229392","tags":["report"]},{"url":"https://bugzilla.suse.com/1229395","tags":["report"]},{"url":"https://bugzilla.suse.com/1229398","tags":["report"]},{"url":"https://bugzilla.suse.com/1229399","tags":["report"]},{"url":"https://bugzilla.suse.com/1229400","tags":["report"]},{"url":"https://bugzilla.suse.com/1229402","tags":["report"]},{"url":"https://bugzilla.suse.com/1229403","tags":["report"]},{"url":"https://bugzilla.suse.com/1229404","tags":["report"]},{"url":"https://bugzilla.suse.com/1229407","tags":["report"]},{"url":"https://bugzilla.suse.com/1229409","tags":["report"]},{"url":"https://bugzilla.suse.com/1229410","tags":["report"]},{"url":"https://bugzilla.suse.com/1229411","tags":["report"]},{"url":"https://bugzilla.suse.com/1229413","tags":["report"]},{"url":"https://bugzilla.suse.com/1229414","tags":["report"]},{"url":"https://bugzilla.suse.com/1229417","tags":["report"]},{"url":"https://bugzilla.suse.com/1229444","tags":["report"]},{"url":"https://bugzilla.suse.com/1229451","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/1229480","tags":["report"]},{"url":"https://bugzilla.suse.com/1229481","tags":["report"]},{"url":"https://bugzilla.suse.com/1229482","tags":["report"]},{"url":"https://bugzilla.suse.com/1229484","tags":["report"]},{"url":"https://bugzilla.suse.com/1229485","tags":["report"]},{"url":"https://bugzilla.suse.com/1229486","tags":["report"]},{"url":"https://bugzilla.suse.com/1229487","tags":["report"]},{"url":"https://bugzilla.suse.com/1229488","tags":["report"]},{"url":"https://bugzilla.suse.com/1229489","tags":["report"]},{"url":"https://bugzilla.suse.com/1229490","tags":["report"]},{"url":"https://bugzilla.suse.com/1229493","tags":["report"]},{"url":"https://bugzilla.suse.com/1229495","tags":["report"]},{"url":"https://bugzilla.suse.com/1229496","tags":["report"]},{"url":"https://bugzilla.suse.com/1229497","tags":["report"]},{"url":"https://bugzilla.suse.com/1229500","tags":["report"]},{"url":"https://bugzilla.suse.com/1229503","tags":["report"]},{"url":"https://bugzilla.suse.com/1229707","tags":["report"]},{"url":"https://bugzilla.suse.com/1229739","tags":["report"]},{"url":"https://bugzilla.suse.com/1229743","tags":["report"]},{"url":"https://bugzilla.suse.com/1229746","tags":["report"]},{"url":"https://bugzilla.suse.com/1229747","tags":["report"]},{"url":"https://bugzilla.suse.com/1229752","tags":["report"]},{"url":"https://bugzilla.suse.com/1229754","tags":["report"]},{"url":"https://bugzilla.suse.com/1229755","tags":["report"]},{"url":"https://bugzilla.suse.com/1229756","tags":["report"]},{"url":"https://bugzilla.suse.com/1229759","tags":["report"]},{"url":"https://bugzilla.suse.com/1229761","tags":["report"]},{"url":"https://bugzilla.suse.com/1229767","tags":["report"]},{"url":"https://bugzilla.suse.com/1229781","tags":["report"]},{"url":"https://bugzilla.suse.com/1229784","tags":["report"]},{"url":"https://bugzilla.suse.com/1229785","tags":["report"]},{"url":"https://bugzilla.suse.com/1229787","tags":["report"]},{"url":"https://bugzilla.suse.com/1229788","tags":["report"]},{"url":"https://bugzilla.suse.com/1229789","tags":["report"]},{"url":"https://bugzilla.suse.com/1229792","tags":["report"]},{"url":"https://bugzilla.suse.com/1229820","tags":["report"]},{"url":"https://bugzilla.suse.com/1229827","tags":["report"]},{"url":"https://bugzilla.suse.com/1229830","tags":["report"]},{"url":"https://bugzilla.suse.com/1229837","tags":["report"]},{"url":"https://bugzilla.suse.com/1229940","tags":["report"]},{"url":"https://bugzilla.suse.com/1230056","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-31076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39486","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44939","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243195-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1219596","tags":["report"]},{"url":"https://bugzilla.suse.com/1222777","tags":["report"]},{"url":"https://bugzilla.suse.com/1225461","tags":["report"]},{"url":"https://bugzilla.suse.com/1225474","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26767","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243383-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1230350","tags":["report"]},{"url":"https://bugzilla.suse.com/1230413","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520044-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1228971","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520047-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1229025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40945","tags":["report"]},{"url":"https://git.kernel.org/linus/89e8a2366e3bce584b6c01549d5019c5cda1205e","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-6999-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7003-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7003-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7004-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7005-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7006-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7003-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7007-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7008-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7005-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7009-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7019-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7007-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6999-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7007-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7029-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7009-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7003-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7003-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-48772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-31076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-32936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-33619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-33621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-33847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-34027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-34030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-34777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38385","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36894","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-41034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42119","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-42145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-46926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41027","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-41055","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-42068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42109","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-42130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-38096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41009","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-42228","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-40945","title":"iommu: Return right value in iommu_sva_bind_device()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.","status":"published","published":"2024-07-12T12:25:19.164Z","modified":"2026-10-15T00:45:43.208Z","updated_at":"2026-11-02T14:34:07.152829Z"}],"euvd":[{"id":"EUVD-2024-38833","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.","status":"published","published":"2024-07-12T12:25:19Z","modified":"2026-10-15T00:45:43Z","updated_at":"2026-11-02T17:27:09.754388Z"}],"ghsa":[{"id":"GHSA-fh5c-w77m-vmmm","title":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.","status":"published","published":"2024-07-12T15:31:28Z","modified":"2026-10-15T03:34:57Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T15:13:31.301503Z"}],"nvd":[{"id":"CVE-2024-40945","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.","status":"published","published":"2024-07-12T13:15:16.853Z","modified":"2026-10-15T01:18:38.13Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T14:10:12.994089Z"}],"osv":[{"id":"BELL-CVE-2024-40945","status":"published","published":"2024-07-16T05:58:42.317814Z","modified":"2026-01-26T09:34:58.626976Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:20.200735Z"},{"id":"DEBIAN-CVE-2024-40945","description":"In the Linux kernel, the following vulnerability has been resolved:  iommu: Return right value in iommu_sva_bind_device()  iommu_sva_bind_device() should return either a sva bond handle or an ERR_PTR value in error cases. Existing drivers (idxd and uacce) only check the return value with IS_ERR(). This could potentially lead to a kernel NULL pointer dereference issue if the function returns NULL instead of an error pointer.  In reality, this doesn't cause any problems because iommu_sva_bind_device() only returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA. In this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will return an error, and the device drivers won't call iommu_sva_bind_device() at all.","status":"published","published":"2024-07-12T13:15:16.853Z","modified":"2026-11-02T12:02:57.870778759Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:43.156294Z"},{"id":"OESA-2024-1941","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\nclk: sunxi-ng: Unregister clocks/resets when unbinding\r\n\r\nCurrently, unbinding a CCU driver unmaps the device\u0026apos;s MMIO region, while\nleaving its clocks/resets and their providers registered. This can cause\na page fault later when some clock operation tries to perform MMIO. Fix\nthis by separating the CCU initialization from the memory allocation,\nand then using a devres callback to unregister the clocks and resets.\r\n\r\nThis also fixes a memory leak of the `struct ccu_reset`, and uses the\ncorrect owner (the specific platform driver) for the clocks and resets.\r\n\r\nEarly OF clock providers are never unregistered, and limited error\nhandling is possible, so they are mostly unchanged. The error reporting\nis made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nthermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR\r\n\r\nIn some case, the GDDV returns a package with a buffer which has\nzero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).\r\n\r\nThen the data_vault_read() got NULL point dereference problem when\naccessing the 0x10 value in data_vault.\r\n\r\n[   71.024560] BUG: kernel NULL pointer dereference, address:\n0000000000000010\r\n\r\nThis patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or\nNULL value in data_vault.(CVE-2022-48703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/smc: Avoid overwriting the copies of clcsock callback functions\r\n\r\nThe callback functions of clcsock will be saved and replaced during\nthe fallback. But if the fallback happens more than once, then the\ncopies of these callback functions will be overwritten incorrectly,\nresulting in a loop call issue:\r\n\r\nclcsk-\u0026gt;sk_error_report\n |- smc_fback_error_report() \u0026lt;------------------------------|\n     |- smc_fback_forward_wakeup()                          | (loop)\n         |- clcsock_callback()  (incorrectly overwritten)   |\n             |- smc-\u0026gt;clcsk_error_report() ------------------|\r\n\r\nSo this patch fixes the issue by saving these function pointers only\nonce in the fallback and avoiding overwriting.(CVE-2022-48780)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr\r\n\r\nThis node pointer is returned by of_find_compatible_node() with\nrefcount incremented. Calling of_node_put() to aovid the refcount leak.(CVE-2022-48859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: Fix double free in of_parse_phandle_with_args_map\r\n\r\nIn of_parse_phandle_with_args_map() the inner loop that\niterates through the map entries calls of_node_put(new)\nto free the reference acquired by the previous iteration\nof the inner loop. This assumes that the value of \u0026quot;new\u0026quot; is\nNULL on the first iteration of the inner loop.\r\n\r\nMake sure that this is true in all iterations of the outer\nloop by setting \u0026quot;new\u0026quot; to NULL after its value is assigned to \u0026quot;cur\u0026quot;.\r\n\r\nExtend the unittest to detect the double free and add an additional\ntest case that actually triggers this path.(CVE-2023-52679)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nft_set_pipapo: do not free live element\r\n\r\nPablo reports a crash with large batches of elements with a\nback-to-back add/remove pattern.  Quoting Pablo:\r\n\r\n  add_elem(\u0026quot;00000000\u0026quot;) timeout 100 ms\n  ...\n  add_elem(\u0026quot;0000000X\u0026quot;) timeout 100 ms\n  del_elem(\u0026quot;0000000X\u0026quot;) \u0026lt;---------------- delete one that was just added\n  ...\n  add_elem(\u0026quot;00005000\u0026quot;) timeout 100 ms\r\n\r\n  1) nft_pipapo_remove() removes element 0000000X\n  Then, KASAN shows a splat.\r\n\r\nLooking at the remove function there is a chance that we will drop a\nrule that maps to a non-deactivated element.\r\n\r\nRemoval happens in two steps, first we do a lookup for key k and return the\nto-be-removed element and mark it as inactive in the next generation.\nThen, in a second step, the element gets removed from the set/map.\r\n\r\nThe _remove function does not work correctly if we have more than one\nelement that share the same key.\r\n\r\nThis can happen if we insert an element into a set when the set already\nholds an element with same key, but the element mapping to the existing\nkey has timed out or is not active in the next generation.\r\n\r\nIn such case its possible that removal will unmap the wrong element.\nIf this happens, we will leak the non-deactivated element, it becomes\nunreachable.\r\n\r\nThe element that got deactivated (and will be freed later) will\nremain reachable in the set data structure, this can result in\na crash when such an element is retrieved during lookup (stale\npointer).\r\n\r\nAdd a check that the fully matching key does in fact map to the element\nthat we have marked as inactive in the deactivation step.\nIf not, we need to continue searching.\r\n\r\nAdd a bug/warn trap at the end of the function as well, the remove\nfunction must not ever be called with an invisible/unreachable/non-existent\nelement.\r\n\r\nv2: avoid uneeded temporary variable (Stefano)(CVE-2024-26924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: release mutex after nft_gc_seq_end from abort path\r\n\r\nThe commit mutex should not be released during the critical section\nbetween nft_gc_seq_begin() and nft_gc_seq_end(), otherwise, async GC\nworker could collect expired objects and get the released commit lock\nwithin the same GC sequence.\r\n\r\nnf_tables_module_autoload() temporarily releases the mutex to load\nmodule dependencies, then it goes back to replay the transaction again.\nMove it at the end of the abort phase after nft_gc_seq_end() is called.(CVE-2024-26925)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: Fix mirred deadlock on device recursion\r\n\r\nWhen the mirred action is used on a classful egress qdisc and a packet is\nmirrored or redirected to self we hit a qdisc lock deadlock.\nSee trace below.\r\n\r\n[..... other info removed for brevity....]\n[   82.890906]\n[   82.890906] ============================================\n[   82.890906] WARNING: possible recursive locking detected\n[   82.890906] 6.8.0-05205-g77fadd89fe2d-dirty #213 Tainted: G        W\n[   82.890906] --------------------------------------------\n[   82.890906] ping/418 is trying to acquire lock:\n[   82.890906] ffff888006994110 (\u0026amp;sch-\u0026gt;q.lock){+.-.}-{3:3}, at:\n__dev_queue_xmit+0x1778/0x3550\n[   82.890906]\n[   82.890906] but task is already holding lock:\n[   82.890906] ffff888006994110 (\u0026amp;sch-\u0026gt;q.lock){+.-.}-{3:3}, at:\n__dev_queue_xmit+0x1778/0x3550\n[   82.890906]\n[   82.890906] other info that might help us debug this:\n[   82.890906]  Possible unsafe locking scenario:\n[   82.890906]\n[   82.890906]        CPU0\n[   82.890906]        ----\n[   82.890906]   lock(\u0026amp;sch-\u0026gt;q.lock);\n[   82.890906]   lock(\u0026amp;sch-\u0026gt;q.lock);\n[   82.890906]\n[   82.890906]  *** DEADLOCK ***\n[   82.890906]\n[..... other info removed for brevity....]\r\n\r\nExample setup (eth0-\u0026gt;eth0) to recreate\ntc qdisc add dev eth0 root handle 1: htb default 30\ntc filter add dev eth0 handle 1: protocol ip prio 2 matchall \\\n     action mirred egress redirect dev eth0\r\n\r\nAnother example(eth0-\u0026gt;eth1-\u0026gt;eth0) to recreate\ntc qdisc add dev eth0 root handle 1: htb default 30\ntc filter add dev eth0 handle 1: protocol ip prio 2 matchall \\\n     action mirred egress redirect dev eth1\r\n\r\ntc qdisc add dev eth1 root handle 1: htb default 30\ntc filter add dev eth1 handle 1: protocol ip prio 2 matchall \\\n     action mirred egress redirect dev eth0\r\n\r\nWe fix this by adding an owner field (CPU id) to struct Qdisc set after\nroot qdisc is entered. When the softirq enters it a second time, if the\nqdisc owner is the same CPU, the packet is dropped to break the loop.(CVE-2024-27010)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-mapping: benchmark: fix node id validation\r\n\r\nWhile validating node ids in map_benchmark_ioctl(), node_possible() may\nbe provided with invalid argument outside of [0,MAX_NUMNODES-1] range\nleading to:\r\n\r\nBUG: KASAN: wild-memory-access in map_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nRead of size 8 at addr 1fffffff8ccb6398 by task dma_map_benchma/971\nCPU: 7 PID: 971 Comm: dma_map_benchma Not tainted 6.9.0-rc6 #37\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996)\nCall Trace:\n \u0026lt;TASK\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:117)\nkasan_report (mm/kasan/report.c:603)\nkasan_check_range (mm/kasan/generic.c:189)\nvariable_test_bit (arch/x86/include/asm/bitops.h:227) [inline]\narch_test_bit (arch/x86/include/asm/bitops.h:239) [inline]\n_test_bit at (include/asm-generic/bitops/instrumented-non-atomic.h:142) [inline]\nnode_state (include/linux/nodemask.h:423) [inline]\nmap_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nfull_proxy_unlocked_ioctl (fs/debugfs/file.c:333)\n__x64_sys_ioctl (fs/ioctl.c:890)\ndo_syscall_64 (arch/x86/entry/common.c:83)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nCompare node ids with sane bounds first. NUMA_NO_NODE is considered a\nspecial valid case meaning that benchmarking kthreads won\u0026apos;t be bound to a\ncpuset of a given node.\r\n\r\nFound by Linux Verification Center (linuxtesting.org).(CVE-2024-34777)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd/dm-raid: don\u0026apos;t call md_reap_sync_thread() directly\r\n\r\nCurrently md_reap_sync_thread() is called from raid_message() directly\nwithout holding \u0026apos;reconfig_mutex\u0026apos;, this is definitely unsafe because\nmd_reap_sync_thread() can change many fields that is protected by\n\u0026apos;reconfig_mutex\u0026apos;.\r\n\r\nHowever, hold \u0026apos;reconfig_mutex\u0026apos; here is still problematic because this\nwill cause deadlock, for example, commit 130443d60b1b (\u0026quot;md: refactor\nidle/frozen_sync_thread() to fix deadlock\u0026quot;).\r\n\r\nFix this problem by using stop_sync_thread() to unregister sync_thread,\nlike md/raid did.(CVE-2024-35808)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: mvpp2: clear BM pool before initialization\r\n\r\nRegister value persist after booting the kernel using\nkexec which results in kernel panic. Thus clear the\nBM pool registers before initialisation to fix the issue.(CVE-2024-35837)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: flush pending destroy work before exit_net release\r\n\r\nSimilar to 2c9f0293280e (\u0026quot;netfilter: nf_tables: flush pending destroy\nwork before netlink notifier\u0026quot;) to address a race between exit_net and\nthe destroy workqueue.\r\n\r\nThe trace below shows an element to be released via destroy workqueue\nwhile exit_net path (triggered via module removal) has already released\nthe set that is used in such transaction.\r\n\r\n[ 1360.547789] BUG: KASAN: slab-use-after-free in nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables]\n[ 1360.547861] Read of size 8 at addr ffff888140500cc0 by task kworker/4:1/152465\n[ 1360.547870] CPU: 4 PID: 152465 Comm: kworker/4:1 Not tainted 6.8.0+ #359\n[ 1360.547882] Workqueue: events nf_tables_trans_destroy_work [nf_tables]\n[ 1360.547984] Call Trace:\n[ 1360.547991]  \u0026lt;TASK\u0026gt;\n[ 1360.547998]  dump_stack_lvl+0x53/0x70\n[ 1360.548014]  print_report+0xc4/0x610\n[ 1360.548026]  ? __virt_addr_valid+0xba/0x160\n[ 1360.548040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[ 1360.548054]  ? nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables]\n[ 1360.548176]  kasan_report+0xae/0xe0\n[ 1360.548189]  ? nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables]\n[ 1360.548312]  nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables]\n[ 1360.548447]  ? __pfx_nf_tables_trans_destroy_work+0x10/0x10 [nf_tables]\n[ 1360.548577]  ? _raw_spin_unlock_irq+0x18/0x30\n[ 1360.548591]  process_one_work+0x2f1/0x670\n[ 1360.548610]  worker_thread+0x4d3/0x760\n[ 1360.548627]  ? __pfx_worker_thread+0x10/0x10\n[ 1360.548640]  kthread+0x16b/0x1b0\n[ 1360.548653]  ? __pfx_kthread+0x10/0x10\n[ 1360.548665]  ret_from_fork+0x2f/0x50\n[ 1360.548679]  ? __pfx_kthread+0x10/0x10\n[ 1360.548690]  ret_from_fork_asm+0x1a/0x30\n[ 1360.548707]  \u0026lt;/TASK\u0026gt;\r\n\r\n[ 1360.548719] Allocated by task 192061:\n[ 1360.548726]  kasan_save_stack+0x20/0x40\n[ 1360.548739]  kasan_save_track+0x14/0x30\n[ 1360.548750]  __kasan_kmalloc+0x8f/0xa0\n[ 1360.548760]  __kmalloc_node+0x1f1/0x450\n[ 1360.548771]  nf_tables_newset+0x10c7/0x1b50 [nf_tables]\n[ 1360.548883]  nfnetlink_rcv_batch+0xbc4/0xdc0 [nfnetlink]\n[ 1360.548909]  nfnetlink_rcv+0x1a8/0x1e0 [nfnetlink]\n[ 1360.548927]  netlink_unicast+0x367/0x4f0\n[ 1360.548935]  netlink_sendmsg+0x34b/0x610\n[ 1360.548944]  ____sys_sendmsg+0x4d4/0x510\n[ 1360.548953]  ___sys_sendmsg+0xc9/0x120\n[ 1360.548961]  __sys_sendmsg+0xbe/0x140\n[ 1360.548971]  do_syscall_64+0x55/0x120\n[ 1360.548982]  entry_SYSCALL_64_after_hwframe+0x55/0x5d\r\n\r\n[ 1360.548994] Freed by task 192222:\n[ 1360.548999]  kasan_save_stack+0x20/0x40\n[ 1360.549009]  kasan_save_track+0x14/0x30\n[ 1360.549019]  kasan_save_free_info+0x3b/0x60\n[ 1360.549028]  poison_slab_object+0x100/0x180\n[ 1360.549036]  __kasan_slab_free+0x14/0x30\n[ 1360.549042]  kfree+0xb6/0x260\n[ 1360.549049]  __nft_release_table+0x473/0x6a0 [nf_tables]\n[ 1360.549131]  nf_tables_exit_net+0x170/0x240 [nf_tables]\n[ 1360.549221]  ops_exit_list+0x50/0xa0\n[ 1360.549229]  free_exit_list+0x101/0x140\n[ 1360.549236]  unregister_pernet_operations+0x107/0x160\n[ 1360.549245]  unregister_pernet_subsys+0x1c/0x30\n[ 1360.549254]  nf_tables_module_exit+0x43/0x80 [nf_tables]\n[ 1360.549345]  __do_sys_delete_module+0x253/0x370\n[ 1360.549352]  do_syscall_64+0x55/0x120\n[ 1360.549360]  entry_SYSCALL_64_after_hwframe+0x55/0x5d\r\n\r\n(gdb) list *__nft_release_table+0x473\n0x1e033 is in __nft_release_table (net/netfilter/nf_tables_api.c:11354).\n11349           list_for_each_entry_safe(flowtable, nf, \u0026amp;table-\u0026gt;flowtables, list) {\n11350                   list_del(\u0026amp;flowtable-\u0026gt;list);\n11351                   nft_use_dec(\u0026amp;table-\u0026gt;use);\n11352                   nf_tables_flowtable_destroy(flowtable);\n11353           }\n11354           list_for_each_entry_safe(set, ns, \u0026amp;table-\u0026gt;sets, list) {\n11355                   list_del(\u0026amp;set-\u0026gt;list);\n11356                   nft_use_dec(\u0026amp;table-\u0026gt;use);\n11357                   if (set-\u0026gt;flags \u0026amp; (NFT_SET_MAP | NFT_SET_OBJECT))\n11358                           nft_map_deactivat\n---truncated---(CVE-2024-35899)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Skip do PCI error slot reset during RAS recovery\r\n\r\nWhy:\n    The PCI error slot reset maybe triggered after inject ue to UMC multi times, this\n    caused system hang.\n    [  557.371857] amdgpu 0000:af:00.0: amdgpu: GPU reset succeeded, trying to resume\n    [  557.373718] [drm] PCIE GART of 512M enabled.\n    [  557.373722] [drm] PTB located at 0x0000031FED700000\n    [  557.373788] [drm] VRAM is lost due to GPU reset!\n    [  557.373789] [drm] PSP is resuming...\n    [  557.547012] mlx5_core 0000:55:00.0: mlx5_pci_err_detected Device state = 1 pci_status: 0. Exit, result = 3, need reset\n    [  557.547067] [drm] PCI error: detected callback, state(1)!!\n    [  557.547069] [drm] No support for XGMI hive yet...\n    [  557.548125] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 0. Enter\n    [  557.607763] mlx5_core 0000:55:00.0: wait vital counter value 0x16b5b after 1 iterations\n    [  557.607777] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 1. Exit, err = 0, result = 5, recovered\n    [  557.610492] [drm] PCI error: slot reset callback!!\n    ...\n    [  560.689382] amdgpu 0000:3f:00.0: amdgpu: GPU reset(2) succeeded!\n    [  560.689546] amdgpu 0000:5a:00.0: amdgpu: GPU reset(2) succeeded!\n    [  560.689562] general protection fault, probably for non-canonical address 0x5f080b54534f611f: 0000 [#1] SMP NOPTI\n    [  560.701008] CPU: 16 PID: 2361 Comm: kworker/u448:9 Tainted: G           OE     5.15.0-91-generic #101-Ubuntu\n    [  560.712057] Hardware name: Microsoft C278A/C278A, BIOS C2789.5.BS.1C11.AG.1 11/08/2023\n    [  560.720959] Workqueue: amdgpu-reset-hive amdgpu_ras_do_recovery [amdgpu]\n    [  560.728887] RIP: 0010:amdgpu_device_gpu_recover.cold+0xbf1/0xcf5 [amdgpu]\n    [  560.736891] Code: ff 41 89 c6 e9 1b ff ff ff 44 0f b6 45 b0 e9 4f ff ff ff be 01 00 00 00 4c 89 e7 e8 76 c9 8b ff 44 0f b6 45 b0 e9 3c fd ff ff \u0026lt;48\u0026gt; 83 ba 18 02 00 00 00 0f 84 6a f8 ff ff 48 8d 7a 78 be 01 00 00\n    [  560.757967] RSP: 0018:ffa0000032e53d80 EFLAGS: 00010202\n    [  560.763848] RAX: ffa00000001dfd10 RBX: ffa0000000197090 RCX: ffa0000032e53db0\n    [  560.771856] RDX: 5f080b54534f5f07 RSI: 0000000000000000 RDI: ff11000128100010\n    [  560.779867] RBP: ffa0000032e53df0 R08: 0000000000000000 R09: ffffffffffe77f08\n    [  560.787879] R10: 0000000000ffff0a R11: 0000000000000001 R12: 0000000000000000\n    [  560.795889] R13: ffa0000032e53e00 R14: 0000000000000000 R15: 0000000000000000\n    [  560.803889] FS:  0000000000000000(0000) GS:ff11007e7e800000(0000) knlGS:0000000000000000\n    [  560.812973] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n    [  560.819422] CR2: 000055a04c118e68 CR3: 0000000007410005 CR4: 0000000000771ee0\n    [  560.827433] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n    [  560.835433] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n    [  560.843444] PKRU: 55555554\n    [  560.846480] Call Trace:\n    [  560.849225]  \u0026lt;TASK\u0026gt;\n    [  560.851580]  ? show_trace_log_lvl+0x1d6/0x2ea\n    [  560.856488]  ? show_trace_log_lvl+0x1d6/0x2ea\n    [  560.861379]  ? amdgpu_ras_do_recovery+0x1b2/0x210 [amdgpu]\n    [  560.867778]  ? show_regs.part.0+0x23/0x29\n    [  560.872293]  ? __die_body.cold+0x8/0xd\n    [  560.876502]  ? die_addr+0x3e/0x60\n    [  560.880238]  ? exc_general_protection+0x1c5/0x410\n    [  560.885532]  ? asm_exc_general_protection+0x27/0x30\n    [  560.891025]  ? amdgpu_device_gpu_recover.cold+0xbf1/0xcf5 [amdgpu]\n    [  560.898323]  amdgpu_ras_do_recovery+0x1b2/0x210 [amdgpu]\n    [  560.904520]  process_one_work+0x228/0x3d0\nHow:\n    In RAS recovery, mode-1 reset is issued from RAS fatal error handling and expected\n    all the nodes in a hive to be reset. no need to issue another mode-1 during this procedure.(CVE-2024-35931)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/9p: fix uninitialized values during inode evict\r\n\r\nIf an iget fails due to not being able to retrieve information\nfrom the server then the inode structure is only partially\ninitialized.  When the inode gets evicted, references to\nuninitialized structures (like fscache cookies) were being\nmade.\r\n\r\nThis patch checks for a bad_inode before doing anything other\nthan clearing the inode from the cache.  Since the inode is\nbad, it shouldn\u0026apos;t have any state associated with it that needs\nto be written back (and there really isn\u0026apos;t a way to complete\nthose anyways).(CVE-2024-36923)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential kernel bug due to lack of writeback flag waiting\r\n\r\nDestructive writes to a block device on which nilfs2 is mounted can cause\na kernel bug in the folio/page writeback start routine or writeback end\nroutine (__folio_start_writeback in the log below):\r\n\r\n kernel BUG at mm/page-writeback.c:3070!\n Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\n ...\n RIP: 0010:__folio_start_writeback+0xbaa/0x10e0\n Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff\n  e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 \u0026lt;0f\u0026gt;\n  0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00\n ...\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2]\n  nilfs_segctor_construct+0x181/0x6b0 [nilfs2]\n  nilfs_segctor_thread+0x548/0x11c0 [nilfs2]\n  kthread+0x2f0/0x390\n  ret_from_fork+0x4b/0x80\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\r\n\r\nThis is because when the log writer starts a writeback for segment summary\nblocks or a super root block that use the backing device\u0026apos;s page cache, it\ndoes not wait for the ongoing folio/page writeback, resulting in an\ninconsistent writeback state.\r\n\r\nFix this issue by waiting for ongoing writebacks when putting\nfolios/pages on the backing device into writeback state.(CVE-2024-37078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: bridge: cdns-mhdp8546: Fix possible null pointer dereference\r\n\r\nIn cdns_mhdp_atomic_enable(), the return value of drm_mode_duplicate() is\nassigned to mhdp_state-\u0026gt;current_mode, and there is a dereference of it in\ndrm_mode_set_name(), which will lead to a NULL pointer dereference on\nfailure of drm_mode_duplicate().\r\n\r\nFix this bug add a check of mhdp_state-\u0026gt;current_mode.(CVE-2024-38548)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: carl9170: add a proper sanity check for endpoints\r\n\r\nSyzkaller reports [1] hitting a warning which is caused by presence\nof a wrong endpoint type at the URB sumbitting stage. While there\nwas a check for a specific 4th endpoint, since it can switch types\nbetween bulk and interrupt, other endpoints are trusted implicitly.\nSimilar warning is triggered in a couple of other syzbot issues [2].\r\n\r\nFix the issue by doing a comprehensive check of all endpoints\ntaking into account difference between high- and full-speed\nconfiguration.\r\n\r\n[1] Syzkaller report:\n...\nWARNING: CPU: 0 PID: 4721 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n carl9170_usb_send_rx_irq_urb+0x273/0x340 drivers/net/wireless/ath/carl9170/usb.c:504\n carl9170_usb_init_device drivers/net/wireless/ath/carl9170/usb.c:939 [inline]\n carl9170_usb_firmware_finish drivers/net/wireless/ath/carl9170/usb.c:999 [inline]\n carl9170_usb_firmware_step2+0x175/0x240 drivers/net/wireless/ath/carl9170/usb.c:1028\n request_firmware_work_func+0x130/0x240 drivers/base/firmware_loader/main.c:1107\n process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289\n worker_thread+0x669/0x1090 kernel/workqueue.c:2436\n kthread+0x2e8/0x3a0 kernel/kthread.c:376\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308\n \u0026lt;/TASK\u0026gt;\r\n\r\n[2] Related syzkaller crashes:(CVE-2024-38567)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmacintosh/via-macii: Fix \u0026quot;BUG: sleeping function called from invalid context\u0026quot;\r\n\r\nThe via-macii ADB driver calls request_irq() after disabling hard\ninterrupts. But disabling interrupts isn\u0026apos;t necessary here because the\nVIA shift register interrupt was masked during VIA1 initialization.(CVE-2024-38607)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: i2c: et8ek8: Don\u0026apos;t strip remove function when driver is builtin\r\n\r\nUsing __exit for the remove function results in the remove callback\nbeing discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets\nunbound (e.g. using sysfs or hotplug), the driver is just removed\nwithout the cleanup being performed. This results in resource leaks. Fix\nit by compiling in the remove callback unconditionally.\r\n\r\nThis also fixes a W=1 modpost warning:\r\n\r\n\tWARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -\u0026gt; et8ek8_remove (section: .exit.text)(CVE-2024-38611)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: stk1160: fix bounds checking in stk1160_copy_video()\r\n\r\nThe subtract in this condition is reversed.  The -\u0026gt;length is the length\nof the buffer.  The -\u0026gt;bytesused is how many bytes we have copied thus\nfar.  When the condition is reversed that means the result of the\nsubtraction is always negative but since it\u0026apos;s unsigned then the result\nis a very high positive value.  That means the overflow check is never\ntrue.\r\n\r\nAdditionally, the -\u0026gt;bytesused doesn\u0026apos;t actually work for this purpose\nbecause we\u0026apos;re not writing to \u0026quot;buf-\u0026gt;mem + buf-\u0026gt;bytesused\u0026quot;.  Instead, the\nmath to calculate the destination where we are writing is a bit\ninvolved.  You calculate the number of full lines already written,\nmultiply by two, skip a line if necessary so that we start on an odd\nnumbered line, and add the offset into the line.\r\n\r\nTo fix this buffer overflow, just take the actual destination where we\nare writing, if the offset is already out of bounds print an error and\nreturn.  Otherwise, write up to buf-\u0026gt;length bytes.(CVE-2024-38621)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfbdev: savage: Handle err return when savagefb_check_var failed\r\n\r\nThe commit 04e5eac8f3ab(\u0026quot;fbdev: savage: Error out if pixclock equals zero\u0026quot;)\nchecks the value of pixclock to avoid divide-by-zero error. However\nthe function savagefb_probe doesn\u0026apos;t handle the error return of\nsavagefb_check_var. When pixclock is 0, it will cause divide-by-zero error.(CVE-2024-39475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING\r\n\r\nXiao reported that lvm2 test lvconvert-raid-takeover.sh can hang with\nsmall possibility, the root cause is exactly the same as commit\nbed9e27baf52 (\u0026quot;Revert \u0026quot;md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\u0026quot;\u0026quot;)\r\n\r\nHowever, Dan reported another hang after that, and junxiao investigated\nthe problem and found out that this is caused by plugged bio can\u0026apos;t issue\nfrom raid5d().\r\n\r\nCurrent implementation in raid5d() has a weird dependence:\r\n\r\n1) md_check_recovery() from raid5d() must hold \u0026apos;reconfig_mutex\u0026apos; to clear\n   MD_SB_CHANGE_PENDING;\n2) raid5d() handles IO in a deadloop, until all IO are issued;\n3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared;\r\n\r\nThis behaviour is introduce before v2.6, and for consequence, if other\ncontext hold \u0026apos;reconfig_mutex\u0026apos;, and md_check_recovery() can\u0026apos;t update\nsuper_block, then raid5d() will waste one cpu 100% by the deadloop, until\n\u0026apos;reconfig_mutex\u0026apos; is released.\r\n\r\nRefer to the implementation from raid1 and raid10, fix this problem by\nskipping issue IO if MD_SB_CHANGE_PENDING is still set after\nmd_check_recovery(), daemon thread will be woken up when \u0026apos;reconfig_mutex\u0026apos;\nis released. Meanwhile, the hang problem will be fixed as well.(CVE-2024-39476)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmmc: davinci: Don\u0026apos;t strip remove function when driver is builtin\r\n\r\nUsing __exit for the remove function results in the remove callback being\ndiscarded with CONFIG_MMC_DAVINCI=y. When such a device gets unbound (e.g.\nusing sysfs or hotplug), the driver is just removed without the cleanup\nbeing performed. This results in resource leaks. Fix it by compiling in the\nremove callback unconditionally.\r\n\r\nThis also fixes a W=1 modpost warning:\r\n\r\nWARNING: modpost: drivers/mmc/host/davinci_mmc: section mismatch in\nreference: davinci_mmcsd_driver+0x10 (section: .data) -\u0026gt;\ndavinci_mmcsd_remove (section: .exit.text)(CVE-2024-39484)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nliquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet\r\n\r\nIn lio_vf_rep_copy_packet() pg_info-\u0026gt;page is compared to a NULL value,\nbut then it is unconditionally passed to skb_add_rx_frag() which looks\nstrange and could lead to null pointer dereference.\r\n\r\nlio_vf_rep_copy_packet() call trace looks like:\n\tocteon_droq_process_packets\n\t octeon_droq_fast_process_packets\n\t  octeon_droq_dispatch_pkt\n\t   octeon_create_recv_info\n\t    ...search in the dispatch_list...\n\t     -\u0026gt;disp_fn(rdisp-\u0026gt;rinfo, ...)\n\t      lio_vf_rep_pkt_recv(struct octeon_recv_info *recv_info, ...)\nIn this path there is no code which sets pg_info-\u0026gt;page to NULL.\nSo this check looks unneeded and doesn\u0026apos;t solve potential problem.\nBut I guess the author had reason to add a check and I have no such card\nand can\u0026apos;t do real test.\nIn addition, the code in the function liquidio_push_packet() in\nliquidio/lio_core.c does exactly the same.\r\n\r\nBased on this, I consider the most acceptable compromise solution to\nadjust this issue by moving skb_add_rx_frag() into conditional scope.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-39506)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring/io-wq: Use set_bit() and test_bit() at worker-\u0026gt;flags\r\n\r\nUtilize set_bit() and test_bit() on worker-\u0026gt;flags within io_uring/io-wq\nto address potential data races.\r\n\r\nThe structure io_worker-\u0026gt;flags may be accessed through various data\npaths, leading to concurrency issues. When KCSAN is enabled, it reveals\ndata races occurring in io_worker_handle_work and\nio_wq_activate_free_worker functions.\r\n\r\n\t BUG: KCSAN: data-race in io_worker_handle_work / io_wq_activate_free_worker\n\t write to 0xffff8885c4246404 of 4 bytes by task 49071 on cpu 28:\n\t io_worker_handle_work (io_uring/io-wq.c:434 io_uring/io-wq.c:569)\n\t io_wq_worker (io_uring/io-wq.c:?)\n\u0026lt;snip\u0026gt;\r\n\r\n\t read to 0xffff8885c4246404 of 4 bytes by task 49024 on cpu 5:\n\t io_wq_activate_free_worker (io_uring/io-wq.c:? io_uring/io-wq.c:285)\n\t io_wq_enqueue (io_uring/io-wq.c:947)\n\t io_queue_iowq (io_uring/io_uring.c:524)\n\t io_req_task_submit (io_uring/io_uring.c:1511)\n\t io_handle_tw_list (io_uring/io_uring.c:1198)\n\u0026lt;snip\u0026gt;\r\n\r\nLine numbers against commit 18daea77cca6 (\u0026quot;Merge tag \u0026apos;for-linus\u0026apos; of\ngit://git.kernel.org/pub/scm/virt/kvm/kvm\u0026quot;).\r\n\r\nThese races involve writes and reads to the same memory location by\ndifferent tasks running on different CPUs. To mitigate this, refactor\nthe code to use atomic operations such as set_bit(), test_bit(), and\nclear_bit() instead of basic \u0026quot;and\u0026quot; and \u0026quot;or\u0026quot; operations. This ensures\nthread-safe manipulation of worker flags.\r\n\r\nAlso, move `create_index` to avoid holes in the structure.(CVE-2024-39508)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: rewrite __kernel_map_pages() to fix sleeping in invalid context\r\n\r\n__kernel_map_pages() is a debug function which clears the valid bit in page\ntable entry for deallocated pages to detect illegal memory accesses to\nfreed pages.\r\n\r\nThis function set/clear the valid bit using __set_memory(). __set_memory()\nacquires init_mm\u0026apos;s semaphore, and this operation may sleep. This is\nproblematic, because  __kernel_map_pages() can be called in atomic context,\nand thus is illegal to sleep. An example warning that this causes:\r\n\r\nBUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578\nin_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd\npreempt_count: 2, expected: 0\nCPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37\nHardware name: riscv-virtio,qemu (DT)\nCall Trace:\n[\u0026lt;ffffffff800060dc\u0026gt;] dump_backtrace+0x1c/0x24\n[\u0026lt;ffffffff8091ef6e\u0026gt;] show_stack+0x2c/0x38\n[\u0026lt;ffffffff8092baf8\u0026gt;] dump_stack_lvl+0x5a/0x72\n[\u0026lt;ffffffff8092bb24\u0026gt;] dump_stack+0x14/0x1c\n[\u0026lt;ffffffff8003b7ac\u0026gt;] __might_resched+0x104/0x10e\n[\u0026lt;ffffffff8003b7f4\u0026gt;] __might_sleep+0x3e/0x62\n[\u0026lt;ffffffff8093276a\u0026gt;] down_write+0x20/0x72\n[\u0026lt;ffffffff8000cf00\u0026gt;] __set_memory+0x82/0x2fa\n[\u0026lt;ffffffff8000d324\u0026gt;] __kernel_map_pages+0x5a/0xd4\n[\u0026lt;ffffffff80196cca\u0026gt;] __alloc_pages_bulk+0x3b2/0x43a\n[\u0026lt;ffffffff8018ee82\u0026gt;] __vmalloc_node_range+0x196/0x6ba\n[\u0026lt;ffffffff80011904\u0026gt;] copy_process+0x72c/0x17ec\n[\u0026lt;ffffffff80012ab4\u0026gt;] kernel_clone+0x60/0x2fe\n[\u0026lt;ffffffff80012f62\u0026gt;] kernel_thread+0x82/0xa0\n[\u0026lt;ffffffff8003552c\u0026gt;] kthreadd+0x14a/0x1be\n[\u0026lt;ffffffff809357de\u0026gt;] ret_from_fork+0xe/0x1c\r\n\r\nRewrite this function with apply_to_existing_page_range(). It is fine to\nnot have any locking, because __kernel_map_pages() works with pages being\nallocated/deallocated and those pages are not changed by anyone else in the\nmeantime.(CVE-2024-40915)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommu: Return right value in iommu_sva_bind_device()\r\n\r\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\r\n\r\nIn reality, this doesn\u0026apos;t cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won\u0026apos;t call iommu_sva_bind_device()\nat all.(CVE-2024-40945)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nima: Avoid blocking in RCU read-side critical section\r\n\r\nA panic happens in ima_match_policy:\r\n\r\nBUG: unable to handle kernel NULL pointer dereference at 0000000000000010\nPGD 42f873067 P4D 0\nOops: 0000 [#1] SMP NOPTI\nCPU: 5 PID: 1286325 Comm: kubeletmonit.sh\nKdump: loaded Tainted: P\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996),\n               BIOS 0.0.0 02/06/2015\nRIP: 0010:ima_match_policy+0x84/0x450\nCode: 49 89 fc 41 89 cf 31 ed 89 44 24 14 eb 1c 44 39\n      7b 18 74 26 41 83 ff 05 74 20 48 8b 1b 48 3b 1d\n      f2 b9 f4 00 0f 84 9c 01 00 00 \u0026lt;44\u0026gt; 85 73 10 74 ea\n      44 8b 6b 14 41 f6 c5 01 75 d4 41 f6 c5 02 74 0f\nRSP: 0018:ff71570009e07a80 EFLAGS: 00010207\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000200\nRDX: ffffffffad8dc7c0 RSI: 0000000024924925 RDI: ff3e27850dea2000\nRBP: 0000000000000000 R08: 0000000000000000 R09: ffffffffabfce739\nR10: ff3e27810cc42400 R11: 0000000000000000 R12: ff3e2781825ef970\nR13: 00000000ff3e2785 R14: 000000000000000c R15: 0000000000000001\nFS:  00007f5195b51740(0000)\nGS:ff3e278b12d40000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000010 CR3: 0000000626d24002 CR4: 0000000000361ee0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n ima_get_action+0x22/0x30\n process_measurement+0xb0/0x830\n ? page_add_file_rmap+0x15/0x170\n ? alloc_set_pte+0x269/0x4c0\n ? prep_new_page+0x81/0x140\n ? simple_xattr_get+0x75/0xa0\n ? selinux_file_open+0x9d/0xf0\n ima_file_check+0x64/0x90\n path_openat+0x571/0x1720\n do_filp_open+0x9b/0x110\n ? page_counter_try_charge+0x57/0xc0\n ? files_cgroup_alloc_fd+0x38/0x60\n ? __alloc_fd+0xd4/0x250\n ? do_sys_open+0x1bd/0x250\n do_sys_open+0x1bd/0x250\n do_syscall_64+0x5d/0x1d0\n entry_SYSCALL_64_after_hwframe+0x65/0xca\r\n\r\nCommit c7423dbdbc9e (\u0026quot;ima: Handle -ESTALE returned by\nima_filter_rule_match()\u0026quot;) introduced call to ima_lsm_copy_rule within a\nRCU read-side critical section which contains kmalloc with GFP_KERNEL.\nThis implies a possible sleep and violates limitations of RCU read-side\ncritical sections on non-PREEMPT systems.\r\n\r\nSleeping within RCU read-side critical section might cause\nsynchronize_rcu() returning early and break RCU protection, allowing a\nUAF to happen.\r\n\r\nThe root cause of this issue could be described as follows:\n|\tThread A\t|\tThread B\t|\n|\t\t\t|ima_match_policy\t|\n|\t\t\t|  rcu_read_lock\t|\n|ima_lsm_update_rule\t|\t\t\t|\n|  synchronize_rcu\t|\t\t\t|\n|\t\t\t|    kmalloc(GFP_KERNEL)|\n|\t\t\t|      sleep\t\t|\n==\u0026gt; synchronize_rcu returns early\n|  kfree(entry)\t\t|\t\t\t|\n|\t\t\t|    entry = entry-\u0026gt;next|\n==\u0026gt; UAF happens and entry now becomes NULL (or could be anything).\n|\t\t\t|    entry-\u0026gt;action\t|\n==\u0026gt; Accessing entry might cause panic.\r\n\r\nTo fix this issue, we are converting all kmalloc that is called within\nRCU read-side critical section to use GFP_ATOMIC.\r\n\r\n[PM: fixed missing comment, long lines, !CONFIG_IMA_LSM_RULES case](CVE-2024-40947)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list\r\n\r\nUse list_for_each_entry_safe() to allow iterating through the list and\ndeleting the entry in the iteration process. The descriptor is freed via\nidxd_desc_complete() and there\u0026apos;s a slight chance may cause issue for\nthe list iterator when the descriptor is reused by another thread\nwithout it being deleted from the list.(CVE-2024-40956)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: prevent possible NULL dereference in rt6_probe()\r\n\r\nsyzbot caught a NULL dereference in rt6_probe() [1]\r\n\r\nBail out if  __in6_dev_get() returns NULL.\r\n\r\n[1]\nOops: general protection fault, probably for non-canonical address 0xdffffc00000000cb: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000658-0x000000000000065f]\nCPU: 1 PID: 22444 Comm: syz-executor.0 Not tainted 6.10.0-rc2-syzkaller-00383-gb8481381d4e2 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\n RIP: 0010:rt6_probe net/ipv6/route.c:656 [inline]\n RIP: 0010:find_match+0x8c4/0xf50 net/ipv6/route.c:758\nCode: 14 fd f7 48 8b 85 38 ff ff ff 48 c7 45 b0 00 00 00 00 48 8d b8 5c 06 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 \u0026lt;0f\u0026gt; b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 19\nRSP: 0018:ffffc900034af070 EFLAGS: 00010203\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffc90004521000\nRDX: 00000000000000cb RSI: ffffffff8990d0cd RDI: 000000000000065c\nRBP: ffffc900034af150 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000000000001 R11: 0000000000000002 R12: 000000000000000a\nR13: 1ffff92000695e18 R14: ffff8880244a1d20 R15: 0000000000000000\nFS:  00007f4844a5a6c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000001b31b27000 CR3: 000000002d42c000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  rt6_nh_find_match+0xfa/0x1a0 net/ipv6/route.c:784\n  nexthop_for_each_fib6_nh+0x26d/0x4a0 net/ipv4/nexthop.c:1496\n  __find_rr_leaf+0x6e7/0xe00 net/ipv6/route.c:825\n  find_rr_leaf net/ipv6/route.c:853 [inline]\n  rt6_select net/ipv6/route.c:897 [inline]\n  fib6_table_lookup+0x57e/0xa30 net/ipv6/route.c:2195\n  ip6_pol_route+0x1cd/0x1150 net/ipv6/route.c:2231\n  pol_lookup_func include/net/ip6_fib.h:616 [inline]\n  fib6_rule_lookup+0x386/0x720 net/ipv6/fib6_rules.c:121\n  ip6_route_output_flags_noref net/ipv6/route.c:2639 [inline]\n  ip6_route_output_flags+0x1d0/0x640 net/ipv6/route.c:2651\n  ip6_dst_lookup_tail.constprop.0+0x961/0x1760 net/ipv6/ip6_output.c:1147\n  ip6_dst_lookup_flow+0x99/0x1d0 net/ipv6/ip6_output.c:1250\n  rawv6_sendmsg+0xdab/0x4340 net/ipv6/raw.c:898\n  inet_sendmsg+0x119/0x140 net/ipv4/af_inet.c:853\n  sock_sendmsg_nosec net/socket.c:730 [inline]\n  __sock_sendmsg net/socket.c:745 [inline]\n  sock_write_iter+0x4b8/0x5c0 net/socket.c:1160\n  new_sync_write fs/read_write.c:497 [inline]\n  vfs_write+0x6b6/0x1140 fs/read_write.c:590\n  ksys_write+0x1f8/0x260 fs/read_write.c:643\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-40960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: imx: Introduce timeout when waiting on transmitter empty\r\n\r\nBy waiting at most 1 second for USR2_TXDC to be set, we avoid a potential\ndeadlock.\r\n\r\nIn case of the timeout, there is not much we can do, so we simply ignore\nthe transmitter state and optimistically try to continue.(CVE-2024-40967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: do not create EA inode under buffer lock\r\n\r\next4_xattr_set_entry() creates new EA inodes while holding buffer lock\non the external xattr block. This is problematic as it nests all the\nallocation locking (which acquires locks on other buffers) under the\nbuffer lock. This can even deadlock when the filesystem is corrupted and\ne.g. quota file is setup to contain xattr block as data block. Move the\nallocation of EA inode out of ext4_xattr_set_entry() into the callers.(CVE-2024-40972)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrop_monitor: replace spin_lock by raw_spin_lock\r\n\r\ntrace_drop_common() is called with preemption disabled, and it acquires\na spin_lock. This is problematic for RT kernels because spin_locks are\nsleeping locks in this configuration, which causes the following splat:\r\n\r\nBUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\nin_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 449, name: rcuc/47\npreempt_count: 1, expected: 0\nRCU nest depth: 2, expected: 2\n5 locks held by rcuc/47/449:\n #0: ff1100086ec30a60 ((softirq_ctrl.lock)){+.+.}-{2:2}, at: __local_bh_disable_ip+0x105/0x210\n #1: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: rt_spin_lock+0xbf/0x130\n #2: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: __local_bh_disable_ip+0x11c/0x210\n #3: ffffffffb394a160 (rcu_callback){....}-{0:0}, at: rcu_do_batch+0x360/0xc70\n #4: ff1100086ee07520 (\u0026amp;data-\u0026gt;lock){+.+.}-{2:2}, at: trace_drop_common.constprop.0+0xb5/0x290\nirq event stamp: 139909\nhardirqs last  enabled at (139908): [\u0026lt;ffffffffb1df2b33\u0026gt;] _raw_spin_unlock_irqrestore+0x63/0x80\nhardirqs last disabled at (139909): [\u0026lt;ffffffffb19bd03d\u0026gt;] trace_drop_common.constprop.0+0x26d/0x290\nsoftirqs last  enabled at (139892): [\u0026lt;ffffffffb07a1083\u0026gt;] __local_bh_enable_ip+0x103/0x170\nsoftirqs last disabled at (139898): [\u0026lt;ffffffffb0909b33\u0026gt;] rcu_cpu_kthread+0x93/0x1f0\nPreemption disabled at:\n[\u0026lt;ffffffffb1de786b\u0026gt;] rt_mutex_slowunlock+0xab/0x2e0\nCPU: 47 PID: 449 Comm: rcuc/47 Not tainted 6.9.0-rc2-rt1+ #7\nHardware name: Dell Inc. PowerEdge R650/0Y2G81, BIOS 1.6.5 04/15/2022\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x8c/0xd0\n dump_stack+0x14/0x20\n __might_resched+0x21e/0x2f0\n rt_spin_lock+0x5e/0x130\n ? trace_drop_common.constprop.0+0xb5/0x290\n ? skb_queue_purge_reason.part.0+0x1bf/0x230\n trace_drop_common.constprop.0+0xb5/0x290\n ? preempt_count_sub+0x1c/0xd0\n ? _raw_spin_unlock_irqrestore+0x4a/0x80\n ? __pfx_trace_drop_common.constprop.0+0x10/0x10\n ? rt_mutex_slowunlock+0x26a/0x2e0\n ? skb_queue_purge_reason.part.0+0x1bf/0x230\n ? __pfx_rt_mutex_slowunlock+0x10/0x10\n ? skb_queue_purge_reason.part.0+0x1bf/0x230\n trace_kfree_skb_hit+0x15/0x20\n trace_kfree_skb+0xe9/0x150\n kfree_skb_reason+0x7b/0x110\n skb_queue_purge_reason.part.0+0x1bf/0x230\n ? __pfx_skb_queue_purge_reason.part.0+0x10/0x10\n ? mark_lock.part.0+0x8a/0x520\n...\r\n\r\ntrace_drop_common() also disables interrupts, but this is a minor issue\nbecause we could easily replace it with a local_lock.\r\n\r\nReplace the spin_lock with raw_spin_lock to avoid sleeping in atomic\ncontext.(CVE-2024-40980)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbatman-adv: bypass empty buckets in batadv_purge_orig_ref()\r\n\r\nMany syzbot reports are pointing to soft lockups in\nbatadv_purge_orig_ref() [1]\r\n\r\nRoot cause is unknown, but we can avoid spending too much\ntime there and perhaps get more interesting reports.\r\n\r\n[1]\r\n\r\nwatchdog: BUG: soft lockup - CPU#0 stuck for 27s! [kworker/u4:6:621]\nModules linked in:\nirq event stamp: 6182794\n hardirqs last  enabled at (6182793): [\u0026lt;ffff8000801dae10\u0026gt;] __local_bh_enable_ip+0x224/0x44c kernel/softirq.c:386\n hardirqs last disabled at (6182794): [\u0026lt;ffff80008ad66a78\u0026gt;] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline]\n hardirqs last disabled at (6182794): [\u0026lt;ffff80008ad66a78\u0026gt;] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551\n softirqs last  enabled at (6182792): [\u0026lt;ffff80008aab71c4\u0026gt;] spin_unlock_bh include/linux/spinlock.h:396 [inline]\n softirqs last  enabled at (6182792): [\u0026lt;ffff80008aab71c4\u0026gt;] batadv_purge_orig_ref+0x114c/0x1228 net/batman-adv/originator.c:1287\n softirqs last disabled at (6182790): [\u0026lt;ffff80008aab61dc\u0026gt;] spin_lock_bh include/linux/spinlock.h:356 [inline]\n softirqs last disabled at (6182790): [\u0026lt;ffff80008aab61dc\u0026gt;] batadv_purge_orig_ref+0x164/0x1228 net/batman-adv/originator.c:1271\nCPU: 0 PID: 621 Comm: kworker/u4:6 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024\nWorkqueue: bat_events batadv_purge_orig\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : should_resched arch/arm64/include/asm/preempt.h:79 [inline]\n pc : __local_bh_enable_ip+0x228/0x44c kernel/softirq.c:388\n lr : __local_bh_enable_ip+0x224/0x44c kernel/softirq.c:386\nsp : ffff800099007970\nx29: ffff800099007980 x28: 1fffe00018fce1bd x27: dfff800000000000\nx26: ffff0000d2620008 x25: ffff0000c7e70de8 x24: 0000000000000001\nx23: 1fffe00018e57781 x22: dfff800000000000 x21: ffff80008aab71c4\nx20: ffff0001b40136c0 x19: ffff0000c72bbc08 x18: 1fffe0001a817bb0\nx17: ffff800125414000 x16: ffff80008032116c x15: 0000000000000001\nx14: 1fffe0001ee9d610 x13: 0000000000000000 x12: 0000000000000003\nx11: 0000000000000000 x10: 0000000000ff0100 x9 : 0000000000000000\nx8 : 00000000005e5789 x7 : ffff80008aab61dc x6 : 0000000000000000\nx5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000\nx2 : 0000000000000006 x1 : 0000000000000080 x0 : ffff800125414000\nCall trace:\n  __daif_local_irq_enable arch/arm64/include/asm/irqflags.h:27 [inline]\n  arch_local_irq_enable arch/arm64/include/asm/irqflags.h:49 [inline]\n  __local_bh_enable_ip+0x228/0x44c kernel/softirq.c:386\n  __raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n  _raw_spin_unlock_bh+0x3c/0x4c kernel/locking/spinlock.c:210\n  spin_unlock_bh include/linux/spinlock.h:396 [inline]\n  batadv_purge_orig_ref+0x114c/0x1228 net/batman-adv/originator.c:1287\n  batadv_purge_orig+0x20/0x70 net/batman-adv/originator.c:1300\n  process_one_work+0x694/0x1204 kernel/workqueue.c:2633\n  process_scheduled_works kernel/workqueue.c:2706 [inline]\n  worker_thread+0x938/0xef4 kernel/workqueue.c:2787\n  kthread+0x288/0x310 kernel/kthread.c:388\n  ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860\nSending NMI from CPU 0 to CPUs 1:\nNMI backtrace for cpu 1\nCPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : arch_local_irq_enable+0x8/0xc arch/arm64/include/asm/irqflags.h:51\n lr : default_idle_call+0xf8/0x128 kernel/sched/idle.c:103\nsp : ffff800093a17d30\nx29: ffff800093a17d30 x28: dfff800000000000 x27: 1ffff00012742fb4\nx26: ffff80008ec9d000 x25: 0000000000000000 x24: 0000000000000002\nx23: 1ffff00011d93a74 x22: ffff80008ec9d3a0 x21: 0000000000000000\nx20: ffff0000c19dbc00 x19: ffff8000802d0fd8 x18: 1fffe00036804396\nx17: ffff80008ec9d000 x16: ffff8000802d089c x15: 0000000000000001\n---truncated---(CVE-2024-40981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc()\r\n\r\nsyzbot found hanging tasks waiting on rtnl_lock [1]\r\n\r\nA reproducer is available in the syzbot bug.\r\n\r\nWhen a request to add multiple actions with the same index is sent, the\nsecond request will block forever on the first request. This holds\nrtnl_lock, and causes tasks to hang.\r\n\r\nReturn -EAGAIN to prevent infinite looping, while keeping documented\nbehavior.\r\n\r\n[1]\r\n\r\nINFO: task kworker/1:0:5088 blocked for more than 143 seconds.\nNot tainted 6.9.0-rc4-syzkaller-00173-g3cdb45594619 #0\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/1:0 state:D stack:23744 pid:5088 tgid:5088 ppid:2 flags:0x00004000\nWorkqueue: events_power_efficient reg_check_chans_work\nCall Trace:\n\u0026lt;TASK\u0026gt;\ncontext_switch kernel/sched/core.c:5409 [inline]\n__schedule+0xf15/0x5d00 kernel/sched/core.c:6746\n__schedule_loop kernel/sched/core.c:6823 [inline]\nschedule+0xe7/0x350 kernel/sched/core.c:6838\nschedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6895\n__mutex_lock_common kernel/locking/mutex.c:684 [inline]\n__mutex_lock+0x5b8/0x9c0 kernel/locking/mutex.c:752\nwiphy_lock include/net/cfg80211.h:5953 [inline]\nreg_leave_invalid_chans net/wireless/reg.c:2466 [inline]\nreg_check_chans_work+0x10a/0x10e0 net/wireless/reg.c:2481(CVE-2024-40995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdkfd: don\u0026apos;t allow mapping the MMIO HDP page with large pages\r\n\r\nWe don\u0026apos;t get the right offset in that case.  The GPU has\nan unused 4K area of the register BAR space into which you can\nremap registers.  We remap the HDP flush registers into this\nspace to allow userspace (CPU or GPU) to flush the HDP when it\nupdates VRAM.  However, on systems with \u0026gt;4K pages, we end up\nexposing PAGE_SIZE of MMIO space.(CVE-2024-41011)","status":"published","published":"2024-08-02T11:07:24Z","modified":"2026-08-18T01:18:33.367302505Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-1942","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\nclk: sunxi-ng: Unregister clocks/resets when unbinding\r\n\r\nCurrently, unbinding a CCU driver unmaps the device\u0026apos;s MMIO region, while\nleaving its clocks/resets and their providers registered. This can cause\na page fault later when some clock operation tries to perform MMIO. Fix\nthis by separating the CCU initialization from the memory allocation,\nand then using a devres callback to unregister the clocks and resets.\r\n\r\nThis also fixes a memory leak of the `struct ccu_reset`, and uses the\ncorrect owner (the specific platform driver) for the clocks and resets.\r\n\r\nEarly OF clock providers are never unregistered, and limited error\nhandling is possible, so they are mostly unchanged. The error reporting\nis made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nthermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR\r\n\r\nIn some case, the GDDV returns a package with a buffer which has\nzero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).\r\n\r\nThen the data_vault_read() got NULL point dereference problem when\naccessing the 0x10 value in data_vault.\r\n\r\n[   71.024560] BUG: kernel NULL pointer dereference, address:\n0000000000000010\r\n\r\nThis patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or\nNULL value in data_vault.(CVE-2022-48703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr\r\n\r\nThis node pointer is returned by of_find_compatible_node() with\nrefcount incremented. Calling of_node_put() to aovid the refcount leak.(CVE-2022-48859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: Fix double free in of_parse_phandle_with_args_map\r\n\r\nIn of_parse_phandle_with_args_map() the inner loop that\niterates through the map entries calls of_node_put(new)\nto free the reference acquired by the previous iteration\nof the inner loop. This assumes that the value of \u0026quot;new\u0026quot; is\nNULL on the first iteration of the inner loop.\r\n\r\nMake sure that this is true in all iterations of the outer\nloop by setting \u0026quot;new\u0026quot; to NULL after its value is assigned to \u0026quot;cur\u0026quot;.\r\n\r\nExtend the unittest to detect the double free and add an additional\ntest case that actually triggers this path.(CVE-2023-52679)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: gspca: cpia1: shift-out-of-bounds in set_flicker\r\n\r\nSyzkaller reported the following issue:\nUBSAN: shift-out-of-bounds in drivers/media/usb/gspca/cpia1.c:1031:27\nshift exponent 245 is too large for 32-bit type \u0026apos;int\u0026apos;\r\n\r\nWhen the value of the variable \u0026quot;sd-\u0026gt;params.exposure.gain\u0026quot; exceeds the\nnumber of bits in an integer, a shift-out-of-bounds error is reported. It\nis triggered because the variable \u0026quot;currentexp\u0026quot; cannot be left-shifted by\nmore than the number of bits in an integer. In order to avoid invalid\nrange during left-shift, the conditional expression is added.(CVE-2023-52764)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ninit/main.c: Fix potential static_command_line memory overflow\r\n\r\nWe allocate memory of size \u0026apos;xlen + strlen(boot_command_line) + 1\u0026apos; for\nstatic_command_line, but the strings copied into static_command_line are\nextra_command_line and command_line, rather than extra_command_line and\nboot_command_line.\r\n\r\nWhen strlen(command_line) \u0026gt; strlen(boot_command_line), static_command_line\nwill overflow.\r\n\r\nThis patch just recovers strlen(command_line) which was miss-consolidated\nwith strlen(boot_command_line) in the commit f5c7310ac73e (\u0026quot;init/main: add\nchecks for the return value of memblock_alloc*()\u0026quot;)(CVE-2024-26988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: restore set elements when delete set fails\r\n\r\nFrom abort path, nft_mapelem_activate() needs to restore refcounters to\nthe original state. Currently, it uses the set-\u0026gt;ops-\u0026gt;walk() to iterate\nover these set elements. The existing set iterator skips inactive\nelements in the next generation, this does not work from the abort path\nto restore the original state since it has to skip active elements\ninstead (not inactive ones).\r\n\r\nThis patch moves the check for inactive elements to the set iterator\ncallback, then it reverses the logic for the .activate case which\nneeds to skip active elements.\r\n\r\nToggle next generation bit for elements when delete set command is\ninvoked and call nft_clear() from .activate (abort) path to restore the\nnext generation bit.\r\n\r\nThe splat below shows an object in mappings memleak:\r\n\r\n[43929.457523] ------------[ cut here ]------------\n[43929.457532] WARNING: CPU: 0 PID: 1139 at include/net/netfilter/nf_tables.h:1237 nft_setelem_data_deactivate+0xe4/0xf0 [nf_tables]\n[...]\n[43929.458014] RIP: 0010:nft_setelem_data_deactivate+0xe4/0xf0 [nf_tables]\n[43929.458076] Code: 83 f8 01 77 ab 49 8d 7c 24 08 e8 37 5e d0 de 49 8b 6c 24 08 48 8d 7d 50 e8 e9 5c d0 de 8b 45 50 8d 50 ff 89 55 50 85 c0 75 86 \u0026lt;0f\u0026gt; 0b eb 82 0f 0b eb b3 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90\n[43929.458081] RSP: 0018:ffff888140f9f4b0 EFLAGS: 00010246\n[43929.458086] RAX: 0000000000000000 RBX: ffff8881434f5288 RCX: dffffc0000000000\n[43929.458090] RDX: 00000000ffffffff RSI: ffffffffa26d28a7 RDI: ffff88810ecc9550\n[43929.458093] RBP: ffff88810ecc9500 R08: 0000000000000001 R09: ffffed10281f3e8f\n[43929.458096] R10: 0000000000000003 R11: ffff0000ffff0000 R12: ffff8881434f52a0\n[43929.458100] R13: ffff888140f9f5f4 R14: ffff888151c7a800 R15: 0000000000000002\n[43929.458103] FS:  00007f0c687c4740(0000) GS:ffff888390800000(0000) knlGS:0000000000000000\n[43929.458107] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[43929.458111] CR2: 00007f58dbe5b008 CR3: 0000000123602005 CR4: 00000000001706f0\n[43929.458114] Call Trace:\n[43929.458118]  \u0026lt;TASK\u0026gt;\n[43929.458121]  ? __warn+0x9f/0x1a0\n[43929.458127]  ? nft_setelem_data_deactivate+0xe4/0xf0 [nf_tables]\n[43929.458188]  ? report_bug+0x1b1/0x1e0\n[43929.458196]  ? handle_bug+0x3c/0x70\n[43929.458200]  ? exc_invalid_op+0x17/0x40\n[43929.458211]  ? nft_setelem_data_deactivate+0xd7/0xf0 [nf_tables]\n[43929.458271]  ? nft_setelem_data_deactivate+0xe4/0xf0 [nf_tables]\n[43929.458332]  nft_mapelem_deactivate+0x24/0x30 [nf_tables]\n[43929.458392]  nft_rhash_walk+0xdd/0x180 [nf_tables]\n[43929.458453]  ? __pfx_nft_rhash_walk+0x10/0x10 [nf_tables]\n[43929.458512]  ? rb_insert_color+0x2e/0x280\n[43929.458520]  nft_map_deactivate+0xdc/0x1e0 [nf_tables]\n[43929.458582]  ? __pfx_nft_map_deactivate+0x10/0x10 [nf_tables]\n[43929.458642]  ? __pfx_nft_mapelem_deactivate+0x10/0x10 [nf_tables]\n[43929.458701]  ? __rcu_read_unlock+0x46/0x70\n[43929.458709]  nft_delset+0xff/0x110 [nf_tables]\n[43929.458769]  nft_flush_table+0x16f/0x460 [nf_tables]\n[43929.458830]  nf_tables_deltable+0x501/0x580 [nf_tables](CVE-2024-27012)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to avoid potential panic during recovery\r\n\r\nDuring recovery, if FAULT_BLOCK is on, it is possible that\nf2fs_reserve_new_block() will return -ENOSPC during recovery,\nthen it may trigger panic.\r\n\r\nAlso, if fault injection rate is 1 and only FAULT_BLOCK fault\ntype is on, it may encounter deadloop in loop of block reservation.\r\n\r\nLet\u0026apos;s change as below to fix these issues:\n- remove bug_on() to avoid panic.\n- limit the loop count of block reservation to avoid potential\ndeadloop.(CVE-2024-27032)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nclk: Fix clk_core_get NULL dereference\r\n\r\nIt is possible for clk_core_get to dereference a NULL in the following\nsequence:\r\n\r\nclk_core_get()\n    of_clk_get_hw_from_clkspec()\n        __of_clk_get_hw_from_provider()\n            __clk_get_hw()\r\n\r\n__clk_get_hw() can return NULL which is dereferenced by clk_core_get() at\nhw-\u0026gt;core.\r\n\r\nPrior to commit dde4eff47c82 (\u0026quot;clk: Look for parents with clkdev based\nclk_lookups\u0026quot;) the check IS_ERR_OR_NULL() was performed which would have\ncaught the NULL.\r\n\r\nReading the description of this function it talks about returning NULL but\nthat cannot be so at the moment.\r\n\r\nUpdate the function to check for hw before dereferencing it and return NULL\nif hw is NULL.(CVE-2024-27038)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: phy: fix phy_get_internal_delay accessing an empty array\r\n\r\nThe phy_get_internal_delay function could try to access to an empty\narray in the case that the driver is calling phy_get_internal_delay\nwithout defining delay_values and rx-internal-delay-ps or\ntx-internal-delay-ps is defined to 0 in the device-tree.\nThis will lead to \u0026quot;unable to handle kernel NULL pointer dereference at\nvirtual address 0\u0026quot;. To avoid this kernel oops, the test should be delay\n\u0026gt;= 0. As there is already delay \u0026lt; 0 test just before, the test could\nonly be size == 0.(CVE-2024-27047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work\r\n\r\nThe workqueue might still be running, when the driver is stopped. To\navoid a use-after-free, call cancel_work_sync() in rtl8xxxu_stop().(CVE-2024-27052)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: do not compare internal table flags on updates\r\n\r\nRestore skipping transaction if table update does not modify flags.(CVE-2024-27065)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npower: supply: bq27xxx-i2c: Do not free non existing IRQ\r\n\r\nThe bq27xxx i2c-client may not have an IRQ, in which case\nclient-\u0026gt;irq will be 0. bq27xxx_battery_i2c_probe() already has\nan if (client-\u0026gt;irq) check wrapping the request_threaded_irq().\r\n\r\nBut bq27xxx_battery_i2c_remove() unconditionally calls\nfree_irq(client-\u0026gt;irq) leading to:\r\n\r\n[  190.310742] ------------[ cut here ]------------\n[  190.310843] Trying to free already-free IRQ 0\n[  190.310861] WARNING: CPU: 2 PID: 1304 at kernel/irq/manage.c:1893 free_irq+0x1b8/0x310\r\n\r\nFollowed by a backtrace when unbinding the driver. Add\nan if (client-\u0026gt;irq) to bq27xxx_battery_i2c_remove() mirroring\nprobe() to fix this.(CVE-2024-27412)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST\r\n\r\nIf we received HCI_EV_IO_CAPA_REQUEST while\nHCI_OP_READ_REMOTE_EXT_FEATURES is yet to be responded assume the remote\ndoes support SSP since otherwise this event shouldn\u0026apos;t be generated.(CVE-2024-27416)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-mapping: benchmark: fix node id validation\r\n\r\nWhile validating node ids in map_benchmark_ioctl(), node_possible() may\nbe provided with invalid argument outside of [0,MAX_NUMNODES-1] range\nleading to:\r\n\r\nBUG: KASAN: wild-memory-access in map_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nRead of size 8 at addr 1fffffff8ccb6398 by task dma_map_benchma/971\nCPU: 7 PID: 971 Comm: dma_map_benchma Not tainted 6.9.0-rc6 #37\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996)\nCall Trace:\n \u0026lt;TASK\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:117)\nkasan_report (mm/kasan/report.c:603)\nkasan_check_range (mm/kasan/generic.c:189)\nvariable_test_bit (arch/x86/include/asm/bitops.h:227) [inline]\narch_test_bit (arch/x86/include/asm/bitops.h:239) [inline]\n_test_bit at (include/asm-generic/bitops/instrumented-non-atomic.h:142) [inline]\nnode_state (include/linux/nodemask.h:423) [inline]\nmap_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nfull_proxy_unlocked_ioctl (fs/debugfs/file.c:333)\n__x64_sys_ioctl (fs/ioctl.c:890)\ndo_syscall_64 (arch/x86/entry/common.c:83)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nCompare node ids with sane bounds first. NUMA_NO_NODE is considered a\nspecial valid case meaning that benchmarking kthreads won\u0026apos;t be bound to a\ncpuset of a given node.\r\n\r\nFound by Linux Verification Center (linuxtesting.org).(CVE-2024-34777)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: mvpp2: clear BM pool before initialization\r\n\r\nRegister value persist after booting the kernel using\nkexec which results in kernel panic. Thus clear the\nBM pool registers before initialisation to fix the issue.(CVE-2024-35837)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Skip do PCI error slot reset during RAS recovery\r\n\r\nWhy:\n    The PCI error slot reset maybe triggered after inject ue to UMC multi times, this\n    caused system hang.\n    [  557.371857] amdgpu 0000:af:00.0: amdgpu: GPU reset succeeded, trying to resume\n    [  557.373718] [drm] PCIE GART of 512M enabled.\n    [  557.373722] [drm] PTB located at 0x0000031FED700000\n    [  557.373788] [drm] VRAM is lost due to GPU reset!\n    [  557.373789] [drm] PSP is resuming...\n    [  557.547012] mlx5_core 0000:55:00.0: mlx5_pci_err_detected Device state = 1 pci_status: 0. Exit, result = 3, need reset\n    [  557.547067] [drm] PCI error: detected callback, state(1)!!\n    [  557.547069] [drm] No support for XGMI hive yet...\n    [  557.548125] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 0. Enter\n    [  557.607763] mlx5_core 0000:55:00.0: wait vital counter value 0x16b5b after 1 iterations\n    [  557.607777] mlx5_core 0000:55:00.0: mlx5_pci_slot_reset Device state = 1 pci_status: 1. Exit, err = 0, result = 5, recovered\n    [  557.610492] [drm] PCI error: slot reset callback!!\n    ...\n    [  560.689382] amdgpu 0000:3f:00.0: amdgpu: GPU reset(2) succeeded!\n    [  560.689546] amdgpu 0000:5a:00.0: amdgpu: GPU reset(2) succeeded!\n    [  560.689562] general protection fault, probably for non-canonical address 0x5f080b54534f611f: 0000 [#1] SMP NOPTI\n    [  560.701008] CPU: 16 PID: 2361 Comm: kworker/u448:9 Tainted: G           OE     5.15.0-91-generic #101-Ubuntu\n    [  560.712057] Hardware name: Microsoft C278A/C278A, BIOS C2789.5.BS.1C11.AG.1 11/08/2023\n    [  560.720959] Workqueue: amdgpu-reset-hive amdgpu_ras_do_recovery [amdgpu]\n    [  560.728887] RIP: 0010:amdgpu_device_gpu_recover.cold+0xbf1/0xcf5 [amdgpu]\n    [  560.736891] Code: ff 41 89 c6 e9 1b ff ff ff 44 0f b6 45 b0 e9 4f ff ff ff be 01 00 00 00 4c 89 e7 e8 76 c9 8b ff 44 0f b6 45 b0 e9 3c fd ff ff \u0026lt;48\u0026gt; 83 ba 18 02 00 00 00 0f 84 6a f8 ff ff 48 8d 7a 78 be 01 00 00\n    [  560.757967] RSP: 0018:ffa0000032e53d80 EFLAGS: 00010202\n    [  560.763848] RAX: ffa00000001dfd10 RBX: ffa0000000197090 RCX: ffa0000032e53db0\n    [  560.771856] RDX: 5f080b54534f5f07 RSI: 0000000000000000 RDI: ff11000128100010\n    [  560.779867] RBP: ffa0000032e53df0 R08: 0000000000000000 R09: ffffffffffe77f08\n    [  560.787879] R10: 0000000000ffff0a R11: 0000000000000001 R12: 0000000000000000\n    [  560.795889] R13: ffa0000032e53e00 R14: 0000000000000000 R15: 0000000000000000\n    [  560.803889] FS:  0000000000000000(0000) GS:ff11007e7e800000(0000) knlGS:0000000000000000\n    [  560.812973] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n    [  560.819422] CR2: 000055a04c118e68 CR3: 0000000007410005 CR4: 0000000000771ee0\n    [  560.827433] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n    [  560.835433] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n    [  560.843444] PKRU: 55555554\n    [  560.846480] Call Trace:\n    [  560.849225]  \u0026lt;TASK\u0026gt;\n    [  560.851580]  ? show_trace_log_lvl+0x1d6/0x2ea\n    [  560.856488]  ? show_trace_log_lvl+0x1d6/0x2ea\n    [  560.861379]  ? amdgpu_ras_do_recovery+0x1b2/0x210 [amdgpu]\n    [  560.867778]  ? show_regs.part.0+0x23/0x29\n    [  560.872293]  ? __die_body.cold+0x8/0xd\n    [  560.876502]  ? die_addr+0x3e/0x60\n    [  560.880238]  ? exc_general_protection+0x1c5/0x410\n    [  560.885532]  ? asm_exc_general_protection+0x27/0x30\n    [  560.891025]  ? amdgpu_device_gpu_recover.cold+0xbf1/0xcf5 [amdgpu]\n    [  560.898323]  amdgpu_ras_do_recovery+0x1b2/0x210 [amdgpu]\n    [  560.904520]  process_one_work+0x228/0x3d0\nHow:\n    In RAS recovery, mode-1 reset is issued from RAS fatal error handling and expected\n    all the nodes in a hive to be reset. no need to issue another mode-1 during this procedure.(CVE-2024-35931)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/9p: fix uninitialized values during inode evict\r\n\r\nIf an iget fails due to not being able to retrieve information\nfrom the server then the inode structure is only partially\ninitialized.  When the inode gets evicted, references to\nuninitialized structures (like fscache cookies) were being\nmade.\r\n\r\nThis patch checks for a bad_inode before doing anything other\nthan clearing the inode from the cache.  Since the inode is\nbad, it shouldn\u0026apos;t have any state associated with it that needs\nto be written back (and there really isn\u0026apos;t a way to complete\nthose anyways).(CVE-2024-36923)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential kernel bug due to lack of writeback flag waiting\r\n\r\nDestructive writes to a block device on which nilfs2 is mounted can cause\na kernel bug in the folio/page writeback start routine or writeback end\nroutine (__folio_start_writeback in the log below):\r\n\r\n kernel BUG at mm/page-writeback.c:3070!\n Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\n ...\n RIP: 0010:__folio_start_writeback+0xbaa/0x10e0\n Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff\n  e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 \u0026lt;0f\u0026gt;\n  0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00\n ...\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2]\n  nilfs_segctor_construct+0x181/0x6b0 [nilfs2]\n  nilfs_segctor_thread+0x548/0x11c0 [nilfs2]\n  kthread+0x2f0/0x390\n  ret_from_fork+0x4b/0x80\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\r\n\r\nThis is because when the log writer starts a writeback for segment summary\nblocks or a super root block that use the backing device\u0026apos;s page cache, it\ndoes not wait for the ongoing folio/page writeback, resulting in an\ninconsistent writeback state.\r\n\r\nFix this issue by waiting for ongoing writebacks when putting\nfolios/pages on the backing device into writeback state.(CVE-2024-37078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: bridge: cdns-mhdp8546: Fix possible null pointer dereference\r\n\r\nIn cdns_mhdp_atomic_enable(), the return value of drm_mode_duplicate() is\nassigned to mhdp_state-\u0026gt;current_mode, and there is a dereference of it in\ndrm_mode_set_name(), which will lead to a NULL pointer dereference on\nfailure of drm_mode_duplicate().\r\n\r\nFix this bug add a check of mhdp_state-\u0026gt;current_mode.(CVE-2024-38548)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: carl9170: add a proper sanity check for endpoints\r\n\r\nSyzkaller reports [1] hitting a warning which is caused by presence\nof a wrong endpoint type at the URB sumbitting stage. While there\nwas a check for a specific 4th endpoint, since it can switch types\nbetween bulk and interrupt, other endpoints are trusted implicitly.\nSimilar warning is triggered in a couple of other syzbot issues [2].\r\n\r\nFix the issue by doing a comprehensive check of all endpoints\ntaking into account difference between high- and full-speed\nconfiguration.\r\n\r\n[1] Syzkaller report:\n...\nWARNING: CPU: 0 PID: 4721 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n carl9170_usb_send_rx_irq_urb+0x273/0x340 drivers/net/wireless/ath/carl9170/usb.c:504\n carl9170_usb_init_device drivers/net/wireless/ath/carl9170/usb.c:939 [inline]\n carl9170_usb_firmware_finish drivers/net/wireless/ath/carl9170/usb.c:999 [inline]\n carl9170_usb_firmware_step2+0x175/0x240 drivers/net/wireless/ath/carl9170/usb.c:1028\n request_firmware_work_func+0x130/0x240 drivers/base/firmware_loader/main.c:1107\n process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289\n worker_thread+0x669/0x1090 kernel/workqueue.c:2436\n kthread+0x2e8/0x3a0 kernel/kthread.c:376\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308\n \u0026lt;/TASK\u0026gt;\r\n\r\n[2] Related syzkaller crashes:(CVE-2024-38567)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmacintosh/via-macii: Fix \u0026quot;BUG: sleeping function called from invalid context\u0026quot;\r\n\r\nThe via-macii ADB driver calls request_irq() after disabling hard\ninterrupts. But disabling interrupts isn\u0026apos;t necessary here because the\nVIA shift register interrupt was masked during VIA1 initialization.(CVE-2024-38607)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: i2c: et8ek8: Don\u0026apos;t strip remove function when driver is builtin\r\n\r\nUsing __exit for the remove function results in the remove callback\nbeing discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets\nunbound (e.g. using sysfs or hotplug), the driver is just removed\nwithout the cleanup being performed. This results in resource leaks. Fix\nit by compiling in the remove callback unconditionally.\r\n\r\nThis also fixes a W=1 modpost warning:\r\n\r\n\tWARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -\u0026gt; et8ek8_remove (section: .exit.text)(CVE-2024-38611)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: add error handle to avoid out-of-bounds\r\n\r\nif the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should\nbe stop to avoid out-of-bounds read, so directly return -EINVAL.(CVE-2024-39471)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfbdev: savage: Handle err return when savagefb_check_var failed\r\n\r\nThe commit 04e5eac8f3ab(\u0026quot;fbdev: savage: Error out if pixclock equals zero\u0026quot;)\nchecks the value of pixclock to avoid divide-by-zero error. However\nthe function savagefb_probe doesn\u0026apos;t handle the error return of\nsavagefb_check_var. When pixclock is 0, it will cause divide-by-zero error.(CVE-2024-39475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING\r\n\r\nXiao reported that lvm2 test lvconvert-raid-takeover.sh can hang with\nsmall possibility, the root cause is exactly the same as commit\nbed9e27baf52 (\u0026quot;Revert \u0026quot;md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\u0026quot;\u0026quot;)\r\n\r\nHowever, Dan reported another hang after that, and junxiao investigated\nthe problem and found out that this is caused by plugged bio can\u0026apos;t issue\nfrom raid5d().\r\n\r\nCurrent implementation in raid5d() has a weird dependence:\r\n\r\n1) md_check_recovery() from raid5d() must hold \u0026apos;reconfig_mutex\u0026apos; to clear\n   MD_SB_CHANGE_PENDING;\n2) raid5d() handles IO in a deadloop, until all IO are issued;\n3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared;\r\n\r\nThis behaviour is introduce before v2.6, and for consequence, if other\ncontext hold \u0026apos;reconfig_mutex\u0026apos;, and md_check_recovery() can\u0026apos;t update\nsuper_block, then raid5d() will waste one cpu 100% by the deadloop, until\n\u0026apos;reconfig_mutex\u0026apos; is released.\r\n\r\nRefer to the implementation from raid1 and raid10, fix this problem by\nskipping issue IO if MD_SB_CHANGE_PENDING is still set after\nmd_check_recovery(), daemon thread will be woken up when \u0026apos;reconfig_mutex\u0026apos;\nis released. Meanwhile, the hang problem will be fixed as well.(CVE-2024-39476)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmmc: davinci: Don\u0026apos;t strip remove function when driver is builtin\r\n\r\nUsing __exit for the remove function results in the remove callback being\ndiscarded with CONFIG_MMC_DAVINCI=y. When such a device gets unbound (e.g.\nusing sysfs or hotplug), the driver is just removed without the cleanup\nbeing performed. This results in resource leaks. Fix it by compiling in the\nremove callback unconditionally.\r\n\r\nThis also fixes a W=1 modpost warning:\r\n\r\nWARNING: modpost: drivers/mmc/host/davinci_mmc: section mismatch in\nreference: davinci_mmcsd_driver+0x10 (section: .data) -\u0026gt;\ndavinci_mmcsd_remove (section: .exit.text)(CVE-2024-39484)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nliquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet\r\n\r\nIn lio_vf_rep_copy_packet() pg_info-\u0026gt;page is compared to a NULL value,\nbut then it is unconditionally passed to skb_add_rx_frag() which looks\nstrange and could lead to null pointer dereference.\r\n\r\nlio_vf_rep_copy_packet() call trace looks like:\n\tocteon_droq_process_packets\n\t octeon_droq_fast_process_packets\n\t  octeon_droq_dispatch_pkt\n\t   octeon_create_recv_info\n\t    ...search in the dispatch_list...\n\t     -\u0026gt;disp_fn(rdisp-\u0026gt;rinfo, ...)\n\t      lio_vf_rep_pkt_recv(struct octeon_recv_info *recv_info, ...)\nIn this path there is no code which sets pg_info-\u0026gt;page to NULL.\nSo this check looks unneeded and doesn\u0026apos;t solve potential problem.\nBut I guess the author had reason to add a check and I have no such card\nand can\u0026apos;t do real test.\nIn addition, the code in the function liquidio_push_packet() in\nliquidio/lio_core.c does exactly the same.\r\n\r\nBased on this, I consider the most acceptable compromise solution to\nadjust this issue by moving skb_add_rx_frag() into conditional scope.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-39506)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring/io-wq: Use set_bit() and test_bit() at worker-\u0026gt;flags\r\n\r\nUtilize set_bit() and test_bit() on worker-\u0026gt;flags within io_uring/io-wq\nto address potential data races.\r\n\r\nThe structure io_worker-\u0026gt;flags may be accessed through various data\npaths, leading to concurrency issues. When KCSAN is enabled, it reveals\ndata races occurring in io_worker_handle_work and\nio_wq_activate_free_worker functions.\r\n\r\n\t BUG: KCSAN: data-race in io_worker_handle_work / io_wq_activate_free_worker\n\t write to 0xffff8885c4246404 of 4 bytes by task 49071 on cpu 28:\n\t io_worker_handle_work (io_uring/io-wq.c:434 io_uring/io-wq.c:569)\n\t io_wq_worker (io_uring/io-wq.c:?)\n\u0026lt;snip\u0026gt;\r\n\r\n\t read to 0xffff8885c4246404 of 4 bytes by task 49024 on cpu 5:\n\t io_wq_activate_free_worker (io_uring/io-wq.c:? io_uring/io-wq.c:285)\n\t io_wq_enqueue (io_uring/io-wq.c:947)\n\t io_queue_iowq (io_uring/io_uring.c:524)\n\t io_req_task_submit (io_uring/io_uring.c:1511)\n\t io_handle_tw_list (io_uring/io_uring.c:1198)\n\u0026lt;snip\u0026gt;\r\n\r\nLine numbers against commit 18daea77cca6 (\u0026quot;Merge tag \u0026apos;for-linus\u0026apos; of\ngit://git.kernel.org/pub/scm/virt/kvm/kvm\u0026quot;).\r\n\r\nThese races involve writes and reads to the same memory location by\ndifferent tasks running on different CPUs. To mitigate this, refactor\nthe code to use atomic operations such as set_bit(), test_bit(), and\nclear_bit() instead of basic \u0026quot;and\u0026quot; and \u0026quot;or\u0026quot; operations. This ensures\nthread-safe manipulation of worker flags.\r\n\r\nAlso, move `create_index` to avoid holes in the structure.(CVE-2024-39508)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: rewrite __kernel_map_pages() to fix sleeping in invalid context\r\n\r\n__kernel_map_pages() is a debug function which clears the valid bit in page\ntable entry for deallocated pages to detect illegal memory accesses to\nfreed pages.\r\n\r\nThis function set/clear the valid bit using __set_memory(). __set_memory()\nacquires init_mm\u0026apos;s semaphore, and this operation may sleep. This is\nproblematic, because  __kernel_map_pages() can be called in atomic context,\nand thus is illegal to sleep. An example warning that this causes:\r\n\r\nBUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578\nin_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd\npreempt_count: 2, expected: 0\nCPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37\nHardware name: riscv-virtio,qemu (DT)\nCall Trace:\n[\u0026lt;ffffffff800060dc\u0026gt;] dump_backtrace+0x1c/0x24\n[\u0026lt;ffffffff8091ef6e\u0026gt;] show_stack+0x2c/0x38\n[\u0026lt;ffffffff8092baf8\u0026gt;] dump_stack_lvl+0x5a/0x72\n[\u0026lt;ffffffff8092bb24\u0026gt;] dump_stack+0x14/0x1c\n[\u0026lt;ffffffff8003b7ac\u0026gt;] __might_resched+0x104/0x10e\n[\u0026lt;ffffffff8003b7f4\u0026gt;] __might_sleep+0x3e/0x62\n[\u0026lt;ffffffff8093276a\u0026gt;] down_write+0x20/0x72\n[\u0026lt;ffffffff8000cf00\u0026gt;] __set_memory+0x82/0x2fa\n[\u0026lt;ffffffff8000d324\u0026gt;] __kernel_map_pages+0x5a/0xd4\n[\u0026lt;ffffffff80196cca\u0026gt;] __alloc_pages_bulk+0x3b2/0x43a\n[\u0026lt;ffffffff8018ee82\u0026gt;] __vmalloc_node_range+0x196/0x6ba\n[\u0026lt;ffffffff80011904\u0026gt;] copy_process+0x72c/0x17ec\n[\u0026lt;ffffffff80012ab4\u0026gt;] kernel_clone+0x60/0x2fe\n[\u0026lt;ffffffff80012f62\u0026gt;] kernel_thread+0x82/0xa0\n[\u0026lt;ffffffff8003552c\u0026gt;] kthreadd+0x14a/0x1be\n[\u0026lt;ffffffff809357de\u0026gt;] ret_from_fork+0xe/0x1c\r\n\r\nRewrite this function with apply_to_existing_page_range(). It is fine to\nnot have any locking, because __kernel_map_pages() works with pages being\nallocated/deallocated and those pages are not changed by anyone else in the\nmeantime.(CVE-2024-40915)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommu: Return right value in iommu_sva_bind_device()\r\n\r\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\r\n\r\nIn reality, this doesn\u0026apos;t cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won\u0026apos;t call iommu_sva_bind_device()\nat all.(CVE-2024-40945)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nima: Avoid blocking in RCU read-side critical section\r\n\r\nA panic happens in ima_match_policy:\r\n\r\nBUG: unable to handle kernel NULL pointer dereference at 0000000000000010\nPGD 42f873067 P4D 0\nOops: 0000 [#1] SMP NOPTI\nCPU: 5 PID: 1286325 Comm: kubeletmonit.sh\nKdump: loaded Tainted: P\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996),\n               BIOS 0.0.0 02/06/2015\nRIP: 0010:ima_match_policy+0x84/0x450\nCode: 49 89 fc 41 89 cf 31 ed 89 44 24 14 eb 1c 44 39\n      7b 18 74 26 41 83 ff 05 74 20 48 8b 1b 48 3b 1d\n      f2 b9 f4 00 0f 84 9c 01 00 00 \u0026lt;44\u0026gt; 85 73 10 74 ea\n      44 8b 6b 14 41 f6 c5 01 75 d4 41 f6 c5 02 74 0f\nRSP: 0018:ff71570009e07a80 EFLAGS: 00010207\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000200\nRDX: ffffffffad8dc7c0 RSI: 0000000024924925 RDI: ff3e27850dea2000\nRBP: 0000000000000000 R08: 0000000000000000 R09: ffffffffabfce739\nR10: ff3e27810cc42400 R11: 0000000000000000 R12: ff3e2781825ef970\nR13: 00000000ff3e2785 R14: 000000000000000c R15: 0000000000000001\nFS:  00007f5195b51740(0000)\nGS:ff3e278b12d40000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000010 CR3: 0000000626d24002 CR4: 0000000000361ee0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n ima_get_action+0x22/0x30\n process_measurement+0xb0/0x830\n ? page_add_file_rmap+0x15/0x170\n ? alloc_set_pte+0x269/0x4c0\n ? prep_new_page+0x81/0x140\n ? simple_xattr_get+0x75/0xa0\n ? selinux_file_open+0x9d/0xf0\n ima_file_check+0x64/0x90\n path_openat+0x571/0x1720\n do_filp_open+0x9b/0x110\n ? page_counter_try_charge+0x57/0xc0\n ? files_cgroup_alloc_fd+0x38/0x60\n ? __alloc_fd+0xd4/0x250\n ? do_sys_open+0x1bd/0x250\n do_sys_open+0x1bd/0x250\n do_syscall_64+0x5d/0x1d0\n entry_SYSCALL_64_after_hwframe+0x65/0xca\r\n\r\nCommit c7423dbdbc9e (\u0026quot;ima: Handle -ESTALE returned by\nima_filter_rule_match()\u0026quot;) introduced call to ima_lsm_copy_rule within a\nRCU read-side critical section which contains kmalloc with GFP_KERNEL.\nThis implies a possible sleep and violates limitations of RCU read-side\ncritical sections on non-PREEMPT systems.\r\n\r\nSleeping within RCU read-side critical section might cause\nsynchronize_rcu() returning early and break RCU protection, allowing a\nUAF to happen.\r\n\r\nThe root cause of this issue could be described as follows:\n|\tThread A\t|\tThread B\t|\n|\t\t\t|ima_match_policy\t|\n|\t\t\t|  rcu_read_lock\t|\n|ima_lsm_update_rule\t|\t\t\t|\n|  synchronize_rcu\t|\t\t\t|\n|\t\t\t|    kmalloc(GFP_KERNEL)|\n|\t\t\t|      sleep\t\t|\n==\u0026gt; synchronize_rcu returns early\n|  kfree(entry)\t\t|\t\t\t|\n|\t\t\t|    entry = entry-\u0026gt;next|\n==\u0026gt; UAF happens and entry now becomes NULL (or could be anything).\n|\t\t\t|    entry-\u0026gt;action\t|\n==\u0026gt; Accessing entry might cause panic.\r\n\r\nTo fix this issue, we are converting all kmalloc that is called within\nRCU read-side critical section to use GFP_ATOMIC.\r\n\r\n[PM: fixed missing comment, long lines, !CONFIG_IMA_LSM_RULES case](CVE-2024-40947)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list\r\n\r\nUse list_for_each_entry_safe() to allow iterating through the list and\ndeleting the entry in the iteration process. The descriptor is freed via\nidxd_desc_complete() and there\u0026apos;s a slight chance may cause issue for\nthe list iterator when the descriptor is reused by another thread\nwithout it being deleted from the list.(CVE-2024-40956)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: prevent possible NULL dereference in rt6_probe()\r\n\r\nsyzbot caught a NULL dereference in rt6_probe() [1]\r\n\r\nBail out if  __in6_dev_get() returns NULL.\r\n\r\n[1]\nOops: general protection fault, probably for non-canonical address 0xdffffc00000000cb: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000658-0x000000000000065f]\nCPU: 1 PID: 22444 Comm: syz-executor.0 Not tainted 6.10.0-rc2-syzkaller-00383-gb8481381d4e2 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\n RIP: 0010:rt6_probe net/ipv6/route.c:656 [inline]\n RIP: 0010:find_match+0x8c4/0xf50 net/ipv6/route.c:758\nCode: 14 fd f7 48 8b 85 38 ff ff ff 48 c7 45 b0 00 00 00 00 48 8d b8 5c 06 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 \u0026lt;0f\u0026gt; b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 19\nRSP: 0018:ffffc900034af070 EFLAGS: 00010203\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffc90004521000\nRDX: 00000000000000cb RSI: ffffffff8990d0cd RDI: 000000000000065c\nRBP: ffffc900034af150 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000000000001 R11: 0000000000000002 R12: 000000000000000a\nR13: 1ffff92000695e18 R14: ffff8880244a1d20 R15: 0000000000000000\nFS:  00007f4844a5a6c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000001b31b27000 CR3: 000000002d42c000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  rt6_nh_find_match+0xfa/0x1a0 net/ipv6/route.c:784\n  nexthop_for_each_fib6_nh+0x26d/0x4a0 net/ipv4/nexthop.c:1496\n  __find_rr_leaf+0x6e7/0xe00 net/ipv6/route.c:825\n  find_rr_leaf net/ipv6/route.c:853 [inline]\n  rt6_select net/ipv6/route.c:897 [inline]\n  fib6_table_lookup+0x57e/0xa30 net/ipv6/route.c:2195\n  ip6_pol_route+0x1cd/0x1150 net/ipv6/route.c:2231\n  pol_lookup_func include/net/ip6_fib.h:616 [inline]\n  fib6_rule_lookup+0x386/0x720 net/ipv6/fib6_rules.c:121\n  ip6_route_output_flags_noref net/ipv6/route.c:2639 [inline]\n  ip6_route_output_flags+0x1d0/0x640 net/ipv6/route.c:2651\n  ip6_dst_lookup_tail.constprop.0+0x961/0x1760 net/ipv6/ip6_output.c:1147\n  ip6_dst_lookup_flow+0x99/0x1d0 net/ipv6/ip6_output.c:1250\n  rawv6_sendmsg+0xdab/0x4340 net/ipv6/raw.c:898\n  inet_sendmsg+0x119/0x140 net/ipv4/af_inet.c:853\n  sock_sendmsg_nosec net/socket.c:730 [inline]\n  __sock_sendmsg net/socket.c:745 [inline]\n  sock_write_iter+0x4b8/0x5c0 net/socket.c:1160\n  new_sync_write fs/read_write.c:497 [inline]\n  vfs_write+0x6b6/0x1140 fs/read_write.c:590\n  ksys_write+0x1f8/0x260 fs/read_write.c:643\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-40960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmips: bmips: BCM6358: make sure CBR is correctly set\r\n\r\nIt was discovered that some device have CBR address set to 0 causing\nkernel panic when arch_sync_dma_for_cpu_all is called.\r\n\r\nThis was notice in situation where the system is booted from TP1 and\nBMIPS_GET_CBR() returns 0 instead of a valid address and\n!!(read_c0_brcm_cmt_local() \u0026amp; (1 \u0026lt;\u0026lt; 31)); not failing.\r\n\r\nThe current check whether RAC flush should be disabled or not are not\nenough hence lets check if CBR is a valid address or not.(CVE-2024-40963)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: imx: Introduce timeout when waiting on transmitter empty\r\n\r\nBy waiting at most 1 second for USR2_TXDC to be set, we avoid a potential\ndeadlock.\r\n\r\nIn case of the timeout, there is not much we can do, so we simply ignore\nthe transmitter state and optimistically try to continue.(CVE-2024-40967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: do not create EA inode under buffer lock\r\n\r\next4_xattr_set_entry() creates new EA inodes while holding buffer lock\non the external xattr block. This is problematic as it nests all the\nallocation locking (which acquires locks on other buffers) under the\nbuffer lock. This can even deadlock when the filesystem is corrupted and\ne.g. quota file is setup to contain xattr block as data block. Move the\nallocation of EA inode out of ext4_xattr_set_entry() into the callers.(CVE-2024-40972)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrop_monitor: replace spin_lock by raw_spin_lock\r\n\r\ntrace_drop_common() is called with preemption disabled, and it acquires\na spin_lock. This is problematic for RT kernels because spin_locks are\nsleeping locks in this configuration, which causes the following splat:\r\n\r\nBUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\nin_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 449, name: rcuc/47\npreempt_count: 1, expected: 0\nRCU nest depth: 2, expected: 2\n5 locks held by rcuc/47/449:\n #0: ff1100086ec30a60 ((softirq_ctrl.lock)){+.+.}-{2:2}, at: __local_bh_disable_ip+0x105/0x210\n #1: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: rt_spin_lock+0xbf/0x130\n #2: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: __local_bh_disable_ip+0x11c/0x210\n #3: ffffffffb394a160 (rcu_callback){....}-{0:0}, at: rcu_do_batch+0x360/0xc70\n #4: ff1100086ee07520 (\u0026amp;data-\u0026gt;lock){+.+.}-{2:2}, at: trace_drop_common.constprop.0+0xb5/0x290\nirq event stamp: 139909\nhardirqs last  enabled at (139908): [\u0026lt;ffffffffb1df2b33\u0026gt;] _raw_spin_unlock_irqrestore+0x63/0x80\nhardirqs last disabled at (139909): [\u0026lt;ffffffffb19bd03d\u0026gt;] trace_drop_common.constprop.0+0x26d/0x290\nsoftirqs last  enabled at (139892): [\u0026lt;ffffffffb07a1083\u0026gt;] __local_bh_enable_ip+0x103/0x170\nsoftirqs last disabled at (139898): [\u0026lt;ffffffffb0909b33\u0026gt;] rcu_cpu_kthread+0x93/0x1f0\nPreemption disabled at:\n[\u0026lt;ffffffffb1de786b\u0026gt;] rt_mutex_slowunlock+0xab/0x2e0\nCPU: 47 PID: 449 Comm: rcuc/47 Not tainted 6.9.0-rc2-rt1+ #7\nHardware name: Dell Inc. PowerEdge R650/0Y2G81, BIOS 1.6.5 04/15/2022\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x8c/0xd0\n dump_stack+0x14/0x20\n __might_resched+0x21e/0x2f0\n rt_spin_lock+0x5e/0x130\n ? trace_drop_common.constprop.0+0xb5/0x290\n ? skb_queue_purge_reason.part.0+0x1bf/0x230\n trace_drop_common.constprop.0+0xb5/0x290\n ? preempt_count_sub+0x1c/0xd0\n ? _raw_spin_unlock_irqrestore+0x4a/0x80\n ? __pfx_trace_drop_common.constprop.0+0x10/0x10\n ? rt_mutex_slowunlock+0x26a/0x2e0\n ? skb_queue_purge_reason.part.0+0x1bf/0x230\n ? __pfx_rt_mutex_slowunlock+0x10/0x10\n ? skb_queue_purge_reason.part.0+0x1bf/0x230\n trace_kfree_skb_hit+0x15/0x20\n trace_kfree_skb+0xe9/0x150\n kfree_skb_reason+0x7b/0x110\n skb_queue_purge_reason.part.0+0x1bf/0x230\n ? __pfx_skb_queue_purge_reason.part.0+0x10/0x10\n ? mark_lock.part.0+0x8a/0x520\n...\r\n\r\ntrace_drop_common() also disables interrupts, but this is a minor issue\nbecause we could easily replace it with a local_lock.\r\n\r\nReplace the spin_lock with raw_spin_lock to avoid sleeping in atomic\ncontext.(CVE-2024-40980)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbatman-adv: bypass empty buckets in batadv_purge_orig_ref()\r\n\r\nMany syzbot reports are pointing to soft lockups in\nbatadv_purge_orig_ref() [1]\r\n\r\nRoot cause is unknown, but we can avoid spending too much\ntime there and perhaps get more interesting reports.\r\n\r\n[1]\r\n\r\nwatchdog: BUG: soft lockup - CPU#0 stuck for 27s! [kworker/u4:6:621]\nModules linked in:\nirq event stamp: 6182794\n hardirqs last  enabled at (6182793): [\u0026lt;ffff8000801dae10\u0026gt;] __local_bh_enable_ip+0x224/0x44c kernel/softirq.c:386\n hardirqs last disabled at (6182794): [\u0026lt;ffff80008ad66a78\u0026gt;] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline]\n hardirqs last disabled at (6182794): [\u0026lt;ffff80008ad66a78\u0026gt;] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551\n softirqs last  enabled at (6182792): [\u0026lt;ffff80008aab71c4\u0026gt;] spin_unlock_bh include/linux/spinlock.h:396 [inline]\n softirqs last  enabled at (6182792): [\u0026lt;ffff80008aab71c4\u0026gt;] batadv_purge_orig_ref+0x114c/0x1228 net/batman-adv/originator.c:1287\n softirqs last disabled at (6182790): [\u0026lt;ffff80008aab61dc\u0026gt;] spin_lock_bh include/linux/spinlock.h:356 [inline]\n softirqs last disabled at (6182790): [\u0026lt;ffff80008aab61dc\u0026gt;] batadv_purge_orig_ref+0x164/0x1228 net/batman-adv/originator.c:1271\nCPU: 0 PID: 621 Comm: kworker/u4:6 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024\nWorkqueue: bat_events batadv_purge_orig\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : should_resched arch/arm64/include/asm/preempt.h:79 [inline]\n pc : __local_bh_enable_ip+0x228/0x44c kernel/softirq.c:388\n lr : __local_bh_enable_ip+0x224/0x44c kernel/softirq.c:386\nsp : ffff800099007970\nx29: ffff800099007980 x28: 1fffe00018fce1bd x27: dfff800000000000\nx26: ffff0000d2620008 x25: ffff0000c7e70de8 x24: 0000000000000001\nx23: 1fffe00018e57781 x22: dfff800000000000 x21: ffff80008aab71c4\nx20: ffff0001b40136c0 x19: ffff0000c72bbc08 x18: 1fffe0001a817bb0\nx17: ffff800125414000 x16: ffff80008032116c x15: 0000000000000001\nx14: 1fffe0001ee9d610 x13: 0000000000000000 x12: 0000000000000003\nx11: 0000000000000000 x10: 0000000000ff0100 x9 : 0000000000000000\nx8 : 00000000005e5789 x7 : ffff80008aab61dc x6 : 0000000000000000\nx5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000\nx2 : 0000000000000006 x1 : 0000000000000080 x0 : ffff800125414000\nCall trace:\n  __daif_local_irq_enable arch/arm64/include/asm/irqflags.h:27 [inline]\n  arch_local_irq_enable arch/arm64/include/asm/irqflags.h:49 [inline]\n  __local_bh_enable_ip+0x228/0x44c kernel/softirq.c:386\n  __raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n  _raw_spin_unlock_bh+0x3c/0x4c kernel/locking/spinlock.c:210\n  spin_unlock_bh include/linux/spinlock.h:396 [inline]\n  batadv_purge_orig_ref+0x114c/0x1228 net/batman-adv/originator.c:1287\n  batadv_purge_orig+0x20/0x70 net/batman-adv/originator.c:1300\n  process_one_work+0x694/0x1204 kernel/workqueue.c:2633\n  process_scheduled_works kernel/workqueue.c:2706 [inline]\n  worker_thread+0x938/0xef4 kernel/workqueue.c:2787\n  kthread+0x288/0x310 kernel/kthread.c:388\n  ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860\nSending NMI from CPU 0 to CPUs 1:\nNMI backtrace for cpu 1\nCPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : arch_local_irq_enable+0x8/0xc arch/arm64/include/asm/irqflags.h:51\n lr : default_idle_call+0xf8/0x128 kernel/sched/idle.c:103\nsp : ffff800093a17d30\nx29: ffff800093a17d30 x28: dfff800000000000 x27: 1ffff00012742fb4\nx26: ffff80008ec9d000 x25: 0000000000000000 x24: 0000000000000002\nx23: 1ffff00011d93a74 x22: ffff80008ec9d3a0 x21: 0000000000000000\nx20: ffff0000c19dbc00 x19: ffff8000802d0fd8 x18: 1fffe00036804396\nx17: ffff80008ec9d000 x16: ffff8000802d089c x15: 0000000000000001\n---truncated---(CVE-2024-40981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nssb: Fix potential NULL pointer dereference in ssb_device_uevent()\r\n\r\nThe ssb_device_uevent() function first attempts to convert the \u0026apos;dev\u0026apos; pointer\nto \u0026apos;struct ssb_device *\u0026apos;. However, it mistakenly dereferences \u0026apos;dev\u0026apos; before\nperforming the NULL check, potentially leading to a NULL pointer\ndereference if \u0026apos;dev\u0026apos; is NULL.\r\n\r\nTo fix this issue, move the NULL check before dereferencing the \u0026apos;dev\u0026apos; pointer,\nensuring that the pointer is valid before attempting to use it.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-40982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc()\r\n\r\nsyzbot found hanging tasks waiting on rtnl_lock [1]\r\n\r\nA reproducer is available in the syzbot bug.\r\n\r\nWhen a request to add multiple actions with the same index is sent, the\nsecond request will block forever on the first request. This holds\nrtnl_lock, and causes tasks to hang.\r\n\r\nReturn -EAGAIN to prevent infinite looping, while keeping documented\nbehavior.\r\n\r\n[1]\r\n\r\nINFO: task kworker/1:0:5088 blocked for more than 143 seconds.\nNot tainted 6.9.0-rc4-syzkaller-00173-g3cdb45594619 #0\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/1:0 state:D stack:23744 pid:5088 tgid:5088 ppid:2 flags:0x00004000\nWorkqueue: events_power_efficient reg_check_chans_work\nCall Trace:\n\u0026lt;TASK\u0026gt;\ncontext_switch kernel/sched/core.c:5409 [inline]\n__schedule+0xf15/0x5d00 kernel/sched/core.c:6746\n__schedule_loop kernel/sched/core.c:6823 [inline]\nschedule+0xe7/0x350 kernel/sched/core.c:6838\nschedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6895\n__mutex_lock_common kernel/locking/mutex.c:684 [inline]\n__mutex_lock+0x5b8/0x9c0 kernel/locking/mutex.c:752\nwiphy_lock include/net/cfg80211.h:5953 [inline]\nreg_leave_invalid_chans net/wireless/reg.c:2466 [inline]\nreg_check_chans_work+0x10a/0x10e0 net/wireless/reg.c:2481(CVE-2024-40995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdkfd: don\u0026apos;t allow mapping the MMIO HDP page with large pages\r\n\r\nWe don\u0026apos;t get the right offset in that case.  The GPU has\nan unused 4K area of the register BAR space into which you can\nremap registers.  We remap the HDP flush registers into this\nspace to allow userspace (CPU or GPU) to flush the HDP when it\nupdates VRAM.  However, on systems with \u0026gt;4K pages, we end up\nexposing PAGE_SIZE of MMIO space.(CVE-2024-41011)","status":"published","published":"2024-08-02T11:07:24Z","modified":"2026-08-18T01:18:32.587445887Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2028","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\nipvlan: Dont Use skb-\u0026gt;sk in ipvlan_process_v{4,6}_outbound\r\n\r\nRaw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will\nhit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.\r\n\r\nWARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70\nModules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper\nCPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nRIP: 0010:sk_mc_loop+0x2d/0x70\nCode: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c\nRSP: 0018:ffffa9584015cd78 EFLAGS: 00010212\nRAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001\nRDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000\nRBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00\nR10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000\nR13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000\nFS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n\u0026lt;IRQ\u0026gt;\n ? __warn (kernel/panic.c:693)\n ? sk_mc_loop (net/core/sock.c:760)\n ? report_bug (lib/bug.c:201 lib/bug.c:219)\n ? handle_bug (arch/x86/kernel/traps.c:239)\n ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1))\n ? asm_exc_invalid_op (./arch/x86/include/asm/idtentry.h:621)\n ? sk_mc_loop (net/core/sock.c:760)\n ip6_finish_output2 (net/ipv6/ip6_output.c:83 (discriminator 1))\n ? nf_hook_slow (net/netfilter/core.c:626)\n ip6_finish_output (net/ipv6/ip6_output.c:222)\n ? __pfx_ip6_finish_output (net/ipv6/ip6_output.c:215)\n ipvlan_xmit_mode_l3 (drivers/net/ipvlan/ipvlan_core.c:602) ipvlan\n ipvlan_start_xmit (drivers/net/ipvlan/ipvlan_main.c:226) ipvlan\n dev_hard_start_xmit (net/core/dev.c:3594)\n sch_direct_xmit (net/sched/sch_generic.c:343)\n __qdisc_run (net/sched/sch_generic.c:416)\n net_tx_action (net/core/dev.c:5286)\n handle_softirqs (kernel/softirq.c:555)\n __irq_exit_rcu (kernel/softirq.c:589)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043)\r\n\r\nThe warning triggers as this:\npacket_sendmsg\n   packet_snd //skb-\u0026gt;sk is packet sk\n      __dev_queue_xmit\n         __dev_xmit_skb //q-\u0026gt;enqueue is not NULL\n             __qdisc_run\n               sch_direct_xmit\n                 dev_hard_start_xmit\n                   ipvlan_start_xmit\n                      ipvlan_xmit_mode_l3 //l3 mode\n                        ipvlan_process_outbound //vepa flag\n                          ipvlan_process_v6_outbound\n                            ip6_local_out\n                                __ip6_finish_output\n                                  ip6_finish_output2 //multicast packet\n                                    sk_mc_loop //sk-\u0026gt;sk_family is AF_PACKET\r\n\r\nCall ip{6}_local_out() with NULL sk in ipvlan as other tunnels to fix this.(CVE-2024-33621)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-mapping: benchmark: fix node id validation\r\n\r\nWhile validating node ids in map_benchmark_ioctl(), node_possible() may\nbe provided with invalid argument outside of [0,MAX_NUMNODES-1] range\nleading to:\r\n\r\nBUG: KASAN: wild-memory-access in map_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nRead of size 8 at addr 1fffffff8ccb6398 by task dma_map_benchma/971\nCPU: 7 PID: 971 Comm: dma_map_benchma Not tainted 6.9.0-rc6 #37\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996)\nCall Trace:\n \u0026lt;TASK\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:117)\nkasan_report (mm/kasan/report.c:603)\nkasan_check_range (mm/kasan/generic.c:189)\nvariable_test_bit (arch/x86/include/asm/bitops.h:227) [inline]\narch_test_bit (arch/x86/include/asm/bitops.h:239) [inline]\n_test_bit at (include/asm-generic/bitops/instrumented-non-atomic.h:142) [inline]\nnode_state (include/linux/nodemask.h:423) [inline]\nmap_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nfull_proxy_unlocked_ioctl (fs/debugfs/file.c:333)\n__x64_sys_ioctl (fs/ioctl.c:890)\ndo_syscall_64 (arch/x86/entry/common.c:83)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nCompare node ids with sane bounds first. NUMA_NO_NODE is considered a\nspecial valid case meaning that benchmarking kthreads won\u0026apos;t be bound to a\ncpuset of a given node.\r\n\r\nFound by Linux Verification Center (linuxtesting.org).(CVE-2024-34777)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/rxe: Fix seg fault in rxe_comp_queue_pkt\r\n\r\nIn rxe_comp_queue_pkt() an incoming response packet skb is enqueued to the\nresp_pkts queue and then a decision is made whether to run the completer\ntask inline or schedule it. Finally the skb is dereferenced to bump a \u0026apos;hw\u0026apos;\nperformance counter. This is wrong because if the completer task is\nalready running in a separate thread it may have already processed the skb\nand freed it which can cause a seg fault.  This has been observed\ninfrequently in testing at high scale.\r\n\r\nThis patch fixes this by changing the order of enqueuing the packet until\nafter the counter is accessed.(CVE-2024-38544)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ar5523: enable proper endpoint verification\r\n\r\nSyzkaller reports [1] hitting a warning about an endpoint in use\nnot having an expected type to it.\r\n\r\nFix the issue by checking for the existence of all proper\nendpoints with their according types intact.\r\n\r\nSadly, this patch has not been tested on real hardware.\r\n\r\n[1] Syzkaller report:\n------------[ cut here ]------------\nusb 1-1: BOGUS urb xfer, pipe 3 != type 1\nWARNING: CPU: 0 PID: 3643 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ar5523_cmd+0x41b/0x780 drivers/net/wireless/ath/ar5523/ar5523.c:275\n ar5523_cmd_read drivers/net/wireless/ath/ar5523/ar5523.c:302 [inline]\n ar5523_host_available drivers/net/wireless/ath/ar5523/ar5523.c:1376 [inline]\n ar5523_probe+0x14b0/0x1d10 drivers/net/wireless/ath/ar5523/ar5523.c:1655\n usb_probe_interface+0x30f/0x7f0 drivers/usb/core/driver.c:396\n call_driver_probe drivers/base/dd.c:560 [inline]\n really_probe+0x249/0xb90 drivers/base/dd.c:639\n __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808\n __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936\n bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427\n __device_attach+0x1e4/0x530 drivers/base/dd.c:1008\n bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487\n device_add+0xbd9/0x1e90 drivers/base/core.c:3517\n usb_set_configuration+0x101d/0x1900 drivers/usb/core/message.c:2170\n usb_generic_driver_probe+0xbe/0x100 drivers/usb/core/generic.c:238\n usb_probe_device+0xd8/0x2c0 drivers/usb/core/driver.c:293\n call_driver_probe drivers/base/dd.c:560 [inline]\n really_probe+0x249/0xb90 drivers/base/dd.c:639\n __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808\n __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936\n bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427\n __device_attach+0x1e4/0x530 drivers/base/dd.c:1008\n bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487\n device_add+0xbd9/0x1e90 drivers/base/core.c:3517\n usb_new_device.cold+0x685/0x10ad drivers/usb/core/hub.c:2573\n hub_port_connect drivers/usb/core/hub.c:5353 [inline]\n hub_port_connect_change drivers/usb/core/hub.c:5497 [inline]\n port_event drivers/usb/core/hub.c:5653 [inline]\n hub_event+0x26cb/0x45d0 drivers/usb/core/hub.c:5735\n process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289\n worker_thread+0x669/0x1090 kernel/workqueue.c:2436\n kthread+0x2e8/0x3a0 kernel/kthread.c:376\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306\n \u0026lt;/TASK\u0026gt;(CVE-2024-38565)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\neth: sungem: remove .ndo_poll_controller to avoid deadlocks\r\n\r\nErhard reports netpoll warnings from sungem:\r\n\r\n  netpoll_send_skb_on_dev(): eth0 enabled interrupts in poll (gem_start_xmit+0x0/0x398)\n  WARNING: CPU: 1 PID: 1 at net/core/netpoll.c:370 netpoll_send_skb+0x1fc/0x20c\r\n\r\ngem_poll_controller() disables interrupts, which may sleep.\nWe can\u0026apos;t sleep in netpoll, it has interrupts disabled completely.\nStrangely, gem_poll_controller() doesn\u0026apos;t even poll the completions,\nand instead acts as if an interrupt has fired so it just schedules\nNAPI and exits. None of this has been necessary for years, since\nnetpoll invokes NAPI directly.(CVE-2024-38597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: fix mb_cache_entry\u0026apos;s e_refcnt leak in ext4_xattr_block_cache_find()\r\n\r\nSyzbot reports a warning as follows:\r\n\r\n============================================\nWARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290\nModules linked in:\nCPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7\nRIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375\n generic_shutdown_super+0x136/0x2d0 fs/super.c:641\n kill_block_super+0x44/0x90 fs/super.c:1675\n ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327\n[...]\n============================================\r\n\r\nThis is because when finding an entry in ext4_xattr_block_cache_find(), if\next4_sb_bread() returns -ENOMEM, the ce\u0026apos;s e_refcnt, which has already grown\nin the __entry_find(), won\u0026apos;t be put away, and eventually trigger the above\nissue in mb_cache_destroy() due to reference count leakage.\r\n\r\nSo call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.(CVE-2024-39276)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING\r\n\r\nXiao reported that lvm2 test lvconvert-raid-takeover.sh can hang with\nsmall possibility, the root cause is exactly the same as commit\nbed9e27baf52 (\u0026quot;Revert \u0026quot;md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\u0026quot;\u0026quot;)\r\n\r\nHowever, Dan reported another hang after that, and junxiao investigated\nthe problem and found out that this is caused by plugged bio can\u0026apos;t issue\nfrom raid5d().\r\n\r\nCurrent implementation in raid5d() has a weird dependence:\r\n\r\n1) md_check_recovery() from raid5d() must hold \u0026apos;reconfig_mutex\u0026apos; to clear\n   MD_SB_CHANGE_PENDING;\n2) raid5d() handles IO in a deadloop, until all IO are issued;\n3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared;\r\n\r\nThis behaviour is introduce before v2.6, and for consequence, if other\ncontext hold \u0026apos;reconfig_mutex\u0026apos;, and md_check_recovery() can\u0026apos;t update\nsuper_block, then raid5d() will waste one cpu 100% by the deadloop, until\n\u0026apos;reconfig_mutex\u0026apos; is released.\r\n\r\nRefer to the implementation from raid1 and raid10, fix this problem by\nskipping issue IO if MD_SB_CHANGE_PENDING is still set after\nmd_check_recovery(), daemon thread will be woken up when \u0026apos;reconfig_mutex\u0026apos;\nis released. Meanwhile, the hang problem will be fixed as well.(CVE-2024-39476)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: xattr: fix buffer overflow for invalid xattr\r\n\r\nWhen an xattr size is not what is expected, it is printed out to the\nkernel log in hex format as a form of debugging.  But when that xattr\nsize is bigger than the expected size, printing it out can cause an\naccess off the end of the buffer.\r\n\r\nFix this all up by properly restricting the size of the debug hex dump\nin the kernel log.(CVE-2024-40902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommu: Return right value in iommu_sva_bind_device()\r\n\r\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\r\n\r\nIn reality, this doesn\u0026apos;t cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won\u0026apos;t call iommu_sva_bind_device()\nat all.(CVE-2024-40945)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntty: add the option to have a tty reject a new ldisc\r\n\r\n... and use it to limit the virtual terminals to just N_TTY.  They are\nkind of special, and in particular, the \u0026quot;con_write()\u0026quot; routine violates\nthe \u0026quot;writes cannot sleep\u0026quot; rule that some ldiscs rely on.\r\n\r\nThis avoids the\r\n\r\n   BUG: sleeping function called from invalid context at kernel/printk/printk.c:2659\r\n\r\nwhen N_GSM has been attached to a virtual console, and gsmld_write()\ncalls con_write() while holding a spinlock, and con_write() then tries\nto get the console lock.(CVE-2024-40966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncan: mcp251xfd: fix infinite loop when xmit fails\r\n\r\nWhen the mcp251xfd_start_xmit() function fails, the driver stops\nprocessing messages, and the interrupt routine does not return,\nrunning indefinitely even after killing the running application.\r\n\r\nError messages:\n[  441.298819] mcp251xfd spi2.0 can0: ERROR in mcp251xfd_start_xmit: -16\n[  441.306498] mcp251xfd spi2.0 can0: Transmit Event FIFO buffer not empty. (seq=0x000017c7, tef_tail=0x000017cf, tef_head=0x000017d0, tx_head=0x000017d3).\n... and repeat forever.\r\n\r\nThe issue can be triggered when multiple devices share the same SPI\ninterface. And there is concurrent access to the bus.\r\n\r\nThe problem occurs because tx_ring-\u0026gt;head increments even if\nmcp251xfd_start_xmit() fails. Consequently, the driver skips one TX\npackage while still expecting a response in\nmcp251xfd_handle_tefif_one().\r\n\r\nResolve the issue by starting a workqueue to write the tx obj\nsynchronously if err = -EBUSY. In case of another error, decrement\ntx_ring-\u0026gt;head, remove skb from the echo stack, and drop the message.\r\n\r\n[mkl: use more imperative wording in patch description](CVE-2024-41088)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers\r\n\r\nregister store validation for NFT_DATA_VALUE is conditional, however,\nthe datatype is always either NFT_DATA_VALUE or NFT_DATA_VERDICT. This\nonly requires a new helper function to infer the register type from the\nset datatype so this conditional check can be removed. Otherwise,\npointer to chain object can be leaked through the registers.(CVE-2024-42070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/lima: fix shared irq handling on driver remove\r\n\r\nlima uses a shared interrupt, so the interrupt handlers must be prepared\nto be called at any time. At driver removal time, the clocks are\ndisabled early and the interrupts stay registered until the very end of\nthe remove process due to the devm usage.\nThis is potentially a bug as the interrupts access device registers\nwhich assumes clocks are enabled. A crash can be triggered by removing\nthe driver in a kernel with CONFIG_DEBUG_SHIRQ enabled.\nThis patch frees the interrupts at each lima device finishing callback\nso that the handlers are already unregistered by the time we fully\ndisable clocks.(CVE-2024-42127)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm: avoid overflows in dirty throttling logic\r\n\r\nThe dirty throttling logic is interspersed with assumptions that dirty\nlimits in PAGE_SIZE units fit into 32-bit (so that various multiplications\nfit into 64-bits).  If limits end up being larger, we will hit overflows,\npossible divisions by 0 etc.  Fix these problems by never allowing so\nlarge dirty limits as they have dubious practical value anyway.  For\ndirty_bytes / dirty_background_bytes interfaces we can just refuse to set\nso large limits.  For dirty_ratio / dirty_background_ratio it isn\u0026apos;t so\nsimple as the dirty limit is computed from the amount of available memory\nwhich can change due to memory hotplug etc.  So when converting dirty\nlimits from ratios to numbers of pages, we just don\u0026apos;t allow the result to\nexceed UINT_MAX.\r\n\r\nThis is root-only triggerable problem which occurs when the operator\nsets dirty limits to \u0026gt;16 TB.(CVE-2024-42131)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlibceph: fix race between delayed_work() and ceph_monc_stop()\r\n\r\nThe way the delayed work is handled in ceph_monc_stop() is prone to\nraces with mon_fault() and possibly also finish_hunting().  Both of\nthese can requeue the delayed work which wouldn\u0026apos;t be canceled by any of\nthe following code in case that happens after cancel_delayed_work_sync()\nruns -- __close_session() doesn\u0026apos;t mess with the delayed work in order\nto avoid interfering with the hunting interval logic.  This part was\nmissed in commit b5d91704f53e (\u0026quot;libceph: behave in mon_fault() if\ncur_mon \u0026lt; 0\u0026quot;) and use-after-free can still ensue on monc and objects\nthat hang off of it, with monc-\u0026gt;auth and monc-\u0026gt;monmap being\nparticularly susceptible to quickly being reused.\r\n\r\nTo fix this:\r\n\r\n- clear monc-\u0026gt;cur_mon and monc-\u0026gt;hunting as part of closing the session\n  in ceph_monc_stop()\n- bail from delayed_work() if monc-\u0026gt;cur_mon is cleared, similar to how\n  it\u0026apos;s done in mon_fault() and finish_hunting() (based on monc-\u0026gt;hunting)\n- call cancel_delayed_work_sync() after the session is closed(CVE-2024-42232)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: gadget: configfs: Prevent OOB read/write in usb_string_copy()\r\n\r\nUserspace provided string \u0026apos;s\u0026apos; could trivially have the length zero. Left\nunchecked this will firstly result in an OOB read in the form\n`if (str[0 - 1] == \u0026apos;\\n\u0026apos;) followed closely by an OOB write in the form\n`str[0 - 1] = \u0026apos;\\0\u0026apos;`.\r\n\r\nThere is already a validating check to catch strings that are too long.\nLet\u0026apos;s supply an additional check for invalid strings that are too short.(CVE-2024-42236)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: make sure the first directory block is not a hole\r\n\r\nThe syzbot constructs a directory that has no dirblock but is non-inline,\ni.e. the first directory block is a hole. And no errors are reported when\ncreating files in this directory in the following flow.\r\n\r\n    ext4_mknod\n     ...\n      ext4_add_entry\n        // Read block 0\n        ext4_read_dirblock(dir, block, DIRENT)\n          bh = ext4_bread(NULL, inode, block, 0)\n          if (!bh \u0026amp;\u0026amp; (type == INDEX || type == DIRENT_HTREE))\n          // The first directory block is a hole\n          // But type == DIRENT, so no error is reported.\r\n\r\nAfter that, we get a directory block without \u0026apos;.\u0026apos; and \u0026apos;..\u0026apos; but with a valid\ndentry. This may cause some code that relies on dot or dotdot (such as\nmake_indexed_dir()) to crash.\r\n\r\nTherefore when ext4_read_dirblock() finds that the first directory block\nis a hole report that the filesystem is corrupted and return an error to\navoid loading corrupted data from disk causing something bad.(CVE-2024-42304)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes\r\n\r\nIn cdv_intel_lvds_get_modes(), the return value of drm_mode_duplicate()\nis assigned to mode, which will lead to a NULL pointer dereference on\nfailure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42310)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbna: adjust \u0026apos;name\u0026apos; buf size of bna_tcb and bna_ccb structures\r\n\r\nTo have enough space to write all possible sprintf() args. Currently\n\u0026apos;name\u0026apos; size is 16, but the first \u0026apos;%s\u0026apos; specifier may already need at\nleast 16 characters, since \u0026apos;bnad-\u0026gt;netdev-\u0026gt;name\u0026apos; is used there.\r\n\r\nFor \u0026apos;%d\u0026apos; specifiers, assume that they require:\n * 1 char for \u0026apos;tx_id + tx_info-\u0026gt;tcb[i]-\u0026gt;id\u0026apos; sum, BNAD_MAX_TXQ_PER_TX is 8\n * 2 chars for \u0026apos;rx_id + rx_info-\u0026gt;rx_ctrl[i].ccb-\u0026gt;id\u0026apos;, BNAD_MAX_RXP_PER_RX\n   is 16\r\n\r\nAnd replace sprintf with snprintf.\r\n\r\nDetected using the static analysis tool - Svace.(CVE-2024-43839)","status":"published","published":"2024-08-23T11:07:30Z","modified":"2026-08-18T01:18:34.948243464Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2076","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\nipvlan: Dont Use skb-\u0026gt;sk in ipvlan_process_v{4,6}_outbound\r\n\r\nRaw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will\nhit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.\r\n\r\nWARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70\nModules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper\nCPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nRIP: 0010:sk_mc_loop+0x2d/0x70\nCode: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c\nRSP: 0018:ffffa9584015cd78 EFLAGS: 00010212\nRAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001\nRDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000\nRBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00\nR10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000\nR13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000\nFS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n\u0026lt;IRQ\u0026gt;\n ? __warn (kernel/panic.c:693)\n ? sk_mc_loop (net/core/sock.c:760)\n ? report_bug (lib/bug.c:201 lib/bug.c:219)\n ? handle_bug (arch/x86/kernel/traps.c:239)\n ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1))\n ? asm_exc_invalid_op (./arch/x86/include/asm/idtentry.h:621)\n ? sk_mc_loop (net/core/sock.c:760)\n ip6_finish_output2 (net/ipv6/ip6_output.c:83 (discriminator 1))\n ? nf_hook_slow (net/netfilter/core.c:626)\n ip6_finish_output (net/ipv6/ip6_output.c:222)\n ? __pfx_ip6_finish_output (net/ipv6/ip6_output.c:215)\n ipvlan_xmit_mode_l3 (drivers/net/ipvlan/ipvlan_core.c:602) ipvlan\n ipvlan_start_xmit (drivers/net/ipvlan/ipvlan_main.c:226) ipvlan\n dev_hard_start_xmit (net/core/dev.c:3594)\n sch_direct_xmit (net/sched/sch_generic.c:343)\n __qdisc_run (net/sched/sch_generic.c:416)\n net_tx_action (net/core/dev.c:5286)\n handle_softirqs (kernel/softirq.c:555)\n __irq_exit_rcu (kernel/softirq.c:589)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043)\r\n\r\nThe warning triggers as this:\npacket_sendmsg\n   packet_snd //skb-\u0026gt;sk is packet sk\n      __dev_queue_xmit\n         __dev_xmit_skb //q-\u0026gt;enqueue is not NULL\n             __qdisc_run\n               sch_direct_xmit\n                 dev_hard_start_xmit\n                   ipvlan_start_xmit\n                      ipvlan_xmit_mode_l3 //l3 mode\n                        ipvlan_process_outbound //vepa flag\n                          ipvlan_process_v6_outbound\n                            ip6_local_out\n                                __ip6_finish_output\n                                  ip6_finish_output2 //multicast packet\n                                    sk_mc_loop //sk-\u0026gt;sk_family is AF_PACKET\r\n\r\nCall ip{6}_local_out() with NULL sk in ipvlan as other tunnels to fix this.(CVE-2024-33621)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: compress: don\u0026apos;t allow unaligned truncation on released compress inode\r\n\r\nf2fs image may be corrupted after below testcase:\n- mkfs.f2fs -O extra_attr,compression -f /dev/vdb\n- mount /dev/vdb /mnt/f2fs\n- touch /mnt/f2fs/file\n- f2fs_io setflags compression /mnt/f2fs/file\n- dd if=/dev/zero of=/mnt/f2fs/file bs=4k count=4\n- f2fs_io release_cblocks /mnt/f2fs/file\n- truncate -s 8192 /mnt/f2fs/file\n- umount /mnt/f2fs\n- fsck.f2fs /dev/vdb\r\n\r\n[ASSERT] (fsck_chk_inode_blk:1256)  --\u0026gt; ino: 0x5 has i_blocks: 0x00000002, but has 0x3 blocks\n[FSCK] valid_block_count matching with CP             [Fail] [0x4, 0x5]\n[FSCK] other corrupted bugs                           [Fail]\r\n\r\nThe reason is: partial truncation assume compressed inode has reserved\nblocks, after partial truncation, valid block count may change w/o\n.i_blocks and .total_valid_block_count update, result in corruption.\r\n\r\nThis patch only allow cluster size aligned truncation on released\ncompress inode for fixing.(CVE-2024-33847)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-mapping: benchmark: fix node id validation\r\n\r\nWhile validating node ids in map_benchmark_ioctl(), node_possible() may\nbe provided with invalid argument outside of [0,MAX_NUMNODES-1] range\nleading to:\r\n\r\nBUG: KASAN: wild-memory-access in map_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nRead of size 8 at addr 1fffffff8ccb6398 by task dma_map_benchma/971\nCPU: 7 PID: 971 Comm: dma_map_benchma Not tainted 6.9.0-rc6 #37\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996)\nCall Trace:\n \u0026lt;TASK\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:117)\nkasan_report (mm/kasan/report.c:603)\nkasan_check_range (mm/kasan/generic.c:189)\nvariable_test_bit (arch/x86/include/asm/bitops.h:227) [inline]\narch_test_bit (arch/x86/include/asm/bitops.h:239) [inline]\n_test_bit at (include/asm-generic/bitops/instrumented-non-atomic.h:142) [inline]\nnode_state (include/linux/nodemask.h:423) [inline]\nmap_benchmark_ioctl (kernel/dma/map_benchmark.c:214)\nfull_proxy_unlocked_ioctl (fs/debugfs/file.c:333)\n__x64_sys_ioctl (fs/ioctl.c:890)\ndo_syscall_64 (arch/x86/entry/common.c:83)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nCompare node ids with sane bounds first. NUMA_NO_NODE is considered a\nspecial valid case meaning that benchmarking kthreads won\u0026apos;t be bound to a\ncpuset of a given node.\r\n\r\nFound by Linux Verification Center (linuxtesting.org).(CVE-2024-34777)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: tproxy: bail out if IP has been disabled on the device\r\n\r\nsyzbot reports:\ngeneral protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]\n[..]\nRIP: 0010:nf_tproxy_laddr4+0xb7/0x340 net/ipv4/netfilter/nf_tproxy_ipv4.c:62\nCall Trace:\n nft_tproxy_eval_v4 net/netfilter/nft_tproxy.c:56 [inline]\n nft_tproxy_eval+0xa9a/0x1a00 net/netfilter/nft_tproxy.c:168\r\n\r\n__in_dev_get_rcu() can return NULL, so check for this.(CVE-2024-36270)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Use mlx5_ipsec_rx_status_destroy to correctly delete status rules\r\n\r\nrx_create no longer allocates a modify_hdr instance that needs to be\ncleaned up. The mlx5_modify_header_dealloc call will lead to a NULL pointer\ndereference. A leak in the rules also previously occurred since there are\nnow two rules populated related to status.\r\n\r\n  BUG: kernel NULL pointer dereference, address: 0000000000000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 109907067 P4D 109907067 PUD 116890067 PMD 0\n  Oops: 0000 [#1] SMP\n  CPU: 1 PID: 484 Comm: ip Not tainted 6.9.0-rc2-rrameshbabu+ #254\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS Arch Linux 1.16.3-1-1 04/01/2014\n  RIP: 0010:mlx5_modify_header_dealloc+0xd/0x70\n  \u0026lt;snip\u0026gt;\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ? show_regs+0x60/0x70\n   ? __die+0x24/0x70\n   ? page_fault_oops+0x15f/0x430\n   ? free_to_partial_list.constprop.0+0x79/0x150\n   ? do_user_addr_fault+0x2c9/0x5c0\n   ? exc_page_fault+0x63/0x110\n   ? asm_exc_page_fault+0x27/0x30\n   ? mlx5_modify_header_dealloc+0xd/0x70\n   rx_create+0x374/0x590\n   rx_add_rule+0x3ad/0x500\n   ? rx_add_rule+0x3ad/0x500\n   ? mlx5_cmd_exec+0x2c/0x40\n   ? mlx5_create_ipsec_obj+0xd6/0x200\n   mlx5e_accel_ipsec_fs_add_rule+0x31/0xf0\n   mlx5e_xfrm_add_state+0x426/0xc00\n  \u0026lt;snip\u0026gt;(CVE-2024-36281)\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\nnet: relax socket state check at accept time.\r\n\r\nChristoph reported the following splat:\r\n\r\nWARNING: CPU: 1 PID: 772 at net/ipv4/af_inet.c:761 __inet_accept+0x1f4/0x4a0\nModules linked in:\nCPU: 1 PID: 772 Comm: syz-executor510 Not tainted 6.9.0-rc7-g7da7119fe22b #56\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2.el7 04/01/2014\nRIP: 0010:__inet_accept+0x1f4/0x4a0 net/ipv4/af_inet.c:759\nCode: 04 38 84 c0 0f 85 87 00 00 00 41 c7 04 24 03 00 00 00 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 ec b7 da fd \u0026lt;0f\u0026gt; 0b e9 7f fe ff ff e8 e0 b7 da fd 0f 0b e9 fe fe ff ff 89 d9 80\nRSP: 0018:ffffc90000c2fc58 EFLAGS: 00010293\nRAX: ffffffff836bdd14 RBX: 0000000000000000 RCX: ffff888104668000\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\nRBP: dffffc0000000000 R08: ffffffff836bdb89 R09: fffff52000185f64\nR10: dffffc0000000000 R11: fffff52000185f64 R12: dffffc0000000000\nR13: 1ffff92000185f98 R14: ffff88810754d880 R15: ffff8881007b7800\nFS:  000000001c772880(0000) GS:ffff88811b280000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fb9fcf2e178 CR3: 00000001045d2002 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n inet_accept+0x138/0x1d0 net/ipv4/af_inet.c:786\n do_accept+0x435/0x620 net/socket.c:1929\n __sys_accept4_file net/socket.c:1969 [inline]\n __sys_accept4+0x9b/0x110 net/socket.c:1999\n __do_sys_accept net/socket.c:2016 [inline]\n __se_sys_accept net/socket.c:2013 [inline]\n __x64_sys_accept+0x7d/0x90 net/socket.c:2013\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x58/0x100 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x4315f9\nCode: fd ff 48 81 c4 80 00 00 00 e9 f1 fe ff ff 0f 1f 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 0f 83 ab b4 fd ff c3 66 2e 0f 1f 84 00 00 00 00\nRSP: 002b:00007ffdb26d9c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002b\nRAX: ffffffffffffffda RBX: 0000000000400300 RCX: 00000000004315f9\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004\nRBP: 00000000006e1018 R08: 0000000000400300 R09: 0000000000400300\nR10: 0000000000400300 R11: 0000000000000246 R12: 0000000000000000\nR13: 000000000040cdf0 R14: 000000000040ce80 R15: 0000000000000055\n \u0026lt;/TASK\u0026gt;\r\n\r\nThe reproducer invokes shutdown() before entering the listener status.\nAfter commit 94062790aedb (\u0026quot;tcp: defer shutdown(SEND_SHUTDOWN) for\nTCP_SYN_RECV sockets\u0026quot;), the above causes the child to reach the accept\nsyscall in FIN_WAIT1 status.\r\n\r\nEric noted we can relax the existing assertion in __inet_accept()(CVE-2024-36484)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nblk-iocost: do not WARN if iocg was already offlined\r\n\r\nIn iocg_pay_debt(), warn is triggered if \u0026apos;active_list\u0026apos; is empty, which\nis intended to confirm iocg is active when it has debt. However, warn\ncan be triggered during a blkcg or disk removal, if iocg_waitq_timer_fn()\nis run at that time:\r\n\r\n  WARNING: CPU: 0 PID: 2344971 at block/blk-iocost.c:1402 iocg_pay_debt+0x14c/0x190\n  Call trace:\n  iocg_pay_debt+0x14c/0x190\n  iocg_kick_waitq+0x438/0x4c0\n  iocg_waitq_timer_fn+0xd8/0x130\n  __run_hrtimer+0x144/0x45c\n  __hrtimer_run_queues+0x16c/0x244\n  hrtimer_interrupt+0x2cc/0x7b0\r\n\r\nThe warn in this situation is meaningless. Since this iocg is being\nremoved, the state of the \u0026apos;active_list\u0026apos; is irrelevant, and \u0026apos;waitq_timer\u0026apos;\nis canceled after removing \u0026apos;active_list\u0026apos; in ioc_pd_free(), which ensures\niocg is freed after iocg_waitq_timer_fn() returns.\r\n\r\nTherefore, add the check if iocg was already offlined to avoid warn\nwhen removing a blkcg or disk.(CVE-2024-36908)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Skip on writeback when it\u0026apos;s not applicable\r\n\r\n[WHY]\ndynamic memory safety error detector (KASAN) catches and generates error\nmessages \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot; as writeback connector does not\nsupport certain features which are not initialized.\r\n\r\n[HOW]\nSkip them when connector type is DRM_MODE_CONNECTOR_WRITEBACK.(CVE-2024-36914)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnsh: Restore skb-\u0026gt;{protocol,data,mac_header} for outer header in nsh_gso_segment().\r\n\r\nsyzbot triggered various splats (see [0] and links) by a crafted GSO\npacket of VIRTIO_NET_HDR_GSO_UDP layering the following protocols:\r\n\r\n  ETH_P_8021AD + ETH_P_NSH + ETH_P_IPV6 + IPPROTO_UDP\r\n\r\nNSH can encapsulate IPv4, IPv6, Ethernet, NSH, and MPLS.  As the inner\nprotocol can be Ethernet, NSH GSO handler, nsh_gso_segment(), calls\nskb_mac_gso_segment() to invoke inner protocol GSO handlers.\r\n\r\nnsh_gso_segment() does the following for the original skb before\ncalling skb_mac_gso_segment()\r\n\r\n  1. reset skb-\u0026gt;network_header\n  2. save the original skb-\u0026gt;{mac_heaeder,mac_len} in a local variable\n  3. pull the NSH header\n  4. resets skb-\u0026gt;mac_header\n  5. set up skb-\u0026gt;mac_len and skb-\u0026gt;protocol for the inner protocol.\r\n\r\nand does the following for the segmented skb\r\n\r\n  6. set ntohs(ETH_P_NSH) to skb-\u0026gt;protocol\n  7. push the NSH header\n  8. restore skb-\u0026gt;mac_header\n  9. set skb-\u0026gt;mac_header + mac_len to skb-\u0026gt;network_header\n 10. restore skb-\u0026gt;mac_len\r\n\r\nThere are two problems in 6-7 and 8-9.\r\n\r\n  (a)\n  After 6 \u0026amp; 7, skb-\u0026gt;data points to the NSH header, so the outer header\n  (ETH_P_8021AD in this case) is stripped when skb is sent out of netdev.\r\n\r\n  Also, if NSH is encapsulated by NSH + Ethernet (so NSH-Ethernet-NSH),\n  skb_pull() in the first nsh_gso_segment() will make skb-\u0026gt;data point\n  to the middle of the outer NSH or Ethernet header because the Ethernet\n  header is not pulled by the second nsh_gso_segment().\r\n\r\n  (b)\n  While restoring skb-\u0026gt;{mac_header,network_header} in 8 \u0026amp; 9,\n  nsh_gso_segment() does not assume that the data in the linear\n  buffer is shifted.\r\n\r\n  However, udp6_ufo_fragment() could shift the data and change\n  skb-\u0026gt;mac_header accordingly as demonstrated by syzbot.\r\n\r\n  If this happens, even the restored skb-\u0026gt;mac_header points to\n  the middle of the outer header.\r\n\r\nIt seems nsh_gso_segment() has never worked with outer headers so far.\r\n\r\nAt the end of nsh_gso_segment(), the outer header must be restored for\nthe segmented skb, instead of the NSH header.\r\n\r\nTo do that, let\u0026apos;s calculate the outer header position relatively from\nthe inner header and set skb-\u0026gt;{data,mac_header,protocol} properly.\r\n\r\n[0]:\nBUG: KMSAN: uninit-value in ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:524 [inline]\nBUG: KMSAN: uninit-value in ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline]\nBUG: KMSAN: uninit-value in ipvlan_queue_xmit+0xf44/0x16b0 drivers/net/ipvlan/ipvlan_core.c:668\n ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:524 [inline]\n ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline]\n ipvlan_queue_xmit+0xf44/0x16b0 drivers/net/ipvlan/ipvlan_core.c:668\n ipvlan_start_xmit+0x5c/0x1a0 drivers/net/ipvlan/ipvlan_main.c:222\n __netdev_start_xmit include/linux/netdevice.h:4989 [inline]\n netdev_start_xmit include/linux/netdevice.h:5003 [inline]\n xmit_one net/core/dev.c:3547 [inline]\n dev_hard_start_xmit+0x244/0xa10 net/core/dev.c:3563\n __dev_queue_xmit+0x33ed/0x51c0 net/core/dev.c:4351\n dev_queue_xmit include/linux/netdevice.h:3171 [inline]\n packet_xmit+0x9c/0x6b0 net/packet/af_packet.c:276\n packet_snd net/packet/af_packet.c:3081 [inline]\n packet_sendmsg+0x8aef/0x9f10 net/packet/af_packet.c:3113\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg net/socket.c:745 [inline]\n __sys_sendto+0x735/0xa10 net/socket.c:2191\n __do_sys_sendto net/socket.c:2203 [inline]\n __se_sys_sendto net/socket.c:2199 [inline]\n __x64_sys_sendto+0x125/0x1c0 net/socket.c:2199\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\r\n\r\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:3819 [inline]\n slab_alloc_node mm/slub.c:3860 [inline]\n __do_kmalloc_node mm/slub.c:3980 [inline]\n __kmalloc_node_track_caller+0x705/0x1000 mm/slub.c:4001\n kmalloc_reserve+0x249/0x4a0 net/core/skbuff.c:582\n __\n---truncated---(CVE-2024-36933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue\r\n\r\nFix NULL pointer data-races in sk_psock_skb_ingress_enqueue() which\nsyzbot reported [1].\r\n\r\n[1]\nBUG: KCSAN: data-race in sk_psock_drop / sk_psock_skb_ingress_enqueue\r\n\r\nwrite to 0xffff88814b3278b8 of 8 bytes by task 10724 on cpu 1:\n sk_psock_stop_verdict net/core/skmsg.c:1257 [inline]\n sk_psock_drop+0x13e/0x1f0 net/core/skmsg.c:843\n sk_psock_put include/linux/skmsg.h:459 [inline]\n sock_map_close+0x1a7/0x260 net/core/sock_map.c:1648\n unix_release+0x4b/0x80 net/unix/af_unix.c:1048\n __sock_release net/socket.c:659 [inline]\n sock_close+0x68/0x150 net/socket.c:1421\n __fput+0x2c1/0x660 fs/file_table.c:422\n __fput_sync+0x44/0x60 fs/file_table.c:507\n __do_sys_close fs/open.c:1556 [inline]\n __se_sys_close+0x101/0x1b0 fs/open.c:1541\n __x64_sys_close+0x1f/0x30 fs/open.c:1541\n do_syscall_64+0xd3/0x1d0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nread to 0xffff88814b3278b8 of 8 bytes by task 10713 on cpu 0:\n sk_psock_data_ready include/linux/skmsg.h:464 [inline]\n sk_psock_skb_ingress_enqueue+0x32d/0x390 net/core/skmsg.c:555\n sk_psock_skb_ingress_self+0x185/0x1e0 net/core/skmsg.c:606\n sk_psock_verdict_apply net/core/skmsg.c:1008 [inline]\n sk_psock_verdict_recv+0x3e4/0x4a0 net/core/skmsg.c:1202\n unix_read_skb net/unix/af_unix.c:2546 [inline]\n unix_stream_read_skb+0x9e/0xf0 net/unix/af_unix.c:2682\n sk_psock_verdict_data_ready+0x77/0x220 net/core/skmsg.c:1223\n unix_stream_sendmsg+0x527/0x860 net/unix/af_unix.c:2339\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg+0x140/0x180 net/socket.c:745\n ____sys_sendmsg+0x312/0x410 net/socket.c:2584\n ___sys_sendmsg net/socket.c:2638 [inline]\n __sys_sendmsg+0x1e9/0x280 net/socket.c:2667\n __do_sys_sendmsg net/socket.c:2676 [inline]\n __se_sys_sendmsg net/socket.c:2674 [inline]\n __x64_sys_sendmsg+0x46/0x50 net/socket.c:2674\n do_syscall_64+0xd3/0x1d0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nvalue changed: 0xffffffff83d7feb0 -\u0026gt; 0x0000000000000000\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 10713 Comm: syz-executor.4 Tainted: G        W          6.8.0-syzkaller-08951-gfe46a7dd189e #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024\r\n\r\nPrior to this, commit 4cd12c6065df (\u0026quot;bpf, sockmap: Fix NULL pointer\ndereference in sk_psock_verdict_data_ready()\u0026quot;) fixed one NULL pointer\nsimilarly due to no protection of saved_data_ready. Here is another\ndifferent caller causing the same issue because of the same reason. So\nwe should protect it with sk_callback_lock read lock because the writer\nside in the sk_psock_drop() uses \u0026quot;write_lock_bh(\u0026amp;sk-\u0026gt;sk_callback_lock);\u0026quot;.\r\n\r\nTo avoid errors that could happen in future, I move those two pairs of\nlock into the sk_psock_data_ready(), which is suggested by John Fastabend.(CVE-2024-36938)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nqibfs: fix dentry leak\r\n\r\nsimple_recursive_removal() drops the pinning references to all positives\nin subtree.  For the cases when its argument has been kept alive by\nthe pinning alone that\u0026apos;s exactly the right thing to do, but here\nthe argument comes from dcache lookup, that needs to be balanced by\nexplicit dput().\r\n\r\nFucked-up-by: Al Viro \u0026lt;viro@zeniv.linux.org.uk\u0026gt;(CVE-2024-36947)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map()\r\n\r\nIf we fail to allocate propname buffer, we need to drop the reference\ncount we just took. Because the pinctrl_dt_free_maps() includes the\ndroping operation, here we call it directly.(CVE-2024-36959)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails\r\n\r\nCalling a6xx_destroy() before adreno_gpu_init() leads to a null pointer\ndereference on:\r\n\r\nmsm_gpu_cleanup() : platform_set_drvdata(gpu-\u0026gt;pdev, NULL);\r\n\r\nas gpu-\u0026gt;pdev is only assigned in:\r\n\r\na6xx_gpu_init()\n|_ adreno_gpu_init\n    |_ msm_gpu_init()\r\n\r\nInstead of relying on handwavy null checks down the cleanup chain,\nexplicitly de-allocate the LLC data and free a6xx_gpu instead.\r\n\r\nPatchwork: https://patchwork.freedesktop.org/patch/588919/(CVE-2024-38390)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw\r\n\r\nWhen running blktests nvme/rdma, the following kmemleak issue will appear.\r\n\r\nkmemleak: Kernel memory leak detector initialized (mempool available:36041)\nkmemleak: Automatic memory scanning thread started\nkmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\nkmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\nkmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\nkmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\r\n\r\nunreferenced object 0xffff88855da53400 (size 192):\n  comm \u0026quot;rdma\u0026quot;, pid 10630, jiffies 4296575922\n  hex dump (first 32 bytes):\n    37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00  7...............\n    10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff  .4.].....4.]....\n  backtrace (crc 47f66721):\n    [\u0026lt;ffffffff911251bd\u0026gt;] kmalloc_trace+0x30d/0x3b0\n    [\u0026lt;ffffffffc2640ff7\u0026gt;] alloc_gid_entry+0x47/0x380 [ib_core]\n    [\u0026lt;ffffffffc2642206\u0026gt;] add_modify_gid+0x166/0x930 [ib_core]\n    [\u0026lt;ffffffffc2643468\u0026gt;] ib_cache_update.part.0+0x6d8/0x910 [ib_core]\n    [\u0026lt;ffffffffc2644e1a\u0026gt;] ib_cache_setup_one+0x24a/0x350 [ib_core]\n    [\u0026lt;ffffffffc263949e\u0026gt;] ib_register_device+0x9e/0x3a0 [ib_core]\n    [\u0026lt;ffffffffc2a3d389\u0026gt;] 0xffffffffc2a3d389\n    [\u0026lt;ffffffffc2688cd8\u0026gt;] nldev_newlink+0x2b8/0x520 [ib_core]\n    [\u0026lt;ffffffffc2645fe3\u0026gt;] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]\n    [\u0026lt;ffffffffc264648c\u0026gt;]\nrdma_nl_rcv_skb.constprop.0.isra.0+0x23c/0x3a0 [ib_core]\n    [\u0026lt;ffffffff9270e7b5\u0026gt;] netlink_unicast+0x445/0x710\n    [\u0026lt;ffffffff9270f1f1\u0026gt;] netlink_sendmsg+0x761/0xc40\n    [\u0026lt;ffffffff9249db29\u0026gt;] __sys_sendto+0x3a9/0x420\n    [\u0026lt;ffffffff9249dc8c\u0026gt;] __x64_sys_sendto+0xdc/0x1b0\n    [\u0026lt;ffffffff92db0ad3\u0026gt;] do_syscall_64+0x93/0x180\n    [\u0026lt;ffffffff92e00126\u0026gt;] entry_SYSCALL_64_after_hwframe+0x71/0x79\r\n\r\nThe root cause: rdma_put_gid_attr is not called when sgid_attr is set\nto ERR_PTR(-ENODEV).(CVE-2024-38539)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/test_hmm.c: handle src_pfns and dst_pfns allocation failure\r\n\r\nThe kcalloc() in dmirror_device_evict_chunk() will return null if the\nphysical memory has run out.  As a result, if src_pfns or dst_pfns is\ndereferenced, the null pointer dereference bug will happen.\r\n\r\nMoreover, the device is going away.  If the kcalloc() fails, the pages\nmapping a chunk could not be evicted.  So add a __GFP_NOFAIL flag in\nkcalloc().\r\n\r\nFinally, as there is no need to have physically contiguous memory, Switch\nkcalloc() to kvcalloc() in order to avoid failing allocations.(CVE-2024-38543)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/rxe: Fix seg fault in rxe_comp_queue_pkt\r\n\r\nIn rxe_comp_queue_pkt() an incoming response packet skb is enqueued to the\nresp_pkts queue and then a decision is made whether to run the completer\ntask inline or schedule it. Finally the skb is dereferenced to bump a \u0026apos;hw\u0026apos;\nperformance counter. This is wrong because if the completer task is\nalready running in a separate thread it may have already processed the skb\nand freed it which can cause a seg fault.  This has been observed\ninfrequently in testing at high scale.\r\n\r\nThis patch fixes this by changing the order of enqueuing the packet until\nafter the counter is accessed.(CVE-2024-38544)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: vc4: Fix possible null pointer dereference\r\n\r\nIn vc4_hdmi_audio_init() of_get_address() may return\nNULL which is later dereferenced. Fix this bug by adding NULL check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38546)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: kirkwood: Fix potential NULL dereference\r\n\r\nIn kirkwood_dma_hw_params() mv_mbus_dram_info() returns NULL if\nCONFIG_PLAT_ORION macro is not defined.\nFix this bug by adding NULL check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38550)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Reload only IB representors upon lag disable/enable\r\n\r\nOn lag disable, the bond IB device along with all of its\nrepresentors are destroyed, and then the slaves\u0026apos; representors get reloaded.\r\n\r\nIn case the slave IB representor load fails, the eswitch error flow\nunloads all representors, including ethernet representors, where the\nnetdevs get detached and removed from lag bond. Such flow is inaccurate\nas the lag driver is not responsible for loading/unloading ethernet\nrepresentors. Furthermore, the flow described above begins by holding\nlag lock to prevent bond changes during disable flow. However, when\nreaching the ethernet representors detachment from lag, the lag lock is\nrequired again, triggering the following deadlock:\r\n\r\nCall trace:\n__switch_to+0xf4/0x148\n__schedule+0x2c8/0x7d0\nschedule+0x50/0xe0\nschedule_preempt_disabled+0x18/0x28\n__mutex_lock.isra.13+0x2b8/0x570\n__mutex_lock_slowpath+0x1c/0x28\nmutex_lock+0x4c/0x68\nmlx5_lag_remove_netdev+0x3c/0x1a0 [mlx5_core]\nmlx5e_uplink_rep_disable+0x70/0xa0 [mlx5_core]\nmlx5e_detach_netdev+0x6c/0xb0 [mlx5_core]\nmlx5e_netdev_change_profile+0x44/0x138 [mlx5_core]\nmlx5e_netdev_attach_nic_profile+0x28/0x38 [mlx5_core]\nmlx5e_vport_rep_unload+0x184/0x1b8 [mlx5_core]\nmlx5_esw_offloads_rep_load+0xd8/0xe0 [mlx5_core]\nmlx5_eswitch_reload_reps+0x74/0xd0 [mlx5_core]\nmlx5_disable_lag+0x130/0x138 [mlx5_core]\nmlx5_lag_disable_change+0x6c/0x70 [mlx5_core] // hold ldev-\u0026gt;lock\nmlx5_devlink_eswitch_mode_set+0xc0/0x410 [mlx5_core]\ndevlink_nl_cmd_eswitch_set_doit+0xdc/0x180\ngenl_family_rcv_msg_doit.isra.17+0xe8/0x138\ngenl_rcv_msg+0xe4/0x220\nnetlink_rcv_skb+0x44/0x108\ngenl_rcv+0x40/0x58\nnetlink_unicast+0x198/0x268\nnetlink_sendmsg+0x1d4/0x418\nsock_sendmsg+0x54/0x60\n__sys_sendto+0xf4/0x120\n__arm64_sys_sendto+0x30/0x40\nel0_svc_common+0x8c/0x120\ndo_el0_svc+0x30/0xa0\nel0_svc+0x20/0x30\nel0_sync_handler+0x90/0xb8\nel0_sync+0x160/0x180\r\n\r\nThus, upon lag enable/disable, load and unload only the IB representors\nof the slaves preventing the deadlock mentioned above.\r\n\r\nWhile at it, refactor the mlx5_esw_offloads_rep_load() function to have\na static helper method for its internal logic, in symmetry with the\nrepresentor unload design.(CVE-2024-38557)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: bfa: Ensure the copied buf is NUL terminated\r\n\r\nCurrently, we allocate a nbytes-sized kernel buffer and copy nbytes from\nuserspace to that buffer. Later, we use sscanf on this buffer but we don\u0026apos;t\nensure that the string is terminated inside the buffer, this can lead to\nOOB read when using sscanf. Fix this issue by using memdup_user_nul instead\nof memdup_user.(CVE-2024-38560)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkunit: Fix kthread reference\r\n\r\nThere is a race condition when a kthread finishes after the deadline and\nbefore the call to kthread_stop(), which may lead to use after free.(CVE-2024-38561)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ar5523: enable proper endpoint verification\r\n\r\nSyzkaller reports [1] hitting a warning about an endpoint in use\nnot having an expected type to it.\r\n\r\nFix the issue by checking for the existence of all proper\nendpoints with their according types intact.\r\n\r\nSadly, this patch has not been tested on real hardware.\r\n\r\n[1] Syzkaller report:\n------------[ cut here ]------------\nusb 1-1: BOGUS urb xfer, pipe 3 != type 1\nWARNING: CPU: 0 PID: 3643 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ar5523_cmd+0x41b/0x780 drivers/net/wireless/ath/ar5523/ar5523.c:275\n ar5523_cmd_read drivers/net/wireless/ath/ar5523/ar5523.c:302 [inline]\n ar5523_host_available drivers/net/wireless/ath/ar5523/ar5523.c:1376 [inline]\n ar5523_probe+0x14b0/0x1d10 drivers/net/wireless/ath/ar5523/ar5523.c:1655\n usb_probe_interface+0x30f/0x7f0 drivers/usb/core/driver.c:396\n call_driver_probe drivers/base/dd.c:560 [inline]\n really_probe+0x249/0xb90 drivers/base/dd.c:639\n __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808\n __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936\n bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427\n __device_attach+0x1e4/0x530 drivers/base/dd.c:1008\n bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487\n device_add+0xbd9/0x1e90 drivers/base/core.c:3517\n usb_set_configuration+0x101d/0x1900 drivers/usb/core/message.c:2170\n usb_generic_driver_probe+0xbe/0x100 drivers/usb/core/generic.c:238\n usb_probe_device+0xd8/0x2c0 drivers/usb/core/driver.c:293\n call_driver_probe drivers/base/dd.c:560 [inline]\n really_probe+0x249/0xb90 drivers/base/dd.c:639\n __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808\n __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936\n bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427\n __device_attach+0x1e4/0x530 drivers/base/dd.c:1008\n bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487\n device_add+0xbd9/0x1e90 drivers/base/core.c:3517\n usb_new_device.cold+0x685/0x10ad drivers/usb/core/hub.c:2573\n hub_port_connect drivers/usb/core/hub.c:5353 [inline]\n hub_port_connect_change drivers/usb/core/hub.c:5497 [inline]\n port_event drivers/usb/core/hub.c:5653 [inline]\n hub_event+0x26cb/0x45d0 drivers/usb/core/hub.c:5735\n process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289\n worker_thread+0x669/0x1090 kernel/workqueue.c:2436\n kthread+0x2e8/0x3a0 kernel/kthread.c:376\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306\n \u0026lt;/TASK\u0026gt;(CVE-2024-38565)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Fix verifier assumptions about socket-\u0026gt;sk\r\n\r\nThe verifier assumes that \u0026apos;sk\u0026apos; field in \u0026apos;struct socket\u0026apos; is valid\nand non-NULL when \u0026apos;socket\u0026apos; pointer itself is trusted and non-NULL.\nThat may not be the case when socket was just created and\npassed to LSM socket_accept hook.\nFix this verifier assumption and adjust tests.(CVE-2024-38566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nepoll: be better about file lifetimes\r\n\r\nepoll can call out to vfs_poll() with a file pointer that may race with\nthe last \u0026apos;fput()\u0026apos;. That would make f_count go down to zero, and while\nthe ep-\u0026gt;mtx locking means that the resulting file pointer tear-down will\nbe blocked until the poll returns, it means that f_count is already\ndead, and any use of it won\u0026apos;t actually get a reference to the file any\nmore: it\u0026apos;s dead regardless.\r\n\r\nMake sure we have a valid ref on the file pointer before we call down to\nvfs_poll() from the epoll routines.(CVE-2024-38580)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: micrel: Fix receiving the timestamp in the frame for lan8841\r\n\r\nThe blamed commit started to use the ptp workqueue to get the second\npart of the timestamp. And when the port was set down, then this\nworkqueue is stopped. But if the config option NETWORK_PHY_TIMESTAMPING\nis not enabled, then the ptp_clock is not initialized so then it would\ncrash when it would try to access the delayed work.\nSo then basically by setting up and then down the port, it would crash.\nThe fix consists in checking if the ptp_clock is initialized and only\nthen cancel the delayed work.(CVE-2024-38593)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\neth: sungem: remove .ndo_poll_controller to avoid deadlocks\r\n\r\nErhard reports netpoll warnings from sungem:\r\n\r\n  netpoll_send_skb_on_dev(): eth0 enabled interrupts in poll (gem_start_xmit+0x0/0x398)\n  WARNING: CPU: 1 PID: 1 at net/core/netpoll.c:370 netpoll_send_skb+0x1fc/0x20c\r\n\r\ngem_poll_controller() disables interrupts, which may sleep.\nWe can\u0026apos;t sleep in netpoll, it has interrupts disabled completely.\nStrangely, gem_poll_controller() doesn\u0026apos;t even poll the completions,\nand instead acts as if an interrupt has fired so it just schedules\nNAPI and exits. None of this has been necessary for years, since\nnetpoll invokes NAPI directly.(CVE-2024-38597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: i2c: et8ek8: Don\u0026apos;t strip remove function when driver is builtin\r\n\r\nUsing __exit for the remove function results in the remove callback\nbeing discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets\nunbound (e.g. using sysfs or hotplug), the driver is just removed\nwithout the cleanup being performed. This results in resource leaks. Fix\nit by compiling in the remove callback unconditionally.\r\n\r\nThis also fixes a W=1 modpost warning:\r\n\r\n\tWARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -\u0026gt; et8ek8_remove (section: .exit.text)(CVE-2024-38611)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nm68k: Fix spinlock race in kernel thread creation\r\n\r\nContext switching does take care to retain the correct lock owner across\nthe switch from \u0026apos;prev\u0026apos; to \u0026apos;next\u0026apos; tasks.  This does rely on interrupts\nremaining disabled for the entire duration of the switch.\r\n\r\nThis condition is guaranteed for normal process creation and context\nswitching between already running processes, because both \u0026apos;prev\u0026apos; and\n\u0026apos;next\u0026apos; already have interrupts disabled in their saved copies of the\nstatus register.\r\n\r\nThe situation is different for newly created kernel threads.  The status\nregister is set to PS_S in copy_thread(), which does leave the IPL at 0.\nUpon restoring the \u0026apos;next\u0026apos; thread\u0026apos;s status register in switch_to() aka\nresume(), interrupts then become enabled prematurely.  resume() then\nreturns via ret_from_kernel_thread() and schedule_tail() where run queue\nlock is released (see finish_task_switch() and finish_lock_switch()).\r\n\r\nA timer interrupt calling scheduler_tick() before the lock is released\nin finish_task_switch() will find the lock already taken, with the\ncurrent task as lock owner.  This causes a spinlock recursion warning as\nreported by Guenter Roeck.\r\n\r\nAs far as I can ascertain, this race has been opened in commit\n533e6903bea0 (\u0026quot;m68k: split ret_from_fork(), simplify kernel_thread()\u0026quot;)\nbut I haven\u0026apos;t done a detailed study of kernel history so it may well\npredate that commit.\r\n\r\nInterrupts cannot be disabled in the saved status register copy for\nkernel threads (init will complain about interrupts disabled when\nfinally starting user space).  Disable interrupts temporarily when\nswitching the tasks\u0026apos; register sets in resume().\r\n\r\nNote that a simple oriw 0x700,%sr after restoring sr is not enough here\n- this leaves enough of a race for the \u0026apos;spinlock recursion\u0026apos; warning to\nstill be observed.\r\n\r\nTested on ARAnyM and qemu (Quadra 800 emulation).(CVE-2024-38613)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: carl9170: re-fix fortified-memset warning\r\n\r\nThe carl9170_tx_release() function sometimes triggers a fortified-memset\nwarning in my randconfig builds:\r\n\r\nIn file included from include/linux/string.h:254,\n                 from drivers/net/wireless/ath/carl9170/tx.c:40:\nIn function \u0026apos;fortify_memset_chk\u0026apos;,\n    inlined from \u0026apos;carl9170_tx_release\u0026apos; at drivers/net/wireless/ath/carl9170/tx.c:283:2,\n    inlined from \u0026apos;kref_put\u0026apos; at include/linux/kref.h:65:3,\n    inlined from \u0026apos;carl9170_tx_put_skb\u0026apos; at drivers/net/wireless/ath/carl9170/tx.c:342:9:\ninclude/linux/fortify-string.h:493:25: error: call to \u0026apos;__write_overflow_field\u0026apos; declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]\n  493 |                         __write_overflow_field(p_size_field, size);\r\n\r\nKees previously tried to avoid this by using memset_after(), but it seems\nthis does not fully address the problem. I noticed that the memset_after()\nhere is done on a different part of the union (status) than the original\ncast was from (rate_driver_data), which may confuse the compiler.\r\n\r\nUnfortunately, the memset_after() trick does not work on driver_rates[]\nbecause that is part of an anonymous struct, and I could not get\nstruct_group() to do this either. Using two separate memset() calls\non the two members does address the warning though.(CVE-2024-38616)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nstm class: Fix a double free in stm_register_device()\r\n\r\nThe put_device(\u0026amp;stm-\u0026gt;dev) call will trigger stm_device_release() which\nfrees \u0026quot;stm\u0026quot; so the vfree(stm) on the next line is a double free.(CVE-2024-38627)\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\next4: fix mb_cache_entry\u0026apos;s e_refcnt leak in ext4_xattr_block_cache_find()\r\n\r\nSyzbot reports a warning as follows:\r\n\r\n============================================\nWARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290\nModules linked in:\nCPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7\nRIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375\n generic_shutdown_super+0x136/0x2d0 fs/super.c:641\n kill_block_super+0x44/0x90 fs/super.c:1675\n ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327\n[...]\n============================================\r\n\r\nThis is because when finding an entry in ext4_xattr_block_cache_find(), if\next4_sb_bread() returns -ENOMEM, the ce\u0026apos;s e_refcnt, which has already grown\nin the __entry_find(), won\u0026apos;t be put away, and eventually trigger the above\nissue in mb_cache_destroy() due to reference count leakage.\r\n\r\nSo call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.(CVE-2024-39276)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/memory-failure: fix handling of dissolved but not taken off from buddy pages\r\n\r\nWhen I did memory failure tests recently, below panic occurs:\r\n\r\npage: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00\nflags: 0x6fffe0000000000(node=1|zone=2|lastcpupid=0x7fff)\nraw: 06fffe0000000000 dead000000000100 dead000000000122 0000000000000000\nraw: 0000000000000000 0000000000000009 00000000ffffffff 0000000000000000\npage dumped because: VM_BUG_ON_PAGE(!PageBuddy(page))\n------------[ cut here ]------------\nkernel BUG at include/linux/page-flags.h:1009!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:__del_page_from_free_list+0x151/0x180\nRSP: 0018:ffffa49c90437998 EFLAGS: 00000046\nRAX: 0000000000000035 RBX: 0000000000000009 RCX: ffff8dd8dfd1c9c8\nRDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff8dd8dfd1c9c0\nRBP: ffffd901233b8000 R08: ffffffffab5511f8 R09: 0000000000008c69\nR10: 0000000000003c15 R11: ffffffffab5511f8 R12: ffff8dd8fffc0c80\nR13: 0000000000000001 R14: ffff8dd8fffc0c80 R15: 0000000000000009\nFS:  00007ff916304740(0000) GS:ffff8dd8dfd00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000055eae50124c8 CR3: 00000008479e0000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __rmqueue_pcplist+0x23b/0x520\n get_page_from_freelist+0x26b/0xe40\n __alloc_pages_noprof+0x113/0x1120\n __folio_alloc_noprof+0x11/0xb0\n alloc_buddy_hugetlb_folio.isra.0+0x5a/0x130\n __alloc_fresh_hugetlb_folio+0xe7/0x140\n alloc_pool_huge_folio+0x68/0x100\n set_max_huge_pages+0x13d/0x340\n hugetlb_sysctl_handler_common+0xe8/0x110\n proc_sys_call_handler+0x194/0x280\n vfs_write+0x387/0x550\n ksys_write+0x64/0xe0\n do_syscall_64+0xc2/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7ff916114887\nRSP: 002b:00007ffec8a2fd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 000055eae500e350 RCX: 00007ff916114887\nRDX: 0000000000000004 RSI: 000055eae500e390 RDI: 0000000000000003\nRBP: 000055eae50104c0 R08: 0000000000000000 R09: 000055eae50104c0\nR10: 0000000000000077 R11: 0000000000000246 R12: 0000000000000004\nR13: 0000000000000004 R14: 00007ff916216b80 R15: 00007ff916216a00\n \u0026lt;/TASK\u0026gt;\nModules linked in: mce_inject hwpoison_inject\n---[ end trace 0000000000000000 ]---\r\n\r\nAnd before the panic, there had an warning about bad page state:\r\n\r\nBUG: Bad page state in process page-types  pfn:8cee00\npage: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00\nflags: 0x6fffe0000000000(node=1|zone=2|lastcpupid=0x7fff)\npage_type: 0xffffff7f(buddy)\nraw: 06fffe0000000000 ffffd901241c0008 ffffd901240f8008 0000000000000000\nraw: 0000000000000000 0000000000000009 00000000ffffff7f 0000000000000000\npage dumped because: nonzero mapcount\nModules linked in: mce_inject hwpoison_inject\nCPU: 8 PID: 154211 Comm: page-types Not tainted 6.9.0-rc4-00499-g5544ec3178e2-dirty #22\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x83/0xa0\n bad_page+0x63/0xf0\n free_unref_page+0x36e/0x5c0\n unpoison_memory+0x50b/0x630\n simple_attr_write_xsigned.constprop.0.isra.0+0xb3/0x110\n debugfs_attr_write+0x42/0x60\n full_proxy_write+0x5b/0x80\n vfs_write+0xcd/0x550\n ksys_write+0x64/0xe0\n do_syscall_64+0xc2/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f189a514887\nRSP: 002b:00007ffdcd899718 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f189a514887\nRDX: 0000000000000009 RSI: 00007ffdcd899730 RDI: 0000000000000003\nRBP: 00007ffdcd8997a0 R08: 0000000000000000 R09: 00007ffdcd8994b2\nR10: 0000000000000000 R11: 0000000000000246 R12: 00007ffdcda199a8\nR13: 0000000000404af1 R14: 000000000040ad78 R15: 00007f189a7a5040\n \u0026lt;/TASK\u0026gt;\r\n\r\nThe root cause should be the below race:\r\n\r\n memory_failure\n  try_memory_failure_hugetlb\n   me_huge_page\n    __page_handle_poison\n     dissolve_free_hugetlb_folio\n     drain_all_pages -- Buddy page can be isolated e.g. for compaction.\n     take_page_off_buddy -- Failed as page is not in the \n---truncated---(CVE-2024-39298)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING\r\n\r\nXiao reported that lvm2 test lvconvert-raid-takeover.sh can hang with\nsmall possibility, the root cause is exactly the same as commit\nbed9e27baf52 (\u0026quot;Revert \u0026quot;md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\u0026quot;\u0026quot;)\r\n\r\nHowever, Dan reported another hang after that, and junxiao investigated\nthe problem and found out that this is caused by plugged bio can\u0026apos;t issue\nfrom raid5d().\r\n\r\nCurrent implementation in raid5d() has a weird dependence:\r\n\r\n1) md_check_recovery() from raid5d() must hold \u0026apos;reconfig_mutex\u0026apos; to clear\n   MD_SB_CHANGE_PENDING;\n2) raid5d() handles IO in a deadloop, until all IO are issued;\n3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared;\r\n\r\nThis behaviour is introduce before v2.6, and for consequence, if other\ncontext hold \u0026apos;reconfig_mutex\u0026apos;, and md_check_recovery() can\u0026apos;t update\nsuper_block, then raid5d() will waste one cpu 100% by the deadloop, until\n\u0026apos;reconfig_mutex\u0026apos; is released.\r\n\r\nRefer to the implementation from raid1 and raid10, fix this problem by\nskipping issue IO if MD_SB_CHANGE_PENDING is still set after\nmd_check_recovery(), daemon thread will be woken up when \u0026apos;reconfig_mutex\u0026apos;\nis released. Meanwhile, the hang problem will be fixed as well.(CVE-2024-39476)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: sr: fix missing sk_buff release in seg6_input_core\r\n\r\nThe seg6_input() function is responsible for adding the SRH into a\npacket, delegating the operation to the seg6_input_core(). This function\nuses the skb_cow_head() to ensure that there is sufficient headroom in\nthe sk_buff for accommodating the link-layer header.\nIn the event that the skb_cow_header() function fails, the\nseg6_input_core() catches the error but it does not release the sk_buff,\nwhich will result in a memory leak.\r\n\r\nThis issue was introduced in commit af3b5158b89d (\u0026quot;ipv6: sr: fix BUG due\nto headroom too small after SRH push\u0026quot;) and persists even after commit\n7a3f5b0de364 (\u0026quot;netfilter: add netfilter hooks to SRv6 data plane\u0026quot;),\nwhere the entire seg6_input() code was refactored to deal with netfilter\nhooks.\r\n\r\nThe proposed patch addresses the identified memory leak by requiring the\nseg6_input_core() function to release the sk_buff in the event that\nskb_cow_head() fails.(CVE-2024-39490)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: hda: cs35l56: Fix lifetime of cs_dsp instance\r\n\r\nThe cs_dsp instance is initialized in the driver probe() so it\nshould be freed in the driver remove(). Also fix a missing call\nto cs_dsp_remove() in the error path of cs35l56_hda_common_probe().\r\n\r\nThe call to cs_dsp_remove() was being done in the component unbind\ncallback cs35l56_hda_unbind(). This meant that if the driver was\nunbound and then re-bound it would be using an uninitialized cs_dsp\ninstance.\r\n\r\nIt is best to initialize the cs_dsp instance in probe() so that it\ncan return an error if it fails. The component binding API doesn\u0026apos;t\nhave any error handling so there\u0026apos;s no way to handle a failure if\ncs_dsp was initialized in the bind.(CVE-2024-39491)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrivers: core: synchronize really_probe() and dev_uevent()\r\n\r\nSynchronize the dev-\u0026gt;driver usage in really_probe() and dev_uevent().\nThese can run in different threads, what can result in the following\nrace condition for dev-\u0026gt;driver uninitialization:\r\n\r\nThread #1:\n==========\r\n\r\nreally_probe() {\n...\nprobe_failed:\n...\ndevice_unbind_cleanup(dev) {\n    ...\n    dev-\u0026gt;driver = NULL;   // \u0026lt;= Failed probe sets dev-\u0026gt;driver to NULL\n    ...\n    }\n...\n}\r\n\r\nThread #2:\n==========\r\n\r\ndev_uevent() {\n...\nif (dev-\u0026gt;driver)\n      // If dev-\u0026gt;driver is NULLed from really_probe() from here on,\n      // after above check, the system crashes\n      add_uevent_var(env, \u0026quot;DRIVER=%s\u0026quot;, dev-\u0026gt;driver-\u0026gt;name);\n...\n}\r\n\r\nreally_probe() holds the lock, already. So nothing needs to be done\nthere. dev_uevent() is called with lock held, often, too. But not\nalways. What implies that we can\u0026apos;t add any locking in dev_uevent()\nitself. So fix this race by adding the lock to the non-protected\npath. This is the path where above race is observed:\r\n\r\n dev_uevent+0x235/0x380\n uevent_show+0x10c/0x1f0  \u0026lt;= Add lock here\n dev_attr_show+0x3a/0xa0\n sysfs_kf_seq_show+0x17c/0x250\n kernfs_seq_show+0x7c/0x90\n seq_read_iter+0x2d7/0x940\n kernfs_fop_read_iter+0xc6/0x310\n vfs_read+0x5bc/0x6b0\n ksys_read+0xeb/0x1b0\n __x64_sys_read+0x42/0x50\n x64_sys_call+0x27ad/0x2d30\n do_syscall_64+0xcd/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nSimilar cases are reported by syzkaller in\r\n\r\nhttps://syzkaller.appspot.com/bug?extid=ffa8143439596313a85a\r\n\r\nBut these are regarding the *initialization* of dev-\u0026gt;driver\r\n\r\ndev-\u0026gt;driver = drv;\r\n\r\nAs this switches dev-\u0026gt;driver to non-NULL these reports can be considered\nto be false-positives (which should be \u0026quot;fixed\u0026quot; by this commit, as well,\nthough).\r\n\r\nThe same issue was reported and tried to be fixed back in 2015 in\r\n\r\nhttps://lore.kernel.org/lkml/1421259054-2574-1-git-send-email-a.sangwan@samsung.com/\r\n\r\nalready.(CVE-2024-39501)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nft_inner: validate mandatory meta and payload\r\n\r\nCheck for mandatory netlink attributes in payload and meta expression\nwhen used embedded from the inner expression, otherwise NULL pointer\ndereference is possible from userspace.(CVE-2024-39504)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory\r\n\r\nThere is a potential out-of-bounds access when using test_bit() on a single\nword. The test_bit() and set_bit() functions operate on long values, and\nwhen testing or setting a single word, they can exceed the word\nboundary. KASAN detects this issue and produces a dump:\r\n\r\n\t BUG: KASAN: slab-out-of-bounds in _scsih_add_device.constprop.0 (./arch/x86/include/asm/bitops.h:60 ./include/asm-generic/bitops/instrumented-atomic.h:29 drivers/scsi/mpt3sas/mpt3sas_scsih.c:7331) mpt3sas\r\n\r\n\t Write of size 8 at addr ffff8881d26e3c60 by task kworker/u1536:2/2965\r\n\r\nFor full log, please look at [1].\r\n\r\nMake the allocation at least the size of sizeof(unsigned long) so that\nset_bit() and test_bit() have sufficient room for read/write operations\nwithout overwriting unallocated memory.\r\n\r\n[1] Link: https://lore.kernel.org/all/ZkNcALr3W3KGYYJG@gmail.com/(CVE-2024-40901)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nax25: Fix refcount imbalance on inbound connections\r\n\r\nWhen releasing a socket in ax25_release(), we call netdev_put() to\ndecrease the refcount on the associated ax.25 device. However, the\nexecution path for accepting an incoming connection never calls\nnetdev_hold(). This imbalance leads to refcount errors, and ultimately\nto kernel crashes.\r\n\r\nA typical call trace for the above situation will start with one of the\nfollowing errors:\r\n\r\n    refcount_t: decrement hit 0; leaking memory.\n    refcount_t: underflow; use-after-free.\r\n\r\nAnd will then have a trace like:\r\n\r\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    ? show_regs+0x64/0x70\n    ? __warn+0x83/0x120\n    ? refcount_warn_saturate+0xb2/0x100\n    ? report_bug+0x158/0x190\n    ? prb_read_valid+0x20/0x30\n    ? handle_bug+0x3e/0x70\n    ? exc_invalid_op+0x1c/0x70\n    ? asm_exc_invalid_op+0x1f/0x30\n    ? refcount_warn_saturate+0xb2/0x100\n    ? refcount_warn_saturate+0xb2/0x100\n    ax25_release+0x2ad/0x360\n    __sock_release+0x35/0xa0\n    sock_close+0x19/0x20\n    [...]\r\n\r\nOn reboot (or any attempt to remove the interface), the kernel gets\nstuck in an infinite loop:\r\n\r\n    unregister_netdevice: waiting for ax0 to become free. Usage count = 0\r\n\r\nThis patch corrects these issues by ensuring that we call netdev_hold()\nand ax25_dev_hold() for new connections in ax25_accept(). This makes the\nlogic leading to ax25_accept() match the logic for ax25_bind(): in both\ncases we increment the refcount, which is ultimately decremented in\nax25_release().(CVE-2024-40910)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: cfg80211: Lock wiphy in cfg80211_get_station\r\n\r\nWiphy should be locked before calling rdev_get_station() (see lockdep\nassert in ieee80211_get_station()).\r\n\r\nThis fixes the following kernel NULL dereference:\r\n\r\n Unable to handle kernel NULL pointer dereference at virtual address 0000000000000050\n Mem abort info:\n   ESR = 0x0000000096000006\n   EC = 0x25: DABT (current EL), IL = 32 bits\n   SET = 0, FnV = 0\n   EA = 0, S1PTW = 0\n   FSC = 0x06: level 2 translation fault\n Data abort info:\n   ISV = 0, ISS = 0x00000006\n   CM = 0, WnR = 0\n user pgtable: 4k pages, 48-bit VAs, pgdp=0000000003001000\n [0000000000000050] pgd=0800000002dca003, p4d=0800000002dca003, pud=08000000028e9003, pmd=0000000000000000\n Internal error: Oops: 0000000096000006 [#1] SMP\n Modules linked in: netconsole dwc3_meson_g12a dwc3_of_simple dwc3 ip_gre gre ath10k_pci ath10k_core ath9k ath9k_common ath9k_hw ath\n CPU: 0 PID: 1091 Comm: kworker/u8:0 Not tainted 6.4.0-02144-g565f9a3a7911-dirty #705\n Hardware name: RPT (r1) (DT)\n Workqueue: bat_events batadv_v_elp_throughput_metric_update\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : ath10k_sta_statistics+0x10/0x2dc [ath10k_core]\n lr : sta_set_sinfo+0xcc/0xbd4\n sp : ffff000007b43ad0\n x29: ffff000007b43ad0 x28: ffff0000071fa900 x27: ffff00000294ca98\n x26: ffff000006830880 x25: ffff000006830880 x24: ffff00000294c000\n x23: 0000000000000001 x22: ffff000007b43c90 x21: ffff800008898acc\n x20: ffff00000294c6e8 x19: ffff000007b43c90 x18: 0000000000000000\n x17: 445946354d552d78 x16: 62661f7200000000 x15: 57464f445946354d\n x14: 0000000000000000 x13: 00000000000000e3 x12: d5f0acbcebea978e\n x11: 00000000000000e3 x10: 000000010048fe41 x9 : 0000000000000000\n x8 : ffff000007b43d90 x7 : 000000007a1e2125 x6 : 0000000000000000\n x5 : ffff0000024e0900 x4 : ffff800000a0250c x3 : ffff000007b43c90\n x2 : ffff00000294ca98 x1 : ffff000006831920 x0 : 0000000000000000\n Call trace:\n  ath10k_sta_statistics+0x10/0x2dc [ath10k_core]\n  sta_set_sinfo+0xcc/0xbd4\n  ieee80211_get_station+0x2c/0x44\n  cfg80211_get_station+0x80/0x154\n  batadv_v_elp_get_throughput+0x138/0x1fc\n  batadv_v_elp_throughput_metric_update+0x1c/0xa4\n  process_one_work+0x1ec/0x414\n  worker_thread+0x70/0x46c\n  kthread+0xdc/0xe0\n  ret_from_fork+0x10/0x20\n Code: a9bb7bfd 910003fd a90153f3 f9411c40 (f9402814)\r\n\r\nThis happens because STA has time to disconnect and reconnect before\nbatadv_v_elp_throughput_metric_update() delayed work gets scheduled. In\nthis situation, ath10k_sta_state() can be in the middle of resetting\narsta data when the work queue get chance to be scheduled and ends up\naccessing it. Locking wiphy prevents that.(CVE-2024-40911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/huge_memory: don\u0026apos;t unpoison huge_zero_folio\r\n\r\nWhen I did memory failure tests recently, below panic occurs:\r\n\r\n kernel BUG at include/linux/mm.h:1135!\n invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n CPU: 9 PID: 137 Comm: kswapd1 Not tainted 6.9.0-rc4-00491-gd5ce28f156fe-dirty #14\n RIP: 0010:shrink_huge_zero_page_scan+0x168/0x1a0\n RSP: 0018:ffff9933c6c57bd0 EFLAGS: 00000246\n RAX: 000000000000003e RBX: 0000000000000000 RCX: ffff88f61fc5c9c8\n RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff88f61fc5c9c0\n RBP: ffffcd7c446b0000 R08: ffffffff9a9405f0 R09: 0000000000005492\n R10: 00000000000030ea R11: ffffffff9a9405f0 R12: 0000000000000000\n R13: 0000000000000000 R14: 0000000000000000 R15: ffff88e703c4ac00\n FS:  0000000000000000(0000) GS:ffff88f61fc40000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055f4da6e9878 CR3: 0000000c71048000 CR4: 00000000000006f0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  do_shrink_slab+0x14f/0x6a0\n  shrink_slab+0xca/0x8c0\n  shrink_node+0x2d0/0x7d0\n  balance_pgdat+0x33a/0x720\n  kswapd+0x1f3/0x410\n  kthread+0xd5/0x100\n  ret_from_fork+0x2f/0x50\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\n Modules linked in: mce_inject hwpoison_inject\n ---[ end trace 0000000000000000 ]---\n RIP: 0010:shrink_huge_zero_page_scan+0x168/0x1a0\n RSP: 0018:ffff9933c6c57bd0 EFLAGS: 00000246\n RAX: 000000000000003e RBX: 0000000000000000 RCX: ffff88f61fc5c9c8\n RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff88f61fc5c9c0\n RBP: ffffcd7c446b0000 R08: ffffffff9a9405f0 R09: 0000000000005492\n R10: 00000000000030ea R11: ffffffff9a9405f0 R12: 0000000000000000\n R13: 0000000000000000 R14: 0000000000000000 R15: ffff88e703c4ac00\n FS:  0000000000000000(0000) GS:ffff88f61fc40000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055f4da6e9878 CR3: 0000000c71048000 CR4: 00000000000006f0\r\n\r\nThe root cause is that HWPoison flag will be set for huge_zero_folio\nwithout increasing the folio refcnt.  But then unpoison_memory() will\ndecrease the folio refcnt unexpectedly as it appears like a successfully\nhwpoisoned folio leading to VM_BUG_ON_PAGE(page_ref_count(page) == 0) when\nreleasing huge_zero_folio.\r\n\r\nSkip unpoisoning huge_zero_folio in unpoison_memory() to fix this issue. \nWe\u0026apos;re not prepared to unpoison huge_zero_folio yet.(CVE-2024-40914)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()\r\n\r\nIn case of token is released due to token-\u0026gt;state == BNXT_HWRM_DEFERRED,\nreleased token (set to NULL) is used in log messages. This issue is\nexpected to be prevented by HWRM_ERR_CODE_PF_UNAVAILABLE error code. But\nthis error code is returned by recent firmware. So some firmware may not\nreturn it. This may lead to NULL pointer dereference.\nAdjust this issue by adding token pointer check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-40919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nblock: fix request.queuelist usage in flush\r\n\r\nFriedrich Weber reported a kernel crash problem and bisected to commit\n81ada09cc25e (\u0026quot;blk-flush: reuse rq queuelist in flush state machine\u0026quot;).\r\n\r\nThe root cause is that we use \u0026quot;list_move_tail(\u0026amp;rq-\u0026gt;queuelist, pending)\u0026quot;\nin the PREFLUSH/POSTFLUSH sequences. But rq-\u0026gt;queuelist.next == xxx since\nit\u0026apos;s popped out from plug-\u0026gt;cached_rq in __blk_mq_alloc_requests_batch().\nWe don\u0026apos;t initialize its queuelist just for this first request, although\nthe queuelist of all later popped requests will be initialized.\r\n\r\nFix it by changing to use \u0026quot;list_add_tail(\u0026amp;rq-\u0026gt;queuelist, pending)\u0026quot; so\nrq-\u0026gt;queuelist doesn\u0026apos;t need to be initialized. It should be ok since rq\ncan\u0026apos;t be on any list when PREFLUSH or POSTFLUSH, has no move actually.\r\n\r\nPlease note the commit 81ada09cc25e (\u0026quot;blk-flush: reuse rq queuelist in\nflush state machine\u0026quot;) also has another requirement that no drivers would\ntouch rq-\u0026gt;queuelist after blk_mq_end_request() since we will reuse it to\nadd rq to the post-flush pending list in POSTFLUSH. If this is not true,\nwe will have to revert that commit IMHO.\r\n\r\nThis updated version adds \u0026quot;list_del_init(\u0026amp;rq-\u0026gt;queuelist)\u0026quot; in flush rq\ncallback since the dm layer may submit request of a weird invalid format\n(REQ_FSEQ_PREFLUSH | REQ_FSEQ_POSTFLUSH), which causes double list_add\nif without this \u0026quot;list_del_init(\u0026amp;rq-\u0026gt;queuelist)\u0026quot;. The weird invalid format\nproblem should be fixed in dm layer.(CVE-2024-40925)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: ethtool: fix the error condition in ethtool_get_phy_stats_ethtool()\r\n\r\nClang static checker (scan-build) warning:\nnet/ethtool/ioctl.c:line 2233, column 2\nCalled function pointer is null (null dereference).\r\n\r\nReturn \u0026apos;-EOPNOTSUPP\u0026apos; when \u0026apos;ops-\u0026gt;get_ethtool_phy_stats\u0026apos; is NULL to fix\nthis typo error.(CVE-2024-40928)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlandlock: Fix d_parent walk\r\n\r\nThe WARN_ON_ONCE() in collect_domain_accesses() can be triggered when\ntrying to link a root mount point.  This cannot work in practice because\nthis directory is mounted, but the VFS check is done after the call to\nsecurity_path_link().\r\n\r\nDo not use source directory\u0026apos;s d_parent when the source directory is the\nmount point.\r\n\r\n[mic: Fix commit message](CVE-2024-40938)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: wwan: iosm: Fix tainted pointer delete is case of region creation fail\r\n\r\nIn case of region creation fail in ipc_devlink_create_region(), previously\ncreated regions delete process starts from tainted pointer which actually\nholds error code value.\nFix this bug by decreasing region index before delete.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-40939)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Fix tainted pointer delete is case of flow rules creation fail\r\n\r\nIn case of flow rule creation fail in mlx5_lag_create_port_sel_table(),\ninstead of previously created rules, the tainted pointer is deleted\ndeveral times.\nFix this bug by using correct flow rules pointers.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-40940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nx86/kexec: Fix bug with call depth tracking\r\n\r\nThe call to cc_platform_has() triggers a fault and system crash if call depth\ntracking is active because the GS segment has been reset by load_segments() and\nGS_BASE is now 0 but call depth tracking uses per-CPU variables to operate.\r\n\r\nCall cc_platform_has() earlier in the function when GS is still valid.\r\n\r\n  [ bp: Massage. ](CVE-2024-40944)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommu: Return right value in iommu_sva_bind_device()\r\n\r\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\r\n\r\nIn reality, this doesn\u0026apos;t cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won\u0026apos;t call iommu_sva_bind_device()\nat all.(CVE-2024-40945)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/page_table_check: fix crash on ZONE_DEVICE\r\n\r\nNot all pages may apply to pgtable check.  One example is ZONE_DEVICE\npages: they map PFNs directly, and they don\u0026apos;t allocate page_ext at all\neven if there\u0026apos;s struct page around.  One may reference\ndevm_memremap_pages().\r\n\r\nWhen both ZONE_DEVICE and page-table-check enabled, then try to map some\ndax memories, one can trigger kernel bug constantly now when the kernel\nwas trying to inject some pfn maps on the dax device:\r\n\r\n kernel BUG at mm/page_table_check.c:55!\r\n\r\nWhile it\u0026apos;s pretty legal to use set_pxx_at() for ZONE_DEVICE pages for page\nfault resolutions, skip all the checks if page_ext doesn\u0026apos;t even exist in\npgtable checker, which applies to ZONE_DEVICE but maybe more.(CVE-2024-40948)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm: huge_memory: fix misused mapping_large_folio_support() for anon folios\r\n\r\nWhen I did a large folios split test, a WARNING \u0026quot;[ 5059.122759][ T166]\nCannot split file folio to non-0 order\u0026quot; was triggered.  But the test cases\nare only for anonmous folios.  while mapping_large_folio_support() is only\nreasonable for page cache folios.\r\n\r\nIn split_huge_page_to_list_to_order(), the folio passed to\nmapping_large_folio_support() maybe anonmous folio.  The folio_test_anon()\ncheck is missing.  So the split of the anonmous THP is failed.  This is\nalso the same for shmem_mapping().  We\u0026apos;d better add a check for both.  But\nthe shmem_mapping() in __split_huge_page() is not involved, as for\nanonmous folios, the end parameter is set to -1, so (head[i].index \u0026gt;= end)\nis always false.  shmem_mapping() is not called.\r\n\r\nAlso add a VM_WARN_ON_ONCE() in mapping_large_folio_support() for anon\nmapping, So we can detect the wrong use more easily.\r\n\r\nTHP folios maybe exist in the pagecache even the file system doesn\u0026apos;t\nsupport large folio, it is because when CONFIG_TRANSPARENT_HUGEPAGE is\nenabled, khugepaged will try to collapse read-only file-backed pages to\nTHP.  But the mapping does not actually support multi order large folios\nproperly.\r\n\r\nUsing /sys/kernel/debug/split_huge_pages to verify this, with this patch,\nlarge anon THP is successfully split and the warning is ceased.(CVE-2024-40950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: fix slab-out-of-bounds in ext4_mb_find_good_group_avg_frag_lists()\r\n\r\nWe can trigger a slab-out-of-bounds with the following commands:\r\n\r\n    mkfs.ext4 -F /dev/$disk 10G\n    mount /dev/$disk /tmp/test\n    echo 2147483647 \u0026gt; /sys/fs/ext4/$disk/mb_group_prealloc\n    echo test \u0026gt; /tmp/test/file \u0026amp;\u0026amp; sync\r\n\r\n==================================================================\nBUG: KASAN: slab-out-of-bounds in ext4_mb_find_good_group_avg_frag_lists+0x8a/0x200 [ext4]\nRead of size 8 at addr ffff888121b9d0f0 by task kworker/u2:0/11\nCPU: 0 PID: 11 Comm: kworker/u2:0 Tainted: GL 6.7.0-next-20240118 #521\nCall Trace:\n dump_stack_lvl+0x2c/0x50\n kasan_report+0xb6/0xf0\n ext4_mb_find_good_group_avg_frag_lists+0x8a/0x200 [ext4]\n ext4_mb_regular_allocator+0x19e9/0x2370 [ext4]\n ext4_mb_new_blocks+0x88a/0x1370 [ext4]\n ext4_ext_map_blocks+0x14f7/0x2390 [ext4]\n ext4_map_blocks+0x569/0xea0 [ext4]\n ext4_do_writepages+0x10f6/0x1bc0 [ext4]\n[...]\n==================================================================\r\n\r\nThe flow of issue triggering is as follows:\r\n\r\n// Set s_mb_group_prealloc to 2147483647 via sysfs\next4_mb_new_blocks\n  ext4_mb_normalize_request\n    ext4_mb_normalize_group_request\n      ac-\u0026gt;ac_g_ex.fe_len = EXT4_SB(sb)-\u0026gt;s_mb_group_prealloc\n  ext4_mb_regular_allocator\n    ext4_mb_choose_next_group\n      ext4_mb_choose_next_group_best_avail\n        mb_avg_fragment_size_order\n          order = fls(len) - 2 = 29\n        ext4_mb_find_good_group_avg_frag_lists\n          frag_list = \u0026amp;sbi-\u0026gt;s_mb_avg_fragment_size[order]\n          if (list_empty(frag_list)) // Trigger SOOB!\r\n\r\nAt 4k block size, the length of the s_mb_avg_fragment_size list is 14,\nbut an oversized s_mb_group_prealloc is set, causing slab-out-of-bounds\nto be triggered by an attempt to access an element at index 29.\r\n\r\nAdd a new attr_id attr_clusters_in_group with values in the range\n[0, sbi-\u0026gt;s_clusters_per_group] and declare mb_group_prealloc as\nthat type to fix the issue. In addition avoid returning an order\nfrom mb_avg_fragment_size_order() greater than MB_NUM_ORDERS(sb)\nand reduce some useless loops.(CVE-2024-40955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntty: add the option to have a tty reject a new ldisc\r\n\r\n... and use it to limit the virtual terminals to just N_TTY.  They are\nkind of special, and in particular, the \u0026quot;con_write()\u0026quot; routine violates\nthe \u0026quot;writes cannot sleep\u0026quot; rule that some ldiscs rely on.\r\n\r\nThis avoids the\r\n\r\n   BUG: sleeping function called from invalid context at kernel/printk/printk.c:2659\r\n\r\nwhen N_GSM has been attached to a virtual console, and gsmld_write()\ncalls con_write() while holding a spinlock, and con_write() then tries\nto get the console lock.(CVE-2024-40966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: don\u0026apos;t set RO when shutting down f2fs\r\n\r\nShutdown does not check the error of thaw_super due to readonly, which\ncauses a deadlock like below.\r\n\r\nf2fs_ioc_shutdown(F2FS_GOING_DOWN_FULLSYNC)        issue_discard_thread\n - bdev_freeze\n  - freeze_super\n - f2fs_stop_checkpoint()\n  - f2fs_handle_critical_error                     - sb_start_write\n    - set RO                                         - waiting\n - bdev_thaw\n  - thaw_super_locked\n    - return -EINVAL, if sb_rdonly()\n - f2fs_stop_discard_thread\n  -\u0026gt; wait for kthread_stop(discard_thread);(CVE-2024-40969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nAvoid hw_desc array overrun in dw-axi-dmac\r\n\r\nI have a use case where nr_buffers = 3 and in which each descriptor is composed by 3\nsegments, resulting in the DMA channel descs_allocated to be 9. Since axi_desc_put()\nhandles the hw_desc considering the descs_allocated, this scenario would result in a\nkernel panic (hw_desc array will be overrun).\r\n\r\nTo fix this, the proposal is to add a new member to the axi_dma_desc structure,\nwhere we keep the number of allocated hw_descs (axi_desc_alloc()) and use it in\naxi_desc_put() to handle the hw_desc array correctly.\r\n\r\nAdditionally I propose to remove the axi_chan_start_first_queued() call after completing\nthe transfer, since it was identified that unbalance can occur (started descriptors can\nbe interrupted and transfer ignored due to DMA channel not being enabled).(CVE-2024-40970)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/radeon: fix UBSAN warning in kv_dpm.c\r\n\r\nAdds bounds check for sumo_vid_mapping_entry.(CVE-2024-40988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/rxe: Fix responder length checking for UD request packets\r\n\r\nAccording to the IBA specification:\nIf a UD request packet is detected with an invalid length, the request\nshall be an invalid request and it shall be silently dropped by\nthe responder. The responder then waits for a new request packet.\r\n\r\ncommit 689c5421bfe0 (\u0026quot;RDMA/rxe: Fix incorrect responder length checking\u0026quot;)\ndefers responder length check for UD QPs in function `copy_data`.\nBut it introduces a regression issue for UD QPs.\r\n\r\nWhen the packet size is too large to fit in the receive buffer.\n`copy_data` will return error code -EINVAL. Then `send_data_in`\nwill return RESPST_ERR_MALFORMED_WQE. UD QP will transfer into\nERROR state.(CVE-2024-40992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nptp: fix integer overflow in max_vclocks_store\r\n\r\nOn 32bit systems, the \u0026quot;4 * max\u0026quot; multiply can overflow.  Use kcalloc()\nto do the allocation to prevent this.(CVE-2024-40994)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Avoid splat in pskb_pull_reason\r\n\r\nsyzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug\nhint in pskb_may_pull.\r\n\r\nWe\u0026apos;d like to retain this debug check because it might hint at integer\noverflows and other issues (kernel code should pull headers, not huge\nvalue).\r\n\r\nIn bpf case, this splat isn\u0026apos;t interesting at all: such (nonsensical)\nbpf programs are typically generated by a fuzzer anyway.\r\n\r\nDo what Eric suggested and suppress such warning.\r\n\r\nFor CONFIG_DEBUG_NET=n we don\u0026apos;t need the extra check because\npskb_may_pull will do the right thing: return an error without the\nWARN() backtrace.(CVE-2024-40996)\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\nmisc: fastrpc: Fix memory leak in audio daemon attach operation\r\n\r\nAudio PD daemon send the name as part of the init IOCTL call. This\nname needs to be copied to kernel for which memory is allocated.\nThis memory is never freed which might result in memory leak. Free\nthe memory when it is not needed.(CVE-2024-41025)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nplatform/x86: toshiba_acpi: Fix array out-of-bounds access\r\n\r\nIn order to use toshiba_dmi_quirks[] together with the standard DMI\nmatching functions, it must be terminated by a empty entry.\r\n\r\nSince this entry is missing, an array out-of-bounds access occurs\nevery time the quirk list is processed.\r\n\r\nFix this by adding the terminating empty entry.(CVE-2024-41028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nksmbd: discard write access to the directory open\r\n\r\nmay_open() does not allow a directory to be opened with the write access.\nHowever, some writing flags set by client result in adding write access\non server, making ksmbd incompatible with FUSE file system. Simply, let\u0026apos;s\ndiscard the write access when opening a directory.\r\n\r\nlist_add corruption. next is NULL.\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:26!\npc : __list_add_valid+0x88/0xbc\nlr : __list_add_valid+0x88/0xbc\nCall trace:\n__list_add_valid+0x88/0xbc\nfuse_finish_open+0x11c/0x170\nfuse_open_common+0x284/0x5e8\nfuse_dir_open+0x14/0x24\ndo_dentry_open+0x2a4/0x4e0\ndentry_open+0x50/0x80\nsmb2_open+0xbe4/0x15a4\nhandle_ksmbd_work+0x478/0x5ec\nprocess_one_work+0x1b4/0x448\nworker_thread+0x25c/0x430\nkthread+0x104/0x1d4\nret_from_fork+0x10/0x20(CVE-2024-41030)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/filemap: skip to create PMD-sized page cache if needed\r\n\r\nOn ARM64, HPAGE_PMD_ORDER is 13 when the base page size is 64KB.  The\nPMD-sized page cache can\u0026apos;t be supported by xarray as the following error\nmessages indicate.\r\n\r\n------------[ cut here ]------------\nWARNING: CPU: 35 PID: 7484 at lib/xarray.c:1025 xas_split_alloc+0xf8/0x128\nModules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib  \\\nnft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct    \\\nnft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4    \\\nip_set rfkill nf_tables nfnetlink vfat fat virtio_balloon drm      \\\nfuse xfs libcrc32c crct10dif_ce ghash_ce sha2_ce sha256_arm64      \\\nsha1_ce virtio_net net_failover virtio_console virtio_blk failover \\\ndimlib virtio_mmio\nCPU: 35 PID: 7484 Comm: test Kdump: loaded Tainted: G W 6.10.0-rc5-gavin+ #9\nHardware name: QEMU KVM Virtual Machine, BIOS edk2-20240524-1.el9 05/24/2024\npstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)\npc : xas_split_alloc+0xf8/0x128\nlr : split_huge_page_to_list_to_order+0x1c4/0x720\nsp : ffff800087a4f6c0\nx29: ffff800087a4f6c0 x28: ffff800087a4f720 x27: 000000001fffffff\nx26: 0000000000000c40 x25: 000000000000000d x24: ffff00010625b858\nx23: ffff800087a4f720 x22: ffffffdfc0780000 x21: 0000000000000000\nx20: 0000000000000000 x19: ffffffdfc0780000 x18: 000000001ff40000\nx17: 00000000ffffffff x16: 0000018000000000 x15: 51ec004000000000\nx14: 0000e00000000000 x13: 0000000000002000 x12: 0000000000000020\nx11: 51ec000000000000 x10: 51ece1c0ffff8000 x9 : ffffbeb961a44d28\nx8 : 0000000000000003 x7 : ffffffdfc0456420 x6 : ffff0000e1aa6eb8\nx5 : 20bf08b4fe778fca x4 : ffffffdfc0456420 x3 : 0000000000000c40\nx2 : 000000000000000d x1 : 000000000000000c x0 : 0000000000000000\nCall trace:\n xas_split_alloc+0xf8/0x128\n split_huge_page_to_list_to_order+0x1c4/0x720\n truncate_inode_partial_folio+0xdc/0x160\n truncate_inode_pages_range+0x1b4/0x4a8\n truncate_pagecache_range+0x84/0xa0\n xfs_flush_unmap_range+0x70/0x90 [xfs]\n xfs_file_fallocate+0xfc/0x4d8 [xfs]\n vfs_fallocate+0x124/0x2e8\n ksys_fallocate+0x4c/0xa0\n __arm64_sys_fallocate+0x24/0x38\n invoke_syscall.constprop.0+0x7c/0xd8\n do_el0_svc+0xb4/0xd0\n el0_svc+0x44/0x1d8\n el0t_64_sync_handler+0x134/0x150\n el0t_64_sync+0x17c/0x180\r\n\r\nFix it by skipping to allocate PMD-sized page cache when its size is\nlarger than MAX_PAGECACHE_ORDER.  For this specific case, we will fall to\nregular path where the readahead window is determined by BDI\u0026apos;s sysfs file\n(read_ahead_kb).(CVE-2024-41031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: ks8851: Fix deadlock with the SPI chip variant\r\n\r\nWhen SMP is enabled and spinlocks are actually functional then there is\na deadlock with the \u0026apos;statelock\u0026apos; spinlock between ks8851_start_xmit_spi\nand ks8851_irq:\r\n\r\n    watchdog: BUG: soft lockup - CPU#0 stuck for 27s!\n    call trace:\n      queued_spin_lock_slowpath+0x100/0x284\n      do_raw_spin_lock+0x34/0x44\n      ks8851_start_xmit_spi+0x30/0xb8\n      ks8851_start_xmit+0x14/0x20\n      netdev_start_xmit+0x40/0x6c\n      dev_hard_start_xmit+0x6c/0xbc\n      sch_direct_xmit+0xa4/0x22c\n      __qdisc_run+0x138/0x3fc\n      qdisc_run+0x24/0x3c\n      net_tx_action+0xf8/0x130\n      handle_softirqs+0x1ac/0x1f0\n      __do_softirq+0x14/0x20\n      ____do_softirq+0x10/0x1c\n      call_on_irq_stack+0x3c/0x58\n      do_softirq_own_stack+0x1c/0x28\n      __irq_exit_rcu+0x54/0x9c\n      irq_exit_rcu+0x10/0x1c\n      el1_interrupt+0x38/0x50\n      el1h_64_irq_handler+0x18/0x24\n      el1h_64_irq+0x64/0x68\n      __netif_schedule+0x6c/0x80\n      netif_tx_wake_queue+0x38/0x48\n      ks8851_irq+0xb8/0x2c8\n      irq_thread_fn+0x2c/0x74\n      irq_thread+0x10c/0x1b0\n      kthread+0xc8/0xd8\n      ret_from_fork+0x10/0x20\r\n\r\nThis issue has not been identified earlier because tests were done on\na device with SMP disabled and so spinlocks were actually NOPs.\r\n\r\nNow use spin_(un)lock_bh for TX queue related locking to avoid execution\nof softirq work synchronously that would lead to a deadlock.(CVE-2024-41036)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfirmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers\r\n\r\nCheck that all fields of a V2 algorithm header fit into the available\nfirmware data buffer.\r\n\r\nThe wmfw V2 format introduced variable-length strings in the algorithm\nblock header. This means the overall header length is variable, and the\nposition of most fields varies depending on the length of the string\nfields. Each field must be checked to ensure that it does not overflow\nthe firmware data buffer.\r\n\r\nAs this ia bugfix patch, the fixes avoid making any significant change to\nthe existing code. This makes it easier to review and less likely to\nintroduce new bugs.(CVE-2024-41038)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni40e: Fix XDP program unloading while removing the driver\r\n\r\nThe commit 6533e558c650 (\u0026quot;i40e: Fix reset path while removing\nthe driver\u0026quot;) introduced a new PF state \u0026quot;__I40E_IN_REMOVE\u0026quot; to block\nmodifying the XDP program while the driver is being removed.\nUnfortunately, such a change is useful only if the \u0026quot;.ndo_bpf()\u0026quot;\ncallback was called out of the rmmod context because unloading the\nexisting XDP program is also a part of driver removing procedure.\nIn other words, from the rmmod context the driver is expected to\nunload the XDP program without reporting any errors. Otherwise,\nthe kernel warning with callstack is printed out to dmesg.\r\n\r\nExample failing scenario:\n 1. Load the i40e driver.\n 2. Load the XDP program.\n 3. Unload the i40e driver (using \u0026quot;rmmod\u0026quot; command).\r\n\r\nThe example kernel warning log:\r\n\r\n[  +0.004646] WARNING: CPU: 94 PID: 10395 at net/core/dev.c:9290 unregister_netdevice_many_notify+0x7a9/0x870\n[...]\n[  +0.010959] RIP: 0010:unregister_netdevice_many_notify+0x7a9/0x870\n[...]\n[  +0.002726] Call Trace:\n[  +0.002457]  \u0026lt;TASK\u0026gt;\n[  +0.002119]  ? __warn+0x80/0x120\n[  +0.003245]  ? unregister_netdevice_many_notify+0x7a9/0x870\n[  +0.005586]  ? report_bug+0x164/0x190\n[  +0.003678]  ? handle_bug+0x3c/0x80\n[  +0.003503]  ? exc_invalid_op+0x17/0x70\n[  +0.003846]  ? asm_exc_invalid_op+0x1a/0x20\n[  +0.004200]  ? unregister_netdevice_many_notify+0x7a9/0x870\n[  +0.005579]  ? unregister_netdevice_many_notify+0x3cc/0x870\n[  +0.005586]  unregister_netdevice_queue+0xf7/0x140\n[  +0.004806]  unregister_netdev+0x1c/0x30\n[  +0.003933]  i40e_vsi_release+0x87/0x2f0 [i40e]\n[  +0.004604]  i40e_remove+0x1a1/0x420 [i40e]\n[  +0.004220]  pci_device_remove+0x3f/0xb0\n[  +0.003943]  device_release_driver_internal+0x19f/0x200\n[  +0.005243]  driver_detach+0x48/0x90\n[  +0.003586]  bus_remove_driver+0x6d/0xf0\n[  +0.003939]  pci_unregister_driver+0x2e/0xb0\n[  +0.004278]  i40e_exit_module+0x10/0x5f0 [i40e]\n[  +0.004570]  __do_sys_delete_module.isra.0+0x197/0x310\n[  +0.005153]  do_syscall_64+0x85/0x170\n[  +0.003684]  ? syscall_exit_to_user_mode+0x69/0x220\n[  +0.004886]  ? do_syscall_64+0x95/0x170\n[  +0.003851]  ? exc_page_fault+0x7e/0x180\n[  +0.003932]  entry_SYSCALL_64_after_hwframe+0x71/0x79\n[  +0.005064] RIP: 0033:0x7f59dc9347cb\n[  +0.003648] Code: 73 01 c3 48 8b 0d 65 16 0c 00 f7 d8 64 89 01 48 83\nc8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 b0 00 00 00 0f\n05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 16 0c 00 f7 d8 64 89 01 48\n[  +0.018753] RSP: 002b:00007ffffac99048 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0\n[  +0.007577] RAX: ffffffffffffffda RBX: 0000559b9bb2f6e0 RCX: 00007f59dc9347cb\n[  +0.007140] RDX: 0000000000000000 RSI: 0000000000000800 RDI: 0000559b9bb2f748\n[  +0.007146] RBP: 00007ffffac99070 R08: 1999999999999999 R09: 0000000000000000\n[  +0.007133] R10: 00007f59dc9a5ac0 R11: 0000000000000206 R12: 0000000000000000\n[  +0.007141] R13: 00007ffffac992d8 R14: 0000559b9bb2f6e0 R15: 0000000000000000\n[  +0.007151]  \u0026lt;/TASK\u0026gt;\n[  +0.002204] ---[ end trace 0000000000000000 ]---\r\n\r\nFix this by checking if the XDP program is being loaded or unloaded.\nThen, block only loading a new program while \u0026quot;__I40E_IN_REMOVE\u0026quot; is set.\nAlso, move testing \u0026quot;__I40E_IN_REMOVE\u0026quot; flag to the beginning of XDP_SETUP\ncallback to avoid unnecessary operations and checks.(CVE-2024-41047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: cyclic allocation of msg_id to avoid reuse\r\n\r\nReusing the msg_id after a maliciously completed reopen request may cause\na read request to remain unprocessed and result in a hung, as shown below:\r\n\r\n       t1       |      t2       |      t3\n-------------------------------------------------\ncachefiles_ondemand_select_req\n cachefiles_ondemand_object_is_close(A)\n cachefiles_ondemand_set_object_reopening(A)\n queue_work(fscache_object_wq, \u0026amp;info-\u0026gt;work)\n                ondemand_object_worker\n                 cachefiles_ondemand_init_object(A)\n                  cachefiles_ondemand_send_req(OPEN)\n                    // get msg_id 6\n                    wait_for_completion(\u0026amp;req_A-\u0026gt;done)\ncachefiles_ondemand_daemon_read\n // read msg_id 6 req_A\n cachefiles_ondemand_get_fd\n copy_to_user\n                                // Malicious completion msg_id 6\n                                copen 6,-1\n                                cachefiles_ondemand_copen\n                                 complete(\u0026amp;req_A-\u0026gt;done)\n                                 // will not set the object to close\n                                 // because ondemand_id \u0026amp;\u0026amp; fd is valid.\r\n\r\n                // ondemand_object_worker() is done\n                // but the object is still reopening.\r\n\r\n                                // new open req_B\n                                cachefiles_ondemand_init_object(B)\n                                 cachefiles_ondemand_send_req(OPEN)\n                                 // reuse msg_id 6\nprocess_open_req\n copen 6,A.size\n // The expected failed copen was executed successfully\r\n\r\nExpect copen to fail, and when it does, it closes fd, which sets the\nobject to close, and then close triggers reopen again. However, due to\nmsg_id reuse resulting in a successful copen, the anonymous fd is not\nclosed until the daemon exits. Therefore read requests waiting for reopen\nto complete may trigger hung task.\r\n\r\nTo avoid this issue, allocate the msg_id cyclically to avoid reusing the\nmsg_id for a very short duration of time.(CVE-2024-41050)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: wait for ondemand_object_worker to finish when dropping object\r\n\r\nWhen queuing ondemand_object_worker() to re-open the object,\ncachefiles_object is not pinned. The cachefiles_object may be freed when\nthe pending read request is completed intentionally and the related\nerofs is umounted. If ondemand_object_worker() runs after the object is\nfreed, it will incur use-after-free problem as shown below.\r\n\r\nprocess A  processs B  process C  process D\r\n\r\ncachefiles_ondemand_send_req()\n// send a read req X\n// wait for its completion\r\n\r\n           // close ondemand fd\n           cachefiles_ondemand_fd_release()\n           // set object as CLOSE\r\n\r\n                       cachefiles_ondemand_daemon_read()\n                       // set object as REOPENING\n                       queue_work(fscache_wq, \u0026amp;info-\u0026gt;ondemand_work)\r\n\r\n                                // close /dev/cachefiles\n                                cachefiles_daemon_release\n                                cachefiles_flush_reqs\n                                complete(\u0026amp;req-\u0026gt;done)\r\n\r\n// read req X is completed\n// umount the erofs fs\ncachefiles_put_object()\n// object will be freed\ncachefiles_ondemand_deinit_obj_info()\nkmem_cache_free(object)\n                       // both info and object are freed\n                       ondemand_object_worker()\r\n\r\nWhen dropping an object, it is no longer necessary to reopen the object,\nso use cancel_work_sync() to cancel or wait for ondemand_object_worker()\nto finish.(CVE-2024-41051)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: ufs: core: Fix ufshcd_abort_one racing issue\r\n\r\nWhen ufshcd_abort_one is racing with the completion ISR, the completed tag\nof the request\u0026apos;s mq_hctx pointer will be set to NULL by ISR.  Return\nsuccess when request is completed by ISR because ufshcd_abort_one does not\nneed to do anything.\r\n\r\nThe racing flow is:\r\n\r\nThread A\nufshcd_err_handler\t\t\t\t\tstep 1\n\t...\n\tufshcd_abort_one\n\t\tufshcd_try_to_abort_task\n\t\t\tufshcd_cmd_inflight(true)\tstep 3\n\t\tufshcd_mcq_req_to_hwq\n\t\t\tblk_mq_unique_tag\n\t\t\t\trq-\u0026gt;mq_hctx-\u0026gt;queue_num\tstep 5\r\n\r\nThread B\nufs_mtk_mcq_intr(cq complete ISR)\t\t\tstep 2\n\tscsi_done\n\t\t...\n\t\t__blk_mq_free_request\n\t\t\trq-\u0026gt;mq_hctx = NULL;\t\tstep 4\r\n\r\nBelow is KE back trace.\n  ufshcd_try_to_abort_task: cmd at tag 41 not pending in the device.\n  ufshcd_try_to_abort_task: cmd at tag=41 is cleared.\n  Aborting tag 41 / CDB 0x28 succeeded\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194\n  pc : [0xffffffddd7a79bf8] blk_mq_unique_tag+0x8/0x14\n  lr : [0xffffffddd6155b84] ufshcd_mcq_req_to_hwq+0x1c/0x40 [ufs_mediatek_mod_ise]\n   do_mem_abort+0x58/0x118\n   el1_abort+0x3c/0x5c\n   el1h_64_sync_handler+0x54/0x90\n   el1h_64_sync+0x68/0x6c\n   blk_mq_unique_tag+0x8/0x14\n   ufshcd_err_handler+0xae4/0xfa8 [ufs_mediatek_mod_ise]\n   process_one_work+0x208/0x4fc\n   worker_thread+0x228/0x438\n   kthread+0x104/0x1d4\n   ret_from_fork+0x10/0x20(CVE-2024-41053)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: ufs: core: Fix ufshcd_clear_cmd racing issue\r\n\r\nWhen ufshcd_clear_cmd is racing with the completion ISR, the completed tag\nof the request\u0026apos;s mq_hctx pointer will be set to NULL by the ISR.  And\nufshcd_clear_cmd\u0026apos;s call to ufshcd_mcq_req_to_hwq will get NULL pointer KE.\nReturn success when the request is completed by ISR because sq does not\nneed cleanup.\r\n\r\nThe racing flow is:\r\n\r\nThread A\nufshcd_err_handler\t\t\t\t\tstep 1\n\tufshcd_try_to_abort_task\n\t\tufshcd_cmd_inflight(true)\t\tstep 3\n\t\tufshcd_clear_cmd\n\t\t\t...\n\t\t\tufshcd_mcq_req_to_hwq\n\t\t\tblk_mq_unique_tag\n\t\t\t\trq-\u0026gt;mq_hctx-\u0026gt;queue_num\tstep 5\r\n\r\nThread B\nufs_mtk_mcq_intr(cq complete ISR)\t\t\tstep 2\n\tscsi_done\n\t\t...\n\t\t__blk_mq_free_request\n\t\t\trq-\u0026gt;mq_hctx = NULL;\t\tstep 4\r\n\r\nBelow is KE back trace:\r\n\r\n  ufshcd_try_to_abort_task: cmd pending in the device. tag = 6\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194\n   pc : [0xffffffd589679bf8] blk_mq_unique_tag+0x8/0x14\n   lr : [0xffffffd5862f95b4] ufshcd_mcq_sq_cleanup+0x6c/0x1cc [ufs_mediatek_mod_ise]\n   Workqueue: ufs_eh_wq_0 ufshcd_err_handler [ufs_mediatek_mod_ise]\n   Call trace:\n    dump_backtrace+0xf8/0x148\n    show_stack+0x18/0x24\n    dump_stack_lvl+0x60/0x7c\n    dump_stack+0x18/0x3c\n    mrdump_common_die+0x24c/0x398 [mrdump]\n    ipanic_die+0x20/0x34 [mrdump]\n    notify_die+0x80/0xd8\n    die+0x94/0x2b8\n    __do_kernel_fault+0x264/0x298\n    do_page_fault+0xa4/0x4b8\n    do_translation_fault+0x38/0x54\n    do_mem_abort+0x58/0x118\n    el1_abort+0x3c/0x5c\n    el1h_64_sync_handler+0x54/0x90\n    el1h_64_sync+0x68/0x6c\n    blk_mq_unique_tag+0x8/0x14\n    ufshcd_clear_cmd+0x34/0x118 [ufs_mediatek_mod_ise]\n    ufshcd_try_to_abort_task+0x2c8/0x5b4 [ufs_mediatek_mod_ise]\n    ufshcd_err_handler+0xa7c/0xfa8 [ufs_mediatek_mod_ise]\n    process_one_work+0x208/0x4fc\n    worker_thread+0x228/0x438\n    kthread+0x104/0x1d4\n    ret_from_fork+0x10/0x20(CVE-2024-41054)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: fix slab-use-after-free in fscache_withdraw_volume()\r\n\r\nWe got the following issue in our fault injection stress test:\r\n\r\n==================================================================\nBUG: KASAN: slab-use-after-free in fscache_withdraw_volume+0x2e1/0x370\nRead of size 4 at addr ffff88810680be08 by task ondemand-04-dae/5798\r\n\r\nCPU: 0 PID: 5798 Comm: ondemand-04-dae Not tainted 6.8.0-dirty #565\nCall Trace:\n kasan_check_range+0xf6/0x1b0\n fscache_withdraw_volume+0x2e1/0x370\n cachefiles_withdraw_volume+0x31/0x50\n cachefiles_withdraw_cache+0x3ad/0x900\n cachefiles_put_unbind_pincount+0x1f6/0x250\n cachefiles_daemon_release+0x13b/0x290\n __fput+0x204/0xa00\n task_work_run+0x139/0x230\r\n\r\nAllocated by task 5820:\n __kmalloc+0x1df/0x4b0\n fscache_alloc_volume+0x70/0x600\n __fscache_acquire_volume+0x1c/0x610\n erofs_fscache_register_volume+0x96/0x1a0\n erofs_fscache_register_fs+0x49a/0x690\n erofs_fc_fill_super+0x6c0/0xcc0\n vfs_get_super+0xa9/0x140\n vfs_get_tree+0x8e/0x300\n do_new_mount+0x28c/0x580\n [...]\r\n\r\nFreed by task 5820:\n kfree+0xf1/0x2c0\n fscache_put_volume.part.0+0x5cb/0x9e0\n erofs_fscache_unregister_fs+0x157/0x1b0\n erofs_kill_sb+0xd9/0x1c0\n deactivate_locked_super+0xa3/0x100\n vfs_get_super+0x105/0x140\n vfs_get_tree+0x8e/0x300\n do_new_mount+0x28c/0x580\n [...]\n==================================================================\r\n\r\nFollowing is the process that triggers the issue:\r\n\r\n        mount failed         |         daemon exit\n------------------------------------------------------------\n deactivate_locked_super        cachefiles_daemon_release\n  erofs_kill_sb\n   erofs_fscache_unregister_fs\n    fscache_relinquish_volume\n     __fscache_relinquish_volume\n      fscache_put_volume(fscache_volume, fscache_volume_put_relinquish)\n       zero = __refcount_dec_and_test(\u0026amp;fscache_volume-\u0026gt;ref, \u0026amp;ref);\n                                 cachefiles_put_unbind_pincount\n                                  cachefiles_daemon_unbind\n                                   cachefiles_withdraw_cache\n                                    cachefiles_withdraw_volumes\n                                     list_del_init(\u0026amp;volume-\u0026gt;cache_link)\n       fscache_free_volume(fscache_volume)\n        cache-\u0026gt;ops-\u0026gt;free_volume\n         cachefiles_free_volume\n          list_del_init(\u0026amp;cachefiles_volume-\u0026gt;cache_link);\n        kfree(fscache_volume)\n                                     cachefiles_withdraw_volume\n                                      fscache_withdraw_volume\n                                       fscache_volume-\u0026gt;n_accesses\n                                       // fscache_volume UAF !!!\r\n\r\nThe fscache_volume in cache-\u0026gt;volumes must not have been freed yet, but its\nreference count may be 0. So use the new fscache_try_get_volume() helper\nfunction try to get its reference count.\r\n\r\nIf the reference count of fscache_volume is 0, fscache_put_volume() is\nfreeing it, so wait for it to be removed from cache-\u0026gt;volumes.\r\n\r\nIf its reference count is not 0, call cachefiles_withdraw_volume() with\nreference count protection to avoid the above issue.(CVE-2024-41058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhfsplus: fix uninit-value in copy_name\r\n\r\n[syzbot reported]\nBUG: KMSAN: uninit-value in sized_strscpy+0xc4/0x160\n sized_strscpy+0xc4/0x160\n copy_name+0x2af/0x320 fs/hfsplus/xattr.c:411\n hfsplus_listxattr+0x11e9/0x1a50 fs/hfsplus/xattr.c:750\n vfs_listxattr fs/xattr.c:493 [inline]\n listxattr+0x1f3/0x6b0 fs/xattr.c:840\n path_listxattr fs/xattr.c:864 [inline]\n __do_sys_listxattr fs/xattr.c:876 [inline]\n __se_sys_listxattr fs/xattr.c:873 [inline]\n __x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873\n x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:3877 [inline]\n slab_alloc_node mm/slub.c:3918 [inline]\n kmalloc_trace+0x57b/0xbe0 mm/slub.c:4065\n kmalloc include/linux/slab.h:628 [inline]\n hfsplus_listxattr+0x4cc/0x1a50 fs/hfsplus/xattr.c:699\n vfs_listxattr fs/xattr.c:493 [inline]\n listxattr+0x1f3/0x6b0 fs/xattr.c:840\n path_listxattr fs/xattr.c:864 [inline]\n __do_sys_listxattr fs/xattr.c:876 [inline]\n __se_sys_listxattr fs/xattr.c:873 [inline]\n __x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873\n x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[Fix]\nWhen allocating memory to strbuf, initialize memory to 0.(CVE-2024-41059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/radeon: check bo_va-\u0026gt;bo is non-NULL before using it\r\n\r\nThe call to radeon_vm_clear_freed might clear bo_va-\u0026gt;bo, so\nwe have to check it before dereferencing it.(CVE-2024-41060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nibmvnic: Add tx check to prevent skb leak\r\n\r\nBelow is a summary of how the driver stores a reference to an skb during\ntransmit:\n    tx_buff[free_map[consumer_index]]-\u0026gt;skb = new_skb;\n    free_map[consumer_index] = IBMVNIC_INVALID_MAP;\n    consumer_index ++;\nWhere variable data looks like this:\n    free_map == [4, IBMVNIC_INVALID_MAP, IBMVNIC_INVALID_MAP, 0, 3]\n                                               \tconsumer_index^\n    tx_buff == [skb=null, skb=\u0026lt;ptr\u0026gt;, skb=\u0026lt;ptr\u0026gt;, skb=null, skb=null]\r\n\r\nThe driver has checks to ensure that free_map[consumer_index] pointed to\na valid index but there was no check to ensure that this index pointed\nto an unused/null skb address. So, if, by some chance, our free_map and\ntx_buff lists become out of sync then we were previously risking an\nskb memory leak. This could then cause tcp congestion control to stop\nsending packets, eventually leading to ETIMEDOUT.\r\n\r\nTherefore, add a conditional to ensure that the skb address is null. If\nnot then warn the user (because this is still a bug that should be\npatched) and free the old pointer to prevent memleak/tcp problems.(CVE-2024-41066)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/sclp: Fix sclp_init() cleanup on failure\r\n\r\nIf sclp_init() fails it only partially cleans up: if there are multiple\nfailing calls to sclp_init() sclp_state_change_event will be added several\ntimes to sclp_reg_list, which results in the following warning:\r\n\r\n------------[ cut here ]------------\nlist_add double add: new=000003ffe1598c10, prev=000003ffe1598bf0, next=000003ffe1598c10.\nWARNING: CPU: 0 PID: 1 at lib/list_debug.c:35 __list_add_valid_or_report+0xde/0xf8\nCPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-rc3\nKrnl PSW : 0404c00180000000 000003ffe0d6076a (__list_add_valid_or_report+0xe2/0xf8)\n           R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3\n...\nCall Trace:\n [\u0026lt;000003ffe0d6076a\u0026gt;] __list_add_valid_or_report+0xe2/0xf8\n([\u0026lt;000003ffe0d60766\u0026gt;] __list_add_valid_or_report+0xde/0xf8)\n [\u0026lt;000003ffe0a8d37e\u0026gt;] sclp_init+0x40e/0x450\n [\u0026lt;000003ffe00009f2\u0026gt;] do_one_initcall+0x42/0x1e0\n [\u0026lt;000003ffe15b77a6\u0026gt;] do_initcalls+0x126/0x150\n [\u0026lt;000003ffe15b7a0a\u0026gt;] kernel_init_freeable+0x1ba/0x1f8\n [\u0026lt;000003ffe0d6650e\u0026gt;] kernel_init+0x2e/0x180\n [\u0026lt;000003ffe000301c\u0026gt;] __ret_from_fork+0x3c/0x60\n [\u0026lt;000003ffe0d759ca\u0026gt;] ret_from_fork+0xa/0x30\r\n\r\nFix this by removing sclp_state_change_event from sclp_reg_list when\nsclp_init() fails.(CVE-2024-41068)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncxl/region: Avoid null pointer dereference in region lookup\r\n\r\ncxl_dpa_to_region() looks up a region based on a memdev and DPA.\nIt wrongly assumes an endpoint found mapping the DPA is also of\na fully assembled region. When not true it leads to a null pointer\ndereference looking up the region name.\r\n\r\nThis appears during testing of region lookup after a failure to\nassemble a BIOS defined region or if the lookup raced with the\nassembly of the BIOS defined region.\r\n\r\nFailure to clean up BIOS defined regions that fail assembly is an\nissue in itself and a fix to that problem will alleviate some of\nthe impact. It will not alleviate the race condition so let\u0026apos;s harden\nthis path.\r\n\r\nThe behavior change is that the kernel oops due to a null pointer\ndereference is replaced with a dev_dbg() message noting that an\nendpoint was mapped.\r\n\r\nAdditional comments are added so that future users of this function\ncan more clearly understand what it provides.(CVE-2024-41084)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nata: libata-core: Fix double free on error\r\n\r\nIf e.g. the ata_port_alloc() call in ata_host_alloc() fails, we will jump\nto the err_out label, which will call devres_release_group().\ndevres_release_group() will trigger a call to ata_host_release().\nata_host_release() calls kfree(host), so executing the kfree(host) in\nata_host_alloc() will lead to a double free:\r\n\r\nkernel BUG at mm/slub.c:553!\nOops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 11 PID: 599 Comm: (udev-worker) Not tainted 6.10.0-rc5 #47\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:kfree+0x2cf/0x2f0\nCode: 5d 41 5e 41 5f 5d e9 80 d6 ff ff 4d 89 f1 41 b8 01 00 00 00 48 89 d9 48 89 da\nRSP: 0018:ffffc90000f377f0 EFLAGS: 00010246\nRAX: ffff888112b1f2c0 RBX: ffff888112b1f2c0 RCX: ffff888112b1f320\nRDX: 000000000000400b RSI: ffffffffc02c9de5 RDI: ffff888112b1f2c0\nRBP: ffffc90000f37830 R08: 0000000000000000 R09: 0000000000000000\nR10: ffffc90000f37610 R11: 617461203a736b6e R12: ffffea00044ac780\nR13: ffff888100046400 R14: ffffffffc02c9de5 R15: 0000000000000006\nFS:  00007f2f1cabe980(0000) GS:ffff88813b380000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f2f1c3acf75 CR3: 0000000111724000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die_body.cold+0x19/0x27\n ? die+0x2e/0x50\n ? do_trap+0xca/0x110\n ? do_error_trap+0x6a/0x90\n ? kfree+0x2cf/0x2f0\n ? exc_invalid_op+0x50/0x70\n ? kfree+0x2cf/0x2f0\n ? asm_exc_invalid_op+0x1a/0x20\n ? ata_host_alloc+0xf5/0x120 [libata]\n ? ata_host_alloc+0xf5/0x120 [libata]\n ? kfree+0x2cf/0x2f0\n ata_host_alloc+0xf5/0x120 [libata]\n ata_host_alloc_pinfo+0x14/0xa0 [libata]\n ahci_init_one+0x6c9/0xd20 [ahci]\r\n\r\nEnsure that we will not call kfree(host) twice, by performing the kfree()\nonly if the devres_open_group() call failed.(CVE-2024-41087)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncan: mcp251xfd: fix infinite loop when xmit fails\r\n\r\nWhen the mcp251xfd_start_xmit() function fails, the driver stops\nprocessing messages, and the interrupt routine does not return,\nrunning indefinitely even after killing the running application.\r\n\r\nError messages:\n[  441.298819] mcp251xfd spi2.0 can0: ERROR in mcp251xfd_start_xmit: -16\n[  441.306498] mcp251xfd spi2.0 can0: Transmit Event FIFO buffer not empty. (seq=0x000017c7, tef_tail=0x000017cf, tef_head=0x000017d0, tx_head=0x000017d3).\n... and repeat forever.\r\n\r\nThe issue can be triggered when multiple devices share the same SPI\ninterface. And there is concurrent access to the bus.\r\n\r\nThe problem occurs because tx_ring-\u0026gt;head increments even if\nmcp251xfd_start_xmit() fails. Consequently, the driver skips one TX\npackage while still expecting a response in\nmcp251xfd_handle_tefif_one().\r\n\r\nResolve the issue by starting a workqueue to write the tx obj\nsynchronously if err = -EBUSY. In case of another error, decrement\ntx_ring-\u0026gt;head, remove skb from the echo stack, and drop the message.\r\n\r\n[mkl: use more imperative wording in patch description](CVE-2024-41088)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/i915/gt: Fix potential UAF by revoke of fence registers\r\n\r\nCI has been sporadically reporting the following issue triggered by\nigt@i915_selftest@live@hangcheck on ADL-P and similar machines:\r\n\r\n\u0026lt;6\u0026gt; [414.049203] i915: Running intel_hangcheck_live_selftests/igt_reset_evict_fence\n...\n\u0026lt;6\u0026gt; [414.068804] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled\n\u0026lt;6\u0026gt; [414.068812] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled\n\u0026lt;3\u0026gt; [414.070354] Unable to pin Y-tiled fence; err:-4\n\u0026lt;3\u0026gt; [414.071282] i915_vma_revoke_fence:301 GEM_BUG_ON(!i915_active_is_idle(\u0026amp;fence-\u0026gt;active))\n...\n\u0026lt;4\u0026gt;[  609.603992] ------------[ cut here ]------------\n\u0026lt;2\u0026gt;[  609.603995] kernel BUG at drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c:301!\n\u0026lt;4\u0026gt;[  609.604003] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n\u0026lt;4\u0026gt;[  609.604006] CPU: 0 PID: 268 Comm: kworker/u64:3 Tainted: G     U  W          6.9.0-CI_DRM_14785-g1ba62f8cea9c+ #1\n\u0026lt;4\u0026gt;[  609.604008] Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-P DDR4 RVP, BIOS RPLPFWI1.R00.4035.A00.2301200723 01/20/2023\n\u0026lt;4\u0026gt;[  609.604010] Workqueue: i915 __i915_gem_free_work [i915]\n\u0026lt;4\u0026gt;[  609.604149] RIP: 0010:i915_vma_revoke_fence+0x187/0x1f0 [i915]\n...\n\u0026lt;4\u0026gt;[  609.604271] Call Trace:\n\u0026lt;4\u0026gt;[  609.604273]  \u0026lt;TASK\u0026gt;\n...\n\u0026lt;4\u0026gt;[  609.604716]  __i915_vma_evict+0x2e9/0x550 [i915]\n\u0026lt;4\u0026gt;[  609.604852]  __i915_vma_unbind+0x7c/0x160 [i915]\n\u0026lt;4\u0026gt;[  609.604977]  force_unbind+0x24/0xa0 [i915]\n\u0026lt;4\u0026gt;[  609.605098]  i915_vma_destroy+0x2f/0xa0 [i915]\n\u0026lt;4\u0026gt;[  609.605210]  __i915_gem_object_pages_fini+0x51/0x2f0 [i915]\n\u0026lt;4\u0026gt;[  609.605330]  __i915_gem_free_objects.isra.0+0x6a/0xc0 [i915]\n\u0026lt;4\u0026gt;[  609.605440]  process_scheduled_works+0x351/0x690\n...\r\n\r\nIn the past, there were similar failures reported by CI from other IGT\ntests, observed on other platforms.\r\n\r\nBefore commit 63baf4f3d587 (\u0026quot;drm/i915/gt: Only wait for GPU activity\nbefore unbinding a GGTT fence\u0026quot;), i915_vma_revoke_fence() was waiting for\nidleness of vma-\u0026gt;active via fence_update().   That commit introduced\nvma-\u0026gt;fence-\u0026gt;active in order for the fence_update() to be able to wait\nselectively on that one instead of vma-\u0026gt;active since only idleness of\nfence registers was needed.  But then, another commit 0d86ee35097a\n(\u0026quot;drm/i915/gt: Make fence revocation unequivocal\u0026quot;) replaced the call to\nfence_update() in i915_vma_revoke_fence() with only fence_write(), and\nalso added that GEM_BUG_ON(!i915_active_is_idle(\u0026amp;fence-\u0026gt;active)) in front.\nNo justification was provided on why we might then expect idleness of\nvma-\u0026gt;fence-\u0026gt;active without first waiting on it.\r\n\r\nThe issue can be potentially caused by a race among revocation of fence\nregisters on one side and sequential execution of signal callbacks invoked\non completion of a request that was using them on the other, still\nprocessed in parallel to revocation of those fence registers.  Fix it by\nwaiting for idleness of vma-\u0026gt;fence-\u0026gt;active in i915_vma_revoke_fence().\r\n\r\n(cherry picked from commit 24bb052d3dd499c5956abad5f7d8e4fd07da7fb1)(CVE-2024-41092)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: avoid using null object of framebuffer\r\n\r\nInstead of using state-\u0026gt;fb-\u0026gt;obj[0] directly, get object from framebuffer\nby calling drm_gem_fb_get_obj() and return error code when object is\nnull to avoid using null object of framebuffer.(CVE-2024-41093)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/fbdev-dma: Only set smem_start is enable per module option\r\n\r\nOnly export struct fb_info.fix.smem_start if that is required by the\nuser and the memory does not come from vmalloc().\r\n\r\nSetting struct fb_info.fix.smem_start breaks systems where DMA\nmemory is backed by vmalloc address space. An example error is\nshown below.\r\n\r\n[    3.536043] ------------[ cut here ]------------\n[    3.540716] virt_to_phys used for non-linear address: 000000007fc4f540 (0xffff800086001000)\n[    3.552628] WARNING: CPU: 4 PID: 61 at arch/arm64/mm/physaddr.c:12 __virt_to_phys+0x68/0x98\n[    3.565455] Modules linked in:\n[    3.568525] CPU: 4 PID: 61 Comm: kworker/u12:5 Not tainted 6.6.23-06226-g4986cc3e1b75-dirty #250\n[    3.577310] Hardware name: NXP i.MX95 19X19 board (DT)\n[    3.582452] Workqueue: events_unbound deferred_probe_work_func\n[    3.588291] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[    3.595233] pc : __virt_to_phys+0x68/0x98\n[    3.599246] lr : __virt_to_phys+0x68/0x98\n[    3.603276] sp : ffff800083603990\n[    3.677939] Call trace:\n[    3.680393]  __virt_to_phys+0x68/0x98\n[    3.684067]  drm_fbdev_dma_helper_fb_probe+0x138/0x238\n[    3.689214]  __drm_fb_helper_initial_config_and_unlock+0x2b0/0x4c0\n[    3.695385]  drm_fb_helper_initial_config+0x4c/0x68\n[    3.700264]  drm_fbdev_dma_client_hotplug+0x8c/0xe0\n[    3.705161]  drm_client_register+0x60/0xb0\n[    3.709269]  drm_fbdev_dma_setup+0x94/0x148\r\n\r\nAdditionally, DMA memory is assumed to by contiguous in physical\naddress space, which is not guaranteed by vmalloc().\r\n\r\nResolve this by checking the module flag drm_leak_fbdev_smem when\nDRM allocated the instance of struct fb_info. Fbdev-dma then only\nsets smem_start only if required (via FBINFO_HIDE_SMEM_START). Also\nguarantee that the framebuffer is not located in vmalloc address\nspace.(CVE-2024-41094)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Mark bpf prog stack with kmsan_unposion_memory in interpreter mode\r\n\r\nsyzbot reported uninit memory usages during map_{lookup,delete}_elem.\r\n\r\n==========\nBUG: KMSAN: uninit-value in __dev_map_lookup_elem kernel/bpf/devmap.c:441 [inline]\nBUG: KMSAN: uninit-value in dev_map_lookup_elem+0xf3/0x170 kernel/bpf/devmap.c:796\n__dev_map_lookup_elem kernel/bpf/devmap.c:441 [inline]\ndev_map_lookup_elem+0xf3/0x170 kernel/bpf/devmap.c:796\n____bpf_map_lookup_elem kernel/bpf/helpers.c:42 [inline]\nbpf_map_lookup_elem+0x5c/0x80 kernel/bpf/helpers.c:38\n___bpf_prog_run+0x13fe/0xe0f0 kernel/bpf/core.c:1997\n__bpf_prog_run256+0xb5/0xe0 kernel/bpf/core.c:2237\n==========\r\n\r\nThe reproducer should be in the interpreter mode.\r\n\r\nThe C reproducer is trying to run the following bpf prog:\r\n\r\n    0: (18) r0 = 0x0\n    2: (18) r1 = map[id:49]\n    4: (b7) r8 = 16777216\n    5: (7b) *(u64 *)(r10 -8) = r8\n    6: (bf) r2 = r10\n    7: (07) r2 += -229\n            ^^^^^^^^^^\r\n\r\n    8: (b7) r3 = 8\n    9: (b7) r4 = 0\n   10: (85) call dev_map_lookup_elem#1543472\n   11: (95) exit\r\n\r\nIt is due to the \u0026quot;void *key\u0026quot; (r2) passed to the helper. bpf allows uninit\nstack memory access for bpf prog with the right privileges. This patch\nuses kmsan_unpoison_memory() to mark the stack as initialized.\r\n\r\nThis should address different syzbot reports on the uninit \u0026quot;void *key\u0026quot;\nargument during map_{lookup,delete}_elem.(CVE-2024-42063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: mana: Fix possible double free in error handling path\r\n\r\nWhen auxiliary_device_add() returns error and then calls\nauxiliary_device_uninit(), callback function adev_release\ncalls kfree(madev). We shouldn\u0026apos;t call kfree(madev) again\nin the error handling path. Set \u0026apos;madev\u0026apos; to NULL.(CVE-2024-42069)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers\r\n\r\nregister store validation for NFT_DATA_VALUE is conditional, however,\nthe datatype is always either NFT_DATA_VALUE or NFT_DATA_VERDICT. This\nonly requires a new helper function to infer the register type from the\nset datatype so this conditional check can be removed. Otherwise,\npointer to chain object can be leaked through the registers.(CVE-2024-42070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems\r\n\r\nThe following two shared buffer operations make use of the Shared Buffer\nStatus Register (SBSR):\r\n\r\n # devlink sb occupancy snapshot pci/0000:01:00.0\n # devlink sb occupancy clearmax pci/0000:01:00.0\r\n\r\nThe register has two masks of 256 bits to denote on which ingress /\negress ports the register should operate on. Spectrum-4 has more than\n256 ports, so the register was extended by cited commit with a new\n\u0026apos;port_page\u0026apos; field.\r\n\r\nHowever, when filling the register\u0026apos;s payload, the driver specifies the\nports as absolute numbers and not relative to the first port of the port\npage, resulting in memory corruptions [1].\r\n\r\nFix by specifying the ports relative to the first port of the port page.\r\n\r\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_sb_occ_snapshot+0xb6d/0xbc0\nRead of size 1 at addr ffff8881068cb00f by task devlink/1566\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xc6/0x120\n print_report+0xce/0x670\n kasan_report+0xd7/0x110\n mlxsw_sp_sb_occ_snapshot+0xb6d/0xbc0\n mlxsw_devlink_sb_occ_snapshot+0x75/0xb0\n devlink_nl_sb_occ_snapshot_doit+0x1f9/0x2a0\n genl_family_rcv_msg_doit+0x20c/0x300\n genl_rcv_msg+0x567/0x800\n netlink_rcv_skb+0x170/0x450\n genl_rcv+0x2d/0x40\n netlink_unicast+0x547/0x830\n netlink_sendmsg+0x8d4/0xdb0\n __sys_sendto+0x49b/0x510\n __x64_sys_sendto+0xe5/0x1c0\n do_syscall_64+0xc1/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[...]\nAllocated by task 1:\n kasan_save_stack+0x33/0x60\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x8f/0xa0\n copy_verifier_state+0xbc2/0xfb0\n do_check_common+0x2c51/0xc7e0\n bpf_check+0x5107/0x9960\n bpf_prog_load+0xf0e/0x2690\n __sys_bpf+0x1a61/0x49d0\n __x64_sys_bpf+0x7d/0xc0\n do_syscall_64+0xc1/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nFreed by task 1:\n kasan_save_stack+0x33/0x60\n kasan_save_track+0x14/0x30\n kasan_save_free_info+0x3b/0x60\n poison_slab_object+0x109/0x170\n __kasan_slab_free+0x14/0x30\n kfree+0xca/0x2b0\n free_verifier_state+0xce/0x270\n do_check_common+0x4828/0xc7e0\n bpf_check+0x5107/0x9960\n bpf_prog_load+0xf0e/0x2690\n __sys_bpf+0x1a61/0x49d0\n __x64_sys_bpf+0x7d/0xc0\n do_syscall_64+0xc1/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-42073)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: amd: acp: add a null check for chip_pdev structure\r\n\r\nWhen acp platform device creation is skipped, chip-\u0026gt;chip_pdev value will\nremain NULL. Add NULL check for chip-\u0026gt;chip_pdev structure in\nsnd_acp_resume() function to avoid null pointer dereference.(CVE-2024-42074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngfs2: Fix NULL pointer dereference in gfs2_log_flush\r\n\r\nIn gfs2_jindex_free(), set sdp-\u0026gt;sd_jdesc to NULL under the log flush\nlock to provide exclusion against gfs2_log_flush().\r\n\r\nIn gfs2_log_flush(), check if sdp-\u0026gt;sd_jdesc is non-NULL before\ndereferencing it.  Otherwise, we could run into a NULL pointer\ndereference when outstanding glock work races with an unmount\n(glock_work_func -\u0026gt; run_queue -\u0026gt; do_xmote -\u0026gt; inode_go_sync -\u0026gt;\ngfs2_log_flush).(CVE-2024-42079)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock\r\n\r\nWhen config CONFIG_USB_DWC3_DUAL_ROLE is selected, and trigger system\nto enter suspend status with below command:\necho mem \u0026gt; /sys/power/state\nThere will be a deadlock issue occurring. Detailed invoking path as\nbelow:\ndwc3_suspend_common()\n    spin_lock_irqsave(\u0026amp;dwc-\u0026gt;lock, flags);              \u0026lt;-- 1st\n    dwc3_gadget_suspend(dwc);\n        dwc3_gadget_soft_disconnect(dwc);\n            spin_lock_irqsave(\u0026amp;dwc-\u0026gt;lock, flags);      \u0026lt;-- 2nd\nThis issue is exposed by commit c7ebd8149ee5 (\u0026quot;usb: dwc3: gadget: Fix\nNULL pointer dereference in dwc3_gadget_suspend\u0026quot;) that removes the code\nof checking whether dwc-\u0026gt;gadget_driver is NULL or not. It causes the\nfollowing code is executed and deadlock occurs when trying to get the\nspinlock. In fact, the root cause is the commit 5265397f9442(\u0026quot;usb: dwc3:\nRemove DWC3 locking during gadget suspend/resume\u0026quot;) that forgot to remove\nthe lock of otg mode. So, remove the redundant lock of otg mode during\ngadget suspend/resume.(CVE-2024-42085)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nclk: sunxi-ng: common: Don\u0026apos;t call hw_to_ccu_common on hw without common\r\n\r\nIn order to set the rate range of a hw sunxi_ccu_probe calls\nhw_to_ccu_common() assuming all entries in desc-\u0026gt;ccu_clks are contained\nin a ccu_common struct. This assumption is incorrect and, in\nconsequence, causes invalid pointer de-references.\r\n\r\nRemove the faulty call. Instead, add one more loop that iterates over\nthe ccu_clks and sets the rate range, if required.(CVE-2024-42100)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: fix adding block group to a reclaim list and the unused list during reclaim\r\n\r\nThere is a potential parallel list adding for retrying in\nbtrfs_reclaim_bgs_work and adding to the unused list. Since the block\ngroup is removed from the reclaim list and it is on a relocation work,\nit can be added into the unused list in parallel. When that happens,\nadding it to the reclaim list will corrupt the list head and trigger\nlist corruption like below.\r\n\r\nFix it by taking fs_info-\u0026gt;unused_bgs_lock.\r\n\r\n  [177.504][T2585409] BTRFS error (device nullb1): error relocating ch= unk 2415919104\n  [177.514][T2585409] list_del corruption. next-\u0026gt;prev should be ff1100= 0344b119c0, but was ff11000377e87c70. (next=3Dff110002390cd9c0)\n  [177.529][T2585409] ------------[ cut here ]------------\n  [177.537][T2585409] kernel BUG at lib/list_debug.c:65!\n  [177.545][T2585409] Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\n  [177.555][T2585409] CPU: 9 PID: 2585409 Comm: kworker/u128:2 Tainted: G        W          6.10.0-rc5-kts #1\n  [177.568][T2585409] Hardware name: Supermicro SYS-520P-WTR/X12SPW-TF, BIOS 1.2 02/14/2022\n  [177.579][T2585409] Workqueue: events_unbound btrfs_reclaim_bgs_work[btrfs]\n  [177.589][T2585409] RIP: 0010:__list_del_entry_valid_or_report.cold+0x70/0x72\n  [177.624][T2585409] RSP: 0018:ff11000377e87a70 EFLAGS: 00010286\n  [177.633][T2585409] RAX: 000000000000006d RBX: ff11000344b119c0 RCX:0000000000000000\n  [177.644][T2585409] RDX: 000000000000006d RSI: 0000000000000008 RDI:ffe21c006efd0f40\n  [177.655][T2585409] RBP: ff110002e0509f78 R08: 0000000000000001 R09:ffe21c006efd0f08\n  [177.665][T2585409] R10: ff11000377e87847 R11: 0000000000000000 R12:ff110002390cd9c0\n  [177.676][T2585409] R13: ff11000344b119c0 R14: ff110002e0508000 R15:dffffc0000000000\n  [177.687][T2585409] FS:  0000000000000000(0000) GS:ff11000fec880000(0000) knlGS:0000000000000000\n  [177.700][T2585409] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  [177.709][T2585409] CR2: 00007f06bc7b1978 CR3: 0000001021e86005 CR4:0000000000771ef0\n  [177.720][T2585409] DR0: 0000000000000000 DR1: 0000000000000000 DR2:0000000000000000\n  [177.731][T2585409] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:0000000000000400\n  [177.742][T2585409] PKRU: 55555554\n  [177.748][T2585409] Call Trace:\n  [177.753][T2585409]  \u0026lt;TASK\u0026gt;\n  [177.759][T2585409]  ? __die_body.cold+0x19/0x27\n  [177.766][T2585409]  ? die+0x2e/0x50\n  [177.772][T2585409]  ? do_trap+0x1ea/0x2d0\n  [177.779][T2585409]  ? __list_del_entry_valid_or_report.cold+0x70/0x72\n  [177.788][T2585409]  ? do_error_trap+0xa3/0x160\n  [177.795][T2585409]  ? __list_del_entry_valid_or_report.cold+0x70/0x72\n  [177.805][T2585409]  ? handle_invalid_op+0x2c/0x40\n  [177.812][T2585409]  ? __list_del_entry_valid_or_report.cold+0x70/0x72\n  [177.820][T2585409]  ? exc_invalid_op+0x2d/0x40\n  [177.827][T2585409]  ? asm_exc_invalid_op+0x1a/0x20\n  [177.834][T2585409]  ? __list_del_entry_valid_or_report.cold+0x70/0x72\n  [177.843][T2585409]  btrfs_delete_unused_bgs+0x3d9/0x14c0 [btrfs]\r\n\r\nThere is a similar retry_list code in btrfs_delete_unused_bgs(), but it is\nsafe, AFAICS. Since the block group was in the unused list, the used bytes\nshould be 0 when it was added to the unused list. Then, it checks\nblock_group-\u0026gt;{used,reserved,pinned} are still 0 under the\nblock_group-\u0026gt;lock. So, they should be still eligible for the unused list,\nnot the reclaim list.\r\n\r\nThe reason it is safe there it\u0026apos;s because because we\u0026apos;re holding\nspace_info-\u0026gt;groups_sem in write mode.\r\n\r\nThat means no other task can allocate from the block group, so while we\nare at deleted_unused_bgs() it\u0026apos;s not possible for other tasks to\nallocate and deallocate extents from the block group, so it can\u0026apos;t be\nadded to the unused list or the reclaim list by anyone else.\r\n\r\nThe bug can be reproduced by btrfs/166 after a few rounds. In practice\nthis can be hit when relocation cannot find more chunk space and ends\nwith ENOSPC.(CVE-2024-42103)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: unconditionally flush pending work before notifier\r\n\r\nsyzbot reports:\r\n\r\nKASAN: slab-uaf in nft_ctx_update include/net/netfilter/nf_tables.h:1831\nKASAN: slab-uaf in nft_commit_release net/netfilter/nf_tables_api.c:9530\nKASAN: slab-uaf int nf_tables_trans_destroy_work+0x152b/0x1750 net/netfilter/nf_tables_api.c:9597\nRead of size 2 at addr ffff88802b0051c4 by task kworker/1:1/45\n[..]\nWorkqueue: events nf_tables_trans_destroy_work\nCall Trace:\n nft_ctx_update include/net/netfilter/nf_tables.h:1831 [inline]\n nft_commit_release net/netfilter/nf_tables_api.c:9530 [inline]\n nf_tables_trans_destroy_work+0x152b/0x1750 net/netfilter/nf_tables_api.c:9597\r\n\r\nProblem is that the notifier does a conditional flush, but its possible\nthat the table-to-be-removed is still referenced by transactions being\nprocessed by the worker, so we need to flush unconditionally.\r\n\r\nWe could make the flush_work depend on whether we found a table to delete\nin nf-next to avoid the flush for most cases.\r\n\r\nAFAICS this problem is only exposed in nf-next, with\ncommit e169285f8c56 (\u0026quot;netfilter: nf_tables: do not store nft_ctx in transaction objects\u0026quot;),\nwith this commit applied there is an unconditional fetch of\ntable-\u0026gt;family which is whats triggering the above splat.(CVE-2024-42109)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: txgbe: initialize num_q_vectors for MSI/INTx interrupts\r\n\r\nWhen using MSI/INTx interrupts, wx-\u0026gt;num_q_vectors is uninitialized.\nThus there will be kernel panic in wx_alloc_q_vectors() to allocate\nqueue vectors.(CVE-2024-42113)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check pipe offset before setting vblank\r\n\r\npipe_ctx has a size of MAX_PIPES so checking its index before accessing\nthe array.\r\n\r\nThis fixes an OVERRUN issue reported by Coverity.(CVE-2024-42120)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check index msg_id before read or write\r\n\r\n[WHAT]\nmsg_id is used as an array index and it cannot be a negative value, and\ntherefore cannot be equal to MOD_HDCP_MESSAGE_ID_INVALID (-1).\r\n\r\n[HOW]\nCheck whether msg_id is valid before reading and setting.\r\n\r\nThis fixes 4 OVERRUN issues reported by Coverity.(CVE-2024-42121)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc/nci: Add the inconsistency check between the input data length and count\r\n\r\nwrite$nci(r0, \u0026amp;(0x7f0000000740)=ANY=[@ANYBLOB=\u0026quot;610501\u0026quot;], 0xf)\r\n\r\nSyzbot constructed a write() call with a data length of 3 bytes but a count value\nof 15, which passed too little data to meet the basic requirements of the function\nnci_rf_intf_activated_ntf_packet().\r\n\r\nTherefore, increasing the comparison between data length and count value to avoid\nproblems caused by inconsistent data length and count.(CVE-2024-42130)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbluetooth/hci: disallow setting handle bigger than HCI_CONN_HANDLE_MAX\r\n\r\nSyzbot hit warning in hci_conn_del() caused by freeing handle that was\nnot allocated using ida allocator.\r\n\r\nThis is caused by handle bigger than HCI_CONN_HANDLE_MAX passed by\nhci_le_big_sync_established_evt(), which makes code think it\u0026apos;s unset\nconnection.\r\n\r\nAdd same check for handle upper bound as in hci_conn_set_handle() to\nprevent warning.(CVE-2024-42132)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: Ignore too large handle values in BIG\r\n\r\nhci_le_big_sync_established_evt is necessary to filter out cases where the\nhandle value is belonging to ida id range, otherwise ida will be erroneously\nreleased in hci_conn_cleanup.(CVE-2024-42133)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nvhost_task: Handle SIGKILL by flushing work and exiting\r\n\r\nInstead of lingering until the device is closed, this has us handle\nSIGKILL by:\r\n\r\n1. marking the worker as killed so we no longer try to use it with\n   new virtqueues and new flush operations.\n2. setting the virtqueue to worker mapping so no new works are queued.\n3. running all the exiting works.(CVE-2024-42135)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncdrom: rearrange last_media_change check to avoid unintentional overflow\r\n\r\nWhen running syzkaller with the newly reintroduced signed integer wrap\nsanitizer we encounter this splat:\r\n\r\n[  366.015950] UBSAN: signed-integer-overflow in ../drivers/cdrom/cdrom.c:2361:33\n[  366.021089] -9223372036854775808 - 346321 cannot be represented in type \u0026apos;__s64\u0026apos; (aka \u0026apos;long long\u0026apos;)\n[  366.025894] program syz-executor.4 is using a deprecated SCSI ioctl, please convert it to SG_IO\n[  366.027502] CPU: 5 PID: 28472 Comm: syz-executor.7 Not tainted 6.8.0-rc2-00035-gb3ef86b5a957 #1\n[  366.027512] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  366.027518] Call Trace:\n[  366.027523]  \u0026lt;TASK\u0026gt;\n[  366.027533]  dump_stack_lvl+0x93/0xd0\n[  366.027899]  handle_overflow+0x171/0x1b0\n[  366.038787] ata1.00: invalid multi_count 32 ignored\n[  366.043924]  cdrom_ioctl+0x2c3f/0x2d10\n[  366.063932]  ? __pm_runtime_resume+0xe6/0x130\n[  366.071923]  sr_block_ioctl+0x15d/0x1d0\n[  366.074624]  ? __pfx_sr_block_ioctl+0x10/0x10\n[  366.077642]  blkdev_ioctl+0x419/0x500\n[  366.080231]  ? __pfx_blkdev_ioctl+0x10/0x10\n...\r\n\r\nHistorically, the signed integer overflow sanitizer did not work in the\nkernel due to its interaction with `-fwrapv` but this has since been\nchanged [1] in the newest version of Clang. It was re-enabled in the\nkernel with Commit 557f8c582a9ba8ab (\u0026quot;ubsan: Reintroduce signed overflow\nsanitizer\u0026quot;).\r\n\r\nLet\u0026apos;s rearrange the check to not perform any arithmetic, thus not\ntripping the sanitizer.(CVE-2024-42136)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file\r\n\r\nIn case of invalid INI file mlxsw_linecard_types_init() deallocates memory\nbut doesn\u0026apos;t reset pointer to NULL and returns 0. In case of any error\noccurred after mlxsw_linecard_types_init() call, mlxsw_linecards_init()\ncalls mlxsw_linecard_types_fini() which performs memory deallocation again.\r\n\r\nAdd pointer reset to NULL.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-42138)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: kexec: Avoid deadlock in kexec crash path\r\n\r\nIf the kexec crash code is called in the interrupt context, the\nmachine_kexec_mask_interrupts() function will trigger a deadlock while\ntrying to acquire the irqdesc spinlock and then deactivate irqchip in\nirq_set_irqchip_state() function.\r\n\r\nUnlike arm64, riscv only requires irq_eoi handler to complete EOI and\nkeeping irq_set_irqchip_state() will only leave this possible deadlock\nwithout any use. So we simply remove it.(CVE-2024-42140)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: E-switch, Create ingress ACL when needed\r\n\r\nCurrently, ingress acl is used for three features. It is created only\nwhen vport metadata match and prio tag are enabled. But active-backup\nlag mode also uses it. It is independent of vport metadata match and\nprio tag. And vport metadata match can be disabled using the\nfollowing devlink command:\r\n\r\n # devlink dev param set pci/0000:08:00.0 name esw_port_metadata \\\n\tvalue false cmode runtime\r\n\r\nIf ingress acl is not created, will hit panic when creating drop rule\nfor active-backup lag mode. If always create it, there will be about\n5% performance degradation.\r\n\r\nFix it by creating ingress acl when needed. If esw_port_metadata is\ntrue, ingress acl exists, then create drop rule using existing\ningress acl. If esw_port_metadata is false, create ingress acl and\nthen create drop rule.(CVE-2024-42142)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nthermal/drivers/mediatek/lvts_thermal: Check NULL ptr on lvts_data\r\n\r\nVerify that lvts_data is not NULL before using it.(CVE-2024-42144)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/pkey: Wipe copies of clear-key structures on failure\r\n\r\nWipe all sensitive data from stack for all IOCTLs, which convert a\nclear-key into a protected- or secure-key.(CVE-2024-42156)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: check validation of fault attrs in f2fs_build_fault_attr()\r\n\r\n- It missed to check validation of fault attrs in parse_options(),\nlet\u0026apos;s fix to add check condition in f2fs_build_fault_attr().\n- Use f2fs_build_fault_attr() in __sbi_store() to clean up code.(CVE-2024-42160)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD\r\n\r\n[Changes from V1:\n - Use a default branch in the switch statement to initialize `val\u0026apos;.]\r\n\r\nGCC warns that `val\u0026apos; may be used uninitialized in the\nBPF_CRE_READ_BITFIELD macro, defined in bpf_core_read.h as:\r\n\r\n\t[...]\n\tunsigned long long val;\t\t\t\t\t\t      \\\n\t[...]\t\t\t\t\t\t\t\t      \\\n\tswitch (__CORE_RELO(s, field, BYTE_SIZE)) {\t\t\t      \\\n\tcase 1: val = *(const unsigned char *)p; break;\t\t\t      \\\n\tcase 2: val = *(const unsigned short *)p; break;\t\t      \\\n\tcase 4: val = *(const unsigned int *)p; break;\t\t\t      \\\n\tcase 8: val = *(const unsigned long long *)p; break;\t\t      \\\n        }       \t\t\t\t\t\t\t      \\\n\t[...]\n\tval;\t\t\t\t\t\t\t\t      \\\n\t}\t\t\t\t\t\t\t\t      \\\r\n\r\nThis patch adds a default entry in the switch statement that sets\n`val\u0026apos; to zero in order to avoid the warning, and random values to be\nused in case __builtin_preserve_field_info returns unexpected values\nfor BPF_FIELD_BYTE_SIZE.\r\n\r\nTested in bpf-next master.\nNo regressions.(CVE-2024-42161)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: mv88e6xxx: Correct check for empty list\r\n\r\nSince commit a3c53be55c95 (\u0026quot;net: dsa: mv88e6xxx: Support multiple MDIO\nbusses\u0026quot;) mv88e6xxx_default_mdio_bus() has checked that the\nreturn value of list_first_entry() is non-NULL.\r\n\r\nThis appears to be intended to guard against the list chip-\u0026gt;mdios being\nempty.  However, it is not the correct check as the implementation of\nlist_first_entry is not designed to return NULL for empty lists.\r\n\r\nInstead, use list_first_entry_or_null() which does return NULL if the\nlist is empty.\r\n\r\nFlagged by Smatch.\nCompile tested only.(CVE-2024-42224)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mt76: replace skb_put with skb_put_zero\r\n\r\nAvoid potentially reusing uninitialized data(CVE-2024-42225)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npowerpc/pseries: Fix scv instruction crash with kexec\r\n\r\nkexec on pseries disables AIL (reloc_on_exc), required for scv\ninstruction support, before other CPUs have been shut down. This means\nthey can execute scv instructions after AIL is disabled, which causes an\ninterrupt at an unexpected entry location that crashes the kernel.\r\n\r\nChange the kexec sequence to disable AIL after other CPUs have been\nbrought down.\r\n\r\nAs a refresher, the real-mode scv interrupt vector is 0x17000, and the\nfixed-location head code probably couldn\u0026apos;t easily deal with implementing\nsuch high addresses so it was just decided not to support that interrupt\nat all.(CVE-2024-42230)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nprotect the fetch of -\u0026gt;fd[fd] in do_dup2() from mispredictions\r\n\r\nboth callers have verified that fd is not greater than -\u0026gt;max_fds;\nhowever, misprediction might end up with\n        tofree = fdt-\u0026gt;fd[fd];\nbeing speculatively executed.  That\u0026apos;s wrong for the same reasons\nwhy it\u0026apos;s wrong in close_fd()/file_close_fd_locked(); the same\nsolution applies - array_index_nospec(fd, fdt-\u0026gt;max_fds) could differ\nfrom fd only in case of speculative execution on mispredicted path.(CVE-2024-42265)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv/mm: Add handling for VM_FAULT_SIGSEGV in mm_fault_error()\r\n\r\nHandle VM_FAULT_SIGSEGV in the page fault path so that we correctly\nkill the process and we don\u0026apos;t BUG() the kernel.(CVE-2024-42267)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Fix missing lock on sync reset reload\r\n\r\nOn sync reset reload work, when remote host updates devlink on reload\nactions performed on that host, it misses taking devlink lock before\ncalling devlink_remote_reload_actions_performed() which results in\ntriggering lock assert like the following:\r\n\r\nWARNING: CPU: 4 PID: 1164 at net/devlink/core.c:261 devl_assert_locked+0x3e/0x50\n…\n CPU: 4 PID: 1164 Comm: kworker/u96:6 Tainted: G S      W          6.10.0-rc2+ #116\n Hardware name: Supermicro SYS-2028TP-DECTR/X10DRT-PT, BIOS 2.0 12/18/2015\n Workqueue: mlx5_fw_reset_events mlx5_sync_reset_reload_work [mlx5_core]\n RIP: 0010:devl_assert_locked+0x3e/0x50\n…\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __warn+0xa4/0x210\n  ? devl_assert_locked+0x3e/0x50\n  ? report_bug+0x160/0x280\n  ? handle_bug+0x3f/0x80\n  ? exc_invalid_op+0x17/0x40\n  ? asm_exc_invalid_op+0x1a/0x20\n  ? devl_assert_locked+0x3e/0x50\n  devlink_notify+0x88/0x2b0\n  ? mlx5_attach_device+0x20c/0x230 [mlx5_core]\n  ? __pfx_devlink_notify+0x10/0x10\n  ? process_one_work+0x4b6/0xbb0\n  process_one_work+0x4b6/0xbb0\n[…](CVE-2024-42268)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init().\r\n\r\nip6table_nat_table_init() accesses net-\u0026gt;gen-\u0026gt;ptr[ip6table_nat_net_ops.id],\nbut the function is exposed to user space before the entry is allocated\nvia register_pernet_subsys().\r\n\r\nLet\u0026apos;s call register_pernet_subsys() before xt_register_template().(CVE-2024-42269)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init().\r\n\r\nWe had a report that iptables-restore sometimes triggered null-ptr-deref\nat boot time. [0]\r\n\r\nThe problem is that iptable_nat_table_init() is exposed to user space\nbefore the kernel fully initialises netns.\r\n\r\nIn the small race window, a user could call iptable_nat_table_init()\nthat accesses net_generic(net, iptable_nat_net_id), which is available\nonly after registering iptable_nat_net_ops.\r\n\r\nLet\u0026apos;s call register_pernet_subsys() before xt_register_template().\r\n\r\n[0]:\nbpfilter: Loaded bpfilter_umh pid 11702\nStarted bpfilter\nBUG: kernel NULL pointer dereference, address: 0000000000000013\n PF: supervisor write access in kernel mode\n PF: error_code(0x0002) - not-present page\nPGD 0 P4D 0\nPREEMPT SMP NOPTI\nCPU: 2 PID: 11879 Comm: iptables-restor Not tainted 6.1.92-99.174.amzn2023.x86_64 #1\nHardware name: Amazon EC2 c6i.4xlarge/, BIOS 1.0 10/16/2017\nRIP: 0010:iptable_nat_table_init (net/ipv4/netfilter/iptable_nat.c:87 net/ipv4/netfilter/iptable_nat.c:121) iptable_nat\nCode: 10 4c 89 f6 48 89 ef e8 0b 19 bb ff 41 89 c4 85 c0 75 38 41 83 c7 01 49 83 c6 28 41 83 ff 04 75 dc 48 8b 44 24 08 48 8b 0c 24 \u0026lt;48\u0026gt; 89 08 4c 89 ef e8 a2 3b a2 cf 48 83 c4 10 44 89 e0 5b 5d 41 5c\nRSP: 0018:ffffbef902843cd0 EFLAGS: 00010246\nRAX: 0000000000000013 RBX: ffff9f4b052caa20 RCX: ffff9f4b20988d80\nRDX: 0000000000000000 RSI: 0000000000000064 RDI: ffffffffc04201c0\nRBP: ffff9f4b29394000 R08: ffff9f4b07f77258 R09: ffff9f4b07f77240\nR10: 0000000000000000 R11: ffff9f4b09635388 R12: 0000000000000000\nR13: ffff9f4b1a3c6c00 R14: ffff9f4b20988e20 R15: 0000000000000004\nFS:  00007f6284340000(0000) GS:ffff9f51fe280000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000013 CR3: 00000001d10a6005 CR4: 00000000007706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? show_trace_log_lvl (arch/x86/kernel/dumpstack.c:259)\n ? show_trace_log_lvl (arch/x86/kernel/dumpstack.c:259)\n ? xt_find_table_lock (net/netfilter/x_tables.c:1259)\n ? __die_body.cold (arch/x86/kernel/dumpstack.c:478 arch/x86/kernel/dumpstack.c:420)\n ? page_fault_oops (arch/x86/mm/fault.c:727)\n ? exc_page_fault (./arch/x86/include/asm/irqflags.h:40 ./arch/x86/include/asm/irqflags.h:75 arch/x86/mm/fault.c:1470 arch/x86/mm/fault.c:1518)\n ? asm_exc_page_fault (./arch/x86/include/asm/idtentry.h:570)\n ? iptable_nat_table_init (net/ipv4/netfilter/iptable_nat.c:87 net/ipv4/netfilter/iptable_nat.c:121) iptable_nat\n xt_find_table_lock (net/netfilter/x_tables.c:1259)\n xt_request_find_table_lock (net/netfilter/x_tables.c:1287)\n get_info (net/ipv4/netfilter/ip_tables.c:965)\n ? security_capable (security/security.c:809 (discriminator 13))\n ? ns_capable (kernel/capability.c:376 kernel/capability.c:397)\n ? do_ipt_get_ctl (net/ipv4/netfilter/ip_tables.c:1656)\n ? bpfilter_send_req (net/bpfilter/bpfilter_kern.c:52) bpfilter\n nf_getsockopt (net/netfilter/nf_sockopt.c:116)\n ip_getsockopt (net/ipv4/ip_sockglue.c:1827)\n __sys_getsockopt (net/socket.c:2327)\n __x64_sys_getsockopt (net/socket.c:2342 net/socket.c:2339 net/socket.c:2339)\n do_syscall_64 (arch/x86/entry/common.c:51 arch/x86/entry/common.c:81)\n entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)\nRIP: 0033:0x7f62844685ee\nCode: 48 8b 0d 45 28 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 37 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 09\nRSP: 002b:00007ffd1f83d638 EFLAGS: 00000246 ORIG_RAX: 0000000000000037\nRAX: ffffffffffffffda RBX: 00007ffd1f83d680 RCX: 00007f62844685ee\nRDX: 0000000000000040 RSI: 0000000000000000 RDI: 0000000000000004\nRBP: 0000000000000004 R08: 00007ffd1f83d670 R09: 0000558798ffa2a0\nR10: 00007ffd1f83d680 R11: 0000000000000246 R12: 00007ffd1f83e3b2\nR13: 00007f6284\n---truncated---(CVE-2024-42270)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: assign CURSEG_ALL_DATA_ATGC if blkaddr is valid\r\n\r\nmkdir /mnt/test/comp\nf2fs_io setflags compression /mnt/test/comp\ndd if=/dev/zero of=/mnt/test/comp/testfile bs=16k count=1\ntruncate --size 13 /mnt/test/comp/testfile\r\n\r\nIn the above scenario, we can get a BUG_ON.\n kernel BUG at fs/f2fs/segment.c:3589!\n Call Trace:\n  do_write_page+0x78/0x390 [f2fs]\n  f2fs_outplace_write_data+0x62/0xb0 [f2fs]\n  f2fs_do_write_data_page+0x275/0x740 [f2fs]\n  f2fs_write_single_data_page+0x1dc/0x8f0 [f2fs]\n  f2fs_write_multi_pages+0x1e5/0xae0 [f2fs]\n  f2fs_write_cache_pages+0xab1/0xc60 [f2fs]\n  f2fs_write_data_pages+0x2d8/0x330 [f2fs]\n  do_writepages+0xcf/0x270\n  __writeback_single_inode+0x44/0x350\n  writeback_sb_inodes+0x242/0x530\n  __writeback_inodes_wb+0x54/0xf0\n  wb_writeback+0x192/0x310\n  wb_workfn+0x30d/0x400\r\n\r\nThe reason is we gave CURSEG_ALL_DATA_ATGC to COMPR_ADDR where the\npage was set the gcing flag by set_cluster_dirty().(CVE-2024-42273)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRevert \u0026quot;ALSA: firewire-lib: operate for period elapse event in process context\u0026quot;\r\n\r\nCommit 7ba5ca32fe6e (\u0026quot;ALSA: firewire-lib: operate for period elapse event\nin process context\u0026quot;) removed the process context workqueue from\namdtp_domain_stream_pcm_pointer() and update_pcm_pointers() to remove\nits overhead.\r\n\r\nWith RME Fireface 800, this lead to a regression since\nKernels 5.14.0, causing an AB/BA deadlock competition for the\nsubstream lock with eventual system freeze under ALSA operation:\r\n\r\nthread 0:\n    * (lock A) acquire substream lock by\n\tsnd_pcm_stream_lock_irq() in\n\tsnd_pcm_status64()\n    * (lock B) wait for tasklet to finish by calling\n    \ttasklet_unlock_spin_wait() in\n\ttasklet_disable_in_atomic() in\n\tohci_flush_iso_completions() of ohci.c\r\n\r\nthread 1:\n    * (lock B) enter tasklet\n    * (lock A) attempt to acquire substream lock,\n    \twaiting for it to be released:\n\tsnd_pcm_stream_lock_irqsave() in\n    \tsnd_pcm_period_elapsed() in\n\tupdate_pcm_pointers() in\n\tprocess_ctx_payloads() in\n\tprocess_rx_packets() of amdtp-stream.c\r\n\r\n? tasklet_unlock_spin_wait\n \u0026lt;/NMI\u0026gt;\n \u0026lt;TASK\u0026gt;\nohci_flush_iso_completions firewire_ohci\namdtp_domain_stream_pcm_pointer snd_firewire_lib\nsnd_pcm_update_hw_ptr0 snd_pcm\nsnd_pcm_status64 snd_pcm\r\n\r\n? native_queued_spin_lock_slowpath\n \u0026lt;/NMI\u0026gt;\n \u0026lt;IRQ\u0026gt;\n_raw_spin_lock_irqsave\nsnd_pcm_period_elapsed snd_pcm\nprocess_rx_packets snd_firewire_lib\nirq_target_callback snd_firewire_lib\nhandle_it_packet firewire_ohci\ncontext_tasklet firewire_ohci\r\n\r\nRestore the process context work queue to prevent deadlock\nAB/BA deadlock competition for ALSA substream lock of\nsnd_pcm_stream_lock_irq() in snd_pcm_status64()\nand snd_pcm_stream_lock_irqsave() in snd_pcm_period_elapsed().\r\n\r\nrevert commit 7ba5ca32fe6e (\u0026quot;ALSA: firewire-lib: operate for period\nelapse event in process context\u0026quot;)\r\n\r\nReplace inline description to prevent future deadlock.(CVE-2024-42274)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: Return non-zero value from tipc_udp_addr2str() on error\r\n\r\ntipc_udp_addr2str() should return non-zero value if the UDP media\naddress is invalid. Otherwise, a buffer overflow access can occur in\ntipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP\nmedia address.(CVE-2024-42284)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/iwcm: Fix a use-after-free related to destroying CM IDs\r\n\r\niw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with\nan existing struct iw_cm_id (cm_id) as follows:\r\n\r\n        conn_id-\u0026gt;cm_id.iw = cm_id;\n        cm_id-\u0026gt;context = conn_id;\n        cm_id-\u0026gt;cm_handler = cma_iw_handler;\r\n\r\nrdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make\nsure that cm_work_handler() does not trigger a use-after-free by only\nfreeing of the struct rdma_id_private after all pending work has finished.(CVE-2024-42285)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI/DPC: Fix use-after-free on concurrent DPC and hot-removal\r\n\r\nKeith reports a use-after-free when a DPC event occurs concurrently to\nhot-removal of the same portion of the hierarchy:\r\n\r\nThe dpc_handler() awaits readiness of the secondary bus below the\nDownstream Port where the DPC event occurred.  To do so, it polls the\nconfig space of the first child device on the secondary bus.  If that\nchild device is concurrently removed, accesses to its struct pci_dev\ncause the kernel to oops.\r\n\r\nThat\u0026apos;s because pci_bridge_wait_for_secondary_bus() neglects to hold a\nreference on the child device.  Before v6.3, the function was only\ncalled on resume from system sleep or on runtime resume.  Holding a\nreference wasn\u0026apos;t necessary back then because the pciehp IRQ thread\ncould never run concurrently.  (On resume from system sleep, IRQs are\nnot enabled until after the resume_noirq phase.  And runtime resume is\nalways awaited before a PCI device is removed.)\r\n\r\nHowever starting with v6.3, pci_bridge_wait_for_secondary_bus() is also\ncalled on a DPC event.  Commit 53b54ad074de (\u0026quot;PCI/DPC: Await readiness\nof secondary bus after reset\u0026quot;), which introduced that, failed to\nappreciate that pci_bridge_wait_for_secondary_bus() now needs to hold a\nreference on the child device because dpc_handler() and pciehp may\nindeed run concurrently.  The commit was backported to v5.10+ stable\nkernels, so that\u0026apos;s the oldest one affected.\r\n\r\nAdd the missing reference acquisition.\r\n\r\nAbridged stack trace:\r\n\r\n  BUG: unable to handle page fault for address: 00000000091400c0\n  CPU: 15 PID: 2464 Comm: irq/53-pcie-dpc 6.9.0\n  RIP: pci_bus_read_config_dword+0x17/0x50\n  pci_dev_wait()\n  pci_bridge_wait_for_secondary_bus()\n  dpc_reset_link()\n  pcie_do_recovery()\n  dpc_handler()(CVE-2024-42302)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkvm: s390: Reject memory region operations for ucontrol VMs\r\n\r\nThis change rejects the KVM_SET_USER_MEMORY_REGION and\nKVM_SET_USER_MEMORY_REGION2 ioctls when called on a ucontrol VM.\nThis is necessary since ucontrol VMs have kvm-\u0026gt;arch.gmap set to 0 and\nwould thus result in a null pointer dereference further in.\nMemory management needs to be performed in userspace and using the\nioctls KVM_S390_UCAS_MAP and KVM_S390_UCAS_UNMAP.\r\n\r\nAlso improve s390 specific documentation for KVM_SET_USER_MEMORY_REGION\nand KVM_SET_USER_MEMORY_REGION2.\r\n\r\n[frankja@linux.ibm.com: commit message spelling fix, subject prefix fix](CVE-2024-43819)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: endpoint: pci-epf-test: Make use of cached \u0026apos;epc_features\u0026apos; in pci_epf_test_core_init()\r\n\r\nInstead of getting the epc_features from pci_epc_get_features() API, use\nthe cached pci_epf_test::epc_features value to avoid the NULL check. Since\nthe NULL check is already performed in pci_epf_test_bind(), having one more\ncheck in pci_epf_test_core_init() is redundant and it is not possible to\nhit the NULL pointer dereference.\r\n\r\nAlso with commit a01e7214bef9 (\u0026quot;PCI: endpoint: Remove \u0026quot;core_init_notifier\u0026quot;\nflag\u0026quot;), \u0026apos;epc_features\u0026apos; got dereferenced without the NULL check, leading to\nthe following false positive Smatch warning:\r\n\r\n  drivers/pci/endpoint/functions/pci-epf-test.c:784 pci_epf_test_core_init() error: we previously assumed \u0026apos;epc_features\u0026apos; could be null (see line 747)\r\n\r\nThus, remove the redundant NULL check and also use the epc_features::\n{msix_capable/msi_capable} flags directly to avoid local variables.\r\n\r\n[kwilczynski: commit log](CVE-2024-43824)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncgroup/cpuset: Prevent UAF in proc_cpuset_show()\r\n\r\nAn UAF can happen when /proc/cpuset is read as reported in [1].\r\n\r\nThis can be reproduced by the following methods:\n1.add an mdelay(1000) before acquiring the cgroup_lock In the\n cgroup_path_ns function.\n2.$cat /proc/\u0026lt;pid\u0026gt;/cpuset   repeatly.\n3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/\n$umount /sys/fs/cgroup/cpuset/   repeatly.\r\n\r\nThe race that cause this bug can be shown as below:\r\n\r\n(umount)\t\t|\t(cat /proc/\u0026lt;pid\u0026gt;/cpuset)\ncss_release\t\t|\tproc_cpuset_show\ncss_release_work_fn\t|\tcss = task_get_css(tsk, cpuset_cgrp_id);\ncss_free_rwork_fn\t|\tcgroup_path_ns(css-\u0026gt;cgroup, ...);\ncgroup_destroy_root\t|\tmutex_lock(\u0026amp;cgroup_mutex);\nrebind_subsystems\t|\ncgroup_free_root \t|\n\t\t\t|\t// cgrp was freed, UAF\n\t\t\t|\tcgroup_path_ns_locked(cgrp,..);\r\n\r\nWhen the cpuset is initialized, the root node top_cpuset.css.cgrp\nwill point to \u0026amp;cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will\nallocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated\n\u0026amp;cgroup_root.cgrp. When the umount operation is executed,\ntop_cpuset.css.cgrp will be rebound to \u0026amp;cgrp_dfl_root.cgrp.\r\n\r\nThe problem is that when rebinding to cgrp_dfl_root, there are cases\nwhere the cgroup_root allocated by setting up the root for cgroup v1\nis cached. This could lead to a Use-After-Free (UAF) if it is\nsubsequently freed. The descendant cgroups of cgroup v1 can only be\nfreed after the css is released. However, the css of the root will never\nbe released, yet the cgroup_root should be freed when it is unmounted.\nThis means that obtaining a reference to the css of the root does\nnot guarantee that css.cgrp-\u0026gt;root will not be freed.\r\n\r\nFix this problem by using rcu_read_lock in proc_cpuset_show().\nAs cgroup_root is kfree_rcu after commit d23b5c577715\n(\u0026quot;cgroup: Make operations on the cgroup root_list RCU safe\u0026quot;),\ncss-\u0026gt;cgroup won\u0026apos;t be freed during the critical section.\nTo call cgroup_path_ns_locked, css_set_lock is needed, so it is safe to\nreplace task_get_css with task_css.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=9b1ff7be974a403aa4cd(CVE-2024-43853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: qmi_wwan: fix memory leak for not ip packets\r\n\r\nFree the unused skb when not ip packets arrive.(CVE-2024-43861)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/vmwgfx: Fix a deadlock in dma buf fence polling\r\n\r\nIntroduce a version of the fence ops that on release doesn\u0026apos;t remove\nthe fence from the pending list, and thus doesn\u0026apos;t require a lock to\nfix poll-\u0026gt;fence wait-\u0026gt;fence unref deadlocks.\r\n\r\nvmwgfx overwrites the wait callback to iterate over the list of all\nfences and update their status, to do that it holds a lock to prevent\nthe list modifcations from other threads. The fence destroy callback\nboth deletes the fence and removes it from the list of pending\nfences, for which it holds a lock.\r\n\r\ndma buf polling cb unrefs a fence after it\u0026apos;s been signaled: so the poll\ncalls the wait, which signals the fences, which are being destroyed.\nThe destruction tries to acquire the lock on the pending fences list\nwhich it can never get because it\u0026apos;s held by the wait from which it\nwas called.\r\n\r\nOld bug, but not a lot of userspace apps were using dma-buf polling\ninterfaces. Fix those, in particular this fixes KDE stalls/deadlock.(CVE-2024-43863)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5e: Fix CT entry update leaks of modify header context\r\n\r\nThe cited commit allocates a new modify header to replace the old\none when updating CT entry. But if failed to allocate a new one, eg.\nexceed the max number firmware can support, modify header will be\nan error pointer that will trigger a panic when deallocating it. And\nthe old modify header point is copied to old attr. When the old\nattr is freed, the old modify header is lost.\r\n\r\nFix it by restoring the old attr to attr when failed to allocate a\nnew modify header context. So when the CT entry is freed, the right\nmodify header context will be freed. And the panic of accessing\nerror pointer is also fixed.(CVE-2024-43864)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Always drain health in shutdown callback\r\n\r\nThere is no point in recovery during device shutdown. if health\nwork started need to wait for it to avoid races and NULL pointer\naccess.\r\n\r\nHence, drain health WQ on shutdown callback.(CVE-2024-43866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv/purgatory: align riscv_kernel_entry\r\n\r\nWhen alignment handling is delegated to the kernel, everything must be\nword-aligned in purgatory, since the trap handler is then set to the\nkexec one. Without the alignment, hitting the exception would\nultimately crash. On other occasions, the kernel\u0026apos;s handler would take\ncare of exceptions.\nThis has been tested on a JH7110 SoC with oreboot and its SBI delegating\nunaligned access exceptions and the kernel configured to handle them.(CVE-2024-43868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nperf: Fix event leak upon exec and file release\r\n\r\nThe perf pending task work is never waited upon the matching event\nrelease. In the case of a child event, released via free_event()\ndirectly, this can potentially result in a leaked event, such as in the\nfollowing scenario that doesn\u0026apos;t even require a weak IRQ work\nimplementation to trigger:\r\n\r\nschedule()\n   prepare_task_switch()\n=======\u0026gt; \u0026lt;NMI\u0026gt;\n      perf_event_overflow()\n         event-\u0026gt;pending_sigtrap = ...\n         irq_work_queue(\u0026amp;event-\u0026gt;pending_irq)\n\u0026lt;======= \u0026lt;/NMI\u0026gt;\n      perf_event_task_sched_out()\n          event_sched_out()\n              event-\u0026gt;pending_sigtrap = 0;\n              atomic_long_inc_not_zero(\u0026amp;event-\u0026gt;refcount)\n              task_work_add(\u0026amp;event-\u0026gt;pending_task)\n   finish_lock_switch()\n=======\u0026gt; \u0026lt;IRQ\u0026gt;\n   perf_pending_irq()\n      //do nothing, rely on pending task work\n\u0026lt;======= \u0026lt;/IRQ\u0026gt;\r\n\r\nbegin_new_exec()\n   perf_event_exit_task()\n      perf_event_exit_event()\n         // If is child event\n         free_event()\n            WARN(atomic_long_cmpxchg(\u0026amp;event-\u0026gt;refcount, 1, 0) != 1)\n            // event is leaked\r\n\r\nSimilar scenarios can also happen with perf_event_remove_on_exec() or\nsimply against concurrent perf_event_release().\r\n\r\nFix this with synchonizing against the possibly remaining pending task\nwork while freeing the event, just like is done with remaining pending\nIRQ work. This means that the pending task callback neither need nor\nshould hold a reference to the event, preventing it from ever beeing\nfreed.(CVE-2024-43869)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexec: Fix ToCToU between perm check and set-uid/gid usage\r\n\r\nWhen opening a file for exec via do_filp_open(), permission checking is\ndone against the file\u0026apos;s metadata at that moment, and on success, a file\npointer is passed back. Much later in the execve() code path, the file\nmetadata (specifically mode, uid, and gid) is used to determine if/how\nto set the uid and gid. However, those values may have changed since the\npermissions check, meaning the execution may gain unintended privileges.\r\n\r\nFor example, if a file could change permissions from executable and not\nset-id:\r\n\r\n---------x 1 root root 16048 Aug  7 13:16 target\r\n\r\nto set-id and non-executable:\r\n\r\n---S------ 1 root root 16048 Aug  7 13:16 target\r\n\r\nit is possible to gain root privileges when execution should have been\ndisallowed.\r\n\r\nWhile this race condition is rare in real-world scenarios, it has been\nobserved (and proven exploitable) when package managers are updating\nthe setuid bits of installed programs. Such files start with being\nworld-executable but then are adjusted to be group-exec with a set-uid\nbit. For example, \u0026quot;chmod o-x,u+s target\u0026quot; makes \u0026quot;target\u0026quot; executable only\nby uid \u0026quot;root\u0026quot; and gid \u0026quot;cdrom\u0026quot;, while also becoming setuid-root:\r\n\r\n-rwxr-xr-x 1 root cdrom 16048 Aug  7 13:16 target\r\n\r\nbecomes:\r\n\r\n-rwsr-xr-- 1 root cdrom 16048 Aug  7 13:16 target\r\n\r\nBut racing the chmod means users without group \u0026quot;cdrom\u0026quot; membership can\nget the permission to execute \u0026quot;target\u0026quot; just before the chmod, and when\nthe chmod finishes, the exec reaches brpm_fill_uid(), and performs the\nsetuid to root, violating the expressed authorization of \u0026quot;only cdrom\ngroup members can setuid to root\u0026quot;.\r\n\r\nRe-check that we still have execute permissions in case the metadata\nhas changed. It would be better to keep a copy from the perm-check time,\nbut until we can do that refactoring, the least-bad option is to do a\nfull inode_permission() call (under inode lock). It is understood that\nthis is safe against dead-locks, but hardly optimal.(CVE-2024-43882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix shift-out-of-bounds in dbDiscardAG\r\n\r\nWhen searching for the next smaller log2 block, BLKSTOL2() returned 0,\ncausing shift exponent -1 to be negative.\r\n\r\nThis patch fixes the issue by exiting the loop directly when negative\nshift is found.(CVE-2024-44938)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to cover read extent cache access with lock\r\n\r\nsyzbot reports a f2fs bug as below:\r\n\r\nBUG: KASAN: slab-use-after-free in sanity_check_extent_cache+0x370/0x410 fs/f2fs/extent_cache.c:46\nRead of size 4 at addr ffff8880739ab220 by task syz-executor200/5097\r\n\r\nCPU: 0 PID: 5097 Comm: syz-executor200 Not tainted 6.9.0-rc6-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n print_address_description mm/kasan/report.c:377 [inline]\n print_report+0x169/0x550 mm/kasan/report.c:488\n kasan_report+0x143/0x180 mm/kasan/report.c:601\n sanity_check_extent_cache+0x370/0x410 fs/f2fs/extent_cache.c:46\n do_read_inode fs/f2fs/inode.c:509 [inline]\n f2fs_iget+0x33e1/0x46e0 fs/f2fs/inode.c:560\n f2fs_nfs_get_inode+0x74/0x100 fs/f2fs/super.c:3237\n generic_fh_to_dentry+0x9f/0xf0 fs/libfs.c:1413\n exportfs_decode_fh_raw+0x152/0x5f0 fs/exportfs/expfs.c:444\n exportfs_decode_fh+0x3c/0x80 fs/exportfs/expfs.c:584\n do_handle_to_path fs/fhandle.c:155 [inline]\n handle_to_path fs/fhandle.c:210 [inline]\n do_handle_open+0x495/0x650 fs/fhandle.c:226\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nWe missed to cover sanity_check_extent_cache() w/ extent cache lock,\nso, below race case may happen, result in use after free issue.\r\n\r\n- f2fs_iget\n - do_read_inode\n  - f2fs_init_read_extent_tree\n  : add largest extent entry in to cache\n\t\t\t\t\t- shrink\n\t\t\t\t\t - f2fs_shrink_read_extent_tree\n\t\t\t\t\t  - __shrink_extent_tree\n\t\t\t\t\t   - __detach_extent_node\n\t\t\t\t\t   : drop largest extent entry\n  - sanity_check_extent_cache\n  : access et-\u0026gt;largest w/o lock\r\n\r\nlet\u0026apos;s refactor sanity_check_extent_cache() to avoid extent cache access\nand call it before f2fs_init_read_extent_tree() to fix this issue.(CVE-2024-44941)","status":"published","published":"2024-08-30T11:07:33Z","modified":"2026-08-18T01:17:32.191184185Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"RHSA-2024:9315","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-11-15T21:33:20Z","modified":"2026-10-20T10:31:15.230449418Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:14.610978Z"},{"id":"UBUNTU-CVE-2024-40945","description":"In the Linux kernel, the following vulnerability has been resolved: iommu: Return right value in iommu_sva_bind_device() iommu_sva_bind_device() should return either a sva bond handle or an ERR_PTR value in error cases. Existing drivers (idxd and uacce) only check the return value with IS_ERR(). This could potentially lead to a kernel NULL pointer dereference issue if the function returns NULL instead of an error pointer. In reality, this doesn't cause any problems because iommu_sva_bind_device() only returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA. In this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will return an error, and the device drivers won't call iommu_sva_bind_device() at all.","status":"published","published":"2024-07-12T13:15:00Z","modified":"2026-10-23T10:36:05.415267715Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T16:54:54.69008Z"},{"id":"CLSA-2024-1727817133","title":"Fix of 73 CVEs","description":"   * CVE-url: https://ubuntu.com/security/CVE-2024-26752\n     - l2tp: pass correct message length to ip6_append_data\n   * CVE-url: https://ubuntu.com/security/CVE-2021-47188\n     - scsi: ufs: core: Improve SCSI abort handling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26677\n     - rxrpc: Fix delayed ACKs to not set the reference serial number\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52527\n     - ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43882\n     - exec: Fix ToCToU between perm check and set-uid/gid usage\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48943\n     - KVM: x86/mmu: make apf token non-zero to fix bug\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38630\n     - watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44987\n     - ipv6: prevent UAF in ip6_send_skb()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42285\n     - RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48733\n     - btrfs: fix use-after-free after failure to create a snapshot\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44940\n     - fou: remove warn in gue_gro_receive on unsupported protocol\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41059\n     - hfsplus: fix uninit-value in copy_name\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46673\n     - scsi: aacraid: Fix double-free on probe failure\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42313\n     - media: venus: fix use after free in vdec_close\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44999\n     - gtp: pull network headers in gtp_dev_xmit()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42271\n     - net/iucv: fix use after free in iucv_sock_close()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44942\n     - f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43858\n     - jfs: Fix array-index-out-of-bounds in diFree\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41071\n     - wifi: mac80211: Avoid address calculations via out of bounds array indexing\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42301\n     - dev/parport: fix the array out-of-bounds risk\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46674\n     - usb: dwc3: st: fix probed platform device ref count on probe error path\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43900\n     - media: xc2028: avoid use-after-free in load_firmware_cb()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42284\n     - tipc: Return non-zero value from tipc_udp_addr2str() on error\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44998\n     - atm: idt77252: prevent use after free in dequeue_rx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42280\n     - mISDN: Fix a use after free in hfcmulti_tx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39503\n     - netns: add pre_exit method to struct pernet_operations\n     - netfilter: ipset: Fix race between namespace cleanup and gc in the list:set\n       type\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39499\n     - vmci: prevent speculation leaks by sanitizing event in event_deliver()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40988\n     - drm/radeon: fix UBSAN warning in kv_dpm.c\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40916\n     - drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40904\n     - USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39506\n     - liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42106\n     - inet_diag: Initialize pad field in struct inet_diag_req_v2\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42145\n     - IB/core: Implement a limit on UMAD receive List\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40945\n     - iommu: Return right value in iommu_sva_bind_device()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40932\n     - drm/exynos/vidi: fix memory leak in .get_modes()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41006\n     - netrom: Fix a memory leak in nr_heartbeat_expiry()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40943\n     - ocfs2: fix races between hole punching and AIO+DIO\n   * CVE-url: https://ubuntu.com/security/CVE-2024-36894\n     - usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42124\n     - scsi: qedf: Make qedf_execute_tmf() non-preemptible\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42115\n     - jffs2: Fix potential illegal address access in jffs2_free_inode\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41035\n     - USB: core: Fix duplicate endpoint bug by clearing reserved bits in the\n       descriptor\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41097\n     - usb: atm: cxacru: fix endpoint checking in cxacru_bind()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42119\n     - drm/amd/display: Skip finding free audio for unknown engine_id\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39501\n     - drivers: core: synchronize really_probe() and dev_uevent()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42105\n     - nilfs2: fix inode number range checks\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40984\n     - ACPICA: Revert \"ACPICA: avoid Info: mapping multiple BARs. Your kernel is\n       fine.\"\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40987\n     - drm/amdgpu: fix UBSAN warning in kv_dpm.c\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42097\n     - ALSA: emux: improve patch ioctl data validation\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42090\n     - pinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40942\n     - wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40981\n     - batman-adv: bypass empty buckets in batadv_purge_orig_ref()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40959\n     - xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42089\n     - ASoC: fsl-asoc-card: set priv-\u003epdev before using it\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40901\n     - scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42101\n     - drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40980\n     - drop_monitor: replace spin_lock by raw_spin_lock\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42084\n     - ftruncate: pass a signed offset\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39509\n     - HID: core: remove unnecessary WARN_ON() in implement()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42096\n     - x86: stop playing stack games in profile_pc()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38619\n     - usb-storage: alauda: Check whether the media is initialized\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42102\n     - Revert \"mm/writeback: fix possible divide-by-zero in wb_dirty_limits(),\n       again\"\n     - mm: avoid overflows in dirty throttling logic\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41044\n     - ppp: reject claimed-as-LCP but actually malformed packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40978\n     - scsi: qedi: Fix crash while reading debugfs attribute\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40941\n     - wifi: iwlwifi: mvm: don't read past the mfuart notifcation\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40905\n     - ipv6: fix possible race in __fib6_drop_pcpu_from()\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52803\n     - SUNRPC: Fix RPC client cleaned up the freed pipefs dentries\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42104\n     - nilfs2: add missing check for inode numbers on directory entries\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42148\n     - bnx2x: Fix multiple UBSAN array-index-out-of-bounds\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42094\n     - net/iucv: Avoid explicit cpumask var allocation on stack\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41046\n     - net: ethernet: lantiq_etop: fix double free in detach\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38538\n     - net: bridge: xmit: make sure we have at least eth header len bytes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26830\n     - i40e: Fix permission check for VF MAC filters\n     - i40e: Fix MAC address setting for a VF via Host/VM\n     - i40e: Do not allow untrusted VF to remove administratively set MAC\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52885\n     - SUNRPC: Fix UAF in svc_tcp_listen_data_ready()\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52629\n     - sh: push-switch: Reorder cleanup operations to avoid use-after-free bug\n   * Miscellaneous upstream changes\n     - fixup! scsi: qla2xxx: Fix double free of fcport","status":"published","published":"2026-10-21T15:07:50Z","modified":"2026-10-26T09:32:02.869172418Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1727817159","title":"Fix of 73 CVEs","description":"   [ Ubuntu: 4.15.0-237.248 ]\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26752\n     - l2tp: pass correct message length to ip6_append_data\n   * CVE-url: https://ubuntu.com/security/CVE-2021-47188\n     - scsi: ufs: core: Improve SCSI abort handling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26677\n     - rxrpc: Fix delayed ACKs to not set the reference serial number\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52527\n     - ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43882\n     - exec: Fix ToCToU between perm check and set-uid/gid usage\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48943\n     - KVM: x86/mmu: make apf token non-zero to fix bug\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38630\n     - watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44987\n     - ipv6: prevent UAF in ip6_send_skb()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42285\n     - RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48733\n     - btrfs: fix use-after-free after failure to create a snapshot\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44940\n     - fou: remove warn in gue_gro_receive on unsupported protocol\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41059\n     - hfsplus: fix uninit-value in copy_name\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46673\n     - scsi: aacraid: Fix double-free on probe failure\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42313\n     - media: venus: fix use after free in vdec_close\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44999\n     - gtp: pull network headers in gtp_dev_xmit()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42271\n     - net/iucv: fix use after free in iucv_sock_close()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44942\n     - f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43858\n     - jfs: Fix array-index-out-of-bounds in diFree\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41071\n     - wifi: mac80211: Avoid address calculations via out of bounds array indexing\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42301\n     - dev/parport: fix the array out-of-bounds risk\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46674\n     - usb: dwc3: st: fix probed platform device ref count on probe error path\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43900\n     - media: xc2028: avoid use-after-free in load_firmware_cb()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42284\n     - tipc: Return non-zero value from tipc_udp_addr2str() on error\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44998\n     - atm: idt77252: prevent use after free in dequeue_rx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42280\n     - mISDN: Fix a use after free in hfcmulti_tx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39503\n     - netns: add pre_exit method to struct pernet_operations\n     - netfilter: ipset: Fix race between namespace cleanup and gc in the list:set\n       type\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39499\n     - vmci: prevent speculation leaks by sanitizing event in event_deliver()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40988\n     - drm/radeon: fix UBSAN warning in kv_dpm.c\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40916\n     - drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40904\n     - USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39506\n     - liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42106\n     - inet_diag: Initialize pad field in struct inet_diag_req_v2\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42145\n     - IB/core: Implement a limit on UMAD receive List\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40945\n     - iommu: Return right value in iommu_sva_bind_device()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40932\n     - drm/exynos/vidi: fix memory leak in .get_modes()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41006\n     - netrom: Fix a memory leak in nr_heartbeat_expiry()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40943\n     - ocfs2: fix races between hole punching and AIO+DIO\n   * CVE-url: https://ubuntu.com/security/CVE-2024-36894\n     - usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42124\n     - scsi: qedf: Make qedf_execute_tmf() non-preemptible\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42115\n     - jffs2: Fix potential illegal address access in jffs2_free_inode\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41035\n     - USB: core: Fix duplicate endpoint bug by clearing reserved bits in the\n       descriptor\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41097\n     - usb: atm: cxacru: fix endpoint checking in cxacru_bind()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42119\n     - drm/amd/display: Skip finding free audio for unknown engine_id\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39501\n     - drivers: core: synchronize really_probe() and dev_uevent()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42105\n     - nilfs2: fix inode number range checks\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40984\n     - ACPICA: Revert \"ACPICA: avoid Info: mapping multiple BARs. Your kernel is\n       fine.\"\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40987\n     - drm/amdgpu: fix UBSAN warning in kv_dpm.c\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42097\n     - ALSA: emux: improve patch ioctl data validation\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42090\n     - pinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40942\n     - wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40981\n     - batman-adv: bypass empty buckets in batadv_purge_orig_ref()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40959\n     - xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42089\n     - ASoC: fsl-asoc-card: set priv-\u003epdev before using it\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40901\n     - scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42101\n     - drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40980\n     - drop_monitor: replace spin_lock by raw_spin_lock\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42084\n     - ftruncate: pass a signed offset\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39509\n     - HID: core: remove unnecessary WARN_ON() in implement()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42096\n     - x86: stop playing stack games in profile_pc()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38619\n     - usb-storage: alauda: Check whether the media is initialized\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42102\n     - Revert \"mm/writeback: fix possible divide-by-zero in wb_dirty_limits(),\n       again\"\n     - mm: avoid overflows in dirty throttling logic\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41044\n     - ppp: reject claimed-as-LCP but actually malformed packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40978\n     - scsi: qedi: Fix crash while reading debugfs attribute\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40941\n     - wifi: iwlwifi: mvm: don't read past the mfuart notifcation\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40905\n     - ipv6: fix possible race in __fib6_drop_pcpu_from()\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52803\n     - SUNRPC: Fix RPC client cleaned up the freed pipefs dentries\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42104\n     - nilfs2: add missing check for inode numbers on directory entries\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42148\n     - bnx2x: Fix multiple UBSAN array-index-out-of-bounds\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42094\n     - net/iucv: Avoid explicit cpumask var allocation on stack\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41046\n     - net: ethernet: lantiq_etop: fix double free in detach\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38538\n     - net: bridge: xmit: make sure we have at least eth header len bytes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26830\n     - i40e: Fix permission check for VF MAC filters\n     - i40e: Fix MAC address setting for a VF via Host/VM\n     - i40e: Do not allow untrusted VF to remove administratively set MAC\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52885\n     - SUNRPC: Fix UAF in svc_tcp_listen_data_ready()\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52629\n     - sh: push-switch: Reorder cleanup operations to avoid use-after-free bug\n   * Miscellaneous upstream changes\n     - fixup! scsi: qla2xxx: Fix double free of fcport","status":"published","published":"2026-10-21T17:05:05Z","modified":"2026-10-26T09:43:33.660181339Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CLSA-2024-1727817758","title":"Fix of 74 CVEs","description":"   * CVE-url: https://ubuntu.com/security/CVE-2024-26752\n     - l2tp: pass correct message length to ip6_append_data\n   * CVE-url: https://ubuntu.com/security/CVE-2021-47188\n     - scsi: ufs: core: Improve SCSI abort handling\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26677\n     - rxrpc: Fix delayed ACKs to not set the reference serial number\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52527\n     - ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43882\n     - exec: Fix ToCToU between perm check and set-uid/gid usage\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48943\n     - KVM: x86/mmu: make apf token non-zero to fix bug\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38630\n     - watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44987\n     - ipv6: prevent UAF in ip6_send_skb()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42285\n     - RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\n   * CVE-url: https://ubuntu.com/security/CVE-2022-48733\n     - btrfs: fix use-after-free after failure to create a snapshot\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44940\n     - fou: remove warn in gue_gro_receive on unsupported protocol\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41059\n     - hfsplus: fix uninit-value in copy_name\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46673\n     - scsi: aacraid: Fix double-free on probe failure\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42313\n     - media: venus: fix use after free in vdec_close\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44999\n     - gtp: pull network headers in gtp_dev_xmit()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42271\n     - net/iucv: fix use after free in iucv_sock_close()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44942\n     - f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43858\n     - jfs: Fix array-index-out-of-bounds in diFree\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41071\n     - wifi: mac80211: Avoid address calculations via out of bounds array indexing\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42301\n     - dev/parport: fix the array out-of-bounds risk\n   * CVE-url: https://ubuntu.com/security/CVE-2024-46674\n     - usb: dwc3: st: fix probed platform device ref count on probe error path\n   * CVE-url: https://ubuntu.com/security/CVE-2024-43900\n     - media: xc2028: avoid use-after-free in load_firmware_cb()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42284\n     - tipc: Return non-zero value from tipc_udp_addr2str() on error\n   * CVE-url: https://ubuntu.com/security/CVE-2024-44998\n     - atm: idt77252: prevent use after free in dequeue_rx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42280\n     - mISDN: Fix a use after free in hfcmulti_tx()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39503\n     - netns: add pre_exit method to struct pernet_operations\n     - netfilter: ipset: Fix race between namespace cleanup and gc in the list:set\n       type\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39499\n     - vmci: prevent speculation leaks by sanitizing event in event_deliver()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40988\n     - drm/radeon: fix UBSAN warning in kv_dpm.c\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40916\n     - drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40904\n     - USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39506\n     - liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42106\n     - inet_diag: Initialize pad field in struct inet_diag_req_v2\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42145\n     - IB/core: Implement a limit on UMAD receive List\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40945\n     - iommu: Return right value in iommu_sva_bind_device()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40932\n     - drm/exynos/vidi: fix memory leak in .get_modes()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41006\n     - netrom: Fix a memory leak in nr_heartbeat_expiry()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40943\n     - ocfs2: fix races between hole punching and AIO+DIO\n   * CVE-url: https://ubuntu.com/security/CVE-2024-36894\n     - usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42124\n     - scsi: qedf: Make qedf_execute_tmf() non-preemptible\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42115\n     - jffs2: Fix potential illegal address access in jffs2_free_inode\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41035\n     - USB: core: Fix duplicate endpoint bug by clearing reserved bits in the\n       descriptor\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41097\n     - usb: atm: cxacru: fix endpoint checking in cxacru_bind()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42119\n     - drm/amd/display: Skip finding free audio for unknown engine_id\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39501\n     - drivers: core: synchronize really_probe() and dev_uevent()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42105\n     - nilfs2: fix inode number range checks\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40984\n     - ACPICA: Revert \"ACPICA: avoid Info: mapping multiple BARs. Your kernel is\n       fine.\"\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40987\n     - drm/amdgpu: fix UBSAN warning in kv_dpm.c\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42097\n     - ALSA: emux: improve patch ioctl data validation\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42090\n     - pinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40942\n     - wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40981\n     - batman-adv: bypass empty buckets in batadv_purge_orig_ref()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40959\n     - xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42089\n     - ASoC: fsl-asoc-card: set priv-\u003epdev before using it\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40901\n     - scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42101\n     - drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40980\n     - drop_monitor: replace spin_lock by raw_spin_lock\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42084\n     - ftruncate: pass a signed offset\n   * CVE-url: https://ubuntu.com/security/CVE-2024-39509\n     - HID: core: remove unnecessary WARN_ON() in implement()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42096\n     - x86: stop playing stack games in profile_pc()\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38619\n     - usb-storage: alauda: Check whether the media is initialized\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42102\n     - Revert \"mm/writeback: fix possible divide-by-zero in wb_dirty_limits(),\n       again\"\n     - mm: avoid overflows in dirty throttling logic\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41044\n     - ppp: reject claimed-as-LCP but actually malformed packets\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40978\n     - scsi: qedi: Fix crash while reading debugfs attribute\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40941\n     - wifi: iwlwifi: mvm: don't read past the mfuart notifcation\n   * CVE-url: https://ubuntu.com/security/CVE-2024-40905\n     - ipv6: fix possible race in __fib6_drop_pcpu_from()\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52803\n     - SUNRPC: Fix RPC client cleaned up the freed pipefs dentries\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42104\n     - nilfs2: add missing check for inode numbers on directory entries\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42148\n     - bnx2x: Fix multiple UBSAN array-index-out-of-bounds\n   * CVE-url: https://ubuntu.com/security/CVE-2024-42094\n     - net/iucv: Avoid explicit cpumask var allocation on stack\n   * CVE-url: https://ubuntu.com/security/CVE-2024-41046\n     - net: ethernet: lantiq_etop: fix double free in detach\n   * CVE-url: https://ubuntu.com/security/CVE-2024-38538\n     - net: bridge: xmit: make sure we have at least eth header len bytes\n   * CVE-url: https://ubuntu.com/security/CVE-2024-26830\n     - i40e: Fix permission check for VF MAC filters\n     - i40e: Fix MAC address setting for a VF via Host/VM\n     - i40e: Do not allow untrusted VF to remove administratively set MAC\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52885\n     - SUNRPC: Fix UAF in svc_tcp_listen_data_ready()\n   * CVE-url: https://ubuntu.com/security/CVE-2023-52629\n     - sh: push-switch: Reorder cleanup operations to avoid use-after-free bug\n   * Miscellaneous upstream changes\n     - fixup! scsi: qla2xxx: Fix double free of fcport","status":"published","published":"2024-10-01T21:22:41Z","modified":"2026-06-04T10:03:36.033944592Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"id":"CVE-2024-40945","title":"iommu: Return right value in iommu_sva_bind_device()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.","status":"published","published":"2024-07-12T12:25:19.164Z","modified":"2026-10-28T02:30:58.742096016Z","updated_at":"2026-11-02T15:44:41.618074Z"},{"id":"DLA-4102-1","title":"linux-6.1 - security update","status":"published","published":"2025-03-31T00:00:00Z","modified":"2026-03-09T01:21:46.81714Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DSA-5730-1","title":"linux - security update","status":"published","published":"2024-07-15T00:00:00Z","modified":"2026-03-09T02:09:17.012851Z","updated_at":"2026-11-02T15:46:17.892347Z"},{"id":"SUSE-SU-2024:2894-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-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).\n- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).\n- CVE-2021-47186: tipc: check for null after calling kmemdup (bsc#1222702).\n- CVE-2021-47546: Kabi fix for ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).\n- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp-\u003ephy' may be out of bound (bsc#1225505).\n- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).\n- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).\n- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).\n- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).\n- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).\n- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571)\n- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len (bsc#1226555).\n- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).\n- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)\n- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).\n- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071)\n- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).\n- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).\n- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869)\n- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).\n- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).\n- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).\n- CVE-2023-52812: drm/amd: check num of link levels when update pcie param (bsc#1225564).\n- CVE-2023-52857: drm/mediatek: Fix coverity issue with unintentional integer overflow (bsc#1225581).\n- CVE-2023-52863: hwmon: (axi-fan-control) Fix possible NULL pointer dereference (bsc#1225586).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).\n- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).\n- CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647).\n- CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2 (bsc#1221656).\n- CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes (bsc#1221659).\n- CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654).\n- CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator' in (bsc#1222323)\n- CVE-2024-26663: tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() (bsc#1222326).\n- CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error (bsc#1222328).\n- CVE-2024-26802: stmmac: Clear variable when destroying workqueue (bsc#1222799).\n- CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021).\n- CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del (bsc#1223652).\n- CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple (bsc#1223806).\n- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)\n- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)\n- CVE-2024-27025: nbd: null check for nla_nest_start (bsc#1223778)\n- CVE-2024-27065: netfilter: nf_tables: do not compare internal table flags on updates (bsc#1223836).\n- CVE-2024-27402: phonet/pep: fix racy skb_queue_empty() use (bsc#1224414).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-35805: dm snapshot: fix lockup in dm_exception_table_exit (bsc#1224743).\n- CVE-2024-35819: soc: fsl: qbman: Use raw spinlock for cgr_lock (bsc#1224683).\n- CVE-2024-35837: net: mvpp2: clear BM pool before initialization (bsc#1224500).\n- CVE-2024-35853: mlxsw: spectrum_acl_tcam: Fix memory leak during rehash (bsc#1224604).\n- CVE-2024-35889: idpf: fix kernel panic on unknown packet types (bsc#1224517).\n- CVE-2024-35890: gro: fix ownership transfer (bsc#1224516).\n- CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)\n- CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)\n- CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700)\n- CVE-2024-35961: net/mlx5: Restore mistakenly dropped parts in register devlink flow (bsc#1224585).\n- CVE-2024-35979: raid1: fix use-after-free for original bio in raid1_write_request() (bsc#1224572).\n- CVE-2024-35995: ACPI: CPPC: Fix access width used for PCC registers (bsc#1224557).\n- CVE-2024-36000: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (bsc#1224548).\n- CVE-2024-36004: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue (bsc#1224545)\n- CVE-2024-36901: ipv6: prevent NULL dereference in ip6_output() (bsc#1225711)\n- CVE-2024-36902: ipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action() (bsc#1225719).\n- CVE-2024-36909: Drivers: hv: vmbus: Do not free ring buffers that couldn't be re-encrypted (bsc#1225744).\n- CVE-2024-36910: uio_hv_generic: Do not free decrypted memory (bsc#1225717).\n- CVE-2024-36911: hv_netvsc: Do not free decrypted memory (bsc#1225745).\n- CVE-2024-36912: Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl (bsc#1225752).\n- CVE-2024-36913: Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails (bsc#1225753).\n- CVE-2024-36914: drm/amd/display: Skip on writeback when it's not applicable (bsc#1225757).\n- CVE-2024-36919: scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload (bsc#1225767).\n- CVE-2024-36923: fs/9p: fix uninitialized values during inode evict (bsc#1225815).\n- CVE-2024-36939: nfs: Handle error of rpc_proc_register() in nfs_net_init() (bsc#1225838).\n- CVE-2024-36946: phonet: fix rtm_phonet_notify() skb allocation (bsc#1225851).\n- CVE-2024-36974: net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP (bsc#1226519).\n- CVE-2024-38555: net/mlx5: Discard command completions in internal error (bsc#1226607).\n- CVE-2024-38558: net: openvswitch: fix overwriting ct original tuple for ICMPv6 (bsc#1226783).\n- CVE-2024-38570: gfs2: Fix potential glock use-after-free on unmount (bsc#1226775).\n- CVE-2024-38586: r8169: Fix possible ring buffer corruption on fragmented Tx packets (bsc#1226750).\n- CVE-2024-38598: md: fix resync softlockup when bitmap size is less than array size (bsc#1226757).\n- CVE-2024-38628: usb: gadget: u_audio: Fix race condition use of controls after free during gadget unbind (bsc#1226911).\n- CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).\n- CVE-2024-39371: io_uring: check for non-NULL file pointer in io_file_can_poll() (bsc#1226990).\n- CVE-2024-39463: 9p: add missing locking around taking dentry fid list (bsc#1227090).\n- CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).\n- CVE-2024-39482: bcache: fix variable length array abuse in btree_iter (bsc#1227447).\n- CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)\n- CVE-2024-39490: ipv6: sr: fix missing sk_buff release in seg6_input_core (bsc#1227626).\n- CVE-2024-39493: crypto: qat - Fix ADF_DEV_RESET_SYNC memory leak (bsc#1227620).\n- CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).\n- CVE-2024-39497: drm/shmem-helper: Fix BUG_ON() on mmap(PROT_WRITE, MAP_PRIVATE) (bsc#1227722)\n- CVE-2024-39502: ionic: fix use after netif_napi_del() (bsc#1227755).\n- CVE-2024-39506: liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).\n- CVE-2024-39508: io_uring/io-wq: Use set_bit() and test_bit() at worker-\u003eflags (bsc#1227732).\n- CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).\n- CVE-2024-40906: net/mlx5: Always stop health timer during driver removal (bsc#1227763).\n- CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).\n- CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).\n- CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).\n- CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).\n- CVE-2024-40937: gve: Clear napi-\u003eskb before dev_kfree_skb_any() (bsc#1227836).\n- CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).\n- CVE-2024-40943: ocfs2: fix races between hole punching and AIO+DIO (bsc#1227849).\n- CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).\n- CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).\n- CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).\n- CVE-2024-40967: serial: imx: Introduce timeout when waiting on transmitter empty (bsc#1227891).\n- CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).\n- CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).\n- CVE-2024-40977: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery (bsc#1227950).\n- CVE-2024-40982: ssb: Fix potential NULL pointer dereference in ssb_device_uevent() (bsc#1227865).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40998: ext4: fix uninitialized ratelimit_state-\u003elock access in __ext4_fill_super() (bsc#1227866).\n- CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).\n- CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).\n- CVE-2024-41009: selftests/bpf: Add more ring buffer test coverage (bsc#1228020).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).\n- CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41016: ocfs2: add bounds checking to ocfs2_xattr_find_entry() (bsc#1228410).\n- CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518)\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520)\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565)\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41059: hfsplus: fix uninit-value in copy_name (bsc#1228561).\n- CVE-2024-41063: Bluetooth: hci_core: cancel all works upon hci_unregister_dev() (bsc#1228580)\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41066: ibmvnic: Add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41071: wifi: mac80211: Avoid address calculations via out of bounds array indexing (bsc#1228625).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617)\n- CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).\n- CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470)\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591)\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705)\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743)\n- CVE-2024-42161: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723)\n- CVE-2024-42230: powerpc/pseries: Fix scv instruction crash with kexec (bsc#1194869).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: Abort address space access upon error (stable-fixes).\n- ACPI: EC: Avoid returning AE_OK on errors in address space handler (stable-fixes).\n- ACPI: processor_idle: Fix invalid comparison with insertion sort for latency (git-fixes).\n- ACPI: video: Add backlight=native quirk for Lenovo Slim 7 16ARH7 (stable-fixes).\n- ACPI: x86: Force StorageD3Enable on more products (stable-fixes).\n- ACPI: x86: utils: Add Picasso to the list for forcing StorageD3Enable (stable-fixes).\n- ALSA: dmaengine_pcm: terminate dmaengine before synchronize (stable-fixes).\n- ALSA: dmaengine: Synchronize dma channel after drop() (stable-fixes).\n- ALSA: emux: improve patch ioctl data validation (stable-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: hda/realtek: Add more codec ID to no shutup pins list (stable-fixes).\n- ALSA: hda/realtek: add quirk for Clevo V5[46]0TU (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic of JP-IK LEAP W502 with ALC897 (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo SU C1400 (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP 250 G7 (stable-fixes).\n- ALSA: hda/realtek: fix mute/micmute LEDs do not work for EliteBook 645/665 G11 (stable-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book Pro 360 (stable-fixes).\n- ALSA: hda/realtek: Limit mic boost on VAIO PRO PX (stable-fixes).\n- ALSA: hda/relatek: Enable Mute LED on HP Laptop 15-gw0xxx (stable-fixes).\n- ALSA: pcm_dmaengine: Do not synchronize DMA channel when DMA is paused (git-fixes).\n- ALSA: usb-audio: Add a quirk for Sonix HD USB Camera (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Fix microphone sound on HD webcam (stable-fixes).\n- ALSA: usb-audio: Move HD Webcam quirk to the right place (git-fixes).\n- arm64: dts: allwinner: Pine H64: correctly remove reg_gmac_3v3 (git-fixes)\n- arm64: dts: hi3798cv200: fix the size of GICR (git-fixes)\n- arm64: dts: imx8qm-mek: fix gpio number for reg_usdhc2_vmmc (git-fixes)\n- arm64: dts: microchip: sparx5: fix mdio reg (git-fixes)\n- arm64: dts: rockchip: Add enable-strobe-pulldown to emmc phy on ROCK (git-fixes)\n- arm64: dts: rockchip: Add sound-dai-cells for RK3368 (git-fixes)\n- arm64: dts: rockchip: fix PMIC interrupt pin on ROCK Pi E (git-fixes)\n- arm64/io: add constant-argument check (bsc#1226502 git-fixes)\n- arm64/io: Provide a WC friendly __iowriteXX_copy() (bsc#1226502)\n- arm64: tegra: Correct Tegra132 I2C alias (git-fixes)\n- ASoC: amd: Adjust error handling in case of absent codec device (git-fixes).\n- ASoC: max98088: Check for clk_prepare_enable() error (git-fixes).\n- ASoC: ti: davinci-mcasp: Set min period size using FIFO config (stable-fixes).\n- ASoC: ti: omap-hdmi: Fix too long driver name (stable-fixes).\n- batman-adv: bypass empty buckets in batadv_purge_orig_ref() (stable-fixes).\n- blk-cgroup: dropping parent refcount after pd_free_fn() is done (bsc#1224573).\n- block: do not add partitions if GD_SUPPRESS_PART_SCAN is set (bsc#1227162).\n- block, loop: support partitions without scanning (bsc#1227162).\n- Bluetooth: ath3k: Fix multiple issues reported by checkpatch.pl (stable-fixes).\n- Bluetooth: btqca: use le32_to_cpu for ver.soc_id (stable-fixes).\n- Bluetooth: hci_core: cancel all works upon hci_unregister_dev() (stable-fixes).\n- Bluetooth: hci_qca: mark OF related data as maybe unused (stable-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot (git-fixes).\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf: aggressively forget precise markings during state checkpointing (bsc#1225903).\n- bpf: allow precision tracking for programs with subprogs (bsc#1225903).\n- bpf: check bpf_func_state-\u003ecallback_depth when pruning states (bsc#1225903).\n- bpf: clean up visit_insn()'s instruction processing (bsc#1225903).\n- bpf: correct loop detection for iterators convergence (bsc#1225903).\n- bpf: encapsulate precision backtracking bookkeeping (bsc#1225903).\n- bpf: ensure state checkpointing at iter_next() call sites (bsc#1225903).\n- bpf: exact states comparison for iterator convergence checks (bsc#1225903).\n- bpf: extract __check_reg_arg() utility function (bsc#1225903).\n- bpf: extract same_callsites() as utility function (bsc#1225903).\n- bpf: extract setup_func_entry() utility function (bsc#1225903).\n- bpf: fix calculation of subseq_idx during precision backtracking (bsc#1225903).\n- bpf: fix mark_all_scalars_precise use in mark_chain_precision (bsc#1225903).\n- bpf: Fix memory leaks in __check_func_call (bsc#1225903).\n- bpf: fix propagate_precision() logic for inner frames (bsc#1225903).\n- bpf: fix regs_exact() logic in regsafe() to remap IDs correctly (bsc#1225903).\n- bpf: Fix to preserve reg parent/live fields when copying range info (bsc#1225903).\n- bpf: generalize MAYBE_NULL vs non-MAYBE_NULL rule (bsc#1225903).\n- bpf: improve precision backtrack logging (bsc#1225903).\n- bpf: Improve verifier u32 scalar equality checking (bsc#1225903).\n- bpf: keep track of max number of bpf_loop callback iterations (bsc#1225903).\n- bpf: maintain bitmasks across all active frames in __mark_chain_precision (bsc#1225903).\n- bpf: mark relevant stack slots scratched for register read instructions (bsc#1225903).\n- bpf: move explored_state() closer to the beginning of verifier.c (bsc#1225903).\n- bpf: perform byte-by-byte comparison only when necessary in regsafe() (bsc#1225903).\n- bpf: print full verifier states on infinite loop detection (bsc#1225903).\n- bpf: regsafe() must not skip check_ids() (bsc#1225903).\n- bpf: reject non-exact register type matches in regsafe() (bsc#1225903).\n- bpf: Remove unused insn_cnt argument from visit_[func_call_]insn() (bsc#1225903).\n- bpf: reorganize struct bpf_reg_state fields (bsc#1225903).\n- bpf: Skip invalid kfunc call in backtrack_insn (bsc#1225903).\n- bpf: states_equal() must build idmap for all function frames (bsc#1225903).\n- bpf: stop setting precise in current state (bsc#1225903).\n- bpf: support precision propagation in the presence of subprogs (bsc#1225903).\n- bpf: take into account liveness when propagating precision (bsc#1225903).\n- bpf: teach refsafe() to take into account ID remapping (bsc#1225903).\n- bpf: unconditionally reset backtrack_state masks on global func exit (bsc#1225903).\n- bpf: use check_ids() for active_lock comparison (bsc#1225903).\n- bpf: Use scalar ids in mark_chain_precision() (bsc#1225903).\n- bpf: verify callbacks as if they are called unknown number of times (bsc#1225903).\n- bpf: Verify scalar ids mapping in regsafe() using check_ids() (bsc#1225903).\n- bpf: widening for callback iterators (bsc#1225903).\n- btrfs: add device major-minor info in the struct btrfs_device (bsc#1227162).\n- btrfs: harden identification of a stale device (bsc#1227162).\n- btrfs: match stale devices by dev_t (bsc#1227162).\n- btrfs: remove the cross file system checks from remap (bsc#1227157).\n- btrfs: use dev_t to match device in device_matched (bsc#1227162).\n- btrfs: validate device maj:min during open (bsc#1227162).\n- bytcr_rt5640 : inverse jack detect for Archos 101 cesium (stable-fixes).\n- cachefiles: add output string to cachefiles_obj_[get|put]_ondemand_fd (git-fixes).\n- can: kvaser_usb: Explicitly initialize family in leafimx driver_info struct (git-fixes).\n- can: kvaser_usb: fix return value for hif_usb_send_regout (stable-fixes).\n- ceph: fix incorrect kmalloc size of pagevec mempool (bsc#1228418).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- checkpatch: really skip LONG_LINE_* when LONG_LINE is ignored (git-fixes).\n- crypto: aead,cipher - zeroize key buffer after use (stable-fixes).\n- crypto: ecdh - explicitly zeroize private_key (stable-fixes).\n- crypto: ecdsa - Fix the public key format description (git-fixes).\n- crypto: hisilicon/sec - Fix memory leak for sec resource release (stable-fixes).\n- csky: ftrace: Drop duplicate implementation of arch_check_ftrace_location() (git-fixes).\n- decompress_bunzip2: fix rare decompression failure (git-fixes).\n- devres: Fix devm_krealloc() wasting memory (git-fixes).\n- devres: Fix memory leakage caused by driver API devm_free_percpu() (git-fixes).\n- dma: fix call order in dmam_free_coherent (git-fixes).\n- docs: crypto: async-tx-api: fix broken code example (git-fixes).\n- docs: Fix formatting of literal sections in fanotify docs (stable-fixes).\n- drm/amd/amdgpu: Fix style errors in amdgpu_drv.c \u0026 amdgpu_device.c (stable-fixes).\n- drm/amd/display: Account for cursor prefetch BW in DML1 mode support (stable-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Check index msg_id before read or write (stable-fixes).\n- drm/amd/display: Check pipe offset before setting vblank (stable-fixes).\n- drm/amd/display: Skip finding free audio for unknown engine_id (stable-fixes).\n- drm/amdgpu/atomfirmware: fix parsing of vram_info (stable-fixes).\n- drm/amdgpu/atomfirmware: silence UBSAN warning (stable-fixes).\n- drm/amdgpu: avoid using null object of framebuffer (stable-fixes).\n- drm/amdgpu: Check if NBIO funcs are NULL in amdgpu_device_baco_exit (git-fixes).\n- drm/amdgpu: Fix pci state save during mode-1 reset (git-fixes).\n- drm/amdgpu: Fix signedness bug in sdma_v4_0_process_trap_irq() (git-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warnings (stable-fixes).\n- drm/amdgpu: Initialize timestamp for some legacy SOCs (stable-fixes).\n- drm/amdgpu: Remove GC HW IP 9.3.0 from noretry=1 (git-fixes).\n- drm/amd/pm: Fix aldebaran pcie speed reporting (git-fixes).\n- drm/amd/pm: remove logically dead code for renoir (git-fixes).\n- drm/dp_mst: Fix all mstb marked as not probed after suspend/resume (git-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/etnaviv: fix DMA direction handling for cached RW buffers (git-fixes).\n- drm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes (git-fixes).\n- drm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes (git-fixes).\n- drm/i915/gt: Do not consider preemption during execlists_dequeue for gen8 (git-fixes).\n- drm/lima: fix shared irq handling on driver remove (stable-fixes).\n- drm/lima: Mark simple_ondemand governor as softdep (git-fixes).\n- drm/mediatek: Add OVL compatible name for MT8195 (git-fixes).\n- drm/meson: fix canvas release in bind function (git-fixes).\n- drm/mgag200: Bind I2C lifetime to DRM device (git-fixes).\n- drm/mgag200: Set DDC timeout in milliseconds (git-fixes).\n- drm/mipi-dsi: Fix mipi_dsi_dcs_write_seq() macro definition format (stable-fixes).\n- drm/mipi-dsi: Fix theoretical int overflow in mipi_dsi_dcs_write_seq() (git-fixes).\n- drm/msm/dpu: drop validity checks for clear_pending_flush() ctl op (git-fixes).\n- drm/msm/mdp5: Remove MDP_CAP_SRC_SPLIT from msm8x53_config (git-fixes).\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes (stable-fixes).\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes (stable-fixes).\n- drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes (git-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: boe-tv101wum-nl6: Check for errors on the NOP in prepare() (git-fixes).\n- drm/panel: boe-tv101wum-nl6: If prepare fails, disable GPIO before regulators (git-fixes).\n- drm/panel: ilitek-ili9881c: Fix warning with GPIO controllers that sleep (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Valve Galileo (stable-fixes).\n- drm/panfrost: Mark simple_ondemand governor as softdep (git-fixes).\n- drm/qxl: Add check for drm_cvt_mode (git-fixes).\n- drm/radeon: check bo_va-\u003ebo is non-NULL before using it (stable-fixes).\n- drm/radeon/radeon_display: Decrease the size of allocated memory (stable-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency (stable-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- eeprom: digsy_mtc: Fix 93xx46 driver probe failure (git-fixes).\n- exfat: check if cluster num is valid (git-fixes).\n- exfat: simplify is_valid_cluster() (git-fixes).\n- filelock: add a new locks_inode_context accessor function (git-fixes).\n- firmware: cs_dsp: Fix overflow checking of wmfw header (git-fixes).\n- firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers (git-fixes).\n- firmware: cs_dsp: Return error if block header overflows file (git-fixes).\n- firmware: cs_dsp: Use strnlen() on name fields in V1 wmfw files (git-fixes).\n- firmware: cs_dsp: Validate payload length before processing block (git-fixes).\n- firmware: dmi: Stop decoding on broken entry (stable-fixes).\n- firmware: turris-mox-rwtm: Do not complete if there are no waiters (git-fixes).\n- firmware: turris-mox-rwtm: Fix checking return value of wait_for_completion_timeout() (git-fixes).\n- firmware: turris-mox-rwtm: Initialize completion before mailbox (git-fixes).\n- fix build warning\n- fs: allow cross-vfsmount reflink/dedupe (bsc#1227157).\n- ftrace: Fix possible use-after-free issue in ftrace_location() (git-fixes).\n- fuse: verify {g,u}id mount options correctly (bsc#1228191).\n- gpio: mc33880: Convert comma to semicolon (git-fixes).\n- hfsplus: fix to avoid false alarm of circular locking (git-fixes).\n- hfsplus: fix uninit-value in copy_name (git-fixes).\n- HID: Add quirk for Logitech Casa touchpad (stable-fixes).\n- HID: wacom: Modify pen IDs (git-fixes).\n- hpet: Support 32-bit userspace (git-fixes).\n- hwmon: (adt7475) Fix default duty on fan is disabled (git-fixes).\n- hwmon: (max6697) Fix swapped temp{1,8} critical alarms (git-fixes).\n- hwmon: (max6697) Fix underflow when writing limit attributes (git-fixes).\n- i2c: mark HostNotify target address as used (git-fixes).\n- i2c: rcar: bring hardware to known state when probing (git-fixes).\n- i2c: tegra: Fix failure during probe deferral cleanup (git-fixes)\n- i2c: tegra: Share same DMA channel for RX and TX (bsc#1227661)\n- i2c: testunit: avoid re-issued work after read message (git-fixes).\n- i2c: testunit: correct Kconfig description (git-fixes).\n- Input: elan_i2c - do not leave interrupt disabled on suspend failure (git-fixes).\n- Input: elantech - fix touchpad state on resume for Lenovo N24 (stable-fixes).\n- Input: ff-core - prefer struct_size over open coded arithmetic (stable-fixes).\n- Input: qt1050 - handle CHIP_ID reading error (git-fixes).\n- Input: silead - Always support 10 fingers (stable-fixes).\n- intel_th: pci: Add Granite Rapids SOC support (stable-fixes).\n- intel_th: pci: Add Granite Rapids support (stable-fixes).\n- intel_th: pci: Add Lunar Lake support (stable-fixes).\n- intel_th: pci: Add Meteor Lake-S support (stable-fixes).\n- intel_th: pci: Add Sapphire Rapids SOC support (stable-fixes).\n- iommu/arm-smmu-v3: Free MSIs in case of ENOMEM (git-fixes).\n- ionic: clean interrupt before enabling queue to avoid credit race (git-fixes).\n- jffs2: Fix potential illegal address access in jffs2_free_inode (git-fixes).\n- jfs: Fix array-index-out-of-bounds in diFree (git-fixes).\n- jfs: xattr: fix buffer overflow for invalid xattr (bsc#1227383).\n- kABI: bpf: bpf_reg_state reorganization kABI workaround (bsc#1225903).\n- kABI: bpf: callback fixes kABI workaround (bsc#1225903).\n- kABI: bpf: struct bpf_{idmap,idset} kABI workaround (bsc#1225903).\n- kABI: bpf: tmp_str_buf kABI workaround (bsc#1225903).\n- kABI: rtas: Workaround false positive due to lost definition (bsc#1227487).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severities: Ignore tpm_tis_core_init (bsc#1082555).\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kabi: Use __iowriteXX_copy_inlined for in-kernel modules (bsc#1226502)\n- kernel-binary: vdso: Own module_dir\n- kernel/sched: Remove dl_boosted flag comment (git fixes (sched)).\n- knfsd: LOOKUP can return an illegal error value (git-fixes).\n- kobject_uevent: Fix OOB access within zap_modalias_env() (git-fixes).\n- kprobes: Make arch_check_ftrace_location static (git-fixes).\n- KVM: nVMX: Clear EXIT_QUALIFICATION when injecting an EPT Misconfig (git-fixes).\n- KVM: PPC: Book3S HV: Fix 'rm_exit' entry in debugfs timings (bsc#1194869).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV Nested: L2 LPCR should inherit L1 LPES setting (bsc#1194869).\n- KVM: PPC: Book3S HV: remove extraneous asterisk from rm_host_ipi_action() comment (bsc#1194869).\n- KVM: PPC: Book3S: Suppress failed alloc warning in H_COPY_TOFROM_GUEST (bsc#1194869).\n- KVM: PPC: Book3S: Suppress warnings when allocating too big memory slots (bsc#1194869).\n- KVM: s390: fix LPSWEY handling (bsc#1227635 git-fixes).\n- KVM: SVM: Process ICR on AVIC IPI delivery failure due to invalid target (git-fixes).\n- KVM: VMX: Report up-to-date exit qualification to userspace (git-fixes).\n- KVM: x86: Add IBPB_BRTYPE support (bsc#1228079).\n- KVM: x86: Always sync PIR to IRR prior to scanning I/O APIC routes (git-fixes).\n- KVM: x86: Bail from kvm_recalculate_phys_map() if x2APIC ID is out-of-bounds (git-fixes).\n- KVM: x86: Disable APIC logical map if logical ID covers multiple MDAs (git-fixes).\n- KVM: x86: Disable APIC logical map if vCPUs are aliased in logical mode (git-fixes).\n- KVM: x86: Do not advertise guest.MAXPHYADDR as host.MAXPHYADDR in CPUID (git-fixes).\n- KVM: x86: Explicitly skip optimized logical map setup if vCPU's LDR==0 (git-fixes).\n- KVM: x86: Explicitly track all possibilities for APIC map's logical modes (git-fixes).\n- KVM: x86: Fix broken debugregs ABI for 32 bit kernels (git-fixes).\n- KVM: x86: Fix KVM_GET_MSRS stack info leak (git-fixes).\n- KVM: x86: Honor architectural behavior for aliased 8-bit APIC IDs (git-fixes).\n- KVM: x86: Purge 'highest ISR' cache when updating APICv state (git-fixes).\n- KVM: x86: Save/restore all NMIs when multiple NMIs are pending (git-fixes).\n- KVM: x86: Skip redundant x2APIC logical mode optimized cluster setup (git-fixes).\n- leds: ss4200: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- leds: triggers: Flush pending brightness before activating trigger (git-fixes).\n- leds: trigger: Unregister sysfs attributes before calling deactivate() (git-fixes).\n- libceph: fix race between delayed_work() and ceph_monc_stop() (bsc#1228190).\n- lib: objagg: Fix general protection fault (git-fixes).\n- lib: objagg: Fix spelling (git-fixes).\n- lib: test_objagg: Fix spelling (git-fixes).\n- lockd: set missing fl_flags field when retrieving args (git-fixes).\n- lockd: use locks_inode_context helper (git-fixes).\n- Make AMD_HSMP=m and mark it unsupported in supported.conf (jsc#PED-8582)\n- media: dvb: as102-fe: Fix as10x_register_addr packing (stable-fixes).\n- media: dvbdev: Initialize sbuf (stable-fixes).\n- media: dvb-frontends: tda10048: Fix integer overflow (stable-fixes).\n- media: dvb-frontends: tda18271c2dd: Remove casting during div (stable-fixes).\n- media: dvb-usb: dib0700_devices: Add missing release_firmware() (stable-fixes).\n- media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control() (git-fixes).\n- media: dw2102: Do not translate i2c read into write (stable-fixes).\n- media: dw2102: fix a potential buffer overflow (git-fixes).\n- media: imon: Fix race getting ictx-\u003elock (git-fixes).\n- media: s2255: Use refcount_t instead of atomic_t for num_channels (stable-fixes).\n- media: uvcvideo: Fix integer overflow calculating timestamp (git-fixes).\n- media: uvcvideo: Override default flags (git-fixes).\n- media: venus: fix use after free in vdec_close (git-fixes).\n- media: venus: flush all buffers in output plane streamoff (git-fixes).\n- mei: demote client disconnect warning on suspend to debug (stable-fixes).\n- mfd: omap-usb-tll: Use struct_size to allocate tll (git-fixes).\n- mtd: partitions: redboot: Added conversion of operands to a larger type (stable-fixes).\n- net/dcb: check for detached device before executing callbacks (bsc#1215587).\n- netfilter: conntrack: ignore overly delayed tcp packets (bsc#1223180).\n- netfilter: conntrack: prepare tcp_in_window for ternary return value (bsc#1223180).\n- netfilter: conntrack: remove pr_debug callsites from tcp tracker (bsc#1223180).\n- netfilter: conntrack: work around exceeded receive window (bsc#1223180).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- net: mana: Fix possible double free in error handling path (git-fixes).\n- net: mana: Fix the extra HZ in mana_hwc_send_request (git-fixes).\n- net: usb: qmi_wwan: add Telit FN912 compositions (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- nfc/nci: Add the inconsistency check between the input data length and count (stable-fixes).\n- NFSD: Add an nfsd_file_fsync tracepoint (git-fixes).\n- NFSD: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection (git-fixes).\n- nfsd: Add errno mapping for EREMOTEIO (git-fixes).\n- NFSD: Add nfsd_file_lru_dispose_list() helper (git-fixes).\n- nfsd: add some comments to nfsd_file_do_acquire (git-fixes).\n- nfsd: allow nfsd_file_get to sanely handle a NULL pointer (git-fixes).\n- nfsd: allow reaping files still under writeback (git-fixes).\n- NFSD: Avoid calling fh_drop_write() twice in do_nfsd_create() (git-fixes).\n- NFSD: Clean up nfsd3_proc_create() (git-fixes).\n- nfsd: Clean up nfsd_file_put() (git-fixes).\n- NFSD: Clean up nfsd_open_verified() (git-fixes).\n- NFSD: Clean up unused code after rhashtable conversion (git-fixes).\n- NFSD: Convert filecache to rhltable (git-fixes).\n- NFSD: Convert the filecache to use rhashtable (git-fixes).\n- NFSD: De-duplicate hash bucket indexing (git-fixes).\n- nfsd: do not free files unconditionally in __nfsd_file_cache_purge (git-fixes).\n- nfsd: do not fsync nfsd_files on last close (git-fixes).\n- nfsd: do not hand out delegation on setuid files being opened for write (git-fixes).\n- nfsd: do not kill nfsd_files because of lease break error (git-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nfsd: do not take/put an extra reference when putting a file (git-fixes).\n- NFSD enforce filehandle check for source file in COPY (git-fixes).\n- NFSD: Ensure nf_inode is never dereferenced (git-fixes).\n- nfsd: fix handling of cached open files in nfsd4_open codepath (git-fixes).\n- NFSD: Fix licensing header in filecache.c (git-fixes).\n- nfsd: fix net-namespace logic in __nfsd_file_cache_purge (git-fixes).\n- nfsd: fix nfsd_file_unhash_and_dispose (git-fixes).\n- NFSD: Fix potential use-after-free in nfsd_file_put() (git-fixes).\n- NFSD: Fix problem of COMMIT and NFS4ERR_DELAY in infinite loop (git-fixes).\n- NFSD: Fix the filecache LRU shrinker (git-fixes).\n- nfsd: fix up the filecache laundrette scheduling (git-fixes).\n- nfsd: fix use-after-free in nfsd_file_do_acquire tracepoint (git-fixes).\n- NFSD: Flesh out a documenting comment for filecache.c (git-fixes).\n- NFSD: handle errors better in write_ports_addfd() (git-fixes).\n- NFSD: Instantiate a struct file when creating a regular NFSv4 file (git-fixes).\n- NFSD: Leave open files out of the filecache LRU (git-fixes).\n- nfsd: map EBADF (git-fixes).\n- NFSD: Move nfsd_file_trace_alloc() tracepoint (git-fixes).\n- NFSD: nfsd_file_hash_remove can compute hashval (git-fixes).\n- nfsd: NFSD_FILE_KEY_INODE only needs to find GC'ed entries (git-fixes).\n- NFSD: nfsd_file_put() can sleep (git-fixes).\n- NFSD: nfsd_file_unhash can compute hashval from nf-\u003enf_inode (git-fixes).\n- NFSD: No longer record nf_hashval in the trace log (git-fixes).\n- NFSD: Pass the target nfsd_file to nfsd_commit() (git-fixes).\n- nfsd: put the export reference in nfsd4_verify_deleg_dentry (git-fixes).\n- NFSD: Record number of flush calls (git-fixes).\n- NFSD: Refactor nfsd_create_setattr() (git-fixes).\n- NFSD: Refactor __nfsd_file_close_inode() (git-fixes).\n- NFSD: Refactor nfsd_file_gc() (git-fixes).\n- NFSD: Refactor nfsd_file_lru_scan() (git-fixes).\n- NFSD: Refactor NFSv3 CREATE (git-fixes).\n- NFSD: Refactor NFSv4 OPEN(CREATE) (git-fixes).\n- NFSD: Remove do_nfsd_create() (git-fixes).\n- NFSD: Remove lockdep assertion from unhash_and_release_locked() (git-fixes).\n- NFSD: Remove nfsd_file::nf_hashval (git-fixes).\n- nfsd: remove the pages_flushed statistic from filecache (git-fixes).\n- nfsd: reorganize filecache.c (git-fixes).\n- NFSD: Replace the 'init once' mechanism (git-fixes).\n- NFSD: Report average age of filecache items (git-fixes).\n- NFSD: Report count of calls to nfsd_file_acquire() (git-fixes).\n- NFSD: Report count of freed filecache items (git-fixes).\n- NFSD: Report filecache LRU size (git-fixes).\n- NFSD: Report the number of items evicted by the LRU walk (git-fixes).\n- nfsd: Retry once in nfsd_open on an -EOPENSTALE return (git-fixes).\n- nfsd: rework hashtable handling in nfsd_do_file_acquire (git-fixes).\n- nfsd: rework refcounting in filecache (git-fixes).\n- NFSD: Separate tracepoints for acquire and create (git-fixes).\n- NFSD: Set up an rhashtable for the filecache (git-fixes).\n- nfsd: silence extraneous printk on nfsd.ko insertion (git-fixes).\n- NFSD: simplify per-net file cache management (git-fixes).\n- nfsd: simplify test_bit return in NFSD_FILE_KEY_FULL comparator (git-fixes).\n- nfsd: simplify the delayed disposal list code (git-fixes).\n- NFSD: Trace filecache LRU activity (git-fixes).\n- NFSD: Trace filecache opens (git-fixes).\n- NFSD: verify the opened dentry after setting a delegation (git-fixes).\n- NFSD: WARN when freeing an item still linked via nf_lru (git-fixes).\n- NFSD: Write verifier might go backwards (git-fixes).\n- NFSD: Zero counters when the filecache is re-initialized (git-fixes).\n- NFS: Fix READ_PLUS when server does not support OP_READ_PLUS (git-fixes).\n- nfs: fix undefined behavior in nfs_block_bits() (git-fixes).\n- nfs: keep server info for remounts (git-fixes).\n- nfs: Leave pages in the pagecache if readpage failed (git-fixes).\n- NFSv4: Fixup smatch warning for ambiguous return (git-fixes).\n- NFSv4.x: by default serialize open/close operations (bsc#1223863 bsc#1227362)\n- nilfs2: add missing check for inode numbers on directory entries (git-fixes).\n- nilfs2: add missing check for inode numbers on directory entries (stable-fixes).\n- nilfs2: avoid undefined behavior in nilfs_cnt32_ge macro (git-fixes).\n- nilfs2: convert persistent object allocator to use kmap_local (git-fixes).\n- nilfs2: fix incorrect inode allocation from reserved inodes (git-fixes).\n- nilfs2: fix inode number range checks (git-fixes).\n- nilfs2: fix inode number range checks (stable-fixes).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme-auth: alloc nvme_dhchap_key as single buffer (git-fixes).\n- nvme-auth: allow mixing of secret and hash lengths (git-fixes).\n- nvme-auth: use transformed key size to create resp (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvme: use ctrl state accessor (bsc#1215492).\n- ocfs2: fix DIO failure due to insufficient transaction credits (bsc#1216834).\n- ocfs2: remove redundant assignment to variable free_space (bsc#1228409).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- orangefs: fix out-of-bounds fsid access (git-fixes).\n- PCI: Add PCI_ERROR_RESPONSE and related definitions (stable-fixes).\n- PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal (git-fixes).\n- PCI: Extend ACS configurability (bsc#1228090).\n- PCI: Fix resource double counting on remove \u0026 rescan (git-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: Introduce cleanup helpers for device reference counts and locks (git-fixes).\n- PCI: Introduce cleanup helpers for device reference counts and locks (stable-fixes).\n- PCI: keystone: Do not enable BAR 0 for AM654x (git-fixes).\n- PCI: keystone: Fix NULL pointer dereference in case of DT error in ks_pcie_setup_rc_app_regs() (git-fixes).\n- PCI: keystone: Relocate ks_pcie_set/clear_dbi_mode() (git-fixes).\n- PCI/PM: Avoid D3cold for HP Pavilion 17 PC/1972 PCIe Ports (git-fixes).\n- PCI/PM: Avoid D3cold for HP Pavilion 17 PC/1972 PCIe Ports (stable-fixes).\n- PCI: rockchip: Use GPIOD_OUT_LOW flag while requesting ep_gpio (git-fixes).\n- PCI: tegra194: Set EP alignment restriction for inbound ATU (git-fixes).\n- pinctrl: core: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- pinctrl: freescale: mxs: Fix refcount of child (git-fixes).\n- pinctrl: single: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- pinctrl: ti: ti-iodelay: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- platform/chrome: cros_ec_debugfs: fix wrong EC message version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86: dell-smbios-base: Use sysfs_emit() (stable-fixes).\n- platform/x86: dell-smbios: Fix wrong token data in sysfs (git-fixes).\n- platform/x86: lg-laptop: Change ACPI device id (stable-fixes).\n- platform/x86: lg-laptop: Remove LGEX0815 hotkey handling (stable-fixes).\n- platform/x86: touchscreen_dmi: Add info for GlobalSpace SolT IVW 11.6' tablet (stable-fixes).\n- platform/x86: touchscreen_dmi: Add info for the EZpad 6s Pro (stable-fixes).\n- platform/x86: wireless-hotkey: Add support for LG Airplane Button (stable-fixes).\n- powerpc/cpuidle: Set CPUIDLE_FLAG_POLLING for snooze state (bsc#1227121 ltc#207129).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc/kasan: Disable address sanitization in kexec paths (bsc#1194869).\n- powerpc/pseries: Fix scv instruction crash with kexec (bsc#1194869).\n- powerpc/rtas: clean up includes (bsc#1227487).\n- powerpc/rtas: Prevent Spectre v1 gadget construction in sys_rtas() (bsc#1227487).\n- power: supply: cros_usbpd: provide ID table for avoiding fallback match (stable-fixes).\n- pwm: stm32: Always do lazy disabling (git-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Ignore optional access flags for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/restrack: Fix potential invalid address access (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- regmap-i2c: Subtract reg size from max_write (stable-fixes).\n- Revert 'ALSA: firewire-lib: obsolete workqueue for period update' (bsc#1208783).\n- Revert 'ALSA: firewire-lib: operate for period elapse event in process context' (bsc#1208783).\n- Revert 'leds: led-core: Fix refcount leak in of_led_get()' (git-fixes).\n- Revert 'usb: musb: da8xx: Set phy in OTG mode by default' (stable-fixes).\n- rpcrdma: fix handling for RDMA_CM_EVENT_DEVICE_REMOVAL (git-fixes).\n- rpm/guards: fix precedence issue with control flow operator With perl 5.40 it report the following error on rpm/guards script: Possible precedence issue with control flow operator (exit) at scripts/guards line 208. Fix the issue by adding parenthesis around ternary operator.\n- rtc: cmos: Fix return value of nvmem callbacks (git-fixes).\n- rtc: interface: Add RTC offset to alarm after fix-up (git-fixes).\n- rtc: isl1208: Fix return value of nvmem callbacks (git-fixes).\n- rtlwifi: rtl8192de: Style clean-ups (stable-fixes).\n- s390: Implement __iowrite32_copy() (bsc#1226502)\n- s390: Stop using weak symbols for __iowrite64_copy() (bsc#1226502)\n- saa7134: Unchecked i2c_transfer function result fixed (git-fixes).\n- sched/fair: Do not balance task to its current running CPU (git fixes (sched)).\n- sched: Fix stop_one_cpu_nowait() vs hotplug (git fixes (sched)).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftests/bpf: Add a selftest for checking subreg equality (bsc#1225903).\n- selftests/bpf: add pre bpf_prog_test_run_opts() callback for test_loader (bsc#1225903).\n- selftests/bpf: add precision propagation tests in the presence of subprogs (bsc#1225903).\n- selftests/bpf: Add pruning test case for bpf_spin_lock (bsc#1225903).\n- selftests/bpf: Check if mark_chain_precision() follows scalar ids (bsc#1225903).\n- selftests/bpf: check if max number of bpf_loop iterations is tracked (bsc#1225903).\n- selftests/bpf: fix __retval() being always ignored (bsc#1225903).\n- selftests/bpf: fix unpriv_disabled check in test_verifier (bsc#1225903).\n- selftests/bpf: __imm_insn \u0026 __imm_const macro for bpf_misc.h (bsc#1225903).\n- selftests/bpf: make test_align selftest more robust (bsc#1225903).\n- selftests/bpf: populate map_array_ro map for verifier_array_access test (bsc#1225903).\n- selftests/bpf: prog_tests entry point for migrated test_verifier tests (bsc#1225903).\n- selftests/bpf: Report program name on parse_test_spec error (bsc#1225903).\n- selftests/bpf: Support custom per-test flags and multiple expected messages (bsc#1225903).\n- selftests/bpf: test case for callback_depth states pruning logic (bsc#1225903).\n- selftests/bpf: test case for relaxed prunning of active_lock.id (bsc#1225903).\n- selftests/bpf: test cases for regsafe() bug skipping check_id() (bsc#1225903).\n- selftests/bpf: Tests execution support for test_loader.c (bsc#1225903).\n- selftests/bpf: tests for iterating callbacks (bsc#1225903).\n- selftests/bpf: test widening for iterating callbacks (bsc#1225903).\n- selftests/bpf: track string payload offset as scalar in strobemeta (bsc#1225903).\n- selftests/bpf: Unprivileged tests for test_loader.c (bsc#1225903).\n- selftests/bpf: Verify copy_register_state() preserves parent/live fields (bsc#1225903).\n- selftests/bpf: verify states_equal() maintains idmap across all frames (bsc#1225903).\n- selftests/bpf: Verify that check_ids() is used for scalars in regsafe() (bsc#1225903).\n- selftests/sigaltstack: Fix ppc64 GCC build (git-fixes).\n- soc: ti: wkup_m3_ipc: Send NULL dummy message instead of pointer message (stable-fixes).\n- spi: imx: Do not expect DMA for i.MX{25,35,50,51,53} cspi devices (stable-fixes).\n- spi: mux: set ctlr-\u003ebits_per_word_mask (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228850).\n- SUNRPC: avoid soft lockup when transmitting UDP to reachable server (bsc#1225272).\n- SUNRPC: Fix gss_free_in_token_pages() (git-fixes).\n- SUNRPC: Fix loop termination condition in gss_free_in_token_pages() (git-fixes).\n- sunrpc: fix NFSACL RPC retry on soft mount (git-fixes).\n- SUNRPC: return proper error from gss_wrap_req_priv (git-fixes).\n- supported.conf:\n- tpm: Allow system suspend to continue when TPM suspend fails (bsc#1082555).\n- tpm: Prevent hwrng from activating during resume (bsc#1082555).\n- tpm_tis: Resend command to recover from data transfer errors (bsc#1082555).\n- tpm_tis: Use tpm_chip_{start,stop} decoration inside tpm_tis_resume (bsc#1082555).\n- tpm, tpm: Implement usage counter for locality (bsc#1082555).\n- tpm, tpm_tis: Avoid cache incoherency in test for interrupts (bsc#1082555).\n- tpm, tpm_tis: Claim locality before writing interrupt registers (bsc#1082555).\n- tpm, tpm_tis: Claim locality in interrupt handler (bsc#1082555).\n- tpm, tpm_tis: Claim locality when interrupts are reenabled on resume (bsc#1082555).\n- tpm, tpm_tis: correct tpm_tis_flags enumeration values (bsc#1082555).\n- tpm, tpm_tis: Do not skip reset of original interrupt vector (bsc#1082555).\n- tpm, tpm_tis: Only handle supported interrupts (bsc#1082555).\n- tracing: Build event generation tests only as modules (git-fixes).\n- tracing/net_sched: NULL pointer dereference in perf_trace_qdisc_reset() (git-fixes).\n- tracing/osnoise: Add osnoise/options file (bsc#1228330)\n- tracing/osnoise: Add OSNOISE_WORKLOAD option (bsc#1228330)\n- tracing/osnoise: Do not follow tracing_cpumask (bsc#1228330)\n- tracing/osnoise: Fix notify new tracing_max_latency (bsc#1228330)\n- tracing/osnoise: Make osnoise_instances static (bsc#1228330)\n- tracing/osnoise: Split workload start from the tracer start (bsc#1228330)\n- tracing/osnoise: Support a list of trace_array *tr (bsc#1228330)\n- tracing/osnoise: Use built-in RCU list checking (bsc#1228330)\n- tracing/timerlat: Notify new max thread latency (bsc#1228330)\n- USB: Add USB_QUIRK_NO_SET_INTF quirk for START BP-850k (stable-fixes).\n- usb: cdns3: allocate TX FIFO size according to composite EP number (git-fixes).\n- usb: cdns3: fix incorrect calculation of ep_buf_size when more than one config (git-fixes).\n- usb: cdns3: fix iso transfer error when mult is not zero (git-fixes).\n- usb: cdns3: improve handling of unaligned address case (git-fixes).\n- usb: cdns3: optimize OUT transfer by copying only actual received data (git-fixes).\n- usb: cdns3: skip set TRB_IOC when usb_request: no_interrupt is true (git-fixes).\n- USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor (git-fixes).\n- usb: dwc3: gadget: Do not delay End Transfer on delayed_status (git-fixes).\n- usb: dwc3: gadget: Force sending delayed status during soft disconnect (git-fixes).\n- usb: dwc3: gadget: Synchronize IRQ between soft connect/disconnect (git-fixes).\n- usb: gadget: call usb_gadget_check_config() to verify UDC capability (git-fixes).\n- usb: gadget: configfs: Prevent OOB read/write in usb_string_copy() (stable-fixes).\n- usb: gadget: printer: SS+ support (stable-fixes).\n- usb: misc: uss720: check for incompatible versions of the Belkin F5U002 (stable-fixes).\n- USB: serial: mos7840: fix crash on resume (git-fixes).\n- USB: serial: option: add Fibocom FM350-GL (stable-fixes).\n- USB: serial: option: add Netprisma LCUK54 series modules (stable-fixes).\n- USB: serial: option: add Rolling RW350-GL variants (stable-fixes).\n- USB: serial: option: add support for Foxconn T99W651 (stable-fixes).\n- USB: serial: option: add Telit FN912 rmnet compositions (stable-fixes).\n- USB: serial: option: add Telit generic core-dump composition (stable-fixes).\n- usb: typec: tcpm: clear pd_event queue in PORT_RESET (git-fixes).\n- usb: xhci-plat: Do not include xhci.h (git-fixes).\n- USB: xhci-plat: fix legacy PHY double init (git-fixes).\n- wifi: ath11k: fix wrong handling of CCMP256 and GCMP ciphers (git-fixes).\n- wifi: brcmsmac: LCN PHY code is used for BCM4313 2G-only device (git-fixes).\n- wifi: cfg80211: fix typo in cfg80211_calculate_bitrate_he() (git-fixes).\n- wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he() (git-fixes).\n- wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values (git-fixes).\n- wifi: cfg80211: wext: add extra SIOCSIWSCAN data check (stable-fixes).\n- wifi: iwlwifi: mvm: d3: fix WoWLAN command version lookup (stable-fixes).\n- wifi: iwlwifi: mvm: Handle BIGTK cipher in kek_kck cmd (stable-fixes).\n- wifi: iwlwifi: mvm: properly set 6 GHz channel direct probe option (stable-fixes).\n- wifi: mac80211: disable softirqs for queued frame handling (git-fixes).\n- wifi: mac80211: fix UBSAN noise in ieee80211_prep_hw_scan() (stable-fixes).\n- wifi: mac80211: handle tasklet frames before stopping (stable-fixes).\n- wifi: mac80211: mesh: init nonpeer_pm to active by default in mesh sdata (stable-fixes).\n- wifi: mt76: replace skb_put with skb_put_zero (stable-fixes).\n- wifi: mwifiex: Fix interface type change (git-fixes).\n- wifi: rtw89: Fix array index mistake in rtw89_sta_info_get_iter() (git-fixes).\n- wifi: wilc1000: fix ies_len type in connect path (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/amd_nb: Use Family 19h Models 60h-7Fh Function 4 IDs (git-fixes).\n- x86/apic: Force native_apic_mem_read() to use the MOV instruction (git-fixes).\n- x86/bhi: Avoid warning in #DB handler due to BHI mitigation (git-fixes).\n- x86/bugs: Remove default case for fully switched enums (bsc#1227900).\n- x86/fpu: Fix AMD X86_BUG_FXSAVE_LEAK fixup (git-fixes).\n- x86/ibt,ftrace: Search for __fentry__ location (git-fixes).\n- x86/Kconfig: Transmeta Crusoe is CPU family 5, not 6 (git-fixes).\n- x86/mm: Allow guest.enc_status_change_prepare() to fail (git-fixes).\n- x86/mm: Fix enc_status_change_finish_noop() (git-fixes).\n- x86/purgatory: Switch to the position-independent small code model (git-fixes).\n- x86/srso: Move retbleed IBPB check into existing 'has_microcode' code block (bsc#1227900).\n- x86/srso: Remove 'pred_cmd' label (bsc#1227900).\n- x86: Stop using weak symbols for __iowrite32_copy() (bsc#1226502)\n- x86/tdx: Fix race between set_memory_encrypted() and load_unaligned_zeropad() (git-fixes).\n- xfs: Add cond_resched to block unmap range and reflink remap path (bsc#1228226).\n- xhci: Apply broken streams quirk to Etron EJ188 xHCI host (stable-fixes).\n- xhci: Apply reset resume quirk to Etron EJ188 xHCI host (stable-fixes).\n- xhci: Set correct transferred length for cancelled bulk transfers (stable-fixes).\n","status":"published","published":"2024-08-13T14:07:49Z","modified":"2025-05-02T04:32:07.924249Z","updated_at":"2026-11-02T15:53:55.136363Z"},{"id":"SUSE-SU-2024:2939-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).\n- CVE-2021-47089: kfence: fix memory leak when cat kfence objects (bsc#1220958).\n- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).\n- CVE-2021-47186: tipc: check for null after calling kmemdup (bsc#1222702).\n- CVE-2021-47432: lib/generic-radix-tree.c: Do not overflow in peek() (bsc#1225391).\n- CVE-2021-47515: seg6: fix the iif in the IPv6 socket control block (bsc#1225426).\n- CVE-2021-47538: rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() (bsc#1225448).\n- CVE-2021-47539: rxrpc: Fix rxrpc_peer leak in rxrpc_look_up_bundle() (bsc#1225452).\n- CVE-2021-47546: ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).\n- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp-\u003ephy' may be out of bound (bsc#1225505).\n- CVE-2021-47555: net: vlan: fix underflow for the real_dev refcnt (bsc#1225467).\n- CVE-2021-47566: Fix clearing user buffer by properly using clear_user() (bsc#1225514).\n- CVE-2021-47571: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() (bsc#1225518).\n- CVE-2021-47572: net: nexthop: fix null pointer dereference when IPv6 is not enabled (bsc#1225389).\n- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).\n- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).\n- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).\n- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).\n- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).\n- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571).\n- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len. (bsc#1226555).\n- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).\n- CVE-2022-48716: ASoC: codecs: wcd938x: fix incorrect used of portid (bsc#1226678).\n- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)\n- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).\n- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071).\n- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).\n- CVE-2023-24023: Bluetooth: Add more enc key size check (bsc#1218148).\n- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).\n- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869).\n- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).\n- CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg (bsc#1222080).\n- CVE-2023-52658: Revert 'net/mlx5: Block entering switchdev mode with ns inconsistency' (bsc#1224719).\n- CVE-2023-52667: net/mlx5e: fix a potential double-free in fs_any_create_groups (bsc#1224603).\n- CVE-2023-52670: rpmsg: virtio: Free driver_override when rpmsg_remove() (bsc#1224696).\n- CVE-2023-52672: pipe: wakeup wr_wait after setting max_usage (bsc#1224614).\n- CVE-2023-52675: powerpc/imc-pmu: Add a null pointer check in update_events_in_group() (bsc#1224504).\n- CVE-2023-52735: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself (bsc#1225475).\n- CVE-2023-52737: btrfs: lock the inode in shared mode before starting fiemap (bsc#1225484).\n- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52762: virtio-blk: fix implicit overflow on virtio_max_dma_size (bsc#1225573).\n- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).\n- CVE-2023-52784: bonding: stop the device in bond_setup_by_slave() (bsc#1224946).\n- CVE-2023-52787: blk-mq: make sure active queue usage is held for bio_integrity_prep() (bsc#1225105).\n- CVE-2023-52812: drm/amd: check num of link levels when update pcie param (bsc#1225564).\n- CVE-2023-52835: perf/core: Bail out early if the request AUX area is out of bound (bsc#1225602).\n- CVE-2023-52837: nbd: fix uaf in nbd_open (bsc#1224935).\n- CVE-2023-52843: llc: verify mac len before reading mac header (bsc#1224951).\n- CVE-2023-52845: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (bsc#1225585).\n- CVE-2023-52846: hsr: Prevent use after free in prp_create_tagged_frame() (bsc#1225098).\n- CVE-2023-52857: drm/mediatek: Fix coverity issue with unintentional integer overflow (bsc#1225581).\n- CVE-2023-52863: hwmon: (axi-fan-control) Fix possible NULL pointer dereference (bsc#1225586).\n- CVE-2023-52869: pstore/platform: Add check for kstrdup (bsc#1225050).\n- CVE-2023-52881: tcp: do not accept ACK of bytes we never sent (bsc#1225611).\n- CVE-2023-52882: clk: sunxi-ng: h6: Reparent CPUX during PLL CPUX rate change (bsc#1225692).\n- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).\n- CVE-2024-26625: Call sock_orphan() at release time (bsc#1221086)\n- CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647).\n- CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2 (bsc#1221656).\n- CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes (bsc#1221659).\n- CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654).\n- CVE-2024-26644: btrfs: do not abort filesystem when attempting to snapshot deleted subvolume (bsc#1221282, bsc#1222072).\n- CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator' in 'dcn21_set_pipe()' (bsc#1222323).\n- CVE-2024-26663: tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() (bsc#1222326).\n- CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error (bsc#1222328).\n- CVE-2024-26720: mm: Avoid overflows in dirty throttling logic (bsc#1222364).\n- CVE-2024-26802: stmmac: Clear variable when destroying workqueue (bsc#1222799).\n- CVE-2024-26813: vfio/platform: Create persistent IRQ handlers (bsc#1222809).\n- CVE-2024-26814: vfio/fsl-mc: Block calling interrupt handler without trigger (bsc#1222810).\n- CVE-2024-26842: scsi: target: core: Add TMF to tmr_list handling (bsc#1223013).\n- CVE-2024-26845: scsi: target: core: Add TMF to tmr_list handling (bsc#1223018).\n- CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021).\n- CVE-2024-26923: Fixed false-positive lockdep splat for spin_lock() in __unix_gc() (bsc#1223384).\n- CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del (bsc#1223652).\n- CVE-2024-26973: fat: fix uninitialized field in nostale filehandles (bsc#1223641).\n- CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple (bsc#1223806).\n- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)\n- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)\n- CVE-2024-27025: nbd: null check for nla_nest_start (bsc#1223778)\n- CVE-2024-27065: netfilter: nf_tables: do not compare internal table flags on updates (bsc#1223836).\n- CVE-2024-27402: phonet/pep: fix racy skb_queue_empty() use (bsc#1224414).\n- CVE-2024-27432: net: ethernet: mtk_eth_soc: fix PPE hanging issue (bsc#1224716).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-35247: fpga: region: add owner module and take its refcount (bsc#1226948).\n- CVE-2024-35789: Check fast rx for non-4addr sta VLAN changes (bsc#1224749).\n- CVE-2024-35790: usb: typec: altmodes/displayport: create sysfs nodes as driver's default device attribute group (bsc#1224712).\n- CVE-2024-35805: dm snapshot: fix lockup in dm_exception_table_exit (bsc#1224743).\n- CVE-2024-35807: ext4: fix corruption during on-line resize (bsc#1224735).\n- CVE-2024-35819: soc: fsl: qbman: Use raw spinlock for cgr_lock (bsc#1224683).\n- CVE-2024-35835: net/mlx5e: fix a double-free in arfs_create_groups (bsc#1224605).\n- CVE-2024-35837: net: mvpp2: clear BM pool before initialization (bsc#1224500).\n- CVE-2024-35848: eeprom: at24: fix memory corruption race condition (bsc#1224612).\n- CVE-2024-35853: mlxsw: spectrum_acl_tcam: Fix memory leak during rehash (bsc#1224604).\n- CVE-2024-35857: icmp: prevent possible NULL dereferences from icmp_build_probe() (bsc#1224619).\n- CVE-2024-35861: Fixed potential UAF in cifs_signal_cifsd_for_reconnect() (bsc#1224766).\n- CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted() (bsc#1224764).\n- CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break() (bsc#1224765).\n- CVE-2024-35869: smb: client: guarantee refcounted children from parent session (bsc#1224679).\n- CVE-2024-35884: udp: do not accept non-tunnel GSO skbs landing in a tunnel (bsc#1224520).\n- CVE-2024-35886: ipv6: Fix infinite recursion in fib6_dump_done() (bsc#1224670).\n- CVE-2024-35889: idpf: fix kernel panic on unknown packet types (bsc#1224517).\n- CVE-2024-35890: gro: fix ownership transfer (bsc#1224516).\n- CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)\n- CVE-2024-35898: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() (bsc#1224498).\n- CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)\n- CVE-2024-35900: netfilter: nf_tables: reject new basechain after table flag update (bsc#1224497).\n- CVE-2024-35925: block: prevent division by zero in blk_rq_stat_sum() (bsc#1224661).\n- CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-35950: drm/client: Fully protect modes with dev-\u003emode_config.mutex (bsc#1224703).\n- CVE-2024-35956: Fixed qgroup prealloc rsv leak in subvolume operations (bsc#1224674)\n- CVE-2024-35958: net: ena: Fix incorrect descriptor free behavior (bsc#1224677).\n- CVE-2024-35960: net/mlx5: Properly link new fs rules into the tree (bsc#1224588).\n- CVE-2024-35961: net/mlx5: Register devlink first under devlink lock (bsc#1224585).\n- CVE-2024-35979: raid1: fix use-after-free for original bio in raid1_write_request() (bsc#1224572).\n- CVE-2024-35995: ACPI: CPPC: Use access_width over bit_width for system memory accesses (bsc#1224557).\n- CVE-2024-35997: Remove I2C_HID_READ_PENDING flag to prevent lock-up (bsc#1224552).\n- CVE-2024-36000: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (bsc#1224548).\n- CVE-2024-36004: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue (bsc#1224545)\n- CVE-2024-36005: netfilter: nf_tables: honor table dormant flag from netdev release event path (bsc#1224539).\n- CVE-2024-36008: ipv4: check for NULL idev in ip_route_use_hint() (bsc#1224540).\n- CVE-2024-36017: rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation (bsc#1225681).\n- CVE-2024-36020: i40e: fix vf may be used uninitialized in this function warning (bsc#1225698).\n- CVE-2024-36021: net: hns3: fix kernel crash when devlink reload during pf initialization (bsc#1225699).\n- CVE-2024-36478: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' (bsc#1226841).\n- CVE-2024-36479: fpga: bridge: add owner module and take its refcount (bsc#1226949).\n- CVE-2024-36890: mm/slab: make __free(kfree) accept error pointers (bsc#1225714).\n- CVE-2024-36894: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete (bsc#1225749).\n- CVE-2024-36899: gpiolib: cdev: Fix use after free in lineinfo_changed_notify (bsc#1225737).\n- CVE-2024-36900: net: hns3: fix kernel crash when devlink reload during initialization (bsc#1225726).\n- CVE-2024-36901: ipv6: prevent NULL dereference in ip6_output() (bsc#1225711)\n- CVE-2024-36902: ipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action() (bsc#1225719).\n- CVE-2024-36904: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique() (bsc#1225732).\n- CVE-2024-36909: Drivers: hv: vmbus: Do not free ring buffers that couldn't be re-encrypted (bsc#1225744).\n- CVE-2024-36910: uio_hv_generic: Do not free decrypted memory (bsc#1225717).\n- CVE-2024-36911: hv_netvsc: Do not free decrypted memory (bsc#1225745).\n- CVE-2024-36912: Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl (bsc#1225752).\n- CVE-2024-36913: Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails (bsc#1225753).\n- CVE-2024-36914: drm/amd/display: Skip on writeback when it's not applicable (bsc#1225757).\n- CVE-2024-36915: nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies (bsc#1225758).\n- CVE-2024-36916: blk-iocost: avoid out of bounds shift (bsc#1225759).\n- CVE-2024-36917: block: fix overflow in blk_ioctl_discard() (bsc#1225770).\n- CVE-2024-36919: scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload (bsc#1225767).\n- CVE-2024-36923: fs/9p: fix uninitialized values during inode evict (bsc#1225815).\n- CVE-2024-36934: bna: ensure the copied buf is NUL terminated (bsc#1225760).\n- CVE-2024-36937: xdp: use flags field to disambiguate broadcast redirect (bsc#1225834).\n- CVE-2024-36939: nfs: Handle error of rpc_proc_register() in nfs_net_init() (bsc#1225838).\n- CVE-2024-36940: pinctrl: core: delete incorrect free in pinctrl_enable() (bsc#1225840).\n- CVE-2024-36945: net/smc: fix neighbour and rtable leak in smc_ib_find_route() (bsc#1225823).\n- CVE-2024-36946: phonet: fix rtm_phonet_notify() skb allocation (bsc#1225851).\n- CVE-2024-36949: amd/amdkfd: sync all devices to wait all processes being evicted (bsc#1225872)\n- CVE-2024-36964: fs/9p: only translate RWX permissions for plain 9P2000 (bsc#1225866).\n- CVE-2024-36971: net: fix __dst_negative_advice() race (bsc#1226145).\n- CVE-2024-36974: net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP (bsc#1226519).\n- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).\n- CVE-2024-37021: fpga: manager: add owner module and take its refcount (bsc#1226950).\n- CVE-2024-37078: nilfs2: fix potential kernel bug due to lack of writeback flag waiting (bsc#1227066).\n- CVE-2024-37354: btrfs: fix crash on racing fsync and size-extending write into prealloc (bsc#1227101).\n- CVE-2024-38545: RDMA/hns: Fix UAF for cq async event (bsc#1226595).\n- CVE-2024-38553: net: fec: remove .ndo_poll_controller to avoid deadlock (bsc#1226744).\n- CVE-2024-38555: net/mlx5: Discard command completions in internal error (bsc#1226607).\n- CVE-2024-38556: net/mlx5: Add a timeout to acquire the command queue semaphore (bsc#1226774).\n- CVE-2024-38557: net/mlx5: Reload only IB representors upon lag disable/enable (bsc#1226781).\n- CVE-2024-38558: net: openvswitch: fix overwriting ct original tuple for ICMPv6 (bsc#1226783).\n- CVE-2024-38559: scsi: qedf: Ensure the copied buf is NUL terminated (bsc#1226785).\n- CVE-2024-38560: scsi: bfa: Ensure the copied buf is NUL terminated (bsc#1226786).\n- CVE-2024-38564: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE (bsc#1226789).\n- CVE-2024-38568: drivers/perf: hisi: hns3: Fix out-of-bound access when valid event group (bsc#1226771).\n- CVE-2024-38570: gfs2: Fix potential glock use-after-free on unmount (bsc#1226775).\n- CVE-2024-38578: ecryptfs: Fix buffer size for tag 66 packet (bsc#1226634).\n- CVE-2024-38580: epoll: be better about file lifetimes (bsc#1226610).\n- CVE-2024-38586: r8169: Fix possible ring buffer corruption on fragmented Tx packets (bsc#1226750).\n- CVE-2024-38594: net: stmmac: move the EST lock to struct stmmac_priv (bsc#1226734).\n- CVE-2024-38597: eth: sungem: remove .ndo_poll_controller to avoid deadlocks (bsc#1226749).\n- CVE-2024-38598: md: fix resync softlockup when bitmap size is less than array size (bsc#1226757).\n- CVE-2024-38603: drivers/perf: hisi: hns3: Actually use devm_add_action_or_reset() (bsc#1226842).\n- CVE-2024-38608: net/mlx5e: Fix netif state handling (bsc#1226746).\n- CVE-2024-38627: stm class: Fix a double free in stm_register_device() (bsc#1226857).\n- CVE-2024-38628: usb: gadget: u_audio: Fix race condition use of controls after free during gadget unbind (bsc#1226911).\n- CVE-2024-38659: enic: Validate length of nl attributes in enic_set_vf_port (bsc#1226883).\n- CVE-2024-38661: s390/ap: Fix crash in AP internal function modify_bitmap() (bsc#1226996).\n- CVE-2024-38780: dma-buf/sw-sync: do not enable IRQ from sync_print_obj() (bsc#1226886).\n- CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).\n- CVE-2024-39301: net/9p: fix uninit-value in p9_client_rpc() (bsc#1226994).\n- CVE-2024-39371: io_uring: check for non-NULL file pointer in io_file_can_poll() (bsc#1226990).\n- CVE-2024-39463: 9p: add missing locking around taking dentry fid list (bsc#1227090).\n- CVE-2024-39468: smb: client: fix deadlock in smb2_find_smb_tcon() (bsc#1227103).\n- CVE-2024-39469: nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors (bsc#1226992).\n- CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).\n- CVE-2024-39475: fbdev: savage: Handle err return when savagefb_check_var failed (bsc#1227435)\n- CVE-2024-39482: bcache: fix variable length array abuse in btree_iter (bsc#1227447).\n- CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)\n- CVE-2024-39490: ipv6: sr: fix missing sk_buff release in seg6_input_core (bsc#1227626).\n- CVE-2024-39493: crypto: qat - fix ADF_DEV_RESET_SYNC memory leak (bsc#1227620).\n- CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).\n- CVE-2024-39497: drm/shmem-helper: fix BUG_ON() on mmap(PROT_WRITE, MAP_PRIVATE) (bsc#1227722).\n- CVE-2024-39502: ionic: fix use after netif_napi_del() (bsc#1227755).\n- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).\n- CVE-2024-39508: io_uring/io-wq: use set_bit() and test_bit() at worker-\u003eflags (bsc#1227732).\n- CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).\n- CVE-2024-40906: net/mlx5: Always stop health timer during driver removal (bsc#1227763).\n- CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).\n- CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).\n- CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).\n- CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).\n- CVE-2024-40937: gve: Clear napi-\u003eskb before dev_kfree_skb_any() (bsc#1227836).\n- CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).\n- CVE-2024-40943: ocfs2: fix races between hole punching and AIO+DIO (bsc#1227849).\n- CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).\n- CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).\n- CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).\n- CVE-2024-40967: serial: imx: Introduce timeout when waiting on transmitter empty (bsc#1227891).\n- CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).\n- CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).\n- CVE-2024-40977: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery (bsc#1227950).\n- CVE-2024-40982: ssb: fix potential NULL pointer dereference in ssb_device_uevent() (bsc#1227865).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40998: ext4: fix uninitialized ratelimit_state-\u003elock access in __ext4_fill_super() (bsc#1227866).\n- CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).\n- CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).\n- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-41011: drm/amdkfd: do not allow mapping the MMIO HDP page with large pages (bsc#1228114).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).\n- CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41016: ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41059: hfsplus: fix uninit-value in copy_name (bsc#1228561).\n- CVE-2024-41063: bluetooth: hci_core: cancel all works upon hci_unregister_dev() (bsc#1228580).\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41071: wifi: mac80211: Avoid address calculations via out of bounds array indexing (bsc#1228625).\n- CVE-2024-41072: wifi: cfg80211: wext: add extra SIOCSIWSCAN data check (bsc#1228626).\n- CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).\n- CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).\n- CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743)\n- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).\n- CVE-2024-42230: powerpc/pseries: Fix scv instruction crash with kexec (bsc#1194869).\n\nThe following non-security bugs were fixed:\n\n- acpi: EC: Abort address space access upon error (stable-fixes).\n- acpi: EC: Avoid returning AE_OK on errors in address space handler (stable-fixes).\n- acpi: processor_idle: Fix invalid comparison with insertion sort for latency (git-fixes).\n- acpi: resource: Do IRQ override on TongFang GXxHRXx and GMxHGxx (stable-fixes).\n- acpi: video: Add backlight=native quirk for Lenovo Slim 7 16ARH7 (stable-fixes).\n- acpi: x86: Force StorageD3Enable on more products (stable-fixes).\n- acpi: x86: utils: Add Picasso to the list for forcing StorageD3Enable (stable-fixes).\n- acpica: Revert 'ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine.' (git-fixes).\n- alsa: dmaengine_pcm: terminate dmaengine before synchronize (stable-fixes).\n- alsa: dmaengine: Synchronize dma channel after drop() (stable-fixes).\n- alsa: emux: improve patch ioctl data validation (stable-fixes).\n- alsa: Fix deadlocks with kctl removals at disconnection (stable-fixes).\n- alsa: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- alsa: hda: intel-dsp-config: harden I2C/I2S codec detection (stable-fixes).\n- alsa: hda/realtek: Add more codec ID to no shutup pins list (stable-fixes).\n- alsa: hda/realtek: add quirk for Clevo V5[46]0TU (stable-fixes).\n- alsa: hda/realtek: Add quirks for Lenovo 13X (stable-fixes).\n- alsa: hda/realtek: Adjust G814JZR to use SPI init for amp (git-fixes).\n- alsa: hda/realtek: Enable headset mic of JP-IK LEAP W502 with ALC897 (stable-fixes).\n- alsa: hda/realtek: Enable headset mic on IdeaPad 330-17IKB 81DM (git-fixes).\n- alsa: hda/realtek: Enable headset mic on Positivo SU C1400 (stable-fixes).\n- alsa: hda/realtek: Enable Mute LED on HP 250 G7 (stable-fixes).\n- alsa: hda/realtek: Fix conflicting quirk for PCI SSID 17aa:3820 (git-fixes).\n- alsa: hda/realtek: fix mute/micmute LEDs do not work for EliteBook 645/665 G11 (stable-fixes).\n- alsa: hda/realtek: fix mute/micmute LEDs do not work for ProBook 440/460 G11 (stable-fixes).\n- alsa: hda/realtek: fix mute/micmute LEDs do not work for ProBook 445/465 G11 (stable-fixes).\n- alsa: hda/realtek: Fix the speaker output on Samsung Galaxy Book Pro 360 (stable-fixes).\n- alsa: hda/realtek: Limit mic boost on N14AP7 (stable-fixes).\n- alsa: hda/realtek: Limit mic boost on VAIO PRO PX (stable-fixes).\n- alsa: hda/realtek: Remove Framework Laptop 16 from quirks (git-fixes).\n- alsa: hda/relatek: Enable Mute LED on HP Laptop 15-gw0xxx (stable-fixes).\n- alsa: pcm_dmaengine: Do not synchronize DMA channel when DMA is paused (git-fixes).\n- alsa: timer: Set lower bound of start tick time (stable-fixes).\n- alsa: usb-audio: Add a quirk for Sonix HD USB Camera (stable-fixes).\n- alsa: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- alsa: usb-audio: Fix microphone sound on HD webcam (stable-fixes).\n- alsa: usb-audio: Move HD Webcam quirk to the right place (git-fixes).\n- alsa/hda: intel-dsp-config: Document AVS as dsp_driver option (git-fixes).\n- arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY (git-fixes).\n- arm64: dts: allwinner: Pine H64: correctly remove reg_gmac_3v3 (git-fixes)\n- arm64: dts: hi3798cv200: fix the size of GICR (git-fixes)\n- arm64: dts: imx8qm-mek: fix gpio number for reg_usdhc2_vmmc (git-fixes)\n- arm64: dts: microchip: sparx5: fix mdio reg (git-fixes)\n- arm64: dts: rockchip: Add enable-strobe-pulldown to emmc phy on ROCK (git-fixes)\n- arm64: dts: rockchip: Add sound-dai-cells for RK3368 (git-fixes)\n- arm64: dts: rockchip: fix PMIC interrupt pin on ROCK Pi E (git-fixes)\n- arm64: mm: Batch dsb and isb when populating pgtables (jsc#PED-8690).\n- arm64: mm: do not acquire mutex when rewriting swapper (jsc#PED-8690).\n- arm64: mm: Do not remap pgtables for allocate vs populate (jsc#PED-8690).\n- arm64: mm: Do not remap pgtables per-cont(pte|pmd) block (jsc#PED-8690).\n- arm64: tegra: Correct Tegra132 I2C alias (git-fixes)\n- arm64/io: add constant-argument check (bsc#1226502 git-fixes)\n- arm64/io: Provide a WC friendly __iowriteXX_copy() (bsc#1226502)\n- asoc: amd: acp: add a null check for chip_pdev structure (git-fixes).\n- asoc: amd: acp: remove i2s configuration check in acp_i2s_probe() (git-fixes).\n- asoc: amd: Adjust error handling in case of absent codec device (git-fixes).\n- asoc: da7219-aad: fix usage of device_get_named_child_node() (stable-fixes).\n- asoc: fsl-asoc-card: set priv-\u003epdev before using it (git-fixes).\n- asoc: max98088: Check for clk_prepare_enable() error (git-fixes).\n- asoc: rt5645: Fix the electric noise due to the CBJ contacts floating (stable-fixes).\n- asoc: rt715-sdca: volume step modification (stable-fixes).\n- asoc: rt715: add vendor clear control register (stable-fixes).\n- asoc: ti: davinci-mcasp: Set min period size using FIFO config (stable-fixes).\n- asoc: ti: omap-hdmi: Fix too long driver name (stable-fixes).\n- ata: ahci: Clean up sysfs file on error (git-fixes).\n- ata: libata-core: Fix double free on error (git-fixes).\n- ata: libata-core: Fix null pointer dereference on error (git-fixes).\n- batman-adv: bypass empty buckets in batadv_purge_orig_ref() (stable-fixes).\n- batman-adv: Do not accept TT entries for out-of-spec VIDs (git-fixes).\n- blk-cgroup: dropping parent refcount after pd_free_fn() is done (bsc#1224573).\n- block, loop: support partitions without scanning (bsc#1227162).\n- block: do not add partitions if GD_SUPPRESS_PART_SCAN is set (bsc#1227162).\n- bluetooth: ath3k: Fix multiple issues reported by checkpatch.pl (stable-fixes).\n- bluetooth: btqca: use le32_to_cpu for ver.soc_id (stable-fixes).\n- bluetooth: hci_core: cancel all works upon hci_unregister_dev() (stable-fixes).\n- bluetooth: hci_qca: mark OF related data as maybe unused (stable-fixes).\n- bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ (git-fixes).\n- bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot (git-fixes).\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener (git-fixes).\n- bpf: aggressively forget precise markings during state checkpointing (bsc#1225903).\n- bpf: allow precision tracking for programs with subprogs (bsc#1225903).\n- bpf: check bpf_func_state-\u003ecallback_depth when pruning states (bsc#1225903).\n- bpf: clean up visit_insn()'s instruction processing (bsc#1225903).\n- bpf: correct loop detection for iterators convergence (bsc#1225903).\n- bpf: encapsulate precision backtracking bookkeeping (bsc#1225903).\n- bpf: ensure state checkpointing at iter_next() call sites (bsc#1225903).\n- bpf: exact states comparison for iterator convergence checks (bsc#1225903).\n- bpf: extract __check_reg_arg() utility function (bsc#1225903).\n- bpf: extract same_callsites() as utility function (bsc#1225903).\n- bpf: extract setup_func_entry() utility function (bsc#1225903).\n- bpf: fix calculation of subseq_idx during precision backtracking (bsc#1225903).\n- bpf: fix mark_all_scalars_precise use in mark_chain_precision (bsc#1225903).\n- bpf: Fix memory leaks in __check_func_call (bsc#1225903).\n- bpf: fix propagate_precision() logic for inner frames (bsc#1225903).\n- bpf: fix regs_exact() logic in regsafe() to remap IDs correctly (bsc#1225903).\n- bpf: Fix to preserve reg parent/live fields when copying range info (bsc#1225903).\n- bpf: generalize MAYBE_NULL vs non-MAYBE_NULL rule (bsc#1225903).\n- bpf: improve precision backtrack logging (bsc#1225903).\n- bpf: Improve verifier u32 scalar equality checking (bsc#1225903).\n- bpf: keep track of max number of bpf_loop callback iterations (bsc#1225903).\n- bpf: maintain bitmasks across all active frames in __mark_chain_precision (bsc#1225903).\n- bpf: mark relevant stack slots scratched for register read instructions (bsc#1225903).\n- bpf: move explored_state() closer to the beginning of verifier.c (bsc#1225903).\n- bpf: perform byte-by-byte comparison only when necessary in regsafe() (bsc#1225903).\n- bpf: print full verifier states on infinite loop detection (bsc#1225903).\n- bpf: regsafe() must not skip check_ids() (bsc#1225903).\n- bpf: reject non-exact register type matches in regsafe() (bsc#1225903).\n- bpf: Remove unused insn_cnt argument from visit_[func_call_]insn() (bsc#1225903).\n- bpf: reorganize struct bpf_reg_state fields (bsc#1225903).\n- bpf: Skip invalid kfunc call in backtrack_insn (bsc#1225903).\n- bpf: states_equal() must build idmap for all function frames (bsc#1225903).\n- bpf: stop setting precise in current state (bsc#1225903).\n- bpf: support precision propagation in the presence of subprogs (bsc#1225903).\n- bpf: take into account liveness when propagating precision (bsc#1225903).\n- bpf: teach refsafe() to take into account ID remapping (bsc#1225903).\n- bpf: unconditionally reset backtrack_state masks on global func exit (bsc#1225903).\n- bpf: use check_ids() for active_lock comparison (bsc#1225903).\n- bpf: Use scalar ids in mark_chain_precision() (bsc#1225903).\n- bpf: verify callbacks as if they are called unknown number of times (bsc#1225903).\n- bpf: Verify scalar ids mapping in regsafe() using check_ids() (bsc#1225903).\n- bpf: widening for callback iterators (bsc#1225903).\n- btrfs: add device major-minor info in the struct btrfs_device (bsc#1227162).\n- btrfs: avoid copying BTRFS_ROOT_SUBVOL_DEAD flag to snapshot of subvolume being deleted (bsc#1221282).\n- btrfs: harden identification of a stale device (bsc#1227162).\n- btrfs: match stale devices by dev_t (bsc#1227162).\n- btrfs: remove the cross file system checks from remap (bsc#1227157).\n- btrfs: use dev_t to match device in device_matched (bsc#1227162).\n- btrfs: validate device maj:min during open (bsc#1227162).\n- bytcr_rt5640 : inverse jack detect for Archos 101 cesium (stable-fixes).\n- cachefiles: add output string to cachefiles_obj_[get|put]_ondemand_fd (git-fixes).\n- cachefiles: remove requests from xarray during flushing requests (bsc#1226588).\n- can: kvaser_usb: Explicitly initialize family in leafimx driver_info struct (git-fixes).\n- can: kvaser_usb: fix return value for hif_usb_send_regout (stable-fixes).\n- ceph: add ceph_cap_unlink_work to fire check_caps() immediately (bsc#1226022).\n- ceph: always check dir caps asynchronously (bsc#1226022).\n- ceph: always queue a writeback when revoking the Fb caps (bsc#1226022).\n- ceph: break the check delayed cap loop every 5s (bsc#1226022).\n- ceph: fix incorrect kmalloc size of pagevec mempool (bsc#1228418).\n- ceph: switch to use cap_delay_lock for the unlink delay list (bsc#1226022).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- check-for-config-changes: ignore also GCC_ASM_GOTO_OUTPUT_BROKEN .\n- checkpatch: really skip LONG_LINE_* when LONG_LINE is ignored (git-fixes).\n- cifs: fix hang in wait_for_response() (bsc#1220812, bsc#1220368).\n- cpufreq: amd-pstate: Fix the inconsistency in max frequency units (git-fixes).\n- crypto: aead,cipher - zeroize key buffer after use (stable-fixes).\n- crypto: ecdh - explicitly zeroize private_key (stable-fixes).\n- crypto: ecdsa - Fix the public key format description (git-fixes).\n- crypto: ecrdsa - Fix module auto-load on add_key (stable-fixes).\n- crypto: hisilicon/sec - Fix memory leak for sec resource release (stable-fixes).\n- csky: ftrace: Drop duplicate implementation of arch_check_ftrace_location() (git-fixes).\n- decompress_bunzip2: fix rare decompression failure (git-fixes).\n- devres: Fix devm_krealloc() wasting memory (git-fixes).\n- devres: Fix memory leakage caused by driver API devm_free_percpu() (git-fixes).\n- dma: fix call order in dmam_free_coherent (git-fixes).\n- dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (git-fixes).\n- dmaengine: ioatdma: Fix missing kmem_cache_destroy() (git-fixes).\n- docs: crypto: async-tx-api: fix broken code example (git-fixes).\n- docs: Fix formatting of literal sections in fanotify docs (stable-fixes).\n- drivers: core: synchronize really_probe() and dev_uevent() (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Valve Galileo (stable-fixes).\n- drm/amd: Fix shutdown (again) on some SMU v13.0.4/11 platforms (git-fixes).\n- drm/amd/amdgpu: Fix style errors in amdgpu_drv.c \u0026 amdgpu_device.c (stable-fixes).\n- drm/amd/display: Account for cursor prefetch BW in DML1 mode support (stable-fixes).\n- drm/amd/display: Add dtbclk access to dcn315 (stable-fixes).\n- drm/amd/display: Add VCO speed parameter for DCN31 FPU (stable-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Check index msg_id before read or write (stable-fixes).\n- drm/amd/display: Check pipe offset before setting vblank (stable-fixes).\n- drm/amd/display: drop unnecessary NULL checks in debugfs (stable-fixes).\n- drm/amd/display: Exit idle optimizations before HDCP execution (stable-fixes).\n- drm/amd/display: revert Exit idle optimizations before HDCP execution (stable-fixes).\n- drm/amd/display: Set color_mgmt_changed to true on unsuspend (stable-fixes).\n- drm/amd/display: Skip finding free audio for unknown engine_id (stable-fixes).\n- drm/amd/pm: Fix aldebaran pcie speed reporting (git-fixes).\n- drm/amd/pm: remove logically dead code for renoir (git-fixes).\n- drm/amdgpu: add error handle to avoid out-of-bounds (stable-fixes).\n- drm/amdgpu: avoid using null object of framebuffer (stable-fixes).\n- drm/amdgpu: Check if NBIO funcs are NULL in amdgpu_device_baco_exit (git-fixes).\n- drm/amdgpu: Fix pci state save during mode-1 reset (git-fixes).\n- drm/amdgpu: Fix signedness bug in sdma_v4_0_process_trap_irq() (git-fixes).\n- drm/amdgpu: Fix the ring buffer size for queue VM flush (stable-fixes).\n- drm/amdgpu: fix UBSAN warning in kv_dpm.c (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warnings (stable-fixes).\n- drm/amdgpu: Initialize timestamp for some legacy SOCs (stable-fixes).\n- drm/amdgpu: Remove GC HW IP 9.3.0 from noretry=1 (git-fixes).\n- drm/amdgpu: Update BO eviction priorities (stable-fixes).\n- drm/amdgpu/atomfirmware: add intergrated info v2.3 table (stable-fixes).\n- drm/amdgpu/atomfirmware: fix parsing of vram_info (stable-fixes).\n- drm/amdgpu/atomfirmware: silence UBSAN warning (stable-fixes).\n- drm/amdgpu/mes: fix use-after-free issue (stable-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/amdkfd: Flush the process wq before creating a kfd_process (stable-fixes).\n- drm/amdkfd: Rework kfd_locked handling (bsc#1225872)\n- drm/bridge/panel: Fix runtime warning on panel bridge release (git-fixes).\n- drm/dp_mst: Fix all mstb marked as not probed after suspend/resume (git-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/etnaviv: fix DMA direction handling for cached RW buffers (git-fixes).\n- drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found (git-fixes).\n- drm/exynos/vidi: fix memory leak in .get_modes() (stable-fixes).\n- drm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes (git-fixes).\n- drm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes (git-fixes).\n- drm/i915/dpt: Make DPT object unshrinkable (git-fixes).\n- drm/i915/gt: Disarm breadcrumbs if engines are already idle (git-fixes).\n- drm/i915/gt: Do not consider preemption during execlists_dequeue for gen8 (git-fixes).\n- drm/i915/gt: Fix potential UAF by revoke of fence registers (git-fixes).\n- drm/i915/guc: avoid FIELD_PREP warning (git-fixes).\n- drm/i915/mso: using joiner is not possible with eDP MSO (git-fixes).\n- drm/komeda: check for error-valued pointer (git-fixes).\n- drm/lima: add mask irq callback to gp and pp (stable-fixes).\n- drm/lima: fix shared irq handling on driver remove (stable-fixes).\n- drm/lima: Mark simple_ondemand governor as softdep (git-fixes).\n- drm/lima: mask irqs in timeout path before hard reset (stable-fixes).\n- drm/mediatek: Add OVL compatible name for MT8195 (git-fixes).\n- drm/meson: fix canvas release in bind function (git-fixes).\n- drm/mgag200: Bind I2C lifetime to DRM device (git-fixes).\n- drm/mgag200: Set DDC timeout in milliseconds (git-fixes).\n- drm/mipi-dsi: Fix mipi_dsi_dcs_write_seq() macro definition format (stable-fixes).\n- drm/mipi-dsi: Fix theoretical int overflow in mipi_dsi_dcs_write_seq() (git-fixes).\n- drm/msm: Enable clamp_to_idle for 7c3 (stable-fixes).\n- drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails (git-fixes).\n- drm/msm/dp: Avoid a long timeout for AUX transfer if nothing connected (git-fixes).\n- drm/msm/dp: Return IRQ_NONE for unhandled interrupts (stable-fixes).\n- drm/msm/dpu: drop validity checks for clear_pending_flush() ctl op (git-fixes).\n- drm/msm/mdp5: Remove MDP_CAP_SRC_SPLIT from msm8x53_config (git-fixes).\n- drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes (git-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes (stable-fixes).\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes (stable-fixes).\n- drm/panel-samsung-atna33xc20: Use ktime_get_boottime for delays (stable-fixes).\n- drm/panel: boe-tv101wum-nl6: Check for errors on the NOP in prepare() (git-fixes).\n- drm/panel: boe-tv101wum-nl6: If prepare fails, disable GPIO before regulators (git-fixes).\n- drm/panel: ilitek-ili9881c: Fix warning with GPIO controllers that sleep (stable-fixes).\n- drm/panel: simple: Add missing display timing flags for KOE TX26D202VM0BWA (git-fixes).\n- drm/panfrost: Mark simple_ondemand governor as softdep (git-fixes).\n- drm/qxl: Add check for drm_cvt_mode (git-fixes).\n- drm/radeon: check bo_va-\u003ebo is non-NULL before using it (stable-fixes).\n- drm/radeon: fix UBSAN warning in kv_dpm.c (stable-fixes).\n- drm/radeon/radeon_display: Decrease the size of allocated memory (stable-fixes).\n- drm/vmwgfx: 3D disabled should not effect STDU memory limits (git-fixes).\n- drm/vmwgfx: Filter modes which exceed graphics memory (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency (stable-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- eeprom: digsy_mtc: Fix 93xx46 driver probe failure (git-fixes).\n- exfat: check if cluster num is valid (git-fixes).\n- exfat: simplify is_valid_cluster() (git-fixes).\n- filelock: add a new locks_inode_context accessor function (git-fixes).\n- firmware: cs_dsp: Fix overflow checking of wmfw header (git-fixes).\n- firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers (git-fixes).\n- firmware: cs_dsp: Return error if block header overflows file (git-fixes).\n- firmware: cs_dsp: Use strnlen() on name fields in V1 wmfw files (git-fixes).\n- firmware: cs_dsp: Validate payload length before processing block (git-fixes).\n- firmware: dmi: Stop decoding on broken entry (stable-fixes).\n- firmware: turris-mox-rwtm: Do not complete if there are no waiters (git-fixes).\n- firmware: turris-mox-rwtm: Fix checking return value of wait_for_completion_timeout() (git-fixes).\n- firmware: turris-mox-rwtm: Initialize completion before mailbox (git-fixes).\n- fs: allow cross-vfsmount reflink/dedupe (bsc#1227157).\n- ftrace: Fix possible use-after-free issue in ftrace_location() (git-fixes).\n- fuse: verify {g,u}id mount options correctly (bsc#1228191).\n- gpio: davinci: Validate the obtained number of IRQs (git-fixes).\n- gpio: mc33880: Convert comma to semicolon (git-fixes).\n- gpio: tqmx86: fix typo in Kconfig label (git-fixes).\n- gpio: tqmx86: introduce shadow register for GPIO output value (git-fixes).\n- gpiolib: cdev: Disallow reconfiguration without direction (uAPI v1) (git-fixes).\n- hfsplus: fix to avoid false alarm of circular locking (git-fixes).\n- hfsplus: fix uninit-value in copy_name (git-fixes).\n- hid: Add quirk for Logitech Casa touchpad (stable-fixes).\n- hid: core: remove unnecessary WARN_ON() in implement() (git-fixes).\n- hid: logitech-dj: Fix memory leak in logi_dj_recv_switch_to_dj_mode() (git-fixes).\n- hid: wacom: Modify pen IDs (git-fixes).\n- hpet: Support 32-bit userspace (git-fixes).\n- hwmon: (adt7475) Fix default duty on fan is disabled (git-fixes).\n- hwmon: (max6697) Fix swapped temp{1,8} critical alarms (git-fixes).\n- hwmon: (max6697) Fix underflow when writing limit attributes (git-fixes).\n- hwmon: (shtc1) Fix property misspelling (git-fixes).\n- i2c: at91: Fix the functionality flags of the slave-only interface (git-fixes).\n- i2c: designware: Fix the functionality flags of the slave-only interface (git-fixes).\n- i2c: mark HostNotify target address as used (git-fixes).\n- i2c: ocores: set IACK bit after core is enabled (git-fixes).\n- i2c: rcar: bring hardware to known state when probing (git-fixes).\n- i2c: tegra: Fix failure during probe deferral cleanup (git-fixes)\n- i2c: tegra: Share same DMA channel for RX and TX (bsc#1227661)\n- i2c: testunit: avoid re-issued work after read message (git-fixes).\n- i2c: testunit: correct Kconfig description (git-fixes).\n- i2c: testunit: discard write requests while old command is running (git-fixes).\n- i2c: testunit: do not erase registers after STOP (git-fixes).\n- iio: accel: fxls8962af: select IIO_BUFFER \u0026 IIO_KFIFO_BUF (git-fixes).\n- iio: adc: ad7266: Fix variable checking bug (git-fixes).\n- iio: adc: ad9467: fix scan type sign (git-fixes).\n- iio: chemical: bme680: Fix calibration data variable (git-fixes).\n- iio: chemical: bme680: Fix overflows in compensate() functions (git-fixes).\n- iio: chemical: bme680: Fix pressure value output (git-fixes).\n- iio: chemical: bme680: Fix sensor data read operation (git-fixes).\n- iio: dac: ad5592r: fix temperature channel scaling value (git-fixes).\n- iio: imu: inv_icm42600: delete unneeded update watermark call (git-fixes).\n- input: elan_i2c - do not leave interrupt disabled on suspend failure (git-fixes).\n- input: elantech - fix touchpad state on resume for Lenovo N24 (stable-fixes).\n- input: ff-core - prefer struct_size over open coded arithmetic (stable-fixes).\n- Input: ili210x - fix ili251x_read_touch_data() return value (git-fixes).\n- input: qt1050 - handle CHIP_ID reading error (git-fixes).\n- input: silead - Always support 10 fingers (stable-fixes).\n- intel_th: pci: Add Granite Rapids SOC support (stable-fixes).\n- intel_th: pci: Add Granite Rapids support (stable-fixes).\n- intel_th: pci: Add Lunar Lake support (stable-fixes).\n- intel_th: pci: Add Meteor Lake-S CPU support (stable-fixes).\n- intel_th: pci: Add Meteor Lake-S support (stable-fixes).\n- intel_th: pci: Add Sapphire Rapids SOC support (stable-fixes).\n- iommu: mtk: fix module autoloading (git-fixes).\n- iommu: Return right value in iommu_sva_bind_device() (git-fixes).\n- iommu/amd: Fix sysfs leak in iommu init (git-fixes).\n- iommu/arm-smmu-v3: Free MSIs in case of ENOMEM (git-fixes).\n- ionic: clean interrupt before enabling queue to avoid credit race (git-fixes).\n- ipvs: Fix checksumming on GSO of SCTP packets (bsc#1221958)\n- jffs2: Fix potential illegal address access in jffs2_free_inode (git-fixes).\n- jfs: Fix array-index-out-of-bounds in diFree (git-fixes).\n- jfs: xattr: fix buffer overflow for invalid xattr (bsc#1227383).\n- kabi: bpf: bpf_reg_state reorganization kABI workaround (bsc#1225903).\n- kabi: bpf: callback fixes kABI workaround (bsc#1225903).\n- kabi: bpf: struct bpf_{idmap,idset} kABI workaround (bsc#1225903).\n- kabi: bpf: tmp_str_buf kABI workaround (bsc#1225903).\n- kabi: rtas: Workaround false positive due to lost definition (bsc#1227487).\n- kabi: Use __iowriteXX_copy_inlined for in-kernel modules (bsc#1226502)\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severities: Ignore tpm_tis_core_init (bsc#1082555).\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kbuild: do not include include/config/auto.conf from shell scripts (bsc#1227274).\n- kbuild: Install dtb files as 0644 in Makefile.dtbinst (git-fixes).\n- kconfig: doc: fix a typo in the note about 'imply' (git-fixes).\n- kconfig: fix comparison to constant symbols, 'm', 'n' (git-fixes).\n- kernel-binary: vdso: Own module_dir\n- kernel-doc: fix struct_group_tagged() parsing (git-fixes).\n- kernel/sched: Remove dl_boosted flag comment (git fixes (sched)).\n- knfsd: LOOKUP can return an illegal error value (git-fixes).\n- kobject_uevent: Fix OOB access within zap_modalias_env() (git-fixes).\n- kprobes: Make arch_check_ftrace_location static (git-fixes).\n- kvm: nVMX: Clear EXIT_QUALIFICATION when injecting an EPT Misconfig (git-fixes).\n- kvm: PPC: Book3S HV Nested: L2 LPCR should inherit L1 LPES setting (bsc#1194869).\n- kvm: PPC: Book3S HV: Fix 'rm_exit' entry in debugfs timings (bsc#1194869).\n- kvm: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- kvm: PPC: Book3S HV: remove extraneous asterisk from rm_host_ipi_action() comment (bsc#1194869).\n- kvm: PPC: Book3S: Suppress failed alloc warning in H_COPY_TOFROM_GUEST (bsc#1194869).\n- kvm: PPC: Book3S: Suppress warnings when allocating too big memory slots (bsc#1194869).\n- kvm: s390: fix LPSWEY handling (bsc#1227635 git-fixes).\n- kvm: SVM: Process ICR on AVIC IPI delivery failure due to invalid target (git-fixes).\n- kvm: VMX: Report up-to-date exit qualification to userspace (git-fixes).\n- kvm: x86: Add IBPB_BRTYPE support (bsc#1228079).\n- kvm: x86: Always sync PIR to IRR prior to scanning I/O APIC routes (git-fixes).\n- kvm: x86: Bail from kvm_recalculate_phys_map() if x2APIC ID is out-of-bounds (git-fixes).\n- kvm: x86: Disable APIC logical map if logical ID covers multiple MDAs (git-fixes).\n- kvm: x86: Disable APIC logical map if vCPUs are aliased in logical mode (git-fixes).\n- kvm: x86: Do not advertise guest.MAXPHYADDR as host.MAXPHYADDR in CPUID (git-fixes).\n- kvm: x86: Explicitly skip optimized logical map setup if vCPU's LDR==0 (git-fixes).\n- kvm: x86: Explicitly track all possibilities for APIC map's logical modes (git-fixes).\n- kvm: x86: Fix broken debugregs ABI for 32 bit kernels (git-fixes).\n- kvm: x86: Fix KVM_GET_MSRS stack info leak (git-fixes).\n- kvm: x86: Honor architectural behavior for aliased 8-bit APIC IDs (git-fixes).\n- kvm: x86: Purge 'highest ISR' cache when updating APICv state (git-fixes).\n- kvm: x86: Save/restore all NMIs when multiple NMIs are pending (git-fixes).\n- kvm: x86: Skip redundant x2APIC logical mode optimized cluster setup (git-fixes).\n- leds: ss4200: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- leds: trigger: Unregister sysfs attributes before calling deactivate() (git-fixes).\n- leds: triggers: Flush pending brightness before activating trigger (git-fixes).\n- lib: memcpy_kunit: Fix an invalid format specifier in an assertion msg (git-fixes).\n- lib: objagg: Fix general protection fault (git-fixes).\n- lib: objagg: Fix spelling (git-fixes).\n- lib: test_objagg: Fix spelling (git-fixes).\n- libceph: fix race between delayed_work() and ceph_monc_stop() (bsc#1228190).\n- lockd: set missing fl_flags field when retrieving args (git-fixes).\n- lockd: use locks_inode_context helper (git-fixes).\n- Make AMD_HSMP=m and mark it unsupported in supported.conf (jsc#PED-8582)\n- media: dvb-frontends: tda10048: Fix integer overflow (stable-fixes).\n- media: dvb-frontends: tda18271c2dd: Remove casting during div (stable-fixes).\n- media: dvb-usb: dib0700_devices: Add missing release_firmware() (stable-fixes).\n- media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control() (git-fixes).\n- media: dvb: as102-fe: Fix as10x_register_addr packing (stable-fixes).\n- media: dvbdev: Initialize sbuf (stable-fixes).\n- media: dw2102: Do not translate i2c read into write (stable-fixes).\n- media: dw2102: fix a potential buffer overflow (git-fixes).\n- media: flexcop-usb: clean up endpoint sanity checks (stable-fixes).\n- media: flexcop-usb: fix sanity check of bNumEndpoints (git-fixes).\n- media: imon: Fix race getting ictx-\u003elock (git-fixes).\n- media: ipu3-cio2: Use temporary storage for struct device pointer (stable-fixes).\n- media: lgdt3306a: Add a check against null-pointer-def (stable-fixes).\n- media: mxl5xx: Move xpt structures off stack (stable-fixes).\n- media: radio-shark2: Avoid led_names truncations (git-fixes).\n- media: s2255: Use refcount_t instead of atomic_t for num_channels (stable-fixes).\n- media: uvcvideo: Fix integer overflow calculating timestamp (git-fixes).\n- media: uvcvideo: Override default flags (git-fixes).\n- media: v4l2-core: hold videodev_lock until dev reg, finishes (stable-fixes).\n- media: venus: fix use after free in vdec_close (git-fixes).\n- media: venus: flush all buffers in output plane streamoff (git-fixes).\n- mei: demote client disconnect warning on suspend to debug (stable-fixes).\n- mei: me: release irq in mei_me_pci_resume error path (git-fixes).\n- mfd: omap-usb-tll: Use struct_size to allocate tll (git-fixes).\n- mkspec-dtb: add toplevel symlinks also on arm\n- mmc: core: Add mmc_gpiod_set_cd_config() function (stable-fixes).\n- mmc: core: Do not force a retune before RPMB switch (stable-fixes).\n- mmc: sdhci_am654: Add ITAPDLYSEL in sdhci_j721e_4bit_set_clock (git-fixes).\n- mmc: sdhci_am654: Add OTAP/ITAP delay enable (git-fixes).\n- mmc: sdhci_am654: Drop lookup for deprecated ti,otap-del-sel (stable-fixes).\n- mmc: sdhci_am654: Fix ITAPDLY for HS400 timing (git-fixes).\n- mmc: sdhci-acpi: Disable write protect detection on Toshiba WT10-A (stable-fixes).\n- mmc: sdhci-acpi: Fix Lenovo Yoga Tablet 2 Pro 1380 sdcard slot not working (stable-fixes).\n- mmc: sdhci-acpi: Sort DMI quirks alphabetically (stable-fixes).\n- mmc: sdhci-pci: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- mmc: sdhci: Do not invert write-protect twice (git-fixes).\n- mmc: sdhci: Do not lock spinlock around mmc_gpio_get_ro() (git-fixes).\n- mtd: partitions: redboot: Added conversion of operands to a larger type (stable-fixes).\n- mtd: rawnand: Bypass a couple of sanity checks during NAND identification (git-fixes).\n- mtd: rawnand: Ensure ECC configuration is propagated to upper layers (git-fixes).\n- mtd: rawnand: rockchip: ensure NVDDR timings are rejected (git-fixes).\n- net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new (git-fixes).\n- net: can: j1939: Initialize unused data in j1939_send_one() (git-fixes).\n- net: can: j1939: recover socket queue on CAN bus error during BAM transmission (git-fixes).\n- net: ena: Fix redundant device NUMA node override (jsc#PED-8690).\n- net: mana: Enable MANA driver on ARM64 with 4K page size (jsc#PED-8491).\n- net: mana: Fix possible double free in error handling path (git-fixes).\n- net: mana: Fix the extra HZ in mana_hwc_send_request (git-fixes).\n- net: phy: Micrel KSZ8061: fix errata solution not taking effect problem (git-fixes).\n- net: phy: micrel: add Microchip KSZ 9477 to the device table (git-fixes).\n- net: usb: ax88179_178a: improve link status logs (git-fixes).\n- net: usb: ax88179_178a: improve reset check (git-fixes).\n- net: usb: qmi_wwan: add Telit FN912 compositions (git-fixes).\n- net: usb: qmi_wwan: add Telit FN920C04 compositions (stable-fixes).\n- net: usb: rtl8150 fix unintiatilzed variables in rtl8150_get_link_ksettings (git-fixes).\n- net: usb: smsc95xx: fix changing LED_SEL bit value updated from EEPROM (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- net/dcb: check for detached device before executing callbacks (bsc#1215587).\n- net/mlx5e: Fix a race in command alloc flow (git-fixes).\n- netfilter: conntrack: ignore overly delayed tcp packets (bsc#1223180).\n- netfilter: conntrack: prepare tcp_in_window for ternary return value (bsc#1223180).\n- netfilter: conntrack: remove pr_debug callsites from tcp tracker (bsc#1223180).\n- netfilter: conntrack: work around exceeded receive window (bsc#1223180).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc/nci: Add the inconsistency check between the input data length and count (stable-fixes).\n- nfs: abort nfs_atomic_open_v23 if name is too long (bsc#1219847).\n- nfs: add atomic_open for NFSv3 to handle O_TRUNC correctly (bsc#1219847).\n- nfs: avoid infinite loop in pnfs_update_layout (bsc#1219633 bsc#1226226).\n- nfs: Fix READ_PLUS when server does not support OP_READ_PLUS (git-fixes).\n- nfs: fix undefined behavior in nfs_block_bits() (git-fixes).\n- nfs: keep server info for remounts (git-fixes).\n- nfs: Leave pages in the pagecache if readpage failed (git-fixes).\n- nfsd enforce filehandle check for source file in COPY (git-fixes).\n- nfsd: Add an nfsd_file_fsync tracepoint (git-fixes).\n- nfsd: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection (git-fixes).\n- nfsd: Add errno mapping for EREMOTEIO (git-fixes).\n- nfsd: Add nfsd_file_lru_dispose_list() helper (git-fixes).\n- nfsd: add some comments to nfsd_file_do_acquire (git-fixes).\n- nfsd: allow nfsd_file_get to sanely handle a NULL pointer (git-fixes).\n- nfsd: allow reaping files still under writeback (git-fixes).\n- nfsd: Avoid calling fh_drop_write() twice in do_nfsd_create() (git-fixes).\n- nfsd: Clean up nfsd_file_put() (git-fixes).\n- nfsd: Clean up nfsd_open_verified() (git-fixes).\n- nfsd: Clean up nfsd3_proc_create() (git-fixes).\n- nfsd: Clean up unused code after rhashtable conversion (git-fixes).\n- nfsd: Convert filecache to rhltable (git-fixes).\n- nfsd: Convert the filecache to use rhashtable (git-fixes).\n- nfsd: De-duplicate hash bucket indexing (git-fixes).\n- nfsd: do not free files unconditionally in __nfsd_file_cache_purge (git-fixes).\n- nfsd: do not fsync nfsd_files on last close (git-fixes).\n- nfsd: do not hand out delegation on setuid files being opened for write (git-fixes).\n- nfsd: do not kill nfsd_files because of lease break error (git-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nfsd: do not take/put an extra reference when putting a file (git-fixes).\n- nfsd: Ensure nf_inode is never dereferenced (git-fixes).\n- nfsd: fix handling of cached open files in nfsd4_open codepath (git-fixes).\n- nfsd: Fix licensing header in filecache.c (git-fixes).\n- nfsd: fix net-namespace logic in __nfsd_file_cache_purge (git-fixes).\n- nfsd: fix nfsd_file_unhash_and_dispose (git-fixes).\n- nfsd: Fix potential use-after-free in nfsd_file_put() (git-fixes).\n- nfsd: Fix problem of COMMIT and NFS4ERR_DELAY in infinite loop (git-fixes).\n- nfsd: Fix the filecache LRU shrinker (git-fixes).\n- nfsd: fix up the filecache laundrette scheduling (git-fixes).\n- nfsd: fix use-after-free in nfsd_file_do_acquire tracepoint (git-fixes).\n- nfsd: Flesh out a documenting comment for filecache.c (git-fixes).\n- nfsd: handle errors better in write_ports_addfd() (git-fixes).\n- nfsd: Instantiate a struct file when creating a regular NFSv4 file (git-fixes).\n- nfsd: Leave open files out of the filecache LRU (git-fixes).\n- nfsd: map EBADF (git-fixes).\n- nfsd: Move nfsd_file_trace_alloc() tracepoint (git-fixes).\n- nfsd: nfsd_file_hash_remove can compute hashval (git-fixes).\n- nfsd: NFSD_FILE_KEY_INODE only needs to find GC'ed entries (git-fixes).\n- nfsd: nfsd_file_put() can sleep (git-fixes).\n- nfsd: nfsd_file_unhash can compute hashval from nf-\u003enf_inode (git-fixes).\n- nfsd: No longer record nf_hashval in the trace log (git-fixes).\n- nfsd: optimise recalculate_deny_mode() for a common case (bsc#1217912).\n- nfsd: Pass the target nfsd_file to nfsd_commit() (git-fixes).\n- nfsd: put the export reference in nfsd4_verify_deleg_dentry (git-fixes).\n- nfsd: Record number of flush calls (git-fixes).\n- nfsd: Refactor __nfsd_file_close_inode() (git-fixes).\n- nfsd: Refactor nfsd_create_setattr() (git-fixes).\n- nfsd: Refactor nfsd_file_gc() (git-fixes).\n- nfsd: Refactor nfsd_file_lru_scan() (git-fixes).\n- nfsd: Refactor NFSv3 CREATE (git-fixes).\n- nfsd: Refactor NFSv4 OPEN(CREATE) (git-fixes).\n- nfsd: Remove do_nfsd_create() (git-fixes).\n- nfsd: Remove lockdep assertion from unhash_and_release_locked() (git-fixes).\n- nfsd: Remove nfsd_file::nf_hashval (git-fixes).\n- nfsd: remove the pages_flushed statistic from filecache (git-fixes).\n- nfsd: reorganize filecache.c (git-fixes).\n- nfsd: Replace the 'init once' mechanism (git-fixes).\n- nfsd: Report average age of filecache items (git-fixes).\n- nfsd: Report count of calls to nfsd_file_acquire() (git-fixes).\n- nfsd: Report count of freed filecache items (git-fixes).\n- nfsd: Report filecache LRU size (git-fixes).\n- nfsd: Report the number of items evicted by the LRU walk (git-fixes).\n- nfsd: Retry once in nfsd_open on an -EOPENSTALE return (git-fixes).\n- nfsd: rework hashtable handling in nfsd_do_file_acquire (git-fixes).\n- nfsd: rework refcounting in filecache (git-fixes).\n- nfsd: Separate tracepoints for acquire and create (git-fixes).\n- nfsd: Set up an rhashtable for the filecache (git-fixes).\n- nfsd: silence extraneous printk on nfsd.ko insertion (git-fixes).\n- nfsd: simplify per-net file cache management (git-fixes).\n- nfsd: simplify test_bit return in NFSD_FILE_KEY_FULL comparator (git-fixes).\n- nfsd: simplify the delayed disposal list code (git-fixes).\n- nfsd: Trace filecache LRU activity (git-fixes).\n- nfsd: Trace filecache opens (git-fixes).\n- nfsd: update comment over __nfsd_file_cache_purge (git-fixes).\n- nfsd: verify the opened dentry after setting a delegation (git-fixes).\n- nfsd: WARN when freeing an item still linked via nf_lru (git-fixes).\n- nfsd: Write verifier might go backwards (git-fixes).\n- nfsd: Zero counters when the filecache is re-initialized (git-fixes).\n- nfsv4: by default serialize open/close operations (bsc#1223863 bsc#1227362)\n- nfsv4: Fixup smatch warning for ambiguous return (git-fixes).\n- nilfs2: add missing check for inode numbers on directory entries (git-fixes).\n- nilfs2: add missing check for inode numbers on directory entries (stable-fixes).\n- nilfs2: avoid undefined behavior in nilfs_cnt32_ge macro (git-fixes).\n- nilfs2: convert persistent object allocator to use kmap_local (git-fixes).\n- nilfs2: fix incorrect inode allocation from reserved inodes (git-fixes).\n- nilfs2: fix inode number range checks (git-fixes).\n- nilfs2: fix inode number range checks (stable-fixes).\n- nilfs2: fix potential hang in nilfs_detach_log_writer() (stable-fixes).\n- nvme-auth: alloc nvme_dhchap_key as single buffer (git-fixes).\n- nvme-auth: allow mixing of secret and hash lengths (git-fixes).\n- nvme-auth: use transformed key size to create resp (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: ensure reset state check ordering (bsc#1215492).\n- nvme: find numa distance only if controller has valid numa id (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: use ctrl state accessor (bsc#1215492).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet-passthru: propagate status from id override functions (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- ocfs2: adjust enabling place for la window (bsc#1219224).\n- ocfs2: fix DIO failure due to insufficient transaction credits (bsc#1216834).\n- ocfs2: fix sparse warnings (bsc#1219224).\n- ocfs2: improve write IO performance when fragmentation is high (bsc#1219224).\n- ocfs2: remove redundant assignment to variable free_space (bsc#1228409).\n- ocfs2: speed up chain-list searching (bsc#1219224).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- orangefs: fix out-of-bounds fsid access (git-fixes).\n- pci: Add PCI_ERROR_RESPONSE and related definitions (stable-fixes).\n- pci: Clear Secondary Status errors after enumeration (bsc#1226928)\n- pci: Extend ACS configurability (bsc#1228090).\n- pci: Fix resource double counting on remove \u0026 rescan (git-fixes).\n- pci: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- pci: Introduce cleanup helpers for device reference counts and locks (git-fixes).\n- pci: Introduce cleanup helpers for device reference counts and locks (stable-fixes).\n- pci: keystone: Do not enable BAR 0 for AM654x (git-fixes).\n- pci: keystone: Fix NULL pointer dereference in case of DT error in ks_pcie_setup_rc_app_regs() (git-fixes).\n- pci: keystone: Relocate ks_pcie_set/clear_dbi_mode() (git-fixes).\n- pci: rockchip: Use GPIOD_OUT_LOW flag while requesting ep_gpio (git-fixes).\n- pci: tegra194: Set EP alignment restriction for inbound ATU (git-fixes).\n- pci/aspm: Update save_state when configuration changes (bsc#1226915)\n- pci/dpc: Fix use-after-free on concurrent DPC and hot-removal (git-fixes).\n- pci/pm: Avoid D3cold for HP Pavilion 17 PC/1972 PCIe Ports (git-fixes).\n- pci/pm: Avoid D3cold for HP Pavilion 17 PC/1972 PCIe Ports (stable-fixes).\n- pinctrl: core: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- pinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER (git-fixes).\n- pinctrl: freescale: mxs: Fix refcount of child (git-fixes).\n- pinctrl: qcom: spmi-gpio: drop broken pm8008 support (git-fixes).\n- pinctrl: rockchip: fix pinmux bits for RK3328 GPIO2-B pins (git-fixes).\n- pinctrl: rockchip: fix pinmux bits for RK3328 GPIO3-B pins (git-fixes).\n- pinctrl: rockchip: fix pinmux reset in rockchip_pmx_set (git-fixes).\n- pinctrl: rockchip: update rk3308 iomux routes (git-fixes).\n- pinctrl: rockchip: use dedicated pinctrl type for RK3328 (git-fixes).\n- pinctrl: single: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- pinctrl: ti: ti-iodelay: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- platform/chrome: cros_ec_debugfs: fix wrong EC message version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86: dell-smbios-base: Use sysfs_emit() (stable-fixes).\n- platform/x86: dell-smbios: Fix wrong token data in sysfs (git-fixes).\n- platform/x86: lg-laptop: Change ACPI device id (stable-fixes).\n- platform/x86: lg-laptop: Remove LGEX0815 hotkey handling (stable-fixes).\n- platform/x86: touchscreen_dmi: Add info for GlobalSpace SolT IVW 11.6' tablet (stable-fixes).\n- platform/x86: touchscreen_dmi: Add info for the EZpad 6s Pro (stable-fixes).\n- platform/x86: wireless-hotkey: Add support for LG Airplane Button (stable-fixes).\n- power: supply: cros_usbpd: provide ID table for avoiding fallback match (stable-fixes).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc/cpuidle: Set CPUIDLE_FLAG_POLLING for snooze state (bsc#1227121 ltc#207129).\n- powerpc/kasan: Disable address sanitization in kexec paths (bsc#1194869).\n- powerpc/pseries: Fix scv instruction crash with kexec (bsc#1194869).\n- powerpc/rtas: clean up includes (bsc#1227487).\n- powerpc/rtas: Prevent Spectre v1 gadget construction in sys_rtas() (bsc#1227487).\n- pwm: stm32: Always do lazy disabling (git-fixes).\n- random: treat bootloader trust toggle the same way as cpu trust toggle (bsc#1226953).\n- ras/amd/atl: Fix MI300 bank hash (bsc#1225300).\n- ras/amd/atl: Use system settings for MI300 DRAM to normalized address translation (bsc#1225300).\n- rdma/cache: Release GID table even if leak is detected (git-fixes)\n- rdma/device: Return error earlier if port in not valid (git-fixes)\n- rdma/hns: Check atomic wr length (git-fixes)\n- rdma/hns: Fix incorrect sge nums calculation (git-fixes)\n- rdma/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- rdma/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- rdma/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- rdma/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- rdma/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- rdma/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- rdma/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- rdma/irdma: Drop unused kernel push code (git-fixes)\n- rdma/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- rdma/mana_ib: Ignore optional access flags for MRs (git-fixes).\n- rdma/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- rdma/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- rdma/mlx5: Add check for srq max_sge attribute (git-fixes)\n- rdma/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- rdma/restrack: Fix potential invalid address access (git-fixes)\n- rdma/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- regmap-i2c: Subtract reg size from max_write (stable-fixes).\n- regulator: bd71815: fix ramp values (git-fixes).\n- regulator: core: Fix modpost error 'regulator_get_regmap' undefined (git-fixes).\n- regulator: irq_helpers: duplicate IRQ name (stable-fixes).\n- regulator: vqmmc-ipq4019: fix module autoloading (stable-fixes).\n- Revert 'Add remote for nfs maintainer'\n- Revert 'ALSA: firewire-lib: obsolete workqueue for period update' (bsc#1208783).\n- Revert 'ALSA: firewire-lib: operate for period elapse event in process context' (bsc#1208783).\n- Revert 'build initrd without systemd' (bsc#1195775)'.\n- Revert 'leds: led-core: Fix refcount leak in of_led_get()' (git-fixes).\n- Revert 'usb: musb: da8xx: Set phy in OTG mode by default' (stable-fixes).\n- rpcrdma: fix handling for RDMA_CM_EVENT_DEVICE_REMOVAL (git-fixes).\n- rpm/guards: fix precedence issue with control flow operator\n- rpm/kernel-obs-build.spec.in: Add iso9660 (bsc#1226212)\n- rpm/kernel-obs-build.spec.in: Add networking modules for docker (bsc#1226211)\n- rpm/kernel-obs-build.spec.in: Include algif_hash, aegis128 and xts modules afgif_hash is needed by some packages (e.g. iwd) for tests, xts is used for LUKS2 volumes by default and aegis128 is useful as AEAD cipher for LUKS2.\n- rpm/mkspec-dtb: dtbs have moved to vendor sub-directories in 6.5\n- rtc: cmos: Fix return value of nvmem callbacks (git-fixes).\n- rtc: interface: Add RTC offset to alarm after fix-up (git-fixes).\n- rtc: isl1208: Fix return value of nvmem callbacks (git-fixes).\n- rtlwifi: rtl8192de: Style clean-ups (stable-fixes).\n- s390: Implement __iowrite32_copy() (bsc#1226502)\n- s390: Stop using weak symbols for __iowrite64_copy() (bsc#1226502)\n- saa7134: Unchecked i2c_transfer function result fixed (git-fixes).\n- sched: Fix stop_one_cpu_nowait() vs hotplug (git fixes (sched)).\n- sched/core: Fix incorrect initialization of the 'burst' parameter in cpu_max_write() (bsc#1226791).\n- sched/fair: Do not balance task to its current running CPU (git fixes (sched)).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- scsi: sd: Update DIX config every time sd_revalidate_disk() is called (bsc#1218570).\n- selftests/bpf: __imm_insn \u0026 __imm_const macro for bpf_misc.h (bsc#1225903).\n- selftests/bpf: Add a selftest for checking subreg equality (bsc#1225903).\n- selftests/bpf: add pre bpf_prog_test_run_opts() callback for test_loader (bsc#1225903).\n- selftests/bpf: add precision propagation tests in the presence of subprogs (bsc#1225903).\n- selftests/bpf: Add pruning test case for bpf_spin_lock (bsc#1225903).\n- selftests/bpf: Check if mark_chain_precision() follows scalar ids (bsc#1225903).\n- selftests/bpf: check if max number of bpf_loop iterations is tracked (bsc#1225903).\n- selftests/bpf: fix __retval() being always ignored (bsc#1225903).\n- selftests/bpf: fix unpriv_disabled check in test_verifier (bsc#1225903).\n- selftests/bpf: make test_align selftest more robust (bsc#1225903).\n- selftests/bpf: populate map_array_ro map for verifier_array_access test (bsc#1225903).\n- selftests/bpf: prog_tests entry point for migrated test_verifier tests (bsc#1225903).\n- selftests/bpf: Report program name on parse_test_spec error (bsc#1225903).\n- selftests/bpf: Support custom per-test flags and multiple expected messages (bsc#1225903).\n- selftests/bpf: test case for callback_depth states pruning logic (bsc#1225903).\n- selftests/bpf: test case for relaxed prunning of active_lock.id (bsc#1225903).\n- selftests/bpf: test cases for regsafe() bug skipping check_id() (bsc#1225903).\n- selftests/bpf: test widening for iterating callbacks (bsc#1225903).\n- selftests/bpf: Tests execution support for test_loader.c (bsc#1225903).\n- selftests/bpf: tests for iterating callbacks (bsc#1225903).\n- selftests/bpf: track string payload offset as scalar in strobemeta (bsc#1225903).\n- selftests/bpf: Unprivileged tests for test_loader.c (bsc#1225903).\n- selftests/bpf: Verify copy_register_state() preserves parent/live fields (bsc#1225903).\n- selftests/bpf: verify states_equal() maintains idmap across all frames (bsc#1225903).\n- selftests/bpf: Verify that check_ids() is used for scalars in regsafe() (bsc#1225903).\n- selftests/sigaltstack: Fix ppc64 GCC build (git-fixes).\n- smb: client: ensure to try all targets when finding nested links (bsc#1224020).\n- smb: client: guarantee refcounted children from parent session (bsc#1224679.\n- soc: ti: wkup_m3_ipc: Send NULL dummy message instead of pointer message (stable-fixes).\n- soundwire: cadence: fix invalid PDI offset (stable-fixes).\n- spi: imx: Do not expect DMA for i.MX{25,35,50,51,53} cspi devices (stable-fixes).\n- spi: mux: set ctlr-\u003ebits_per_word_mask (stable-fixes).\n- spi: stm32: Do not warn about spurious interrupts (git-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228850).\n- sunrpc: avoid soft lockup when transmitting UDP to reachable server (bsc#1225272).\n- sunrpc: Fix gss_free_in_token_pages() (git-fixes).\n- sunrpc: Fix loop termination condition in gss_free_in_token_pages() (git-fixes).\n- sunrpc: fix NFSACL RPC retry on soft mount (git-fixes).\n- sunrpc: return proper error from gss_wrap_req_priv (git-fixes).\n- supported.conf: Add APM X-Gene SoC hardware monitoring driver (bsc#1223265 jsc#PED-8570)\n- supported.conf: mark orangefs as optional We do not support orangefs at all (and it is already marked as such), but since there are no SLE consumers of it, mark it as optional.\n- supported.conf: mark ufs as unsupported UFS is an unsupported filesystem, mark it as such. We still keep it around (not marking as optional), to accommodate any potential migrations from BSD systems.\n- tpm_tis: Resend command to recover from data transfer errors (bsc#1082555).\n- tpm_tis: Use tpm_chip_{start,stop} decoration inside tpm_tis_resume (bsc#1082555).\n- tpm, tpm_tis: Avoid cache incoherency in test for interrupts (bsc#1082555).\n- tpm, tpm_tis: Claim locality before writing interrupt registers (bsc#1082555).\n- tpm, tpm_tis: Claim locality in interrupt handler (bsc#1082555).\n- tpm, tpm_tis: Claim locality when interrupts are reenabled on resume (bsc#1082555).\n- tpm, tpm_tis: correct tpm_tis_flags enumeration values (bsc#1082555).\n- tpm, tpm_tis: Do not skip reset of original interrupt vector (bsc#1082555).\n- tpm, tpm_tis: Only handle supported interrupts (bsc#1082555).\n- tpm, tpm: Implement usage counter for locality (bsc#1082555).\n- tpm: Allow system suspend to continue when TPM suspend fails (bsc#1082555).\n- tpm: Prevent hwrng from activating during resume (bsc#1082555).\n- tracing: Build event generation tests only as modules (git-fixes).\n- tracing/net_sched: NULL pointer dereference in perf_trace_qdisc_reset() (git-fixes).\n- tracing/osnoise: Add OSNOISE_WORKLOAD option (bsc#1228330)\n- tracing/osnoise: Add osnoise/options file (bsc#1228330)\n- tracing/osnoise: Do not follow tracing_cpumask (bsc#1228330)\n- tracing/osnoise: Fix notify new tracing_max_latency (bsc#1228330)\n- tracing/osnoise: Make osnoise_instances static (bsc#1228330)\n- tracing/osnoise: Split workload start from the tracer start (bsc#1228330)\n- tracing/osnoise: Support a list of trace_array *tr (bsc#1228330)\n- tracing/osnoise: Use built-in RCU list checking (bsc#1228330)\n- tracing/timerlat: Notify new max thread latency (bsc#1228330)\n- tty: mcf: MCF54418 has 10 UARTS (git-fixes).\n- usb-storage: alauda: Check whether the media is initialized (git-fixes).\n- usb: Add USB_QUIRK_NO_SET_INTF quirk for START BP-850k (stable-fixes).\n- usb: atm: cxacru: fix endpoint checking in cxacru_bind() (git-fixes).\n- usb: cdns3: allocate TX FIFO size according to composite EP number (git-fixes).\n- usb: cdns3: fix incorrect calculation of ep_buf_size when more than one config (git-fixes).\n- usb: cdns3: fix iso transfer error when mult is not zero (git-fixes).\n- usb: cdns3: improve handling of unaligned address case (git-fixes).\n- usb: cdns3: optimize OUT transfer by copying only actual received data (git-fixes).\n- usb: cdns3: skip set TRB_IOC when usb_request: no_interrupt is true (git-fixes).\n- usb: class: cdc-wdm: Fix CPU lockup caused by excessive log messages (git-fixes).\n- usb: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor (git-fixes).\n- usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock (git-fixes).\n- usb: dwc3: gadget: Do not delay End Transfer on delayed_status (git-fixes).\n- usb: dwc3: gadget: Force sending delayed status during soft disconnect (git-fixes).\n- usb: dwc3: gadget: Synchronize IRQ between soft connect/disconnect (git-fixes).\n- usb: fotg210-hcd: delete an incorrect bounds test (git-fixes).\n- usb: gadget: call usb_gadget_check_config() to verify UDC capability (git-fixes).\n- usb: gadget: configfs: Prevent OOB read/write in usb_string_copy() (stable-fixes).\n- usb: gadget: printer: fix races against disable (git-fixes).\n- usb: gadget: printer: SS+ support (stable-fixes).\n- usb: misc: uss720: check for incompatible versions of the Belkin F5U002 (stable-fixes).\n- usb: musb: da8xx: fix a resource leak in probe() (git-fixes).\n- usb: serial: mos7840: fix crash on resume (git-fixes).\n- usb: serial: option: add Fibocom FM350-GL (stable-fixes).\n- usb: serial: option: add Netprisma LCUK54 series modules (stable-fixes).\n- usb: serial: option: add Rolling RW350-GL variants (stable-fixes).\n- usb: serial: option: add support for Foxconn T99W651 (stable-fixes).\n- usb: serial: option: add Telit FN912 rmnet compositions (stable-fixes).\n- usb: serial: option: add Telit generic core-dump composition (stable-fixes).\n- usb: typec: tcpm: clear pd_event queue in PORT_RESET (git-fixes).\n- usb: typec: tcpm: fix use-after-free case in tcpm_register_source_caps (git-fixes).\n- usb: typec: tcpm: Ignore received Hard Reset in TOGGLING state (git-fixes).\n- usb: typec: ucsi: Ack also failed Get Error commands (git-fixes).\n- usb: typec: ucsi: Never send a lone connector change ack (git-fixes).\n- usb: xen-hcd: Traverse host/ when CONFIG_USB_XEN_HCD is selected (git-fixes).\n- usb: xhci-plat: Do not include xhci.h (git-fixes).\n- usb: xhci-plat: fix legacy PHY double init (git-fixes).\n- usb: xhci: address off-by-one in xhci_num_trbs_free() (git-fixes).\n- usb: xhci: Implement xhci_handshake_check_state() helper (git-fixes).\n- usb: xhci: improve debug message in xhci_ring_expansion_needed() (git-fixes).\n- watchdog: bd9576_wdt: switch to using devm_fwnode_gpiod_get() (stable-fixes).\n- watchdog: bd9576: Drop 'always-running' property (git-fixes).\n- wifi: ath11k: fix wrong handling of CCMP256 and GCMP ciphers (git-fixes).\n- wifi: brcmsmac: LCN PHY code is used for BCM4313 2G-only device (git-fixes).\n- wifi: cfg80211: fix the order of arguments for trace events of the tx_rx_evt class (stable-fixes).\n- wifi: cfg80211: fix typo in cfg80211_calculate_bitrate_he() (git-fixes).\n- wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he() (git-fixes).\n- wifi: cfg80211: Lock wiphy in cfg80211_get_station (git-fixes).\n- wifi: cfg80211: pmsr: use correct nla_get_uX functions (git-fixes).\n- wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values (git-fixes).\n- wifi: cfg80211: wext: add extra SIOCSIWSCAN data check (stable-fixes).\n- wifi: iwlwifi: dbg_ini: move iwl_dbg_tlv_free outside of debugfs ifdef (git-fixes).\n- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids (git-fixes).\n- wifi: iwlwifi: mvm: d3: fix WoWLAN command version lookup (stable-fixes).\n- wifi: iwlwifi: mvm: do not read past the mfuart notifcation (git-fixes).\n- wifi: iwlwifi: mvm: Handle BIGTK cipher in kek_kck cmd (stable-fixes).\n- wifi: iwlwifi: mvm: properly set 6 GHz channel direct probe option (stable-fixes).\n- wifi: iwlwifi: mvm: revert gen2 TX A-MPDU size to 64 (git-fixes).\n- wifi: mac80211: correctly parse Spatial Reuse Parameter Set element (git-fixes).\n- wifi: mac80211: disable softirqs for queued frame handling (git-fixes).\n- wifi: mac80211: Fix deadlock in ieee80211_sta_ps_deliver_wakeup() (git-fixes).\n- wifi: mac80211: fix UBSAN noise in ieee80211_prep_hw_scan() (stable-fixes).\n- wifi: mac80211: handle tasklet frames before stopping (stable-fixes).\n- wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects (git-fixes).\n- wifi: mac80211: mesh: init nonpeer_pm to active by default in mesh sdata (stable-fixes).\n- wifi: mt76: replace skb_put with skb_put_zero (stable-fixes).\n- wifi: mwifiex: Fix interface type change (git-fixes).\n- wifi: rtl8xxxu: Fix the TX power of RTL8192CU, RTL8723AU (stable-fixes).\n- wifi: rtlwifi: rtl8192de: Fix endianness issue in RX path (stable-fixes).\n- wifi: rtlwifi: rtl8192de: Fix low speed with WPA3-SAE (stable-fixes).\n- wifi: rtw89: Fix array index mistake in rtw89_sta_info_get_iter() (git-fixes).\n- wifi: wilc1000: fix ies_len type in connect path (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x.509: Fix the parser of extended key usage for length (bsc#1218820).\n- x86: Stop using weak symbols for __iowrite32_copy() (bsc#1226502)\n- x86/amd_nb: Use Family 19h Models 60h-7Fh Function 4 IDs (git-fixes).\n- x86/apic: Force native_apic_mem_read() to use the MOV instruction (git-fixes).\n- x86/bhi: Avoid warning in #DB handler due to BHI mitigation (git-fixes).\n- x86/bugs: Remove default case for fully switched enums (bsc#1227900).\n- x86/fpu: Fix AMD X86_BUG_FXSAVE_LEAK fixup (git-fixes).\n- x86/ibt,ftrace: Search for __fentry__ location (git-fixes).\n- x86/Kconfig: Transmeta Crusoe is CPU family 5, not 6 (git-fixes).\n- x86/mce: Dynamically size space for machine check records (bsc#1222241).\n- x86/mm: Allow guest.enc_status_change_prepare() to fail (git-fixes).\n- x86/mm: Fix enc_status_change_finish_noop() (git-fixes).\n- x86/purgatory: Switch to the position-independent small code model (git-fixes).\n- x86/srso: Move retbleed IBPB check into existing 'has_microcode' code block (bsc#1227900).\n- x86/srso: Remove 'pred_cmd' label (bsc#1227900).\n- x86/tdx: Fix race between set_memory_encrypted() and load_unaligned_zeropad() (git-fixes).\n- x86/tsc: Trust initial offset in architectural TSC-adjust MSRs (bsc#1222015 bsc#1226962).\n- xfs: Add cond_resched to block unmap range and reflink remap path (bsc#1228226).\n- xfs: make sure sb_fdblocks is non-negative (bsc#1225419).\n- xhci: Apply broken streams quirk to Etron EJ188 xHCI host (stable-fixes).\n- xhci: Apply reset resume quirk to Etron EJ188 xHCI host (stable-fixes).\n- xhci: Fix failure to detect ring expansion need (git-fixes).\n- xhci: fix matching completion events with TDs (git-fixes).\n- xhci: Fix transfer ring expansion size calculation (git-fixes).\n- xhci: Handle TD clearing for multiple streams case (git-fixes).\n- xhci: remove unused stream_id parameter from xhci_handle_halted_endpoint() (git-fixes).\n- xhci: restre deleted trb fields for tracing (git-fixes).\n- xhci: retry Stop Endpoint on buggy NEC controllers (git-fixes).\n- xhci: Set correct transferred length for cancelled bulk transfers (stable-fixes).\n- xhci: Simplify event ring dequeue pointer update for port change events (git-fixes).\n- xhci: simplify event ring dequeue tracking for transfer events (git-fixes).\n- xhci: Stop unnecessary tracking of free trbs in a ring (git-fixes).\n- xhci: update event ring dequeue pointer position to controller correctly (git-fixes).\n","status":"published","published":"2024-08-16T07:05:17Z","modified":"2026-02-04T03:31:08.424908Z","updated_at":"2026-11-02T15:53:55.136363Z"},{"id":"SUSE-SU-2024:2947-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-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).\n- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).\n- CVE-2021-47186: ipc: check for null after calling kmemdup (bsc#1222702).\n- CVE-2021-47546: Kabi fix for ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).\n- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp-\u003ephy' may be out of bound (bsc#1225505).\n- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).\n- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).\n- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).\n- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).\n- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).\n- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571)\n- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len (bsc#1226555).\n- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).\n- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)\n- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).\n- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071)\n- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).\n- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).\n- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869)\n- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).\n- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).\n- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).\n- CVE-2023-52812: drm/amd: check num of link levels when update pcie param (bsc#1225564).\n- CVE-2023-52857: drm/mediatek: Fix coverity issue with unintentional integer overflow (bsc#1225581).\n- CVE-2023-52863: hwmon: (axi-fan-control) Fix possible NULL pointer dereference (bsc#1225586).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).\n- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).\n- CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647).\n- CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2 (bsc#1221656).\n- CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes (bsc#1221659).\n- CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654).\n- CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator' in (bsc#1222323)\n- CVE-2024-26663: tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() (bsc#1222326).\n- CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error (bsc#1222328).\n- CVE-2024-26802: stmmac: Clear variable when destroying workqueue (bsc#1222799).\n- CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021).\n- CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del (bsc#1223652).\n- CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple (bsc#1223806).\n- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)\n- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)\n- CVE-2024-27025: nbd: null check for nla_nest_start (bsc#1223778)\n- CVE-2024-27065: netfilter: nf_tables: do not compare internal table flags on updates (bsc#1223836).\n- CVE-2024-27402: phonet/pep: fix racy skb_queue_empty() use (bsc#1224414).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-35805: dm snapshot: fix lockup in dm_exception_table_exit (bsc#1224743).\n- CVE-2024-35819: soc: fsl: qbman: Use raw spinlock for cgr_lock (bsc#1224683).\n- CVE-2024-35837: net: mvpp2: clear BM pool before initialization (bsc#1224500).\n- CVE-2024-35853: mlxsw: spectrum_acl_tcam: Fix memory leak during rehash (bsc#1224604).\n- CVE-2024-35889: idpf: fix kernel panic on unknown packet types (bsc#1224517).\n- CVE-2024-35890: gro: fix ownership transfer (bsc#1224516).\n- CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)\n- CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)\n- CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700)\n- CVE-2024-35961: net/mlx5: Restore mistakenly dropped parts in register devlink flow (bsc#1224585).\n- CVE-2024-35995: ACPI: CPPC: Fix access width used for PCC registers (bsc#1224557).\n- CVE-2024-36000: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (bsc#1224548).\n- CVE-2024-36004: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue (bsc#1224545)\n- CVE-2024-36901: ipv6: prevent NULL dereference in ip6_output() (bsc#1225711)\n- CVE-2024-36902: ipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action() (bsc#1225719).\n- CVE-2024-36909: Drivers: hv: vmbus: Do not free ring buffers that couldn't be re-encrypted (bsc#1225744).\n- CVE-2024-36910: uio_hv_generic: Do not free decrypted memory (bsc#1225717).\n- CVE-2024-36911: hv_netvsc: Do not free decrypted memory (bsc#1225745).\n- CVE-2024-36912: Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl (bsc#1225752).\n- CVE-2024-36913: Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails (bsc#1225753).\n- CVE-2024-36914: drm/amd/display: Skip on writeback when it's not applicable (bsc#1225757).\n- CVE-2024-36919: scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload (bsc#1225767).\n- CVE-2024-36923: fs/9p: fix uninitialized values during inode evict (bsc#1225815).\n- CVE-2024-36939: nfs: Handle error of rpc_proc_register() in nfs_net_init() (bsc#1225838).\n- CVE-2024-36946: phonet: fix rtm_phonet_notify() skb allocation (bsc#1225851).\n- CVE-2024-36974: net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP (bsc#1226519).\n- CVE-2024-38555: net/mlx5: Discard command completions in internal error (bsc#1226607).\n- CVE-2024-38558: net: openvswitch: fix overwriting ct original tuple for ICMPv6 (bsc#1226783).\n- CVE-2024-38570: gfs2: Fix potential glock use-after-free on unmount (bsc#1226775).\n- CVE-2024-38586: r8169: Fix possible ring buffer corruption on fragmented Tx packets (bsc#1226750).\n- CVE-2024-38598: md: fix resync softlockup when bitmap size is less than array size (bsc#1226757).\n- CVE-2024-38628: usb: gadget: u_audio: Fix race condition use of controls after free during gadget unbind (bsc#1226911).\n- CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).\n- CVE-2024-39371: io_uring: check for non-NULL file pointer in io_file_can_poll() (bsc#1226990).\n- CVE-2024-39463: 9p: add missing locking around taking dentry fid list (bsc#1227090).\n- CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).\n- CVE-2024-39482: bcache: fix variable length array abuse in btree_iter (bsc#1227447).\n- CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)\n- CVE-2024-39490: ipv6: sr: fix missing sk_buff release in seg6_input_core (bsc#1227626).\n- CVE-2024-39493: crypto: qat - Fix ADF_DEV_RESET_SYNC memory leak (bsc#1227620).\n- CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).\n- CVE-2024-39497: drm/shmem-helper: Fix BUG_ON() on mmap(PROT_WRITE, MAP_PRIVATE) (bsc#1227722)\n- CVE-2024-39502: ionic: fix use after netif_napi_del() (bsc#1227755).\n- CVE-2024-39506: liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).\n- CVE-2024-39508: io_uring/io-wq: Use set_bit() and test_bit() at worker-\u003eflags (bsc#1227732).\n- CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).\n- CVE-2024-40906: net/mlx5: Always stop health timer during driver removal (bsc#1227763).\n- CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).\n- CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).\n- CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).\n- CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).\n- CVE-2024-40937: gve: Clear napi-\u003eskb before dev_kfree_skb_any() (bsc#1227836).\n- CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).\n- CVE-2024-40943: ocfs2: fix races between hole punching and AIO+DIO (bsc#1227849).\n- CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).\n- CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).\n- CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).\n- CVE-2024-40967: serial: imx: Introduce timeout when waiting on transmitter empty (bsc#1227891).\n- CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).\n- CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).\n- CVE-2024-40977: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery (bsc#1227950).\n- CVE-2024-40982: ssb: Fix potential NULL pointer dereference in ssb_device_uevent() (bsc#1227865).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40998: ext4: fix uninitialized ratelimit_state-\u003elock access in __ext4_fill_super() (bsc#1227866).\n- CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).\n- CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).\n- CVE-2024-41009: selftests/bpf: Add more ring buffer test coverage (bsc#1228020).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).\n- CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41016: ocfs2: add bounds checking to ocfs2_xattr_find_entry() (bsc#1228410).\n- CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518)\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520)\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565)\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41059: hfsplus: fix uninit-value in copy_name (bsc#1228561).\n- CVE-2024-41063: Bluetooth: hci_core: cancel all works upon hci_unregister_dev() (bsc#1228580)\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41066: ibmvnic: Add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41071: wifi: mac80211: Avoid address calculations via out of bounds array indexing (bsc#1228625).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617)\n- CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).\n- CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470)\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591)\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705)\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743)\n- CVE-2024-42161: bpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723)\n- CVE-2024-42230: powerpc/pseries: Fix scv instruction crash with kexec (bsc#1194869).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: Abort address space access upon error (stable-fixes).\n- ACPI: EC: Avoid returning AE_OK on errors in address space handler (stable-fixes).\n- ACPI: processor_idle: Fix invalid comparison with insertion sort for latency (git-fixes).\n- ACPI: video: Add backlight=native quirk for Lenovo Slim 7 16ARH7 (stable-fixes).\n- ACPI: x86: Force StorageD3Enable on more products (stable-fixes).\n- ACPI: x86: utils: Add Picasso to the list for forcing StorageD3Enable (stable-fixes).\n- ALSA: dmaengine_pcm: terminate dmaengine before synchronize (stable-fixes).\n- ALSA: dmaengine: Synchronize dma channel after drop() (stable-fixes).\n- ALSA: emux: improve patch ioctl data validation (stable-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: hda/realtek: Add more codec ID to no shutup pins list (stable-fixes).\n- ALSA: hda/realtek: add quirk for Clevo V5[46]0TU (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic of JP-IK LEAP W502 with ALC897 (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo SU C1400 (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP 250 G7 (stable-fixes).\n- ALSA: hda/realtek: fix mute/micmute LEDs do not work for EliteBook 645/665 G11 (stable-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book Pro 360 (stable-fixes).\n- ALSA: hda/realtek: Limit mic boost on VAIO PRO PX (stable-fixes).\n- ALSA: hda/relatek: Enable Mute LED on HP Laptop 15-gw0xxx (stable-fixes).\n- ALSA: pcm_dmaengine: Do not synchronize DMA channel when DMA is paused (git-fixes).\n- ALSA: usb-audio: Add a quirk for Sonix HD USB Camera (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Fix microphone sound on HD webcam (stable-fixes).\n- ALSA: usb-audio: Move HD Webcam quirk to the right place (git-fixes).\n- arm64: dts: allwinner: Pine H64: correctly remove reg_gmac_3v3 (git-fixes)\n- arm64: dts: hi3798cv200: fix the size of GICR (git-fixes)\n- arm64: dts: imx8qm-mek: fix gpio number for reg_usdhc2_vmmc (git-fixes)\n- arm64: dts: microchip: sparx5: fix mdio reg (git-fixes)\n- arm64: dts: rockchip: Add enable-strobe-pulldown to emmc phy on ROCK (git-fixes)\n- arm64: dts: rockchip: Add sound-dai-cells for RK3368 (git-fixes)\n- arm64: dts: rockchip: fix PMIC interrupt pin on ROCK Pi E (git-fixes)\n- arm64/io: add constant-argument check (bsc#1226502 git-fixes)\n- arm64/io: Provide a WC friendly __iowriteXX_copy() (bsc#1226502)\n- arm64: tegra: Correct Tegra132 I2C alias (git-fixes)\n- ASoC: amd: Adjust error handling in case of absent codec device (git-fixes).\n- ASoC: max98088: Check for clk_prepare_enable() error (git-fixes).\n- ASoC: ti: davinci-mcasp: Set min period size using FIFO config (stable-fixes).\n- ASoC: ti: omap-hdmi: Fix too long driver name (stable-fixes).\n- batman-adv: bypass empty buckets in batadv_purge_orig_ref() (stable-fixes).\n- blk-cgroup: dropping parent refcount after pd_free_fn() is done (bsc#1224573).\n- block: do not add partitions if GD_SUPPRESS_PART_SCAN is set (bsc#1227162).\n- block, loop: support partitions without scanning (bsc#1227162).\n- Bluetooth: ath3k: Fix multiple issues reported by checkpatch.pl (stable-fixes).\n- Bluetooth: btqca: use le32_to_cpu for ver.soc_id (stable-fixes).\n- Bluetooth: hci_core: cancel all works upon hci_unregister_dev() (stable-fixes).\n- Bluetooth: hci_qca: mark OF related data as maybe unused (stable-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot (git-fixes).\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf: aggressively forget precise markings during state checkpointing (bsc#1225903).\n- bpf: allow precision tracking for programs with subprogs (bsc#1225903).\n- bpf: check bpf_func_state-\u003ecallback_depth when pruning states (bsc#1225903).\n- bpf: clean up visit_insn()'s instruction processing (bsc#1225903).\n- bpf: correct loop detection for iterators convergence (bsc#1225903).\n- bpf: encapsulate precision backtracking bookkeeping (bsc#1225903).\n- bpf: ensure state checkpointing at iter_next() call sites (bsc#1225903).\n- bpf: exact states comparison for iterator convergence checks (bsc#1225903).\n- bpf: extract __check_reg_arg() utility function (bsc#1225903).\n- bpf: extract same_callsites() as utility function (bsc#1225903).\n- bpf: extract setup_func_entry() utility function (bsc#1225903).\n- bpf: fix calculation of subseq_idx during precision backtracking (bsc#1225903).\n- bpf: fix mark_all_scalars_precise use in mark_chain_precision (bsc#1225903).\n- bpf: Fix memory leaks in __check_func_call (bsc#1225903).\n- bpf: fix propagate_precision() logic for inner frames (bsc#1225903).\n- bpf: fix regs_exact() logic in regsafe() to remap IDs correctly (bsc#1225903).\n- bpf: Fix to preserve reg parent/live fields when copying range info (bsc#1225903).\n- bpf: generalize MAYBE_NULL vs non-MAYBE_NULL rule (bsc#1225903).\n- bpf: improve precision backtrack logging (bsc#1225903).\n- bpf: Improve verifier u32 scalar equality checking (bsc#1225903).\n- bpf: keep track of max number of bpf_loop callback iterations (bsc#1225903).\n- bpf: maintain bitmasks across all active frames in __mark_chain_precision (bsc#1225903).\n- bpf: mark relevant stack slots scratched for register read instructions (bsc#1225903).\n- bpf: move explored_state() closer to the beginning of verifier.c (bsc#1225903).\n- bpf: perform byte-by-byte comparison only when necessary in regsafe() (bsc#1225903).\n- bpf: print full verifier states on infinite loop detection (bsc#1225903).\n- bpf: regsafe() must not skip check_ids() (bsc#1225903).\n- bpf: reject non-exact register type matches in regsafe() (bsc#1225903).\n- bpf: Remove unused insn_cnt argument from visit_[func_call_]insn() (bsc#1225903).\n- bpf: reorganize struct bpf_reg_state fields (bsc#1225903).\n- bpf: Skip invalid kfunc call in backtrack_insn (bsc#1225903).\n- bpf: states_equal() must build idmap for all function frames (bsc#1225903).\n- bpf: stop setting precise in current state (bsc#1225903).\n- bpf: support precision propagation in the presence of subprogs (bsc#1225903).\n- bpf: take into account liveness when propagating precision (bsc#1225903).\n- bpf: teach refsafe() to take into account ID remapping (bsc#1225903).\n- bpf: unconditionally reset backtrack_state masks on global func exit (bsc#1225903).\n- bpf: use check_ids() for active_lock comparison (bsc#1225903).\n- bpf: Use scalar ids in mark_chain_precision() (bsc#1225903).\n- bpf: verify callbacks as if they are called unknown number of times (bsc#1225903).\n- bpf: Verify scalar ids mapping in regsafe() using check_ids() (bsc#1225903).\n- bpf: widening for callback iterators (bsc#1225903).\n- btrfs: add device major-minor info in the struct btrfs_device (bsc#1227162).\n- btrfs: harden identification of a stale device (bsc#1227162).\n- btrfs: match stale devices by dev_t (bsc#1227162).\n- btrfs: remove the cross file system checks from remap (bsc#1227157).\n- btrfs: use dev_t to match device in device_matched (bsc#1227162).\n- btrfs: validate device maj:min during open (bsc#1227162).\n- bytcr_rt5640 : inverse jack detect for Archos 101 cesium (stable-fixes).\n- cachefiles: add output string to cachefiles_obj_[get|put]_ondemand_fd (git-fixes).\n- can: kvaser_usb: Explicitly initialize family in leafimx driver_info struct (git-fixes).\n- can: kvaser_usb: fix return value for hif_usb_send_regout (stable-fixes).\n- ceph: fix incorrect kmalloc size of pagevec mempool (bsc#1228418).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- crypto: aead,cipher - zeroize key buffer after use (stable-fixes).\n- crypto: ecdh - explicitly zeroize private_key (stable-fixes).\n- crypto: ecdsa - Fix the public key format description (git-fixes).\n- crypto: hisilicon/sec - Fix memory leak for sec resource release (stable-fixes).\n- csky: ftrace: Drop duplicate implementation of arch_check_ftrace_location() (git-fixes).\n- decompress_bunzip2: fix rare decompression failure (git-fixes).\n- devres: Fix devm_krealloc() wasting memory (git-fixes).\n- devres: Fix memory leakage caused by driver API devm_free_percpu() (git-fixes).\n- dma: fix call order in dmam_free_coherent (git-fixes).\n- docs: crypto: async-tx-api: fix broken code example (git-fixes).\n- docs: Fix formatting of literal sections in fanotify docs (stable-fixes).\n- drm/amd/amdgpu: Fix style errors in amdgpu_drv.c \u0026 amdgpu_device.c (stable-fixes).\n- drm/amd/display: Account for cursor prefetch BW in DML1 mode support (stable-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Check index msg_id before read or write (stable-fixes).\n- drm/amd/display: Check pipe offset before setting vblank (stable-fixes).\n- drm/amd/display: Skip finding free audio for unknown engine_id (stable-fixes).\n- drm/amdgpu/atomfirmware: fix parsing of vram_info (stable-fixes).\n- drm/amdgpu/atomfirmware: silence UBSAN warning (stable-fixes).\n- drm/amdgpu: avoid using null object of framebuffer (stable-fixes).\n- drm/amdgpu: Check if NBIO funcs are NULL in amdgpu_device_baco_exit (git-fixes).\n- drm/amdgpu: Fix pci state save during mode-1 reset (git-fixes).\n- drm/amdgpu: Fix signedness bug in sdma_v4_0_process_trap_irq() (git-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warnings (stable-fixes).\n- drm/amdgpu: Initialize timestamp for some legacy SOCs (stable-fixes).\n- drm/amdgpu: Remove GC HW IP 9.3.0 from noretry=1 (git-fixes).\n- drm/amd/pm: Fix aldebaran pcie speed reporting (git-fixes).\n- drm/amd/pm: remove logically dead code for renoir (git-fixes).\n- drm/dp_mst: Fix all mstb marked as not probed after suspend/resume (git-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/etnaviv: fix DMA direction handling for cached RW buffers (git-fixes).\n- drm/gma500: fix null pointer dereference in cdv_intel_lvds_get_modes (git-fixes).\n- drm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes (git-fixes).\n- drm/i915/gt: Do not consider preemption during execlists_dequeue for gen8 (git-fixes).\n- drm/lima: fix shared irq handling on driver remove (stable-fixes).\n- drm/lima: Mark simple_ondemand governor as softdep (git-fixes).\n- drm/mediatek: Add OVL compatible name for MT8195 (git-fixes).\n- drm/meson: fix canvas release in bind function (git-fixes).\n- drm/mgag200: Bind I2C lifetime to DRM device (git-fixes).\n- drm/mgag200: Set DDC timeout in milliseconds (git-fixes).\n- drm/mipi-dsi: Fix mipi_dsi_dcs_write_seq() macro definition format (stable-fixes).\n- drm/mipi-dsi: Fix theoretical int overflow in mipi_dsi_dcs_write_seq() (git-fixes).\n- drm/msm/dpu: drop validity checks for clear_pending_flush() ctl op (git-fixes).\n- drm/msm/mdp5: Remove MDP_CAP_SRC_SPLIT from msm8x53_config (git-fixes).\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes (stable-fixes).\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes (stable-fixes).\n- drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes (git-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: boe-tv101wum-nl6: Check for errors on the NOP in prepare() (git-fixes).\n- drm/panel: boe-tv101wum-nl6: If prepare fails, disable GPIO before regulators (git-fixes).\n- drm/panel: ilitek-ili9881c: Fix warning with GPIO controllers that sleep (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Valve Galileo (stable-fixes).\n- drm/panfrost: Mark simple_ondemand governor as softdep (git-fixes).\n- drm/qxl: Add check for drm_cvt_mode (git-fixes).\n- drm/radeon: check bo_va-\u003ebo is non-NULL before using it (stable-fixes).\n- drm/radeon/radeon_display: Decrease the size of allocated memory (stable-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency (stable-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- eeprom: digsy_mtc: Fix 93xx46 driver probe failure (git-fixes).\n- exfat: check if cluster num is valid (git-fixes).\n- exfat: simplify is_valid_cluster() (git-fixes).\n- filelock: add a new locks_inode_context accessor function (git-fixes).\n- firmware: cs_dsp: Fix overflow checking of wmfw header (git-fixes).\n- firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers (git-fixes).\n- firmware: cs_dsp: Return error if block header overflows file (git-fixes).\n- firmware: cs_dsp: Use strnlen() on name fields in V1 wmfw files (git-fixes).\n- firmware: cs_dsp: Validate payload length before processing block (git-fixes).\n- firmware: dmi: Stop decoding on broken entry (stable-fixes).\n- firmware: turris-mox-rwtm: Do not complete if there are no waiters (git-fixes).\n- firmware: turris-mox-rwtm: Fix checking return value of wait_for_completion_timeout() (git-fixes).\n- firmware: turris-mox-rwtm: Initialize completion before mailbox (git-fixes).\n- fix build warning\n- fs: allow cross-vfsmount reflink/dedupe (bsc#1227157).\n- ftrace: Fix possible use-after-free issue in ftrace_location() (git-fixes).\n- fuse: verify {g,u}id mount options correctly (bsc#1228191).\n- gpio: mc33880: Convert comma to semicolon (git-fixes).\n- hfsplus: fix to avoid false alarm of circular locking (git-fixes).\n- hfsplus: fix uninit-value in copy_name (git-fixes).\n- HID: Add quirk for Logitech Casa touchpad (stable-fixes).\n- HID: wacom: Modify pen IDs (git-fixes).\n- hpet: Support 32-bit userspace (git-fixes).\n- hwmon: (adt7475) Fix default duty on fan is disabled (git-fixes).\n- hwmon: (max6697) Fix swapped temp{1,8} critical alarms (git-fixes).\n- hwmon: (max6697) Fix underflow when writing limit attributes (git-fixes).\n- i2c: mark HostNotify target address as used (git-fixes).\n- i2c: rcar: bring hardware to known state when probing (git-fixes).\n- i2c: tegra: Fix failure during probe deferral cleanup (git-fixes)\n- i2c: tegra: Share same DMA channel for RX and TX (bsc#1227661)\n- i2c: testunit: avoid re-issued work after read message (git-fixes).\n- i2c: testunit: correct Kconfig description (git-fixes).\n- Input: elan_i2c - do not leave interrupt disabled on suspend failure (git-fixes).\n- Input: elantech - fix touchpad state on resume for Lenovo N24 (stable-fixes).\n- Input: ff-core - prefer struct_size over open coded arithmetic (stable-fixes).\n- Input: qt1050 - handle CHIP_ID reading error (git-fixes).\n- Input: silead - Always support 10 fingers (stable-fixes).\n- intel_th: pci: Add Granite Rapids SOC support (stable-fixes).\n- intel_th: pci: Add Granite Rapids support (stable-fixes).\n- intel_th: pci: Add Lunar Lake support (stable-fixes).\n- intel_th: pci: Add Meteor Lake-S support (stable-fixes).\n- intel_th: pci: Add Sapphire Rapids SOC support (stable-fixes).\n- iommu/arm-smmu-v3: Free MSIs in case of ENOMEM (git-fixes).\n- ionic: clean interrupt before enabling queue to avoid credit race (git-fixes).\n- jffs2: Fix potential illegal address access in jffs2_free_inode (git-fixes).\n- jfs: Fix array-index-out-of-bounds in diFree (git-fixes).\n- jfs: xattr: fix buffer overflow for invalid xattr (bsc#1227383).\n- kABI: bpf: bpf_reg_state reorganization kABI workaround (bsc#1225903).\n- kABI: bpf: callback fixes kABI workaround (bsc#1225903).\n- kABI: bpf: struct bpf_{idmap,idset} kABI workaround (bsc#1225903).\n- kABI: bpf: tmp_str_buf kABI workaround (bsc#1225903).\n- kABI: rtas: Workaround false positive due to lost definition (bsc#1227487).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severities: Ignore tpm_tis_core_init (bsc#1082555).\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kabi: Use __iowriteXX_copy_inlined for in-kernel modules (bsc#1226502)\n- kernel-binary: vdso: Own module_dir\n- kernel/sched: Remove dl_boosted flag comment (git fixes (sched)).\n- knfsd: LOOKUP can return an illegal error value (git-fixes).\n- kobject_uevent: Fix OOB access within zap_modalias_env() (git-fixes).\n- kprobes: Make arch_check_ftrace_location static (git-fixes).\n- KVM: nVMX: Clear EXIT_QUALIFICATION when injecting an EPT Misconfig (git-fixes).\n- KVM: PPC: Book3S HV: Fix 'rm_exit' entry in debugfs timings (bsc#1194869).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV Nested: L2 LPCR should inherit L1 LPES setting (bsc#1194869).\n- KVM: PPC: Book3S HV: remove extraneous asterisk from rm_host_ipi_action() comment (bsc#1194869).\n- KVM: PPC: Book3S: Suppress failed alloc warning in H_COPY_TOFROM_GUEST (bsc#1194869).\n- KVM: PPC: Book3S: Suppress warnings when allocating too big memory slots (bsc#1194869).\n- KVM: s390: fix LPSWEY handling (bsc#1227635 git-fixes).\n- KVM: SVM: Process ICR on AVIC IPI delivery failure due to invalid target (git-fixes).\n- KVM: VMX: Report up-to-date exit qualification to userspace (git-fixes).\n- KVM: x86: Add IBPB_BRTYPE support (bsc#1228079).\n- KVM: x86: Always sync PIR to IRR prior to scanning I/O APIC routes (git-fixes).\n- KVM: x86: Bail from kvm_recalculate_phys_map() if x2APIC ID is out-of-bounds (git-fixes).\n- KVM: x86: Disable APIC logical map if logical ID covers multiple MDAs (git-fixes).\n- KVM: x86: Disable APIC logical map if vCPUs are aliased in logical mode (git-fixes).\n- KVM: x86: Do not advertise guest.MAXPHYADDR as host.MAXPHYADDR in CPUID (git-fixes).\n- KVM: x86: Explicitly skip optimized logical map setup if vCPU's LDR==0 (git-fixes).\n- KVM: x86: Explicitly track all possibilities for APIC map's logical modes (git-fixes).\n- KVM: x86: Fix broken debugregs ABI for 32 bit kernels (git-fixes).\n- KVM: x86: Fix KVM_GET_MSRS stack info leak (git-fixes).\n- KVM: x86: Honor architectural behavior for aliased 8-bit APIC IDs (git-fixes).\n- KVM: x86: Purge 'highest ISR' cache when updating APICv state (git-fixes).\n- KVM: x86: Save/restore all NMIs when multiple NMIs are pending (git-fixes).\n- KVM: x86: Skip redundant x2APIC logical mode optimized cluster setup (git-fixes).\n- leds: ss4200: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- leds: triggers: Flush pending brightness before activating trigger (git-fixes).\n- leds: trigger: Unregister sysfs attributes before calling deactivate() (git-fixes).\n- libceph: fix race between delayed_work() and ceph_monc_stop() (bsc#1228190).\n- lib: objagg: Fix general protection fault (git-fixes).\n- lib: objagg: Fix spelling (git-fixes).\n- lib: test_objagg: Fix spelling (git-fixes).\n- lockd: set missing fl_flags field when retrieving args (git-fixes).\n- lockd: use locks_inode_context helper (git-fixes).\n- Make AMD_HSMP=m and mark it unsupported in supported.conf (jsc#PED-8582)\n- media: dvb: as102-fe: Fix as10x_register_addr packing (stable-fixes).\n- media: dvbdev: Initialize sbuf (stable-fixes).\n- media: dvb-frontends: tda10048: Fix integer overflow (stable-fixes).\n- media: dvb-frontends: tda18271c2dd: Remove casting during div (stable-fixes).\n- media: dvb-usb: dib0700_devices: Add missing release_firmware() (stable-fixes).\n- media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control() (git-fixes).\n- media: dw2102: Do not translate i2c read into write (stable-fixes).\n- media: dw2102: fix a potential buffer overflow (git-fixes).\n- media: imon: Fix race getting ictx-\u003elock (git-fixes).\n- media: s2255: Use refcount_t instead of atomic_t for num_channels (stable-fixes).\n- media: uvcvideo: Fix integer overflow calculating timestamp (git-fixes).\n- media: uvcvideo: Override default flags (git-fixes).\n- media: venus: fix use after free in vdec_close (git-fixes).\n- media: venus: flush all buffers in output plane streamoff (git-fixes).\n- mei: demote client disconnect warning on suspend to debug (stable-fixes).\n- mfd: omap-usb-tll: Use struct_size to allocate tll (git-fixes).\n- mtd: partitions: redboot: Added conversion of operands to a larger type (stable-fixes).\n- net/dcb: check for detached device before executing callbacks (bsc#1215587).\n- netfilter: conntrack: ignore overly delayed tcp packets (bsc#1223180).\n- netfilter: conntrack: prepare tcp_in_window for ternary return value (bsc#1223180).\n- netfilter: conntrack: remove pr_debug callsites from tcp tracker (bsc#1223180).\n- netfilter: conntrack: work around exceeded receive window (bsc#1223180).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- net: mana: Fix possible double free in error handling path (git-fixes).\n- net: mana: Fix the extra HZ in mana_hwc_send_request (git-fixes).\n- net: usb: qmi_wwan: add Telit FN912 compositions (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- nfc/nci: Add the inconsistency check between the input data length and count (stable-fixes).\n- NFSD: Add an nfsd_file_fsync tracepoint (git-fixes).\n- NFSD: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection (git-fixes).\n- nfsd: Add errno mapping for EREMOTEIO (git-fixes).\n- NFSD: Add nfsd_file_lru_dispose_list() helper (git-fixes).\n- nfsd: add some comments to nfsd_file_do_acquire (git-fixes).\n- nfsd: allow nfsd_file_get to sanely handle a NULL pointer (git-fixes).\n- nfsd: allow reaping files still under writeback (git-fixes).\n- NFSD: Avoid calling fh_drop_write() twice in do_nfsd_create() (git-fixes).\n- NFSD: Clean up nfsd3_proc_create() (git-fixes).\n- nfsd: Clean up nfsd_file_put() (git-fixes).\n- NFSD: Clean up nfsd_open_verified() (git-fixes).\n- NFSD: Clean up unused code after rhashtable conversion (git-fixes).\n- NFSD: Convert filecache to rhltable (git-fixes).\n- NFSD: Convert the filecache to use rhashtable (git-fixes).\n- NFSD: De-duplicate hash bucket indexing (git-fixes).\n- nfsd: do not free files unconditionally in __nfsd_file_cache_purge (git-fixes).\n- nfsd: do not fsync nfsd_files on last close (git-fixes).\n- nfsd: do not hand out delegation on setuid files being opened for write (git-fixes).\n- nfsd: do not kill nfsd_files because of lease break error (git-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nfsd: do not take/put an extra reference when putting a file (git-fixes).\n- NFSD enforce filehandle check for source file in COPY (git-fixes).\n- NFSD: Ensure nf_inode is never dereferenced (git-fixes).\n- nfsd: fix handling of cached open files in nfsd4_open codepath (git-fixes).\n- NFSD: Fix licensing header in filecache.c (git-fixes).\n- nfsd: fix net-namespace logic in __nfsd_file_cache_purge (git-fixes).\n- nfsd: fix nfsd_file_unhash_and_dispose (git-fixes).\n- NFSD: Fix potential use-after-free in nfsd_file_put() (git-fixes).\n- NFSD: Fix problem of COMMIT and NFS4ERR_DELAY in infinite loop (git-fixes).\n- NFSD: Fix the filecache LRU shrinker (git-fixes).\n- nfsd: fix up the filecache laundrette scheduling (git-fixes).\n- nfsd: fix use-after-free in nfsd_file_do_acquire tracepoint (git-fixes).\n- NFSD: Flesh out a documenting comment for filecache.c (git-fixes).\n- NFSD: handle errors better in write_ports_addfd() (git-fixes).\n- NFSD: Instantiate a struct file when creating a regular NFSv4 file (git-fixes).\n- NFSD: Leave open files out of the filecache LRU (git-fixes).\n- nfsd: map EBADF (git-fixes).\n- NFSD: Move nfsd_file_trace_alloc() tracepoint (git-fixes).\n- NFSD: nfsd_file_hash_remove can compute hashval (git-fixes).\n- nfsd: NFSD_FILE_KEY_INODE only needs to find GC'ed entries (git-fixes).\n- NFSD: nfsd_file_put() can sleep (git-fixes).\n- NFSD: nfsd_file_unhash can compute hashval from nf-\u003enf_inode (git-fixes).\n- NFSD: No longer record nf_hashval in the trace log (git-fixes).\n- NFSD: Pass the target nfsd_file to nfsd_commit() (git-fixes).\n- nfsd: put the export reference in nfsd4_verify_deleg_dentry (git-fixes).\n- NFSD: Record number of flush calls (git-fixes).\n- NFSD: Refactor nfsd_create_setattr() (git-fixes).\n- NFSD: Refactor __nfsd_file_close_inode() (git-fixes).\n- NFSD: Refactor nfsd_file_gc() (git-fixes).\n- NFSD: Refactor nfsd_file_lru_scan() (git-fixes).\n- NFSD: Refactor NFSv3 CREATE (git-fixes).\n- NFSD: Refactor NFSv4 OPEN(CREATE) (git-fixes).\n- NFSD: Remove do_nfsd_create() (git-fixes).\n- NFSD: Remove lockdep assertion from unhash_and_release_locked() (git-fixes).\n- NFSD: Remove nfsd_file::nf_hashval (git-fixes).\n- nfsd: remove the pages_flushed statistic from filecache (git-fixes).\n- nfsd: reorganize filecache.c (git-fixes).\n- NFSD: Replace the 'init once' mechanism (git-fixes).\n- NFSD: Report average age of filecache items (git-fixes).\n- NFSD: Report count of calls to nfsd_file_acquire() (git-fixes).\n- NFSD: Report count of freed filecache items (git-fixes).\n- NFSD: Report filecache LRU size (git-fixes).\n- NFSD: Report the number of items evicted by the LRU walk (git-fixes).\n- nfsd: Retry once in nfsd_open on an -EOPENSTALE return (git-fixes).\n- nfsd: rework hashtable handling in nfsd_do_file_acquire (git-fixes).\n- nfsd: rework refcounting in filecache (git-fixes).\n- NFSD: Separate tracepoints for acquire and create (git-fixes).\n- NFSD: Set up an rhashtable for the filecache (git-fixes).\n- nfsd: silence extraneous printk on nfsd.ko insertion (git-fixes).\n- NFSD: simplify per-net file cache management (git-fixes).\n- nfsd: simplify test_bit return in NFSD_FILE_KEY_FULL comparator (git-fixes).\n- nfsd: simplify the delayed disposal list code (git-fixes).\n- NFSD: Trace filecache LRU activity (git-fixes).\n- NFSD: Trace filecache opens (git-fixes).\n- NFSD: verify the opened dentry after setting a delegation (git-fixes).\n- NFSD: WARN when freeing an item still linked via nf_lru (git-fixes).\n- NFSD: Write verifier might go backwards (git-fixes).\n- NFSD: Zero counters when the filecache is re-initialized (git-fixes).\n- NFS: Fix READ_PLUS when server does not support OP_READ_PLUS (git-fixes).\n- nfs: fix undefined behavior in nfs_block_bits() (git-fixes).\n- nfs: keep server info for remounts (git-fixes).\n- nfs: Leave pages in the pagecache if readpage failed (git-fixes).\n- NFSv4: Fixup smatch warning for ambiguous return (git-fixes).\n- NFSv4.x: by default serialize open/close operations (bsc#1223863 bsc#1227362)\n- nilfs2: add missing check for inode numbers on directory entries (git-fixes).\n- nilfs2: add missing check for inode numbers on directory entries (stable-fixes).\n- nilfs2: avoid undefined behavior in nilfs_cnt32_ge macro (git-fixes).\n- nilfs2: convert persistent object allocator to use kmap_local (git-fixes).\n- nilfs2: fix incorrect inode allocation from reserved inodes (git-fixes).\n- nilfs2: fix inode number range checks (git-fixes).\n- nilfs2: fix inode number range checks (stable-fixes).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme-auth: alloc nvme_dhchap_key as single buffer (git-fixes).\n- nvme-auth: allow mixing of secret and hash lengths (git-fixes).\n- nvme-auth: use transformed key size to create resp (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: ensure reset state check ordering (bsc#1215492).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvme: use ctrl state accessor (bsc#1215492).\n- ocfs2: fix DIO failure due to insufficient transaction credits (bsc#1216834).\n- ocfs2: remove redundant assignment to variable free_space (bsc#1228409).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- orangefs: fix out-of-bounds fsid access (git-fixes).\n- PCI: Add PCI_ERROR_RESPONSE and related definitions (stable-fixes).\n- PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal (git-fixes).\n- PCI: Extend ACS configurability (bsc#1228090).\n- PCI: Fix resource double counting on remove \u0026 rescan (git-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: Introduce cleanup helpers for device reference counts and locks (git-fixes).\n- PCI: Introduce cleanup helpers for device reference counts and locks (stable-fixes).\n- PCI: keystone: Do not enable BAR 0 for AM654x (git-fixes).\n- PCI: keystone: Fix NULL pointer dereference in case of DT error in ks_pcie_setup_rc_app_regs() (git-fixes).\n- PCI: keystone: Relocate ks_pcie_set/clear_dbi_mode() (git-fixes).\n- PCI/PM: Avoid D3cold for HP Pavilion 17 PC/1972 PCIe Ports (git-fixes).\n- PCI/PM: Avoid D3cold for HP Pavilion 17 PC/1972 PCIe Ports (stable-fixes).\n- PCI: rockchip: Use GPIOD_OUT_LOW flag while requesting ep_gpio (git-fixes).\n- PCI: tegra194: Set EP alignment restriction for inbound ATU (git-fixes).\n- pinctrl: core: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- pinctrl: freescale: mxs: Fix refcount of child (git-fixes).\n- pinctrl: single: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- pinctrl: ti: ti-iodelay: fix possible memory leak when pinctrl_enable() fails (git-fixes).\n- platform/chrome: cros_ec_debugfs: fix wrong EC message version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86: dell-smbios-base: Use sysfs_emit() (stable-fixes).\n- platform/x86: dell-smbios: Fix wrong token data in sysfs (git-fixes).\n- platform/x86: lg-laptop: Change ACPI device id (stable-fixes).\n- platform/x86: lg-laptop: Remove LGEX0815 hotkey handling (stable-fixes).\n- platform/x86: touchscreen_dmi: Add info for GlobalSpace SolT IVW 11.6' tablet (stable-fixes).\n- platform/x86: touchscreen_dmi: Add info for the EZpad 6s Pro (stable-fixes).\n- platform/x86: wireless-hotkey: Add support for LG Airplane Button (stable-fixes).\n- powerpc/cpuidle: Set CPUIDLE_FLAG_POLLING for snooze state (bsc#1227121 ltc#207129).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc/kasan: Disable address sanitization in kexec paths (bsc#1194869).\n- powerpc/pseries: Fix scv instruction crash with kexec (bsc#1194869).\n- powerpc/rtas: clean up includes (bsc#1227487).\n- powerpc/rtas: Prevent Spectre v1 gadget construction in sys_rtas() (bsc#1227487).\n- power: supply: cros_usbpd: provide ID table for avoiding fallback match (stable-fixes).\n- pwm: stm32: Always do lazy disabling (git-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Ignore optional access flags for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/restrack: Fix potential invalid address access (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- regmap-i2c: Subtract reg size from max_write (stable-fixes).\n- Revert 'ALSA: firewire-lib: obsolete workqueue for period update' (bsc#1208783).\n- Revert 'ALSA: firewire-lib: operate for period elapse event in process context' (bsc#1208783).\n- Revert 'leds: led-core: Fix refcount leak in of_led_get()' (git-fixes).\n- Revert 'usb: musb: da8xx: Set phy in OTG mode by default' (stable-fixes).\n- rpcrdma: fix handling for RDMA_CM_EVENT_DEVICE_REMOVAL (git-fixes).\n- rtc: cmos: Fix return value of nvmem callbacks (git-fixes).\n- rtc: interface: Add RTC offset to alarm after fix-up (git-fixes).\n- rtc: isl1208: Fix return value of nvmem callbacks (git-fixes).\n- rtlwifi: rtl8192de: Style clean-ups (stable-fixes).\n- s390: Implement __iowrite32_copy() (bsc#1226502)\n- s390: Stop using weak symbols for __iowrite64_copy() (bsc#1226502)\n- saa7134: Unchecked i2c_transfer function result fixed (git-fixes).\n- sched/fair: Do not balance task to its current running CPU (git fixes (sched)).\n- sched: Fix stop_one_cpu_nowait() vs hotplug (git fixes (sched)).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftests/bpf: Add a selftest for checking subreg equality (bsc#1225903).\n- selftests/bpf: add pre bpf_prog_test_run_opts() callback for test_loader (bsc#1225903).\n- selftests/bpf: add precision propagation tests in the presence of subprogs (bsc#1225903).\n- selftests/bpf: Add pruning test case for bpf_spin_lock (bsc#1225903).\n- selftests/bpf: Check if mark_chain_precision() follows scalar ids (bsc#1225903).\n- selftests/bpf: check if max number of bpf_loop iterations is tracked (bsc#1225903).\n- selftests/bpf: fix __retval() being always ignored (bsc#1225903).\n- selftests/bpf: fix unpriv_disabled check in test_verifier (bsc#1225903).\n- selftests/bpf: __imm_insn \u0026 __imm_const macro for bpf_misc.h (bsc#1225903).\n- selftests/bpf: make test_align selftest more robust (bsc#1225903).\n- selftests/bpf: populate map_array_ro map for verifier_array_access test (bsc#1225903).\n- selftests/bpf: prog_tests entry point for migrated test_verifier tests (bsc#1225903).\n- selftests/bpf: Report program name on parse_test_spec error (bsc#1225903).\n- selftests/bpf: Support custom per-test flags and multiple expected messages (bsc#1225903).\n- selftests/bpf: test case for callback_depth states pruning logic (bsc#1225903).\n- selftests/bpf: test case for relaxed prunning of active_lock.id (bsc#1225903).\n- selftests/bpf: test cases for regsafe() bug skipping check_id() (bsc#1225903).\n- selftests/bpf: Tests execution support for test_loader.c (bsc#1225903).\n- selftests/bpf: tests for iterating callbacks (bsc#1225903).\n- selftests/bpf: test widening for iterating callbacks (bsc#1225903).\n- selftests/bpf: track string payload offset as scalar in strobemeta (bsc#1225903).\n- selftests/bpf: Unprivileged tests for test_loader.c (bsc#1225903).\n- selftests/bpf: Verify copy_register_state() preserves parent/live fields (bsc#1225903).\n- selftests/bpf: verify states_equal() maintains idmap across all frames (bsc#1225903).\n- selftests/bpf: Verify that check_ids() is used for scalars in regsafe() (bsc#1225903).\n- selftests/sigaltstack: Fix ppc64 GCC build (git-fixes).\n- soc: ti: wkup_m3_ipc: Send NULL dummy message instead of pointer message (stable-fixes).\n- spi: imx: Do not expect DMA for i.MX{25,35,50,51,53} cspi devices (stable-fixes).\n- spi: mux: set ctlr-\u003ebits_per_word_mask (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228850).\n- SUNRPC: avoid soft lockup when transmitting UDP to reachable server (bsc#1225272).\n- SUNRPC: Fix gss_free_in_token_pages() (git-fixes).\n- SUNRPC: Fix loop termination condition in gss_free_in_token_pages() (git-fixes).\n- sunrpc: fix NFSACL RPC retry on soft mount (git-fixes).\n- SUNRPC: return proper error from gss_wrap_req_priv (git-fixes).\n- supported.conf:\n- tpm: Allow system suspend to continue when TPM suspend fails (bsc#1082555).\n- tpm: Prevent hwrng from activating during resume (bsc#1082555).\n- tpm_tis: Resend command to recover from data transfer errors (bsc#1082555).\n- tpm_tis: Use tpm_chip_{start,stop} decoration inside tpm_tis_resume (bsc#1082555).\n- tpm, tpm: Implement usage counter for locality (bsc#1082555).\n- tpm, tpm_tis: Avoid cache incoherency in test for interrupts (bsc#1082555).\n- tpm, tpm_tis: Claim locality before writing interrupt registers (bsc#1082555).\n- tpm, tpm_tis: Claim locality in interrupt handler (bsc#1082555).\n- tpm, tpm_tis: Claim locality when interrupts are reenabled on resume (bsc#1082555).\n- tpm, tpm_tis: correct tpm_tis_flags enumeration values (bsc#1082555).\n- tpm, tpm_tis: Do not skip reset of original interrupt vector (bsc#1082555).\n- tpm, tpm_tis: Only handle supported interrupts (bsc#1082555).\n- tracing: Build event generation tests only as modules (git-fixes).\n- tracing/net_sched: NULL pointer dereference in perf_trace_qdisc_reset() (git-fixes).\n- tracing/osnoise: Add osnoise/options file (bsc#1228330)\n- tracing/osnoise: Add OSNOISE_WORKLOAD option (bsc#1228330)\n- tracing/osnoise: Do not follow tracing_cpumask (bsc#1228330)\n- tracing/osnoise: Fix notify new tracing_max_latency (bsc#1228330)\n- tracing/osnoise: Make osnoise_instances static (bsc#1228330)\n- tracing/osnoise: Split workload start from the tracer start (bsc#1228330)\n- tracing/osnoise: Support a list of trace_array *tr (bsc#1228330)\n- tracing/osnoise: Use built-in RCU list checking (bsc#1228330)\n- tracing/timerlat: Notify new max thread latency (bsc#1228330)\n- USB: Add USB_QUIRK_NO_SET_INTF quirk for START BP-850k (stable-fixes).\n- usb: cdns3: allocate TX FIFO size according to composite EP number (git-fixes).\n- usb: cdns3: fix incorrect calculation of ep_buf_size when more than one config (git-fixes).\n- usb: cdns3: fix iso transfer error when mult is not zero (git-fixes).\n- usb: cdns3: improve handling of unaligned address case (git-fixes).\n- usb: cdns3: optimize OUT transfer by copying only actual received data (git-fixes).\n- usb: cdns3: skip set TRB_IOC when usb_request: no_interrupt is true (git-fixes).\n- USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor (git-fixes).\n- usb: dwc3: gadget: Do not delay End Transfer on delayed_status (git-fixes).\n- usb: dwc3: gadget: Force sending delayed status during soft disconnect (git-fixes).\n- usb: dwc3: gadget: Synchronize IRQ between soft connect/disconnect (git-fixes).\n- usb: gadget: call usb_gadget_check_config() to verify UDC capability (git-fixes).\n- usb: gadget: configfs: Prevent OOB read/write in usb_string_copy() (stable-fixes).\n- usb: gadget: printer: SS+ support (stable-fixes).\n- usb: misc: uss720: check for incompatible versions of the Belkin F5U002 (stable-fixes).\n- USB: serial: mos7840: fix crash on resume (git-fixes).\n- USB: serial: option: add Fibocom FM350-GL (stable-fixes).\n- USB: serial: option: add Netprisma LCUK54 series modules (stable-fixes).\n- USB: serial: option: add Rolling RW350-GL variants (stable-fixes).\n- USB: serial: option: add support for Foxconn T99W651 (stable-fixes).\n- USB: serial: option: add Telit FN912 rmnet compositions (stable-fixes).\n- USB: serial: option: add Telit generic core-dump composition (stable-fixes).\n- usb: typec: tcpm: clear pd_event queue in PORT_RESET (git-fixes).\n- usb: xhci-plat: Do not include xhci.h (git-fixes).\n- USB: xhci-plat: fix legacy PHY double init (git-fixes).\n- wifi: ath11k: fix wrong handling of CCMP256 and GCMP ciphers (git-fixes).\n- wifi: brcmsmac: LCN PHY code is used for BCM4313 2G-only device (git-fixes).\n- wifi: cfg80211: fix typo in cfg80211_calculate_bitrate_he() (git-fixes).\n- wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he() (git-fixes).\n- wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values (git-fixes).\n- wifi: cfg80211: wext: add extra SIOCSIWSCAN data check (stable-fixes).\n- wifi: iwlwifi: mvm: d3: fix WoWLAN command version lookup (stable-fixes).\n- wifi: iwlwifi: mvm: Handle BIGTK cipher in kek_kck cmd (stable-fixes).\n- wifi: iwlwifi: mvm: properly set 6 GHz channel direct probe option (stable-fixes).\n- wifi: mac80211: disable softirqs for queued frame handling (git-fixes).\n- wifi: mac80211: fix UBSAN noise in ieee80211_prep_hw_scan() (stable-fixes).\n- wifi: mac80211: handle tasklet frames before stopping (stable-fixes).\n- wifi: mac80211: mesh: init nonpeer_pm to active by default in mesh sdata (stable-fixes).\n- wifi: mt76: replace skb_put with skb_put_zero (stable-fixes).\n- wifi: mwifiex: Fix interface type change (git-fixes).\n- wifi: rtw89: Fix array index mistake in rtw89_sta_info_get_iter() (git-fixes).\n- wifi: wilc1000: fix ies_len type in connect path (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/amd_nb: Use Family 19h Models 60h-7Fh Function 4 IDs (git-fixes).\n- x86/apic: Force native_apic_mem_read() to use the MOV instruction (git-fixes).\n- x86/bhi: Avoid warning in #DB handler due to BHI mitigation (git-fixes).\n- x86/bugs: Remove default case for fully switched enums (bsc#1227900).\n- x86/fpu: Fix AMD X86_BUG_FXSAVE_LEAK fixup (git-fixes).\n- x86/ibt,ftrace: Search for __fentry__ location (git-fixes).\n- x86/Kconfig: Transmeta Crusoe is CPU family 5, not 6 (git-fixes).\n- x86/mm: Allow guest.enc_status_change_prepare() to fail (git-fixes).\n- x86/mm: Fix enc_status_change_finish_noop() (git-fixes).\n- x86/purgatory: Switch to the position-independent small code model (git-fixes).\n- x86/srso: Move retbleed IBPB check into existing 'has_microcode' code block (bsc#1227900).\n- x86/srso: Remove 'pred_cmd' label (bsc#1227900).\n- x86: Stop using weak symbols for __iowrite32_copy() (bsc#1226502)\n- x86/tdx: Fix race between set_memory_encrypted() and load_unaligned_zeropad() (git-fixes).\n- xfs: Add cond_resched to block unmap range and reflink remap path (bsc#1228226).\n- xhci: Apply broken streams quirk to Etron EJ188 xHCI host (stable-fixes).\n- xhci: Apply reset resume quirk to Etron EJ188 xHCI host (stable-fixes).\n- xhci: Set correct transferred length for cancelled bulk transfers (stable-fixes).\n","status":"published","published":"2024-08-16T13:46:19Z","modified":"2026-02-04T04:14:42.830641Z","updated_at":"2026-11-02T15:53:55.136363Z"},{"id":"SUSE-SU-2024:3194-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\nThe following security bugs were fixed:\n\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2023-52489: Fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)\n- CVE-2024-36881: Reset ptes when close() for wr-protected ones (bsc#1225718).\n- CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342,).\n- CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496)\n- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505)\n- CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472)\n- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-27079: Add kABI workaround patch (bsc#1223742).\n- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).\n- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).\n- CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252,).\n- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404)\n- CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402)\n- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42308: Update DRM patch reference (bsc#1229411)\n- CVE-2024-42301: Update parport patch reference (bsc#1229407)\n- CVE-2024-42290: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287,).\n- CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-43850: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-26669: kABI fix for --Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: kABI fix for -Fix delayed ACKs to not set the reference serial number (bsc#1222387).\n- CVE-2024-41050: Cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: Wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41074: Set object to close if ondemand_id \u003e 0 in copen (bsc#1228643).\n- CVE-2024-41075: Add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41012: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42159: Use proper format specifier in mpi3mr_sas_port_add() (bsc#1228754 CVE-2024-42159 git-fixes).\n- CVE-2024-42241: Disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert 'Make sure to try to detach at least one movable task' (bsc#1228978).\n- CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26837: Skip MDB replays of deferred events on offload (bsc#1222973).\n- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-36911: Do not free decrypted memory (bsc#1225745).\n- CVE-2024-36910: Do not free decrypted memory (bsc#1225717).\n- CVE-2024-36909: Do not free ring buffers that couldn't be re-encrypted (bsc#1225744).\n- CVE-2024-40938: Fix d_parent walk (bsc#1227840).\n- CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-41010: Add netlink helper library (bsc#1228021).\n- CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-42138: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42139: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: Initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42073: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-41000: Prefer different overflow check (bsc#1227867).\n- CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-42161: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-41069: Fix route memory corruption (bsc#1228644).\n- CVE-2024-39506: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-42145: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-40994: Fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-42124: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42096: Stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42224: Correct check for empty list (bsc#1228723).\n- CVE-2024-41048: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-40958: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40939: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-36933: Restore skb-\u003e{protocol,data,mac_header} for outer header in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-41044: Reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41066: Add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-42093: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42122: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-41078: Fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-40989: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-41064: Avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41036: Fix deadlock with the SPI chip variant (bsc#1228496)\n- CVE-2024-41040: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-35949: Make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-41081: Block BH in ila_output() (bsc#1228617).\n- CVE-2024-41076: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-42079: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-41057: Fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: Fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41015: Add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-40956: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-27437: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-41032: Check if a hash-index is in cpu_possible_mask (bsc#1228460)\n- CVE-2024-40957: Fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811)\n- CVE-2024-41041: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-40954: Do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-42070: Fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-41070: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-40959: Check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-40909: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n\nThe following non-security bugs were fixed:\n\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add NULL check for 'afb' before dereferencing in amdgpu_dm_plane_handle_cursor_update (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kcov: properly check for softirq context (git-fixes).\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- KVM: Stop processing *all* memslots when 'null' mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement 'queue-depth' iopolicy (bsc#1227706).\n- nvme-multipath: prepare for 'queue-depth' iopolicy (bsc#1227706).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (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: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-10T09:06:25Z","modified":"2026-02-04T02:14:25.258066Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3195-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\nThe following security bugs were fixed:\n\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2023-52489: Fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-36881: Fix reset ptes when close() for wr-protected (bsc#1225718).\n- CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505).\n- CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).\n- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).\n- CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).\n- CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).\n- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42290: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).\n- CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-43850: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-26669: Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: Blacklist e7870cf13d20 (' Fix delayed ACKs to not set the reference serial number') (bsc#1222387)\n- CVE-2024-41050: Cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: Wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41074: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41075: Add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41012: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42159: Fix sanitise num_phys (bsc#1228754).\n- CVE-2024-42241: Disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).\n- CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26837: Race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).\n- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-40938: Fix d_parent walk (bsc#1227840).\n- CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-41010: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-42138: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42139: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: Initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42073: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-41000: Prefer different overflow check (bsc#1227867).\n- CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-42161: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-41069: Fix route memory corruption (bsc#1228644).\n- CVE-2024-39506: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-42145: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-40994: Fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-42124: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42096: Stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42224: Correct check for empty list (bsc#1228723).\n- CVE-2024-41048: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-40958: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40939: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-36933: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-41044: Reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41066: Add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-42093: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42122: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-41078: Fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-40989: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-41064: Avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41036: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41040: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-35949: Make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-41081: Block BH in ila_output() (bsc#1228617).\n- CVE-2024-41076: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-42079: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-41057: Fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: Fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41015: Add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-40956: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-27437: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-41032: Check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-40957: Fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-41041: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-40954: Do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-42070: Fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-41070: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-40959: Check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-40909: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n\nThe following non-security bugs were fixed:\n\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- certs: Move RSA self-test data to separate file (bsc#1222777).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add NULL check for 'afb' before dereferencing in amdgpu_dm_plane_handle_cursor_update (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kcov: properly check for softirq context (git-fixes).\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- KVM: Stop processing *all* memslots when 'null' mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement 'queue-depth' iopolicy (bsc#1227706).\n- nvme-multipath: prepare for 'queue-depth' iopolicy (bsc#1227706).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (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: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-10T14:10:24Z","modified":"2026-02-04T02:36:48.443793Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3383-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-2024-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n- CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-42308: Update DRM patch reference (bsc#1229411)\n- CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).\n- CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).\n- CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).\n- CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).\n- CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42159: scsi: mpi3mr: fix sanitise num_phys (bsc#1228754).\n- CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-42142: net/mlx5: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42139: ice: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42109: netfilter: nf_tables: unconditionally flush pending work before notifier (bsc#1228505).\n- CVE-2024-42107: ice: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42106: inet_diag: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42095: serial: 8250_omap: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42082: xdp: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-41084: cxl/region: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).\n- CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-41075: cachefiles: add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41074: cachefiles: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41068: s390/sclp: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41051: cachefiles: wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41050: cachefiles: cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-41020: filelock: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41010: bpf: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-41000: block/ioctl: prefer different overflow check (bsc#1227867).\n- CVE-2024-40995: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40978: scsi: qedi: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40957: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40939: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).\n- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free (bsc#1226604).\n- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-36911: hv_netvsc: Do not free decrypted memory (bsc#1225745).\n- CVE-2024-36910: uio_hv_generic: Do not free decrypted memory (bsc#1225717).\n- CVE-2024-36909: Drivers: hv: vmbus: Do not free ring buffers that couldn't be re-encrypted (bsc#1225744).\n- CVE-2024-36881: mm/userfaultfd: Fix reset ptes when close() for wr-protected (bsc#1225718).\n- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)\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-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26677: blacklist.conf: Add e7870cf13d20 ('rxrpc: Fix delayed ACKs to not set the reference serial number') (bsc#1222387)\n- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).\n- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).\n- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section-\u003eusage (bsc#1221326).\n\n\nThe following non-security bugs were fixed:\n\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Drop libata patch that caused a regression (bsc#1229054)\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: Stop processing *all* memslots when 'null' mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- Move upstreamed powerpc patches into sorted section\n- Move upstreamed sound patches into sorted section\n- Moved upstreamed ASoC patch into sorted section\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- Revert 'ALSA: firewire-lib: obsolete workqueue for period update' (bsc#1208783).\n- Revert 'ALSA: firewire-lib: operate for period elapse event in process context' (bsc#1208783).\n- Revert 'KVM: Prevent module exit until all VMs are freed' (git-fixes).\n- Revert 'Revert 'md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d'' (git-fixes).\n- Revert 'md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d' (git-fixes).\n- Revert 'misc: fastrpc: Restrict untrusted app to attach to privileged PD' (git-fixes).\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()' (bsc#1230413).\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 'usb: gadget: uvc: cleanup request when not in correct state' (stable-fixes).\n- Revert 'usb: typec: tcpm: clear pd_event queue in PORT_RESET' (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- Update config files. Disable CONFIG_KFENCE on ppc64le (bsc#1226920)\n- Update config files. Disable vdpa drivers for Alibaba ENI and SolidNET (jsc#PED-8954, bsc#1227834)\n- Update patch references for ASoC regression fixes (bsc#1229045, bsc#1229046)\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- blacklist.conf: Add libata upstream revert entry (bsc#1229054)\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-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: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi: more build fix without patches.kabi (bsc#1226502)\n- kcov: properly check for softirq context (git-fixes).\n- kernel-binary.spec.in: Enable klp_symbols on openSUSE Tumbleweed (boo#1229042). \n- kernel-binary: generate and install compile_commands.json (bsc#1228971). \n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement 'queue-depth' iopolicy (bsc#1227706).\n- nvme-multipath: prepare for 'queue-depth' iopolicy (bsc#1227706).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (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: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-23T08:29:55Z","modified":"2026-02-04T02:30:48.4895Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2025:20044-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 kernel was updated to receive various security bugfixes.\n\nThis release includes the first live patch.\n\nThe following security bugs were fixed:\n\n- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287,).\n- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: blacklist.conf: Add e7870cf13d20 (\"rxrpc: Fix delayed ACKs to not set the reference serial number\") (bsc#1222387)\n- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).\n- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26837: net: bridge: switchdev: Skip MDB replays of deferred events on offload (bsc#1222973).\n- CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-36881: mm/userfaultfd: reset ptes when close() for wr-protected ones (bsc#1225718).\n- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free syzbot reported a suspicious rcu usage[1] in bridge's mst code. (bsc#1226604).\n- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).\n- CVE-2024-40939: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-40957: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40978: scsi: qedi: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40995: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-41000: block/ioctl: prefer different overflow check (bsc#1227867).\n- CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-41010: bpf: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41020: filelock: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-41050: cachefiles: cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: cachefiles: wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41068: s390/sclp: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41074: cachefiles: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41075: cachefiles: add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).\n- CVE-2024-41084: cxl/region: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42082: xdp: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42095: serial: 8250_omap: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42106: inet_diag: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42107: ice: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42109: netfilter: nf_tables: unconditionall (bsc#1228505).\n- CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42139: ice: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42142: net/mlx5: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727 CVE-2024-42157 git-fixes).\n- CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-42159: scsi: mpi3mr: sanitise num_phys (bsc#1228754).\n- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).\n- CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert \"sched/fair: Make sure to try to detach at least one movable task\" (bsc#1228978).\n- CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init(). (bsc#1229402).\n- CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init(). (bsc#1229404).\n- CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42308: Update DRM patch reference (bsc#1229411)\n- CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level()  (bsc#1229353).\n- CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session  (bsc#1229827).\n\nAdditional CVEs were previously fixed and are only mentioned in the metadata.\n\nThe following non-security bugs were fixed:\n\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Drop libata patch that caused a regression (bsc#1229054)\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: Stop processing *all* memslots when \"null\" mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- Move upstreamed powerpc patches into sorted section\n- Move upstreamed sound patches into sorted section\n- Moved upstreamed ASoC patch into sorted section\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- Revert \"ALSA: firewire-lib: obsolete workqueue for period update\" (bsc#1208783).\n- Revert \"ALSA: firewire-lib: operate for period elapse event in process context\" (bsc#1208783).\n- Revert \"KVM: Prevent module exit until all VMs are freed\" (git-fixes).\n- Revert \"Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\"\" (git-fixes).\n- Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\" (git-fixes).\n- Revert \"misc: fastrpc: Restrict untrusted app to attach to privileged PD\" (git-fixes).\n- Revert \"usb: gadget: uvc: cleanup request when not in correct state\" (stable-fixes).\n- Revert \"usb: typec: tcpm: clear pd_event queue in PORT_RESET\" (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- Update config files. Disable vdpa drivers for Alibaba ENI and SolidNET (jsc#PED-8954, bsc#1227834)\n- Update config files. Disable CONFIG_KFENCE on ppc64le (bsc#1226920)\n- Update patch references for ASoC regression fixes (bsc#1229045 bsc#1229046)\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- blacklist.conf: Add libata upstream revert entry (bsc#1229054)\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing \"n_accesses\" check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-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: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kcov: properly check for softirq context (git-fixes).\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- media: Revert \"media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()\" (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-multipath: prepare for \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands \"c#\", \"dp#\" and \"dx#\" (bsc#1194869).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (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: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2025-02-03T08:54:39Z","modified":"2026-03-23T04:50:03.568046Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20047-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-52489: mm/sparsemem: fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).\n- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: Blacklist e7870cf13d20 (\" Fix delayed ACKs to not set the reference serial number\") (bsc#1222387)\n- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).\n- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).\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-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-36881: mm/userfaultfd: Fix reset ptes when close() for wr-protected (bsc#1225718).\n- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free (bsc#1226604).\n- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).\n- CVE-2024-40939: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-40957: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40978: scsi: qedi: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40995: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-41000: block/ioctl: prefer different overflow check (bsc#1227867).\n- CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-41010: bpf: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41020: filelock: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-41050: cachefiles: cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: cachefiles: wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41068: s390/sclp: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41074: cachefiles: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41075: cachefiles: add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).\n- CVE-2024-41084: cxl/region: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42082: xdp: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42095: serial: 8250_omap: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42106: inet_diag: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42107: ice: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42109: netfilter: nf_tables: unconditionally flush pending work before notifier (bsc#1228505).\n- CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42139: ice: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42142: net/mlx5: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-42159: scsi: mpi3mr: fix sanitise num_phys (bsc#1228754).\n- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).\n- CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert \"sched/fair: Make sure to try to detach at least one movable task\" (bsc#1228978).\n- CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).\n- CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).\n- CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n\nThe following non-security bugs were fixed:\n\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Drop libata patch that caused a regression (bsc#1229054)\n- Fix build errors without patches.kabi (bsc#1226502)\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: Stop processing *all* memslots when \"null\" mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- Move upstreamed powerpc patches into sorted section\n- Move upstreamed sound patches into sorted section\n- Moved upstreamed ASoC patch into sorted section\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- README.BRANCH: Add Petr Tesarik as branch maintainer\n- Revert \"ALSA: firewire-lib: obsolete workqueue for period update\" (bsc#1208783).\n- Revert \"ALSA: firewire-lib: operate for period elapse event in process context\" (bsc#1208783).\n- Revert \"KVM: Prevent module exit until all VMs are freed\" (git-fixes).\n- Revert \"Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\"\" (git-fixes).\n- Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\" (git-fixes).\n- Revert \"misc: fastrpc: Restrict untrusted app to attach to privileged PD\" (git-fixes).\n- Revert \"usb: gadget: uvc: cleanup request when not in correct state\" (stable-fixes).\n- Revert \"usb: typec: tcpm: clear pd_event queue in PORT_RESET\" (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- Update config files. Disable vdpa drivers for Alibaba ENI and SolidNET (jsc#PED-8954, bsc#1227834)\n- Update config files. Disable CONFIG_KFENCE on ppc64le (bsc#1226920)\n- Update patch refefernce for MFD patch (jsc#PED-10029)\n- Update patch reference for MD patch (jsc#PED-10029 jsc#PED-10045)\n- Update patch reference for SPI patch (jsc#PED-10105)\n- Update patch reference for iwlwifi fix (jsc#PED-10055)\n- Update patch reference of USB patch (jsc#PED-10108)\n- Update patch references for ASoC regression fixes (bsc#1229045 bsc#1229046)\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- blacklist.conf: Add libata upstream revert entry (bsc#1229054)\n- blacklist.conf: printk/sysctl: breaks kernel without pre-requisite patches (bsc#1229025)\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- check-for-config-changes: ignore also GCC_ASM_GOTO_OUTPUT_BROKEN Mainline commit f2f6a8e88717 (\"init/Kconfig: remove CONFIG_GCC_ASM_GOTO_OUTPUT_WORKAROUND\") replaced GCC_ASM_GOTO_OUTPUT_WORKAROUND with GCC_ASM_GOTO_OUTPUT_BROKEN. Ignore both when checking config changes.\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- config.sh: generate and install compile_commands.json (bsc#1228971) This file contains the command line options used to compile every C file. It's useful for the livepatching team.\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing \"n_accesses\" check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-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: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kcov: properly check for softirq context (git-fixes).\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- media: Revert \"media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()\" (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-multipath: prepare for \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands \"c#\", \"dp#\" and \"dx#\" (bsc#1194869).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (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: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2025-02-03T08:55:15Z","modified":"2026-03-23T04:50:42.230219Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"USN-6999-1","title":"linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-lowlatency, linux-oem-6.8, linux-oracle vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - FPGA Framework;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Microchip PCI driver;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - PCI subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Sonic Silicon Backplane drivers;\n  - Greybus lights staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Core kernel;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Landlock security;\n  - Linux Security Modules (LSM) Framework;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - SOF drivers;\n  - KVM core;\n(CVE-2024-40911, CVE-2024-37356, CVE-2024-40935, CVE-2024-40944,\nCVE-2024-41003, CVE-2024-40990, CVE-2024-40952, CVE-2024-40940,\nCVE-2024-40930, CVE-2024-40985, CVE-2024-40941, CVE-2024-38630,\nCVE-2024-39466, CVE-2024-40933, CVE-2024-38624, CVE-2024-40924,\nCVE-2024-40945, CVE-2024-40899, CVE-2024-38622, CVE-2024-40979,\nCVE-2024-36484, CVE-2024-41004, CVE-2024-39474, CVE-2022-48772,\nCVE-2024-36244, CVE-2024-38664, CVE-2024-40925, CVE-2024-40980,\nCVE-2024-39480, CVE-2024-36270, CVE-2024-40936, CVE-2024-40904,\nCVE-2024-38635, CVE-2024-40927, CVE-2024-36481, CVE-2024-40929,\nCVE-2024-40958, CVE-2024-36978, CVE-2024-40992, CVE-2024-40908,\nCVE-2024-39504, CVE-2024-41001, CVE-2024-40967, CVE-2023-52884,\nCVE-2024-40997, CVE-2024-40903, CVE-2024-40913, CVE-2024-34030,\nCVE-2024-39473, CVE-2024-40966, CVE-2024-40951, CVE-2024-40902,\nCVE-2024-40982, CVE-2024-40923, CVE-2024-39467, CVE-2024-40910,\nCVE-2024-40909, CVE-2024-39463, CVE-2024-40974, CVE-2024-41002,\nCVE-2024-39464, CVE-2024-39496, CVE-2024-41040, CVE-2024-39469,\nCVE-2024-39500, CVE-2024-39510, CVE-2024-38627, CVE-2024-32936,\nCVE-2024-40975, CVE-2024-38390, CVE-2024-40959, CVE-2024-41006,\nCVE-2024-40986, CVE-2024-40987, CVE-2024-40922, CVE-2024-40983,\nCVE-2024-37354, CVE-2024-38637, CVE-2024-39277, CVE-2024-40943,\nCVE-2024-39371, CVE-2024-40921, CVE-2024-40953, CVE-2024-38634,\nCVE-2024-38659, CVE-2024-39492, CVE-2024-40976, CVE-2024-40906,\nCVE-2024-40965, CVE-2024-38667, CVE-2024-39498, CVE-2024-38628,\nCVE-2024-38661, CVE-2024-38663, CVE-2024-40998, CVE-2024-40948,\nCVE-2024-38306, CVE-2024-40928, CVE-2024-39468, CVE-2024-39494,\nCVE-2024-39505, CVE-2024-40963, CVE-2024-39499, CVE-2024-39506,\nCVE-2024-40995, CVE-2024-39491, CVE-2024-40900, CVE-2024-39478,\nCVE-2024-39490, CVE-2024-39291, CVE-2024-40981, CVE-2024-40926,\nCVE-2024-40939, CVE-2024-38385, CVE-2024-39483, CVE-2024-40989,\nCVE-2024-40955, CVE-2024-39501, CVE-2024-38381, CVE-2024-33621,\nCVE-2024-40964, CVE-2024-42148, CVE-2024-36286, CVE-2024-38629,\nCVE-2024-39509, CVE-2024-39298, CVE-2024-36489, CVE-2024-34777,\nCVE-2024-40957, CVE-2024-40919, CVE-2024-39462, CVE-2024-39495,\nCVE-2024-39497, CVE-2024-38636, CVE-2024-36281, CVE-2024-39479,\nCVE-2024-40932, CVE-2024-36288, CVE-2024-38623, CVE-2024-40969,\nCVE-2024-40931, CVE-2024-36971, CVE-2024-40934, CVE-2024-36015,\nCVE-2024-39485, CVE-2024-40996, CVE-2024-39507, CVE-2024-36973,\nCVE-2024-38625, CVE-2024-39301, CVE-2024-34027, CVE-2024-37026,\nCVE-2024-40960, CVE-2024-37078, CVE-2024-40912, CVE-2024-40988,\nCVE-2024-41005, CVE-2024-39276, CVE-2024-38662, CVE-2024-39502,\nCVE-2024-36479, CVE-2024-40947, CVE-2024-38780, CVE-2024-38388,\nCVE-2024-40917, CVE-2024-36974, CVE-2024-40970, CVE-2024-40901,\nCVE-2024-38384, CVE-2024-39475, CVE-2024-40949, CVE-2024-37021,\nCVE-2024-38633, CVE-2024-39503, CVE-2024-41000, CVE-2024-33847,\nCVE-2024-35247, CVE-2024-40968, CVE-2024-33619, CVE-2024-38619,\nCVE-2024-40984, CVE-2024-36478, CVE-2024-39493, CVE-2024-42078,\nCVE-2024-40954, CVE-2024-40978, CVE-2024-39508, CVE-2024-40915,\nCVE-2024-39489, CVE-2024-40920, CVE-2024-38618, CVE-2024-40938,\nCVE-2024-39296, CVE-2024-40962, CVE-2024-39470, CVE-2024-39481,\nCVE-2024-40977, CVE-2024-38621, CVE-2024-40971, CVE-2024-31076,\nCVE-2024-36972, CVE-2024-39471, CVE-2024-40994, CVE-2024-40973,\nCVE-2024-40916, CVE-2024-40942, CVE-2024-40956, CVE-2024-39465,\nCVE-2024-40914, CVE-2024-40937, CVE-2024-40918, CVE-2024-40905,\nCVE-2024-39488, CVE-2024-38632, CVE-2024-39461, CVE-2024-40999,\nCVE-2024-40972, CVE-2024-36477, CVE-2024-40961)\n","status":"published","published":"2024-09-11T14:36:17Z","modified":"2026-10-26T22:33:53.084634611Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-6999-2","title":"linux-raspi vulnerabilities","description":"Chenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - FPGA Framework;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Microchip PCI driver;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - PCI subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Sonic Silicon Backplane drivers;\n  - Greybus lights staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Tracing file system;\n  - IOMMU subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Core kernel;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Landlock security;\n  - Linux Security Modules (LSM) Framework;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - SOF drivers;\n  - KVM core;\n(CVE-2024-40978, CVE-2024-39504, CVE-2024-39483, CVE-2024-36478,\nCVE-2024-40928, CVE-2024-36971, CVE-2024-40947, CVE-2024-31076,\nCVE-2024-40934, CVE-2024-40909, CVE-2024-40962, CVE-2024-38635,\nCVE-2024-38632, CVE-2024-40912, CVE-2024-40967, CVE-2024-39492,\nCVE-2024-40974, CVE-2024-39466, CVE-2024-40939, CVE-2024-40988,\nCVE-2024-40951, CVE-2024-41005, CVE-2024-40968, CVE-2024-39493,\nCVE-2024-40949, CVE-2022-48772, CVE-2024-40944, CVE-2024-40998,\nCVE-2024-39490, CVE-2024-39467, CVE-2024-42078, CVE-2024-40953,\nCVE-2024-40990, CVE-2024-40902, CVE-2024-39461, CVE-2024-39301,\nCVE-2024-36978, CVE-2024-39475, CVE-2024-39496, CVE-2024-40901,\nCVE-2024-40985, CVE-2024-33621, CVE-2024-38663, CVE-2024-39497,\nCVE-2024-40937, CVE-2024-40941, CVE-2024-40987, CVE-2024-40918,\nCVE-2024-32936, CVE-2024-40999, CVE-2024-40938, CVE-2024-39488,\nCVE-2024-39510, CVE-2024-40924, CVE-2024-38661, CVE-2024-40989,\nCVE-2024-39509, CVE-2024-40983, CVE-2024-39471, CVE-2024-39502,\nCVE-2024-39508, CVE-2024-39371, CVE-2024-40982, CVE-2024-40910,\nCVE-2024-40903, CVE-2024-39296, CVE-2024-39507, CVE-2024-40906,\nCVE-2024-37354, CVE-2024-40905, CVE-2024-34027, CVE-2024-38618,\nCVE-2024-40900, CVE-2024-39469, CVE-2024-38662, CVE-2024-35247,\nCVE-2024-40922, CVE-2024-40926, CVE-2024-39503, CVE-2024-40899,\nCVE-2024-40977, CVE-2024-38634, CVE-2024-40933, CVE-2024-40992,\nCVE-2024-40904, CVE-2024-36479, CVE-2024-40996, CVE-2024-40957,\nCVE-2024-40931, CVE-2024-39291, CVE-2024-38780, CVE-2024-39277,\nCVE-2024-38628, CVE-2024-40932, CVE-2024-41004, CVE-2024-33847,\nCVE-2024-40972, CVE-2024-40945, CVE-2023-52884, CVE-2024-38664,\nCVE-2024-39462, CVE-2024-40965, CVE-2024-38388, CVE-2024-40916,\nCVE-2024-36489, CVE-2024-40975, CVE-2024-40942, CVE-2024-40995,\nCVE-2024-40997, CVE-2024-38385, CVE-2024-40911, CVE-2024-39474,\nCVE-2024-39470, CVE-2024-41000, CVE-2024-36015, CVE-2024-38633,\nCVE-2024-40943, CVE-2024-39489, CVE-2024-36477, CVE-2024-39491,\nCVE-2024-40919, CVE-2024-40914, CVE-2024-40966, CVE-2024-41002,\nCVE-2024-40960, CVE-2024-38624, CVE-2024-40964, CVE-2024-40936,\nCVE-2024-40913, CVE-2024-40955, CVE-2024-37026, CVE-2024-38384,\nCVE-2024-37078, CVE-2024-36244, CVE-2024-38622, CVE-2024-39485,\nCVE-2024-39479, CVE-2024-39505, CVE-2024-36973, CVE-2024-39498,\nCVE-2024-40908, CVE-2024-37356, CVE-2024-39480, CVE-2024-38381,\nCVE-2024-40940, CVE-2024-40980, CVE-2024-39276, CVE-2024-39499,\nCVE-2024-36484, CVE-2024-38636, CVE-2024-38390, CVE-2024-38619,\nCVE-2024-39478, CVE-2024-40959, CVE-2024-36288, CVE-2024-40935,\nCVE-2024-41006, CVE-2024-38625, CVE-2024-36972, CVE-2024-39298,\nCVE-2024-39468, CVE-2024-40970, CVE-2024-37021, CVE-2024-40981,\nCVE-2024-40921, CVE-2024-34777, CVE-2024-39500, CVE-2024-40927,\nCVE-2024-40979, CVE-2024-38627, CVE-2024-39501, CVE-2024-39481,\nCVE-2024-40917, CVE-2024-40956, CVE-2024-42148, CVE-2024-36481,\nCVE-2024-40925, CVE-2024-40986, CVE-2024-40948, CVE-2024-41003,\nCVE-2024-39506, CVE-2024-40952, CVE-2024-38306, CVE-2024-40971,\nCVE-2024-41001, CVE-2024-40973, CVE-2024-36281, CVE-2024-40923,\nCVE-2024-39473, CVE-2024-38637, CVE-2024-40984, CVE-2024-39463,\nCVE-2024-41040, CVE-2024-38623, CVE-2024-40954, CVE-2024-36286,\nCVE-2024-38667, CVE-2024-39465, CVE-2024-40915, CVE-2024-33619,\nCVE-2024-40920, CVE-2024-40969, CVE-2024-38659, CVE-2024-34030,\nCVE-2024-38630, CVE-2024-40976, CVE-2024-36974, CVE-2024-40930,\nCVE-2024-39464, CVE-2024-38621, CVE-2024-40958, CVE-2024-40994,\nCVE-2024-39494, CVE-2024-40961, CVE-2024-39495, CVE-2024-40963,\nCVE-2024-36270, CVE-2024-38629, CVE-2024-40929)\n","status":"published","published":"2024-09-23T15:33:39Z","modified":"2026-10-26T22:33:08.126007801Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7003-1","title":"linux, linux-aws, linux-azure, linux-bluefield, linux-gcp, linux-gkeop, linux-ibm, linux-kvm, linux-oracle vulnerabilities","description":"\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - USB subsystem;\n  - JFFS2 file system;\n  - JFS file system;\n  - File systems infrastructure;\n  - NILFS2 file system;\n  - IOMMU subsystem;\n  - Sun RPC protocol;\n  - Netfilter;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2024-40905, CVE-2024-41095, CVE-2024-41035, CVE-2024-36974,\nCVE-2024-40959, CVE-2024-40978, CVE-2024-42236, CVE-2024-40963,\nCVE-2024-40916, CVE-2024-41006, CVE-2024-39495, CVE-2023-52803,\nCVE-2024-42070, CVE-2024-41041, CVE-2024-42157, CVE-2024-36894,\nCVE-2024-42153, CVE-2024-42127, CVE-2024-42224, CVE-2024-40932,\nCVE-2024-42105, CVE-2024-40968, CVE-2024-41044, CVE-2024-41046,\nCVE-2023-52887, CVE-2024-42094, CVE-2024-40960, CVE-2024-41007,\nCVE-2024-40961, CVE-2024-39487, CVE-2024-39502, CVE-2024-42086,\nCVE-2024-36978, CVE-2024-39503, CVE-2024-41049, CVE-2024-42090,\nCVE-2024-42232, CVE-2024-39499, CVE-2024-40902, CVE-2024-37078,\nCVE-2024-39501, CVE-2024-42119, CVE-2024-40901, CVE-2024-42101,\nCVE-2024-42104, CVE-2024-42145, CVE-2024-41097, CVE-2024-40942,\nCVE-2024-41034, CVE-2024-40904, CVE-2024-41089, CVE-2024-42084,\nCVE-2024-42093, CVE-2024-40945, CVE-2024-40958, CVE-2024-42124,\nCVE-2024-40987, CVE-2024-40912, CVE-2024-39506, CVE-2024-40941,\nCVE-2024-39509, CVE-2024-40974, CVE-2024-39505, CVE-2024-42115,\nCVE-2024-40988, CVE-2024-40995, CVE-2024-42097, CVE-2024-41087,\nCVE-2024-42106, CVE-2024-40984, CVE-2024-40981, CVE-2024-42102,\nCVE-2024-42148, CVE-2024-42154, CVE-2024-42096, CVE-2024-40934,\nCVE-2024-40980, CVE-2024-42076, CVE-2024-40943, CVE-2024-42092,\nCVE-2024-42089, CVE-2024-42223, CVE-2024-38619, CVE-2024-42087,\nCVE-2024-39469)\n","status":"published","published":"2024-09-12T09:40:42Z","modified":"2026-10-26T22:32:59.360568386Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7003-2","title":"linux-aws-5.4, linux-azure-5.4, linux-gcp-5.4, linux-hwe-5.4, linux-ibm-5.4, linux-oracle-5.4 vulnerabilities","description":"\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - USB subsystem;\n  - JFFS2 file system;\n  - JFS file system;\n  - File systems infrastructure;\n  - NILFS2 file system;\n  - IOMMU subsystem;\n  - Sun RPC protocol;\n  - Netfilter;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2024-40941, CVE-2024-42086, CVE-2024-41097, CVE-2024-40958,\nCVE-2024-41089, CVE-2024-40942, CVE-2024-40968, CVE-2024-40934,\nCVE-2024-40902, CVE-2024-42124, CVE-2023-52887, CVE-2024-42115,\nCVE-2024-41041, CVE-2024-39501, CVE-2024-40932, CVE-2024-42102,\nCVE-2024-40960, CVE-2024-39487, CVE-2024-39503, CVE-2024-40945,\nCVE-2024-40959, CVE-2024-40987, CVE-2024-40995, CVE-2024-40988,\nCVE-2024-42084, CVE-2024-40943, CVE-2024-42070, CVE-2024-40904,\nCVE-2024-41049, CVE-2024-41046, CVE-2024-39502, CVE-2024-42097,\nCVE-2024-42090, CVE-2024-42236, CVE-2024-42223, CVE-2024-42094,\nCVE-2024-41007, CVE-2024-42105, CVE-2024-41035, CVE-2024-41087,\nCVE-2024-42157, CVE-2024-39495, CVE-2024-36894, CVE-2024-40916,\nCVE-2024-39469, CVE-2024-40974, CVE-2024-42153, CVE-2024-36974,\nCVE-2024-42096, CVE-2024-42232, CVE-2024-40980, CVE-2024-41034,\nCVE-2024-42087, CVE-2024-42093, CVE-2024-41095, CVE-2024-42145,\nCVE-2024-42148, CVE-2023-52803, CVE-2024-39499, CVE-2024-42104,\nCVE-2024-42224, CVE-2024-37078, CVE-2024-42092, CVE-2024-39505,\nCVE-2024-38619, CVE-2024-42106, CVE-2024-40978, CVE-2024-41044,\nCVE-2024-42089, CVE-2024-40981, CVE-2024-42154, CVE-2024-36978,\nCVE-2024-42076, CVE-2024-40984, CVE-2024-42127, CVE-2024-42119,\nCVE-2024-40961, CVE-2024-39509, CVE-2024-42101, CVE-2024-40901,\nCVE-2024-40963, CVE-2024-40905, CVE-2024-39506, CVE-2024-40912,\nCVE-2024-41006)\n","status":"published","published":"2024-09-12T10:47:52Z","modified":"2026-10-26T22:33:47.296644393Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7003-3","title":"linux-xilinx-zynqmp vulnerabilities","description":"\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - USB subsystem;\n  - JFFS2 file system;\n  - JFS file system;\n  - File systems infrastructure;\n  - NILFS2 file system;\n  - IOMMU subsystem;\n  - Sun RPC protocol;\n  - Netfilter;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2024-42094, CVE-2024-42154, CVE-2024-42101, CVE-2024-40995,\nCVE-2024-40959, CVE-2024-42076, CVE-2024-40961, CVE-2024-42096,\nCVE-2024-42092, CVE-2024-39501, CVE-2024-41046, CVE-2024-42087,\nCVE-2024-39502, CVE-2024-42090, CVE-2024-40974, CVE-2024-40942,\nCVE-2024-39509, CVE-2024-40934, CVE-2024-42148, CVE-2024-42127,\nCVE-2024-42115, CVE-2024-39505, CVE-2024-36978, CVE-2024-39503,\nCVE-2024-40912, CVE-2024-41034, CVE-2024-42119, CVE-2024-41006,\nCVE-2024-40902, CVE-2024-40968, CVE-2024-39499, CVE-2024-42093,\nCVE-2024-40941, CVE-2024-42106, CVE-2024-42145, CVE-2024-41097,\nCVE-2024-36974, CVE-2024-41044, CVE-2024-39495, CVE-2024-40981,\nCVE-2024-40987, CVE-2024-42232, CVE-2024-40905, CVE-2024-39506,\nCVE-2024-42153, CVE-2024-41007, CVE-2024-40978, CVE-2024-40960,\nCVE-2023-52887, CVE-2024-41087, CVE-2024-41049, CVE-2024-42086,\nCVE-2024-40958, CVE-2024-40980, CVE-2024-42084, CVE-2024-42224,\nCVE-2024-39487, CVE-2024-40943, CVE-2024-40984, CVE-2024-41095,\nCVE-2024-41035, CVE-2024-41089, CVE-2024-36894, CVE-2024-42104,\nCVE-2024-40988, CVE-2024-42105, CVE-2024-39469, CVE-2024-40901,\nCVE-2024-40963, CVE-2024-42097, CVE-2024-42089, CVE-2024-42124,\nCVE-2024-42223, CVE-2023-52803, CVE-2024-42070, CVE-2024-42157,\nCVE-2024-42102, CVE-2024-40916, CVE-2024-40904, CVE-2024-41041,\nCVE-2024-40932, CVE-2024-40945, CVE-2024-38619, CVE-2024-37078,\nCVE-2024-42236)\n","status":"published","published":"2024-09-13T08:01:57Z","modified":"2026-10-26T22:32:41.902537397Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7003-4","title":"linux-raspi vulnerabilities","description":"It was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - USB subsystem;\n  - JFFS2 file system;\n  - JFS file system;\n  - File systems infrastructure;\n  - NILFS2 file system;\n  - IOMMU subsystem;\n  - Sun RPC protocol;\n  - Netfilter;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2024-41034, CVE-2024-40984, CVE-2024-40987, CVE-2024-42119,\nCVE-2024-42224, CVE-2024-42101, CVE-2024-42096, CVE-2024-41095,\nCVE-2024-42087, CVE-2024-42104, CVE-2024-42148, CVE-2024-39495,\nCVE-2024-40980, CVE-2024-42223, CVE-2024-40961, CVE-2024-40988,\nCVE-2024-42127, CVE-2024-42090, CVE-2024-42236, CVE-2024-40995,\nCVE-2024-41007, CVE-2024-40968, CVE-2024-40901, CVE-2024-42097,\nCVE-2024-41041, CVE-2024-36974, CVE-2024-42115, CVE-2024-40978,\nCVE-2024-38619, CVE-2024-41049, CVE-2024-41035, CVE-2024-41044,\nCVE-2024-42154, CVE-2024-39499, CVE-2024-42070, CVE-2024-40959,\nCVE-2024-39487, CVE-2024-42157, CVE-2024-40916, CVE-2024-42076,\nCVE-2024-41087, CVE-2024-42094, CVE-2024-42124, CVE-2024-40905,\nCVE-2024-42145, CVE-2024-40963, CVE-2024-36894, CVE-2024-40942,\nCVE-2024-42092, CVE-2024-42153, CVE-2024-41089, CVE-2024-40912,\nCVE-2023-52887, CVE-2024-40934, CVE-2024-41006, CVE-2024-39501,\nCVE-2024-42084, CVE-2024-39506, CVE-2024-39509, CVE-2024-40943,\nCVE-2024-42106, CVE-2024-42093, CVE-2024-40902, CVE-2024-42086,\nCVE-2024-40958, CVE-2024-39502, CVE-2024-42232, CVE-2024-42089,\nCVE-2024-37078, CVE-2024-39469, CVE-2024-41046, CVE-2024-42102,\nCVE-2024-40974, CVE-2024-39505, CVE-2024-40960, CVE-2024-42105,\nCVE-2024-40932, CVE-2024-40904, CVE-2024-40981, CVE-2024-39503,\nCVE-2024-41097, CVE-2024-40941, CVE-2024-36978, CVE-2023-52803,\nCVE-2024-40945)\n","status":"published","published":"2024-09-26T09:55:30Z","modified":"2026-10-26T22:32:34.214395135Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7003-5","title":"linux-raspi-5.4 vulnerabilities","description":"\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - USB subsystem;\n  - JFFS2 file system;\n  - JFS file system;\n  - File systems infrastructure;\n  - NILFS2 file system;\n  - IOMMU subsystem;\n  - Sun RPC protocol;\n  - Netfilter;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2024-40916, CVE-2024-41035, CVE-2024-39469, CVE-2024-39499,\nCVE-2024-36978, CVE-2024-42092, CVE-2024-42087, CVE-2024-42102,\nCVE-2024-40978, CVE-2024-40902, CVE-2024-36974, CVE-2024-42096,\nCVE-2024-40974, CVE-2024-40904, CVE-2024-40905, CVE-2024-42153,\nCVE-2024-42106, CVE-2024-42070, CVE-2024-41097, CVE-2024-42090,\nCVE-2024-42105, CVE-2024-42104, CVE-2024-39502, CVE-2024-41089,\nCVE-2024-40945, CVE-2024-38619, CVE-2024-40961, CVE-2024-42127,\nCVE-2024-39487, CVE-2024-40988, CVE-2024-41044, CVE-2024-42236,\nCVE-2024-40942, CVE-2024-39506, CVE-2024-39509, CVE-2024-39503,\nCVE-2024-40934, CVE-2024-40959, CVE-2024-42101, CVE-2024-40960,\nCVE-2024-40968, CVE-2024-41087, CVE-2023-52803, CVE-2024-40987,\nCVE-2024-40943, CVE-2024-42089, CVE-2023-52887, CVE-2024-37078,\nCVE-2024-42148, CVE-2024-36894, CVE-2024-42097, CVE-2024-41006,\nCVE-2024-40984, CVE-2024-40963, CVE-2024-42223, CVE-2024-40912,\nCVE-2024-42086, CVE-2024-41049, CVE-2024-42157, CVE-2024-41034,\nCVE-2024-42145, CVE-2024-42124, CVE-2024-40995, CVE-2024-42224,\nCVE-2024-40981, CVE-2024-41095, CVE-2024-40901, CVE-2024-42115,\nCVE-2024-41041, CVE-2024-41007, CVE-2024-39505, CVE-2024-40932,\nCVE-2024-39495, CVE-2024-40980, CVE-2024-42084, CVE-2024-41046,\nCVE-2024-42119, CVE-2024-42076, CVE-2024-42232, CVE-2024-39501,\nCVE-2024-40958, CVE-2024-40941, CVE-2024-42093, CVE-2024-42094,\nCVE-2024-42154)\n","status":"published","published":"2024-10-01T13:21:56Z","modified":"2026-10-26T22:32:50.411327582Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7004-1","title":"linux-azure vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - FPGA Framework;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Microchip PCI driver;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - PCI subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Sonic Silicon Backplane drivers;\n  - Greybus lights staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Tracing file system;\n  - IOMMU subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Core kernel;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Landlock security;\n  - Linux Security Modules (LSM) Framework;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - SOF drivers;\n  - KVM core;\n(CVE-2024-36270, CVE-2024-38627, CVE-2024-39508, CVE-2024-41001,\nCVE-2024-38634, CVE-2024-40979, CVE-2024-40903, CVE-2024-34030,\nCVE-2024-38621, CVE-2024-34027, CVE-2024-39504, CVE-2024-38385,\nCVE-2024-36288, CVE-2024-39301, CVE-2024-38628, CVE-2024-42270,\nCVE-2024-39507, CVE-2024-36286, CVE-2024-40960, CVE-2024-36479,\nCVE-2024-41002, CVE-2024-36974, CVE-2024-40943, CVE-2024-40976,\nCVE-2024-38662, CVE-2024-40995, CVE-2024-39497, CVE-2024-31076,\nCVE-2024-39371, CVE-2024-40983, CVE-2024-40985, CVE-2024-38618,\nCVE-2024-40914, CVE-2024-40989, CVE-2024-40973, CVE-2024-38663,\nCVE-2024-39463, CVE-2024-38633, CVE-2024-36978, CVE-2024-40970,\nCVE-2024-40932, CVE-2024-39480, CVE-2024-39471, CVE-2024-40962,\nCVE-2024-40986, CVE-2024-40937, CVE-2024-39469, CVE-2024-40904,\nCVE-2024-39466, CVE-2024-38388, CVE-2024-39494, CVE-2024-41004,\nCVE-2024-38381, CVE-2022-48772, CVE-2024-33847, CVE-2024-40969,\nCVE-2024-40957, CVE-2024-40933, CVE-2024-37354, CVE-2024-39468,\nCVE-2024-40917, CVE-2024-38623, CVE-2024-40958, CVE-2024-39502,\nCVE-2024-38384, CVE-2024-39506, CVE-2024-40940, CVE-2024-34777,\nCVE-2024-41005, CVE-2024-39470, CVE-2024-39464, CVE-2024-39492,\nCVE-2024-38629, CVE-2024-39505, CVE-2024-40952, CVE-2024-40941,\nCVE-2024-39474, CVE-2024-38664, CVE-2024-40929, CVE-2024-39489,\nCVE-2024-40953, CVE-2024-40916, CVE-2024-40911, CVE-2024-32936,\nCVE-2024-40934, CVE-2024-37078, CVE-2024-39483, CVE-2024-40967,\nCVE-2024-40924, CVE-2024-39462, CVE-2024-40981, CVE-2024-36281,\nCVE-2024-39291, CVE-2024-39481, CVE-2024-40978, CVE-2024-38622,\nCVE-2024-39503, CVE-2024-40956, CVE-2023-52884, CVE-2024-39498,\nCVE-2024-38661, CVE-2024-40918, CVE-2024-39479, CVE-2024-40915,\nCVE-2024-39501, CVE-2024-39488, CVE-2024-40925, CVE-2024-40930,\nCVE-2024-40961, CVE-2024-40951, CVE-2024-38636, CVE-2024-39491,\nCVE-2024-39495, CVE-2024-39509, CVE-2024-40947, CVE-2024-36477,\nCVE-2024-36478, CVE-2024-42148, CVE-2024-39473, CVE-2024-39510,\nCVE-2024-40923, CVE-2024-38624, CVE-2024-38659, CVE-2024-36971,\nCVE-2024-38625, CVE-2024-40913, CVE-2024-35247, CVE-2024-36481,\nCVE-2024-36484, CVE-2024-40928, CVE-2024-40927, CVE-2024-40944,\nCVE-2024-39485, CVE-2024-36244, CVE-2024-40910, CVE-2024-40945,\nCVE-2024-33621, CVE-2024-38667, CVE-2024-40992, CVE-2024-40908,\nCVE-2024-40901, CVE-2024-40906, CVE-2024-38390, CVE-2024-40900,\nCVE-2024-41006, CVE-2024-40968, CVE-2024-40966, CVE-2024-40977,\nCVE-2024-33619, CVE-2024-39496, CVE-2024-38630, CVE-2024-40920,\nCVE-2024-39499, CVE-2024-40899, CVE-2024-41003, CVE-2024-40964,\nCVE-2024-40922, CVE-2024-38632, CVE-2024-40931, CVE-2024-40982,\nCVE-2024-40971, CVE-2024-39277, CVE-2024-39467, CVE-2024-36015,\nCVE-2024-40954, CVE-2024-40938, CVE-2024-40921, CVE-2024-39296,\nCVE-2024-41040, CVE-2024-40965, CVE-2024-39465, CVE-2024-40984,\nCVE-2024-39478, CVE-2024-40990, CVE-2024-40926, CVE-2024-40980,\nCVE-2024-40905, CVE-2024-39475, CVE-2024-40959, CVE-2024-40902,\nCVE-2024-38780, CVE-2024-40935, CVE-2024-37021, CVE-2024-40997,\nCVE-2024-40936, CVE-2024-40987, CVE-2024-40939, CVE-2024-37026,\nCVE-2024-36973, CVE-2024-40972, CVE-2024-42078, CVE-2024-38306,\nCVE-2024-40949, CVE-2024-36489, CVE-2024-38637, CVE-2024-40912,\nCVE-2024-39276, CVE-2024-39493, CVE-2024-40994, CVE-2024-40948,\nCVE-2024-36972, CVE-2024-40942, CVE-2024-37356, CVE-2024-38619,\nCVE-2024-40988, CVE-2024-38635, CVE-2024-41000, CVE-2024-40955,\nCVE-2024-40999, CVE-2024-40974, CVE-2024-39490, CVE-2024-39298,\nCVE-2024-40975, CVE-2024-40998, CVE-2024-40996, CVE-2024-40963,\nCVE-2024-40909, CVE-2024-40919, CVE-2024-39500, CVE-2024-39461)\n","status":"published","published":"2024-09-12T13:23:45Z","modified":"2026-10-26T22:33:28.70692352Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7005-1","title":"linux-nvidia, linux-nvidia-lowlatency vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - FPGA Framework;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Microchip PCI driver;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - PCI subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Sonic Silicon Backplane drivers;\n  - Greybus lights staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Tracing file system;\n  - IOMMU subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Core kernel;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Landlock security;\n  - Linux Security Modules (LSM) Framework;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - SOF drivers;\n  - KVM core;\n(CVE-2024-40963, CVE-2024-40994, CVE-2024-36481, CVE-2024-39301,\nCVE-2024-38390, CVE-2024-40976, CVE-2024-40934, CVE-2024-40902,\nCVE-2024-40916, CVE-2024-39298, CVE-2024-38659, CVE-2024-38384,\nCVE-2024-38635, CVE-2024-39494, CVE-2024-40926, CVE-2024-40956,\nCVE-2024-40948, CVE-2024-40920, CVE-2024-38624, CVE-2024-39498,\nCVE-2024-38780, CVE-2024-39503, CVE-2024-40919, CVE-2024-39505,\nCVE-2024-40988, CVE-2024-36972, CVE-2024-36974, CVE-2024-39495,\nCVE-2024-40992, CVE-2024-36015, CVE-2024-38618, CVE-2024-39478,\nCVE-2024-40975, CVE-2024-39507, CVE-2024-39479, CVE-2024-39291,\nCVE-2024-40925, CVE-2024-39493, CVE-2024-41005, CVE-2024-40932,\nCVE-2024-39467, CVE-2024-40973, CVE-2024-38634, CVE-2024-34027,\nCVE-2024-39462, CVE-2024-40949, CVE-2024-40908, CVE-2024-40929,\nCVE-2024-38662, CVE-2024-39489, CVE-2024-40953, CVE-2024-38306,\nCVE-2024-40915, CVE-2024-39470, CVE-2024-40969, CVE-2024-31076,\nCVE-2024-38663, CVE-2024-38629, CVE-2024-38633, CVE-2024-40959,\nCVE-2024-39475, CVE-2024-40947, CVE-2024-40971, CVE-2024-40979,\nCVE-2024-40996, CVE-2024-36484, CVE-2024-40960, CVE-2022-48772,\nCVE-2024-33619, CVE-2024-40923, CVE-2024-41006, CVE-2024-39474,\nCVE-2024-40944, CVE-2024-39473, CVE-2024-39469, CVE-2024-40914,\nCVE-2024-40900, CVE-2023-52884, CVE-2024-40931, CVE-2024-38664,\nCVE-2024-41004, CVE-2024-38636, CVE-2024-41001, CVE-2024-39497,\nCVE-2024-40974, CVE-2024-42078, CVE-2024-40954, CVE-2024-39483,\nCVE-2024-40978, CVE-2024-40952, CVE-2024-39481, CVE-2024-40955,\nCVE-2024-39471, CVE-2024-41000, CVE-2024-40972, CVE-2024-40957,\nCVE-2024-40913, CVE-2024-36478, CVE-2024-40984, CVE-2024-40990,\nCVE-2024-39510, CVE-2024-38381, CVE-2024-39277, CVE-2024-39464,\nCVE-2024-40995, CVE-2024-40905, CVE-2024-40986, CVE-2024-36971,\nCVE-2024-39480, CVE-2024-40938, CVE-2024-39509, CVE-2024-40982,\nCVE-2024-39500, CVE-2024-37026, CVE-2024-40965, CVE-2024-40961,\nCVE-2024-40989, CVE-2024-36973, CVE-2024-39504, CVE-2024-37354,\nCVE-2024-39488, CVE-2024-38661, CVE-2024-40998, CVE-2024-36489,\nCVE-2024-37021, CVE-2024-40917, CVE-2024-36281, CVE-2024-40964,\nCVE-2024-39496, CVE-2024-40980, CVE-2024-39465, CVE-2024-40983,\nCVE-2024-40936, CVE-2024-40899, CVE-2024-40933, CVE-2024-36288,\nCVE-2024-36286, CVE-2024-40987, CVE-2024-40939, CVE-2024-38667,\nCVE-2024-38628, CVE-2024-40977, CVE-2024-39276, CVE-2024-40941,\nCVE-2024-39491, CVE-2024-37078, CVE-2024-36978, CVE-2024-38623,\nCVE-2024-40962, CVE-2024-40935, CVE-2024-40997, CVE-2024-40981,\nCVE-2024-40922, CVE-2024-39461, CVE-2024-40999, CVE-2024-40918,\nCVE-2024-40927, CVE-2024-42148, CVE-2024-39371, CVE-2024-40985,\nCVE-2024-34030, CVE-2024-39485, CVE-2024-39296, CVE-2024-39466,\nCVE-2024-40909, CVE-2024-39492, CVE-2024-39502, CVE-2024-40903,\nCVE-2024-41040, CVE-2024-40968, CVE-2024-41003, CVE-2024-39499,\nCVE-2024-39508, CVE-2024-34777, CVE-2024-38627, CVE-2024-40930,\nCVE-2024-38388, CVE-2024-39490, CVE-2024-40906, CVE-2024-40940,\nCVE-2024-40937, CVE-2024-40911, CVE-2024-38385, CVE-2024-36244,\nCVE-2024-38622, CVE-2024-40958, CVE-2024-41002, CVE-2024-38621,\nCVE-2024-40970, CVE-2024-40904, CVE-2024-40928, CVE-2024-40967,\nCVE-2024-40951, CVE-2024-38637, CVE-2024-37356, CVE-2024-39463,\nCVE-2024-40912, CVE-2024-33847, CVE-2024-39468, CVE-2024-40942,\nCVE-2024-40910, CVE-2024-38625, CVE-2024-35247, CVE-2024-36479,\nCVE-2024-40943, CVE-2024-32936, CVE-2024-38630, CVE-2024-39501,\nCVE-2024-40966, CVE-2024-40921, CVE-2024-40924, CVE-2024-39506,\nCVE-2024-36270, CVE-2024-33621, CVE-2024-40945, CVE-2024-40901,\nCVE-2024-38632, CVE-2024-38619)\n","status":"published","published":"2024-09-12T13:47:54Z","modified":"2026-10-26T22:33:30.162166072Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7005-2","title":"linux-nvidia-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - FPGA Framework;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Microchip PCI driver;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - PCI subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Sonic Silicon Backplane drivers;\n  - Greybus lights staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Tracing file system;\n  - IOMMU subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Core kernel;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Landlock security;\n  - Linux Security Modules (LSM) Framework;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - SOF drivers;\n  - KVM core;\n(CVE-2024-39465, CVE-2024-39492, CVE-2024-40976, CVE-2024-40956,\nCVE-2024-39480, CVE-2024-39467, CVE-2024-39478, CVE-2024-39489,\nCVE-2024-41003, CVE-2024-39510, CVE-2024-39498, CVE-2024-40994,\nCVE-2024-40937, CVE-2024-39488, CVE-2024-40990, CVE-2024-40955,\nCVE-2024-40905, CVE-2024-39496, CVE-2024-36478, CVE-2024-40920,\nCVE-2024-40954, CVE-2024-32936, CVE-2024-40919, CVE-2024-40947,\nCVE-2024-40975, CVE-2024-39481, CVE-2024-40983, CVE-2024-39276,\nCVE-2024-37026, CVE-2024-40980, CVE-2022-48772, CVE-2024-39470,\nCVE-2024-40951, CVE-2024-40927, CVE-2024-38635, CVE-2024-40974,\nCVE-2024-39468, CVE-2024-38384, CVE-2024-37354, CVE-2024-40992,\nCVE-2024-40934, CVE-2024-40925, CVE-2024-40935, CVE-2024-39473,\nCVE-2024-40910, CVE-2024-40979, CVE-2024-39501, CVE-2024-38628,\nCVE-2024-39298, CVE-2024-40909, CVE-2024-38629, CVE-2024-41000,\nCVE-2024-40989, CVE-2024-40924, CVE-2024-40943, CVE-2024-41006,\nCVE-2024-38621, CVE-2024-39462, CVE-2024-38633, CVE-2024-40911,\nCVE-2024-39499, CVE-2024-40968, CVE-2024-40985, CVE-2024-40977,\nCVE-2024-39461, CVE-2024-40966, CVE-2024-40944, CVE-2024-39466,\nCVE-2024-38630, CVE-2024-41040, CVE-2024-39503, CVE-2024-36974,\nCVE-2024-39464, CVE-2024-40960, CVE-2024-40982, CVE-2024-36281,\nCVE-2024-40899, CVE-2024-39291, CVE-2024-40908, CVE-2024-35247,\nCVE-2024-41001, CVE-2024-39493, CVE-2024-39474, CVE-2024-39485,\nCVE-2024-36286, CVE-2024-38622, CVE-2024-36244, CVE-2024-40933,\nCVE-2024-40940, CVE-2024-39491, CVE-2024-38637, CVE-2024-38388,\nCVE-2024-40999, CVE-2024-33621, CVE-2024-34027, CVE-2024-40945,\nCVE-2024-36484, CVE-2024-40958, CVE-2024-40988, CVE-2024-40915,\nCVE-2024-39494, CVE-2024-40996, CVE-2024-38662, CVE-2024-40961,\nCVE-2024-40916, CVE-2024-40949, CVE-2024-41002, CVE-2024-39497,\nCVE-2024-40986, CVE-2024-40963, CVE-2024-33619, CVE-2024-40918,\nCVE-2024-34030, CVE-2024-33847, CVE-2024-40995, CVE-2024-40981,\nCVE-2024-40942, CVE-2024-40932, CVE-2024-39490, CVE-2024-39495,\nCVE-2024-40959, CVE-2024-39505, CVE-2024-34777, CVE-2024-39471,\nCVE-2023-52884, CVE-2024-40984, CVE-2024-40913, CVE-2024-38618,\nCVE-2024-37356, CVE-2024-40928, CVE-2024-42148, CVE-2024-39469,\nCVE-2024-38623, CVE-2024-40964, CVE-2024-38780, CVE-2024-40970,\nCVE-2024-36489, CVE-2024-36978, CVE-2024-40971, CVE-2024-40929,\nCVE-2024-31076, CVE-2024-40948, CVE-2024-40997, CVE-2024-39371,\nCVE-2024-36973, CVE-2024-40953, CVE-2024-41005, CVE-2024-40965,\nCVE-2024-39463, CVE-2024-39508, CVE-2024-37078, CVE-2024-39509,\nCVE-2024-38390, CVE-2024-38659, CVE-2024-39507, CVE-2024-36015,\nCVE-2024-40921, CVE-2024-40904, CVE-2024-40941, CVE-2024-40957,\nCVE-2024-38619, CVE-2024-40998, CVE-2024-38627, CVE-2024-39277,\nCVE-2024-40939, CVE-2024-40902, CVE-2024-38625, CVE-2024-36972,\nCVE-2024-38385, CVE-2024-38663, CVE-2024-40926, CVE-2024-40952,\nCVE-2024-40973, CVE-2024-40962, CVE-2024-40912, CVE-2024-40900,\nCVE-2024-40931, CVE-2024-36270, CVE-2024-40967, CVE-2024-39506,\nCVE-2024-36288, CVE-2024-38634, CVE-2024-39296, CVE-2024-42078,\nCVE-2024-38381, CVE-2024-40969, CVE-2024-36479, CVE-2024-38636,\nCVE-2024-39504, CVE-2024-40936, CVE-2024-38306, CVE-2024-40987,\nCVE-2024-40906, CVE-2024-40914, CVE-2024-40901, CVE-2024-40930,\nCVE-2024-40917, CVE-2024-39500, CVE-2024-36481, CVE-2024-39479,\nCVE-2024-38667, CVE-2024-39475, CVE-2024-41004, CVE-2024-40903,\nCVE-2024-36971, CVE-2024-38624, CVE-2024-39502, CVE-2024-39483,\nCVE-2024-38632, CVE-2024-40923, CVE-2024-39301, CVE-2024-38661,\nCVE-2024-40938, CVE-2024-40978, CVE-2024-40922, CVE-2024-40972,\nCVE-2024-37021, CVE-2024-38664)\n","status":"published","published":"2024-09-13T11:22:12Z","modified":"2026-10-26T22:33:28.423230775Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7006-1","title":"linux-iot vulnerabilities","description":"\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - SuperH RISC architecture;\n  - x86 architecture;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Pin controllers subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - USB subsystem;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - File systems infrastructure;\n  - NILFS2 file system;\n  - IOMMU subsystem;\n  - Sun RPC protocol;\n  - Netfilter;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - HD-audio driver;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2024-42154, CVE-2024-42093, CVE-2024-42096, CVE-2024-40984,\nCVE-2024-39502, CVE-2024-36901, CVE-2024-41044, CVE-2024-40961,\nCVE-2024-40981, CVE-2024-42236, CVE-2024-42232, CVE-2024-41041,\nCVE-2024-40958, CVE-2024-40905, CVE-2024-42084, CVE-2024-40934,\nCVE-2024-42124, CVE-2024-39505, CVE-2024-39506, CVE-2024-39501,\nCVE-2021-46926, CVE-2024-40941, CVE-2024-42145, CVE-2024-41089,\nCVE-2024-40932, CVE-2024-42224, CVE-2024-41097, CVE-2024-40959,\nCVE-2024-42157, CVE-2024-39469, CVE-2024-39499, CVE-2024-40974,\nCVE-2024-42094, CVE-2024-36894, CVE-2024-42087, CVE-2024-42104,\nCVE-2023-52803, CVE-2024-41034, CVE-2024-40995, CVE-2023-52629,\nCVE-2024-40912, CVE-2024-39484, CVE-2024-41006, CVE-2023-52760,\nCVE-2024-41095, CVE-2024-41046, CVE-2024-42070, CVE-2023-52887,\nCVE-2024-40960, CVE-2024-41007, CVE-2024-40901, CVE-2024-42119,\nCVE-2024-40987, CVE-2024-42148, CVE-2024-41049, CVE-2024-40963,\nCVE-2024-41087, CVE-2024-42223, CVE-2024-42090, CVE-2024-42105,\nCVE-2024-42089, CVE-2024-40916, CVE-2024-40942, CVE-2024-40978,\nCVE-2024-40902, CVE-2024-26921, CVE-2024-39495, CVE-2024-40943,\nCVE-2024-36978, CVE-2024-26929, CVE-2024-40988, CVE-2024-39503,\nCVE-2024-42101, CVE-2024-40904, CVE-2024-42086, CVE-2024-42106,\nCVE-2024-26830, CVE-2024-41035, CVE-2024-42153, CVE-2024-39509,\nCVE-2024-37078, CVE-2024-42076, CVE-2024-36974, CVE-2024-40980,\nCVE-2024-40945, CVE-2024-39487, CVE-2024-42092, CVE-2024-38619,\nCVE-2024-42127, CVE-2024-40968, CVE-2024-42115, CVE-2024-42102,\nCVE-2024-42097)\n","status":"published","published":"2024-09-12T14:07:21Z","modified":"2026-10-26T22:33:29.380989166Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7007-1","title":"linux, linux-aws, 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-intel-iotg, linux-intel-iotg-5.15, linux-kvm, linux-nvidia, linux-oracle, linux-raspi vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\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\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-40961, CVE-2024-38597, CVE-2024-39468, CVE-2024-36978,\nCVE-2024-42161, CVE-2024-38573, CVE-2024-40905, CVE-2024-42094,\nCVE-2024-36894, CVE-2024-40914, CVE-2024-40956, CVE-2024-42106,\nCVE-2024-38610, CVE-2024-39506, CVE-2024-42098, CVE-2024-42232,\nCVE-2024-38590, CVE-2024-39488, CVE-2024-42127, CVE-2024-41006,\nCVE-2024-42131, CVE-2024-41005, CVE-2024-40963, CVE-2024-38559,\nCVE-2024-42130, CVE-2024-37078, CVE-2024-42082, CVE-2024-40984,\nCVE-2024-38560, CVE-2024-42090, CVE-2024-33621, CVE-2024-40974,\nCVE-2024-42115, CVE-2024-40971, CVE-2024-40943, CVE-2024-38627,\nCVE-2024-38548, CVE-2024-40934, CVE-2024-38579, CVE-2024-38558,\nCVE-2024-39495, CVE-2023-52884, CVE-2024-42225, CVE-2024-38659,\nCVE-2024-40927, CVE-2024-40967, CVE-2024-38624, CVE-2024-38583,\nCVE-2024-41047, CVE-2024-38623, CVE-2024-39509, CVE-2024-36971,\nCVE-2024-42120, CVE-2024-38589, CVE-2024-36270, CVE-2024-42105,\nCVE-2024-36032, CVE-2024-42101, CVE-2024-40908, CVE-2024-42089,\nCVE-2024-39482, CVE-2024-38662, CVE-2024-41007, CVE-2024-38635,\nCVE-2023-52887, CVE-2024-40912, CVE-2024-41027, CVE-2024-38598,\nCVE-2024-38381, CVE-2024-39503, CVE-2024-39301, CVE-2024-40988,\nCVE-2024-41000, CVE-2024-39507, CVE-2024-35247, CVE-2024-39277,\nCVE-2024-42229, CVE-2024-42085, CVE-2024-35927, CVE-2024-42224,\nCVE-2024-38567, CVE-2024-42097, CVE-2024-41049, CVE-2024-39466,\nCVE-2024-40957, CVE-2024-40978, CVE-2024-42093, CVE-2024-40937,\nCVE-2024-41034, CVE-2024-41048, CVE-2024-39471, CVE-2024-39502,\nCVE-2024-38555, CVE-2024-40970, CVE-2024-36972, CVE-2024-40995,\nCVE-2024-42154, CVE-2024-40916, CVE-2024-39505, CVE-2024-39475,\nCVE-2024-38599, CVE-2024-38596, CVE-2024-39493, CVE-2024-42124,\nCVE-2024-38549, CVE-2024-42084, CVE-2024-40942, CVE-2024-42077,\nCVE-2024-42152, CVE-2024-40904, CVE-2024-31076, CVE-2024-40960,\nCVE-2024-41035, CVE-2024-40945, CVE-2024-38605, CVE-2024-42140,\nCVE-2024-41041, CVE-2024-36014, CVE-2024-38612, CVE-2024-41092,\nCVE-2024-38546, CVE-2024-40902, CVE-2024-42068, CVE-2024-42121,\nCVE-2024-42236, CVE-2024-34777, CVE-2024-39467, CVE-2024-42087,\nCVE-2024-39501, CVE-2024-40980, CVE-2024-38550, CVE-2024-42223,\nCVE-2024-38607, CVE-2024-42247, CVE-2024-41046, CVE-2024-42080,\nCVE-2024-40901, CVE-2024-38571, CVE-2024-39480, CVE-2024-42070,\nCVE-2024-41093, CVE-2024-42148, CVE-2024-38601, CVE-2024-39500,\nCVE-2024-41097, CVE-2024-38565, CVE-2024-38661, CVE-2024-38615,\nCVE-2024-41040, CVE-2024-34027, CVE-2024-37356, CVE-2024-42157,\nCVE-2024-40941, CVE-2024-38634, CVE-2024-41004, CVE-2024-38780,\nCVE-2024-38552, CVE-2024-39276, CVE-2024-38618, CVE-2024-38588,\nCVE-2024-42086, CVE-2024-41087, CVE-2024-38582, CVE-2024-40932,\nCVE-2024-39489, CVE-2024-40968, CVE-2024-42119, CVE-2024-42137,\nCVE-2024-40929, CVE-2024-38591, CVE-2024-36489, CVE-2022-48772,\nCVE-2024-42153, CVE-2024-40959, CVE-2024-40987, CVE-2024-36015,\nCVE-2024-41044, CVE-2024-41002, CVE-2024-42109, CVE-2024-38587,\nCVE-2024-36286, CVE-2024-41055, CVE-2024-39469, CVE-2024-39487,\nCVE-2024-38580, CVE-2024-38619, CVE-2024-38613, CVE-2024-42145,\nCVE-2024-41095, CVE-2024-40958, CVE-2024-40911, CVE-2024-42102,\nCVE-2024-33847, CVE-2024-36974, CVE-2024-40994, CVE-2024-38633,\nCVE-2024-40981, CVE-2024-40983, CVE-2024-42096, CVE-2024-42104,\nCVE-2024-42092, CVE-2024-40954, CVE-2024-38637, CVE-2024-42240,\nCVE-2024-38621, CVE-2024-38578, CVE-2024-38547, CVE-2024-39490,\nCVE-2024-42076, CVE-2024-42244, CVE-2024-39499, CVE-2024-38586,\nCVE-2024-41089, CVE-2024-40976, CVE-2024-42095, CVE-2024-40931,\nCVE-2024-40990)\n","status":"published","published":"2024-09-13T09:38:11Z","modified":"2026-10-26T22:35:38.116170981Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7007-2","title":"linux-ibm-5.15, linux-oracle-5.15 vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\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\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-42140, CVE-2024-38580, CVE-2024-38555, CVE-2024-38591,\nCVE-2024-40942, CVE-2024-42130, CVE-2024-41095, CVE-2024-40994,\nCVE-2024-39469, CVE-2024-38610, CVE-2024-42097, CVE-2024-42137,\nCVE-2024-31076, CVE-2024-38552, CVE-2024-36489, CVE-2024-40983,\nCVE-2024-40908, CVE-2024-39493, CVE-2024-40970, CVE-2024-40901,\nCVE-2024-38567, CVE-2024-38599, CVE-2024-38605, CVE-2024-42119,\nCVE-2024-38590, CVE-2024-38558, CVE-2023-52884, CVE-2024-41000,\nCVE-2024-42101, CVE-2024-40943, CVE-2024-39507, CVE-2024-42115,\nCVE-2024-40968, CVE-2024-42095, CVE-2024-41034, CVE-2024-38618,\nCVE-2024-38633, CVE-2024-40904, CVE-2024-42070, CVE-2024-38583,\nCVE-2024-39471, CVE-2024-38578, CVE-2024-38637, CVE-2024-40987,\nCVE-2024-39506, CVE-2024-39482, CVE-2024-42124, CVE-2024-40981,\nCVE-2024-35927, CVE-2022-48772, CVE-2024-38588, CVE-2023-52887,\nCVE-2024-40941, CVE-2024-34027, CVE-2024-38627, CVE-2024-42106,\nCVE-2024-40927, CVE-2024-38559, CVE-2024-39499, CVE-2024-39505,\nCVE-2024-42120, CVE-2024-38615, CVE-2024-39467, CVE-2024-42232,\nCVE-2024-38589, CVE-2024-38621, CVE-2024-41002, CVE-2024-40934,\nCVE-2024-38582, CVE-2024-39480, CVE-2024-38571, CVE-2024-39301,\nCVE-2024-38612, CVE-2024-39495, CVE-2024-39276, CVE-2024-42096,\nCVE-2024-41041, CVE-2024-40912, CVE-2024-41089, CVE-2024-41093,\nCVE-2024-40931, CVE-2024-42092, CVE-2024-41047, CVE-2024-40956,\nCVE-2024-42229, CVE-2024-40914, CVE-2024-39490, CVE-2024-38548,\nCVE-2024-41044, CVE-2024-40967, CVE-2024-38596, CVE-2024-40902,\nCVE-2024-41055, CVE-2024-38601, CVE-2024-42153, CVE-2024-38623,\nCVE-2024-35247, CVE-2024-38635, CVE-2024-38662, CVE-2024-42086,\nCVE-2024-42102, CVE-2024-42154, CVE-2024-38587, CVE-2024-39466,\nCVE-2024-40911, CVE-2024-39503, CVE-2024-42090, CVE-2024-42087,\nCVE-2024-40929, CVE-2024-37078, CVE-2024-39489, CVE-2024-42244,\nCVE-2024-40980, CVE-2024-38624, CVE-2024-42105, CVE-2024-36270,\nCVE-2024-41092, CVE-2024-40937, CVE-2024-38780, CVE-2024-41035,\nCVE-2024-42104, CVE-2024-40988, CVE-2024-36894, CVE-2024-42157,\nCVE-2024-38613, CVE-2024-40916, CVE-2024-41040, CVE-2024-36032,\nCVE-2024-40978, CVE-2024-38579, CVE-2024-38550, CVE-2024-41049,\nCVE-2024-40959, CVE-2024-42131, CVE-2024-42161, CVE-2024-42247,\nCVE-2024-37356, CVE-2024-40905, CVE-2024-42098, CVE-2024-40932,\nCVE-2024-42236, CVE-2024-38565, CVE-2024-38661, CVE-2024-40963,\nCVE-2024-42240, CVE-2024-40984, CVE-2024-39277, CVE-2024-38573,\nCVE-2024-39509, CVE-2024-41006, CVE-2024-34777, CVE-2024-42152,\nCVE-2024-40954, CVE-2024-39501, CVE-2024-42109, CVE-2024-42080,\nCVE-2024-42225, CVE-2024-41007, CVE-2024-42077, CVE-2024-38634,\nCVE-2024-40995, CVE-2024-42084, CVE-2024-40974, CVE-2024-38586,\nCVE-2024-42224, CVE-2024-40960, CVE-2024-39500, CVE-2024-41004,\nCVE-2024-42145, CVE-2024-38619, CVE-2024-36974, CVE-2024-39502,\nCVE-2024-41097, CVE-2024-40958, CVE-2024-41027, CVE-2024-36972,\nCVE-2024-36286, CVE-2024-40990, CVE-2024-42082, CVE-2024-40945,\nCVE-2024-36014, CVE-2024-42068, CVE-2024-41087, CVE-2024-36978,\nCVE-2024-42148, CVE-2024-40971, CVE-2024-38546, CVE-2024-39488,\nCVE-2024-41048, CVE-2024-42121, CVE-2024-38381, CVE-2024-41046,\nCVE-2024-36971, CVE-2024-42085, CVE-2024-39487, CVE-2024-33847,\nCVE-2024-38607, CVE-2024-33621, CVE-2024-40957, CVE-2024-42127,\nCVE-2024-38547, CVE-2024-36015, CVE-2024-38549, CVE-2024-38597,\nCVE-2024-42093, CVE-2024-42089, CVE-2024-39468, CVE-2024-38560,\nCVE-2024-42223, CVE-2024-38659, CVE-2024-38598, CVE-2024-40976,\nCVE-2024-42094, CVE-2024-41005, CVE-2024-39475, CVE-2024-40961,\nCVE-2024-42076)\n","status":"published","published":"2024-09-23T09:59:41Z","modified":"2026-10-26T22:33:05.953947064Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7007-3","title":"linux-lowlatency, linux-lowlatency-hwe-5.15 vulnerabilities","description":"Chenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\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\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-42105, CVE-2024-41002, CVE-2024-38558, CVE-2023-52887,\nCVE-2024-39487, CVE-2024-39276, CVE-2024-42077, CVE-2024-39493,\nCVE-2024-40934, CVE-2024-39277, CVE-2024-42087, CVE-2024-38598,\nCVE-2024-38618, CVE-2024-40981, CVE-2024-42127, CVE-2024-38607,\nCVE-2024-38586, CVE-2024-40901, CVE-2024-40916, CVE-2024-42247,\nCVE-2024-42093, CVE-2024-36489, CVE-2024-38615, CVE-2024-42120,\nCVE-2024-38567, CVE-2024-40957, CVE-2024-39501, CVE-2024-42140,\nCVE-2024-33621, CVE-2024-38573, CVE-2023-52884, CVE-2024-39468,\nCVE-2024-41092, CVE-2024-40931, CVE-2024-42145, CVE-2024-39490,\nCVE-2024-38555, CVE-2024-42086, CVE-2024-38597, CVE-2024-40956,\nCVE-2024-42223, CVE-2024-36894, CVE-2024-40961, CVE-2024-42076,\nCVE-2024-40994, CVE-2024-38619, CVE-2024-39467, CVE-2024-39466,\nCVE-2022-48772, CVE-2024-39507, CVE-2024-40914, CVE-2024-41046,\nCVE-2024-42094, CVE-2024-38591, CVE-2024-42098, CVE-2024-41027,\nCVE-2024-41040, CVE-2024-41089, CVE-2024-40945, CVE-2024-39503,\nCVE-2024-37356, CVE-2024-36286, CVE-2024-39495, CVE-2024-42101,\nCVE-2024-40941, CVE-2024-42137, CVE-2024-38381, CVE-2024-38627,\nCVE-2024-31076, CVE-2024-42092, CVE-2024-40932, CVE-2024-40995,\nCVE-2024-40937, CVE-2024-39489, CVE-2024-42084, CVE-2024-40929,\nCVE-2024-36978, CVE-2024-36015, CVE-2024-36014, CVE-2024-42124,\nCVE-2024-40976, CVE-2024-39502, CVE-2024-38599, CVE-2024-38661,\nCVE-2024-42104, CVE-2024-42096, CVE-2024-40904, CVE-2024-40990,\nCVE-2024-38579, CVE-2024-40974, CVE-2024-41055, CVE-2024-38633,\nCVE-2024-38659, CVE-2024-41093, CVE-2024-42154, CVE-2024-38624,\nCVE-2024-41049, CVE-2024-38552, CVE-2024-38578, CVE-2024-38605,\nCVE-2024-40970, CVE-2024-38601, CVE-2024-38550, CVE-2024-38559,\nCVE-2024-38571, CVE-2024-40971, CVE-2024-41097, CVE-2024-40967,\nCVE-2024-38612, CVE-2024-38587, CVE-2024-41004, CVE-2024-33847,\nCVE-2024-38580, CVE-2024-39506, CVE-2024-42102, CVE-2024-36032,\nCVE-2024-38548, CVE-2024-39499, CVE-2024-38610, CVE-2024-42152,\nCVE-2024-40943, CVE-2024-40959, CVE-2024-39488, CVE-2024-36972,\nCVE-2024-38637, CVE-2024-40942, CVE-2024-42106, CVE-2024-38546,\nCVE-2024-38634, CVE-2024-39471, CVE-2024-39482, CVE-2024-41095,\nCVE-2024-42229, CVE-2024-42131, CVE-2024-41007, CVE-2024-42095,\nCVE-2024-42097, CVE-2024-39480, CVE-2024-35927, CVE-2024-42153,\nCVE-2024-42080, CVE-2024-42089, CVE-2024-41087, CVE-2024-39475,\nCVE-2024-42119, CVE-2024-41041, CVE-2024-38623, CVE-2024-39469,\nCVE-2024-34777, CVE-2024-42157, CVE-2024-42085, CVE-2024-36270,\nCVE-2024-34027, CVE-2024-35247, CVE-2024-38549, CVE-2024-40954,\nCVE-2024-41034, CVE-2024-41044, CVE-2024-39509, CVE-2024-40987,\nCVE-2024-42161, CVE-2024-40911, CVE-2024-42070, CVE-2024-42109,\nCVE-2024-37078, CVE-2024-40912, CVE-2024-40988, CVE-2024-40978,\nCVE-2024-41048, CVE-2024-41005, CVE-2024-40905, CVE-2024-41047,\nCVE-2024-41006, CVE-2024-38560, CVE-2024-42225, CVE-2024-42148,\nCVE-2024-38596, CVE-2024-38588, CVE-2024-39301, CVE-2024-38613,\nCVE-2024-38635, CVE-2024-40960, CVE-2024-39505, CVE-2024-42244,\nCVE-2024-40963, CVE-2024-39500, CVE-2024-42082, CVE-2024-36971,\nCVE-2024-42068, CVE-2024-40984, CVE-2024-41035, CVE-2024-38583,\nCVE-2024-42121, CVE-2024-40968, CVE-2024-40958, CVE-2024-40927,\nCVE-2024-40980, CVE-2024-40908, CVE-2024-38780, CVE-2024-38590,\nCVE-2024-42115, CVE-2024-42224, CVE-2024-42232, CVE-2024-42240,\nCVE-2024-42236, CVE-2024-38547, CVE-2024-38565, CVE-2024-40902,\nCVE-2024-38662, CVE-2024-42090, CVE-2024-36974, CVE-2024-38621,\nCVE-2024-41000, CVE-2024-40983, CVE-2024-42130, CVE-2024-38582,\nCVE-2024-38589)\n","status":"published","published":"2024-09-23T15:52:38Z","modified":"2026-10-26T22:33:37.683464668Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7008-1","title":"linux-lowlatency-hwe-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - FPGA Framework;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Microchip PCI driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - PCI subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Sonic Silicon Backplane drivers;\n  - Greybus lights staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Tracing file system;\n  - IOMMU subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Core kernel;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Landlock security;\n  - Linux Security Modules (LSM) Framework;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - SOF drivers;\n  - KVM core;\n(CVE-2024-38623, CVE-2024-38662, CVE-2024-39484, CVE-2024-42148,\nCVE-2024-39493, CVE-2024-38637, CVE-2024-40962, CVE-2024-36281,\nCVE-2024-40922, CVE-2024-40958, CVE-2024-40920, CVE-2024-40986,\nCVE-2024-40929, CVE-2024-40967, CVE-2024-39296, CVE-2024-40900,\nCVE-2024-40995, CVE-2024-40974, CVE-2024-40942, CVE-2024-39464,\nCVE-2024-40916, CVE-2024-40952, CVE-2024-40997, CVE-2024-41004,\nCVE-2024-40970, CVE-2024-40911, CVE-2024-40972, CVE-2024-36477,\nCVE-2024-40996, CVE-2024-40988, CVE-2024-38619, CVE-2024-40998,\nCVE-2024-38627, CVE-2024-36971, CVE-2024-37021, CVE-2024-40989,\nCVE-2024-40947, CVE-2024-40957, CVE-2024-39508, CVE-2024-41005,\nCVE-2024-40931, CVE-2024-34777, CVE-2024-38633, CVE-2024-38663,\nCVE-2024-36288, CVE-2024-40955, CVE-2024-40973, CVE-2024-39483,\nCVE-2024-38388, CVE-2024-40976, CVE-2024-38622, CVE-2024-40915,\nCVE-2024-38661, CVE-2024-38306, CVE-2024-39507, CVE-2024-38659,\nCVE-2024-40980, CVE-2024-39301, CVE-2024-40945, CVE-2024-39461,\nCVE-2024-40948, CVE-2024-39465, CVE-2024-38667, CVE-2024-39498,\nCVE-2024-39470, CVE-2024-38629, CVE-2024-40984, CVE-2024-38381,\nCVE-2024-40903, CVE-2024-38636, CVE-2024-36478, CVE-2023-52884,\nCVE-2024-40906, CVE-2024-39371, CVE-2024-38384, CVE-2024-40938,\nCVE-2024-36978, CVE-2024-39502, CVE-2024-39291, CVE-2024-39473,\nCVE-2024-40956, CVE-2024-38618, CVE-2024-40992, CVE-2024-40944,\nCVE-2024-39495, CVE-2024-39494, CVE-2024-38632, CVE-2024-38390,\nCVE-2024-39497, CVE-2024-40899, CVE-2024-40939, CVE-2024-36481,\nCVE-2024-40977, CVE-2024-40961, CVE-2024-33847, CVE-2024-40963,\nCVE-2024-39276, CVE-2024-40902, CVE-2024-40971, CVE-2024-39485,\nCVE-2024-40930, CVE-2024-40985, CVE-2024-39501, CVE-2024-40960,\nCVE-2024-39503, CVE-2024-40909, CVE-2024-36973, CVE-2024-36489,\nCVE-2024-40928, CVE-2024-34027, CVE-2024-40914, CVE-2024-40925,\nCVE-2024-39500, CVE-2024-39292, CVE-2024-40987, CVE-2024-39480,\nCVE-2024-40934, CVE-2024-36270, CVE-2024-38780, CVE-2024-39479,\nCVE-2024-39462, CVE-2024-40966, CVE-2024-39510, CVE-2024-39471,\nCVE-2024-39505, CVE-2024-37078, CVE-2024-40913, CVE-2024-37356,\nCVE-2024-38624, CVE-2024-40917, CVE-2024-39506, CVE-2024-40943,\nCVE-2024-38625, CVE-2024-38664, CVE-2024-40901, CVE-2024-40964,\nCVE-2024-40924, CVE-2024-40918, CVE-2024-36974, CVE-2022-48772,\nCVE-2024-39509, CVE-2024-38385, CVE-2024-40994, CVE-2024-39469,\nCVE-2024-40905, CVE-2024-35247, CVE-2024-41006, CVE-2024-40965,\nCVE-2024-40932, CVE-2024-39491, CVE-2024-39499, CVE-2024-40908,\nCVE-2024-36972, CVE-2024-37026, CVE-2024-40968, CVE-2024-36244,\nCVE-2024-39468, CVE-2024-39489, CVE-2024-33621, CVE-2024-40951,\nCVE-2024-39481, CVE-2024-40959, CVE-2024-40935, CVE-2024-40927,\nCVE-2024-40912, CVE-2024-36479, CVE-2024-39467, CVE-2024-34030,\nCVE-2024-41003, CVE-2024-40936, CVE-2024-39474, CVE-2024-40969,\nCVE-2024-40904, CVE-2024-40937, CVE-2024-40978, CVE-2024-40983,\nCVE-2024-40910, CVE-2024-39466, CVE-2024-40949, CVE-2024-39478,\nCVE-2024-40999, CVE-2024-33619, CVE-2024-38621, CVE-2024-40981,\nCVE-2024-39475, CVE-2024-40954, CVE-2024-41000, CVE-2024-39496,\nCVE-2024-40926, CVE-2024-41040, CVE-2024-39298, CVE-2024-38635,\nCVE-2024-39492, CVE-2024-38628, CVE-2024-39504, CVE-2024-42078,\nCVE-2024-41001, CVE-2024-39463, CVE-2024-36286, CVE-2024-36484,\nCVE-2024-40990, CVE-2024-31076, CVE-2024-38630, CVE-2024-40979,\nCVE-2024-36015, CVE-2024-40923, CVE-2024-40921, CVE-2024-41002,\nCVE-2024-40940, CVE-2024-40975, CVE-2024-40953, CVE-2024-40933,\nCVE-2024-37354, CVE-2024-40982, CVE-2024-38634, CVE-2024-39490,\nCVE-2024-39277, CVE-2024-39488, CVE-2024-40941, CVE-2024-32936,\nCVE-2024-40919)\n","status":"published","published":"2024-09-13T10:51:48Z","modified":"2026-10-26T22:33:27.842467788Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7009-1","title":"linux-azure, linux-azure-5.15, linux-azure-fde vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\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\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-38613, CVE-2024-42096, CVE-2024-40908, CVE-2024-42137,\nCVE-2024-38590, CVE-2024-41044, CVE-2024-39480, CVE-2024-39469,\nCVE-2024-39471, CVE-2024-42089, CVE-2024-38588, CVE-2024-41092,\nCVE-2024-42120, CVE-2024-40901, CVE-2024-40981, CVE-2024-42127,\nCVE-2024-40932, CVE-2024-39475, CVE-2024-40957, CVE-2024-39501,\nCVE-2024-42090, CVE-2024-40904, CVE-2024-40978, CVE-2022-48772,\nCVE-2024-40934, CVE-2024-38548, CVE-2024-41005, CVE-2024-36489,\nCVE-2024-36978, CVE-2024-38573, CVE-2024-42106, CVE-2024-42104,\nCVE-2024-42085, CVE-2024-38621, CVE-2024-42098, CVE-2024-38662,\nCVE-2024-38587, CVE-2024-41089, CVE-2024-42095, CVE-2024-40916,\nCVE-2024-39487, CVE-2024-42229, CVE-2023-52884, CVE-2024-40974,\nCVE-2024-40980, CVE-2024-42225, CVE-2024-39502, CVE-2024-37356,\nCVE-2024-39488, CVE-2024-40912, CVE-2024-39507, CVE-2024-38591,\nCVE-2024-31076, CVE-2024-40984, CVE-2024-39500, CVE-2024-38582,\nCVE-2024-34027, CVE-2024-36270, CVE-2024-42076, CVE-2024-42247,\nCVE-2024-42154, CVE-2024-41047, CVE-2024-42244, CVE-2024-41049,\nCVE-2024-33847, CVE-2024-36015, CVE-2024-42161, CVE-2024-42082,\nCVE-2024-41048, CVE-2024-40961, CVE-2024-41000, CVE-2024-38598,\nCVE-2024-41040, CVE-2024-36971, CVE-2024-41007, CVE-2024-36972,\nCVE-2024-38610, CVE-2024-40937, CVE-2024-38615, CVE-2024-38555,\nCVE-2024-40943, CVE-2024-39466, CVE-2024-40990, CVE-2024-42115,\nCVE-2024-40995, CVE-2024-38612, CVE-2024-40987, CVE-2024-38558,\nCVE-2024-42236, CVE-2024-38381, CVE-2024-42157, CVE-2024-38560,\nCVE-2024-42101, CVE-2024-40970, CVE-2024-42094, CVE-2024-42148,\nCVE-2024-35247, CVE-2024-40963, CVE-2024-38580, CVE-2024-38633,\nCVE-2024-38637, CVE-2024-40905, CVE-2024-41093, CVE-2024-38619,\nCVE-2024-42093, CVE-2024-40945, CVE-2024-42092, CVE-2024-36286,\nCVE-2024-40954, CVE-2024-41041, CVE-2024-38571, CVE-2024-39503,\nCVE-2024-38546, CVE-2024-40976, CVE-2024-36014, CVE-2024-41087,\nCVE-2024-42109, CVE-2024-42070, CVE-2024-42080, CVE-2024-41006,\nCVE-2024-42145, CVE-2024-40960, CVE-2024-38597, CVE-2024-42086,\nCVE-2024-40967, CVE-2024-42130, CVE-2024-42153, CVE-2024-39509,\nCVE-2024-40914, CVE-2024-39277, CVE-2024-41055, CVE-2024-41095,\nCVE-2024-38780, CVE-2024-36974, CVE-2024-38607, CVE-2024-38583,\nCVE-2024-40927, CVE-2024-39490, CVE-2024-38599, CVE-2023-52887,\nCVE-2024-38565, CVE-2024-38552, CVE-2024-40942, CVE-2024-37078,\nCVE-2024-40911, CVE-2024-41035, CVE-2024-38550, CVE-2024-42102,\nCVE-2024-42121, CVE-2024-36032, CVE-2024-42240, CVE-2024-42140,\nCVE-2024-38589, CVE-2024-40931, CVE-2024-39505, CVE-2024-38596,\nCVE-2024-42223, CVE-2024-38567, CVE-2024-39495, CVE-2024-40959,\nCVE-2024-38586, CVE-2024-42087, CVE-2024-38661, CVE-2024-41097,\nCVE-2024-38559, CVE-2024-38618, CVE-2024-39493, CVE-2024-41002,\nCVE-2024-40958, CVE-2024-39468, CVE-2024-38601, CVE-2024-39499,\nCVE-2024-39482, CVE-2024-38579, CVE-2024-42077, CVE-2024-38578,\nCVE-2024-34777, CVE-2024-39301, CVE-2024-38605, CVE-2024-42131,\nCVE-2024-42084, CVE-2024-41027, CVE-2024-40968, CVE-2024-38547,\nCVE-2024-42119, CVE-2024-38627, CVE-2024-40941, CVE-2024-40994,\nCVE-2024-40988, CVE-2024-40902, CVE-2024-41046, CVE-2024-38549,\nCVE-2024-39506, CVE-2024-38634, CVE-2024-42124, CVE-2024-42105,\nCVE-2024-38623, CVE-2024-38624, CVE-2024-33621, CVE-2024-42068,\nCVE-2024-36894, CVE-2024-39489, CVE-2024-42270, CVE-2024-40929,\nCVE-2024-39276, CVE-2024-42152, CVE-2024-41034, CVE-2024-40983,\nCVE-2024-42224, CVE-2024-40956, CVE-2024-40971, CVE-2024-38635,\nCVE-2024-42097, CVE-2024-42232, CVE-2024-38659, CVE-2024-39467,\nCVE-2024-41004)\n","status":"published","published":"2024-09-13T11:47:02Z","modified":"2026-10-26T22:33:39.46132957Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7009-2","title":"linux-azure-fde-5.15 vulnerabilities","description":"Chenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\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\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-42076, CVE-2024-40994, CVE-2024-40932, CVE-2024-41000,\nCVE-2024-42224, CVE-2024-38633, CVE-2024-40954, CVE-2024-36270,\nCVE-2024-38623, CVE-2024-38549, CVE-2024-42225, CVE-2024-42085,\nCVE-2024-42157, CVE-2024-42229, CVE-2024-42109, CVE-2024-41040,\nCVE-2024-38607, CVE-2024-39493, CVE-2024-38546, CVE-2024-41046,\nCVE-2024-38567, CVE-2024-42092, CVE-2024-39501, CVE-2024-41005,\nCVE-2024-42223, CVE-2024-39480, CVE-2024-38571, CVE-2024-41048,\nCVE-2024-38605, CVE-2024-42094, CVE-2024-38598, CVE-2024-38559,\nCVE-2024-38558, CVE-2024-40931, CVE-2024-40942, CVE-2024-39495,\nCVE-2024-40981, CVE-2024-40911, CVE-2024-42148, CVE-2024-33621,\nCVE-2024-39502, CVE-2024-41095, CVE-2024-40960, CVE-2024-36286,\nCVE-2024-42232, CVE-2024-42130, CVE-2024-42154, CVE-2024-41087,\nCVE-2024-41004, CVE-2024-39277, CVE-2024-38560, CVE-2024-36978,\nCVE-2024-42089, CVE-2024-37356, CVE-2024-38547, CVE-2024-38381,\nCVE-2024-36015, CVE-2024-38548, CVE-2024-42120, CVE-2024-41092,\nCVE-2024-40978, CVE-2024-38619, CVE-2024-40914, CVE-2024-41089,\nCVE-2024-40988, CVE-2024-41047, CVE-2024-38565, CVE-2024-38550,\nCVE-2023-52887, CVE-2024-38552, CVE-2024-38583, CVE-2024-38613,\nCVE-2024-40967, CVE-2024-40927, CVE-2024-42124, CVE-2024-42244,\nCVE-2024-42152, CVE-2024-39509, CVE-2024-38662, CVE-2024-38618,\nCVE-2024-42140, CVE-2024-38579, CVE-2024-40945, CVE-2024-42101,\nCVE-2024-42104, CVE-2024-41044, CVE-2024-42161, CVE-2024-42093,\nCVE-2024-42270, CVE-2024-42097, CVE-2024-40970, CVE-2024-40908,\nCVE-2024-38582, CVE-2024-42247, CVE-2024-38661, CVE-2024-40941,\nCVE-2024-42084, CVE-2024-42090, CVE-2024-42131, CVE-2024-42077,\nCVE-2024-40995, CVE-2024-42105, CVE-2024-41035, CVE-2024-41097,\nCVE-2024-38780, CVE-2024-35247, CVE-2024-36974, CVE-2024-42070,\nCVE-2024-40902, CVE-2024-36972, CVE-2024-38586, CVE-2024-38573,\nCVE-2024-38612, CVE-2024-42121, CVE-2023-52884, CVE-2024-39276,\nCVE-2024-38615, CVE-2024-42095, CVE-2024-42086, CVE-2024-39507,\nCVE-2024-40983, CVE-2024-40943, CVE-2024-41002, CVE-2024-40958,\nCVE-2024-41049, CVE-2024-38596, CVE-2024-37078, CVE-2024-38637,\nCVE-2024-38621, CVE-2024-42153, CVE-2024-38659, CVE-2024-39468,\nCVE-2024-38589, CVE-2024-38587, CVE-2024-36971, CVE-2024-38599,\nCVE-2024-31076, CVE-2024-39490, CVE-2024-40959, CVE-2024-38634,\nCVE-2024-38624, CVE-2024-42240, CVE-2024-42127, CVE-2024-42102,\nCVE-2024-38578, CVE-2024-34027, CVE-2024-38601, CVE-2024-42087,\nCVE-2024-38597, CVE-2024-38591, CVE-2024-39503, CVE-2024-42236,\nCVE-2024-42082, CVE-2024-40956, CVE-2024-41041, CVE-2024-38580,\nCVE-2024-39506, CVE-2024-36894, CVE-2024-40987, CVE-2024-39475,\nCVE-2024-38635, CVE-2024-41007, CVE-2024-39471, CVE-2024-39467,\nCVE-2022-48772, CVE-2024-40934, CVE-2024-42106, CVE-2024-39469,\nCVE-2024-40963, CVE-2024-39482, CVE-2024-39505, CVE-2024-36014,\nCVE-2024-39500, CVE-2024-42096, CVE-2024-41055, CVE-2024-40937,\nCVE-2024-38590, CVE-2024-38610, CVE-2024-41034, CVE-2024-42115,\nCVE-2024-40974, CVE-2024-40968, CVE-2024-42080, CVE-2024-40957,\nCVE-2024-40971, CVE-2024-36032, CVE-2024-39499, CVE-2024-42137,\nCVE-2024-39489, CVE-2024-40976, CVE-2024-39466, CVE-2024-42145,\nCVE-2024-36489, CVE-2024-40980, CVE-2024-39301, CVE-2024-40905,\nCVE-2024-41093, CVE-2024-40912, CVE-2024-42119, CVE-2024-38588,\nCVE-2024-40916, CVE-2024-39488, CVE-2024-41027, CVE-2024-42068,\nCVE-2024-40904, CVE-2024-40961, CVE-2024-33847, CVE-2024-38555,\nCVE-2024-41006, CVE-2024-40929, CVE-2024-34777, CVE-2024-38627,\nCVE-2024-40984, CVE-2024-40990, CVE-2024-39487, CVE-2024-42098,\nCVE-2024-40901)\n","status":"published","published":"2024-09-25T08:27:37Z","modified":"2026-08-06T03:07:31.441367086Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7019-1","title":"linux-xilinx-zynqmp vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nBenedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde\ndiscovered that an untrusted hypervisor could inject malicious #VC\ninterrupts and compromise the security guarantees of AMD SEV-SNP. This flaw\nis known as WeSee. A local attacker in control of the hypervisor could use\nthis to expose sensitive information or possibly execute arbitrary code in\nthe trusted execution environment. (CVE-2024-25742)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FireWire subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Trusted Execution Environment drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Xen hypervisor drivers;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - eCrypt file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Core kernel;\n  - Tracing infrastructure;\n  - Dynamic debug library;\n  - PCI iomap interfaces;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - ALSA SH drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n  - KVM core;\n(CVE-2024-42085, CVE-2024-42154, CVE-2024-42229, CVE-2024-38548,\nCVE-2024-42120, CVE-2024-38555, CVE-2024-38598, CVE-2024-40954,\nCVE-2024-38571, CVE-2024-36020, CVE-2024-36270, CVE-2024-39482,\nCVE-2024-39468, CVE-2024-38607, CVE-2024-26923, CVE-2024-42145,\nCVE-2024-41040, CVE-2024-35852, CVE-2024-35805, CVE-2024-35890,\nCVE-2024-36965, CVE-2024-42077, CVE-2024-26958, CVE-2024-35823,\nCVE-2024-42124, CVE-2024-26680, CVE-2024-38549, CVE-2024-36286,\nCVE-2024-27398, CVE-2024-35990, CVE-2024-36975, CVE-2024-27437,\nCVE-2024-35848, CVE-2024-26900, CVE-2024-26654, CVE-2024-40971,\nCVE-2024-35847, CVE-2024-35982, CVE-2024-42232, CVE-2022-48808,\nCVE-2024-35822, CVE-2024-36950, CVE-2024-33621, CVE-2024-39276,\nCVE-2024-40968, CVE-2024-35857, CVE-2024-40905, CVE-2023-52880,\nCVE-2024-35819, CVE-2024-35791, CVE-2024-42076, CVE-2024-40904,\nCVE-2024-35976, CVE-2024-35854, CVE-2024-26642, CVE-2024-27393,\nCVE-2024-26934, CVE-2024-26960, CVE-2024-42137, CVE-2024-38588,\nCVE-2024-40970, CVE-2024-36972, CVE-2024-26977, CVE-2024-38546,\nCVE-2024-41095, CVE-2024-39292, CVE-2024-41087, CVE-2024-33847,\nCVE-2024-40978, CVE-2024-41049, CVE-2024-35895, CVE-2024-35804,\nCVE-2024-42093, CVE-2024-36017, CVE-2024-38591, CVE-2024-42080,\nCVE-2024-41089, CVE-2024-38613, CVE-2024-39466, CVE-2024-40931,\nCVE-2024-35907, CVE-2024-36919, CVE-2024-36934, CVE-2024-42240,\nCVE-2024-35940, CVE-2024-36938, CVE-2024-42121, CVE-2024-39490,\nCVE-2024-40961, CVE-2024-42223, CVE-2024-41041, CVE-2024-41093,\nCVE-2024-42068, CVE-2024-41044, CVE-2024-42086, CVE-2024-42105,\nCVE-2024-36954, CVE-2024-35796, CVE-2024-38610, CVE-2024-36929,\nCVE-2024-35893, CVE-2024-38601, CVE-2024-40981, CVE-2024-36889,\nCVE-2024-27015, CVE-2024-35897, CVE-2024-39469, CVE-2024-35825,\nCVE-2024-26922, CVE-2024-38573, CVE-2024-42130, CVE-2024-38580,\nCVE-2024-26814, CVE-2024-36955, CVE-2024-26813, CVE-2024-27396,\nCVE-2024-36937, CVE-2024-36928, CVE-2024-42224, CVE-2024-27004,\nCVE-2024-42104, CVE-2024-42225, CVE-2024-38659, CVE-2024-35955,\nCVE-2024-42106, CVE-2024-39489, CVE-2024-31076, CVE-2024-26817,\nCVE-2024-35884, CVE-2024-42095, CVE-2024-42131, CVE-2024-40956,\nCVE-2024-40941, CVE-2024-36007, CVE-2024-27009, CVE-2024-40959,\nCVE-2024-42089, CVE-2024-37078, CVE-2024-35960, CVE-2024-41002,\nCVE-2024-39301, CVE-2024-35988, CVE-2023-52887, CVE-2024-35885,\nCVE-2024-39484, CVE-2024-35872, CVE-2024-40974, CVE-2024-35851,\nCVE-2024-26957, CVE-2024-38623, CVE-2024-35944, CVE-2024-41005,\nCVE-2024-42152, CVE-2024-35888, CVE-2024-38621, CVE-2024-26989,\nCVE-2024-42148, CVE-2024-27401, CVE-2024-36883, CVE-2024-35855,\nCVE-2024-26936, CVE-2024-26935, CVE-2022-48772, CVE-2024-35853,\nCVE-2024-35997, CVE-2024-27059, CVE-2024-36953, CVE-2024-35969,\nCVE-2024-42094, CVE-2024-38661, CVE-2024-35925, CVE-2024-40914,\nCVE-2024-36940, CVE-2024-27016, CVE-2024-26828, CVE-2024-40911,\nCVE-2024-38634, CVE-2024-38558, CVE-2024-38582, CVE-2023-52629,\nCVE-2024-27020, CVE-2024-35247, CVE-2024-26999, CVE-2024-26687,\nCVE-2024-38565, CVE-2024-38612, CVE-2024-39495, CVE-2024-26974,\nCVE-2024-42101, CVE-2024-38597, CVE-2024-26929, CVE-2024-40927,\nCVE-2024-26830, CVE-2024-26973, CVE-2024-40980, CVE-2024-38560,\nCVE-2024-41047, CVE-2024-42098, CVE-2024-39507, CVE-2024-38599,\nCVE-2024-35789, CVE-2024-27395, CVE-2024-41092, CVE-2024-42161,\nCVE-2024-41006, CVE-2024-36931, CVE-2024-38619, CVE-2024-35813,\nCVE-2024-35898, CVE-2024-41027, CVE-2024-40932, CVE-2024-40960,\nCVE-2024-26925, CVE-2024-41048, CVE-2024-36886, CVE-2024-35877,\nCVE-2024-40963, CVE-2024-36960, CVE-2024-38590, CVE-2024-40902,\nCVE-2024-35871, CVE-2024-38579, CVE-2024-40987, CVE-2024-36025,\nCVE-2024-35806, CVE-2024-35899, CVE-2024-26993, CVE-2024-41097,\nCVE-2024-39488, CVE-2024-42115, CVE-2024-42127, CVE-2024-37356,\nCVE-2024-26812, CVE-2024-36939, CVE-2024-35807, CVE-2024-26886,\nCVE-2024-35809, CVE-2024-40937, CVE-2024-35970, CVE-2024-35817,\nCVE-2024-35973, CVE-2024-40945, CVE-2024-42153, CVE-2024-36964,\nCVE-2024-42090, CVE-2024-38552, CVE-2024-39467, CVE-2024-26961,\nCVE-2024-38615, CVE-2024-38618, CVE-2024-40988, CVE-2024-38605,\nCVE-2024-41004, CVE-2024-26966, CVE-2024-42096, CVE-2024-26996,\nCVE-2024-36969, CVE-2024-36489, CVE-2024-40957, CVE-2024-36974,\nCVE-2024-39502, CVE-2024-26976, CVE-2024-27399, CVE-2024-36905,\nCVE-2024-35958, CVE-2024-35927, CVE-2024-27001, CVE-2024-39487,\nCVE-2024-41034, CVE-2024-36904, CVE-2024-41055, CVE-2024-38550,\nCVE-2024-38567, CVE-2024-38586, CVE-2024-40916, CVE-2024-38589,\nCVE-2023-52884, CVE-2024-26810, CVE-2024-35989, CVE-2024-36894,\nCVE-2024-39471, CVE-2024-35900, CVE-2024-42097, CVE-2024-36959,\nCVE-2024-26931, CVE-2024-40934, CVE-2024-36947, CVE-2024-34777,\nCVE-2024-27018, CVE-2024-39499, CVE-2024-36906, CVE-2024-35984,\nCVE-2024-39500, CVE-2024-26965, CVE-2024-26921, CVE-2024-27013,\nCVE-2024-39509, CVE-2024-27008, CVE-2024-36916, CVE-2024-40942,\nCVE-2024-35978, CVE-2024-26969, CVE-2024-26964, CVE-2024-35879,\nCVE-2024-36016, CVE-2024-26629, CVE-2024-42236, CVE-2024-40943,\nCVE-2024-36902, CVE-2024-42247, CVE-2024-36006, CVE-2024-36014,\nCVE-2024-26955, CVE-2024-39277, CVE-2024-39506, CVE-2024-35936,\nCVE-2024-26950, CVE-2024-35938, CVE-2024-41035, CVE-2024-42140,\nCVE-2024-36971, CVE-2024-35910, CVE-2024-34027, CVE-2024-35933,\nCVE-2024-35886, CVE-2024-39501, CVE-2024-42109, CVE-2024-42157,\nCVE-2024-35905, CVE-2024-41007, CVE-2024-40912, CVE-2024-26984,\nCVE-2024-35915, CVE-2024-35934, CVE-2024-38633, CVE-2024-26952,\nCVE-2024-27017, CVE-2024-38627, CVE-2024-42070, CVE-2024-41046,\nCVE-2024-35821, CVE-2024-35815, CVE-2024-36978, CVE-2024-36967,\nCVE-2023-52752, CVE-2024-38583, CVE-2024-38578, CVE-2024-26926,\nCVE-2023-52699, CVE-2024-36952, CVE-2024-38600, CVE-2024-42102,\nCVE-2024-38559, CVE-2024-38637, CVE-2024-42082, CVE-2023-52488,\nCVE-2024-36032, CVE-2024-35950, CVE-2024-35930, CVE-2024-38780,\nCVE-2024-40995, CVE-2024-36004, CVE-2024-26956, CVE-2024-35896,\nCVE-2024-26994, CVE-2024-38624, CVE-2024-39480, CVE-2023-52882,\nCVE-2024-35912, CVE-2024-36015, CVE-2024-27019, CVE-2024-40983,\nCVE-2023-52760, CVE-2024-39503, CVE-2024-36957, CVE-2024-26980,\nCVE-2024-40908, CVE-2024-40958, CVE-2024-35902, CVE-2024-42087,\nCVE-2024-36933, CVE-2024-38635, CVE-2024-26988, CVE-2024-36941,\nCVE-2024-26970, CVE-2024-36005, CVE-2024-36029, CVE-2024-36008,\nCVE-2024-42244, CVE-2024-40967, CVE-2023-52585, CVE-2024-26951,\nCVE-2024-39475, CVE-2024-35922, CVE-2024-36901, CVE-2024-40901,\nCVE-2024-36031, CVE-2024-41000, CVE-2024-40929, CVE-2024-40994,\nCVE-2024-42084, CVE-2024-38547, CVE-2024-26937, CVE-2024-40984,\nCVE-2024-27000, CVE-2024-35785, CVE-2024-35849, CVE-2024-42119,\nCVE-2024-35947, CVE-2024-39505, CVE-2024-42092, CVE-2024-26811,\nCVE-2024-35935, CVE-2024-36946, CVE-2024-40990, CVE-2024-26981,\nCVE-2024-38596, CVE-2024-40976, CVE-2024-36880)\n","status":"published","published":"2024-09-18T10:00:09Z","modified":"2026-10-26T22:33:18.442136814Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7029-1","title":"linux-hwe-6.8","description":"Chenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - FPGA Framework;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Microchip PCI driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - PCI subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Sonic Silicon Backplane drivers;\n  - Greybus lights staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Tracing file system;\n  - IOMMU subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Core kernel;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Landlock security;\n  - Linux Security Modules (LSM) Framework;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - SOF drivers;\n  - KVM core;\n(CVE-2024-39498, CVE-2024-33847, CVE-2024-39510, CVE-2024-39462,\nCVE-2024-40930, CVE-2024-38634, CVE-2024-40962, CVE-2024-37078,\nCVE-2024-39371, CVE-2024-40972, CVE-2024-41002, CVE-2024-40920,\nCVE-2024-40982, CVE-2024-40915, CVE-2024-40942, CVE-2024-42154,\nCVE-2024-40937, CVE-2024-40967, CVE-2024-40909, CVE-2024-36244,\nCVE-2024-33619, CVE-2024-39277, CVE-2024-40900, CVE-2024-38661,\nCVE-2024-40974, CVE-2024-38618, CVE-2024-32936, CVE-2024-40906,\nCVE-2024-40919, CVE-2024-39470, CVE-2024-38390, CVE-2024-40966,\nCVE-2024-39467, CVE-2024-40938, CVE-2024-39471, CVE-2024-39485,\nCVE-2024-39495, CVE-2024-39492, CVE-2024-39475, CVE-2024-40953,\nCVE-2024-40939, CVE-2024-39493, CVE-2024-38637, CVE-2024-40945,\nCVE-2024-41006, CVE-2024-39461, CVE-2024-40948, CVE-2024-40916,\nCVE-2024-40925, CVE-2024-40956, CVE-2024-40970, CVE-2024-40912,\nCVE-2024-33621, CVE-2024-40989, CVE-2024-36489, CVE-2024-37354,\nCVE-2024-34027, CVE-2024-39506, CVE-2024-39296, CVE-2024-40977,\nCVE-2024-38624, CVE-2024-40983, CVE-2024-40911, CVE-2024-36477,\nCVE-2024-38384, CVE-2024-39507, CVE-2024-38659, CVE-2024-40987,\nCVE-2024-40922, CVE-2024-36978, CVE-2024-38629, CVE-2024-38622,\nCVE-2024-40921, CVE-2024-40903, CVE-2024-38306, CVE-2024-40926,\nCVE-2024-39291, CVE-2024-36286, CVE-2024-40910, CVE-2024-40943,\nCVE-2024-40899, CVE-2024-37356, CVE-2024-40961, CVE-2024-39468,\nCVE-2024-40940, CVE-2024-40931, CVE-2024-38381, CVE-2024-40998,\nCVE-2024-34030, CVE-2024-41000, CVE-2024-40986, CVE-2024-38663,\nCVE-2024-40914, CVE-2024-31076, CVE-2024-42228, CVE-2024-40978,\nCVE-2024-40975, CVE-2024-39494, CVE-2024-40905, CVE-2024-40908,\nCVE-2024-38625, CVE-2024-38388, CVE-2024-40965, CVE-2024-41004,\nCVE-2023-52884, CVE-2024-39484, CVE-2024-40951, CVE-2024-40988,\nCVE-2024-40929, CVE-2024-39491, CVE-2024-40992, CVE-2024-41009,\nCVE-2024-40976, CVE-2024-40917, CVE-2024-39502, CVE-2024-40999,\nCVE-2024-39479, CVE-2024-39505, CVE-2024-40981, CVE-2024-38662,\nCVE-2024-38636, CVE-2024-39496, CVE-2024-39276, CVE-2024-41003,\nCVE-2024-37021, CVE-2024-36972, CVE-2024-38780, CVE-2024-40954,\nCVE-2024-40963, CVE-2024-36478, CVE-2024-39465, CVE-2024-39474,\nCVE-2024-39490, CVE-2024-36484, CVE-2024-36974, CVE-2024-38628,\nCVE-2024-36479, CVE-2024-42078, CVE-2024-40936, CVE-2024-38385,\nCVE-2024-40996, CVE-2024-40901, CVE-2024-40969, CVE-2024-39483,\nCVE-2024-40990, CVE-2024-40947, CVE-2024-40980, CVE-2024-39464,\nCVE-2024-40923, CVE-2024-40933, CVE-2024-39481, CVE-2024-40927,\nCVE-2024-38667, CVE-2024-42159, CVE-2024-38635, CVE-2024-38627,\nCVE-2024-38630, CVE-2024-39504, CVE-2024-34777, CVE-2024-40944,\nCVE-2024-37026, CVE-2024-38633, CVE-2024-40941, CVE-2024-39499,\nCVE-2024-36270, CVE-2024-35247, CVE-2024-40924, CVE-2024-40984,\nCVE-2024-40968, CVE-2024-39489, CVE-2024-39298, CVE-2024-40949,\nCVE-2024-39508, CVE-2024-41001, CVE-2024-40934, CVE-2024-40957,\nCVE-2024-39292, CVE-2024-40979, CVE-2024-39488, CVE-2024-40995,\nCVE-2024-39500, CVE-2024-40918, CVE-2024-36015, CVE-2024-39503,\nCVE-2024-39301, CVE-2024-39466, CVE-2024-42224, CVE-2024-39478,\nCVE-2024-40902, CVE-2024-39509, CVE-2024-39463, CVE-2024-40971,\nCVE-2024-40928, CVE-2024-38664, CVE-2024-39473, CVE-2024-39501,\nCVE-2024-36288, CVE-2024-42148, CVE-2024-38621, CVE-2024-38632,\nCVE-2024-41005, CVE-2024-38619, CVE-2024-36973, CVE-2024-40994,\nCVE-2024-42160, CVE-2024-40960, CVE-2024-40958, CVE-2024-39469,\nCVE-2022-48772, CVE-2024-40964, CVE-2024-40913, CVE-2024-36481,\nCVE-2024-40932, CVE-2024-36971, CVE-2024-40935, CVE-2024-38623,\nCVE-2024-40997, CVE-2024-40952, CVE-2024-40955, CVE-2024-36281,\nCVE-2024-39480, CVE-2024-40904, CVE-2024-40985, CVE-2024-39497,\nCVE-2024-40973, CVE-2024-40959)\n","status":"published","published":"2024-09-23T16:18:42Z","modified":"2026-10-26T22:33:33.280304216Z","updated_at":"2026-11-02T16:58:18.876384Z"}]}}