{"id":"CVE-2024-40965","aliases":["AZL-48957","AZL-48969","BELL-CVE-2024-40965","DEBIAN-CVE-2024-40965","EUVD-2024-38762","GHSA-r49f-c964-6w6w","OESA-2025-1095","OESA-2025-1096","OESA-2025-1097","RHSA-2024:9315","ROOT-OS-DEBIAN-11-CVE-2024-40965","ROOT-OS-DEBIAN-12-CVE-2024-40965","SUSE-SU-2024:3551-1","SUSE-SU-2024:3553-1","SUSE-SU-2024:3561-1","SUSE-SU-2024:3564-1","SUSE-SU-2024:3983-1","SUSE-SU-2024:3985-1","SUSE-SU-2024:4100-1","SUSE-SU-2024:4364-1","SUSE-SU-2025:0034-1","SUSE-SU-2025:20073-1","SUSE-SU-2025:20077-1","UBUNTU-CVE-2024-40965","USN-6999-1","USN-6999-2","USN-7004-1","USN-7005-1","USN-7005-2","USN-7008-1","USN-7029-1","USN-7288-1","USN-7288-2","USN-7289-1","USN-7289-2","USN-7289-3","USN-7289-4","USN-7291-1","USN-7293-1","USN-7294-1","USN-7294-2","USN-7294-3","USN-7294-4","USN-7295-1","USN-7305-1","USN-7308-1","USN-7331-1","USN-7388-1","USN-7389-1","USN-7390-1","USN-7393-1","USN-7401-1","USN-7413-1","USN-7458-1","USN-7539-1","USN-7540-1"],"status":"published","title":"i2c: lpi2c: Avoid calling clk_get_rate during transfer","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","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.00221,"percentile":0.12756,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-667"],"published":"2024-07-12T12:32:05Z","modified":"2026-11-10T02:49:08Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.64.2-9"],"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":["6.6.64","6.9.7"],"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":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","fixed_in":["5.4.0-1142.152~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","fixed_in":["5.4.0-1145.152~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","fixed_in":["5.4.0-1143.152~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","fixed_in":["5.4.0-208.228~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","fixed_in":["5.4.0-1086.91~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","fixed_in":["5.4.0-1138.147~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","fixed_in":["5.4.0-1129.142~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux","fixed_in":["5.4.0-208.228"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","fixed_in":["5.4.0-1140.150"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1080.87~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","fixed_in":["5.4.0-1145.152"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1081.90~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","fixed_in":["5.4.0-1099.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","fixed_in":["5.4.0-1143.152"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1077.86~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-134.145~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","fixed_in":["5.4.0-1086.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1074.77~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1073.79~20.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","fixed_in":["5.4.0-1048.51"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","fixed_in":["5.4.0-1127.136"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-133.143~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","fixed_in":["5.4.0-1138.147"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1075.81~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","fixed_in":["5.4.0-1129.142"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1073.77~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.4.0-1058.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1039.39~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","fixed_in":["5.4.0-1140.151+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","fixed_in":["5.4.0-1145.152+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","fixed_in":["5.4.0-1116.126"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","fixed_in":["5.4.0-1143.152+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-133.144"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1078.85"],"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-1081.90"],"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-1081.90.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1077.86"],"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-1075.81"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1060.68"],"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-1070.73"],"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-1073.79"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1076.81"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-133.143"],"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-1072.73"],"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-1033.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1021.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1075.81"],"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-1072.75"],"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-1044.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1060.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1071.73"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1078.86"],"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-1078.85+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1080.89+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-133.144+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1077.86+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":"Azure Linux:2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"5.15.200.1-1"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.64.2-9"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.134-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.100-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.10.0"},{"fixed":"6.6.64"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.9.7"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.162-1","6.1.164-1","6.1.170-1","6.1.170-2","6.1.170-3","6.1.172-1","6.1.174-1","6.1.176-1","6.1.177-1","6.1.180-1","6.1.187-1","6.1.190-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","6.10-1~exp1","6.10.1-1~exp1","6.10.11-1","6.10.11-1~bpo12+1","6.10.12-1","6.10.3-1","6.10.4-1","6.10.6-1","6.10.6-1~bpo12+1","6.10.7-1","6.10.9-1","6.11-1~exp1","6.11.10-1","6.11.10-1~bpo12+1","6.11.2-1","6.11.4-1","6.11.5-1","6.11.5-1~bpo12+1","6.11.6-1","6.11.7-1","6.11.9-1","6.11~rc4-1~exp1","6.11~rc5-1~exp1","6.12.10-1","6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.11-1","6.12.11-1+alpha","6.12.11-1+alpha.1","6.12.111-1","6.12.113-1","6.12.12-1","6.12.12-1~bpo12+1","6.12.13-1","6.12.15-1","6.12.16-1","6.12.17-1","6.12.19-1","6.12.20-1","6.12.21-1","6.12.22-1","6.12.22-1~bpo12+1","6.12.25-1","6.12.27-1","6.12.27-1~bpo12+1","6.12.29-1","6.12.3-1","6.12.30-1","6.12.30-1~bpo12+1","6.12.31-1","6.12.32-1","6.12.32-1~bpo12+1","6.12.33-1","6.12.33-1~bpo12+1","6.12.35-1","6.12.35-1~bpo12+1","6.12.37-1","6.12.38-1","6.12.38-1~bpo12+1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.5-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.6-1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.8-1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.9-1","6.12.9-1+alpha","6.12.9-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.12~rc6-1~exp1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.10-1","6.16.11-1","6.16.12-1","6.16.12-1~bpo13+1","6.16.12-2","6.16.3-1","6.16.3-1~bpo13+1","6.16.5-1","6.16.6-1","6.16.7-1","6.16.8-1","6.16.9-1","6.16~rc7-1~exp1","6.17.10-1","6.17.11-1","6.17.12-1","6.17.13-1","6.17.13-1~bpo13+1","6.17.2-1~exp1","6.17.5-1~exp1","6.17.6-1","6.17.7-1","6.17.7-2","6.17.8-1","6.17.8-1~bpo13+1","6.17.9-1","6.18.1-1~exp1","6.18.10-1","6.18.12-1","6.18.12-1~bpo13+1","6.18.13-1","6.18.14-1","6.18.15-1","6.18.15-1~bpo13+1","6.18.2-1~exp1","6.18.3-1","6.18.5-1","6.18.5-1~bpo13+1","6.18.8-1","6.18.9-1","6.18.9-1~bpo13+1","6.18~rc4-1~exp1","6.18~rc4-1~exp2","6.18~rc5-1~exp1","6.18~rc6-1~exp1","6.18~rc7-1~exp1","6.19-1~exp1","6.19.10-1","6.19.10-1~bpo13+1","6.19.11-1","6.19.11-1~bpo13+1","6.19.12-1","6.19.13-1","6.19.13-1~bpo13+1","6.19.14-1","6.19.14-1~bpo13+1","6.19.2-1~exp1","6.19.3-1~exp1","6.19.4-1~exp1","6.19.5-1~exp1","6.19.6-1","6.19.6-2","6.19.6-2~bpo13+1","6.19.8-1","6.19.8-1~bpo13+1","6.19~rc4-1~exp1","6.19~rc5-1~exp1","6.19~rc6-1~exp1","6.19~rc7-1~exp1","6.19~rc8-1~exp1","6.3.1-1~exp1","6.3.11-1","6.3.2-1~exp1","6.3.4-1~exp1","6.3.5-1~exp1","6.3.7-1","6.3.7-1~bpo12+1","6.4.1-1~exp1","6.4.11-1","6.4.13-1","6.4.4-1","6.4.4-1~bpo12+1","6.4.4-2","6.4.4-3","6.4.4-3~bpo12+1","6.4~rc6-1~exp1","6.4~rc7-1~exp1","6.5.1-1~exp1","6.5.10-1","6.5.10-1~bpo12+1","6.5.13-1","6.5.3-1","6.5.3-1~bpo12+1","6.5.6-1","6.5.8-1","6.5~rc4-1~exp1","6.5~rc6-1~exp1","6.5~rc7-1~exp1","6.6.11-1","6.6.13-1","6.6.13-1~bpo12+1","6.6.15-1","6.6.15-2","6.6.3-1~exp1","6.6.4-1~exp1","6.6.7-1~exp1","6.6.8-1","6.6.9-1","6.7-1~exp1","6.7.1-1~exp1","6.7.12-1","6.7.12-1~bpo12+1","6.7.4-1~exp1","6.7.7-1","6.7.9-1","6.7.9-2","6.8.11-1","6.8.12-1","6.8.12-1~bpo12+1","6.8.9-1","6.9.10-1","6.9.10-1~bpo12+1","6.9.11-1","6.9.12-1","6.9.2-1~exp1","6.9.7-1","6.9.7-1~bpo12+1","6.9.8-1","6.9.9-1","7.0-1~exp1","7.0.1-1~exp1","7.0.10-1","7.0.10-1~bpo13+1","7.0.12-1","7.0.12-2","7.0.12-2~bpo13+1","7.0.13-1","7.0.13-1~bpo13+1","7.0.14-1","7.0.3-1","7.0.4-1","7.0.4-1~bpo13+1","7.0.7-1","7.0.7-1~bpo13+1","7.0.9-1","7.0.9-1~bpo13+1","7.1.1-1~exp1","7.1.10-1","7.1.12-1","7.1.13-1","7.1.13-1~bpo13+1","7.1.2-1~exp1","7.1.3-1","7.1.3-1+sunvdc","7.1.3-1~bpo13+1","7.1.4-1","7.1.5-1","7.1.6-1","7.1.7-1","7.1.7-1~bpo13+1","7.1.8-1","7.1.8-1~bpo13+1","7.1.8-2","7.1.9-1","7.1.9-1+sparc64","7.1~rc2-1~exp1","7.1~rc3-1~exp1","7.1~rc4-1~exp1","7.1~rc4-1~exp2","7.1~rc5-1~exp1","7.1~rc7-1~exp1","7.2.10-1","7.2.11-1","7.2.11-1~bpo13+1","7.2.12-1","7.2.13-1","7.2.14-1","7.2.15-1","7.2.2-1~exp1","7.2.3-1~exp1","7.2.6-1","7.2.6-1~bpo13+1","7.2.7-1","7.2.8-1","7.2.9-1","7.2.9-1~bpo13+1","7.2~rc3-1~exp1","7.2~rc5-1~exp1","7.2~rc7-1~exp1","7.3.1-1~exp1","7.3~rc6-1~exp1","7.3~rc7-1~exp1"]},{"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":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-248.0.0.150.oe2203sp3"}]}],"bundled":40},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-248.0.0.147.oe2203sp4"}]}],"bundled":40},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-76.0.0.69.oe2403"}]}],"bundled":143},{"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":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-source-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-syms-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.6.coco15sp6.1"}]}],"bundled":147},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1.150600.12.10.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1.150600.12.10.2"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.2"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.25.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.3.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.14.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.72.1"}]}],"bundled":204},{"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.72.1"}]}],"bundled":204},{"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.72.1"}]}],"bundled":204},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.72.1"}]}],"bundled":204},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.72.1"}]}],"bundled":204},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.72.1"}]}],"bundled":204},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.76.1"}]}],"bundled":211},{"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.76.1"}]}],"bundled":211},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5-RT_Update_22","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":211},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.76.1"}]}],"bundled":211},{"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.76.1"}]}],"bundled":211},{"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.76.1"}]}],"bundled":211},{"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.76.1"}]}],"bundled":211},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.76.1"}]}],"bundled":211},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.76.1"}]}],"bundled":211},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.76.1"}]}],"bundled":211},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.76.1"}]}],"bundled":211},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.76.1"}]}],"bundled":211},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_62","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.88.1"}]}],"bundled":439},{"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.88.1.150500.6.39.4"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1.150500.6.39.4"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_21","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.5.1"}]}],"bundled":439},{"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.88.1"}]}],"bundled":439},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.234.1"}]}],"bundled":120},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-20.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-17.1.1.51"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-20.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-20.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0-RT_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.2"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-11.1"}]}],"bundled":162},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-11.1"}]}],"bundled":162},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1023.24~14.04.1","4.15.0-1030.31~14.04.1","4.15.0-1031.32~14.04.1","4.15.0-1032.33~14.04.2","4.15.0-1035.36~14.04.2","4.15.0-1036.38~14.04.2","4.15.0-1037.39~14.04.2","4.15.0-1039.41~14.04.2","4.15.0-1040.44~14.04.1","4.15.0-1041.45~14.04.1","4.15.0-1042.46~14.04.1","4.15.0-1045.49~14.04.1","4.15.0-1046.50~14.04.1","4.15.0-1047.51~14.04.1","4.15.0-1049.54~14.04.1","4.15.0-1050.55~14.04.1","4.15.0-1051.56~14.04.1","4.15.0-1052.57~14.04.1","4.15.0-1055.60~14.04.1","4.15.0-1056.61~14.04.1","4.15.0-1057.62~14.04.1","4.15.0-1059.64~14.04.1","4.15.0-1060.65~14.04.1","4.15.0-1061.66~14.04.1","4.15.0-1063.68~14.04.1","4.15.0-1064.69~14.04.1","4.15.0-1066.71~14.04.1","4.15.0-1067.72~14.04.1","4.15.0-1069.74~14.04.1","4.15.0-1071.76~14.04.1","4.15.0-1074.79~14.04.1","4.15.0-1077.82~14.04.1","4.15.0-1082.92~14.04.1","4.15.0-1083.93~14.04.1","4.15.0-1089.99~14.04.1","4.15.0-1091.101~14.04.1","4.15.0-1092.102~14.04.1","4.15.0-1093.103~14.04.1","4.15.0-1095.105~14.04.1","4.15.0-1096.106~14.04.1","4.15.0-1098.109~14.04.1","4.15.0-1100.111~14.04.1","4.15.0-1102.113~14.04.1","4.15.0-1103.114~14.04.1","4.15.0-1106.118~14.04.1","4.15.0-1108.120~14.04.1","4.15.0-1109.121~14.04.1","4.15.0-1110.122~14.04.1","4.15.0-1111.123~14.04.1","4.15.0-1112.124~14.04.1","4.15.0-1113.126~14.04.1","4.15.0-1114.127~14.04.1","4.15.0-1115.128~14.04.1","4.15.0-1118.131~14.04.1","4.15.0-1121.134~14.04.1","4.15.0-1122.135~14.04.1","4.15.0-1123.136~14.04.1","4.15.0-1124.137~14.04.1","4.15.0-1125.138~14.04.1","4.15.0-1126.139~14.04.1","4.15.0-1127.140~14.04.1","4.15.0-1129.142~14.04.1","4.15.0-1130.143~14.04.1","4.15.0-1131.144~14.04.1","4.15.0-1133.146~14.04.1","4.15.0-1134.147~14.04.1","4.15.0-1136.149~14.04.1","4.15.0-1137.150~14.04.1","4.15.0-1138.151~14.04.1","4.15.0-1139.152~14.04.1","4.15.0-1142.156~14.04.1","4.15.0-1145.160~14.04.1","4.15.0-1146.161~14.04.1","4.15.0-1149.164~14.04.1","4.15.0-1150.165~14.04.1","4.15.0-1151.166~14.04.1","4.15.0-1153.168~14.04.1","4.15.0-1157.172~14.04.2","4.15.0-1158.173~14.04.1","4.15.0-1159.174~14.04.1","4.15.0-1162.177~14.04.1","4.15.0-1163.178~14.04.1","4.15.0-1164.179~14.04.1","4.15.0-1165.180~14.04.1","4.15.0-1166.181~14.04.1","4.15.0-1167.182~14.04.1","4.15.0-1168.183~14.04.1","4.15.0-1169.184~14.04.1","4.15.0-1170.185~14.04.1","4.15.0-1171.186~14.04.1","4.15.0-1172.187~14.04.1","4.15.0-1173.188~14.04.1","4.15.0-1174.189~14.04.1","4.15.0-1175.190~14.04.1","4.15.0-1176.191~14.04.1","4.15.0-1177.192~14.04.1","4.15.0-1178.193~14.04.1","4.15.0-1179.194~14.04.1","4.15.0-1180.195~14.04.1","4.15.0-1181.196~14.04.1","4.15.0-1182.197~14.04.1","4.15.0-1183.198~14.04.1","4.15.0-1184.199~14.04.1","4.15.0-1185.200~14.04.1","4.15.0-1186.201~14.04.1","4.15.0-1187.202~14.04.1","4.15.0-1188.203~14.04.1","4.15.0-1189.204~14.04.1","4.15.0-1190.205~14.04.1","4.15.0-1191.206~14.04.1","4.15.0-1192.207~14.04.1","4.15.0-1193.208~14.04.1","4.15.0-1194.209~14.04.1","4.15.0-1195.210~14.04.1","4.15.0-1196.211~14.04.1","4.15.0-1197.212~14.04.1","4.15.0-1199.214~14.04.1","4.15.0-1200.215~14.04.1","4.15.0-1201.216~14.04.1","4.15.0-1202.217~14.04.1","4.15.0-1205.220~14.04.1","4.15.0-1206.221~14.04.1","4.15.0-1207.222~14.04.1","4.15.0-1208.223~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.31~16.04.1","4.15.0-1031.33~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1035.37~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1039.41~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43~16.04.1","4.15.0-1043.45~16.04.1","4.15.0-1044.46~16.04.1","4.15.0-1045.47~16.04.1","4.15.0-1047.49~16.04.1","4.15.0-1048.50~16.04.1","4.15.0-1050.52~16.04.1","4.15.0-1051.53~16.04.1","4.15.0-1052.54~16.04.1","4.15.0-1054.56~16.04.1","4.15.0-1056.58~16.04.1","4.15.0-1057.59~16.04.1","4.15.0-1058.60~16.04.1","4.15.0-1060.62~16.04.1","4.15.0-1063.67~16.04.1","4.15.0-1065.69~16.04.1","4.15.0-1066.70~16.04.1","4.15.0-1067.71~16.04.1","4.15.0-1073.77~16.04.1","4.15.0-1074.78~16.04.1","4.15.0-1079.83~16.04.1","4.15.0-1080.84~16.04.1","4.15.0-1082.86~16.04.1","4.15.0-1083.87~16.04.1","4.15.0-1085.90~16.04.1","4.15.0-1088.93~16.04.1","4.15.0-1090.95~16.04.1","4.15.0-1091.96~16.04.1","4.15.0-1093.99~16.04.1","4.15.0-1094.101~16.04.1","4.15.0-1095.102~16.04.1","4.15.0-1096.103~16.04.1","4.15.0-1097.104~16.04.1","4.15.0-1098.105~16.04.1","4.15.0-1099.106~16.04.1","4.15.0-1102.109~16.04.1","4.15.0-1103.110~16.04.1","4.15.0-1106.113~16.04.1","4.15.0-1109.116~16.04.1","4.15.0-1110.117~16.04.1","4.15.0-1111.118~16.04.1","4.15.0-1112.119~16.04.1","4.15.0-1113.120~16.04.1","4.15.0-1115.122~16.04.1","4.15.0-1116.123~16.04.1","4.15.0-1118.125~16.04.1","4.15.0-1119.126~16.04.2","4.15.0-1120.128~16.04.1","4.15.0-1123.132~16.04.1","4.15.0-1124.133~16.04.1","4.15.0-1126.135~16.04.2","4.15.0-1127.136~16.04.1","4.15.0-1128.137~16.04.1","4.15.0-1130.139~16.04.1","4.15.0-1133.143~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.154~16.04.1","4.15.0-1143.155~16.04.1","4.15.0-1146.158~16.04.2","4.15.0-1147.159~16.04.1","4.15.0-1148.160~16.04.1","4.15.0-1151.164~16.04.1","4.15.0-1153.166~16.04.1","4.15.0-1154.167~16.04.1","4.15.0-1155.168~16.04.1","4.15.0-1156.169~16.04.1","4.15.0-1157.170~16.04.1","4.15.0-1158.171~16.04.1","4.15.0-1159.172~16.04.1","4.15.0-1160.173~16.04.1","4.15.0-1161.174~16.04.1","4.15.0-1162.175~16.04.1","4.15.0-1163.176~16.04.1","4.15.0-1164.177~16.04.1","4.15.0-1165.178~16.04.1","4.15.0-1166.179~16.04.1","4.15.0-1167.180~16.04.1","4.15.0-1168.181~16.04.1","4.15.0-1169.182~16.04.1","4.15.0-1170.183~16.04.1","4.15.0-1172.185~16.04.1","4.15.0-1173.186~16.04.1","4.15.0-1174.187~16.04.1","4.15.0-1175.188~16.04.1","4.15.0-1176.189~16.04.1","4.15.0-1177.190~16.04.1","4.15.0-1178.191~16.04.1","4.15.0-1179.192~16.04.1","4.15.0-1180.193~16.04.1","4.15.0-1181.194~16.04.1","4.15.0-1182.195~16.04.1","4.15.0-1183.196~16.04.1","4.15.0-1184.197~16.04.1","4.15.0-1185.198~16.04.1","4.15.0-1186.199~16.04.1","4.15.0-1187.200~16.04.1","4.15.0-1188.201~16.04.1","4.15.0-1189.202~16.04.1","4.15.0-1190.203~16.04.1","4.15.0-1191.204~16.04.1","4.15.0-1192.205~16.04.1","4.15.0-1194.207~16.04.1","4.15.0-1195.208~16.04.1","4.15.0-1196.209~16.04.1","4.15.0-1197.210~16.04.1","4.15.0-1198.211~16.04.1","4.15.0-1199.212~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1","4.15.0-1022.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1025.26~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1030.31~16.04.1","4.15.0-1031.32~16.04.1","4.15.0-1032.33~16.04.1","4.15.0-1035.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1039.43","4.15.0-1040.44","4.15.0-1041.45","4.15.0-1042.46","4.15.0-1045.49","4.15.0-1046.50","4.15.0-1047.51","4.15.0-1049.54","4.15.0-1050.55","4.15.0-1051.56","4.15.0-1052.57","4.15.0-1055.60","4.15.0-1056.61","4.15.0-1057.62","4.15.0-1059.64","4.15.0-1060.65","4.15.0-1061.66","4.15.0-1063.68","4.15.0-1064.69","4.15.0-1066.71","4.15.0-1067.72","4.15.0-1069.74","4.15.0-1071.76","4.15.0-1075.80","4.15.0-1077.82","4.15.0-1082.92~16.04.1","4.15.0-1083.93~16.04.1","4.15.0-1089.99~16.04.1","4.15.0-1091.101~16.04.1","4.15.0-1092.102~16.04.1","4.15.0-1093.103~16.04.1","4.15.0-1095.105~16.04.1","4.15.0-1096.106~16.04.1","4.15.0-1098.109~16.04.1","4.15.0-1100.111~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1103.114~16.04.1","4.15.0-1106.118~16.04.1","4.15.0-1108.120~16.04.1","4.15.0-1109.121~16.04.1","4.15.0-1110.122~16.04.1","4.15.0-1111.123~16.04.1","4.15.0-1112.124~16.04.1","4.15.0-1113.126~16.04.1","4.15.0-1114.127~16.04.1","4.15.0-1115.128~16.04.1","4.15.0-1118.131~16.04.1","4.15.0-1121.134~16.04.1","4.15.0-1122.135~16.04.1","4.15.0-1123.136~16.04.1","4.15.0-1124.137~16.04.1","4.15.0-1125.138~16.04.1","4.15.0-1126.139~16.04.1","4.15.0-1127.140~16.04.1","4.15.0-1129.142~16.04.1","4.15.0-1130.143~16.04.1","4.15.0-1131.144~16.04.1","4.15.0-1133.146~16.04.1","4.15.0-1134.147~16.04.1","4.15.0-1136.149~16.04.1","4.15.0-1137.150~16.04.1","4.15.0-1138.151~16.04.1","4.15.0-1139.152~16.04.1","4.15.0-1142.156~16.04.1","4.15.0-1145.160~16.04.1","4.15.0-1146.161~16.04.1","4.15.0-1149.164~16.04.1","4.15.0-1150.165~16.04.1","4.15.0-1151.166~16.04.1","4.15.0-1153.168~16.04.1","4.15.0-1159.174~16.04.1","4.15.0-1162.177~16.04.1","4.15.0-1163.178~16.04.1","4.15.0-1164.179~16.04.1","4.15.0-1165.180~16.04.1","4.15.0-1166.181~16.04.1","4.15.0-1167.182~16.04.1","4.15.0-1168.183~16.04.1","4.15.0-1169.184~16.04.1","4.15.0-1170.185~16.04.1","4.15.0-1171.186~16.04.1","4.15.0-1172.187~16.04.1","4.15.0-1173.188~16.04.1","4.15.0-1174.189~16.04.1","4.15.0-1175.190~16.04.1","4.15.0-1176.191~16.04.1","4.15.0-1177.192~16.04.1","4.15.0-1178.193~16.04.1","4.15.0-1179.194~16.04.1","4.15.0-1180.195~16.04.1","4.15.0-1181.196~16.04.1","4.15.0-1182.197~16.04.1","4.15.0-1183.198~16.04.1","4.15.0-1184.199~16.04.1","4.15.0-1185.200~16.04.1","4.15.0-1186.201~16.04.1","4.15.0-1187.202~16.04.1","4.15.0-1188.203~16.04.1","4.15.0-1189.204~16.04.1","4.15.0-1190.205~16.04.1","4.15.0-1191.206~16.04.1","4.15.0-1192.207~16.04.1","4.15.0-1193.208~16.04.1","4.15.0-1194.209~16.04.1","4.15.0-1195.210~16.04.1","4.15.0-1196.211~16.04.1","4.15.0-1197.212~16.04.1","4.15.0-1200.215~16.04.1","4.15.0-1204.219~16.04.1","4.15.0-1205.220~16.04.1","4.15.0-1206.221~16.04.1","4.15.0-1208.223~16.04.1","4.15.0-1209.224~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1","4.15.0-1018.19~16.04.2","4.15.0-1019.20~16.04.1","4.15.0-1021.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1024.25~16.04.2","4.15.0-1025.26~16.04.1","4.15.0-1026.27~16.04.1","4.15.0-1027.28~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1029.31~16.04.1","4.15.0-1030.32~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1034.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1046.49","4.15.0-1047.50","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.56","4.15.0-1055.59","4.15.0-1058.62","4.15.0-1060.64","4.15.0-1061.65","4.15.0-1071.81~16.04.1","4.15.0-1077.87~16.04.1","4.15.0-1078.88~16.04.1","4.15.0-1080.90~16.04.1","4.15.0-1081.92~16.04.1","4.15.0-1083.94~16.04.1","4.15.0-1084.95~16.04.1","4.15.0-1086.98~16.04.1","4.15.0-1087.100~16.04.1","4.15.0-1088.101~16.04.1","4.15.0-1090.103~16.04.1","4.15.0-1091.104~16.04.1","4.15.0-1092.105~16.04.1","4.15.0-1093.106~16.04.1","4.15.0-1094.107~16.04.1","4.15.0-1095.108~16.04.1","4.15.0-1096.109~16.04.1","4.15.0-1097.110~16.04.1","4.15.0-1098.111~16.04.1","4.15.0-1099.112~16.04.1","4.15.0-1100.113~16.04.1","4.15.0-1103.116~16.04.1","4.15.0-1106.120~16.04.1","4.15.0-1107.121~16.04.1","4.15.0-1108.122~16.04.1","4.15.0-1109.123~16.04.1","4.15.0-1110.124~16.04.1","4.15.0-1111.125~16.04.1","4.15.0-1112.126~16.04.1","4.15.0-1114.128~16.04.1","4.15.0-1115.129~16.04.1","4.15.0-1116.130~16.04.1","4.15.0-1118.132~16.04.1","4.15.0-1119.133~16.04.1","4.15.0-1120.134~16.04.1","4.15.0-1121.135~16.04.1","4.15.0-1122.136~16.04.1","4.15.0-1124.138~16.04.1","4.15.0-1127.142~16.04.1","4.15.0-1130.146~16.04.1","4.15.0-1131.147~16.04.1","4.15.0-1134.150~16.04.2","4.15.0-1135.151~16.04.2","4.15.0-1136.152~16.04.1","4.15.0-1137.153~16.04.1","4.15.0-1138.154~16.04.1","4.15.0-1141.157~16.04.2","4.15.0-1142.158~16.04.1","4.15.0-1143.159~16.04.1","4.15.0-1146.162~16.04.1","4.15.0-1147.163~16.04.1","4.15.0-1148.164~16.04.1","4.15.0-1149.165~16.04.1","4.15.0-1150.166~16.04.1","4.15.0-1151.167~16.04.1","4.15.0-1152.168~16.04.1","4.15.0-1153.170~16.04.1","4.15.0-1154.171~16.04.1","4.15.0-1155.172~16.04.1","4.15.0-1156.173~16.04.1","4.15.0-1157.174~16.04.1","4.15.0-1158.175~16.04.1","4.15.0-1159.176~16.04.1","4.15.0-1160.177~16.04.1","4.15.0-1161.178~16.04.1","4.15.0-1162.179~16.04.1","4.15.0-1163.180~16.04.1","4.15.0-1164.181~16.04.1","4.15.0-1165.182~16.04.1","4.15.0-1166.183~16.04.1","4.15.0-1167.184~16.04.2","4.15.0-1168.185~16.04.1","4.15.0-1169.186~16.04.1","4.15.0-1170.187~16.04.1","4.15.0-1171.188~16.04.1","4.15.0-1172.189~16.04.1","4.15.0-1173.190~16.04.1","4.15.0-1174.191~16.04.1","4.15.0-1175.192~16.04.1","4.15.0-1176.193~16.04.1","4.15.0-1177.194~16.04.1","4.15.0-1178.195~16.04.1","4.15.0-1179.196~16.04.1","4.15.0-1180.197~16.04.1","4.15.0-1181.198~16.04.1","4.15.0-1182.199~16.04.1","4.15.0-1183.200~16.04.2","4.15.0-1184.201~16.04.1","4.15.0-1185.202~16.04.1","4.15.0-1187.204~16.04.1","4.15.0-1188.205~16.04.1","4.15.0-1189.206~16.04.1","4.15.0-1190.207~16.04.1","4.15.0-1191.208~16.04.1","4.15.0-1192.209~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1","4.15.0-33.36~16.04.1","4.15.0-34.37~16.04.1","4.15.0-36.39~16.04.1","4.15.0-38.41~16.04.1","4.15.0-39.42~16.04.1","4.15.0-42.45~16.04.1","4.15.0-43.46~16.04.1","4.15.0-45.48~16.04.1","4.15.0-46.49~16.04.1","4.15.0-47.50~16.04.1","4.15.0-48.51~16.04.1","4.15.0-50.54~16.04.1","4.15.0-51.55~16.04.1","4.15.0-52.56~16.04.1","4.15.0-54.58~16.04.1","4.15.0-55.60~16.04.2","4.15.0-58.64~16.04.1","4.15.0-60.67~16.04.1","4.15.0-62.69~16.04.1","4.15.0-64.73~16.04.1","4.15.0-65.74~16.04.1","4.15.0-66.75~16.04.1","4.15.0-69.78~16.04.1","4.15.0-70.79~16.04.1","4.15.0-72.81~16.04.1","4.15.0-74.83~16.04.1","4.15.0-76.86~16.04.1","4.15.0-88.88~16.04.1","4.15.0-91.92~16.04.1","4.15.0-96.97~16.04.1","4.15.0-99.100~16.04.1","4.15.0-101.102~16.04.1","4.15.0-106.107~16.04.1","4.15.0-107.108~16.04.1","4.15.0-112.113~16.04.1","4.15.0-115.116~16.04.1","4.15.0-117.118~16.04.1","4.15.0-118.119~16.04.1","4.15.0-120.122~16.04.1","4.15.0-122.124~16.04.1","4.15.0-123.126~16.04.1","4.15.0-126.129~16.04.1","4.15.0-128.131~16.04.1","4.15.0-129.132~16.04.1","4.15.0-132.136~16.04.1","4.15.0-133.137~16.04.1","4.15.0-136.140~16.04.1","4.15.0-137.141~16.04.1","4.15.0-139.143~16.04.1","4.15.0-140.144~16.04.1","4.15.0-142.146~16.04.1","4.15.0-143.147~16.04.3","4.15.0-144.148~16.04.1","4.15.0-147.151~16.04.1","4.15.0-151.157~16.04.1","4.15.0-153.160~16.04.1","4.15.0-154.161~16.04.1","4.15.0-156.163~16.04.1","4.15.0-158.166~16.04.1","4.15.0-159.167~16.04.1","4.15.0-161.169~16.04.1","4.15.0-162.170~16.04.1","4.15.0-163.171~16.04.1","4.15.0-166.174~16.04.1","4.15.0-167.175~16.04.1","4.15.0-169.177~16.04.1","4.15.0-171.180~16.04.1","4.15.0-173.182~16.04.1","4.15.0-175.184~16.04.1","4.15.0-176.185~16.04.1","4.15.0-177.186~16.04.1","4.15.0-180.189~16.04.1","4.15.0-184.194~16.04.1","4.15.0-187.198~16.04.1","4.15.0-188.199~16.04.1","4.15.0-189.200~16.04.1","4.15.0-191.202~16.04.1","4.15.0-192.203~16.04.1","4.15.0-193.204~16.04.1","4.15.0-194.205~16.04.1","4.15.0-196.207~16.04.1","4.15.0-197.208~16.04.1","4.15.0-200.211~16.04.2","4.15.0-201.212~16.04.1","4.15.0-202.213~16.04.1","4.15.0-206.217~16.04.1","4.15.0-208.219~16.04.1","4.15.0-209.220~16.04.1","4.15.0-210.221~16.04.1","4.15.0-211.222~16.04.1","4.15.0-212.223~16.04.1","4.15.0-213.224~16.04.1","4.15.0-214.225~16.04.1","4.15.0-216.227~16.04.1","4.15.0-218.229~16.04.1","4.15.0-219.230~16.04.1","4.15.0-220.231~16.04.1","4.15.0-221.232~16.04.1","4.15.0-222.233~16.04.1","4.15.0-223.235~16.04.1","4.15.0-224.236~16.04.1","4.15.0-225.237~16.04.1","4.15.0-226.238~16.04.1","4.15.0-227.239~16.04.1","4.15.0-228.240~16.04.1","4.15.0-229.241~16.04.1","4.15.0-230.242~16.04.1","4.15.0-231.243~16.04.1","4.15.0-232.244~16.04.1","4.15.0-233.245~16.04.1","4.15.0-234.246~16.04.1","4.15.0-235.247~16.04.1","4.15.0-236.248~16.04.1","4.15.0-237.249~16.04.1","4.15.0-238.250~16.04.1","4.15.0-239.251~16.04.1","4.15.0-240.252~16.04.1","4.15.0-241.253~16.04.1","4.15.0-242.254~16.04.1","4.15.0-243.255~16.04.1","4.15.0-245.257~16.04.1","4.15.0-246.258~16.04.1","4.15.0-247.259~16.04.1","4.15.0-248.260~16.04.1","4.15.0-249.261~16.04.1","4.15.0-250.262~16.04.1","4.15.0-253.265~16.04.1","4.15.0-254.266~16.04.1","4.15.0-257.269~16.04.1","4.15.0-260.272~16.04.2","4.15.0-261.273~16.04.1","4.15.0-262.274~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9~16.04.1","4.15.0-1008.10~16.04.1","4.15.0-1009.11~16.04.1","4.15.0-1010.12~16.04.1","4.15.0-1011.13~16.04.1","4.15.0-1013.15~16.04.1","4.15.0-1014.16~16.04.1","4.15.0-1015.17~16.04.1","4.15.0-1017.19~16.04.2","4.15.0-1018.20~16.04.1","4.15.0-1021.23~16.04.1","4.15.0-1022.25~16.04.1","4.15.0-1023.26~16.04.1","4.15.0-1025.28~16.04.1","4.15.0-1026.29~16.04.1","4.15.0-1027.30~16.04.1","4.15.0-1029.32~16.04.1","4.15.0-1030.33~16.04.1","4.15.0-1031.34~16.04.1","4.15.0-1033.36~16.04.1","4.15.0-1035.38~16.04.1","4.15.0-1037.41~16.04.1","4.15.0-1038.42~16.04.1","4.15.0-1039.43~16.04.1","4.15.0-1045.49~16.04.1","4.15.0-1046.50~16.04.1","4.15.0-1050.54~16.04.1","4.15.0-1051.55~16.04.1","4.15.0-1053.57~16.04.1","4.15.0-1054.58~16.04.1","4.15.0-1056.61~16.04.1","4.15.0-1058.64~16.04.1","4.15.0-1059.65~16.04.1","4.15.0-1061.67~16.04.1","4.15.0-1062.68~16.04.1","4.15.0-1064.71~16.04.1","4.15.0-1065.73~16.04.1","4.15.0-1066.74~16.04.1","4.15.0-1067.75~16.04.1","4.15.0-1068.76~16.04.1","4.15.0-1069.77~16.04.1","4.15.0-1070.78~16.04.1","4.15.0-1071.79~16.04.1","4.15.0-1072.80~16.04.1","4.15.0-1075.83~16.04.1","4.15.0-1078.86~16.04.1","4.15.0-1079.87~16.04.1","4.15.0-1080.88~16.04.1","4.15.0-1081.89~16.04.1","4.15.0-1082.90~16.04.1","4.15.0-1083.91~16.04.1","4.15.0-1084.92~16.04.1","4.15.0-1085.93~16.04.1","4.15.0-1086.94~16.04.1","4.15.0-1087.95~16.04.1","4.15.0-1089.98~16.04.1","4.15.0-1090.99~16.04.1","4.15.0-1091.100~16.04.1","4.15.0-1092.101~16.04.1","4.15.0-1093.102~16.04.1","4.15.0-1095.104~16.04.1","4.15.0-1098.108~16.04.1","4.15.0-1101.112~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1104.115~16.04.1","4.15.0-1105.116~16.04.1","4.15.0-1106.117~16.04.1","4.15.0-1107.118~16.04.1","4.15.0-1108.119~16.04.1","4.15.0-1111.122~16.04.2","4.15.0-1112.123~16.04.1","4.15.0-1113.124~16.04.1","4.15.0-1115.126~16.04.1","4.15.0-1116.127~16.04.1","4.15.0-1117.128~16.04.1","4.15.0-1118.129~16.04.1","4.15.0-1119.130~16.04.1","4.15.0-1120.131~16.04.1","4.15.0-1121.132~16.04.1","4.15.0-1122.133~16.04.1","4.15.0-1123.134~16.04.1","4.15.0-1124.135~16.04.1","4.15.0-1125.136~16.04.1","4.15.0-1126.137~16.04.1","4.15.0-1127.138~16.04.1","4.15.0-1128.139~16.04.1","4.15.0-1129.140~16.04.1","4.15.0-1130.141~16.04.1","4.15.0-1131.142~16.04.1","4.15.0-1132.143~16.04.1","4.15.0-1133.144~16.04.1","4.15.0-1134.145~16.04.1","4.15.0-1135.146~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1138.149~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.153~16.04.1","4.15.0-1143.154~16.04.1","4.15.0-1144.155~16.04.1","4.15.0-1145.156~16.04.1","4.15.0-1148.159~16.04.1","4.15.0-1149.160~16.04.1","4.15.0-1150.161~16.04.1","4.15.0-1151.162~16.04.1","4.15.0-1153.164~16.04.1","4.15.0-1154.165~16.04.1","4.15.0-1156.167~16.04.1","4.15.0-1158.169~16.04.1","4.15.0-1160.171~16.04.1","4.15.0-1161.172~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35","4.15.0-33.36","4.15.0-34.37","4.15.0-36.39","4.15.0-38.41","4.15.0-39.42","4.15.0-42.45","4.15.0-43.46","4.15.0-44.47","4.15.0-45.48","4.15.0-46.49","4.15.0-47.50","4.15.0-48.51","4.15.0-50.54","4.15.0-51.55","4.15.0-52.56","4.15.0-54.58","4.15.0-55.60","4.15.0-58.64","4.15.0-60.67","4.15.0-62.69","4.15.0-64.73","4.15.0-65.74","4.15.0-66.75","4.15.0-69.78","4.15.0-70.79","4.15.0-72.81","4.15.0-74.84","4.15.0-76.86","4.15.0-88.88","4.15.0-91.92","4.15.0-96.97","4.15.0-99.100","4.15.0-101.102","4.15.0-106.107","4.15.0-108.109","4.15.0-109.110","4.15.0-111.112","4.15.0-112.113","4.15.0-115.116","4.15.0-117.118","4.15.0-118.119","4.15.0-121.123","4.15.0-122.124","4.15.0-123.126","4.15.0-124.127","4.15.0-126.129","4.15.0-128.131","4.15.0-129.132","4.15.0-130.134","4.15.0-132.136","4.15.0-134.138","4.15.0-135.139","4.15.0-136.140","4.15.0-137.141","4.15.0-139.143","4.15.0-140.144","4.15.0-141.145","4.15.0-142.146","4.15.0-143.147","4.15.0-144.148","4.15.0-147.151","4.15.0-151.157","4.15.0-153.160","4.15.0-154.161","4.15.0-156.163","4.15.0-158.166","4.15.0-159.167","4.15.0-161.169","4.15.0-162.170","4.15.0-163.171","4.15.0-166.174","4.15.0-167.175","4.15.0-169.177","4.15.0-171.180","4.15.0-173.182","4.15.0-175.184","4.15.0-176.185","4.15.0-177.186","4.15.0-180.189","4.15.0-184.194","4.15.0-187.198","4.15.0-188.199","4.15.0-189.200","4.15.0-191.202","4.15.0-192.203","4.15.0-193.204","4.15.0-194.205","4.15.0-196.207","4.15.0-197.208","4.15.0-200.211","4.15.0-201.212","4.15.0-202.213","4.15.0-204.215","4.15.0-206.217","4.15.0-208.220","4.15.0-209.220","4.15.0-210.221","4.15.0-211.222","4.15.0-212.223","4.15.0-213.224","4.15.0-214.225","4.15.0-216.227","4.15.0-218.229","4.15.0-219.230","4.15.0-220.231","4.15.0-221.232","4.15.0-222.233","4.15.0-223.235","4.15.0-224.236","4.15.0-225.237","4.15.0-226.238","4.15.0-227.239","4.15.0-228.240","4.15.0-229.241","4.15.0-230.242","4.15.0-231.243","4.15.0-232.244","4.15.0-233.245","4.15.0-234.246","4.15.0-235.247","4.15.0-236.248","4.15.0-237.249","4.15.0-238.250","4.15.0-239.251","4.15.0-240.252","4.15.0-241.253","4.15.0-242.254","4.15.0-243.255","4.15.0-245.257","4.15.0-246.258","4.15.0-247.259","4.15.0-248.260","4.15.0-249.261","4.15.0-250.262","4.15.0-251.263","4.15.0-253.265","4.15.0-254.266","4.15.0-257.269","4.15.0-260.272","4.15.0-261.273","4.15.0-262.274"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","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-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1027.27","4.15.0-1029.30","4.15.0-1031.33","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1035.37","4.15.0-1037.39","4.15.0-1039.41","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1043.45","4.15.0-1044.46","4.15.0-1045.47","4.15.0-1047.49","4.15.0-1048.50","4.15.0-1050.52","4.15.0-1051.53","4.15.0-1052.54","4.15.0-1054.56","4.15.0-1056.58","4.15.0-1057.59","4.15.0-1058.60","4.15.0-1060.62","4.15.0-1063.67","4.15.0-1065.69","4.15.0-1066.70","4.15.0-1067.71","4.15.0-1073.77","4.15.0-1076.80","4.15.0-1077.81","4.15.0-1079.83","4.15.0-1080.84","4.15.0-1082.86","4.15.0-1083.87","4.15.0-1086.91","4.15.0-1087.92","4.15.0-1088.93","4.15.0-1090.95","4.15.0-1091.96","4.15.0-1092.98","4.15.0-1093.99","4.15.0-1094.101","4.15.0-1095.102","4.15.0-1096.103","4.15.0-1097.104","4.15.0-1098.105","4.15.0-1099.106","4.15.0-1101.108","4.15.0-1102.109","4.15.0-1103.110","4.15.0-1106.113","4.15.0-1109.116","4.15.0-1110.117","4.15.0-1111.118","4.15.0-1112.119","4.15.0-1114.121","4.15.0-1115.122","4.15.0-1116.123","4.15.0-1118.125","4.15.0-1119.127","4.15.0-1121.129","4.15.0-1123.132","4.15.0-1124.133","4.15.0-1126.135","4.15.0-1127.136","4.15.0-1128.137","4.15.0-1130.139","4.15.0-1133.143","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1150.163","4.15.0-1151.164","4.15.0-1153.166","4.15.0-1154.167","4.15.0-1155.168","4.15.0-1156.169","4.15.0-1157.170","4.15.0-1158.171","4.15.0-1159.172","4.15.0-1160.173","4.15.0-1161.174","4.15.0-1162.175","4.15.0-1163.176","4.15.0-1164.177","4.15.0-1165.178","4.15.0-1166.179","4.15.0-1167.180","4.15.0-1168.181","4.15.0-1169.182","4.15.0-1170.183","4.15.0-1172.185","4.15.0-1173.186","4.15.0-1174.187","4.15.0-1175.188","4.15.0-1176.189","4.15.0-1177.190","4.15.0-1178.191","4.15.0-1179.192","4.15.0-1180.193","4.15.0-1181.194","4.15.0-1182.195","4.15.0-1183.196","4.15.0-1184.197","4.15.0-1185.198","4.15.0-1186.199","4.15.0-1187.200","4.15.0-1188.201","4.15.0-1189.202","4.15.0-1190.203","4.15.0-1191.204","4.15.0-1192.205","4.15.0-1194.207","4.15.0-1195.208","4.15.0-1196.209","4.15.0-1197.210","4.15.0-1198.211","4.15.0-1199.212"]},{"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-1142.152~18.04.1"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1","5.4.0-1124.134~18.04.1","5.4.0-1125.135~18.04.1","5.4.0-1126.136~18.04.1","5.4.0-1127.137~18.04.2","5.4.0-1128.138~18.04.1","5.4.0-1129.139~18.04.1","5.4.0-1130.140~18.04.1","5.4.0-1131.141~18.04.1","5.4.0-1132.142~18.04.1","5.4.0-1133.143~18.04.1","5.4.0-1134.144~18.04.1","5.4.0-1135.145~18.04.1","5.4.0-1136.146~18.04.1","5.4.0-1137.147~18.04.1","5.4.0-1139.149~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1082.92","4.15.0-1083.93","4.15.0-1089.99","4.15.0-1091.101","4.15.0-1092.102","4.15.0-1093.103","4.15.0-1095.105","4.15.0-1096.106","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1102.113","4.15.0-1103.114","4.15.0-1104.116","4.15.0-1106.118","4.15.0-1108.120","4.15.0-1109.121","4.15.0-1110.122","4.15.0-1111.123","4.15.0-1112.125","4.15.0-1113.126","4.15.0-1114.127","4.15.0-1115.128","4.15.0-1118.131","4.15.0-1121.134","4.15.0-1122.135","4.15.0-1123.136","4.15.0-1124.137","4.15.0-1125.138","4.15.0-1126.139","4.15.0-1127.140","4.15.0-1129.142","4.15.0-1130.143","4.15.0-1131.144","4.15.0-1133.146","4.15.0-1134.147","4.15.0-1136.149","4.15.0-1137.150","4.15.0-1138.151","4.15.0-1139.152","4.15.0-1142.156","4.15.0-1145.160","4.15.0-1146.161","4.15.0-1149.164","4.15.0-1150.165","4.15.0-1151.166","4.15.0-1153.168","4.15.0-1157.172","4.15.0-1158.173","4.15.0-1159.174","4.15.0-1161.176","4.15.0-1162.177","4.15.0-1163.178","4.15.0-1164.179","4.15.0-1165.180","4.15.0-1166.181","4.15.0-1167.182","4.15.0-1168.183","4.15.0-1169.184","4.15.0-1170.185","4.15.0-1171.186","4.15.0-1172.187","4.15.0-1173.188","4.15.0-1174.189","4.15.0-1175.190","4.15.0-1176.191","4.15.0-1177.192","4.15.0-1178.193","4.15.0-1179.194","4.15.0-1180.195","4.15.0-1181.196","4.15.0-1182.197","4.15.0-1183.198","4.15.0-1184.199","4.15.0-1185.200","4.15.0-1186.201","4.15.0-1187.202","4.15.0-1188.203","4.15.0-1189.204","4.15.0-1190.205","4.15.0-1191.206","4.15.0-1192.207","4.15.0-1193.208","4.15.0-1194.209","4.15.0-1195.210","4.15.0-1196.211","4.15.0-1197.212","4.15.0-1199.214","4.15.0-1200.215","4.15.0-1201.216","4.15.0-1202.217","4.15.0-1204.219","4.15.0-1205.220","4.15.0-1206.221","4.15.0-1207.222","4.15.0-1208.223","4.15.0-1209.224"]},{"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-1145.152~18.04.1"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1","5.4.0-1129.136~18.04.1","5.4.0-1130.137~18.04.1","5.4.0-1131.138~18.04.1","5.4.0-1132.139~18.04.1","5.4.0-1133.140~18.04.1","5.4.0-1134.141~18.04.1","5.4.0-1135.142~18.04.1","5.4.0-1136.143~18.04.1","5.4.0-1137.144~18.04.1","5.4.0-1138.145~18.04.1","5.4.0-1139.146~18.04.1","5.4.0-1140.147~18.04.1","5.4.0-1142.149~18.04.1","5.4.0-1143.150~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1071.81","4.15.0-1077.87","4.15.0-1078.88","4.15.0-1080.90","4.15.0-1081.92","4.15.0-1083.94","4.15.0-1084.95","4.15.0-1086.98","4.15.0-1087.100","4.15.0-1088.101","4.15.0-1090.103","4.15.0-1091.104","4.15.0-1092.105","4.15.0-1093.106","4.15.0-1094.107","4.15.0-1095.108","4.15.0-1096.109","4.15.0-1097.110","4.15.0-1098.111","4.15.0-1099.112","4.15.0-1100.113","4.15.0-1103.116","4.15.0-1106.120","4.15.0-1107.121","4.15.0-1108.122","4.15.0-1109.123","4.15.0-1110.124","4.15.0-1111.125","4.15.0-1112.126","4.15.0-1114.128","4.15.0-1115.129","4.15.0-1116.130","4.15.0-1118.132","4.15.0-1119.133","4.15.0-1120.134","4.15.0-1121.135","4.15.0-1122.136","4.15.0-1124.138","4.15.0-1127.142","4.15.0-1130.146","4.15.0-1131.147","4.15.0-1134.150","4.15.0-1135.151","4.15.0-1136.152","4.15.0-1137.153","4.15.0-1138.154","4.15.0-1141.157","4.15.0-1142.158","4.15.0-1143.159","4.15.0-1145.161","4.15.0-1146.162","4.15.0-1147.163","4.15.0-1148.164","4.15.0-1149.165","4.15.0-1150.166","4.15.0-1151.167","4.15.0-1152.168","4.15.0-1153.170","4.15.0-1154.171","4.15.0-1155.172","4.15.0-1156.173","4.15.0-1157.174","4.15.0-1158.175","4.15.0-1159.176","4.15.0-1160.177","4.15.0-1161.178","4.15.0-1162.179","4.15.0-1163.180","4.15.0-1164.181","4.15.0-1165.182","4.15.0-1166.183","4.15.0-1167.184","4.15.0-1168.185","4.15.0-1169.186","4.15.0-1170.187","4.15.0-1171.188","4.15.0-1172.189","4.15.0-1173.190","4.15.0-1174.191","4.15.0-1175.192","4.15.0-1176.193","4.15.0-1177.194","4.15.0-1178.195","4.15.0-1179.196","4.15.0-1180.197","4.15.0-1181.198","4.15.0-1182.199","4.15.0-1183.200","4.15.0-1184.201","4.15.0-1185.202","4.15.0-1186.203","4.15.0-1187.204","4.15.0-1188.205","4.15.0-1189.206","4.15.0-1190.207","4.15.0-1191.208","4.15.0-1192.209"]},{"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-1143.152~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1128.137~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1139.148~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.150~18.04.1","5.4.0-1142.151~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-208.228~18.04.1"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1","5.4.0-181.201~18.04.1","5.4.0-182.202~18.04.1","5.4.0-186.206~18.04.1","5.4.0-187.207~18.04.1","5.4.0-189.209~18.04.1","5.4.0-190.210~18.04.1","5.4.0-192.212~18.04.1","5.4.0-193.213~18.04.1","5.4.0-195.215~18.04.1","5.4.0-196.216~18.04.1","5.4.0-198.218~18.04.1","5.4.0-200.220~18.04.1","5.4.0-202.222~18.04.1","5.4.0-204.224~18.04.1","5.4.0-205.225~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-1086.91~18.04.1"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1076.81~18.04.1","5.4.0-1077.82~18.04.1","5.4.0-1078.83~18.04.1","5.4.0-1079.84~18.04.1","5.4.0-1080.85~18.04.1","5.4.0-1081.86~18.04.1","5.4.0-1082.87~18.04.1","5.4.0-1083.88~18.04.1","5.4.0-1084.89~18.04.1","5.4.0-1085.90~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-kvm","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-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1026.26","4.15.0-1027.27","4.15.0-1028.28","4.15.0-1029.29","4.15.0-1030.30","4.15.0-1031.31","4.15.0-1032.32","4.15.0-1034.34","4.15.0-1035.35","4.15.0-1036.36","4.15.0-1038.38","4.15.0-1039.39","4.15.0-1042.42","4.15.0-1043.43","4.15.0-1044.44","4.15.0-1046.46","4.15.0-1047.47","4.15.0-1048.48","4.15.0-1050.50","4.15.0-1051.51","4.15.0-1052.52","4.15.0-1053.53","4.15.0-1056.57","4.15.0-1058.59","4.15.0-1059.60","4.15.0-1060.61","4.15.0-1067.68","4.15.0-1069.70","4.15.0-1071.72","4.15.0-1072.73","4.15.0-1074.75","4.15.0-1075.76","4.15.0-1077.79","4.15.0-1079.81","4.15.0-1081.83","4.15.0-1082.84","4.15.0-1084.86","4.15.0-1085.87","4.15.0-1086.88","4.15.0-1087.89","4.15.0-1088.90","4.15.0-1089.91","4.15.0-1090.92","4.15.0-1091.93","4.15.0-1092.94","4.15.0-1094.96","4.15.0-1097.99","4.15.0-1098.100","4.15.0-1099.101","4.15.0-1100.102","4.15.0-1101.103","4.15.0-1102.104","4.15.0-1103.105","4.15.0-1105.107","4.15.0-1106.108","4.15.0-1107.109","4.15.0-1109.112","4.15.0-1110.113","4.15.0-1112.115","4.15.0-1113.116","4.15.0-1114.117","4.15.0-1116.119","4.15.0-1119.123","4.15.0-1122.127","4.15.0-1123.128","4.15.0-1125.130","4.15.0-1126.131","4.15.0-1127.132","4.15.0-1128.133","4.15.0-1129.134","4.15.0-1132.137","4.15.0-1133.138","4.15.0-1134.139","4.15.0-1135.140","4.15.0-1136.141","4.15.0-1137.142","4.15.0-1138.143","4.15.0-1139.144","4.15.0-1140.145","4.15.0-1141.146","4.15.0-1142.147","4.15.0-1143.148","4.15.0-1144.149","4.15.0-1145.150","4.15.0-1146.151","4.15.0-1147.152","4.15.0-1148.153","4.15.0-1149.154","4.15.0-1150.155","4.15.0-1151.156","4.15.0-1152.157","4.15.0-1153.158","4.15.0-1154.159","4.15.0-1155.160","4.15.0-1156.161","4.15.0-1157.162","4.15.0-1158.163","4.15.0-1159.164","4.15.0-1160.165","4.15.0-1161.166","4.15.0-1162.167","4.15.0-1163.168","4.15.0-1164.169","4.15.0-1165.170","4.15.0-1166.171","4.15.0-1167.172","4.15.0-1168.173","4.15.0-1169.174","4.15.0-1170.175","4.15.0-1171.176","4.15.0-1172.177","4.15.0-1173.178","4.15.0-1174.179","4.15.0-1175.180","4.15.0-1176.181","4.15.0-1177.182","4.15.0-1178.183","4.15.0-1179.184","4.15.0-1180.185","4.15.0-1181.186"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9","4.15.0-1008.10","4.15.0-1009.11","4.15.0-1010.12","4.15.0-1011.13","4.15.0-1013.15","4.15.0-1014.16","4.15.0-1015.17","4.15.0-1017.19","4.15.0-1018.20","4.15.0-1021.23","4.15.0-1022.25","4.15.0-1023.26","4.15.0-1025.28","4.15.0-1026.29","4.15.0-1027.30","4.15.0-1029.32","4.15.0-1030.33","4.15.0-1031.34","4.15.0-1033.36","4.15.0-1035.39","4.15.0-1037.41","4.15.0-1038.42","4.15.0-1039.43","4.15.0-1045.49","4.15.0-1047.51","4.15.0-1048.52","4.15.0-1050.54","4.15.0-1051.55","4.15.0-1053.57","4.15.0-1054.58","4.15.0-1057.62","4.15.0-1058.64","4.15.0-1059.65","4.15.0-1061.67","4.15.0-1062.68","4.15.0-1063.70","4.15.0-1064.71","4.15.0-1065.73","4.15.0-1066.74","4.15.0-1067.75","4.15.0-1068.76","4.15.0-1069.77","4.15.0-1070.78","4.15.0-1071.79","4.15.0-1072.80","4.15.0-1075.83","4.15.0-1078.86","4.15.0-1079.87","4.15.0-1080.88","4.15.0-1081.89","4.15.0-1082.90","4.15.0-1083.91","4.15.0-1084.92","4.15.0-1085.93","4.15.0-1086.94","4.15.0-1087.95","4.15.0-1089.98","4.15.0-1090.99","4.15.0-1091.100","4.15.0-1092.101","4.15.0-1093.102","4.15.0-1095.104","4.15.0-1098.108","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1106.117","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1120.131","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.153","4.15.0-1143.154","4.15.0-1144.155","4.15.0-1145.156","4.15.0-1146.157","4.15.0-1147.158","4.15.0-1148.159","4.15.0-1149.160","4.15.0-1150.161","4.15.0-1151.162","4.15.0-1152.163","4.15.0-1153.164","4.15.0-1154.165","4.15.0-1155.166","4.15.0-1156.167","4.15.0-1158.169","4.15.0-1160.171","4.15.0-1161.172"]},{"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-1138.147~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1131.140~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~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-1129.142~18.04.1"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1","5.4.0-1108.120~18.04.1","5.4.0-1109.121~18.04.1","5.4.0-1110.122~18.04.1","5.4.0-1111.123~18.04.1","5.4.0-1112.124~18.04.1","5.4.0-1114.126~18.04.1","5.4.0-1115.127~18.04.1","5.4.0-1116.128~18.04.1","5.4.0-1117.129~18.04.1","5.4.0-1118.130~18.04.1","5.4.0-1119.131~18.04.1","5.4.0-1120.132~18.04.1","5.4.0-1121.133~18.04.1","5.4.0-1122.134~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4","4.15.0-2018.18","4.15.0-2021.21","4.15.0-2022.22","4.15.0-2024.24","4.15.0-2025.25","4.15.0-2026.26","4.15.0-2027.27","4.15.0-2030.31","4.15.0-2031.32","4.15.0-2033.34","4.15.0-2034.35","4.15.0-2035.37","4.15.0-2036.38","4.15.0-2037.39","4.15.0-2038.40","4.15.0-2039.41","4.15.0-2040.42","4.15.0-2041.43","4.15.0-2042.44","4.15.0-2044.46","4.15.0-2045.47","4.15.0-2048.50","4.15.0-2051.53","4.15.0-2052.54","4.15.0-2053.55","4.15.0-2054.56","4.15.0-2055.57","4.15.0-2056.58","4.15.0-2057.59","4.15.0-2059.61","4.15.0-2060.62","4.15.0-2061.63","4.15.0-2063.66","4.15.0-2064.67","4.15.0-2065.68","4.15.0-2066.69","4.15.0-2067.70","4.15.0-2069.72","4.15.0-2072.76","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2078.83","4.15.0-2079.84","4.15.0-2080.85","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2085.91","4.15.0-2087.93","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2103.109","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2107.113","4.15.0-2108.114","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123","4.15.0-2118.124","4.15.0-2119.125","4.15.0-2120.126","4.15.0-2121.127","4.15.0-2122.128","4.15.0-2123.129","4.15.0-2124.130","4.15.0-2125.131","4.15.0-2126.132","4.15.0-2127.133","4.15.0-2128.134","4.15.0-2129.135","4.15.0-2130.136","4.15.0-2132.138","4.15.0-2133.139","4.15.0-2134.140","4.15.0-2135.141","4.15.0-2136.142","4.15.0-2137.143"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-2006.7","4.15.0-2007.8","4.15.0-2008.9","4.15.0-2009.10","4.15.0-2012.14","4.15.0-2013.15","4.15.0-2015.17","4.15.0-2016.18","4.15.0-2017.20","4.15.0-2018.21","4.15.0-2020.23","4.15.0-2021.24","4.15.0-2022.25","4.15.0-2023.26","4.15.0-2024.27","4.15.0-2025.28","4.15.0-2026.29","4.15.0-2027.30","4.15.0-2030.33","4.15.0-2033.37","4.15.0-2034.38","4.15.0-2035.39","4.15.0-2036.40","4.15.0-2037.41","4.15.0-2038.42","4.15.0-2039.43","4.15.0-2041.45","4.15.0-2042.46","4.15.0-2043.47","4.15.0-2045.49","4.15.0-2046.50","4.15.0-2047.51","4.15.0-2048.52","4.15.0-2049.53","4.15.0-2050.54","4.15.0-2053.58","4.15.0-2056.62","4.15.0-2057.63","4.15.0-2059.65","4.15.0-2060.66","4.15.0-2062.68","4.15.0-2066.72","4.15.0-2067.73","4.15.0-2068.74","4.15.0-2070.76","4.15.0-2071.77","4.15.0-2072.78","4.15.0-2073.79","4.15.0-2074.80","4.15.0-2075.81","4.15.0-2076.82","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1027.32","4.15.0-1029.34","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1037.42","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1040.45","4.15.0-1041.46","4.15.0-1044.50","4.15.0-1045.52","4.15.0-1046.53","4.15.0-1048.55","4.15.0-1049.56","4.15.0-1050.58","4.15.0-1051.59","4.15.0-1052.60","4.15.0-1053.61","4.15.0-1054.62","4.15.0-1055.63","4.15.0-1056.64","4.15.0-1057.65","4.15.0-1058.66","4.15.0-1059.67","4.15.0-1060.68","4.15.0-1063.71","4.15.0-1066.75","4.15.0-1067.76","4.15.0-1068.77","4.15.0-1069.78","4.15.0-1070.79","4.15.0-1071.80","4.15.0-1072.81","4.15.0-1073.82","4.15.0-1075.84","4.15.0-1076.85","4.15.0-1078.87","4.15.0-1080.89","4.15.0-1081.90","4.15.0-1083.92","4.15.0-1084.93","4.15.0-1085.94","4.15.0-1087.96","4.15.0-1090.100","4.15.0-1093.104","4.15.0-1094.105","4.15.0-1096.107","4.15.0-1097.108","4.15.0-1098.109","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1103.114","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1109.120","4.15.0-1110.121","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.153","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1145.157","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1149.161","4.15.0-1150.162","4.15.0-1151.163","4.15.0-1152.164","4.15.0-1153.165","4.15.0-1154.166"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2013.14","4.15.0-2016.18","4.15.0-2017.19","4.15.0-2018.20","4.15.0-2019.21","4.15.0-2020.22","4.15.0-2021.23","4.15.0-2022.24","4.15.0-2024.26","4.15.0-2025.27","4.15.0-2026.28","4.15.0-2028.31","4.15.0-2029.32","4.15.0-2030.33","4.15.0-2031.34","4.15.0-2032.35","4.15.0-2034.37","4.15.0-2037.41","4.15.0-2040.45","4.15.0-2041.46","4.15.0-2043.48","4.15.0-2044.49","4.15.0-2045.50","4.15.0-2047.52","4.15.0-2050.55","4.15.0-2052.57","4.15.0-2054.59","4.15.0-2055.60","4.15.0-2056.61","4.15.0-2057.62","4.15.0-2058.63","4.15.0-2059.64","4.15.0-2060.65","4.15.0-2061.66","4.15.0-2062.67","4.15.0-2063.68","4.15.0-2064.69","4.15.0-2065.70","4.15.0-2066.71","4.15.0-2067.72","4.15.0-2068.73","4.15.0-2069.74","4.15.0-2070.75","4.15.0-2071.76","4.15.0-2072.77","4.15.0-2073.78","4.15.0-2074.79","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1011.12"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-208.228"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197","5.4.0-181.201","5.4.0-182.202","5.4.0-186.206","5.4.0-187.207","5.4.0-189.209","5.4.0-190.210","5.4.0-192.212","5.4.0-193.213","5.4.0-195.215","5.4.0-196.216","5.4.0-198.218","5.4.0-200.220","5.4.0-202.222","5.4.0-204.224","5.4.0-205.225"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.150"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1129.139","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1139.149"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1080.87~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1145.152"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135","5.4.0-1129.136","5.4.0-1130.137","5.4.0-1131.138","5.4.0-1132.139","5.4.0-1133.140","5.4.0-1134.141","5.4.0-1135.142","5.4.0-1136.143","5.4.0-1137.144","5.4.0-1138.145","5.4.0-1139.146","5.4.0-1140.147","5.4.0-1142.149","5.4.0-1143.150"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.90~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1099.106"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1143.152"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1128.137","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1142.151"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1077.86~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-134.145~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1086.91"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1077.82","5.4.0-1078.83","5.4.0-1079.84","5.4.0-1080.85","5.4.0-1081.86","5.4.0-1082.87","5.4.0-1083.88","5.4.0-1084.89","5.4.0-1085.90"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1074.77~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~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-1073.79~20.04.2"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1048.51"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1042.43","5.4.0-1043.44","5.4.0-1044.45","5.4.0-1045.46"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1127.136"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1113.120","5.4.0-1114.121","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.127","5.4.0-1120.128","5.4.0-1121.129","5.4.0-1122.130","5.4.0-1123.131","5.4.0-1124.132","5.4.0-1125.133","5.4.0-1126.134"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-133.143~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1138.147"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.81~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.142"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119","5.4.0-1108.120","5.4.0-1109.121","5.4.0-1110.122","5.4.0-1111.123","5.4.0-1112.124","5.4.0-1113.125","5.4.0-1114.126","5.4.0-1115.127","5.4.0-1116.128","5.4.0-1117.129","5.4.0-1118.130","5.4.0-1119.131","5.4.0-1120.132","5.4.0-1121.133","5.4.0-1122.134"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1073.77~20.04.1"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1","5.15.0-1068.72~20.04.1","5.15.0-1069.73~20.04.1","5.15.0-1070.74~20.04.1","5.15.0-1071.75~20.04.1","5.15.0-1072.76~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1058.62"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.51","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1050.54","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~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:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1039.39~20.04.1"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1"]},{"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-1140.151+fips1"}]}],"versions":["5.4.0-1021.21+fips2","5.4.0-1069.73+fips2","5.4.0-1071.76+fips1","5.4.0-1072.77+fips1","5.4.0-1073.78+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1083.90+fips1","5.4.0-1085.92+fips1","5.4.0-1086.93+fips1","5.4.0-1088.96+fips1","5.4.0-1089.97+fips1","5.4.0-1092.100+fips1","5.4.0-1093.101+fips1","5.4.0-1094.102+fips1","5.4.0-1096.104+fips1","5.4.0-1099.107+fips1","5.4.0-1100.108+fips1","5.4.0-1101.109+fips1","5.4.0-1102.110+fips1","5.4.0-1103.111+fips1","5.4.0-1104.112+fips1","5.4.0-1105.113+fips1","5.4.0-1106.114+fips1","5.4.0-1107.115+fips1","5.4.0-1108.116+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.123+fips1","5.4.0-1114.124+fips1","5.4.0-1116.126+fips1","5.4.0-1117.127+fips1","5.4.0-1118.128+fips1","5.4.0-1119.129+fips1","5.4.0-1120.130+fips1","5.4.0-1121.131+fips1","5.4.0-1122.132+fips1","5.4.0-1123.133+fips1","5.4.0-1124.134+fips1","5.4.0-1125.135+fips1","5.4.0-1126.136+fips2","5.4.0-1127.137+fips1","5.4.0-1128.138+fips1","5.4.0-1129.139+fips1","5.4.0-1130.140+fips1","5.4.0-1131.141+fips1","5.4.0-1132.142+fips1","5.4.0-1133.143+fips1","5.4.0-1134.144+fips1","5.4.0-1135.145+fips1","5.4.0-1136.146+fips1","5.4.0-1137.147+fips1","5.4.0-1139.149+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-1145.152+fips1"}]}],"versions":["5.4.0-1022.22+fips1","5.4.0-1073.76+fips1","5.4.0-1074.77+fips1","5.4.0-1076.79+fips1","5.4.0-1078.81+fips1","5.4.0-1080.83+fips1","5.4.0-1083.87+fips1","5.4.0-1085.90+fips1","5.4.0-1086.91+fips1","5.4.0-1089.94+fips1","5.4.0-1090.95+fips1","5.4.0-1091.96+fips1","5.4.0-1094.100+fips1","5.4.0-1095.101+fips1","5.4.0-1098.104+fips1","5.4.0-1100.106+fips1","5.4.0-1101.107+fips1","5.4.0-1103.109+fips1","5.4.0-1104.110+fips1","5.4.0-1105.111+fips1","5.4.0-1106.112+fips1","5.4.0-1107.113+fips1","5.4.0-1108.114+fips1","5.4.0-1109.115+fips1","5.4.0-1110.116+fips1","5.4.0-1111.117+fips1","5.4.0-1112.118+fips1","5.4.0-1113.119+fips1","5.4.0-1114.120+fips1","5.4.0-1115.122+fips1","5.4.0-1116.123+fips1","5.4.0-1117.124+fips1","5.4.0-1118.125+fips1","5.4.0-1119.126+fips1","5.4.0-1121.128+fips1","5.4.0-1122.129+fips1","5.4.0-1123.130+fips1","5.4.0-1124.131+fips1","5.4.0-1126.133+fips1","5.4.0-1127.134+fips1","5.4.0-1128.135+fips1","5.4.0-1129.136+fips1","5.4.0-1130.137+fips1","5.4.0-1131.138+fips1","5.4.0-1132.139+fips1","5.4.0-1133.140+fips1","5.4.0-1134.141+fips1","5.4.0-1135.142+fips1","5.4.0-1136.143+fips1","5.4.0-1137.144+fips1","5.4.0-1138.145+fips1","5.4.0-1139.146+fips1","5.4.0-1140.147+fips1","5.4.0-1142.149+fips1","5.4.0-1143.150+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1116.126"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32","5.4.0-1031.36","5.4.0-1032.37","5.4.0-1033.38","5.4.0-1034.40","5.4.0-1035.41","5.4.0-1036.42","5.4.0-1037.43","5.4.0-1038.44","5.4.0-1040.46","5.4.0-1041.47","5.4.0-1042.48","5.4.0-1043.49","5.4.0-1045.51","5.4.0-1046.52","5.4.0-1047.53","5.4.0-1048.54","5.4.0-1049.55","5.4.0-1051.57","5.4.0-1054.61","5.4.0-1056.64","5.4.0-1057.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1061.69","5.4.0-1062.70","5.4.0-1064.73","5.4.0-1065.74","5.4.0-1068.77","5.4.0-1069.78","5.4.0-1070.79","5.4.0-1072.81","5.4.0-1073.82","5.4.0-1074.83","5.4.0-1075.84","5.4.0-1076.85","5.4.0-1077.86","5.4.0-1078.87","5.4.0-1079.88","5.4.0-1080.89","5.4.0-1081.90","5.4.0-1082.91","5.4.0-1083.92","5.4.0-1084.93","5.4.0-1085.94","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1088.97","5.4.0-1089.98","5.4.0-1090.100","5.4.0-1091.101","5.4.0-1092.102","5.4.0-1094.104","5.4.0-1095.105","5.4.0-1096.106","5.4.0-1097.107","5.4.0-1098.108","5.4.0-1099.109","5.4.0-1100.110","5.4.0-1101.111","5.4.0-1102.112","5.4.0-1103.113","5.4.0-1104.114","5.4.0-1105.115","5.4.0-1106.116","5.4.0-1107.117","5.4.0-1108.118","5.4.0-1109.119","5.4.0-1110.120","5.4.0-1111.121","5.4.0-1112.122"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1143.152+fips1"}]}],"versions":["5.4.0-1021.21+fips1","5.4.0-1067.71~20.04.1","5.4.0-1069.73+fips2","5.4.0-1071.75+fips1","5.4.0-1073.78+fips1","5.4.0-1075.80+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1086.94+fips1","5.4.0-1087.95+fips1","5.4.0-1089.97+fips1","5.4.0-1092.101+fips1","5.4.0-1093.102+fips1","5.4.0-1096.105+fips1","5.4.0-1097.106+fips1","5.4.0-1098.107+fips1","5.4.0-1100.109+fips1","5.4.0-1101.110+fips1","5.4.0-1102.111+fips1","5.4.0-1103.112+fips1","5.4.0-1104.113+fips1","5.4.0-1105.114+fips1","5.4.0-1106.115+fips1","5.4.0-1107.116+fips1","5.4.0-1108.117+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.122+fips1","5.4.0-1115.124+fips1","5.4.0-1116.125+fips1","5.4.0-1117.126+fips1","5.4.0-1118.127+fips1","5.4.0-1120.129+fips1","5.4.0-1121.130+fips1","5.4.0-1122.131+fips1","5.4.0-1124.133+fips1","5.4.0-1125.134+fips1","5.4.0-1126.135+fips1","5.4.0-1127.136+fips1","5.4.0-1128.137+fips1","5.4.0-1129.138+fips1","5.4.0-1130.139+fips1","5.4.0-1131.140+fips1","5.4.0-1132.141+fips1","5.4.0-1133.142+fips1","5.4.0-1134.143+fips1","5.4.0-1135.144+fips1","5.4.0-1136.145+fips1","5.4.0-1137.146+fips1","5.4.0-1138.147+fips1","5.4.0-1139.148+fips1","5.4.0-1140.149+fips1","5.4.0-1141.150+fips1","5.4.0-1142.151+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-133.144"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141"]},{"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-1078.85"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83"]},{"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-1081.90"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88"]},{"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-1081.90.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.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-1077.86"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84"]},{"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-1075.81"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.68"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67"]},{"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-1070.73"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72"]},{"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-1073.79"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1076.81"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-133.143"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141"]},{"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-1072.73"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72"]},{"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-1033.33"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1021.21"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20"]},{"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-1075.81"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80"]},{"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-1072.75"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74"]},{"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-1044.48"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.62"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1045.47","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1050.52","5.15.0-1051.53","5.15.0-1052.54","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1071.73"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1066.68"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1078.86"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1077.85"]},{"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-1078.85+fips1"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+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-1080.89+fips1"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-133.144+fips1"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+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-1077.86+fips1"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+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: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: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: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},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-133.144"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141"],"bundled":104},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-133.143"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141"],"bundled":104},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-133.143~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1"],"bundled":104},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.90"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.90.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.68"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.73"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.81"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.90~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.90~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","5.15.0-1072.81~20.04.1.1","5.15.0-1073.82~20.04.1.1","5.15.0-1074.83~20.04.1.1","5.15.0-1076.85~20.04.1.1","5.15.0-1078.87~20.04.1.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.81~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1070.73"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1073.79~20.04.2"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1073.79"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1077.86~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1077.86"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.81"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-208.228~18.04.1"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1","5.4.0-181.201~18.04.1","5.4.0-182.202~18.04.1","5.4.0-186.206~18.04.1","5.4.0-187.207~18.04.1","5.4.0-189.209~18.04.1","5.4.0-190.210~18.04.1","5.4.0-192.212~18.04.1","5.4.0-193.213~18.04.1","5.4.0-195.215~18.04.1","5.4.0-196.216~18.04.1","5.4.0-198.218~18.04.1","5.4.0-200.220~18.04.1","5.4.0-202.222~18.04.1","5.4.0-204.224~18.04.1","5.4.0-205.225~18.04.1"],"bundled":145},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-208.228"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197","5.4.0-181.201","5.4.0-182.202","5.4.0-186.206","5.4.0-187.207","5.4.0-189.209","5.4.0-190.210","5.4.0-192.212","5.4.0-193.213","5.4.0-195.215","5.4.0-196.216","5.4.0-198.218","5.4.0-200.220","5.4.0-202.222","5.4.0-204.224","5.4.0-205.225"],"bundled":145},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1145.152~18.04.1"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1","5.4.0-1129.136~18.04.1","5.4.0-1130.137~18.04.1","5.4.0-1131.138~18.04.1","5.4.0-1132.139~18.04.1","5.4.0-1133.140~18.04.1","5.4.0-1134.141~18.04.1","5.4.0-1135.142~18.04.1","5.4.0-1136.143~18.04.1","5.4.0-1137.144~18.04.1","5.4.0-1138.145~18.04.1","5.4.0-1139.146~18.04.1","5.4.0-1140.147~18.04.1","5.4.0-1142.149~18.04.1","5.4.0-1143.150~18.04.1"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1143.152~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1128.137~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1139.148~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.150~18.04.1","5.4.0-1142.151~18.04.1"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1086.91~18.04.1"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1076.81~18.04.1","5.4.0-1077.82~18.04.1","5.4.0-1078.83~18.04.1","5.4.0-1079.84~18.04.1","5.4.0-1080.85~18.04.1","5.4.0-1081.86~18.04.1","5.4.0-1082.87~18.04.1","5.4.0-1083.88~18.04.1","5.4.0-1084.89~18.04.1","5.4.0-1085.90~18.04.1"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1145.152"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135","5.4.0-1129.136","5.4.0-1130.137","5.4.0-1131.138","5.4.0-1132.139","5.4.0-1133.140","5.4.0-1134.141","5.4.0-1135.142","5.4.0-1136.143","5.4.0-1137.144","5.4.0-1138.145","5.4.0-1139.146","5.4.0-1140.147","5.4.0-1142.149","5.4.0-1143.150"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1099.106"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1143.152"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1128.137","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1142.151"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1138.147~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1131.140~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1140.150"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1129.139","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1139.149"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1138.147"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1086.91"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1077.82","5.4.0-1078.83","5.4.0-1079.84","5.4.0-1080.85","5.4.0-1081.86","5.4.0-1082.87","5.4.0-1083.88","5.4.0-1084.89","5.4.0-1085.90"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1127.136"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1113.120","5.4.0-1114.121","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.127","5.4.0-1120.128","5.4.0-1121.129","5.4.0-1122.130","5.4.0-1123.131","5.4.0-1124.132","5.4.0-1125.133","5.4.0-1126.134"],"bundled":144},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1058.62"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.51","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1050.54","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60"],"bundled":149},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.75"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1078.85"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83"],"bundled":106},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-134.145~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1"],"bundled":105},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1080.87~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1"],"bundled":356},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1076.81"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78"],"bundled":356},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1033.33"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32"],"bundled":357},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1021.21"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20"],"bundled":357},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.48"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45"],"bundled":356},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1116.126"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32","5.4.0-1031.36","5.4.0-1032.37","5.4.0-1033.38","5.4.0-1034.40","5.4.0-1035.41","5.4.0-1036.42","5.4.0-1037.43","5.4.0-1038.44","5.4.0-1040.46","5.4.0-1041.47","5.4.0-1042.48","5.4.0-1043.49","5.4.0-1045.51","5.4.0-1046.52","5.4.0-1047.53","5.4.0-1048.54","5.4.0-1049.55","5.4.0-1051.57","5.4.0-1054.61","5.4.0-1056.64","5.4.0-1057.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1061.69","5.4.0-1062.70","5.4.0-1064.73","5.4.0-1065.74","5.4.0-1068.77","5.4.0-1069.78","5.4.0-1070.79","5.4.0-1072.81","5.4.0-1073.82","5.4.0-1074.83","5.4.0-1075.84","5.4.0-1076.85","5.4.0-1077.86","5.4.0-1078.87","5.4.0-1079.88","5.4.0-1080.89","5.4.0-1081.90","5.4.0-1082.91","5.4.0-1083.92","5.4.0-1084.93","5.4.0-1085.94","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1088.97","5.4.0-1089.98","5.4.0-1090.100","5.4.0-1091.101","5.4.0-1092.102","5.4.0-1094.104","5.4.0-1095.105","5.4.0-1096.106","5.4.0-1097.107","5.4.0-1098.108","5.4.0-1099.109","5.4.0-1100.110","5.4.0-1101.111","5.4.0-1102.112","5.4.0-1103.113","5.4.0-1104.114","5.4.0-1105.115","5.4.0-1106.116","5.4.0-1107.117","5.4.0-1108.118","5.4.0-1109.119","5.4.0-1110.120","5.4.0-1111.121","5.4.0-1112.122"],"bundled":295},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1142.152~18.04.1"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1","5.4.0-1124.134~18.04.1","5.4.0-1125.135~18.04.1","5.4.0-1126.136~18.04.1","5.4.0-1127.137~18.04.2","5.4.0-1128.138~18.04.1","5.4.0-1129.139~18.04.1","5.4.0-1130.140~18.04.1","5.4.0-1131.141~18.04.1","5.4.0-1132.142~18.04.1","5.4.0-1133.143~18.04.1","5.4.0-1134.144~18.04.1","5.4.0-1135.145~18.04.1","5.4.0-1136.146~18.04.1","5.4.0-1137.147~18.04.1","5.4.0-1139.149~18.04.1"],"bundled":295},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1048.51"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1042.43","5.4.0-1043.44","5.4.0-1044.45","5.4.0-1045.46"],"bundled":316},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1074.77~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1"],"bundled":358},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.142"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119","5.4.0-1108.120","5.4.0-1109.121","5.4.0-1110.122","5.4.0-1111.123","5.4.0-1112.124","5.4.0-1113.125","5.4.0-1114.126","5.4.0-1115.127","5.4.0-1116.128","5.4.0-1117.129","5.4.0-1118.130","5.4.0-1119.131","5.4.0-1120.132","5.4.0-1121.133","5.4.0-1122.134"],"bundled":401},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.142~18.04.1"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1","5.4.0-1108.120~18.04.1","5.4.0-1109.121~18.04.1","5.4.0-1110.122~18.04.1","5.4.0-1111.123~18.04.1","5.4.0-1112.124~18.04.1","5.4.0-1114.126~18.04.1","5.4.0-1115.127~18.04.1","5.4.0-1116.128~18.04.1","5.4.0-1117.129~18.04.1","5.4.0-1118.130~18.04.1","5.4.0-1119.131~18.04.1","5.4.0-1120.132~18.04.1","5.4.0-1121.133~18.04.1","5.4.0-1122.134~18.04.1"],"bundled":398}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/d038693e08adf9c162c6377800495e4f5a2df045","tags":["web"]},{"url":"https://git.kernel.org/stable/c/2b42e9587a7a9c7b824e0feb92958f258263963e","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/4268254a39484fc11ba991ae148bacbe75d9cc0a","tags":["x_transferred","Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40965","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-r49f-c964-6w6w"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-40965","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/40xxx/CVE-2024-40965.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-40965","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52513","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26753","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26781","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26790","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26793","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36479","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36484","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53183","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56539","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56571","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56610","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57892","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52434","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26954","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38571","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39474","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39482","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40949","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43875","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43876","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46694","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46711","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47735","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49926","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50175","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50181","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50183","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50295","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53140","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53144","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53166","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53207","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-54193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56557","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56567","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56641","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56653","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56687","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56718","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56729","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56769","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57874","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57910","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57926","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21658","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21670","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://nvd.nist.gov/vuln/detail/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://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://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://nvd.nist.gov/vuln/detail/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://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://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://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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/CVE-2024-39471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062501-CVE-2024-39471-3dee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-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://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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/CVE-2024-39499","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39499-ed0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071204-CVE-2024-39501-058b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39503","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/CVE-2024-40901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071207-CVE-2024-40901-05c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-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://nvd.nist.gov/vuln/detail/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://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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40945","tags":["advisory"]},{"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://nvd.nist.gov/vuln/detail/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","report"]},{"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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://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://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://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://nvd.nist.gov/vuln/detail/CVE-2024-41038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072923-CVE-2024-41038-41ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41039","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41039-b3bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/CVE-2024-41060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072905-CVE-2024-41060-b7de@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/CVE-2024-42084","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072942-CVE-2024-42084-9283@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42090","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072946-CVE-2024-42090-5687@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/CVE-2024-42124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073025-CVE-2024-42124-e4ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/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://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://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-20243551-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1183045","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1216223","tags":["report"]},{"url":"https://bugzilla.suse.com/1216776","tags":["report"]},{"url":"https://bugzilla.suse.com/1220382","tags":["report"]},{"url":"https://bugzilla.suse.com/1221527","tags":["report"]},{"url":"https://bugzilla.suse.com/1221610","tags":["report"]},{"url":"https://bugzilla.suse.com/1221650","tags":["report"]},{"url":"https://bugzilla.suse.com/1222629","tags":["report"]},{"url":"https://bugzilla.suse.com/1223600","tags":["report"]},{"url":"https://bugzilla.suse.com/1223848","tags":["report"]},{"url":"https://bugzilla.suse.com/1225487","tags":["report"]},{"url":"https://bugzilla.suse.com/1225812","tags":["report"]},{"url":"https://bugzilla.suse.com/1225903","tags":["report"]},{"url":"https://bugzilla.suse.com/1226003","tags":["report"]},{"url":"https://bugzilla.suse.com/1226507","tags":["report"]},{"url":"https://bugzilla.suse.com/1226606","tags":["report"]},{"url":"https://bugzilla.suse.com/1226666","tags":["report"]},{"url":"https://bugzilla.suse.com/1226846","tags":["report"]},{"url":"https://bugzilla.suse.com/1226860","tags":["report"]},{"url":"https://bugzilla.suse.com/1227487","tags":["report"]},{"url":"https://bugzilla.suse.com/1227694","tags":["report"]},{"url":"https://bugzilla.suse.com/1227726","tags":["report"]},{"url":"https://bugzilla.suse.com/1227819","tags":["report"]},{"url":"https://bugzilla.suse.com/1227885","tags":["report"]},{"url":"https://bugzilla.suse.com/1227890","tags":["report"]},{"url":"https://bugzilla.suse.com/1227962","tags":["report"]},{"url":"https://bugzilla.suse.com/1228090","tags":["report"]},{"url":"https://bugzilla.suse.com/1228140","tags":["report"]},{"url":"https://bugzilla.suse.com/1228244","tags":["report"]},{"url":"https://bugzilla.suse.com/1228507","tags":["report"]},{"url":"https://bugzilla.suse.com/1228771","tags":["report"]},{"url":"https://bugzilla.suse.com/1229001","tags":["report"]},{"url":"https://bugzilla.suse.com/1229004","tags":["report"]},{"url":"https://bugzilla.suse.com/1229019","tags":["report"]},{"url":"https://bugzilla.suse.com/1229086","tags":["report"]},{"url":"https://bugzilla.suse.com/1229167","tags":["report"]},{"url":"https://bugzilla.suse.com/1229169","tags":["report"]},{"url":"https://bugzilla.suse.com/1229289","tags":["report"]},{"url":"https://bugzilla.suse.com/1229334","tags":["report"]},{"url":"https://bugzilla.suse.com/1229362","tags":["report"]},{"url":"https://bugzilla.suse.com/1229363","tags":["report"]},{"url":"https://bugzilla.suse.com/1229364","tags":["report"]},{"url":"https://bugzilla.suse.com/1229371","tags":["report"]},{"url":"https://bugzilla.suse.com/1229380","tags":["report"]},{"url":"https://bugzilla.suse.com/1229389","tags":["report"]},{"url":"https://bugzilla.suse.com/1229394","tags":["report"]},{"url":"https://bugzilla.suse.com/1229429","tags":["report"]},{"url":"https://bugzilla.suse.com/1229443","tags":["report"]},{"url":"https://bugzilla.suse.com/1229452","tags":["report"]},{"url":"https://bugzilla.suse.com/1229455","tags":["report"]},{"url":"https://bugzilla.suse.com/1229456","tags":["report"]},{"url":"https://bugzilla.suse.com/1229494","tags":["report"]},{"url":"https://bugzilla.suse.com/1229585","tags":["report"]},{"url":"https://bugzilla.suse.com/1229753","tags":["report"]},{"url":"https://bugzilla.suse.com/1229764","tags":["report"]},{"url":"https://bugzilla.suse.com/1229768","tags":["report"]},{"url":"https://bugzilla.suse.com/1229790","tags":["report"]},{"url":"https://bugzilla.suse.com/1229810","tags":["report"]},{"url":"https://bugzilla.suse.com/1229899","tags":["report"]},{"url":"https://bugzilla.suse.com/1229928","tags":["report"]},{"url":"https://bugzilla.suse.com/1230015","tags":["report"]},{"url":"https://bugzilla.suse.com/1230119","tags":["report"]},{"url":"https://bugzilla.suse.com/1230123","tags":["report"]},{"url":"https://bugzilla.suse.com/1230124","tags":["report"]},{"url":"https://bugzilla.suse.com/1230125","tags":["report"]},{"url":"https://bugzilla.suse.com/1230169","tags":["report"]},{"url":"https://bugzilla.suse.com/1230170","tags":["report"]},{"url":"https://bugzilla.suse.com/1230171","tags":["report"]},{"url":"https://bugzilla.suse.com/1230173","tags":["report"]},{"url":"https://bugzilla.suse.com/1230174","tags":["report"]},{"url":"https://bugzilla.suse.com/1230175","tags":["report"]},{"url":"https://bugzilla.suse.com/1230176","tags":["report"]},{"url":"https://bugzilla.suse.com/1230178","tags":["report"]},{"url":"https://bugzilla.suse.com/1230180","tags":["report"]},{"url":"https://bugzilla.suse.com/1230181","tags":["report"]},{"url":"https://bugzilla.suse.com/1230185","tags":["report"]},{"url":"https://bugzilla.suse.com/1230191","tags":["report"]},{"url":"https://bugzilla.suse.com/1230192","tags":["report"]},{"url":"https://bugzilla.suse.com/1230193","tags":["report"]},{"url":"https://bugzilla.suse.com/1230194","tags":["report"]},{"url":"https://bugzilla.suse.com/1230195","tags":["report"]},{"url":"https://bugzilla.suse.com/1230200","tags":["report"]},{"url":"https://bugzilla.suse.com/1230204","tags":["report"]},{"url":"https://bugzilla.suse.com/1230206","tags":["report"]},{"url":"https://bugzilla.suse.com/1230207","tags":["report"]},{"url":"https://bugzilla.suse.com/1230209","tags":["report"]},{"url":"https://bugzilla.suse.com/1230211","tags":["report"]},{"url":"https://bugzilla.suse.com/1230213","tags":["report"]},{"url":"https://bugzilla.suse.com/1230217","tags":["report"]},{"url":"https://bugzilla.suse.com/1230221","tags":["report"]},{"url":"https://bugzilla.suse.com/1230224","tags":["report"]},{"url":"https://bugzilla.suse.com/1230230","tags":["report"]},{"url":"https://bugzilla.suse.com/1230232","tags":["report"]},{"url":"https://bugzilla.suse.com/1230233","tags":["report"]},{"url":"https://bugzilla.suse.com/1230240","tags":["report"]},{"url":"https://bugzilla.suse.com/1230244","tags":["report"]},{"url":"https://bugzilla.suse.com/1230245","tags":["report"]},{"url":"https://bugzilla.suse.com/1230247","tags":["report"]},{"url":"https://bugzilla.suse.com/1230248","tags":["report"]},{"url":"https://bugzilla.suse.com/1230269","tags":["report"]},{"url":"https://bugzilla.suse.com/1230270","tags":["report"]},{"url":"https://bugzilla.suse.com/1230295","tags":["report"]},{"url":"https://bugzilla.suse.com/1230340","tags":["report"]},{"url":"https://bugzilla.suse.com/1230350","tags":["report"]},{"url":"https://bugzilla.suse.com/1230413","tags":["report"]},{"url":"https://bugzilla.suse.com/1230426","tags":["report"]},{"url":"https://bugzilla.suse.com/1230430","tags":["report"]},{"url":"https://bugzilla.suse.com/1230431","tags":["report"]},{"url":"https://bugzilla.suse.com/1230432","tags":["report"]},{"url":"https://bugzilla.suse.com/1230433","tags":["report"]},{"url":"https://bugzilla.suse.com/1230434","tags":["report"]},{"url":"https://bugzilla.suse.com/1230435","tags":["report"]},{"url":"https://bugzilla.suse.com/1230440","tags":["report"]},{"url":"https://bugzilla.suse.com/1230441","tags":["report"]},{"url":"https://bugzilla.suse.com/1230442","tags":["report"]},{"url":"https://bugzilla.suse.com/1230444","tags":["report"]},{"url":"https://bugzilla.suse.com/1230450","tags":["report"]},{"url":"https://bugzilla.suse.com/1230451","tags":["report"]},{"url":"https://bugzilla.suse.com/1230454","tags":["report"]},{"url":"https://bugzilla.suse.com/1230455","tags":["report"]},{"url":"https://bugzilla.suse.com/1230457","tags":["report"]},{"url":"https://bugzilla.suse.com/1230459","tags":["report"]},{"url":"https://bugzilla.suse.com/1230506","tags":["report"]},{"url":"https://bugzilla.suse.com/1230507","tags":["report"]},{"url":"https://bugzilla.suse.com/1230511","tags":["report"]},{"url":"https://bugzilla.suse.com/1230515","tags":["report"]},{"url":"https://bugzilla.suse.com/1230517","tags":["report"]},{"url":"https://bugzilla.suse.com/1230518","tags":["report"]},{"url":"https://bugzilla.suse.com/1230519","tags":["report"]},{"url":"https://bugzilla.suse.com/1230520","tags":["report"]},{"url":"https://bugzilla.suse.com/1230521","tags":["report"]},{"url":"https://bugzilla.suse.com/1230524","tags":["report"]},{"url":"https://bugzilla.suse.com/1230526","tags":["report"]},{"url":"https://bugzilla.suse.com/1230533","tags":["report"]},{"url":"https://bugzilla.suse.com/1230535","tags":["report"]},{"url":"https://bugzilla.suse.com/1230539","tags":["report"]},{"url":"https://bugzilla.suse.com/1230540","tags":["report"]},{"url":"https://bugzilla.suse.com/1230549","tags":["report"]},{"url":"https://bugzilla.suse.com/1230556","tags":["report"]},{"url":"https://bugzilla.suse.com/1230562","tags":["report"]},{"url":"https://bugzilla.suse.com/1230563","tags":["report"]},{"url":"https://bugzilla.suse.com/1230564","tags":["report"]},{"url":"https://bugzilla.suse.com/1230580","tags":["report"]},{"url":"https://bugzilla.suse.com/1230582","tags":["report"]},{"url":"https://bugzilla.suse.com/1230589","tags":["report"]},{"url":"https://bugzilla.suse.com/1230602","tags":["report"]},{"url":"https://bugzilla.suse.com/1230699","tags":["report"]},{"url":"https://bugzilla.suse.com/1230700","tags":["report"]},{"url":"https://bugzilla.suse.com/1230701","tags":["report"]},{"url":"https://bugzilla.suse.com/1230702","tags":["report"]},{"url":"https://bugzilla.suse.com/1230703","tags":["report"]},{"url":"https://bugzilla.suse.com/1230704","tags":["report"]},{"url":"https://bugzilla.suse.com/1230705","tags":["report"]},{"url":"https://bugzilla.suse.com/1230706","tags":["report"]},{"url":"https://bugzilla.suse.com/1230709","tags":["report"]},{"url":"https://bugzilla.suse.com/1230711","tags":["report"]},{"url":"https://bugzilla.suse.com/1230712","tags":["report"]},{"url":"https://bugzilla.suse.com/1230715","tags":["report"]},{"url":"https://bugzilla.suse.com/1230719","tags":["report"]},{"url":"https://bugzilla.suse.com/1230722","tags":["report"]},{"url":"https://bugzilla.suse.com/1230724","tags":["report"]},{"url":"https://bugzilla.suse.com/1230725","tags":["report"]},{"url":"https://bugzilla.suse.com/1230726","tags":["report"]},{"url":"https://bugzilla.suse.com/1230727","tags":["report"]},{"url":"https://bugzilla.suse.com/1230730","tags":["report"]},{"url":"https://bugzilla.suse.com/1230731","tags":["report"]},{"url":"https://bugzilla.suse.com/1230732","tags":["report"]},{"url":"https://bugzilla.suse.com/1230747","tags":["report"]},{"url":"https://bugzilla.suse.com/1230748","tags":["report"]},{"url":"https://bugzilla.suse.com/1230749","tags":["report"]},{"url":"https://bugzilla.suse.com/1230751","tags":["report"]},{"url":"https://bugzilla.suse.com/1230752","tags":["report"]},{"url":"https://bugzilla.suse.com/1230753","tags":["report"]},{"url":"https://bugzilla.suse.com/1230756","tags":["report"]},{"url":"https://bugzilla.suse.com/1230761","tags":["report"]},{"url":"https://bugzilla.suse.com/1230766","tags":["report"]},{"url":"https://bugzilla.suse.com/1230767","tags":["report"]},{"url":"https://bugzilla.suse.com/1230768","tags":["report"]},{"url":"https://bugzilla.suse.com/1230771","tags":["report"]},{"url":"https://bugzilla.suse.com/1230772","tags":["report"]},{"url":"https://bugzilla.suse.com/1230775","tags":["report"]},{"url":"https://bugzilla.suse.com/1230776","tags":["report"]},{"url":"https://bugzilla.suse.com/1230780","tags":["report"]},{"url":"https://bugzilla.suse.com/1230783","tags":["report"]},{"url":"https://bugzilla.suse.com/1230786","tags":["report"]},{"url":"https://bugzilla.suse.com/1230787","tags":["report"]},{"url":"https://bugzilla.suse.com/1230791","tags":["report"]},{"url":"https://bugzilla.suse.com/1230794","tags":["report"]},{"url":"https://bugzilla.suse.com/1230796","tags":["report"]},{"url":"https://bugzilla.suse.com/1230802","tags":["report"]},{"url":"https://bugzilla.suse.com/1230806","tags":["report"]},{"url":"https://bugzilla.suse.com/1230808","tags":["report"]},{"url":"https://bugzilla.suse.com/1230809","tags":["report"]},{"url":"https://bugzilla.suse.com/1230810","tags":["report"]},{"url":"https://bugzilla.suse.com/1230812","tags":["report"]},{"url":"https://bugzilla.suse.com/1230813","tags":["report"]},{"url":"https://bugzilla.suse.com/1230814","tags":["report"]},{"url":"https://bugzilla.suse.com/1230815","tags":["report"]},{"url":"https://bugzilla.suse.com/1230821","tags":["report"]},{"url":"https://bugzilla.suse.com/1230825","tags":["report"]},{"url":"https://bugzilla.suse.com/1230830","tags":["report"]},{"url":"https://bugzilla.suse.com/1230831","tags":["report"]},{"url":"https://bugzilla.suse.com/1230854","tags":["report"]},{"url":"https://bugzilla.suse.com/1230948","tags":["report"]},{"url":"https://bugzilla.suse.com/1231008","tags":["report"]},{"url":"https://bugzilla.suse.com/1231035","tags":["report"]},{"url":"https://bugzilla.suse.com/1231120","tags":["report"]},{"url":"https://bugzilla.suse.com/1231146","tags":["report"]},{"url":"https://bugzilla.suse.com/1231182","tags":["report"]},{"url":"https://bugzilla.suse.com/1231183","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52610","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46774","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46822","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243553-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1229748","tags":["report"]},{"url":"https://bugzilla.suse.com/1230212","tags":["report"]},{"url":"https://bugzilla.suse.com/1230542","tags":["report"]},{"url":"https://bugzilla.suse.com/1230707","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46727","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243561-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243564-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243983-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1204171","tags":["report"]},{"url":"https://bugzilla.suse.com/1205796","tags":["report"]},{"url":"https://bugzilla.suse.com/1206188","tags":["report"]},{"url":"https://bugzilla.suse.com/1206344","tags":["report"]},{"url":"https://bugzilla.suse.com/1209290","tags":["report"]},{"url":"https://bugzilla.suse.com/1210449","tags":["report"]},{"url":"https://bugzilla.suse.com/1210627","tags":["report"]},{"url":"https://bugzilla.suse.com/1213034","tags":["report"]},{"url":"https://bugzilla.suse.com/1216813","tags":["report"]},{"url":"https://bugzilla.suse.com/1218562","tags":["report"]},{"url":"https://bugzilla.suse.com/1223384","tags":["report"]},{"url":"https://bugzilla.suse.com/1223524","tags":["report"]},{"url":"https://bugzilla.suse.com/1223824","tags":["report"]},{"url":"https://bugzilla.suse.com/1225189","tags":["report"]},{"url":"https://bugzilla.suse.com/1225336","tags":["report"]},{"url":"https://bugzilla.suse.com/1225611","tags":["report"]},{"url":"https://bugzilla.suse.com/1225762","tags":["report"]},{"url":"https://bugzilla.suse.com/1226498","tags":["report"]},{"url":"https://bugzilla.suse.com/1226797","tags":["report"]},{"url":"https://bugzilla.suse.com/1227437","tags":["report"]},{"url":"https://bugzilla.suse.com/1228119","tags":["report"]},{"url":"https://bugzilla.suse.com/1228269","tags":["report"]},{"url":"https://bugzilla.suse.com/1228709","tags":["report"]},{"url":"https://bugzilla.suse.com/1228743","tags":["report"]},{"url":"https://bugzilla.suse.com/1229005","tags":["report"]},{"url":"https://bugzilla.suse.com/1229450","tags":["report"]},{"url":"https://bugzilla.suse.com/1229454","tags":["report"]},{"url":"https://bugzilla.suse.com/1229556","tags":["report"]},{"url":"https://bugzilla.suse.com/1229769","tags":["report"]},{"url":"https://bugzilla.suse.com/1229837","tags":["report"]},{"url":"https://bugzilla.suse.com/1230179","tags":["report"]},{"url":"https://bugzilla.suse.com/1230405","tags":["report"]},{"url":"https://bugzilla.suse.com/1230414","tags":["report"]},{"url":"https://bugzilla.suse.com/1230429","tags":["report"]},{"url":"https://bugzilla.suse.com/1230456","tags":["report"]},{"url":"https://bugzilla.suse.com/1230600","tags":["report"]},{"url":"https://bugzilla.suse.com/1230620","tags":["report"]},{"url":"https://bugzilla.suse.com/1230773","tags":["report"]},{"url":"https://bugzilla.suse.com/1230801","tags":["report"]},{"url":"https://bugzilla.suse.com/1230903","tags":["report"]},{"url":"https://bugzilla.suse.com/1230918","tags":["report"]},{"url":"https://bugzilla.suse.com/1231016","tags":["report"]},{"url":"https://bugzilla.suse.com/1231072","tags":["report"]},{"url":"https://bugzilla.suse.com/1231073","tags":["report"]},{"url":"https://bugzilla.suse.com/1231094","tags":["report"]},{"url":"https://bugzilla.suse.com/1231096","tags":["report"]},{"url":"https://bugzilla.suse.com/1231105","tags":["report"]},{"url":"https://bugzilla.suse.com/1231114","tags":["report"]},{"url":"https://bugzilla.suse.com/1231148","tags":["report"]},{"url":"https://bugzilla.suse.com/1231179","tags":["report"]},{"url":"https://bugzilla.suse.com/1231191","tags":["report"]},{"url":"https://bugzilla.suse.com/1231193","tags":["report"]},{"url":"https://bugzilla.suse.com/1231195","tags":["report"]},{"url":"https://bugzilla.suse.com/1231197","tags":["report"]},{"url":"https://bugzilla.suse.com/1231200","tags":["report"]},{"url":"https://bugzilla.suse.com/1231203","tags":["report"]},{"url":"https://bugzilla.suse.com/1231293","tags":["report"]},{"url":"https://bugzilla.suse.com/1231344","tags":["report"]},{"url":"https://bugzilla.suse.com/1231375","tags":["report"]},{"url":"https://bugzilla.suse.com/1231383","tags":["report"]},{"url":"https://bugzilla.suse.com/1231439","tags":["report"]},{"url":"https://bugzilla.suse.com/1231442","tags":["report"]},{"url":"https://bugzilla.suse.com/1231496","tags":["report"]},{"url":"https://bugzilla.suse.com/1231502","tags":["report"]},{"url":"https://bugzilla.suse.com/1231539","tags":["report"]},{"url":"https://bugzilla.suse.com/1231540","tags":["report"]},{"url":"https://bugzilla.suse.com/1231578","tags":["report"]},{"url":"https://bugzilla.suse.com/1231673","tags":["report"]},{"url":"https://bugzilla.suse.com/1231857","tags":["report"]},{"url":"https://bugzilla.suse.com/1231861","tags":["report"]},{"url":"https://bugzilla.suse.com/1231872","tags":["report"]},{"url":"https://bugzilla.suse.com/1231883","tags":["report"]},{"url":"https://bugzilla.suse.com/1231885","tags":["report"]},{"url":"https://bugzilla.suse.com/1231887","tags":["report"]},{"url":"https://bugzilla.suse.com/1231888","tags":["report"]},{"url":"https://bugzilla.suse.com/1231889","tags":["report"]},{"url":"https://bugzilla.suse.com/1231890","tags":["report"]},{"url":"https://bugzilla.suse.com/1231892","tags":["report"]},{"url":"https://bugzilla.suse.com/1231893","tags":["report"]},{"url":"https://bugzilla.suse.com/1231895","tags":["report"]},{"url":"https://bugzilla.suse.com/1231896","tags":["report"]},{"url":"https://bugzilla.suse.com/1231897","tags":["report"]},{"url":"https://bugzilla.suse.com/1231902","tags":["report"]},{"url":"https://bugzilla.suse.com/1231903","tags":["report"]},{"url":"https://bugzilla.suse.com/1231907","tags":["report"]},{"url":"https://bugzilla.suse.com/1231914","tags":["report"]},{"url":"https://bugzilla.suse.com/1231929","tags":["report"]},{"url":"https://bugzilla.suse.com/1231935","tags":["report"]},{"url":"https://bugzilla.suse.com/1231936","tags":["report"]},{"url":"https://bugzilla.suse.com/1231937","tags":["report"]},{"url":"https://bugzilla.suse.com/1231938","tags":["report"]},{"url":"https://bugzilla.suse.com/1231939","tags":["report"]},{"url":"https://bugzilla.suse.com/1231940","tags":["report"]},{"url":"https://bugzilla.suse.com/1231941","tags":["report"]},{"url":"https://bugzilla.suse.com/1231942","tags":["report"]},{"url":"https://bugzilla.suse.com/1231944","tags":["report"]},{"url":"https://bugzilla.suse.com/1231950","tags":["report"]},{"url":"https://bugzilla.suse.com/1231954","tags":["report"]},{"url":"https://bugzilla.suse.com/1231958","tags":["report"]},{"url":"https://bugzilla.suse.com/1231960","tags":["report"]},{"url":"https://bugzilla.suse.com/1231961","tags":["report"]},{"url":"https://bugzilla.suse.com/1231962","tags":["report"]},{"url":"https://bugzilla.suse.com/1231965","tags":["report"]},{"url":"https://bugzilla.suse.com/1231967","tags":["report"]},{"url":"https://bugzilla.suse.com/1231968","tags":["report"]},{"url":"https://bugzilla.suse.com/1231972","tags":["report"]},{"url":"https://bugzilla.suse.com/1231973","tags":["report"]},{"url":"https://bugzilla.suse.com/1231976","tags":["report"]},{"url":"https://bugzilla.suse.com/1231979","tags":["report"]},{"url":"https://bugzilla.suse.com/1231987","tags":["report"]},{"url":"https://bugzilla.suse.com/1231988","tags":["report"]},{"url":"https://bugzilla.suse.com/1231990","tags":["report"]},{"url":"https://bugzilla.suse.com/1231992","tags":["report"]},{"url":"https://bugzilla.suse.com/1231995","tags":["report"]},{"url":"https://bugzilla.suse.com/1231996","tags":["report"]},{"url":"https://bugzilla.suse.com/1231997","tags":["report"]},{"url":"https://bugzilla.suse.com/1231998","tags":["report"]},{"url":"https://bugzilla.suse.com/1232001","tags":["report"]},{"url":"https://bugzilla.suse.com/1232004","tags":["report"]},{"url":"https://bugzilla.suse.com/1232005","tags":["report"]},{"url":"https://bugzilla.suse.com/1232006","tags":["report"]},{"url":"https://bugzilla.suse.com/1232007","tags":["report"]},{"url":"https://bugzilla.suse.com/1232025","tags":["report"]},{"url":"https://bugzilla.suse.com/1232026","tags":["report"]},{"url":"https://bugzilla.suse.com/1232033","tags":["report"]},{"url":"https://bugzilla.suse.com/1232034","tags":["report"]},{"url":"https://bugzilla.suse.com/1232035","tags":["report"]},{"url":"https://bugzilla.suse.com/1232036","tags":["report"]},{"url":"https://bugzilla.suse.com/1232037","tags":["report"]},{"url":"https://bugzilla.suse.com/1232038","tags":["report"]},{"url":"https://bugzilla.suse.com/1232039","tags":["report"]},{"url":"https://bugzilla.suse.com/1232043","tags":["report"]},{"url":"https://bugzilla.suse.com/1232049","tags":["report"]},{"url":"https://bugzilla.suse.com/1232067","tags":["report"]},{"url":"https://bugzilla.suse.com/1232069","tags":["report"]},{"url":"https://bugzilla.suse.com/1232070","tags":["report"]},{"url":"https://bugzilla.suse.com/1232071","tags":["report"]},{"url":"https://bugzilla.suse.com/1232075","tags":["report"]},{"url":"https://bugzilla.suse.com/1232083","tags":["report"]},{"url":"https://bugzilla.suse.com/1232084","tags":["report"]},{"url":"https://bugzilla.suse.com/1232085","tags":["report"]},{"url":"https://bugzilla.suse.com/1232089","tags":["report"]},{"url":"https://bugzilla.suse.com/1232097","tags":["report"]},{"url":"https://bugzilla.suse.com/1232104","tags":["report"]},{"url":"https://bugzilla.suse.com/1232105","tags":["report"]},{"url":"https://bugzilla.suse.com/1232108","tags":["report"]},{"url":"https://bugzilla.suse.com/1232114","tags":["report"]},{"url":"https://bugzilla.suse.com/1232116","tags":["report"]},{"url":"https://bugzilla.suse.com/1232119","tags":["report"]},{"url":"https://bugzilla.suse.com/1232120","tags":["report"]},{"url":"https://bugzilla.suse.com/1232123","tags":["report"]},{"url":"https://bugzilla.suse.com/1232124","tags":["report"]},{"url":"https://bugzilla.suse.com/1232133","tags":["report"]},{"url":"https://bugzilla.suse.com/1232135","tags":["report"]},{"url":"https://bugzilla.suse.com/1232136","tags":["report"]},{"url":"https://bugzilla.suse.com/1232140","tags":["report"]},{"url":"https://bugzilla.suse.com/1232145","tags":["report"]},{"url":"https://bugzilla.suse.com/1232149","tags":["report"]},{"url":"https://bugzilla.suse.com/1232150","tags":["report"]},{"url":"https://bugzilla.suse.com/1232151","tags":["report"]},{"url":"https://bugzilla.suse.com/1232154","tags":["report"]},{"url":"https://bugzilla.suse.com/1232155","tags":["report"]},{"url":"https://bugzilla.suse.com/1232160","tags":["report"]},{"url":"https://bugzilla.suse.com/1232163","tags":["report"]},{"url":"https://bugzilla.suse.com/1232164","tags":["report"]},{"url":"https://bugzilla.suse.com/1232170","tags":["report"]},{"url":"https://bugzilla.suse.com/1232172","tags":["report"]},{"url":"https://bugzilla.suse.com/1232174","tags":["report"]},{"url":"https://bugzilla.suse.com/1232175","tags":["report"]},{"url":"https://bugzilla.suse.com/1232191","tags":["report"]},{"url":"https://bugzilla.suse.com/1232196","tags":["report"]},{"url":"https://bugzilla.suse.com/1232199","tags":["report"]},{"url":"https://bugzilla.suse.com/1232200","tags":["report"]},{"url":"https://bugzilla.suse.com/1232201","tags":["report"]},{"url":"https://bugzilla.suse.com/1232217","tags":["report"]},{"url":"https://bugzilla.suse.com/1232220","tags":["report"]},{"url":"https://bugzilla.suse.com/1232221","tags":["report"]},{"url":"https://bugzilla.suse.com/1232229","tags":["report"]},{"url":"https://bugzilla.suse.com/1232233","tags":["report"]},{"url":"https://bugzilla.suse.com/1232237","tags":["report"]},{"url":"https://bugzilla.suse.com/1232251","tags":["report"]},{"url":"https://bugzilla.suse.com/1232253","tags":["report"]},{"url":"https://bugzilla.suse.com/1232259","tags":["report"]},{"url":"https://bugzilla.suse.com/1232260","tags":["report"]},{"url":"https://bugzilla.suse.com/1232262","tags":["report"]},{"url":"https://bugzilla.suse.com/1232263","tags":["report"]},{"url":"https://bugzilla.suse.com/1232282","tags":["report"]},{"url":"https://bugzilla.suse.com/1232285","tags":["report"]},{"url":"https://bugzilla.suse.com/1232286","tags":["report"]},{"url":"https://bugzilla.suse.com/1232304","tags":["report"]},{"url":"https://bugzilla.suse.com/1232305","tags":["report"]},{"url":"https://bugzilla.suse.com/1232307","tags":["report"]},{"url":"https://bugzilla.suse.com/1232309","tags":["report"]},{"url":"https://bugzilla.suse.com/1232310","tags":["report"]},{"url":"https://bugzilla.suse.com/1232313","tags":["report"]},{"url":"https://bugzilla.suse.com/1232314","tags":["report"]},{"url":"https://bugzilla.suse.com/1232316","tags":["report"]},{"url":"https://bugzilla.suse.com/1232329","tags":["report"]},{"url":"https://bugzilla.suse.com/1232332","tags":["report"]},{"url":"https://bugzilla.suse.com/1232335","tags":["report"]},{"url":"https://bugzilla.suse.com/1232337","tags":["report"]},{"url":"https://bugzilla.suse.com/1232342","tags":["report"]},{"url":"https://bugzilla.suse.com/1232345","tags":["report"]},{"url":"https://bugzilla.suse.com/1232352","tags":["report"]},{"url":"https://bugzilla.suse.com/1232354","tags":["report"]},{"url":"https://bugzilla.suse.com/1232355","tags":["report"]},{"url":"https://bugzilla.suse.com/1232358","tags":["report"]},{"url":"https://bugzilla.suse.com/1232361","tags":["report"]},{"url":"https://bugzilla.suse.com/1232366","tags":["report"]},{"url":"https://bugzilla.suse.com/1232367","tags":["report"]},{"url":"https://bugzilla.suse.com/1232368","tags":["report"]},{"url":"https://bugzilla.suse.com/1232369","tags":["report"]},{"url":"https://bugzilla.suse.com/1232374","tags":["report"]},{"url":"https://bugzilla.suse.com/1232381","tags":["report"]},{"url":"https://bugzilla.suse.com/1232383","tags":["report"]},{"url":"https://bugzilla.suse.com/1232392","tags":["report"]},{"url":"https://bugzilla.suse.com/1232395","tags":["report"]},{"url":"https://bugzilla.suse.com/1232418","tags":["report"]},{"url":"https://bugzilla.suse.com/1232424","tags":["report"]},{"url":"https://bugzilla.suse.com/1232432","tags":["report"]},{"url":"https://bugzilla.suse.com/1232435","tags":["report"]},{"url":"https://bugzilla.suse.com/1232442","tags":["report"]},{"url":"https://bugzilla.suse.com/1232446","tags":["report"]},{"url":"https://bugzilla.suse.com/1232501","tags":["report"]},{"url":"https://bugzilla.suse.com/1232519","tags":["report"]},{"url":"https://bugzilla.suse.com/1232630","tags":["report"]},{"url":"https://bugzilla.suse.com/1232631","tags":["report"]},{"url":"https://bugzilla.suse.com/1232632","tags":["report"]},{"url":"https://bugzilla.suse.com/1232757","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50081","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243985-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1054914","tags":["report"]},{"url":"https://bugzilla.suse.com/1065729","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1226631","tags":["report"]},{"url":"https://bugzilla.suse.com/1228747","tags":["report"]},{"url":"https://bugzilla.suse.com/1229891","tags":["report"]},{"url":"https://bugzilla.suse.com/1230055","tags":["report"]},{"url":"https://bugzilla.suse.com/1230289","tags":["report"]},{"url":"https://bugzilla.suse.com/1230550","tags":["report"]},{"url":"https://bugzilla.suse.com/1230763","tags":["report"]},{"url":"https://bugzilla.suse.com/1230774","tags":["report"]},{"url":"https://bugzilla.suse.com/1231084","tags":["report"]},{"url":"https://bugzilla.suse.com/1231085","tags":["report"]},{"url":"https://bugzilla.suse.com/1231087","tags":["report"]},{"url":"https://bugzilla.suse.com/1231115","tags":["report"]},{"url":"https://bugzilla.suse.com/1231277","tags":["report"]},{"url":"https://bugzilla.suse.com/1231327","tags":["report"]},{"url":"https://bugzilla.suse.com/1231991","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46857","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244100-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1082555","tags":["report"]},{"url":"https://bugzilla.suse.com/1176081","tags":["report"]},{"url":"https://bugzilla.suse.com/1219125","tags":["report"]},{"url":"https://bugzilla.suse.com/1220439","tags":["report"]},{"url":"https://bugzilla.suse.com/1221980","tags":["report"]},{"url":"https://bugzilla.suse.com/1226585","tags":["report"]},{"url":"https://bugzilla.suse.com/1227941","tags":["report"]},{"url":"https://bugzilla.suse.com/1227947","tags":["report"]},{"url":"https://bugzilla.suse.com/1227952","tags":["report"]},{"url":"https://bugzilla.suse.com/1228000","tags":["report"]},{"url":"https://bugzilla.suse.com/1228410","tags":["report"]},{"url":"https://bugzilla.suse.com/1228564","tags":["report"]},{"url":"https://bugzilla.suse.com/1228620","tags":["report"]},{"url":"https://bugzilla.suse.com/1229042","tags":["report"]},{"url":"https://bugzilla.suse.com/1229154","tags":["report"]},{"url":"https://bugzilla.suse.com/1229568","tags":["report"]},{"url":"https://bugzilla.suse.com/1231111","tags":["report"]},{"url":"https://bugzilla.suse.com/1231537","tags":["report"]},{"url":"https://bugzilla.suse.com/1231858","tags":["report"]},{"url":"https://bugzilla.suse.com/1231859","tags":["report"]},{"url":"https://bugzilla.suse.com/1231864","tags":["report"]},{"url":"https://bugzilla.suse.com/1232016","tags":["report"]},{"url":"https://bugzilla.suse.com/1232047","tags":["report"]},{"url":"https://bugzilla.suse.com/1232056","tags":["report"]},{"url":"https://bugzilla.suse.com/1232111","tags":["report"]},{"url":"https://bugzilla.suse.com/1232126","tags":["report"]},{"url":"https://bugzilla.suse.com/1232134","tags":["report"]},{"url":"https://bugzilla.suse.com/1232141","tags":["report"]},{"url":"https://bugzilla.suse.com/1232142","tags":["report"]},{"url":"https://bugzilla.suse.com/1232152","tags":["report"]},{"url":"https://bugzilla.suse.com/1232180","tags":["report"]},{"url":"https://bugzilla.suse.com/1232218","tags":["report"]},{"url":"https://bugzilla.suse.com/1232236","tags":["report"]},{"url":"https://bugzilla.suse.com/1232339","tags":["report"]},{"url":"https://bugzilla.suse.com/1232394","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-46343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50007","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244364-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1218644","tags":["report"]},{"url":"https://bugzilla.suse.com/1221309","tags":["report"]},{"url":"https://bugzilla.suse.com/1221333","tags":["report"]},{"url":"https://bugzilla.suse.com/1222364","tags":["report"]},{"url":"https://bugzilla.suse.com/1222590","tags":["report"]},{"url":"https://bugzilla.suse.com/1223202","tags":["report"]},{"url":"https://bugzilla.suse.com/1223656","tags":["report"]},{"url":"https://bugzilla.suse.com/1223919","tags":["report"]},{"url":"https://bugzilla.suse.com/1223942","tags":["report"]},{"url":"https://bugzilla.suse.com/1224518","tags":["report"]},{"url":"https://bugzilla.suse.com/1224526","tags":["report"]},{"url":"https://bugzilla.suse.com/1224574","tags":["report"]},{"url":"https://bugzilla.suse.com/1225725","tags":["report"]},{"url":"https://bugzilla.suse.com/1225730","tags":["report"]},{"url":"https://bugzilla.suse.com/1225742","tags":["report"]},{"url":"https://bugzilla.suse.com/1225764","tags":["report"]},{"url":"https://bugzilla.suse.com/1226560","tags":["report"]},{"url":"https://bugzilla.suse.com/1226592","tags":["report"]},{"url":"https://bugzilla.suse.com/1226748","tags":["report"]},{"url":"https://bugzilla.suse.com/1226872","tags":["report"]},{"url":"https://bugzilla.suse.com/1227853","tags":["report"]},{"url":"https://bugzilla.suse.com/1228430","tags":["report"]},{"url":"https://bugzilla.suse.com/1228486","tags":["report"]},{"url":"https://bugzilla.suse.com/1228650","tags":["report"]},{"url":"https://bugzilla.suse.com/1228857","tags":["report"]},{"url":"https://bugzilla.suse.com/1229312","tags":["report"]},{"url":"https://bugzilla.suse.com/1229752","tags":["report"]},{"url":"https://bugzilla.suse.com/1229808","tags":["report"]},{"url":"https://bugzilla.suse.com/1230220","tags":["report"]},{"url":"https://bugzilla.suse.com/1230231","tags":["report"]},{"url":"https://bugzilla.suse.com/1230558","tags":["report"]},{"url":"https://bugzilla.suse.com/1230827","tags":["report"]},{"url":"https://bugzilla.suse.com/1231083","tags":["report"]},{"url":"https://bugzilla.suse.com/1231089","tags":["report"]},{"url":"https://bugzilla.suse.com/1231098","tags":["report"]},{"url":"https://bugzilla.suse.com/1231101","tags":["report"]},{"url":"https://bugzilla.suse.com/1231108","tags":["report"]},{"url":"https://bugzilla.suse.com/1231132","tags":["report"]},{"url":"https://bugzilla.suse.com/1231135","tags":["report"]},{"url":"https://bugzilla.suse.com/1231138","tags":["report"]},{"url":"https://bugzilla.suse.com/1231169","tags":["report"]},{"url":"https://bugzilla.suse.com/1231178","tags":["report"]},{"url":"https://bugzilla.suse.com/1231180","tags":["report"]},{"url":"https://bugzilla.suse.com/1231181","tags":["report"]},{"url":"https://bugzilla.suse.com/1231187","tags":["report"]},{"url":"https://bugzilla.suse.com/1231202","tags":["report"]},{"url":"https://bugzilla.suse.com/1231434","tags":["report"]},{"url":"https://bugzilla.suse.com/1231441","tags":["report"]},{"url":"https://bugzilla.suse.com/1231452","tags":["report"]},{"url":"https://bugzilla.suse.com/1231465","tags":["report"]},{"url":"https://bugzilla.suse.com/1231474","tags":["report"]},{"url":"https://bugzilla.suse.com/1231481","tags":["report"]},{"url":"https://bugzilla.suse.com/1231541","tags":["report"]},{"url":"https://bugzilla.suse.com/1231646","tags":["report"]},{"url":"https://bugzilla.suse.com/1231849","tags":["report"]},{"url":"https://bugzilla.suse.com/1231856","tags":["report"]},{"url":"https://bugzilla.suse.com/1231904","tags":["report"]},{"url":"https://bugzilla.suse.com/1231916","tags":["report"]},{"url":"https://bugzilla.suse.com/1231920","tags":["report"]},{"url":"https://bugzilla.suse.com/1231923","tags":["report"]},{"url":"https://bugzilla.suse.com/1231930","tags":["report"]},{"url":"https://bugzilla.suse.com/1231931","tags":["report"]},{"url":"https://bugzilla.suse.com/1231947","tags":["report"]},{"url":"https://bugzilla.suse.com/1231952","tags":["report"]},{"url":"https://bugzilla.suse.com/1231953","tags":["report"]},{"url":"https://bugzilla.suse.com/1231959","tags":["report"]},{"url":"https://bugzilla.suse.com/1231978","tags":["report"]},{"url":"https://bugzilla.suse.com/1232013","tags":["report"]},{"url":"https://bugzilla.suse.com/1232015","tags":["report"]},{"url":"https://bugzilla.suse.com/1232017","tags":["report"]},{"url":"https://bugzilla.suse.com/1232027","tags":["report"]},{"url":"https://bugzilla.suse.com/1232028","tags":["report"]},{"url":"https://bugzilla.suse.com/1232048","tags":["report"]},{"url":"https://bugzilla.suse.com/1232050","tags":["report"]},{"url":"https://bugzilla.suse.com/1232076","tags":["report"]},{"url":"https://bugzilla.suse.com/1232080","tags":["report"]},{"url":"https://bugzilla.suse.com/1232094","tags":["report"]},{"url":"https://bugzilla.suse.com/1232096","tags":["report"]},{"url":"https://bugzilla.suse.com/1232098","tags":["report"]},{"url":"https://bugzilla.suse.com/1232147","tags":["report"]},{"url":"https://bugzilla.suse.com/1232159","tags":["report"]},{"url":"https://bugzilla.suse.com/1232162","tags":["report"]},{"url":"https://bugzilla.suse.com/1232165","tags":["report"]},{"url":"https://bugzilla.suse.com/1232185","tags":["report"]},{"url":"https://bugzilla.suse.com/1232187","tags":["report"]},{"url":"https://bugzilla.suse.com/1232189","tags":["report"]},{"url":"https://bugzilla.suse.com/1232195","tags":["report"]},{"url":"https://bugzilla.suse.com/1232198","tags":["report"]},{"url":"https://bugzilla.suse.com/1232224","tags":["report"]},{"url":"https://bugzilla.suse.com/1232232","tags":["report"]},{"url":"https://bugzilla.suse.com/1232254","tags":["report"]},{"url":"https://bugzilla.suse.com/1232255","tags":["report"]},{"url":"https://bugzilla.suse.com/1232264","tags":["report"]},{"url":"https://bugzilla.suse.com/1232272","tags":["report"]},{"url":"https://bugzilla.suse.com/1232279","tags":["report"]},{"url":"https://bugzilla.suse.com/1232287","tags":["report"]},{"url":"https://bugzilla.suse.com/1232293","tags":["report"]},{"url":"https://bugzilla.suse.com/1232312","tags":["report"]},{"url":"https://bugzilla.suse.com/1232317","tags":["report"]},{"url":"https://bugzilla.suse.com/1232318","tags":["report"]},{"url":"https://bugzilla.suse.com/1232333","tags":["report"]},{"url":"https://bugzilla.suse.com/1232334","tags":["report"]},{"url":"https://bugzilla.suse.com/1232349","tags":["report"]},{"url":"https://bugzilla.suse.com/1232357","tags":["report"]},{"url":"https://bugzilla.suse.com/1232359","tags":["report"]},{"url":"https://bugzilla.suse.com/1232362","tags":["report"]},{"url":"https://bugzilla.suse.com/1232364","tags":["report"]},{"url":"https://bugzilla.suse.com/1232370","tags":["report"]},{"url":"https://bugzilla.suse.com/1232371","tags":["report"]},{"url":"https://bugzilla.suse.com/1232378","tags":["report"]},{"url":"https://bugzilla.suse.com/1232385","tags":["report"]},{"url":"https://bugzilla.suse.com/1232387","tags":["report"]},{"url":"https://bugzilla.suse.com/1232413","tags":["report"]},{"url":"https://bugzilla.suse.com/1232416","tags":["report"]},{"url":"https://bugzilla.suse.com/1232436","tags":["report"]},{"url":"https://bugzilla.suse.com/1232483","tags":["report"]},{"url":"https://bugzilla.suse.com/1232500","tags":["report"]},{"url":"https://bugzilla.suse.com/1232503","tags":["report"]},{"url":"https://bugzilla.suse.com/1232504","tags":["report"]},{"url":"https://bugzilla.suse.com/1232507","tags":["report"]},{"url":"https://bugzilla.suse.com/1232520","tags":["report"]},{"url":"https://bugzilla.suse.com/1232552","tags":["report"]},{"url":"https://bugzilla.suse.com/1232819","tags":["report"]},{"url":"https://bugzilla.suse.com/1232860","tags":["report"]},{"url":"https://bugzilla.suse.com/1232870","tags":["report"]},{"url":"https://bugzilla.suse.com/1232873","tags":["report"]},{"url":"https://bugzilla.suse.com/1232877","tags":["report"]},{"url":"https://bugzilla.suse.com/1232878","tags":["report"]},{"url":"https://bugzilla.suse.com/1232881","tags":["report"]},{"url":"https://bugzilla.suse.com/1232884","tags":["report"]},{"url":"https://bugzilla.suse.com/1232885","tags":["report"]},{"url":"https://bugzilla.suse.com/1232887","tags":["report"]},{"url":"https://bugzilla.suse.com/1232888","tags":["report"]},{"url":"https://bugzilla.suse.com/1232890","tags":["report"]},{"url":"https://bugzilla.suse.com/1232892","tags":["report"]},{"url":"https://bugzilla.suse.com/1232896","tags":["report"]},{"url":"https://bugzilla.suse.com/1232897","tags":["report"]},{"url":"https://bugzilla.suse.com/1232905","tags":["report"]},{"url":"https://bugzilla.suse.com/1232907","tags":["report"]},{"url":"https://bugzilla.suse.com/1232919","tags":["report"]},{"url":"https://bugzilla.suse.com/1232926","tags":["report"]},{"url":"https://bugzilla.suse.com/1232928","tags":["report"]},{"url":"https://bugzilla.suse.com/1232935","tags":["report"]},{"url":"https://bugzilla.suse.com/1233035","tags":["report"]},{"url":"https://bugzilla.suse.com/1233049","tags":["report"]},{"url":"https://bugzilla.suse.com/1233051","tags":["report"]},{"url":"https://bugzilla.suse.com/1233056","tags":["report"]},{"url":"https://bugzilla.suse.com/1233057","tags":["report"]},{"url":"https://bugzilla.suse.com/1233061","tags":["report"]},{"url":"https://bugzilla.suse.com/1233063","tags":["report"]},{"url":"https://bugzilla.suse.com/1233065","tags":["report"]},{"url":"https://bugzilla.suse.com/1233067","tags":["report"]},{"url":"https://bugzilla.suse.com/1233070","tags":["report"]},{"url":"https://bugzilla.suse.com/1233073","tags":["report"]},{"url":"https://bugzilla.suse.com/1233074","tags":["report"]},{"url":"https://bugzilla.suse.com/1233100","tags":["report"]},{"url":"https://bugzilla.suse.com/1233103","tags":["report"]},{"url":"https://bugzilla.suse.com/1233104","tags":["report"]},{"url":"https://bugzilla.suse.com/1233105","tags":["report"]},{"url":"https://bugzilla.suse.com/1233106","tags":["report"]},{"url":"https://bugzilla.suse.com/1233107","tags":["report"]},{"url":"https://bugzilla.suse.com/1233108","tags":["report"]},{"url":"https://bugzilla.suse.com/1233110","tags":["report"]},{"url":"https://bugzilla.suse.com/1233111","tags":["report"]},{"url":"https://bugzilla.suse.com/1233113","tags":["report"]},{"url":"https://bugzilla.suse.com/1233114","tags":["report"]},{"url":"https://bugzilla.suse.com/1233117","tags":["report"]},{"url":"https://bugzilla.suse.com/1233123","tags":["report"]},{"url":"https://bugzilla.suse.com/1233125","tags":["report"]},{"url":"https://bugzilla.suse.com/1233129","tags":["report"]},{"url":"https://bugzilla.suse.com/1233130","tags":["report"]},{"url":"https://bugzilla.suse.com/1233134","tags":["report"]},{"url":"https://bugzilla.suse.com/1233135","tags":["report"]},{"url":"https://bugzilla.suse.com/1233150","tags":["report"]},{"url":"https://bugzilla.suse.com/1233189","tags":["report"]},{"url":"https://bugzilla.suse.com/1233191","tags":["report"]},{"url":"https://bugzilla.suse.com/1233197","tags":["report"]},{"url":"https://bugzilla.suse.com/1233205","tags":["report"]},{"url":"https://bugzilla.suse.com/1233206","tags":["report"]},{"url":"https://bugzilla.suse.com/1233209","tags":["report"]},{"url":"https://bugzilla.suse.com/1233210","tags":["report"]},{"url":"https://bugzilla.suse.com/1233211","tags":["report"]},{"url":"https://bugzilla.suse.com/1233212","tags":["report"]},{"url":"https://bugzilla.suse.com/1233214","tags":["report"]},{"url":"https://bugzilla.suse.com/1233216","tags":["report"]},{"url":"https://bugzilla.suse.com/1233238","tags":["report"]},{"url":"https://bugzilla.suse.com/1233241","tags":["report"]},{"url":"https://bugzilla.suse.com/1233253","tags":["report"]},{"url":"https://bugzilla.suse.com/1233255","tags":["report"]},{"url":"https://bugzilla.suse.com/1233293","tags":["report"]},{"url":"https://bugzilla.suse.com/1233350","tags":["report"]},{"url":"https://bugzilla.suse.com/1233452","tags":["report"]},{"url":"https://bugzilla.suse.com/1233453","tags":["report"]},{"url":"https://bugzilla.suse.com/1233454","tags":["report"]},{"url":"https://bugzilla.suse.com/1233456","tags":["report"]},{"url":"https://bugzilla.suse.com/1233457","tags":["report"]},{"url":"https://bugzilla.suse.com/1233458","tags":["report"]},{"url":"https://bugzilla.suse.com/1233460","tags":["report"]},{"url":"https://bugzilla.suse.com/1233462","tags":["report"]},{"url":"https://bugzilla.suse.com/1233463","tags":["report"]},{"url":"https://bugzilla.suse.com/1233468","tags":["report"]},{"url":"https://bugzilla.suse.com/1233471","tags":["report"]},{"url":"https://bugzilla.suse.com/1233476","tags":["report"]},{"url":"https://bugzilla.suse.com/1233478","tags":["report"]},{"url":"https://bugzilla.suse.com/1233479","tags":["report"]},{"url":"https://bugzilla.suse.com/1233481","tags":["report"]},{"url":"https://bugzilla.suse.com/1233484","tags":["report"]},{"url":"https://bugzilla.suse.com/1233487","tags":["report"]},{"url":"https://bugzilla.suse.com/1233490","tags":["report"]},{"url":"https://bugzilla.suse.com/1233491","tags":["report"]},{"url":"https://bugzilla.suse.com/1233528","tags":["report"]},{"url":"https://bugzilla.suse.com/1233548","tags":["report"]},{"url":"https://bugzilla.suse.com/1233552","tags":["report"]},{"url":"https://bugzilla.suse.com/1233553","tags":["report"]},{"url":"https://bugzilla.suse.com/1233554","tags":["report"]},{"url":"https://bugzilla.suse.com/1233555","tags":["report"]},{"url":"https://bugzilla.suse.com/1233557","tags":["report"]},{"url":"https://bugzilla.suse.com/1233560","tags":["report"]},{"url":"https://bugzilla.suse.com/1233561","tags":["report"]},{"url":"https://bugzilla.suse.com/1233570","tags":["report"]},{"url":"https://bugzilla.suse.com/1233577","tags":["report"]},{"url":"https://bugzilla.suse.com/1233580","tags":["report"]},{"url":"https://bugzilla.suse.com/1233977","tags":["report"]},{"url":"https://bugzilla.suse.com/1234012","tags":["report"]},{"url":"https://bugzilla.suse.com/1234025","tags":["report"]},{"url":"https://bugzilla.suse.com/1234085","tags":["report"]},{"url":"https://bugzilla.suse.com/1234093","tags":["report"]},{"url":"https://bugzilla.suse.com/1234098","tags":["report"]},{"url":"https://bugzilla.suse.com/1234108","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53110","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250034-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520073-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520077-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-40965","tags":["report"]},{"url":"https://git.kernel.org/linus/4268254a39484fc11ba991ae148bacbe75d9cc0a","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-6999-1","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-7008-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7005-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6999-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7029-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7288-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7289-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7291-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7288-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7289-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7293-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7294-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7295-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7289-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7305-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7289-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7308-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7294-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7294-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7294-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7331-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7388-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7389-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7390-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7393-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7401-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7413-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7458-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7539-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7540-1","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-40945","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-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-2024-42270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42154","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-42224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-0927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-21400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-52332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-38096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-47191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21971","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-40965","title":"i2c: lpi2c: Avoid calling clk_get_rate during transfer","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","status":"published","published":"2024-07-12T12:32:05.453Z","modified":"2026-05-11T20:23:16.328Z","updated_at":"2026-11-02T14:34:06.811965Z"}],"euvd":[{"id":"EUVD-2024-38762","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","status":"published","published":"2024-07-12T12:32:05Z","modified":"2026-05-11T20:23:16Z","updated_at":"2026-11-02T19:04:56.237997Z"}],"ghsa":[{"id":"GHSA-r49f-c964-6w6w","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","status":"published","published":"2024-07-12T15:31:28Z","modified":"2024-12-09T15:32:39Z","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-667"],"updated_at":"2026-11-02T14:59:05.809648Z"}],"nvd":[{"id":"CVE-2024-40965","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","status":"published","published":"2024-07-12T13:15:18.37Z","modified":"2026-06-17T07:46:58.64Z","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-667"],"updated_at":"2026-11-02T14:10:12.994089Z"}],"osv":[{"id":"AZL-48957","title":"CVE-2024-40965 affecting package kernel 5.15.200.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","status":"published","published":"2024-07-12T13:15:18Z","modified":"2026-04-21T04:29:42.571733Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:06.032783Z"},{"id":"AZL-48969","title":"CVE-2024-40965 affecting package kernel for versions less than 6.6.64.2-9","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","status":"published","published":"2024-07-12T13:15:18Z","modified":"2026-11-05T05:40:51Z","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-05T16:41:20.514083Z"},{"id":"BELL-CVE-2024-40965","status":"published","published":"2024-07-16T05:58:45.663646Z","modified":"2026-01-26T09:35:00.479349Z","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-40965","description":"In the Linux kernel, the following vulnerability has been resolved:  i2c: lpi2c: Avoid calling clk_get_rate during transfer  Instead of repeatedly calling clk_get_rate for each transfer, lock the clock rate and cache the value. A deadlock has been observed while adding tlv320aic32x4 audio codec to the system. When this clock provider adds its clock, the clk mutex is locked already, it needs to access i2c, which in return needs the mutex for clk_get_rate as well.","status":"published","published":"2024-07-12T13:15:18.37Z","modified":"2026-11-02T12:02:38.095642915Z","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-2025-1095","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix race condition between session lookup and expire\n\n Thread A                        +  Thread B\n ksmbd_session_lookup            |  smb2_sess_setup\n   sess = xa_load                |\n                                 |\n                                 |    xa_erase(\u0026amp;conn-\u0026gt;sessions, sess-\u0026gt;id);\n                                 |\n                                 |    ksmbd_session_destroy(sess) --\u0026gt; kfree(sess)\n                                 |\n   // UAF!                       |\n   sess-\u0026gt;last_active = jiffies   |\n                                 +\n\nThis patch add rwsem to fix race condition between ksmbd_session_lookup\nand ksmbd_expire_session.(CVE-2023-52480)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/siw: Fix connection failure handling\n\nIn case immediate MPA request processing fails, the newly\ncreated endpoint unlinks the listening endpoint and is\nready to be dropped. This special case was not handled\ncorrectly by the code handling the later TCP socket close,\ncausing a NULL dereference crash in siw_cm_work_handler()\nwhen dereferencing a NULL listener. We now also cancel\nthe useless MPA timeout, if immediate MPA request\nprocessing fails.\n\nThis patch furthermore simplifies MPA processing in general:\nScheduling a useless TCP socket read in sk_data_ready() upcall\nis now surpressed, if the socket is already moved out of\nTCP_ESTABLISHED state.(CVE-2023-52513)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Fix buffer overflow in trans_stat_show\n\nFix buffer overflow in trans_stat_show().\n\nConvert simple snprintf to the more secure scnprintf with size of\nPAGE_SIZE.\n\nAdd condition checking if we are exceeding PAGE_SIZE and exit early from\nloop. Also add at the end a warning that we exceeded PAGE_SIZE and that\nstats is disabled.\n\nReturn -EFBIG in the case where we don\u0026apos;t have enough space to write the\nfull transition table.\n\nAlso document in the ABI that this function can return -EFBIG error.(CVE-2023-52614)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: adc: ad7091r: Allow users to configure device events\n\nAD7091R-5 devices are supported by the ad7091r-5 driver together with\nthe ad7091r-base driver. Those drivers declared iio events for notifying\nuser space when ADC readings fall bellow the thresholds of low limit\nregisters or above the values set in high limit registers.\nHowever, to configure iio events and their thresholds, a set of callback\nfunctions must be implemented and those were not present until now.\nThe consequence of trying to configure ad7091r-5 events without the\nproper callback functions was a null pointer dereference in the kernel\nbecause the pointers to the callback functions were not set.\n\nImplement event configuration callbacks allowing users to read/write\nevent thresholds and enable/disable event generation.\n\nSince the event spec structs are generic to AD7091R devices, also move\nthose from the ad7091r-5 driver the base driver so they can be reused\nwhen support for ad7091r-2/-4/-8 be added.(CVE-2023-52627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915: Fix potential context UAFs\n\ngem_context_register() makes the context visible to userspace, and which\npoint a separate thread can trigger the I915_GEM_CONTEXT_DESTROY ioctl.\nSo we need to ensure that nothing uses the ctx ptr after this.  And we\nneed to ensure that adding the ctx to the xarray is the *last* thing\nthat gem_context_register() does with the ctx pointer.\n\n[tursulin: Stable and fixes tags add/tidy.]\n(cherry picked from commit bed4b455cf5374e68879be56971c1da563bcd90c)(CVE-2023-52913)\n\nA race condition was found in the Linux kernel\u0026apos;s net/bluetooth device driver in conn_info_{min,max}_age_set() function. This can result in integrity overflow issue, possibly leading to bluetooth connection abnormality or denial of service.\n\n\n\n\n(CVE-2024-24857)\n\nA race condition was found in the Linux kernel\u0026apos;s net/bluetooth in sniff_{min,max}_interval_set() function. This can result in a bluetooth sniffing exception issue, possibly leading denial of service.\n\n\n\n\n\n\n\n(CVE-2024-24859)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxhci: handle isoc Babble and Buffer Overrun events properly\n\nxHCI 4.9 explicitly forbids assuming that the xHC has released its\nownership of a multi-TRB TD when it reports an error on one of the\nearly TRBs. Yet the driver makes such assumption and releases the TD,\nallowing the remaining TRBs to be freed or overwritten by new TDs.\n\nThe xHC should also report completion of the final TRB due to its IOC\nflag being set by us, regardless of prior errors. This event cannot\nbe recognized if the TD has already been freed earlier, resulting in\n\u0026quot;Transfer event TRB DMA ptr not part of current TD\u0026quot; error message.\n\nFix this by reusing the logic for processing isoc Transaction Errors.\nThis also handles hosts which fail to report the final completion.\n\nFix transfer length reporting on Babble errors. They may be caused by\ndevice malfunction, no guarantee that the buffer has been filled.(CVE-2024-26659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (coretemp) Fix out-of-bounds memory access\n\nFix a bug that pdata-\u0026gt;cpu_map[] is set before out-of-bounds check.\nThe problem might be triggered on systems with more than 128 cores per\npackage.(CVE-2024-26664)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations\n\n- Disallow families other than NFPROTO_{IPV4,IPV6,INET}.\n- Disallow layer 4 protocol with no ports, since destination port is a\n  mandatory attribute for this object.(CVE-2024-26673)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: roles: fix NULL pointer issue when put module\u0026apos;s reference\n\nIn current design, usb role class driver will get usb_role_switch parent\u0026apos;s\nmodule reference after the user get usb_role_switch device and put the\nreference after the user put the usb_role_switch device. However, the\nparent device of usb_role_switch may be removed before the user put the\nusb_role_switch. If so, then, NULL pointer issue will be met when the user\nput the parent module\u0026apos;s reference.\n\nThis will save the module pointer in structure of usb_role_switch. Then,\nwe don\u0026apos;t need to find module by iterating long relations.(CVE-2024-26747)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix memory double free when handle zero packet\n\n829  if (request-\u0026gt;complete) {\n830          spin_unlock(\u0026amp;priv_dev-\u0026gt;lock);\n831          usb_gadget_giveback_request(\u0026amp;priv_ep-\u0026gt;endpoint,\n832                                    request);\n833          spin_lock(\u0026amp;priv_dev-\u0026gt;lock);\n834  }\n835\n836  if (request-\u0026gt;buf == priv_dev-\u0026gt;zlp_buf)\n837      cdns3_gadget_ep_free_request(\u0026amp;priv_ep-\u0026gt;endpoint, request);\n\nDriver append an additional zero packet request when queue a packet, which\nlength mod max packet size is 0. When transfer complete, run to line 831,\nusb_gadget_giveback_request() will free this requestion. 836 condition is\ntrue, so cdns3_gadget_ep_free_request() free this request again.\n\nLog:\n\n[ 1920.140696][  T150] BUG: KFENCE: use-after-free read in cdns3_gadget_giveback+0x134/0x2c0 [cdns3]\n[ 1920.140696][  T150]\n[ 1920.151837][  T150] Use-after-free read at 0x000000003d1cd10b (in kfence-#36):\n[ 1920.159082][  T150]  cdns3_gadget_giveback+0x134/0x2c0 [cdns3]\n[ 1920.164988][  T150]  cdns3_transfer_completed+0x438/0x5f8 [cdns3]\n\nAdd check at line 829, skip call usb_gadget_giveback_request() if it is\nadditional zero length packet request. Needn\u0026apos;t call\nusb_gadget_giveback_request() because it is allocated in this driver.(CVE-2024-26748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fixed memory use after free at cdns3_gadget_ep_disable()\n\n  ...\n  cdns3_gadget_ep_free_request(\u0026amp;priv_ep-\u0026gt;endpoint, \u0026amp;priv_req-\u0026gt;request);\n  list_del_init(\u0026amp;priv_req-\u0026gt;list);\n  ...\n\n\u0026apos;priv_req\u0026apos; actually free at cdns3_gadget_ep_free_request(). But\nlist_del_init() use priv_req-\u0026gt;list after it.\n\n[ 1542.642868][  T534] BUG: KFENCE: use-after-free read in __list_del_entry_valid+0x10/0xd4\n[ 1542.642868][  T534]\n[ 1542.653162][  T534] Use-after-free read at 0x000000009ed0ba99 (in kfence-#3):\n[ 1542.660311][  T534]  __list_del_entry_valid+0x10/0xd4\n[ 1542.665375][  T534]  cdns3_gadget_ep_disable+0x1f8/0x388 [cdns3]\n[ 1542.671571][  T534]  usb_ep_disable+0x44/0xe4\n[ 1542.675948][  T534]  ffs_func_eps_disable+0x64/0xc8\n[ 1542.680839][  T534]  ffs_func_set_alt+0x74/0x368\n[ 1542.685478][  T534]  ffs_func_disable+0x18/0x28\n\nMove list_del_init() before cdns3_gadget_ep_free_request() to resolve this\nproblem.(CVE-2024-26749)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: virtio/akcipher - Fix stack overflow on memcpy\n\nsizeof(struct virtio_crypto_akcipher_session_para) is less than\nsizeof(struct virtio_crypto_op_ctrl_req::u), copying more bytes from\nstack variable leads stack overflow. Clang reports this issue by\ncommands:\nmake -j CC=clang-14 mrproper \u0026gt;/dev/null 2\u0026gt;\u0026amp;1\nmake -j O=/tmp/crypto-build CC=clang-14 allmodconfig \u0026gt;/dev/null 2\u0026gt;\u0026amp;1\nmake -j O=/tmp/crypto-build W=1 CC=clang-14 drivers/crypto/virtio/\n  virtio_crypto_akcipher_algs.o(CVE-2024-26753)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix possible deadlock in subflow diag\n\nSyzbot and Eric reported a lockdep splat in the subflow diag:\n\n   WARNING: possible circular locking dependency detected\n   6.8.0-rc4-syzkaller-00212-g40b9385dd8e6 #0 Not tainted\n\n   syz-executor.2/24141 is trying to acquire lock:\n   ffff888045870130 (k-sk_lock-AF_INET6){+.+.}-{0:0}, at:\n   tcp_diag_put_ulp net/ipv4/tcp_diag.c:100 [inline]\n   ffff888045870130 (k-sk_lock-AF_INET6){+.+.}-{0:0}, at:\n   tcp_diag_get_aux+0x738/0x830 net/ipv4/tcp_diag.c:137\n\n   but task is already holding lock:\n   ffffc9000135e488 (\u0026amp;h-\u0026gt;lhash2[i].lock){+.+.}-{2:2}, at: spin_lock\n   include/linux/spinlock.h:351 [inline]\n   ffffc9000135e488 (\u0026amp;h-\u0026gt;lhash2[i].lock){+.+.}-{2:2}, at:\n   inet_diag_dump_icsk+0x39f/0x1f80 net/ipv4/inet_diag.c:1038\n\n   which lock already depends on the new lock.\n\n   the existing dependency chain (in reverse order) is:\n\n   -\u0026gt; #1 (\u0026amp;h-\u0026gt;lhash2[i].lock){+.+.}-{2:2}:\n   lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754\n   __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]\n   _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154\n   spin_lock include/linux/spinlock.h:351 [inline]\n   __inet_hash+0x335/0xbe0 net/ipv4/inet_hashtables.c:743\n   inet_csk_listen_start+0x23a/0x320 net/ipv4/inet_connection_sock.c:1261\n   __inet_listen_sk+0x2a2/0x770 net/ipv4/af_inet.c:217\n   inet_listen+0xa3/0x110 net/ipv4/af_inet.c:239\n   rds_tcp_listen_init+0x3fd/0x5a0 net/rds/tcp_listen.c:316\n   rds_tcp_init_net+0x141/0x320 net/rds/tcp.c:577\n   ops_init+0x352/0x610 net/core/net_namespace.c:136\n   __register_pernet_operations net/core/net_namespace.c:1214 [inline]\n   register_pernet_operations+0x2cb/0x660 net/core/net_namespace.c:1283\n   register_pernet_device+0x33/0x80 net/core/net_namespace.c:1370\n   rds_tcp_init+0x62/0xd0 net/rds/tcp.c:735\n   do_one_initcall+0x238/0x830 init/main.c:1236\n   do_initcall_level+0x157/0x210 init/main.c:1298\n   do_initcalls+0x3f/0x80 init/main.c:1314\n   kernel_init_freeable+0x42f/0x5d0 init/main.c:1551\n   kernel_init+0x1d/0x2a0 init/main.c:1441\n   ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147\n   ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242\n\n   -\u0026gt; #0 (k-sk_lock-AF_INET6){+.+.}-{0:0}:\n   check_prev_add kernel/locking/lockdep.c:3134 [inline]\n   check_prevs_add kernel/locking/lockdep.c:3253 [inline]\n   validate_chain+0x18ca/0x58e0 kernel/locking/lockdep.c:3869\n   __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137\n   lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754\n   lock_sock_fast include/net/sock.h:1723 [inline]\n   subflow_get_info+0x166/0xd20 net/mptcp/diag.c:28\n   tcp_diag_put_ulp net/ipv4/tcp_diag.c:100 [inline]\n   tcp_diag_get_aux+0x738/0x830 net/ipv4/tcp_diag.c:137\n   inet_sk_diag_fill+0x10ed/0x1e00 net/ipv4/inet_diag.c:345\n   inet_diag_dump_icsk+0x55b/0x1f80 net/ipv4/inet_diag.c:1061\n   __inet_diag_dump+0x211/0x3a0 net/ipv4/inet_diag.c:1263\n   inet_diag_dump_compat+0x1c1/0x2d0 net/ipv4/inet_diag.c:1371\n   netlink_dump+0x59b/0xc80 net/netlink/af_netlink.c:2264\n   __netlink_dump_start+0x5df/0x790 net/netlink/af_netlink.c:2370\n   netlink_dump_start include/linux/netlink.h:338 [inline]\n   inet_diag_rcv_msg_compat+0x209/0x4c0 net/ipv4/inet_diag.c:1405\n   sock_diag_rcv_msg+0xe7/0x410\n   netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2543\n   sock_diag_rcv+0x2a/0x40 net/core/sock_diag.c:280\n   netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]\n   netlink_unicast+0x7ea/0x980 net/netlink/af_netlink.c:1367\n   netlink_sendmsg+0xa3b/0xd70 net/netlink/af_netlink.c:1908\n   sock_sendmsg_nosec net/socket.c:730 [inline]\n   __sock_sendmsg+0x221/0x270 net/socket.c:745\n   ____sys_sendmsg+0x525/0x7d0 net/socket.c:2584\n   ___sys_sendmsg net/socket.c:2638 [inline]\n   __sys_sendmsg+0x2b0/0x3a0 net/socket.c:2667\n   do_syscall_64+0xf9/0x240\n   entry_SYSCALL_64_after_hwframe+0x6f/0x77\n\nAs noted by Eric we can break the lock dependency chain avoid\ndumping \n---truncated---(CVE-2024-26781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read\n\nThere is chip (ls1028a) errata:\n\nThe SoC may hang on 16 byte unaligned read transactions by QDMA.\n\nUnaligned read transactions initiated by QDMA may stall in the NOC\n(Network On-Chip), causing a deadlock condition. Stalled transactions will\ntrigger completion timeouts in PCIe controller.\n\nWorkaround:\nEnable prefetch by setting the source descriptor prefetchable bit\n( SD[PF] = 1 ).\n\nImplement this workaround.(CVE-2024-26790)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngtp: fix use-after-free and null-ptr-deref in gtp_newlink()\n\nThe gtp_link_ops operations structure for the subsystem must be\nregistered after registering the gtp_net_ops pernet operations structure.\n\nSyzkaller hit \u0026apos;general protection fault in gtp_genl_dump_pdp\u0026apos; bug:\n\n[ 1010.702740] gtp: GTP module unloaded\n[ 1010.715877] general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI\n[ 1010.715888] KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]\n[ 1010.715895] CPU: 1 PID: 128616 Comm: a.out Not tainted 6.8.0-rc6-std-def-alt1 #1\n[ 1010.715899] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-alt1 04/01/2014\n[ 1010.715908] RIP: 0010:gtp_newlink+0x4d7/0x9c0 [gtp]\n[ 1010.715915] Code: 80 3c 02 00 0f 85 41 04 00 00 48 8b bb d8 05 00 00 e8 ed f6 ff ff 48 89 c2 48 89 c5 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02 00 0f 85 4f 04 00 00 4c 89 e2 4c 8b 6d 00 48 b8 00 00 00\n[ 1010.715920] RSP: 0018:ffff888020fbf180 EFLAGS: 00010203\n[ 1010.715929] RAX: dffffc0000000000 RBX: ffff88800399c000 RCX: 0000000000000000\n[ 1010.715933] RDX: 0000000000000001 RSI: ffffffff84805280 RDI: 0000000000000282\n[ 1010.715938] RBP: 000000000000000d R08: 0000000000000001 R09: 0000000000000000\n[ 1010.715942] R10: 0000000000000001 R11: 0000000000000001 R12: ffff88800399cc80\n[ 1010.715947] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000400\n[ 1010.715953] FS:  00007fd1509ab5c0(0000) GS:ffff88805b300000(0000) knlGS:0000000000000000\n[ 1010.715958] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1010.715962] CR2: 0000000000000000 CR3: 000000001c07a000 CR4: 0000000000750ee0\n[ 1010.715968] PKRU: 55555554\n[ 1010.715972] Call Trace:\n[ 1010.715985]  ? __die_body.cold+0x1a/0x1f\n[ 1010.715995]  ? die_addr+0x43/0x70\n[ 1010.716002]  ? exc_general_protection+0x199/0x2f0\n[ 1010.716016]  ? asm_exc_general_protection+0x1e/0x30\n[ 1010.716026]  ? gtp_newlink+0x4d7/0x9c0 [gtp]\n[ 1010.716034]  ? gtp_net_exit+0x150/0x150 [gtp]\n[ 1010.716042]  __rtnl_newlink+0x1063/0x1700\n[ 1010.716051]  ? rtnl_setlink+0x3c0/0x3c0\n[ 1010.716063]  ? is_bpf_text_address+0xc0/0x1f0\n[ 1010.716070]  ? kernel_text_address.part.0+0xbb/0xd0\n[ 1010.716076]  ? __kernel_text_address+0x56/0xa0\n[ 1010.716084]  ? unwind_get_return_address+0x5a/0xa0\n[ 1010.716091]  ? create_prof_cpu_mask+0x30/0x30\n[ 1010.716098]  ? arch_stack_walk+0x9e/0xf0\n[ 1010.716106]  ? stack_trace_save+0x91/0xd0\n[ 1010.716113]  ? stack_trace_consume_entry+0x170/0x170\n[ 1010.716121]  ? __lock_acquire+0x15c5/0x5380\n[ 1010.716139]  ? mark_held_locks+0x9e/0xe0\n[ 1010.716148]  ? kmem_cache_alloc_trace+0x35f/0x3c0\n[ 1010.716155]  ? __rtnl_newlink+0x1700/0x1700\n[ 1010.716160]  rtnl_newlink+0x69/0xa0\n[ 1010.716166]  rtnetlink_rcv_msg+0x43b/0xc50\n[ 1010.716172]  ? rtnl_fdb_dump+0x9f0/0x9f0\n[ 1010.716179]  ? lock_acquire+0x1fe/0x560\n[ 1010.716188]  ? netlink_deliver_tap+0x12f/0xd50\n[ 1010.716196]  netlink_rcv_skb+0x14d/0x440\n[ 1010.716202]  ? rtnl_fdb_dump+0x9f0/0x9f0\n[ 1010.716208]  ? netlink_ack+0xab0/0xab0\n[ 1010.716213]  ? netlink_deliver_tap+0x202/0xd50\n[ 1010.716220]  ? netlink_deliver_tap+0x218/0xd50\n[ 1010.716226]  ? __virt_addr_valid+0x30b/0x590\n[ 1010.716233]  netlink_unicast+0x54b/0x800\n[ 1010.716240]  ? netlink_attachskb+0x870/0x870\n[ 1010.716248]  ? __check_object_size+0x2de/0x3b0\n[ 1010.716254]  netlink_sendmsg+0x938/0xe40\n[ 1010.716261]  ? netlink_unicast+0x800/0x800\n[ 1010.716269]  ? __import_iovec+0x292/0x510\n[ 1010.716276]  ? netlink_unicast+0x800/0x800\n[ 1010.716284]  __sock_sendmsg+0x159/0x190\n[ 1010.716290]  ____sys_sendmsg+0x712/0x880\n[ 1010.716297]  ? sock_write_iter+0x3d0/0x3d0\n[ 1010.716304]  ? __ia32_sys_recvmmsg+0x270/0x270\n[ 1010.716309]  ? lock_acquire+0x1fe/0x560\n[ 1010.716315]  ? drain_array_locked+0x90/0x90\n[ 1010.716324]  ___sys_sendmsg+0xf8/0x170\n[ 1010.716331]  ? sendmsg_copy_msghdr+0x170/0x170\n[ 1010.716337]  ? lockdep_init_map\n---truncated---(CVE-2024-26793)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix potencial out-of-bounds when buffer offset is invalid\n\nI found potencial out-of-bounds when buffer offset fields of a few requests\nis invalid. This patch set the minimum value of buffer offset field to\n-\u0026gt;Buffer offset to validate buffer length.(CVE-2024-26952)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: Get runtime PM before walking tree during disable_unused\n\nDoug reported [1] the following hung task:\n\n INFO: task swapper/0:1 blocked for more than 122 seconds.\n       Not tainted 5.15.149-21875-gf795ebc40eb8 #1\n \u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\n task:swapper/0       state:D stack:    0 pid:    1 ppid:     0 flags:0x00000008\n Call trace:\n  __switch_to+0xf4/0x1f4\n  __schedule+0x418/0xb80\n  schedule+0x5c/0x10c\n  rpm_resume+0xe0/0x52c\n  rpm_resume+0x178/0x52c\n  __pm_runtime_resume+0x58/0x98\n  clk_pm_runtime_get+0x30/0xb0\n  clk_disable_unused_subtree+0x58/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused+0x4c/0xe4\n  do_one_initcall+0xcc/0x2d8\n  do_initcall_level+0xa4/0x148\n  do_initcalls+0x5c/0x9c\n  do_basic_setup+0x24/0x30\n  kernel_init_freeable+0xec/0x164\n  kernel_init+0x28/0x120\n  ret_from_fork+0x10/0x20\n INFO: task kworker/u16:0:9 blocked for more than 122 seconds.\n       Not tainted 5.15.149-21875-gf795ebc40eb8 #1\n \u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\n task:kworker/u16:0   state:D stack:    0 pid:    9 ppid:     2 flags:0x00000008\n Workqueue: events_unbound deferred_probe_work_func\n Call trace:\n  __switch_to+0xf4/0x1f4\n  __schedule+0x418/0xb80\n  schedule+0x5c/0x10c\n  schedule_preempt_disabled+0x2c/0x48\n  __mutex_lock+0x238/0x488\n  __mutex_lock_slowpath+0x1c/0x28\n  mutex_lock+0x50/0x74\n  clk_prepare_lock+0x7c/0x9c\n  clk_core_prepare_lock+0x20/0x44\n  clk_prepare+0x24/0x30\n  clk_bulk_prepare+0x40/0xb0\n  mdss_runtime_resume+0x54/0x1c8\n  pm_generic_runtime_resume+0x30/0x44\n  __genpd_runtime_resume+0x68/0x7c\n  genpd_runtime_resume+0x108/0x1f4\n  __rpm_callback+0x84/0x144\n  rpm_callback+0x30/0x88\n  rpm_resume+0x1f4/0x52c\n  rpm_resume+0x178/0x52c\n  __pm_runtime_resume+0x58/0x98\n  __device_attach+0xe0/0x170\n  device_initial_probe+0x1c/0x28\n  bus_probe_device+0x3c/0x9c\n  device_add+0x644/0x814\n  mipi_dsi_device_register_full+0xe4/0x170\n  devm_mipi_dsi_device_register_full+0x28/0x70\n  ti_sn_bridge_probe+0x1dc/0x2c0\n  auxiliary_bus_probe+0x4c/0x94\n  really_probe+0xcc/0x2c8\n  __driver_probe_device+0xa8/0x130\n  driver_probe_device+0x48/0x110\n  __device_attach_driver+0xa4/0xcc\n  bus_for_each_drv+0x8c/0xd8\n  __device_attach+0xf8/0x170\n  device_initial_probe+0x1c/0x28\n  bus_probe_device+0x3c/0x9c\n  deferred_probe_work_func+0x9c/0xd8\n  process_one_work+0x148/0x518\n  worker_thread+0x138/0x350\n  kthread+0x138/0x1e0\n  ret_from_fork+0x10/0x20\n\nThe first thread is walking the clk tree and calling\nclk_pm_runtime_get() to power on devices required to read the clk\nhardware via struct clk_ops::is_enabled(). This thread holds the clk\nprepare_lock, and is trying to runtime PM resume a device, when it finds\nthat the device is in the process of resuming so the thread schedule()s\naway waiting for the device to finish resuming before continuing. The\nsecond thread is runtime PM resuming the same device, but the runtime\nresume callback is calling clk_prepare(), trying to grab the\nprepare_lock waiting on the first thread.\n\nThis is a classic ABBA deadlock. To properly fix the deadlock, we must\nnever runtime PM resume or suspend a device with the clk prepare_lock\nheld. Actually doing that is near impossible today because the global\nprepare_lock would have to be dropped in the middle of the tree, the\ndevice runtime PM resumed/suspended, and then the prepare_lock grabbed\nagain to ensure consistency of the clk tree topology. If anything\nchanges with the clk tree in the meantime, we\u0026apos;ve lost and will need to\nstart the operation all over again.\n\nLuckily, most of the time we\u0026apos;re simply incrementing or decrementing the\nruntime PM count on an active device, so we don\u0026apos;t have the chance to\nschedule away with the prepare_lock held. Let\u0026apos;s fix this immediate\nproblem that can be\n---truncated---(CVE-2024-27004)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfpga: bridge: add owner module and take its refcount\n\nThe current implementation of the fpga bridge assumes that the low-level\nmodule registers a driver for the parent device and uses its owner pointer\nto take the module\u0026apos;s refcount. This approach is problematic since it can\nlead to a null pointer dereference while attempting to get the bridge if\nthe parent device does not have a driver.\n\nTo address this problem, add a module owner pointer to the fpga_bridge\nstruct and use it to take the module\u0026apos;s refcount. Modify the function for\nregistering a bridge to take an additional owner module parameter and\nrename it to avoid conflicts. Use the old function name for a helper macro\nthat automatically sets the module that registers the bridge as the owner.\nThis ensures compatibility with existing low-level control modules and\nreduces the chances of registering a bridge without setting the owner.\n\nAlso, update the documentation to keep it consistent with the new interface\nfor registering an fpga bridge.\n\nOther changes: opportunistically move put_device() from __fpga_bridge_get()\nto fpga_bridge_get() and of_fpga_bridge_get() to improve code clarity since\nthe bridge device is taken in these functions.(CVE-2024-36479)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: relax socket state check at accept time.\n\nChristoph reported the following splat:\n\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;\n\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.\n\nEric noted we can relax the existing assertion in __inet_accept()(CVE-2024-36484)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfpga: manager: add owner module and take its refcount\n\nThe current implementation of the fpga manager assumes that the low-level\nmodule registers a driver for the parent device and uses its owner pointer\nto take the module\u0026apos;s refcount. This approach is problematic since it can\nlead to a null pointer dereference while attempting to get the manager if\nthe parent device does not have a driver.\n\nTo address this problem, add a module owner pointer to the fpga_manager\nstruct and use it to take the module\u0026apos;s refcount. Modify the functions for\nregistering the manager to take an additional owner module parameter and\nrename them to avoid conflicts. Use the old function names for helper\nmacros that automatically set the module that registers the manager as the\nowner. This ensures compatibility with existing low-level control modules\nand reduces the chances of registering a manager without setting the owner.\n\nAlso, update the documentation to keep it consistent with the new interface\nfor registering an fpga manager.\n\nOther changes: opportunistically move put_device() from __fpga_mgr_get() to\nfpga_mgr_get() and of_fpga_mgr_get() to improve code clarity since the\nmanager device is taken in these functions.(CVE-2024-37021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.(CVE-2024-40965)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64: probes: Fix uprobes for big-endian kernels\n\nThe arm64 uprobes code is broken for big-endian kernels as it doesn\u0026apos;t\nconvert the in-memory instruction encoding (which is always\nlittle-endian) into the kernel\u0026apos;s native endianness before analyzing and\nsimulating instructions. This may result in a few distinct problems:\n\n* The kernel may may erroneously reject probing an instruction which can\n  safely be probed.\n\n* The kernel may erroneously erroneously permit stepping an\n  instruction out-of-line when that instruction cannot be stepped\n  out-of-line safely.\n\n* The kernel may erroneously simulate instruction incorrectly dur to\n  interpretting the byte-swapped encoding.\n\nThe endianness mismatch isn\u0026apos;t caught by the compiler or sparse because:\n\n* The arch_uprobe::{insn,ixol} fields are encoded as arrays of u8, so\n  the compiler and sparse have no idea these contain a little-endian\n  32-bit value. The core uprobes code populates these with a memcpy()\n  which similarly does not handle endianness.\n\n* While the uprobe_opcode_t type is an alias for __le32, both\n  arch_uprobe_analyze_insn() and arch_uprobe_skip_sstep() cast from u8[]\n  to the similarly-named probe_opcode_t, which is an alias for u32.\n  Hence there is no endianness conversion warning.\n\nFix this by changing the arch_uprobe::{insn,ixol} fields to __le32 and\nadding the appropriate __le32_to_cpu() conversions prior to consuming\nthe instruction encoding. The core uprobes copies these fields as opaque\nranges of bytes, and so is unaffected by this change.\n\nAt the same time, remove MAX_UINSN_BYTES and consistently use\nAARCH64_INSN_SIZE for clarity.\n\nTested with the following:\n\n| #include \u0026lt;stdio.h\u0026gt;\n| #include \u0026lt;stdbool.h\u0026gt;\n|\n| #define noinline __attribute__((noinline))\n|\n| static noinline void *adrp_self(void)\n| {\n|         void *addr;\n|\n|         asm volatile(\n|         \u0026quot;       adrp    %x0, adrp_self\\n\u0026quot;\n|         \u0026quot;       add     %x0, %x0, :lo12:adrp_self\\n\u0026quot;\n|         : \u0026quot;=r\u0026quot; (addr));\n| }\n|\n|\n| int main(int argc, char *argv)\n| {\n|         void *ptr = adrp_self();\n|         bool equal = (ptr == adrp_self);\n|\n|         printf(\u0026quot;adrp_self   =\u0026gt; %p\\n\u0026quot;\n|                \u0026quot;adrp_self() =\u0026gt; %p\\n\u0026quot;\n|                \u0026quot;%s\\n\u0026quot;,\n|                adrp_self, ptr, equal ? \u0026quot;EQUAL\u0026quot; : \u0026quot;NOT EQUAL\u0026quot;);\n|\n|         return 0;\n| }\n\n.... where the adrp_self() function was compiled to:\n\n| 00000000004007e0 \u0026lt;adrp_self\u0026gt;:\n|   4007e0:       90000000        adrp    x0, 400000 \u0026lt;__ehdr_start\u0026gt;\n|   4007e4:       911f8000        add     x0, x0, #0x7e0\n|   4007e8:       d65f03c0        ret\n\nBefore this patch, the ADRP is not recognized, and is assumed to be\nsteppable, resulting in corruption of the result:\n\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0x4007e0\n| EQUAL\n| # echo \u0026apos;p /root/adrp-self:0x007e0\u0026apos; \u0026gt; /sys/kernel/tracing/uprobe_events\n| # echo 1 \u0026gt; /sys/kernel/tracing/events/uprobes/enable\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0xffffffffff7e0\n| NOT EQUAL\n\nAfter this patch, the ADRP is correctly recognized and simulated:\n\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0x4007e0\n| EQUAL\n| #\n| # echo \u0026apos;p /root/adrp-self:0x007e0\u0026apos; \u0026gt; /sys/kernel/tracing/uprobe_events\n| # echo 1 \u0026gt; /sys/kernel/tracing/events/uprobes/enable\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0x4007e0\n| EQUAL(CVE-2024-50194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm cache: fix flushing uninitialized delayed_work on cache_ctr error\n\nAn unexpected WARN_ON from flush_work() may occur when cache creation\nfails, caused by destroying the uninitialized delayed_work waker in the\nerror path of cache_create(). For example, the warning appears on the\nsuperblock checksum error.\n\nReproduce steps:\n\ndmsetup create cmeta --table \u0026quot;0 8192 linear /dev/sdc 0\u0026quot;\ndmsetup create cdata --table \u0026quot;0 65536 linear /dev/sdc 8192\u0026quot;\ndmsetup create corig --table \u0026quot;0 524288 linear /dev/sdc 262144\u0026quot;\ndd if=/dev/urandom of=/dev/mapper/cmeta bs=4k count=1 oflag=direct\ndmsetup create cache --table \u0026quot;0 524288 cache /dev/mapper/cmeta \\\n/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\u0026quot;\n\nKernel logs:\n\n(snip)\nWARNING: CPU: 0 PID: 84 at kernel/workqueue.c:4178 __flush_work+0x5d4/0x890\n\nFix by pulling out the cancel_delayed_work_sync() from the constructor\u0026apos;s\nerror path. This patch doesn\u0026apos;t affect the use-after-free fix for\nconcurrent dm_resume and dm_destroy (commit 6a459d8edbdb (\u0026quot;dm cache: Fix\nUAF in destroy()\u0026quot;)) as cache_dtr is not changed.(CVE-2024-50280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix null-ptr-deref in block_touch_buffer tracepoint\n\nPatch series \u0026quot;nilfs2: fix null-ptr-deref bugs on block tracepoints\u0026quot;.\n\nThis series fixes null pointer dereference bugs that occur when using\nnilfs2 and two block-related tracepoints.\n\n\nThis patch (of 2):\n\nIt has been reported that when using \u0026quot;block:block_touch_buffer\u0026quot;\ntracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a\nNULL pointer dereference, or a general protection fault when KASAN is\nenabled.\n\nThis happens because since the tracepoint was added in touch_buffer(), it\nreferences the dev_t member bh-\u0026gt;b_bdev-\u0026gt;bd_dev regardless of whether the\nbuffer head has a pointer to a block_device structure.  In the current\nimplementation, the block_device structure is set after the function\nreturns to the caller.\n\nHere, touch_buffer() is used to mark the folio/page that owns the buffer\nhead as accessed, but the common search helper for folio/page used by the\ncaller function was optimized to mark the folio/page as accessed when it\nwas reimplemented a long time ago, eliminating the need to call\ntouch_buffer() here in the first place.\n\nSo this solves the issue by eliminating the touch_buffer() call itself.(CVE-2024-53131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: net: Do not use drvdata in release\n\nThe drvdata is not available in release. Let\u0026apos;s just use container_of()\nto get the uml_net instance. Otherwise, removing a network device will\nresult in a crash:\n\nRIP: 0033:net_device_release+0x10/0x6f\nRSP: 00000000e20c7c40  EFLAGS: 00010206\nRAX: 000000006002e4e7 RBX: 00000000600f1baf RCX: 00000000624074e0\nRDX: 0000000062778000 RSI: 0000000060551c80 RDI: 00000000627af028\nRBP: 00000000e20c7c50 R08: 00000000603ad594 R09: 00000000e20c7b70\nR10: 000000000000135a R11: 00000000603ad422 R12: 0000000000000000\nR13: 0000000062c7af00 R14: 0000000062406d60 R15: 00000000627700b6\nKernel panic - not syncing: Segfault with no mm\nCPU: 0 UID: 0 PID: 29 Comm: kworker/0:2 Not tainted 6.12.0-rc6-g59b723cd2adb #1\nWorkqueue: events mc_work_proc\nStack:\n 627af028 62c7af00 e20c7c80 60276fcd\n 62778000 603f5820 627af028 00000000\n e20c7cb0 603a2bcd 627af000 62770010\nCall Trace:\n [\u0026lt;60276fcd\u0026gt;] device_release+0x70/0xba\n [\u0026lt;603a2bcd\u0026gt;] kobject_put+0xba/0xe7\n [\u0026lt;60277265\u0026gt;] put_device+0x19/0x1c\n [\u0026lt;60281266\u0026gt;] platform_device_put+0x26/0x29\n [\u0026lt;60281e5f\u0026gt;] platform_device_unregister+0x2c/0x2e\n [\u0026lt;6002ec9c\u0026gt;] net_remove+0x63/0x69\n [\u0026lt;60031316\u0026gt;] ? mconsole_reply+0x0/0x50\n [\u0026lt;600310c8\u0026gt;] mconsole_remove+0x160/0x1cc\n [\u0026lt;60087d40\u0026gt;] ? __remove_hrtimer+0x38/0x74\n [\u0026lt;60087ff8\u0026gt;] ? hrtimer_try_to_cancel+0x8c/0x98\n [\u0026lt;6006b3cf\u0026gt;] ? dl_server_stop+0x3f/0x48\n [\u0026lt;6006b390\u0026gt;] ? dl_server_stop+0x0/0x48\n [\u0026lt;600672e8\u0026gt;] ? dequeue_entities+0x327/0x390\n [\u0026lt;60038fa6\u0026gt;] ? um_set_signals+0x0/0x43\n [\u0026lt;6003070c\u0026gt;] mc_work_proc+0x77/0x91\n [\u0026lt;60057664\u0026gt;] process_scheduled_works+0x1b3/0x2dd\n [\u0026lt;60055f32\u0026gt;] ? assign_work+0x0/0x58\n [\u0026lt;60057f0a\u0026gt;] worker_thread+0x1e9/0x293\n [\u0026lt;6005406f\u0026gt;] ? set_pf_worker+0x0/0x64\n [\u0026lt;6005d65d\u0026gt;] ? arch_local_irq_save+0x0/0x2d\n [\u0026lt;6005d748\u0026gt;] ? kthread_exit+0x0/0x3a\n [\u0026lt;60057d21\u0026gt;] ? worker_thread+0x0/0x293\n [\u0026lt;6005dbf1\u0026gt;] kthread+0x126/0x12b\n [\u0026lt;600219c5\u0026gt;] new_thread_handler+0x85/0xb6(CVE-2024-53183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen: Fix the issue of resource not being properly released in xenbus_dev_probe()\n\nThis patch fixes an issue in the function xenbus_dev_probe(). In the\nxenbus_dev_probe() function, within the if (err) branch at line 313, the\nprogram incorrectly returns err directly without releasing the resources\nallocated by err = drv-\u0026gt;probe(dev, id). As the return value is non-zero,\nthe upper layers assume the processing logic has failed. However, the probe\noperation was performed earlier without a corresponding remove operation.\nSince the probe actually allocates resources, failing to perform the remove\noperation could lead to problems.\n\nTo fix this issue, we followed the resource release logic of the\nxenbus_dev_remove() function by adding a new block fail_remove before the\nfail_put block. After entering the branch if (err) at line 313, the\nfunction will use a goto statement to jump to the fail_remove block,\nensuring that the previously acquired resources are correctly released,\nthus preventing the reference count leak.\n\nThis bug was identified by an experimental static analysis tool developed\nby our team. The tool specializes in analyzing reference count operations\nand detecting potential issues where resources are not properly managed.\nIn this case, the tool flagged the missing release operation as a\npotential problem, which led to the development of this patch.(CVE-2024-53198)\n\nIn the Linux kernel, the following vulnerability has been resolved:drm/amd/display: Fix null check for pipe_ctx-\u0026gt;plane_state in dcn20_program_pipeThis commit addresses a null pointer dereference issue indcn20_program_pipe(). Previously, commit 8e4ed3cf1642 ( drm/amd/display:Add null check for pipe_ctx-\u0026gt;plane_state in dcn20_program_pipe )partially fixed the null pointer dereference issue. However, indcn20_update_dchubp_dpp(), the variable pipe_ctx is passed in, andplane_state is accessed again through pipe_ctx. Multiple if statementsdirectly call attributes of plane_state, leading to potential nullpointer dereference issues. This patch adds necessary null checks toensure stability.(CVE-2024-53201)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan()\n\nReplace one-element array with a flexible-array member in `struct\nmwifiex_ie_types_wildcard_ssid_params` to fix the following warning\non a MT8173 Chromebook (mt8173-elm-hana):\n\n[  356.775250] ------------[ cut here ]------------\n[  356.784543] memcpy: detected field-spanning write (size 6) of single field \u0026quot;wildcard_ssid_tlv-\u0026gt;ssid\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:904 (size 1)\n[  356.813403] WARNING: CPU: 3 PID: 742 at drivers/net/wireless/marvell/mwifiex/scan.c:904 mwifiex_scan_networks+0x4fc/0xf28 [mwifiex]\n\nThe \u0026quot;(size 6)\u0026quot; above is exactly the length of the SSID of the network\nthis device was connected to. The source of the warning looks like:\n\n    ssid_len = user_scan_in-\u0026gt;ssid_list[i].ssid_len;\n    [...]\n    memcpy(wildcard_ssid_tlv-\u0026gt;ssid,\n           user_scan_in-\u0026gt;ssid_list[i].ssid, ssid_len);\n\nThere is a #define WILDCARD_SSID_TLV_MAX_SIZE that uses sizeof() on this\nstruct, but it already didn\u0026apos;t account for the size of the one-element\narray, so it doesn\u0026apos;t need to be changed.(CVE-2024-56539)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: uvcvideo: Require entities to have a non-zero unique ID\n\nPer UVC 1.1+ specification 3.7.2, units and terminals must have a non-zero\nunique ID.\n\n```\nEach Unit and Terminal within the video function is assigned a unique\nidentification number, the Unit ID (UID) or Terminal ID (TID), contained in\nthe bUnitID or bTerminalID field of the descriptor. The value 0x00 is\nreserved for undefined ID,\n```\n\nSo, deny allocating an entity with ID 0 or an ID that belongs to a unit\nthat is already added to the list of entities.\n\nThis also prevents some syzkaller reproducers from triggering warnings due\nto a chain of entities referring to themselves. In one particular case, an\nOutput Unit is connected to an Input Unit, both with the same ID of 1. But\nwhen looking up for the source ID of the Output Unit, that same entity is\nfound instead of the input entity, which leads to such warnings.\n\nIn another case, a backward chain was considered finished as the source ID\nwas 0. Later on, that entity was found, but its pads were not valid.\n\nHere is a sample stack trace for one of those cases.\n\n[   20.650953] usb 1-1: new high-speed USB device number 2 using dummy_hcd\n[   20.830206] usb 1-1: Using ep0 maxpacket: 8\n[   20.833501] usb 1-1: config 0 descriptor??\n[   21.038518] usb 1-1: string descriptor 0 read error: -71\n[   21.038893] usb 1-1: Found UVC 0.00 device \u0026lt;unnamed\u0026gt; (2833:0201)\n[   21.039299] uvcvideo 1-1:0.0: Entity type for entity Output 1 was not initialized!\n[   21.041583] uvcvideo 1-1:0.0: Entity type for entity Input 1 was not initialized!\n[   21.042218] ------------[ cut here ]------------\n[   21.042536] WARNING: CPU: 0 PID: 9 at drivers/media/mc/mc-entity.c:1147 media_create_pad_link+0x2c4/0x2e0\n[   21.043195] Modules linked in:\n[   21.043535] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.11.0-rc7-00030-g3480e43aeccf #444\n[   21.044101] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\n[   21.044639] Workqueue: usb_hub_wq hub_event\n[   21.045100] RIP: 0010:media_create_pad_link+0x2c4/0x2e0\n[   21.045508] Code: fe e8 20 01 00 00 b8 f4 ff ff ff 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 0f 0b eb e9 0f 0b eb 0a 0f 0b eb 06 \u0026lt;0f\u0026gt; 0b eb 02 0f 0b b8 ea ff ff ff eb d4 66 2e 0f 1f 84 00 00 00 00\n[   21.046801] RSP: 0018:ffffc9000004b318 EFLAGS: 00010246\n[   21.047227] RAX: ffff888004e5d458 RBX: 0000000000000000 RCX: ffffffff818fccf1\n[   21.047719] RDX: 000000000000007b RSI: 0000000000000000 RDI: ffff888004313290\n[   21.048241] RBP: ffff888004313290 R08: 0001ffffffffffff R09: 0000000000000000\n[   21.048701] R10: 0000000000000013 R11: 0001888004313290 R12: 0000000000000003\n[   21.049138] R13: ffff888004313080 R14: ffff888004313080 R15: 0000000000000000\n[   21.049648] FS:  0000000000000000(0000) GS:ffff88803ec00000(0000) knlGS:0000000000000000\n[   21.050271] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   21.050688] CR2: 0000592cc27635b0 CR3: 000000000431c000 CR4: 0000000000750ef0\n[   21.051136] PKRU: 55555554\n[   21.051331] Call Trace:\n[   21.051480]  \u0026lt;TASK\u0026gt;\n[   21.051611]  ? __warn+0xc4/0x210\n[   21.051861]  ? media_create_pad_link+0x2c4/0x2e0\n[   21.052252]  ? report_bug+0x11b/0x1a0\n[   21.052540]  ? trace_hardirqs_on+0x31/0x40\n[   21.052901]  ? handle_bug+0x3d/0x70\n[   21.053197]  ? exc_invalid_op+0x1a/0x50\n[   21.053511]  ? asm_exc_invalid_op+0x1a/0x20\n[   21.053924]  ? media_create_pad_link+0x91/0x2e0\n[   21.054364]  ? media_create_pad_link+0x2c4/0x2e0\n[   21.054834]  ? media_create_pad_link+0x91/0x2e0\n[   21.055131]  ? _raw_spin_unlock+0x1e/0x40\n[   21.055441]  ? __v4l2_device_register_subdev+0x202/0x210\n[   21.055837]  uvc_mc_register_entities+0x358/0x400\n[   21.056144]  uvc_register_chains+0x1fd/0x290\n[   21.056413]  uvc_probe+0x380e/0x3dc0\n[   21.056676]  ? __lock_acquire+0x5aa/0x26e0\n[   21.056946]  ? find_held_lock+0x33/0xa0\n[   21.057196]  ? kernfs_activate+0x70/0x80\n[   21.057533]  ? usb_match_dy\n---truncated---(CVE-2024-56571)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: hisi_sas: Create all dump files during debugfs initialization\n\nFor the current debugfs of hisi_sas, after user triggers dump, the\ndriver allocate memory space to save the register information and create\ndebugfs files to display the saved information. In this process, the\ndebugfs files created after each dump.\n\nTherefore, when the dump is triggered while the driver is unbind, the\nfollowing hang occurs:\n\n[67840.853907] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a0\n[67840.862947] Mem abort info:\n[67840.865855]   ESR = 0x0000000096000004\n[67840.869713]   EC = 0x25: DABT (current EL), IL = 32 bits\n[67840.875125]   SET = 0, FnV = 0\n[67840.878291]   EA = 0, S1PTW = 0\n[67840.881545]   FSC = 0x04: level 0 translation fault\n[67840.886528] Data abort info:\n[67840.889524]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n[67840.895117]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[67840.900284]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[67840.905709] user pgtable: 4k pages, 48-bit VAs, pgdp=0000002803a1f000\n[67840.912263] [00000000000000a0] pgd=0000000000000000, p4d=0000000000000000\n[67840.919177] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP\n[67840.996435] pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[67841.003628] pc : down_write+0x30/0x98\n[67841.007546] lr : start_creating.part.0+0x60/0x198\n[67841.012495] sp : ffff8000b979ba20\n[67841.016046] x29: ffff8000b979ba20 x28: 0000000000000010 x27: 0000000000024b40\n[67841.023412] x26: 0000000000000012 x25: ffff20202b355ae8 x24: ffff20202b35a8c8\n[67841.030779] x23: ffffa36877928208 x22: ffffa368b4972240 x21: ffff8000b979bb18\n[67841.038147] x20: ffff00281dc1e3c0 x19: fffffffffffffffe x18: 0000000000000020\n[67841.045515] x17: 0000000000000000 x16: ffffa368b128a530 x15: ffffffffffffffff\n[67841.052888] x14: ffff8000b979bc18 x13: ffffffffffffffff x12: ffff8000b979bb18\n[67841.060263] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa368b1289b18\n[67841.067640] x8 : 0000000000000012 x7 : 0000000000000000 x6 : 00000000000003a9\n[67841.075014] x5 : 0000000000000000 x4 : ffff002818c5cb00 x3 : 0000000000000001\n[67841.082388] x2 : 0000000000000000 x1 : ffff002818c5cb00 x0 : 00000000000000a0\n[67841.089759] Call trace:\n[67841.092456]  down_write+0x30/0x98\n[67841.096017]  start_creating.part.0+0x60/0x198\n[67841.100613]  debugfs_create_dir+0x48/0x1f8\n[67841.104950]  debugfs_create_files_v3_hw+0x88/0x348 [hisi_sas_v3_hw]\n[67841.111447]  debugfs_snapshot_regs_v3_hw+0x708/0x798 [hisi_sas_v3_hw]\n[67841.118111]  debugfs_trigger_dump_v3_hw_write+0x9c/0x120 [hisi_sas_v3_hw]\n[67841.125115]  full_proxy_write+0x68/0xc8\n[67841.129175]  vfs_write+0xd8/0x3f0\n[67841.132708]  ksys_write+0x70/0x108\n[67841.136317]  __arm64_sys_write+0x24/0x38\n[67841.140440]  invoke_syscall+0x50/0x128\n[67841.144385]  el0_svc_common.constprop.0+0xc8/0xf0\n[67841.149273]  do_el0_svc+0x24/0x38\n[67841.152773]  el0_svc+0x38/0xd8\n[67841.156009]  el0t_64_sync_handler+0xc0/0xc8\n[67841.160361]  el0t_64_sync+0x1a4/0x1a8\n[67841.164189] Code: b9000882 d2800002 d2800023 f9800011 (c85ffc05)\n[67841.170443] ---[ end trace 0000000000000000 ]---\n\nTo fix this issue, create all directories and files during debugfs\ninitialization. In this way, the driver only needs to allocate memory\nspace to save information each time the user triggers dumping.(CVE-2024-56588)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nkcsan: Turn report_filterlist_lock into a raw_spinlock\n\nRan Xiaokai reports that with a KCSAN-enabled PREEMPT_RT kernel, we can see\nsplats like:\n\n| BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\n| in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1\n| preempt_count: 10002, expected: 0\n| RCU nest depth: 0, expected: 0\n| no locks held by swapper/1/0.\n| irq event stamp: 156674\n| hardirqs last  enabled at (156673): [\u0026lt;ffffffff81130bd9\u0026gt;] do_idle+0x1f9/0x240\n| hardirqs last disabled at (156674): [\u0026lt;ffffffff82254f84\u0026gt;] sysvec_apic_timer_interrupt+0x14/0xc0\n| softirqs last  enabled at (0): [\u0026lt;ffffffff81099f47\u0026gt;] copy_process+0xfc7/0x4b60\n| softirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n| Preemption disabled at:\n| [\u0026lt;ffffffff814a3e2a\u0026gt;] paint_ptr+0x2a/0x90\n| CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.11.0+ #3\n| Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org 04/01/2014\n| Call Trace:\n|  \u0026lt;IRQ\u0026gt;\n|  dump_stack_lvl+0x7e/0xc0\n|  dump_stack+0x1d/0x30\n|  __might_resched+0x1a2/0x270\n|  rt_spin_lock+0x68/0x170\n|  kcsan_skip_report_debugfs+0x43/0xe0\n|  print_report+0xb5/0x590\n|  kcsan_report_known_origin+0x1b1/0x1d0\n|  kcsan_setup_watchpoint+0x348/0x650\n|  __tsan_unaligned_write1+0x16d/0x1d0\n|  hrtimer_interrupt+0x3d6/0x430\n|  __sysvec_apic_timer_interrupt+0xe8/0x3a0\n|  sysvec_apic_timer_interrupt+0x97/0xc0\n|  \u0026lt;/IRQ\u0026gt;\n\nOn a detected data race, KCSAN\u0026apos;s reporting logic checks if it should\nfilter the report. That list is protected by the report_filterlist_lock\n*non-raw* spinlock which may sleep on RT kernels.\n\nSince KCSAN may report data races in any context, convert it to a\nraw_spinlock.\n\nThis requires being careful about when to allocate memory for the filter\nlist itself which can be done via KCSAN\u0026apos;s debugfs interface. Concurrent\nmodification of the filter list via debugfs should be rare: the chosen\nstrategy is to optimistically pre-allocate memory before the critical\nsection and discard if unused.(CVE-2024-56610)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM\n\nWe currently assume that there is at least one VMA in a MM, which isn\u0026apos;t\ntrue.\n\nSo we might end up having find_vma() return NULL, to then de-reference\nNULL.  So properly handle find_vma() returning NULL.\n\nThis fixes the report:\n\nOops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\nCPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024\nRIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]\nRIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194\nCode: ...\nRSP: 0018:ffffc9000375fd08 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000\nRDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044\nRBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1\nR10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003\nR13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8\nFS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709\n __do_sys_migrate_pages mm/mempolicy.c:1727 [inline]\n __se_sys_migrate_pages mm/mempolicy.c:1723 [inline]\n __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723\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\n\n[akpm@linux-foundation.org: add unlikely()](CVE-2024-56611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix use after free on unload\n\nSystem crash is observed with stack trace warning of use after\nfree. There are 2 signals to tell dpc_thread to terminate (UNLOADING\nflag and kthread_stop).\n\nOn setting the UNLOADING flag when dpc_thread happens to run at the time\nand sees the flag, this causes dpc_thread to exit and clean up\nitself. When kthread_stop is called for final cleanup, this causes use\nafter free.\n\nRemove UNLOADING signal to terminate dpc_thread.  Use the kthread_stop\nas the main signal to exit dpc_thread.\n\n[596663.812935] kernel BUG at mm/slub.c:294!\n[596663.812950] invalid opcode: 0000 [#1] SMP PTI\n[596663.812957] CPU: 13 PID: 1475935 Comm: rmmod Kdump: loaded Tainted: G          IOE    --------- -  - 4.18.0-240.el8.x86_64 #1\n[596663.812960] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 08/20/2012\n[596663.812974] RIP: 0010:__slab_free+0x17d/0x360\n\n...\n[596663.813008] Call Trace:\n[596663.813022]  ? __dentry_kill+0x121/0x170\n[596663.813030]  ? _cond_resched+0x15/0x30\n[596663.813034]  ? _cond_resched+0x15/0x30\n[596663.813039]  ? wait_for_completion+0x35/0x190\n[596663.813048]  ? try_to_wake_up+0x63/0x540\n[596663.813055]  free_task+0x5a/0x60\n[596663.813061]  kthread_stop+0xf3/0x100\n[596663.813103]  qla2x00_remove_one+0x284/0x440 [qla2xxx](CVE-2024-56623)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport\n\nSince transport-\u0026gt;sock has been set to NULL during reset transport,\nXPRT_SOCK_UPD_TIMEOUT also needs to be cleared. Otherwise, the\nxs_tcp_set_socket_timeouts() may be triggered in xs_tcp_send_request()\nto dereference the transport-\u0026gt;sock that has been set to NULL.(CVE-2024-56688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n9p/xen: fix release of IRQ\n\nKernel logs indicate an IRQ was double-freed.\n\nPass correct device ID during IRQ release.\n\n[Dominique: remove confusing variable reset to 0](CVE-2024-56704)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nionic: Fix netdev notifier unregister on failure\n\nIf register_netdev() fails, then the driver leaks the netdev notifier.\nFix this by calling ionic_lif_unregister() on register_netdev()\nfailure. This will also call ionic_lif_unregister_phc() if it has\nalready been registered.(CVE-2024-56715)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem()\n\nWhen information such as info-\u0026gt;screen_base is not ready, calling\nsh7760fb_free_mem() does not release memory correctly. Call\ndma_free_coherent() instead.(CVE-2024-56746)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix slab-use-after-free due to dangling pointer dqi_priv\n\nWhen mounting ocfs2 and then remounting it as read-only, a\nslab-use-after-free occurs after the user uses a syscall to\nquota_getnextquota.  Specifically, sb_dqinfo(sb, type)-\u0026gt;dqi_priv is the\ndangling pointer.\n\nDuring the remounting process, the pointer dqi_priv is freed but is never\nset as null leaving it to be accessed.  Additionally, the read-only option\nfor remounting sets the DQUOT_SUSPENDED flag instead of setting the\nDQUOT_USAGE_ENABLED flags.  Moreover, later in the process of getting the\nnext quota, the function ocfs2_get_next_id is called and only checks the\nquota usage flags and not the quota suspended flags.\n\nTo fix this, I set dqi_priv to null when it is freed after remounting with\nread-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id.\n\n[akpm@linux-foundation.org: coding-style cleanups](CVE-2024-57892)","status":"published","published":"2025-02-08T11:08:11Z","modified":"2026-08-18T01:17:43.09203885Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2025-1096","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential OOBs in smb2_parse_contexts()\n\nValidate offsets and lengths before dereferencing create contexts in\nsmb2_parse_contexts().\n\nThis fixes following oops when accessing invalid create contexts from\nserver:\n\n  BUG: unable to handle page fault for address: ffff8881178d8cc3\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 4a01067 P4D 4a01067 PUD 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 3 PID: 1736 Comm: mount.cifs Not tainted 6.7.0-rc4 #1\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS\n  rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014\n  RIP: 0010:smb2_parse_contexts+0xa0/0x3a0 [cifs]\n  Code: f8 10 75 13 48 b8 93 ad 25 50 9c b4 11 e7 49 39 06 0f 84 d2 00\n  00 00 8b 45 00 85 c0 74 61 41 29 c5 48 01 c5 41 83 fd 0f 76 55 \u0026lt;0f\u0026gt; b7\n  7d 04 0f b7 45 06 4c 8d 74 3d 00 66 83 f8 04 75 bc ba 04 00\n  RSP: 0018:ffffc900007939e0 EFLAGS: 00010216\n  RAX: ffffc90000793c78 RBX: ffff8880180cc000 RCX: ffffc90000793c90\n  RDX: ffffc90000793cc0 RSI: ffff8880178d8cc0 RDI: ffff8880180cc000\n  RBP: ffff8881178d8cbf R08: ffffc90000793c22 R09: 0000000000000000\n  R10: ffff8880180cc000 R11: 0000000000000024 R12: 0000000000000000\n  R13: 0000000000000020 R14: 0000000000000000 R15: ffffc90000793c22\n  FS: 00007f873753cbc0(0000) GS:ffff88806bc00000(0000)\n  knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: ffff8881178d8cc3 CR3: 00000000181ca000 CR4: 0000000000750ef0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ? __die+0x23/0x70\n   ? page_fault_oops+0x181/0x480\n   ? search_module_extables+0x19/0x60\n   ? srso_alias_return_thunk+0x5/0xfbef5\n   ? exc_page_fault+0x1b6/0x1c0\n   ? asm_exc_page_fault+0x26/0x30\n   ? smb2_parse_contexts+0xa0/0x3a0 [cifs]\n   SMB2_open+0x38d/0x5f0 [cifs]\n   ? smb2_is_path_accessible+0x138/0x260 [cifs]\n   smb2_is_path_accessible+0x138/0x260 [cifs]\n   cifs_is_path_remote+0x8d/0x230 [cifs]\n   cifs_mount+0x7e/0x350 [cifs]\n   cifs_smb3_do_mount+0x128/0x780 [cifs]\n   smb3_get_tree+0xd9/0x290 [cifs]\n   vfs_get_tree+0x2c/0x100\n   ? capable+0x37/0x70\n   path_mount+0x2d7/0xb80\n   ? srso_alias_return_thunk+0x5/0xfbef5\n   ? _raw_spin_unlock_irqrestore+0x44/0x60\n   __x64_sys_mount+0x11a/0x150\n   do_syscall_64+0x47/0xf0\n   entry_SYSCALL_64_after_hwframe+0x6f/0x77\n  RIP: 0033:0x7f8737657b1e(CVE-2023-52434)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix race condition between session lookup and expire\n\n Thread A                        +  Thread B\n ksmbd_session_lookup            |  smb2_sess_setup\n   sess = xa_load                |\n                                 |\n                                 |    xa_erase(\u0026amp;conn-\u0026gt;sessions, sess-\u0026gt;id);\n                                 |\n                                 |    ksmbd_session_destroy(sess) --\u0026gt; kfree(sess)\n                                 |\n   // UAF!                       |\n   sess-\u0026gt;last_active = jiffies   |\n                                 +\n\nThis patch add rwsem to fix race condition between ksmbd_session_lookup\nand ksmbd_expire_session.(CVE-2023-52480)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Fix buffer overflow in trans_stat_show\n\nFix buffer overflow in trans_stat_show().\n\nConvert simple snprintf to the more secure scnprintf with size of\nPAGE_SIZE.\n\nAdd condition checking if we are exceeding PAGE_SIZE and exit early from\nloop. Also add at the end a warning that we exceeded PAGE_SIZE and that\nstats is disabled.\n\nReturn -EFBIG in the case where we don\u0026apos;t have enough space to write the\nfull transition table.\n\nAlso document in the ABI that this function can return -EFBIG error.(CVE-2023-52614)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: adc: ad7091r: Allow users to configure device events\n\nAD7091R-5 devices are supported by the ad7091r-5 driver together with\nthe ad7091r-base driver. Those drivers declared iio events for notifying\nuser space when ADC readings fall bellow the thresholds of low limit\nregisters or above the values set in high limit registers.\nHowever, to configure iio events and their thresholds, a set of callback\nfunctions must be implemented and those were not present until now.\nThe consequence of trying to configure ad7091r-5 events without the\nproper callback functions was a null pointer dereference in the kernel\nbecause the pointers to the callback functions were not set.\n\nImplement event configuration callbacks allowing users to read/write\nevent thresholds and enable/disable event generation.\n\nSince the event spec structs are generic to AD7091R devices, also move\nthose from the ad7091r-5 driver the base driver so they can be reused\nwhen support for ad7091r-2/-4/-8 be added.(CVE-2023-52627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915: Fix potential context UAFs\n\ngem_context_register() makes the context visible to userspace, and which\npoint a separate thread can trigger the I915_GEM_CONTEXT_DESTROY ioctl.\nSo we need to ensure that nothing uses the ctx ptr after this.  And we\nneed to ensure that adding the ctx to the xarray is the *last* thing\nthat gem_context_register() does with the ctx pointer.\n\n[tursulin: Stable and fixes tags add/tidy.]\n(cherry picked from commit bed4b455cf5374e68879be56971c1da563bcd90c)(CVE-2023-52913)\n\nA race condition was found in the Linux kernel\u0026apos;s net/bluetooth device driver in conn_info_{min,max}_age_set() function. This can result in integrity overflow issue, possibly leading to bluetooth connection abnormality or denial of service.\n\n\n\n\n(CVE-2024-24857)\n\nA race condition was found in the Linux kernel\u0026apos;s net/bluetooth in sniff_{min,max}_interval_set() function. This can result in a bluetooth sniffing exception issue, possibly leading denial of service.\n\n\n\n\n\n\n\n(CVE-2024-24859)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxhci: handle isoc Babble and Buffer Overrun events properly\n\nxHCI 4.9 explicitly forbids assuming that the xHC has released its\nownership of a multi-TRB TD when it reports an error on one of the\nearly TRBs. Yet the driver makes such assumption and releases the TD,\nallowing the remaining TRBs to be freed or overwritten by new TDs.\n\nThe xHC should also report completion of the final TRB due to its IOC\nflag being set by us, regardless of prior errors. This event cannot\nbe recognized if the TD has already been freed earlier, resulting in\n\u0026quot;Transfer event TRB DMA ptr not part of current TD\u0026quot; error message.\n\nFix this by reusing the logic for processing isoc Transaction Errors.\nThis also handles hosts which fail to report the final completion.\n\nFix transfer length reporting on Babble errors. They may be caused by\ndevice malfunction, no guarantee that the buffer has been filled.(CVE-2024-26659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (coretemp) Fix out-of-bounds memory access\n\nFix a bug that pdata-\u0026gt;cpu_map[] is set before out-of-bounds check.\nThe problem might be triggered on systems with more than 128 cores per\npackage.(CVE-2024-26664)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations\n\n- Disallow families other than NFPROTO_{IPV4,IPV6,INET}.\n- Disallow layer 4 protocol with no ports, since destination port is a\n  mandatory attribute for this object.(CVE-2024-26673)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: roles: fix NULL pointer issue when put module\u0026apos;s reference\n\nIn current design, usb role class driver will get usb_role_switch parent\u0026apos;s\nmodule reference after the user get usb_role_switch device and put the\nreference after the user put the usb_role_switch device. However, the\nparent device of usb_role_switch may be removed before the user put the\nusb_role_switch. If so, then, NULL pointer issue will be met when the user\nput the parent module\u0026apos;s reference.\n\nThis will save the module pointer in structure of usb_role_switch. Then,\nwe don\u0026apos;t need to find module by iterating long relations.(CVE-2024-26747)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix memory double free when handle zero packet\n\n829  if (request-\u0026gt;complete) {\n830          spin_unlock(\u0026amp;priv_dev-\u0026gt;lock);\n831          usb_gadget_giveback_request(\u0026amp;priv_ep-\u0026gt;endpoint,\n832                                    request);\n833          spin_lock(\u0026amp;priv_dev-\u0026gt;lock);\n834  }\n835\n836  if (request-\u0026gt;buf == priv_dev-\u0026gt;zlp_buf)\n837      cdns3_gadget_ep_free_request(\u0026amp;priv_ep-\u0026gt;endpoint, request);\n\nDriver append an additional zero packet request when queue a packet, which\nlength mod max packet size is 0. When transfer complete, run to line 831,\nusb_gadget_giveback_request() will free this requestion. 836 condition is\ntrue, so cdns3_gadget_ep_free_request() free this request again.\n\nLog:\n\n[ 1920.140696][  T150] BUG: KFENCE: use-after-free read in cdns3_gadget_giveback+0x134/0x2c0 [cdns3]\n[ 1920.140696][  T150]\n[ 1920.151837][  T150] Use-after-free read at 0x000000003d1cd10b (in kfence-#36):\n[ 1920.159082][  T150]  cdns3_gadget_giveback+0x134/0x2c0 [cdns3]\n[ 1920.164988][  T150]  cdns3_transfer_completed+0x438/0x5f8 [cdns3]\n\nAdd check at line 829, skip call usb_gadget_giveback_request() if it is\nadditional zero length packet request. Needn\u0026apos;t call\nusb_gadget_giveback_request() because it is allocated in this driver.(CVE-2024-26748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fixed memory use after free at cdns3_gadget_ep_disable()\n\n  ...\n  cdns3_gadget_ep_free_request(\u0026amp;priv_ep-\u0026gt;endpoint, \u0026amp;priv_req-\u0026gt;request);\n  list_del_init(\u0026amp;priv_req-\u0026gt;list);\n  ...\n\n\u0026apos;priv_req\u0026apos; actually free at cdns3_gadget_ep_free_request(). But\nlist_del_init() use priv_req-\u0026gt;list after it.\n\n[ 1542.642868][  T534] BUG: KFENCE: use-after-free read in __list_del_entry_valid+0x10/0xd4\n[ 1542.642868][  T534]\n[ 1542.653162][  T534] Use-after-free read at 0x000000009ed0ba99 (in kfence-#3):\n[ 1542.660311][  T534]  __list_del_entry_valid+0x10/0xd4\n[ 1542.665375][  T534]  cdns3_gadget_ep_disable+0x1f8/0x388 [cdns3]\n[ 1542.671571][  T534]  usb_ep_disable+0x44/0xe4\n[ 1542.675948][  T534]  ffs_func_eps_disable+0x64/0xc8\n[ 1542.680839][  T534]  ffs_func_set_alt+0x74/0x368\n[ 1542.685478][  T534]  ffs_func_disable+0x18/0x28\n\nMove list_del_init() before cdns3_gadget_ep_free_request() to resolve this\nproblem.(CVE-2024-26749)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: virtio/akcipher - Fix stack overflow on memcpy\n\nsizeof(struct virtio_crypto_akcipher_session_para) is less than\nsizeof(struct virtio_crypto_op_ctrl_req::u), copying more bytes from\nstack variable leads stack overflow. Clang reports this issue by\ncommands:\nmake -j CC=clang-14 mrproper \u0026gt;/dev/null 2\u0026gt;\u0026amp;1\nmake -j O=/tmp/crypto-build CC=clang-14 allmodconfig \u0026gt;/dev/null 2\u0026gt;\u0026amp;1\nmake -j O=/tmp/crypto-build W=1 CC=clang-14 drivers/crypto/virtio/\n  virtio_crypto_akcipher_algs.o(CVE-2024-26753)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix possible deadlock in subflow diag\n\nSyzbot and Eric reported a lockdep splat in the subflow diag:\n\n   WARNING: possible circular locking dependency detected\n   6.8.0-rc4-syzkaller-00212-g40b9385dd8e6 #0 Not tainted\n\n   syz-executor.2/24141 is trying to acquire lock:\n   ffff888045870130 (k-sk_lock-AF_INET6){+.+.}-{0:0}, at:\n   tcp_diag_put_ulp net/ipv4/tcp_diag.c:100 [inline]\n   ffff888045870130 (k-sk_lock-AF_INET6){+.+.}-{0:0}, at:\n   tcp_diag_get_aux+0x738/0x830 net/ipv4/tcp_diag.c:137\n\n   but task is already holding lock:\n   ffffc9000135e488 (\u0026amp;h-\u0026gt;lhash2[i].lock){+.+.}-{2:2}, at: spin_lock\n   include/linux/spinlock.h:351 [inline]\n   ffffc9000135e488 (\u0026amp;h-\u0026gt;lhash2[i].lock){+.+.}-{2:2}, at:\n   inet_diag_dump_icsk+0x39f/0x1f80 net/ipv4/inet_diag.c:1038\n\n   which lock already depends on the new lock.\n\n   the existing dependency chain (in reverse order) is:\n\n   -\u0026gt; #1 (\u0026amp;h-\u0026gt;lhash2[i].lock){+.+.}-{2:2}:\n   lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754\n   __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]\n   _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154\n   spin_lock include/linux/spinlock.h:351 [inline]\n   __inet_hash+0x335/0xbe0 net/ipv4/inet_hashtables.c:743\n   inet_csk_listen_start+0x23a/0x320 net/ipv4/inet_connection_sock.c:1261\n   __inet_listen_sk+0x2a2/0x770 net/ipv4/af_inet.c:217\n   inet_listen+0xa3/0x110 net/ipv4/af_inet.c:239\n   rds_tcp_listen_init+0x3fd/0x5a0 net/rds/tcp_listen.c:316\n   rds_tcp_init_net+0x141/0x320 net/rds/tcp.c:577\n   ops_init+0x352/0x610 net/core/net_namespace.c:136\n   __register_pernet_operations net/core/net_namespace.c:1214 [inline]\n   register_pernet_operations+0x2cb/0x660 net/core/net_namespace.c:1283\n   register_pernet_device+0x33/0x80 net/core/net_namespace.c:1370\n   rds_tcp_init+0x62/0xd0 net/rds/tcp.c:735\n   do_one_initcall+0x238/0x830 init/main.c:1236\n   do_initcall_level+0x157/0x210 init/main.c:1298\n   do_initcalls+0x3f/0x80 init/main.c:1314\n   kernel_init_freeable+0x42f/0x5d0 init/main.c:1551\n   kernel_init+0x1d/0x2a0 init/main.c:1441\n   ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147\n   ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242\n\n   -\u0026gt; #0 (k-sk_lock-AF_INET6){+.+.}-{0:0}:\n   check_prev_add kernel/locking/lockdep.c:3134 [inline]\n   check_prevs_add kernel/locking/lockdep.c:3253 [inline]\n   validate_chain+0x18ca/0x58e0 kernel/locking/lockdep.c:3869\n   __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137\n   lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754\n   lock_sock_fast include/net/sock.h:1723 [inline]\n   subflow_get_info+0x166/0xd20 net/mptcp/diag.c:28\n   tcp_diag_put_ulp net/ipv4/tcp_diag.c:100 [inline]\n   tcp_diag_get_aux+0x738/0x830 net/ipv4/tcp_diag.c:137\n   inet_sk_diag_fill+0x10ed/0x1e00 net/ipv4/inet_diag.c:345\n   inet_diag_dump_icsk+0x55b/0x1f80 net/ipv4/inet_diag.c:1061\n   __inet_diag_dump+0x211/0x3a0 net/ipv4/inet_diag.c:1263\n   inet_diag_dump_compat+0x1c1/0x2d0 net/ipv4/inet_diag.c:1371\n   netlink_dump+0x59b/0xc80 net/netlink/af_netlink.c:2264\n   __netlink_dump_start+0x5df/0x790 net/netlink/af_netlink.c:2370\n   netlink_dump_start include/linux/netlink.h:338 [inline]\n   inet_diag_rcv_msg_compat+0x209/0x4c0 net/ipv4/inet_diag.c:1405\n   sock_diag_rcv_msg+0xe7/0x410\n   netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2543\n   sock_diag_rcv+0x2a/0x40 net/core/sock_diag.c:280\n   netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]\n   netlink_unicast+0x7ea/0x980 net/netlink/af_netlink.c:1367\n   netlink_sendmsg+0xa3b/0xd70 net/netlink/af_netlink.c:1908\n   sock_sendmsg_nosec net/socket.c:730 [inline]\n   __sock_sendmsg+0x221/0x270 net/socket.c:745\n   ____sys_sendmsg+0x525/0x7d0 net/socket.c:2584\n   ___sys_sendmsg net/socket.c:2638 [inline]\n   __sys_sendmsg+0x2b0/0x3a0 net/socket.c:2667\n   do_syscall_64+0xf9/0x240\n   entry_SYSCALL_64_after_hwframe+0x6f/0x77\n\nAs noted by Eric we can break the lock dependency chain avoid\ndumping \n---truncated---(CVE-2024-26781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read\n\nThere is chip (ls1028a) errata:\n\nThe SoC may hang on 16 byte unaligned read transactions by QDMA.\n\nUnaligned read transactions initiated by QDMA may stall in the NOC\n(Network On-Chip), causing a deadlock condition. Stalled transactions will\ntrigger completion timeouts in PCIe controller.\n\nWorkaround:\nEnable prefetch by setting the source descriptor prefetchable bit\n( SD[PF] = 1 ).\n\nImplement this workaround.(CVE-2024-26790)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngtp: fix use-after-free and null-ptr-deref in gtp_newlink()\n\nThe gtp_link_ops operations structure for the subsystem must be\nregistered after registering the gtp_net_ops pernet operations structure.\n\nSyzkaller hit \u0026apos;general protection fault in gtp_genl_dump_pdp\u0026apos; bug:\n\n[ 1010.702740] gtp: GTP module unloaded\n[ 1010.715877] general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI\n[ 1010.715888] KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]\n[ 1010.715895] CPU: 1 PID: 128616 Comm: a.out Not tainted 6.8.0-rc6-std-def-alt1 #1\n[ 1010.715899] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-alt1 04/01/2014\n[ 1010.715908] RIP: 0010:gtp_newlink+0x4d7/0x9c0 [gtp]\n[ 1010.715915] Code: 80 3c 02 00 0f 85 41 04 00 00 48 8b bb d8 05 00 00 e8 ed f6 ff ff 48 89 c2 48 89 c5 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02 00 0f 85 4f 04 00 00 4c 89 e2 4c 8b 6d 00 48 b8 00 00 00\n[ 1010.715920] RSP: 0018:ffff888020fbf180 EFLAGS: 00010203\n[ 1010.715929] RAX: dffffc0000000000 RBX: ffff88800399c000 RCX: 0000000000000000\n[ 1010.715933] RDX: 0000000000000001 RSI: ffffffff84805280 RDI: 0000000000000282\n[ 1010.715938] RBP: 000000000000000d R08: 0000000000000001 R09: 0000000000000000\n[ 1010.715942] R10: 0000000000000001 R11: 0000000000000001 R12: ffff88800399cc80\n[ 1010.715947] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000400\n[ 1010.715953] FS:  00007fd1509ab5c0(0000) GS:ffff88805b300000(0000) knlGS:0000000000000000\n[ 1010.715958] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1010.715962] CR2: 0000000000000000 CR3: 000000001c07a000 CR4: 0000000000750ee0\n[ 1010.715968] PKRU: 55555554\n[ 1010.715972] Call Trace:\n[ 1010.715985]  ? __die_body.cold+0x1a/0x1f\n[ 1010.715995]  ? die_addr+0x43/0x70\n[ 1010.716002]  ? exc_general_protection+0x199/0x2f0\n[ 1010.716016]  ? asm_exc_general_protection+0x1e/0x30\n[ 1010.716026]  ? gtp_newlink+0x4d7/0x9c0 [gtp]\n[ 1010.716034]  ? gtp_net_exit+0x150/0x150 [gtp]\n[ 1010.716042]  __rtnl_newlink+0x1063/0x1700\n[ 1010.716051]  ? rtnl_setlink+0x3c0/0x3c0\n[ 1010.716063]  ? is_bpf_text_address+0xc0/0x1f0\n[ 1010.716070]  ? kernel_text_address.part.0+0xbb/0xd0\n[ 1010.716076]  ? __kernel_text_address+0x56/0xa0\n[ 1010.716084]  ? unwind_get_return_address+0x5a/0xa0\n[ 1010.716091]  ? create_prof_cpu_mask+0x30/0x30\n[ 1010.716098]  ? arch_stack_walk+0x9e/0xf0\n[ 1010.716106]  ? stack_trace_save+0x91/0xd0\n[ 1010.716113]  ? stack_trace_consume_entry+0x170/0x170\n[ 1010.716121]  ? __lock_acquire+0x15c5/0x5380\n[ 1010.716139]  ? mark_held_locks+0x9e/0xe0\n[ 1010.716148]  ? kmem_cache_alloc_trace+0x35f/0x3c0\n[ 1010.716155]  ? __rtnl_newlink+0x1700/0x1700\n[ 1010.716160]  rtnl_newlink+0x69/0xa0\n[ 1010.716166]  rtnetlink_rcv_msg+0x43b/0xc50\n[ 1010.716172]  ? rtnl_fdb_dump+0x9f0/0x9f0\n[ 1010.716179]  ? lock_acquire+0x1fe/0x560\n[ 1010.716188]  ? netlink_deliver_tap+0x12f/0xd50\n[ 1010.716196]  netlink_rcv_skb+0x14d/0x440\n[ 1010.716202]  ? rtnl_fdb_dump+0x9f0/0x9f0\n[ 1010.716208]  ? netlink_ack+0xab0/0xab0\n[ 1010.716213]  ? netlink_deliver_tap+0x202/0xd50\n[ 1010.716220]  ? netlink_deliver_tap+0x218/0xd50\n[ 1010.716226]  ? __virt_addr_valid+0x30b/0x590\n[ 1010.716233]  netlink_unicast+0x54b/0x800\n[ 1010.716240]  ? netlink_attachskb+0x870/0x870\n[ 1010.716248]  ? __check_object_size+0x2de/0x3b0\n[ 1010.716254]  netlink_sendmsg+0x938/0xe40\n[ 1010.716261]  ? netlink_unicast+0x800/0x800\n[ 1010.716269]  ? __import_iovec+0x292/0x510\n[ 1010.716276]  ? netlink_unicast+0x800/0x800\n[ 1010.716284]  __sock_sendmsg+0x159/0x190\n[ 1010.716290]  ____sys_sendmsg+0x712/0x880\n[ 1010.716297]  ? sock_write_iter+0x3d0/0x3d0\n[ 1010.716304]  ? __ia32_sys_recvmmsg+0x270/0x270\n[ 1010.716309]  ? lock_acquire+0x1fe/0x560\n[ 1010.716315]  ? drain_array_locked+0x90/0x90\n[ 1010.716324]  ___sys_sendmsg+0xf8/0x170\n[ 1010.716331]  ? sendmsg_copy_msghdr+0x170/0x170\n[ 1010.716337]  ? lockdep_init_map\n---truncated---(CVE-2024-26793)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix potencial out-of-bounds when buffer offset is invalid\n\nI found potencial out-of-bounds when buffer offset fields of a few requests\nis invalid. This patch set the minimum value of buffer offset field to\n-\u0026gt;Buffer offset to validate buffer length.(CVE-2024-26952)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()\n\nIf -\u0026gt;NameOffset of smb2_create_req is smaller than Buffer offset of\nsmb2_create_req, slab-out-of-bounds read can happen from smb2_open.\nThis patch set the minimum value of the name offset to the buffer offset\nto validate name length of smb2_create_req().(CVE-2024-26954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: Get runtime PM before walking tree during disable_unused\n\nDoug reported [1] the following hung task:\n\n INFO: task swapper/0:1 blocked for more than 122 seconds.\n       Not tainted 5.15.149-21875-gf795ebc40eb8 #1\n \u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\n task:swapper/0       state:D stack:    0 pid:    1 ppid:     0 flags:0x00000008\n Call trace:\n  __switch_to+0xf4/0x1f4\n  __schedule+0x418/0xb80\n  schedule+0x5c/0x10c\n  rpm_resume+0xe0/0x52c\n  rpm_resume+0x178/0x52c\n  __pm_runtime_resume+0x58/0x98\n  clk_pm_runtime_get+0x30/0xb0\n  clk_disable_unused_subtree+0x58/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused_subtree+0x38/0x208\n  clk_disable_unused+0x4c/0xe4\n  do_one_initcall+0xcc/0x2d8\n  do_initcall_level+0xa4/0x148\n  do_initcalls+0x5c/0x9c\n  do_basic_setup+0x24/0x30\n  kernel_init_freeable+0xec/0x164\n  kernel_init+0x28/0x120\n  ret_from_fork+0x10/0x20\n INFO: task kworker/u16:0:9 blocked for more than 122 seconds.\n       Not tainted 5.15.149-21875-gf795ebc40eb8 #1\n \u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\n task:kworker/u16:0   state:D stack:    0 pid:    9 ppid:     2 flags:0x00000008\n Workqueue: events_unbound deferred_probe_work_func\n Call trace:\n  __switch_to+0xf4/0x1f4\n  __schedule+0x418/0xb80\n  schedule+0x5c/0x10c\n  schedule_preempt_disabled+0x2c/0x48\n  __mutex_lock+0x238/0x488\n  __mutex_lock_slowpath+0x1c/0x28\n  mutex_lock+0x50/0x74\n  clk_prepare_lock+0x7c/0x9c\n  clk_core_prepare_lock+0x20/0x44\n  clk_prepare+0x24/0x30\n  clk_bulk_prepare+0x40/0xb0\n  mdss_runtime_resume+0x54/0x1c8\n  pm_generic_runtime_resume+0x30/0x44\n  __genpd_runtime_resume+0x68/0x7c\n  genpd_runtime_resume+0x108/0x1f4\n  __rpm_callback+0x84/0x144\n  rpm_callback+0x30/0x88\n  rpm_resume+0x1f4/0x52c\n  rpm_resume+0x178/0x52c\n  __pm_runtime_resume+0x58/0x98\n  __device_attach+0xe0/0x170\n  device_initial_probe+0x1c/0x28\n  bus_probe_device+0x3c/0x9c\n  device_add+0x644/0x814\n  mipi_dsi_device_register_full+0xe4/0x170\n  devm_mipi_dsi_device_register_full+0x28/0x70\n  ti_sn_bridge_probe+0x1dc/0x2c0\n  auxiliary_bus_probe+0x4c/0x94\n  really_probe+0xcc/0x2c8\n  __driver_probe_device+0xa8/0x130\n  driver_probe_device+0x48/0x110\n  __device_attach_driver+0xa4/0xcc\n  bus_for_each_drv+0x8c/0xd8\n  __device_attach+0xf8/0x170\n  device_initial_probe+0x1c/0x28\n  bus_probe_device+0x3c/0x9c\n  deferred_probe_work_func+0x9c/0xd8\n  process_one_work+0x148/0x518\n  worker_thread+0x138/0x350\n  kthread+0x138/0x1e0\n  ret_from_fork+0x10/0x20\n\nThe first thread is walking the clk tree and calling\nclk_pm_runtime_get() to power on devices required to read the clk\nhardware via struct clk_ops::is_enabled(). This thread holds the clk\nprepare_lock, and is trying to runtime PM resume a device, when it finds\nthat the device is in the process of resuming so the thread schedule()s\naway waiting for the device to finish resuming before continuing. The\nsecond thread is runtime PM resuming the same device, but the runtime\nresume callback is calling clk_prepare(), trying to grab the\nprepare_lock waiting on the first thread.\n\nThis is a classic ABBA deadlock. To properly fix the deadlock, we must\nnever runtime PM resume or suspend a device with the clk prepare_lock\nheld. Actually doing that is near impossible today because the global\nprepare_lock would have to be dropped in the middle of the tree, the\ndevice runtime PM resumed/suspended, and then the prepare_lock grabbed\nagain to ensure consistency of the clk tree topology. If anything\nchanges with the clk tree in the meantime, we\u0026apos;ve lost and will need to\nstart the operation all over again.\n\nLuckily, most of the time we\u0026apos;re simply incrementing or decrementing the\nruntime PM count on an active device, so we don\u0026apos;t have the chance to\nschedule away with the prepare_lock held. Let\u0026apos;s fix this immediate\nproblem that can be\n---truncated---(CVE-2024-27004)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfpga: bridge: add owner module and take its refcount\n\nThe current implementation of the fpga bridge assumes that the low-level\nmodule registers a driver for the parent device and uses its owner pointer\nto take the module\u0026apos;s refcount. This approach is problematic since it can\nlead to a null pointer dereference while attempting to get the bridge if\nthe parent device does not have a driver.\n\nTo address this problem, add a module owner pointer to the fpga_bridge\nstruct and use it to take the module\u0026apos;s refcount. Modify the function for\nregistering a bridge to take an additional owner module parameter and\nrename it to avoid conflicts. Use the old function name for a helper macro\nthat automatically sets the module that registers the bridge as the owner.\nThis ensures compatibility with existing low-level control modules and\nreduces the chances of registering a bridge without setting the owner.\n\nAlso, update the documentation to keep it consistent with the new interface\nfor registering an fpga bridge.\n\nOther changes: opportunistically move put_device() from __fpga_bridge_get()\nto fpga_bridge_get() and of_fpga_bridge_get() to improve code clarity since\nthe bridge device is taken in these functions.(CVE-2024-36479)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfpga: manager: add owner module and take its refcount\n\nThe current implementation of the fpga manager assumes that the low-level\nmodule registers a driver for the parent device and uses its owner pointer\nto take the module\u0026apos;s refcount. This approach is problematic since it can\nlead to a null pointer dereference while attempting to get the manager if\nthe parent device does not have a driver.\n\nTo address this problem, add a module owner pointer to the fpga_manager\nstruct and use it to take the module\u0026apos;s refcount. Modify the functions for\nregistering the manager to take an additional owner module parameter and\nrename them to avoid conflicts. Use the old function names for helper\nmacros that automatically set the module that registers the manager as the\nowner. This ensures compatibility with existing low-level control modules\nand reduces the chances of registering a manager without setting the owner.\n\nAlso, update the documentation to keep it consistent with the new interface\nfor registering an fpga manager.\n\nOther changes: opportunistically move put_device() from __fpga_mgr_get() to\nfpga_mgr_get() and of_fpga_mgr_get() to improve code clarity since the\nmanager device is taken in these functions.(CVE-2024-37021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.(CVE-2024-40965)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64: probes: Fix uprobes for big-endian kernels\n\nThe arm64 uprobes code is broken for big-endian kernels as it doesn\u0026apos;t\nconvert the in-memory instruction encoding (which is always\nlittle-endian) into the kernel\u0026apos;s native endianness before analyzing and\nsimulating instructions. This may result in a few distinct problems:\n\n* The kernel may may erroneously reject probing an instruction which can\n  safely be probed.\n\n* The kernel may erroneously erroneously permit stepping an\n  instruction out-of-line when that instruction cannot be stepped\n  out-of-line safely.\n\n* The kernel may erroneously simulate instruction incorrectly dur to\n  interpretting the byte-swapped encoding.\n\nThe endianness mismatch isn\u0026apos;t caught by the compiler or sparse because:\n\n* The arch_uprobe::{insn,ixol} fields are encoded as arrays of u8, so\n  the compiler and sparse have no idea these contain a little-endian\n  32-bit value. The core uprobes code populates these with a memcpy()\n  which similarly does not handle endianness.\n\n* While the uprobe_opcode_t type is an alias for __le32, both\n  arch_uprobe_analyze_insn() and arch_uprobe_skip_sstep() cast from u8[]\n  to the similarly-named probe_opcode_t, which is an alias for u32.\n  Hence there is no endianness conversion warning.\n\nFix this by changing the arch_uprobe::{insn,ixol} fields to __le32 and\nadding the appropriate __le32_to_cpu() conversions prior to consuming\nthe instruction encoding. The core uprobes copies these fields as opaque\nranges of bytes, and so is unaffected by this change.\n\nAt the same time, remove MAX_UINSN_BYTES and consistently use\nAARCH64_INSN_SIZE for clarity.\n\nTested with the following:\n\n| #include \u0026lt;stdio.h\u0026gt;\n| #include \u0026lt;stdbool.h\u0026gt;\n|\n| #define noinline __attribute__((noinline))\n|\n| static noinline void *adrp_self(void)\n| {\n|         void *addr;\n|\n|         asm volatile(\n|         \u0026quot;       adrp    %x0, adrp_self\\n\u0026quot;\n|         \u0026quot;       add     %x0, %x0, :lo12:adrp_self\\n\u0026quot;\n|         : \u0026quot;=r\u0026quot; (addr));\n| }\n|\n|\n| int main(int argc, char *argv)\n| {\n|         void *ptr = adrp_self();\n|         bool equal = (ptr == adrp_self);\n|\n|         printf(\u0026quot;adrp_self   =\u0026gt; %p\\n\u0026quot;\n|                \u0026quot;adrp_self() =\u0026gt; %p\\n\u0026quot;\n|                \u0026quot;%s\\n\u0026quot;,\n|                adrp_self, ptr, equal ? \u0026quot;EQUAL\u0026quot; : \u0026quot;NOT EQUAL\u0026quot;);\n|\n|         return 0;\n| }\n\n.... where the adrp_self() function was compiled to:\n\n| 00000000004007e0 \u0026lt;adrp_self\u0026gt;:\n|   4007e0:       90000000        adrp    x0, 400000 \u0026lt;__ehdr_start\u0026gt;\n|   4007e4:       911f8000        add     x0, x0, #0x7e0\n|   4007e8:       d65f03c0        ret\n\nBefore this patch, the ADRP is not recognized, and is assumed to be\nsteppable, resulting in corruption of the result:\n\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0x4007e0\n| EQUAL\n| # echo \u0026apos;p /root/adrp-self:0x007e0\u0026apos; \u0026gt; /sys/kernel/tracing/uprobe_events\n| # echo 1 \u0026gt; /sys/kernel/tracing/events/uprobes/enable\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0xffffffffff7e0\n| NOT EQUAL\n\nAfter this patch, the ADRP is correctly recognized and simulated:\n\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0x4007e0\n| EQUAL\n| #\n| # echo \u0026apos;p /root/adrp-self:0x007e0\u0026apos; \u0026gt; /sys/kernel/tracing/uprobe_events\n| # echo 1 \u0026gt; /sys/kernel/tracing/events/uprobes/enable\n| # ./adrp-self\n| adrp_self   =\u0026gt; 0x4007e0\n| adrp_self() =\u0026gt; 0x4007e0\n| EQUAL(CVE-2024-50194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm cache: fix flushing uninitialized delayed_work on cache_ctr error\n\nAn unexpected WARN_ON from flush_work() may occur when cache creation\nfails, caused by destroying the uninitialized delayed_work waker in the\nerror path of cache_create(). For example, the warning appears on the\nsuperblock checksum error.\n\nReproduce steps:\n\ndmsetup create cmeta --table \u0026quot;0 8192 linear /dev/sdc 0\u0026quot;\ndmsetup create cdata --table \u0026quot;0 65536 linear /dev/sdc 8192\u0026quot;\ndmsetup create corig --table \u0026quot;0 524288 linear /dev/sdc 262144\u0026quot;\ndd if=/dev/urandom of=/dev/mapper/cmeta bs=4k count=1 oflag=direct\ndmsetup create cache --table \u0026quot;0 524288 cache /dev/mapper/cmeta \\\n/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\u0026quot;\n\nKernel logs:\n\n(snip)\nWARNING: CPU: 0 PID: 84 at kernel/workqueue.c:4178 __flush_work+0x5d4/0x890\n\nFix by pulling out the cancel_delayed_work_sync() from the constructor\u0026apos;s\nerror path. This patch doesn\u0026apos;t affect the use-after-free fix for\nconcurrent dm_resume and dm_destroy (commit 6a459d8edbdb (\u0026quot;dm cache: Fix\nUAF in destroy()\u0026quot;)) as cache_dtr is not changed.(CVE-2024-50280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix null-ptr-deref in block_touch_buffer tracepoint\n\nPatch series \u0026quot;nilfs2: fix null-ptr-deref bugs on block tracepoints\u0026quot;.\n\nThis series fixes null pointer dereference bugs that occur when using\nnilfs2 and two block-related tracepoints.\n\n\nThis patch (of 2):\n\nIt has been reported that when using \u0026quot;block:block_touch_buffer\u0026quot;\ntracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a\nNULL pointer dereference, or a general protection fault when KASAN is\nenabled.\n\nThis happens because since the tracepoint was added in touch_buffer(), it\nreferences the dev_t member bh-\u0026gt;b_bdev-\u0026gt;bd_dev regardless of whether the\nbuffer head has a pointer to a block_device structure.  In the current\nimplementation, the block_device structure is set after the function\nreturns to the caller.\n\nHere, touch_buffer() is used to mark the folio/page that owns the buffer\nhead as accessed, but the common search helper for folio/page used by the\ncaller function was optimized to mark the folio/page as accessed when it\nwas reimplemented a long time ago, eliminating the need to call\ntouch_buffer() here in the first place.\n\nSo this solves the issue by eliminating the touch_buffer() call itself.(CVE-2024-53131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: net: Do not use drvdata in release\n\nThe drvdata is not available in release. Let\u0026apos;s just use container_of()\nto get the uml_net instance. Otherwise, removing a network device will\nresult in a crash:\n\nRIP: 0033:net_device_release+0x10/0x6f\nRSP: 00000000e20c7c40  EFLAGS: 00010206\nRAX: 000000006002e4e7 RBX: 00000000600f1baf RCX: 00000000624074e0\nRDX: 0000000062778000 RSI: 0000000060551c80 RDI: 00000000627af028\nRBP: 00000000e20c7c50 R08: 00000000603ad594 R09: 00000000e20c7b70\nR10: 000000000000135a R11: 00000000603ad422 R12: 0000000000000000\nR13: 0000000062c7af00 R14: 0000000062406d60 R15: 00000000627700b6\nKernel panic - not syncing: Segfault with no mm\nCPU: 0 UID: 0 PID: 29 Comm: kworker/0:2 Not tainted 6.12.0-rc6-g59b723cd2adb #1\nWorkqueue: events mc_work_proc\nStack:\n 627af028 62c7af00 e20c7c80 60276fcd\n 62778000 603f5820 627af028 00000000\n e20c7cb0 603a2bcd 627af000 62770010\nCall Trace:\n [\u0026lt;60276fcd\u0026gt;] device_release+0x70/0xba\n [\u0026lt;603a2bcd\u0026gt;] kobject_put+0xba/0xe7\n [\u0026lt;60277265\u0026gt;] put_device+0x19/0x1c\n [\u0026lt;60281266\u0026gt;] platform_device_put+0x26/0x29\n [\u0026lt;60281e5f\u0026gt;] platform_device_unregister+0x2c/0x2e\n [\u0026lt;6002ec9c\u0026gt;] net_remove+0x63/0x69\n [\u0026lt;60031316\u0026gt;] ? mconsole_reply+0x0/0x50\n [\u0026lt;600310c8\u0026gt;] mconsole_remove+0x160/0x1cc\n [\u0026lt;60087d40\u0026gt;] ? __remove_hrtimer+0x38/0x74\n [\u0026lt;60087ff8\u0026gt;] ? hrtimer_try_to_cancel+0x8c/0x98\n [\u0026lt;6006b3cf\u0026gt;] ? dl_server_stop+0x3f/0x48\n [\u0026lt;6006b390\u0026gt;] ? dl_server_stop+0x0/0x48\n [\u0026lt;600672e8\u0026gt;] ? dequeue_entities+0x327/0x390\n [\u0026lt;60038fa6\u0026gt;] ? um_set_signals+0x0/0x43\n [\u0026lt;6003070c\u0026gt;] mc_work_proc+0x77/0x91\n [\u0026lt;60057664\u0026gt;] process_scheduled_works+0x1b3/0x2dd\n [\u0026lt;60055f32\u0026gt;] ? assign_work+0x0/0x58\n [\u0026lt;60057f0a\u0026gt;] worker_thread+0x1e9/0x293\n [\u0026lt;6005406f\u0026gt;] ? set_pf_worker+0x0/0x64\n [\u0026lt;6005d65d\u0026gt;] ? arch_local_irq_save+0x0/0x2d\n [\u0026lt;6005d748\u0026gt;] ? kthread_exit+0x0/0x3a\n [\u0026lt;60057d21\u0026gt;] ? worker_thread+0x0/0x293\n [\u0026lt;6005dbf1\u0026gt;] kthread+0x126/0x12b\n [\u0026lt;600219c5\u0026gt;] new_thread_handler+0x85/0xb6(CVE-2024-53183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen: Fix the issue of resource not being properly released in xenbus_dev_probe()\n\nThis patch fixes an issue in the function xenbus_dev_probe(). In the\nxenbus_dev_probe() function, within the if (err) branch at line 313, the\nprogram incorrectly returns err directly without releasing the resources\nallocated by err = drv-\u0026gt;probe(dev, id). As the return value is non-zero,\nthe upper layers assume the processing logic has failed. However, the probe\noperation was performed earlier without a corresponding remove operation.\nSince the probe actually allocates resources, failing to perform the remove\noperation could lead to problems.\n\nTo fix this issue, we followed the resource release logic of the\nxenbus_dev_remove() function by adding a new block fail_remove before the\nfail_put block. After entering the branch if (err) at line 313, the\nfunction will use a goto statement to jump to the fail_remove block,\nensuring that the previously acquired resources are correctly released,\nthus preventing the reference count leak.\n\nThis bug was identified by an experimental static analysis tool developed\nby our team. The tool specializes in analyzing reference count operations\nand detecting potential issues where resources are not properly managed.\nIn this case, the tool flagged the missing release operation as a\npotential problem, which led to the development of this patch.(CVE-2024-53198)\n\nIn the Linux kernel, the following vulnerability has been resolved:drm/amd/display: Fix null check for pipe_ctx-\u0026gt;plane_state in dcn20_program_pipeThis commit addresses a null pointer dereference issue indcn20_program_pipe(). Previously, commit 8e4ed3cf1642 ( drm/amd/display:Add null check for pipe_ctx-\u0026gt;plane_state in dcn20_program_pipe )partially fixed the null pointer dereference issue. However, indcn20_update_dchubp_dpp(), the variable pipe_ctx is passed in, andplane_state is accessed again through pipe_ctx. Multiple if statementsdirectly call attributes of plane_state, leading to potential nullpointer dereference issues. This patch adds necessary null checks toensure stability.(CVE-2024-53201)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan()\n\nReplace one-element array with a flexible-array member in `struct\nmwifiex_ie_types_wildcard_ssid_params` to fix the following warning\non a MT8173 Chromebook (mt8173-elm-hana):\n\n[  356.775250] ------------[ cut here ]------------\n[  356.784543] memcpy: detected field-spanning write (size 6) of single field \u0026quot;wildcard_ssid_tlv-\u0026gt;ssid\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:904 (size 1)\n[  356.813403] WARNING: CPU: 3 PID: 742 at drivers/net/wireless/marvell/mwifiex/scan.c:904 mwifiex_scan_networks+0x4fc/0xf28 [mwifiex]\n\nThe \u0026quot;(size 6)\u0026quot; above is exactly the length of the SSID of the network\nthis device was connected to. The source of the warning looks like:\n\n    ssid_len = user_scan_in-\u0026gt;ssid_list[i].ssid_len;\n    [...]\n    memcpy(wildcard_ssid_tlv-\u0026gt;ssid,\n           user_scan_in-\u0026gt;ssid_list[i].ssid, ssid_len);\n\nThere is a #define WILDCARD_SSID_TLV_MAX_SIZE that uses sizeof() on this\nstruct, but it already didn\u0026apos;t account for the size of the one-element\narray, so it doesn\u0026apos;t need to be changed.(CVE-2024-56539)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: uvcvideo: Require entities to have a non-zero unique ID\n\nPer UVC 1.1+ specification 3.7.2, units and terminals must have a non-zero\nunique ID.\n\n```\nEach Unit and Terminal within the video function is assigned a unique\nidentification number, the Unit ID (UID) or Terminal ID (TID), contained in\nthe bUnitID or bTerminalID field of the descriptor. The value 0x00 is\nreserved for undefined ID,\n```\n\nSo, deny allocating an entity with ID 0 or an ID that belongs to a unit\nthat is already added to the list of entities.\n\nThis also prevents some syzkaller reproducers from triggering warnings due\nto a chain of entities referring to themselves. In one particular case, an\nOutput Unit is connected to an Input Unit, both with the same ID of 1. But\nwhen looking up for the source ID of the Output Unit, that same entity is\nfound instead of the input entity, which leads to such warnings.\n\nIn another case, a backward chain was considered finished as the source ID\nwas 0. Later on, that entity was found, but its pads were not valid.\n\nHere is a sample stack trace for one of those cases.\n\n[   20.650953] usb 1-1: new high-speed USB device number 2 using dummy_hcd\n[   20.830206] usb 1-1: Using ep0 maxpacket: 8\n[   20.833501] usb 1-1: config 0 descriptor??\n[   21.038518] usb 1-1: string descriptor 0 read error: -71\n[   21.038893] usb 1-1: Found UVC 0.00 device \u0026lt;unnamed\u0026gt; (2833:0201)\n[   21.039299] uvcvideo 1-1:0.0: Entity type for entity Output 1 was not initialized!\n[   21.041583] uvcvideo 1-1:0.0: Entity type for entity Input 1 was not initialized!\n[   21.042218] ------------[ cut here ]------------\n[   21.042536] WARNING: CPU: 0 PID: 9 at drivers/media/mc/mc-entity.c:1147 media_create_pad_link+0x2c4/0x2e0\n[   21.043195] Modules linked in:\n[   21.043535] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.11.0-rc7-00030-g3480e43aeccf #444\n[   21.044101] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\n[   21.044639] Workqueue: usb_hub_wq hub_event\n[   21.045100] RIP: 0010:media_create_pad_link+0x2c4/0x2e0\n[   21.045508] Code: fe e8 20 01 00 00 b8 f4 ff ff ff 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 0f 0b eb e9 0f 0b eb 0a 0f 0b eb 06 \u0026lt;0f\u0026gt; 0b eb 02 0f 0b b8 ea ff ff ff eb d4 66 2e 0f 1f 84 00 00 00 00\n[   21.046801] RSP: 0018:ffffc9000004b318 EFLAGS: 00010246\n[   21.047227] RAX: ffff888004e5d458 RBX: 0000000000000000 RCX: ffffffff818fccf1\n[   21.047719] RDX: 000000000000007b RSI: 0000000000000000 RDI: ffff888004313290\n[   21.048241] RBP: ffff888004313290 R08: 0001ffffffffffff R09: 0000000000000000\n[   21.048701] R10: 0000000000000013 R11: 0001888004313290 R12: 0000000000000003\n[   21.049138] R13: ffff888004313080 R14: ffff888004313080 R15: 0000000000000000\n[   21.049648] FS:  0000000000000000(0000) GS:ffff88803ec00000(0000) knlGS:0000000000000000\n[   21.050271] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   21.050688] CR2: 0000592cc27635b0 CR3: 000000000431c000 CR4: 0000000000750ef0\n[   21.051136] PKRU: 55555554\n[   21.051331] Call Trace:\n[   21.051480]  \u0026lt;TASK\u0026gt;\n[   21.051611]  ? __warn+0xc4/0x210\n[   21.051861]  ? media_create_pad_link+0x2c4/0x2e0\n[   21.052252]  ? report_bug+0x11b/0x1a0\n[   21.052540]  ? trace_hardirqs_on+0x31/0x40\n[   21.052901]  ? handle_bug+0x3d/0x70\n[   21.053197]  ? exc_invalid_op+0x1a/0x50\n[   21.053511]  ? asm_exc_invalid_op+0x1a/0x20\n[   21.053924]  ? media_create_pad_link+0x91/0x2e0\n[   21.054364]  ? media_create_pad_link+0x2c4/0x2e0\n[   21.054834]  ? media_create_pad_link+0x91/0x2e0\n[   21.055131]  ? _raw_spin_unlock+0x1e/0x40\n[   21.055441]  ? __v4l2_device_register_subdev+0x202/0x210\n[   21.055837]  uvc_mc_register_entities+0x358/0x400\n[   21.056144]  uvc_register_chains+0x1fd/0x290\n[   21.056413]  uvc_probe+0x380e/0x3dc0\n[   21.056676]  ? __lock_acquire+0x5aa/0x26e0\n[   21.056946]  ? find_held_lock+0x33/0xa0\n[   21.057196]  ? kernfs_activate+0x70/0x80\n[   21.057533]  ? usb_match_dy\n---truncated---(CVE-2024-56571)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: hisi_sas: Create all dump files during debugfs initialization\n\nFor the current debugfs of hisi_sas, after user triggers dump, the\ndriver allocate memory space to save the register information and create\ndebugfs files to display the saved information. In this process, the\ndebugfs files created after each dump.\n\nTherefore, when the dump is triggered while the driver is unbind, the\nfollowing hang occurs:\n\n[67840.853907] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a0\n[67840.862947] Mem abort info:\n[67840.865855]   ESR = 0x0000000096000004\n[67840.869713]   EC = 0x25: DABT (current EL), IL = 32 bits\n[67840.875125]   SET = 0, FnV = 0\n[67840.878291]   EA = 0, S1PTW = 0\n[67840.881545]   FSC = 0x04: level 0 translation fault\n[67840.886528] Data abort info:\n[67840.889524]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n[67840.895117]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[67840.900284]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[67840.905709] user pgtable: 4k pages, 48-bit VAs, pgdp=0000002803a1f000\n[67840.912263] [00000000000000a0] pgd=0000000000000000, p4d=0000000000000000\n[67840.919177] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP\n[67840.996435] pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[67841.003628] pc : down_write+0x30/0x98\n[67841.007546] lr : start_creating.part.0+0x60/0x198\n[67841.012495] sp : ffff8000b979ba20\n[67841.016046] x29: ffff8000b979ba20 x28: 0000000000000010 x27: 0000000000024b40\n[67841.023412] x26: 0000000000000012 x25: ffff20202b355ae8 x24: ffff20202b35a8c8\n[67841.030779] x23: ffffa36877928208 x22: ffffa368b4972240 x21: ffff8000b979bb18\n[67841.038147] x20: ffff00281dc1e3c0 x19: fffffffffffffffe x18: 0000000000000020\n[67841.045515] x17: 0000000000000000 x16: ffffa368b128a530 x15: ffffffffffffffff\n[67841.052888] x14: ffff8000b979bc18 x13: ffffffffffffffff x12: ffff8000b979bb18\n[67841.060263] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa368b1289b18\n[67841.067640] x8 : 0000000000000012 x7 : 0000000000000000 x6 : 00000000000003a9\n[67841.075014] x5 : 0000000000000000 x4 : ffff002818c5cb00 x3 : 0000000000000001\n[67841.082388] x2 : 0000000000000000 x1 : ffff002818c5cb00 x0 : 00000000000000a0\n[67841.089759] Call trace:\n[67841.092456]  down_write+0x30/0x98\n[67841.096017]  start_creating.part.0+0x60/0x198\n[67841.100613]  debugfs_create_dir+0x48/0x1f8\n[67841.104950]  debugfs_create_files_v3_hw+0x88/0x348 [hisi_sas_v3_hw]\n[67841.111447]  debugfs_snapshot_regs_v3_hw+0x708/0x798 [hisi_sas_v3_hw]\n[67841.118111]  debugfs_trigger_dump_v3_hw_write+0x9c/0x120 [hisi_sas_v3_hw]\n[67841.125115]  full_proxy_write+0x68/0xc8\n[67841.129175]  vfs_write+0xd8/0x3f0\n[67841.132708]  ksys_write+0x70/0x108\n[67841.136317]  __arm64_sys_write+0x24/0x38\n[67841.140440]  invoke_syscall+0x50/0x128\n[67841.144385]  el0_svc_common.constprop.0+0xc8/0xf0\n[67841.149273]  do_el0_svc+0x24/0x38\n[67841.152773]  el0_svc+0x38/0xd8\n[67841.156009]  el0t_64_sync_handler+0xc0/0xc8\n[67841.160361]  el0t_64_sync+0x1a4/0x1a8\n[67841.164189] Code: b9000882 d2800002 d2800023 f9800011 (c85ffc05)\n[67841.170443] ---[ end trace 0000000000000000 ]---\n\nTo fix this issue, create all directories and files during debugfs\ninitialization. In this way, the driver only needs to allocate memory\nspace to save information each time the user triggers dumping.(CVE-2024-56588)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nkcsan: Turn report_filterlist_lock into a raw_spinlock\n\nRan Xiaokai reports that with a KCSAN-enabled PREEMPT_RT kernel, we can see\nsplats like:\n\n| BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\n| in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1\n| preempt_count: 10002, expected: 0\n| RCU nest depth: 0, expected: 0\n| no locks held by swapper/1/0.\n| irq event stamp: 156674\n| hardirqs last  enabled at (156673): [\u0026lt;ffffffff81130bd9\u0026gt;] do_idle+0x1f9/0x240\n| hardirqs last disabled at (156674): [\u0026lt;ffffffff82254f84\u0026gt;] sysvec_apic_timer_interrupt+0x14/0xc0\n| softirqs last  enabled at (0): [\u0026lt;ffffffff81099f47\u0026gt;] copy_process+0xfc7/0x4b60\n| softirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n| Preemption disabled at:\n| [\u0026lt;ffffffff814a3e2a\u0026gt;] paint_ptr+0x2a/0x90\n| CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.11.0+ #3\n| Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org 04/01/2014\n| Call Trace:\n|  \u0026lt;IRQ\u0026gt;\n|  dump_stack_lvl+0x7e/0xc0\n|  dump_stack+0x1d/0x30\n|  __might_resched+0x1a2/0x270\n|  rt_spin_lock+0x68/0x170\n|  kcsan_skip_report_debugfs+0x43/0xe0\n|  print_report+0xb5/0x590\n|  kcsan_report_known_origin+0x1b1/0x1d0\n|  kcsan_setup_watchpoint+0x348/0x650\n|  __tsan_unaligned_write1+0x16d/0x1d0\n|  hrtimer_interrupt+0x3d6/0x430\n|  __sysvec_apic_timer_interrupt+0xe8/0x3a0\n|  sysvec_apic_timer_interrupt+0x97/0xc0\n|  \u0026lt;/IRQ\u0026gt;\n\nOn a detected data race, KCSAN\u0026apos;s reporting logic checks if it should\nfilter the report. That list is protected by the report_filterlist_lock\n*non-raw* spinlock which may sleep on RT kernels.\n\nSince KCSAN may report data races in any context, convert it to a\nraw_spinlock.\n\nThis requires being careful about when to allocate memory for the filter\nlist itself which can be done via KCSAN\u0026apos;s debugfs interface. Concurrent\nmodification of the filter list via debugfs should be rare: the chosen\nstrategy is to optimistically pre-allocate memory before the critical\nsection and discard if unused.(CVE-2024-56610)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM\n\nWe currently assume that there is at least one VMA in a MM, which isn\u0026apos;t\ntrue.\n\nSo we might end up having find_vma() return NULL, to then de-reference\nNULL.  So properly handle find_vma() returning NULL.\n\nThis fixes the report:\n\nOops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\nCPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024\nRIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]\nRIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194\nCode: ...\nRSP: 0018:ffffc9000375fd08 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000\nRDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044\nRBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1\nR10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003\nR13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8\nFS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709\n __do_sys_migrate_pages mm/mempolicy.c:1727 [inline]\n __se_sys_migrate_pages mm/mempolicy.c:1723 [inline]\n __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723\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\n\n[akpm@linux-foundation.org: add unlikely()](CVE-2024-56611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix use after free on unload\n\nSystem crash is observed with stack trace warning of use after\nfree. There are 2 signals to tell dpc_thread to terminate (UNLOADING\nflag and kthread_stop).\n\nOn setting the UNLOADING flag when dpc_thread happens to run at the time\nand sees the flag, this causes dpc_thread to exit and clean up\nitself. When kthread_stop is called for final cleanup, this causes use\nafter free.\n\nRemove UNLOADING signal to terminate dpc_thread.  Use the kthread_stop\nas the main signal to exit dpc_thread.\n\n[596663.812935] kernel BUG at mm/slub.c:294!\n[596663.812950] invalid opcode: 0000 [#1] SMP PTI\n[596663.812957] CPU: 13 PID: 1475935 Comm: rmmod Kdump: loaded Tainted: G          IOE    --------- -  - 4.18.0-240.el8.x86_64 #1\n[596663.812960] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 08/20/2012\n[596663.812974] RIP: 0010:__slab_free+0x17d/0x360\n\n...\n[596663.813008] Call Trace:\n[596663.813022]  ? __dentry_kill+0x121/0x170\n[596663.813030]  ? _cond_resched+0x15/0x30\n[596663.813034]  ? _cond_resched+0x15/0x30\n[596663.813039]  ? wait_for_completion+0x35/0x190\n[596663.813048]  ? try_to_wake_up+0x63/0x540\n[596663.813055]  free_task+0x5a/0x60\n[596663.813061]  kthread_stop+0xf3/0x100\n[596663.813103]  qla2x00_remove_one+0x284/0x440 [qla2xxx](CVE-2024-56623)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport\n\nSince transport-\u0026gt;sock has been set to NULL during reset transport,\nXPRT_SOCK_UPD_TIMEOUT also needs to be cleared. Otherwise, the\nxs_tcp_set_socket_timeouts() may be triggered in xs_tcp_send_request()\nto dereference the transport-\u0026gt;sock that has been set to NULL.(CVE-2024-56688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n9p/xen: fix release of IRQ\n\nKernel logs indicate an IRQ was double-freed.\n\nPass correct device ID during IRQ release.\n\n[Dominique: remove confusing variable reset to 0](CVE-2024-56704)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nionic: Fix netdev notifier unregister on failure\n\nIf register_netdev() fails, then the driver leaks the netdev notifier.\nFix this by calling ionic_lif_unregister() on register_netdev()\nfailure. This will also call ionic_lif_unregister_phc() if it has\nalready been registered.(CVE-2024-56715)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem()\n\nWhen information such as info-\u0026gt;screen_base is not ready, calling\nsh7760fb_free_mem() does not release memory correctly. Call\ndma_free_coherent() instead.(CVE-2024-56746)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix slab-use-after-free due to dangling pointer dqi_priv\n\nWhen mounting ocfs2 and then remounting it as read-only, a\nslab-use-after-free occurs after the user uses a syscall to\nquota_getnextquota.  Specifically, sb_dqinfo(sb, type)-\u0026gt;dqi_priv is the\ndangling pointer.\n\nDuring the remounting process, the pointer dqi_priv is freed but is never\nset as null leaving it to be accessed.  Additionally, the read-only option\nfor remounting sets the DQUOT_SUSPENDED flag instead of setting the\nDQUOT_USAGE_ENABLED flags.  Moreover, later in the process of getting the\nnext quota, the function ocfs2_get_next_id is called and only checks the\nquota usage flags and not the quota suspended flags.\n\nTo fix this, I set dqi_priv to null when it is freed after remounting with\nread-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id.\n\n[akpm@linux-foundation.org: coding-style cleanups](CVE-2024-57892)","status":"published","published":"2025-02-08T11:08:11Z","modified":"2026-08-18T01:18:46.994904196Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2025-1097","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix potencial out-of-bounds when buffer offset is invalid\n\nI found potencial out-of-bounds when buffer offset fields of a few requests\nis invalid. This patch set the minimum value of buffer offset field to\n-\u0026gt;Buffer offset to validate buffer length.(CVE-2024-26952)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()\n\nIf -\u0026gt;NameOffset of smb2_create_req is smaller than Buffer offset of\nsmb2_create_req, slab-out-of-bounds read can happen from smb2_open.\nThis patch set the minimum value of the name offset to the buffer offset\nto validate name length of smb2_create_req().(CVE-2024-26954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfpga: bridge: add owner module and take its refcount\n\nThe current implementation of the fpga bridge assumes that the low-level\nmodule registers a driver for the parent device and uses its owner pointer\nto take the module\u0026apos;s refcount. This approach is problematic since it can\nlead to a null pointer dereference while attempting to get the bridge if\nthe parent device does not have a driver.\n\nTo address this problem, add a module owner pointer to the fpga_bridge\nstruct and use it to take the module\u0026apos;s refcount. Modify the function for\nregistering a bridge to take an additional owner module parameter and\nrename it to avoid conflicts. Use the old function name for a helper macro\nthat automatically sets the module that registers the bridge as the owner.\nThis ensures compatibility with existing low-level control modules and\nreduces the chances of registering a bridge without setting the owner.\n\nAlso, update the documentation to keep it consistent with the new interface\nfor registering an fpga bridge.\n\nOther changes: opportunistically move put_device() from __fpga_bridge_get()\nto fpga_bridge_get() and of_fpga_bridge_get() to improve code clarity since\nthe bridge device is taken in these functions.(CVE-2024-36479)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-iocost: avoid out of bounds shift\n\nUBSAN catches undefined behavior in blk-iocost, where sometimes\niocg-\u0026gt;delay is shifted right by a number that is too large,\nresulting in undefined behavior on some architectures.\n\n[  186.556576] ------------[ cut here ]------------\nUBSAN: shift-out-of-bounds in block/blk-iocost.c:1366:23\nshift exponent 64 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;)\nCPU: 16 PID: 0 Comm: swapper/16 Tainted: G S          E    N 6.9.0-0_fbk700_debug_rc2_kbuilder_0_gc85af715cac0 #1\nHardware name: Quanta Twin Lakes MP/Twin Lakes Passive MP, BIOS F09_3A23 12/08/2020\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x8f/0xe0\n __ubsan_handle_shift_out_of_bounds+0x22c/0x280\n iocg_kick_delay+0x30b/0x310\n ioc_timer_fn+0x2fb/0x1f80\n __run_timer_base+0x1b6/0x250\n...\n\nAvoid that undefined behavior by simply taking the\n\u0026quot;delay = 0\u0026quot; branch if the shift is too large.\n\nI am not sure what the symptoms of an undefined value\ndelay will be, but I suspect it could be more than a\nlittle annoying to debug.(CVE-2024-36916)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfpga: manager: add owner module and take its refcount\n\nThe current implementation of the fpga manager assumes that the low-level\nmodule registers a driver for the parent device and uses its owner pointer\nto take the module\u0026apos;s refcount. This approach is problematic since it can\nlead to a null pointer dereference while attempting to get the manager if\nthe parent device does not have a driver.\n\nTo address this problem, add a module owner pointer to the fpga_manager\nstruct and use it to take the module\u0026apos;s refcount. Modify the functions for\nregistering the manager to take an additional owner module parameter and\nrename them to avoid conflicts. Use the old function names for helper\nmacros that automatically set the module that registers the manager as the\nowner. This ensures compatibility with existing low-level control modules\nand reduces the chances of registering a manager without setting the owner.\n\nAlso, update the documentation to keep it consistent with the new interface\nfor registering an fpga manager.\n\nOther changes: opportunistically move put_device() from __fpga_mgr_get() to\nfpga_mgr_get() and of_fpga_mgr_get() to improve code clarity since the\nmanager device is taken in these functions.(CVE-2024-37021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nthermal/drivers/tsens: Fix null pointer dereference\n\ncompute_intercept_slope() is called from calibrate_8960() (in tsens-8960.c)\nas compute_intercept_slope(priv, p1, NULL, ONE_PT_CALIB) which lead to null\npointer dereference (if DEBUG or DYNAMIC_DEBUG set).\nFix this bug by adding null pointer check.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38571)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcmfmac: pcie: handle randbuf allocation failure\n\nThe kzalloc() in brcmf_pcie_download_fw_nvram() will return null\nif the physical memory has run out. As a result, if we use\nget_random_bytes() to generate random bytes in the randbuf, the\nnull pointer dereference bug will happen.\n\nIn order to prevent allocation failure, this patch adds a separate\nfunction using buffer on kernel stack to generate random bytes in\nthe randbuf, which could prevent the kernel stack from overflow.(CVE-2024-38575)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntools/nolibc/stdlib: fix memory error in realloc()\n\nPass user_p_len to memcpy() instead of heap-\u0026gt;len to prevent realloc()\nfrom copying an extra sizeof(heap) bytes from beyond the allocated\nregion.(CVE-2024-38585)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: stk1160: fix bounds checking in stk1160_copy_video()\n\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.\n\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.\n\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)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmalloc: fix vmalloc which may return null if called with __GFP_NOFAIL\n\ncommit a421ef303008 (\u0026quot;mm: allow !GFP_KERNEL allocations for kvmalloc\u0026quot;)\nincludes support for __GFP_NOFAIL, but it presents a conflict with commit\ndd544141b9eb (\u0026quot;vmalloc: back off when the current task is OOM-killed\u0026quot;).  A\npossible scenario is as follows:\n\nprocess-a\n__vmalloc_node_range(GFP_KERNEL | __GFP_NOFAIL)\n    __vmalloc_area_node()\n        vm_area_alloc_pages()\n\t\t--\u0026gt; oom-killer send SIGKILL to process-a\n        if (fatal_signal_pending(current)) break;\n--\u0026gt; return NULL;\n\nTo fix this, do not check fatal_signal_pending() in vm_area_alloc_pages()\nif __GFP_NOFAIL set.\n\nThis issue occurred during OPLUS KASAN TEST. Below is part of the log\n-\u0026gt; oom-killer sends signal to process\n[65731.222840] [ T1308] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/apps/uid_10198,task=gs.intelligence,pid=32454,uid=10198\n\n[65731.259685] [T32454] Call trace:\n[65731.259698] [T32454]  dump_backtrace+0xf4/0x118\n[65731.259734] [T32454]  show_stack+0x18/0x24\n[65731.259756] [T32454]  dump_stack_lvl+0x60/0x7c\n[65731.259781] [T32454]  dump_stack+0x18/0x38\n[65731.259800] [T32454]  mrdump_common_die+0x250/0x39c [mrdump]\n[65731.259936] [T32454]  ipanic_die+0x20/0x34 [mrdump]\n[65731.260019] [T32454]  atomic_notifier_call_chain+0xb4/0xfc\n[65731.260047] [T32454]  notify_die+0x114/0x198\n[65731.260073] [T32454]  die+0xf4/0x5b4\n[65731.260098] [T32454]  die_kernel_fault+0x80/0x98\n[65731.260124] [T32454]  __do_kernel_fault+0x160/0x2a8\n[65731.260146] [T32454]  do_bad_area+0x68/0x148\n[65731.260174] [T32454]  do_mem_abort+0x151c/0x1b34\n[65731.260204] [T32454]  el1_abort+0x3c/0x5c\n[65731.260227] [T32454]  el1h_64_sync_handler+0x54/0x90\n[65731.260248] [T32454]  el1h_64_sync+0x68/0x6c\n\n[65731.260269] [T32454]  z_erofs_decompress_queue+0x7f0/0x2258\n--\u0026gt; be-\u0026gt;decompressed_pages = kvcalloc(be-\u0026gt;nr_pages, sizeof(struct page *), GFP_KERNEL | __GFP_NOFAIL);\n\tkernel panic by NULL pointer dereference.\n\terofs assume kvmalloc with __GFP_NOFAIL never return NULL.\n[65731.260293] [T32454]  z_erofs_runqueue+0xf30/0x104c\n[65731.260314] [T32454]  z_erofs_readahead+0x4f0/0x968\n[65731.260339] [T32454]  read_pages+0x170/0xadc\n[65731.260364] [T32454]  page_cache_ra_unbounded+0x874/0xf30\n[65731.260388] [T32454]  page_cache_ra_order+0x24c/0x714\n[65731.260411] [T32454]  filemap_fault+0xbf0/0x1a74\n[65731.260437] [T32454]  __do_fault+0xd0/0x33c\n[65731.260462] [T32454]  handle_mm_fault+0xf74/0x3fe0\n[65731.260486] [T32454]  do_mem_abort+0x54c/0x1b34\n[65731.260509] [T32454]  el0_da+0x44/0x94\n[65731.260531] [T32454]  el0t_64_sync_handler+0x98/0xb4\n[65731.260553] [T32454]  el0t_64_sync+0x198/0x19c(CVE-2024-39474)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbcache: fix variable length array abuse in btree_iter\n\nbtree_iter is used in two ways: either allocated on the stack with a\nfixed size MAX_BSETS, or from a mempool with a dynamic size based on the\nspecific cache set. Previously, the struct had a fixed-length array of\nsize MAX_BSETS which was indexed out-of-bounds for the dynamically-sized\niterators, which causes UBSAN to complain.\n\nThis patch uses the same approach as in bcachefs\u0026apos;s sort_iter and splits\nthe iterator into a btree_iter with a flexible array member and a\nbtree_iter_stack which embeds a btree_iter as well as a fixed-length\ndata array.(CVE-2024-39482)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngreybus: Fix use-after-free bug in gb_interface_release due to race condition.\n\nIn gb_interface_create, \u0026amp;intf-\u0026gt;mode_switch_completion is bound with\ngb_interface_mode_switch_work. Then it will be started by\ngb_interface_request_mode_switch. Here is the relevant code.\nif (!queue_work(system_long_wq, \u0026amp;intf-\u0026gt;mode_switch_work)) {\n\t...\n}\n\nIf we call gb_interface_release to make cleanup, there may be an\nunfinished work. This function will call kfree to free the object\n\u0026quot;intf\u0026quot;. However, if gb_interface_mode_switch_work is scheduled to\nrun after kfree, it may cause use-after-free error as\ngb_interface_mode_switch_work will use the object \u0026quot;intf\u0026quot;.\nThe possible execution flow that may lead to the issue is as follows:\n\nCPU0                            CPU1\n\n                            |   gb_interface_create\n                            |   gb_interface_request_mode_switch\ngb_interface_release        |\nkfree(intf) (free)          |\n                            |   gb_interface_mode_switch_work\n                            |   mutex_lock(\u0026amp;intf-\u0026gt;mutex) (use)\n\nFix it by canceling the work before kfree.(CVE-2024-39495)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/dpt: Make DPT object unshrinkable\n\nIn some scenarios, the DPT object gets shrunk but\nthe actual framebuffer did not and thus its still\nthere on the DPT\u0026apos;s vm-\u0026gt;bound_list. Then it tries to\nrewrite the PTEs via a stale CPU mapping. This causes panic.\n\n[vsyrjala: Add TODO comment]\n(cherry picked from commit 51064d471c53dcc8eddd2333c3f1c1d9131ba36c)(CVE-2024-40924)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngve: Clear napi-\u0026gt;skb before dev_kfree_skb_any()\n\ngve_rx_free_skb incorrectly leaves napi-\u0026gt;skb referencing an skb after it\nis freed with dev_kfree_skb_any(). This can result in a subsequent call\nto napi_get_frags returning a dangling pointer.\n\nFix this by clearing napi-\u0026gt;skb before the skb is freed.(CVE-2024-40937)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: shmem: fix getting incorrect lruvec when replacing a shmem folio\n\nWhen testing shmem swapin, I encountered the warning below on my machine. \nThe reason is that replacing an old shmem folio with a new one causes\nmem_cgroup_migrate() to clear the old folio\u0026apos;s memcg data.  As a result,\nthe old folio cannot get the correct memcg\u0026apos;s lruvec needed to remove\nitself from the LRU list when it is being freed.  This could lead to\npossible serious problems, such as LRU list crashes due to holding the\nwrong LRU lock, and incorrect LRU statistics.\n\nTo fix this issue, we can fallback to use the mem_cgroup_replace_folio()\nto replace the old shmem folio.\n\n[ 5241.100311] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x5d9960\n[ 5241.100317] head: order:4 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0\n[ 5241.100319] flags: 0x17fffe0000040068(uptodate|lru|head|swapbacked|node=0|zone=2|lastcpupid=0x3ffff)\n[ 5241.100323] raw: 17fffe0000040068 fffffdffd6687948 fffffdffd69ae008 0000000000000000\n[ 5241.100325] raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000\n[ 5241.100326] head: 17fffe0000040068 fffffdffd6687948 fffffdffd69ae008 0000000000000000\n[ 5241.100327] head: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000\n[ 5241.100328] head: 17fffe0000000204 fffffdffd6665801 ffffffffffffffff 0000000000000000\n[ 5241.100329] head: 0000000a00000010 0000000000000000 00000000ffffffff 0000000000000000\n[ 5241.100330] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg \u0026amp;\u0026amp; !mem_cgroup_disabled())\n[ 5241.100338] ------------[ cut here ]------------\n[ 5241.100339] WARNING: CPU: 19 PID: 78402 at include/linux/memcontrol.h:775 folio_lruvec_lock_irqsave+0x140/0x150\n[...]\n[ 5241.100374] pc : folio_lruvec_lock_irqsave+0x140/0x150\n[ 5241.100375] lr : folio_lruvec_lock_irqsave+0x138/0x150\n[ 5241.100376] sp : ffff80008b38b930\n[...]\n[ 5241.100398] Call trace:\n[ 5241.100399]  folio_lruvec_lock_irqsave+0x140/0x150\n[ 5241.100401]  __page_cache_release+0x90/0x300\n[ 5241.100404]  __folio_put+0x50/0x108\n[ 5241.100406]  shmem_replace_folio+0x1b4/0x240\n[ 5241.100409]  shmem_swapin_folio+0x314/0x528\n[ 5241.100411]  shmem_get_folio_gfp+0x3b4/0x930\n[ 5241.100412]  shmem_fault+0x74/0x160\n[ 5241.100414]  __do_fault+0x40/0x218\n[ 5241.100417]  do_shared_fault+0x34/0x1b0\n[ 5241.100419]  do_fault+0x40/0x168\n[ 5241.100420]  handle_pte_fault+0x80/0x228\n[ 5241.100422]  __handle_mm_fault+0x1c4/0x440\n[ 5241.100424]  handle_mm_fault+0x60/0x1f0\n[ 5241.100426]  do_page_fault+0x120/0x488\n[ 5241.100429]  do_translation_fault+0x4c/0x68\n[ 5241.100431]  do_mem_abort+0x48/0xa0\n[ 5241.100434]  el0_da+0x38/0xc0\n[ 5241.100436]  el0t_64_sync_handler+0x68/0xc0\n[ 5241.100437]  el0t_64_sync+0x14c/0x150\n[ 5241.100439] ---[ end trace 0000000000000000 ]---\n\n[baolin.wang@linux.alibaba.com: remove less helpful comments, per Matthew]\n  Link: https://lkml.kernel.org/r/ccad3fe1375b468ebca3227b6b729f3eaf9d8046.1718423197.git.baolin.wang@linux.alibaba.com(CVE-2024-40949)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: prevent possible NULL deref in fib6_nh_init()\n\nsyzbot reminds us that in6_dev_get() can return NULL.\n\nfib6_nh_init()\n    ip6_validate_gw(  \u0026amp;idev  )\n        ip6_route_check_nh(  idev  )\n            *idev = in6_dev_get(dev); // can be NULL\n\nOops: general protection fault, probably for non-canonical address 0xdffffc00000000bc: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x00000000000005e0-0x00000000000005e7]\nCPU: 0 PID: 11237 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00249-gbe27b8965297 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024\n RIP: 0010:fib6_nh_init+0x640/0x2160 net/ipv6/route.c:3606\nCode: 00 00 fc ff df 4c 8b 64 24 58 48 8b 44 24 28 4c 8b 74 24 30 48 89 c1 48 89 44 24 28 48 8d 98 e0 05 00 00 48 89 d8 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 38 84 c0 0f 85 b3 17 00 00 8b 1b 31 ff 89 de e8 b8 8b\nRSP: 0018:ffffc900032775a0 EFLAGS: 00010202\nRAX: 00000000000000bc RBX: 00000000000005e0 RCX: 0000000000000000\nRDX: 0000000000000010 RSI: ffffc90003277a54 RDI: ffff88802b3a08d8\nRBP: ffffc900032778b0 R08: 00000000000002fc R09: 0000000000000000\nR10: 00000000000002fc R11: 0000000000000000 R12: ffff88802b3a08b8\nR13: 1ffff9200064eec8 R14: ffffc90003277a00 R15: dffffc0000000000\nFS:  00007f940feb06c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 00000000245e8000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  ip6_route_info_create+0x99e/0x12b0 net/ipv6/route.c:3809\n  ip6_route_add+0x28/0x160 net/ipv6/route.c:3853\n  ipv6_route_ioctl+0x588/0x870 net/ipv6/route.c:4483\n  inet6_ioctl+0x21a/0x280 net/ipv6/af_inet6.c:579\n  sock_do_ioctl+0x158/0x460 net/socket.c:1222\n  sock_ioctl+0x629/0x8e0 net/socket.c:1341\n  vfs_ioctl fs/ioctl.c:51 [inline]\n  __do_sys_ioctl fs/ioctl.c:907 [inline]\n  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f940f07cea9(CVE-2024-40961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.(CVE-2024-40965)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Disassociate vcpus from redistributor region on teardown\n\nWhen tearing down a redistributor region, make sure we don\u0026apos;t have\nany dangling pointer to that region stored in a vcpu.(CVE-2024-40989)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/sqpoll: work around a potential audit memory leak\n\nkmemleak complains that there\u0026apos;s a memory leak related to connect\nhandling:\n\nunreferenced object 0xffff0001093bdf00 (size 128):\ncomm \u0026quot;iou-sqp-455\u0026quot;, pid 457, jiffies 4294894164\nhex dump (first 32 bytes):\n02 00 fa ea 7f 00 00 01 00 00 00 00 00 00 00 00  ................\n00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nbacktrace (crc 2e481b1a):\n[\u0026lt;00000000c0a26af4\u0026gt;] kmemleak_alloc+0x30/0x38\n[\u0026lt;000000009c30bb45\u0026gt;] kmalloc_trace+0x228/0x358\n[\u0026lt;000000009da9d39f\u0026gt;] __audit_sockaddr+0xd0/0x138\n[\u0026lt;0000000089a93e34\u0026gt;] move_addr_to_kernel+0x1a0/0x1f8\n[\u0026lt;000000000b4e80e6\u0026gt;] io_connect_prep+0x1ec/0x2d4\n[\u0026lt;00000000abfbcd99\u0026gt;] io_submit_sqes+0x588/0x1e48\n[\u0026lt;00000000e7c25e07\u0026gt;] io_sq_thread+0x8a4/0x10e4\n[\u0026lt;00000000d999b491\u0026gt;] ret_from_fork+0x10/0x20\n\nwhich can can happen if:\n\n1) The command type does something on the prep side that triggers an\n   audit call.\n2) The thread hasn\u0026apos;t done any operations before this that triggered\n   an audit call inside -\u0026gt;issue(), where we have audit_uring_entry()\n   and audit_uring_exit().\n\nWork around this by issuing a blanket NOP operation before the SQPOLL\ndoes anything.(CVE-2024-41001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: vmalloc: check if a hash-index is in cpu_possible_mask\n\nThe problem is that there are systems where cpu_possible_mask has gaps\nbetween set CPUs, for example SPARC.  In this scenario addr_to_vb_xa()\nhash function can return an index which accesses to not-possible and not\nsetup CPU area using per_cpu() macro.  This results in an oops on SPARC.\n\nA per-cpu vmap_block_queue is also used as hash table, incorrectly\nassuming the cpu_possible_mask has no gaps.  Fix it by adjusting an index\nto a next possible CPU.(CVE-2024-41032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx()\n\nThe following is emitted when using idxd (DSA) dmanegine as the data\nmover for ntb_transport that ntb_netdev uses.\n\n[74412.546922] BUG: using smp_processor_id() in preemptible [00000000] code: irq/52-idxd-por/14526\n[74412.556784] caller is netif_rx_internal+0x42/0x130\n[74412.562282] CPU: 6 PID: 14526 Comm: irq/52-idxd-por Not tainted 6.9.5 #5\n[74412.569870] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.E9I.1752.P05.2402080856 02/08/2024\n[74412.581699] Call Trace:\n[74412.584514]  \u0026lt;TASK\u0026gt;\n[74412.586933]  dump_stack_lvl+0x55/0x70\n[74412.591129]  check_preemption_disabled+0xc8/0xf0\n[74412.596374]  netif_rx_internal+0x42/0x130\n[74412.600957]  __netif_rx+0x20/0xd0\n[74412.604743]  ntb_netdev_rx_handler+0x66/0x150 [ntb_netdev]\n[74412.610985]  ntb_complete_rxc+0xed/0x140 [ntb_transport]\n[74412.617010]  ntb_rx_copy_callback+0x53/0x80 [ntb_transport]\n[74412.623332]  idxd_dma_complete_txd+0xe3/0x160 [idxd]\n[74412.628963]  idxd_wq_thread+0x1a6/0x2b0 [idxd]\n[74412.634046]  irq_thread_fn+0x21/0x60\n[74412.638134]  ? irq_thread+0xa8/0x290\n[74412.642218]  irq_thread+0x1a0/0x290\n[74412.646212]  ? __pfx_irq_thread_fn+0x10/0x10\n[74412.651071]  ? __pfx_irq_thread_dtor+0x10/0x10\n[74412.656117]  ? __pfx_irq_thread+0x10/0x10\n[74412.660686]  kthread+0x100/0x130\n[74412.664384]  ? __pfx_kthread+0x10/0x10\n[74412.668639]  ret_from_fork+0x31/0x50\n[74412.672716]  ? __pfx_kthread+0x10/0x10\n[74412.676978]  ret_from_fork_asm+0x1a/0x30\n[74412.681457]  \u0026lt;/TASK\u0026gt;\n\nThe cause is due to the idxd driver interrupt completion handler uses\nthreaded interrupt and the threaded handler is not hard or soft interrupt\ncontext. However __netif_rx() can only be called from interrupt context.\nChange the call to netif_rx() in order to allow completion via normal\ncontext for dmaengine drivers that utilize threaded irq handling.\n\nWhile the following commit changed from netif_rx() to __netif_rx(),\nbaebdf48c360 (\u0026quot;net: dev: Makes sure netif_rx() can be invoked in any context.\u0026quot;),\nthe change should\u0026apos;ve been a noop instead. However, the code precedes this\nfix should\u0026apos;ve been using netif_rx_ni() or netif_rx_any_context().(CVE-2024-42110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: page_ref: remove folio_try_get_rcu()\n\nThe below bug was reported on a non-SMP kernel:\n\n[  275.267158][ T4335] ------------[ cut here ]------------\n[  275.267949][ T4335] kernel BUG at include/linux/page_ref.h:275!\n[  275.268526][ T4335] invalid opcode: 0000 [#1] KASAN PTI\n[  275.269001][ T4335] CPU: 0 PID: 4335 Comm: trinity-c3 Not tainted 6.7.0-rc4-00061-gefa7df3e3bb5 #1\n[  275.269787][ T4335] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014\n[  275.270679][ T4335] RIP: 0010:try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))\n[  275.272813][ T4335] RSP: 0018:ffffc90005dcf650 EFLAGS: 00010202\n[  275.273346][ T4335] RAX: 0000000000000246 RBX: ffffea00066e0000 RCX: 0000000000000000\n[  275.274032][ T4335] RDX: fffff94000cdc007 RSI: 0000000000000004 RDI: ffffea00066e0034\n[  275.274719][ T4335] RBP: ffffea00066e0000 R08: 0000000000000000 R09: fffff94000cdc006\n[  275.275404][ T4335] R10: ffffea00066e0037 R11: 0000000000000000 R12: 0000000000000136\n[  275.276106][ T4335] R13: ffffea00066e0034 R14: dffffc0000000000 R15: ffffea00066e0008\n[  275.276790][ T4335] FS:  00007fa2f9b61740(0000) GS:ffffffff89d0d000(0000) knlGS:0000000000000000\n[  275.277570][ T4335] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  275.278143][ T4335] CR2: 00007fa2f6c00000 CR3: 0000000134b04000 CR4: 00000000000406f0\n[  275.278833][ T4335] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[  275.279521][ T4335] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[  275.280201][ T4335] Call Trace:\n[  275.280499][ T4335]  \u0026lt;TASK\u0026gt;\n[ 275.280751][ T4335] ? die (arch/x86/kernel/dumpstack.c:421 arch/x86/kernel/dumpstack.c:434 arch/x86/kernel/dumpstack.c:447)\n[ 275.281087][ T4335] ? do_trap (arch/x86/kernel/traps.c:112 arch/x86/kernel/traps.c:153)\n[ 275.281463][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))\n[ 275.281884][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))\n[ 275.282300][ T4335] ? do_error_trap (arch/x86/kernel/traps.c:174)\n[ 275.282711][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))\n[ 275.283129][ T4335] ? handle_invalid_op (arch/x86/kernel/traps.c:212)\n[ 275.283561][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))\n[ 275.283990][ T4335] ? exc_invalid_op (arch/x86/kernel/traps.c:264)\n[ 275.284415][ T4335] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:568)\n[ 275.284859][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))\n[ 275.285278][ T4335] try_grab_folio (mm/gup.c:148)\n[ 275.285684][ T4335] __get_user_pages (mm/gup.c:1297 (discriminator 1))\n[ 275.286111][ T4335] ? __pfx___get_user_pages (mm/gup.c:1188)\n[ 275.286579][ T4335] ? __pfx_validate_chain (kernel/locking/lockdep.c:3825)\n[ 275.287034][ T4335] ? mark_lock (kernel/locking/lockdep.c:4656 (discriminator 1))\n[ 275.287416][ T4335] __gup_longterm_locked (mm/gup.c:1509 mm/gup.c:2209)\n[ 275.288192][ T4335] ? __pfx___gup_longterm_locked (mm/gup.c:2204)\n[ 275.288697][ T4335] ? __pfx_lock_acquire (kernel/locking/lockdep.c:5722)\n[ 275.289135][ T4335] ? __pfx___might_resched (kernel/sched/core.c:10106)\n[ 275.289595][ T4335] pin_user_pages_remote (mm/gup.c:3350)\n[ 275.290041][ T4335] ? __pfx_pin_user_pages_remote (mm/gup.c:3350)\n[ 275.290545][ T4335] ? find_held_lock (kernel/locking/lockdep.c:5244 (discriminator 1))\n[ 275.290961][ T4335] ? mm_access (kernel/fork.c:1573)\n[ 275.291353][ T4335] process_vm_rw_single_vec+0x142/0x360\n[ 275.291900][ T4335] ? __pfx_process_vm_rw_single_vec+0x10/0x10\n[ 275.292471][ T4335] ? mm_access (kernel/fork.c:1573)\n[ 275.292859][ T4335] process_vm_rw_core+0x272/0x4e0\n[ 275.293384][ T4335] ? hlock_class (a\n---truncated---(CVE-2024-42251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix null reference error when checking end of zone\n\nThis patch fixes a potentially null pointer being accessed by\nis_end_zone_blkaddr() that checks the last block of a zone\nwhen f2fs is mounted as a single device.(CVE-2024-43857)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix event leak upon exit\n\nWhen a task is scheduled out, pending sigtrap deliveries are deferred\nto the target task upon resume to userspace via task_work.\n\nHowever failures while adding an event\u0026apos;s callback to the task_work\nengine are ignored. And since the last call for events exit happen\nafter task work is eventually closed, there is a small window during\nwhich pending sigtrap can be queued though ignored, leaking the event\nrefcount addition such as in the following scenario:\n\n    TASK A\n    -----\n\n    do_exit()\n       exit_task_work(tsk);\n\n       \u0026lt;IRQ\u0026gt;\n       perf_event_overflow()\n          event-\u0026gt;pending_sigtrap = pending_id;\n          irq_work_queue(\u0026amp;event-\u0026gt;pending_irq);\n       \u0026lt;/IRQ\u0026gt;\n    =========\u0026gt; PREEMPTION: TASK A -\u0026gt; TASK B\n       event_sched_out()\n          event-\u0026gt;pending_sigtrap = 0;\n          atomic_long_inc_not_zero(\u0026amp;event-\u0026gt;refcount)\n          // FAILS: task work has exited\n          task_work_add(\u0026amp;event-\u0026gt;pending_task)\n       [...]\n       \u0026lt;IRQ WORK\u0026gt;\n       perf_pending_irq()\n          // early return: event-\u0026gt;oncpu = -1\n       \u0026lt;/IRQ WORK\u0026gt;\n       [...]\n    =========\u0026gt; TASK B -\u0026gt; TASK A\n       perf_event_exit_task(tsk)\n          perf_event_exit_event()\n             free_event()\n                WARN(atomic_long_cmpxchg(\u0026amp;event-\u0026gt;refcount, 1, 0) != 1)\n                // leak event due to unexpected refcount == 2\n\nAs a result the event is never released while the task exits.\n\nFix this with appropriate task_work_add()\u0026apos;s error handling.(CVE-2024-43870)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: endpoint: Clean up error handling in vpci_scan_bus()\n\nSmatch complains about inconsistent NULL checking in vpci_scan_bus():\n\n    drivers/pci/endpoint/functions/pci-epf-vntb.c:1024 vpci_scan_bus() error: we previously assumed \u0026apos;vpci_bus\u0026apos; could be null (see line 1021)\n\nInstead of printing an error message and then crashing we should return\nan error code and clean up.\n\nAlso the NULL check is reversed so it prints an error for success\ninstead of failure.(CVE-2024-43875)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: rcar: Demote WARN() to dev_warn_ratelimited() in rcar_pcie_wakeup()\n\nAvoid large backtrace, it is sufficient to warn the user that there has\nbeen a link problem. Either the link has failed and the system is in need\nof maintenance, or the link continues to work and user has been informed.\nThe message from the warning can be looked up in the sources.\n\nThis makes an actual link issue less verbose.\n\nFirst of all, this controller has a limitation in that the controller\ndriver has to assist the hardware with transition to L1 link state by\nwriting L1IATN to PMCTRL register, the L1 and L0 link state switching\nis not fully automatic on this controller.\n\nIn case of an ASMedia ASM1062 PCIe SATA controller which does not support\nASPM, on entry to suspend or during platform pm_test, the SATA controller\nenters D3hot state and the link enters L1 state. If the SATA controller\nwakes up before rcar_pcie_wakeup() was called and returns to D0, the link\nreturns to L0 before the controller driver even started its transition to\nL1 link state. At this point, the SATA controller did send an PM_ENTER_L1\nDLLP to the PCIe controller and the PCIe controller received it, and the\nPCIe controller did set PMSR PMEL1RX bit.\n\nOnce rcar_pcie_wakeup() is called, if the link is already back in L0 state\nand PMEL1RX bit is set, the controller driver has no way to determine if\nit should perform the link transition to L1 state, or treat the link as if\nit is in L0 state. Currently the driver attempts to perform the transition\nto L1 link state unconditionally, which in this specific case fails with a\nPMSR L1FAEG poll timeout, however the link still works as it is already\nback in L0 state.\n\nReduce this warning verbosity. In case the link is really broken, the\nrcar_pcie_config_access() would fail, otherwise it will succeed and any\nsystem with this controller and ASM1062 can suspend without generating\na backtrace.(CVE-2024-43876)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: pci: ivtv: Add check for DMA map result\n\nIn case DMA fails, \u0026apos;dma-\u0026gt;SG_length\u0026apos; is 0. This value is later used to\naccess \u0026apos;dma-\u0026gt;SGarray[dma-\u0026gt;SG_length - 1]\u0026apos;, which will cause out of\nbounds access.\n\nAdd check to return early on invalid value. Adjust warnings accordingly.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-43877)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_acl_erp: Fix object nesting warning\n\nACLs in Spectrum-2 and newer ASICs can reside in the algorithmic TCAM\n(A-TCAM) or in the ordinary circuit TCAM (C-TCAM). The former can\ncontain more ACLs (i.e., tc filters), but the number of masks in each\nregion (i.e., tc chain) is limited.\n\nIn order to mitigate the effects of the above limitation, the device\nallows filters to share a single mask if their masks only differ in up\nto 8 consecutive bits. For example, dst_ip/25 can be represented using\ndst_ip/24 with a delta of 1 bit. The C-TCAM does not have a limit on the\nnumber of masks being used (and therefore does not support mask\naggregation), but can contain a limited number of filters.\n\nThe driver uses the \u0026quot;objagg\u0026quot; library to perform the mask aggregation by\npassing it objects that consist of the filter\u0026apos;s mask and whether the\nfilter is to be inserted into the A-TCAM or the C-TCAM since filters in\ndifferent TCAMs cannot share a mask.\n\nThe set of created objects is dependent on the insertion order of the\nfilters and is not necessarily optimal. Therefore, the driver will\nperiodically ask the library to compute a more optimal set (\u0026quot;hints\u0026quot;) by\nlooking at all the existing objects.\n\nWhen the library asks the driver whether two objects can be aggregated\nthe driver only compares the provided masks and ignores the A-TCAM /\nC-TCAM indication. This is the right thing to do since the goal is to\nmove as many filters as possible to the A-TCAM. The driver also forbids\ntwo identical masks from being aggregated since this can only happen if\none was intentionally put in the C-TCAM to avoid a conflict in the\nA-TCAM.\n\nThe above can result in the following set of hints:\n\nH1: {mask X, A-TCAM} -\u0026gt; H2: {mask Y, A-TCAM} // X is Y + delta\nH3: {mask Y, C-TCAM} -\u0026gt; H4: {mask Z, A-TCAM} // Y is Z + delta\n\nAfter getting the hints from the library the driver will start migrating\nfilters from one region to another while consulting the computed hints\nand instructing the device to perform a lookup in both regions during\nthe transition.\n\nAssuming a filter with mask X is being migrated into the A-TCAM in the\nnew region, the hints lookup will return H1. Since H2 is the parent of\nH1, the library will try to find the object associated with it and\ncreate it if necessary in which case another hints lookup (recursive)\nwill be performed. This hints lookup for {mask Y, A-TCAM} will either\nreturn H2 or H3 since the driver passes the library an object comparison\nfunction that ignores the A-TCAM / C-TCAM indication.\n\nThis can eventually lead to nested objects which are not supported by\nthe library [1].\n\nFix by removing the object comparison function from both the driver and\nthe library as the driver was the only user. That way the lookup will\nonly return exact matches.\n\nI do not have a reliable reproducer that can reproduce the issue in a\ntimely manner, but before the fix the issue would reproduce in several\nminutes and with the fix it does not reproduce in over an hour.\n\nNote that the current usefulness of the hints is limited because they\ninclude the C-TCAM indication and represent aggregation that cannot\nactually happen. This will be addressed in net-next.\n\n[1]\nWARNING: CPU: 0 PID: 153 at lib/objagg.c:170 objagg_obj_parent_assign+0xb5/0xd0\nModules linked in:\nCPU: 0 PID: 153 Comm: kworker/0:18 Not tainted 6.9.0-rc6-custom-g70fbc2c1c38b #42\nHardware name: Mellanox Technologies Ltd. MSN3700C/VMOD0008, BIOS 5.11 10/10/2018\nWorkqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work\nRIP: 0010:objagg_obj_parent_assign+0xb5/0xd0\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __objagg_obj_get+0x2bb/0x580\n objagg_obj_get+0xe/0x80\n mlxsw_sp_acl_erp_mask_get+0xb5/0xf0\n mlxsw_sp_acl_atcam_entry_add+0xe8/0x3c0\n mlxsw_sp_acl_tcam_entry_create+0x5e/0xa0\n mlxsw_sp_acl_tcam_vchunk_migrate_one+0x16b/0x270\n mlxsw_sp_acl_tcam_vregion_rehash_work+0xbe/0x510\n process_one_work+0x151/0x370(CVE-2024-43880)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: change DMA direction while mapping reinjected packets\n\nFor fragmented packets, ath12k reassembles each fragment as a normal\npacket and then reinjects it into HW ring. In this case, the DMA\ndirection should be DMA_TO_DEVICE, not DMA_FROM_DEVICE. Otherwise,\nan invalid payload may be reinjected into the HW and\nsubsequently delivered to the host.\n\nGiven that arbitrary memory can be allocated to the skb buffer,\nknowledge about the data contained in the reinjected buffer is lacking.\nConsequently, there’s a risk of private information being leaked.\n\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.1.1-00209-QCAHKSWPL_SILICONZ-1(CVE-2024-43881)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen: privcmd: Switch from mutex to spinlock for irqfds\n\nirqfd_wakeup() gets EPOLLHUP, when it is called by\neventfd_release() by way of wake_up_poll(\u0026amp;ctx-\u0026gt;wqh, EPOLLHUP), which\ngets called under spin_lock_irqsave(). We can\u0026apos;t use a mutex here as it\nwill lead to a deadlock.\n\nFix it by switching over to a spin lock.(CVE-2024-44957)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntick/broadcast: Move per CPU pointer access into the atomic section\n\nThe recent fix for making the take over of the broadcast timer more\nreliable retrieves a per CPU pointer in preemptible context.\n\nThis went unnoticed as compilers hoist the access into the non-preemptible\nregion where the pointer is actually used. But of course it\u0026apos;s valid that\nthe compiler keeps it at the place where the code puts it which rightfully\ntriggers:\n\n  BUG: using smp_processor_id() in preemptible [00000000] code:\n       caller is hotplug_cpu__broadcast_tick_pull+0x1c/0xc0\n\nMove it to the actual usage site which is in a non-preemptible region.(CVE-2024-44968)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: do not clear page dirty inside extent_write_locked_range()\n\n[BUG]\nFor subpage + zoned case, the following workload can lead to rsv data\nleak at unmount time:\n\n  # mkfs.btrfs -f -s 4k $dev\n  # mount $dev $mnt\n  # fsstress -w -n 8 -d $mnt -s 1709539240\n  0/0: fiemap - no filename\n  0/1: copyrange read - no filename\n  0/2: write - no filename\n  0/3: rename - no source filename\n  0/4: creat f0 x:0 0 0\n  0/4: creat add id=0,parent=-1\n  0/5: writev f0[259 1 0 0 0 0] [778052,113,965] 0\n  0/6: ioctl(FIEMAP) f0[259 1 0 0 224 887097] [1294220,2291618343991484791,0x10000] -1\n  0/7: dwrite - xfsctl(XFS_IOC_DIOINFO) f0[259 1 0 0 224 887097] return 25, fallback to stat()\n  0/7: dwrite f0[259 1 0 0 224 887097] [696320,102400] 0\n  # umount $mnt\n\nThe dmesg includes the following rsv leak detection warning (all call\ntrace skipped):\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 2 PID: 4528 at fs/btrfs/inode.c:8653 btrfs_destroy_inode+0x1e0/0x200 [btrfs]\n  ---[ end trace 0000000000000000 ]---\n  ------------[ cut here ]------------\n  WARNING: CPU: 2 PID: 4528 at fs/btrfs/inode.c:8654 btrfs_destroy_inode+0x1a8/0x200 [btrfs]\n  ---[ end trace 0000000000000000 ]---\n  ------------[ cut here ]------------\n  WARNING: CPU: 2 PID: 4528 at fs/btrfs/inode.c:8660 btrfs_destroy_inode+0x1a0/0x200 [btrfs]\n  ---[ end trace 0000000000000000 ]---\n  BTRFS info (device sda): last unmount of filesystem 1b4abba9-de34-4f07-9e7f-157cf12a18d6\n  ------------[ cut here ]------------\n  WARNING: CPU: 3 PID: 4528 at fs/btrfs/block-group.c:4434 btrfs_free_block_groups+0x338/0x500 [btrfs]\n  ---[ end trace 0000000000000000 ]---\n  BTRFS info (device sda): space_info DATA has 268218368 free, is not full\n  BTRFS info (device sda): space_info total=268435456, used=204800, pinned=0, reserved=0, may_use=12288, readonly=0 zone_unusable=0\n  BTRFS info (device sda): global_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): trans_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): chunk_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): delayed_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): delayed_refs_rsv: size 0 reserved 0\n  ------------[ cut here ]------------\n  WARNING: CPU: 3 PID: 4528 at fs/btrfs/block-group.c:4434 btrfs_free_block_groups+0x338/0x500 [btrfs]\n  ---[ end trace 0000000000000000 ]---\n  BTRFS info (device sda): space_info METADATA has 267796480 free, is not full\n  BTRFS info (device sda): space_info total=268435456, used=131072, pinned=0, reserved=0, may_use=262144, readonly=0 zone_unusable=245760\n  BTRFS info (device sda): global_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): trans_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): chunk_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): delayed_block_rsv: size 0 reserved 0\n  BTRFS info (device sda): delayed_refs_rsv: size 0 reserved 0\n\nAbove $dev is a tcmu-runner emulated zoned HDD, which has a max zone\nappend size of 64K, and the system has 64K page size.\n\n[CAUSE]\nI have added several trace_printk() to show the events (header skipped):\n\n  \u0026gt; btrfs_dirty_pages: r/i=5/259 dirty start=774144 len=114688\n  \u0026gt; btrfs_dirty_pages: r/i=5/259 dirty part of page=720896 off_in_page=53248 len_in_page=12288\n  \u0026gt; btrfs_dirty_pages: r/i=5/259 dirty part of page=786432 off_in_page=0 len_in_page=65536\n  \u0026gt; btrfs_dirty_pages: r/i=5/259 dirty part of page=851968 off_in_page=0 len_in_page=36864\n\nThe above lines show our buffered write has dirtied 3 pages of inode\n259 of root 5:\n\n  704K             768K              832K              896K\n  I           |////I/////////////////I///////////|     I\n              756K                               868K\n\n  |///| is the dirtied range using subpage bitmaps. and \u0026apos;I\u0026apos; is the page\n  boundary.\n\n  Meanwhile all three pages (704K, 768K, 832K) have their PageDirty\n  flag set.\n\n  \u0026gt; btrfs_direct_write: r/i=5/259 start dio filepos=696320 len=102400\n\nThen direct IO writ\n---truncated---(CVE-2024-44972)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: fix panic caused by partcmd_update\n\nWe find a bug as below:\nBUG: unable to handle page fault for address: 00000003\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 3 PID: 358 Comm: bash Tainted: G        W I        6.6.0-10893-g60d6\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4\nRIP: 0010:partition_sched_domains_locked+0x483/0x600\nCode: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9\nRSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202\nRAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000002fe80\nRBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000\nR10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002\nR13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000\nFS:  00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? show_regs+0x8c/0xa0\n ? __die_body+0x23/0xa0\n ? __die+0x3a/0x50\n ? page_fault_oops+0x1d2/0x5c0\n ? partition_sched_domains_locked+0x483/0x600\n ? search_module_extables+0x2a/0xb0\n ? search_exception_tables+0x67/0x90\n ? kernelmode_fixup_or_oops+0x144/0x1b0\n ? __bad_area_nosemaphore+0x211/0x360\n ? up_read+0x3b/0x50\n ? bad_area_nosemaphore+0x1a/0x30\n ? exc_page_fault+0x890/0xd90\n ? __lock_acquire.constprop.0+0x24f/0x8d0\n ? __lock_acquire.constprop.0+0x24f/0x8d0\n ? asm_exc_page_fault+0x26/0x30\n ? partition_sched_domains_locked+0x483/0x600\n ? partition_sched_domains_locked+0xf0/0x600\n rebuild_sched_domains_locked+0x806/0xdc0\n update_partition_sd_lb+0x118/0x130\n cpuset_write_resmask+0xffc/0x1420\n cgroup_file_write+0xb2/0x290\n kernfs_fop_write_iter+0x194/0x290\n new_sync_write+0xeb/0x160\n vfs_write+0x16f/0x1d0\n ksys_write+0x81/0x180\n __x64_sys_write+0x21/0x30\n x64_sys_call+0x2f25/0x4630\n do_syscall_64+0x44/0xb0\n entry_SYSCALL_64_after_hwframe+0x78/0xe2\nRIP: 0033:0x7f44a553c887\n\nIt can be reproduced with cammands:\ncd /sys/fs/cgroup/\nmkdir test\ncd test/\necho +cpuset \u0026gt; ../cgroup.subtree_control\necho root \u0026gt; cpuset.cpus.partition\ncat /sys/fs/cgroup/cpuset.cpus.effective\n0-3\necho 0-3 \u0026gt; cpuset.cpus // taking away all cpus from root\n\nThis issue is caused by the incorrect rebuilding of scheduling domains.\nIn this scenario, test/cpuset.cpus.partition should be an invalid root\nand should not trigger the rebuilding of scheduling domains. When calling\nupdate_parent_effective_cpumask with partcmd_update, if newmask is not\nnull, it should recheck newmask whether there are cpus is available\nfor parect/cs that has tasks.(CVE-2024-44975)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: mana: Fix RX buf alloc_size alignment and atomic op panic\n\nThe MANA driver\u0026apos;s RX buffer alloc_size is passed into napi_build_skb() to\ncreate SKB. skb_shinfo(skb) is located at the end of skb, and its alignment\nis affected by the alloc_size passed into napi_build_skb(). The size needs\nto be aligned properly for better performance and atomic operations.\nOtherwise, on ARM64 CPU, for certain MTU settings like 4000, atomic\noperations may panic on the skb_shinfo(skb)-\u0026gt;dataref due to alignment fault.\n\nTo fix this bug, add proper alignment to the alloc_size calculation.\n\nSample panic info:\n[  253.298819] Unable to handle kernel paging request at virtual address ffff000129ba5cce\n[  253.300900] Mem abort info:\n[  253.301760]   ESR = 0x0000000096000021\n[  253.302825]   EC = 0x25: DABT (current EL), IL = 32 bits\n[  253.304268]   SET = 0, FnV = 0\n[  253.305172]   EA = 0, S1PTW = 0\n[  253.306103]   FSC = 0x21: alignment fault\nCall trace:\n __skb_clone+0xfc/0x198\n skb_clone+0x78/0xe0\n raw6_local_deliver+0xfc/0x228\n ip6_protocol_deliver_rcu+0x80/0x500\n ip6_input_finish+0x48/0x80\n ip6_input+0x48/0xc0\n ip6_sublist_rcv_finish+0x50/0x78\n ip6_sublist_rcv+0x1cc/0x2b8\n ipv6_list_rcv+0x100/0x150\n __netif_receive_skb_list_core+0x180/0x220\n netif_receive_skb_list_internal+0x198/0x2a8\n __napi_poll+0x138/0x250\n net_rx_action+0x148/0x330\n handle_softirqs+0x12c/0x3a0(CVE-2024-45001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix validity interception issue when gisa is switched off\n\nWe might run into a SIE validity if gisa has been disabled either via using\nkernel parameter \u0026quot;kvm.use_gisa=0\u0026quot; or by setting the related sysfs\nattribute to N (echo N \u0026gt;/sys/module/kvm/parameters/use_gisa).\n\nThe validity is caused by an invalid value in the SIE control block\u0026apos;s\ngisa designation. That happens because we pass the uninitialized gisa\norigin to virt_to_phys() before writing it to the gisa designation.\n\nTo fix this we return 0 in kvm_s390_get_gisa_desc() if the origin is 0.\nkvm_s390_get_gisa_desc() is used to determine which gisa designation to\nset in the SIE control block. A value of 0 in the gisa designation disables\ngisa usage.\n\nThe issue surfaces in the host kernel with the following kernel message as\nsoon a new kvm guest start is attemted.\n\nkvm: unhandled validity intercept 0x1011\nWARNING: CPU: 0 PID: 781237 at arch/s390/kvm/intercept.c:101 kvm_handle_sie_intercept+0x42e/0x4d0 [kvm]\nModules linked in: vhost_net tap tun xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp nft_compat x_tables nf_nat_tftp nf_conntrack_tftp vfio_pci_core irqbypass vhost_vsock vmw_vsock_virtio_transport_common vsock vhost vhost_iotlb kvm nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables sunrpc mlx5_ib ib_uverbs ib_core mlx5_core uvdevice s390_trng eadm_sch vfio_ccw zcrypt_cex4 mdev vfio_iommu_type1 vfio sch_fq_codel drm i2c_core loop drm_panel_orientation_quirks configfs nfnetlink lcs ctcm fsm dm_service_time ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common dm_mirror dm_region_hash dm_log zfcp scsi_transport_fc scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt dm_multipath rng_core autofs4 [last unloaded: vfio_pci]\nCPU: 0 PID: 781237 Comm: CPU 0/KVM Not tainted 6.10.0-08682-gcad9f11498ea #6\nHardware name: IBM 3931 A01 701 (LPAR)\nKrnl PSW : 0704c00180000000 000003d93deb0122 (kvm_handle_sie_intercept+0x432/0x4d0 [kvm])\n           R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3\nKrnl GPRS: 000003d900000027 000003d900000023 0000000000000028 000002cd00000000\n           000002d063a00900 00000359c6daf708 00000000000bebb5 0000000000001eff\n           000002cfd82e9000 000002cfd80bc000 0000000000001011 000003d93deda412\n           000003ff8962df98 000003d93de77ce0 000003d93deb011e 00000359c6daf960\nKrnl Code: 000003d93deb0112: c020fffe7259\tlarl\t%r2,000003d93de7e5c4\n           000003d93deb0118: c0e53fa8beac\tbrasl\t%r14,000003d9bd3c7e70\n          #000003d93deb011e: af000000\t\tmc\t0,0\n          \u0026gt;000003d93deb0122: a728ffea\t\tlhi\t%r2,-22\n           000003d93deb0126: a7f4fe24\t\tbrc\t15,000003d93deafd6e\n           000003d93deb012a: 9101f0b0\t\ttm\t176(%r15),1\n           000003d93deb012e: a774fe48\t\tbrc\t7,000003d93deafdbe\n           000003d93deb0132: 40a0f0ae\t\tsth\t%r10,174(%r15)\nCall Trace:\n [\u0026lt;000003d93deb0122\u0026gt;] kvm_handle_sie_intercept+0x432/0x4d0 [kvm]\n([\u0026lt;000003d93deb011e\u0026gt;] kvm_handle_sie_intercept+0x42e/0x4d0 [kvm])\n [\u0026lt;000003d93deacc10\u0026gt;] vcpu_post_run+0x1d0/0x3b0 [kvm]\n [\u0026lt;000003d93deaceda\u0026gt;] __vcpu_run+0xea/0x2d0 [kvm]\n [\u0026lt;000003d93dead9da\u0026gt;] kvm_arch_vcpu_ioctl_run+0x16a/0x430 [kvm]\n [\u0026lt;000003d93de93ee0\u0026gt;] kvm_vcpu_ioctl+0x190/0x7c0 [kvm]\n [\u0026lt;000003d9bd728b4e\u0026gt;] vfs_ioctl+0x2e/0x70\n [\u0026lt;000003d9bd72a092\u0026gt;] __s390x_sys_ioctl+0xc2/0xd0\n [\u0026lt;000003d9be0e9222\u0026gt;] __do_syscall+0x1f2/0x2e0\n [\u0026lt;000003d9be0f9a90\u0026gt;] system_call+0x70/0x98\nLast Breaking-Event-Address:\n [\u0026lt;000003d9bd3c7f58\u0026gt;] __warn_printk+0xe8/0xf0(CVE-2024-45005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nchar: xillybus: Don\u0026apos;t destroy workqueue from work item running on it\n\nTriggered by a kref decrement, destroy_workqueue() may be called from\nwithin a work item for destroying its own workqueue. This illegal\nsituation is averted by adding a module-global workqueue for exclusive\nuse of the offending work item. Other work items continue to be queued\non per-device workqueues to ensure performance.(CVE-2024-45007)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: use dma non-coherent allocator\n\nCurrently, enabling SG_DEBUG in the kernel will cause nouveau to hit a\nBUG() on startup, when the iommu is enabled:\n\nkernel BUG at include/linux/scatterlist.h:187!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30\nHardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019\nRIP: 0010:sg_init_one+0x85/0xa0\nCode: 69 88 32 01 83 e1 03 f6 c3 03 75 20 a8 01 75 1e 48 09 cb 41 89 54\n24 08 49 89 1c 24 41 89 6c 24 0c 5b 5d 41 5c e9 7b b9 88 00 \u0026lt;0f\u0026gt; 0b 0f 0b\n0f 0b 48 8b 05 5e 46 9a 01 eb b2 66 66 2e 0f 1f 84 00\nRSP: 0018:ffffa776017bf6a0 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffffa77600d87000 RCX: 000000000000002b\nRDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffa77680d87000\nRBP: 000000000000e000 R08: 0000000000000000 R09: 0000000000000000\nR10: ffff98f4c46aa508 R11: 0000000000000000 R12: ffff98f4c46aa508\nR13: ffff98f4c46aa008 R14: ffffa77600d4a000 R15: ffffa77600d4a018\nFS:  00007feeb5aae980(0000) GS:ffff98f5c4dc0000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f22cb9a4520 CR3: 00000001043ba000 CR4: 00000000003506f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? die+0x36/0x90\n ? do_trap+0xdd/0x100\n ? sg_init_one+0x85/0xa0\n ? do_error_trap+0x65/0x80\n ? sg_init_one+0x85/0xa0\n ? exc_invalid_op+0x50/0x70\n ? sg_init_one+0x85/0xa0\n ? asm_exc_invalid_op+0x1a/0x20\n ? sg_init_one+0x85/0xa0\n nvkm_firmware_ctor+0x14a/0x250 [nouveau]\n nvkm_falcon_fw_ctor+0x42/0x70 [nouveau]\n ga102_gsp_booter_ctor+0xb4/0x1a0 [nouveau]\n r535_gsp_oneinit+0xb3/0x15f0 [nouveau]\n ? srso_return_thunk+0x5/0x5f\n ? srso_return_thunk+0x5/0x5f\n ? nvkm_udevice_new+0x95/0x140 [nouveau]\n ? srso_return_thunk+0x5/0x5f\n ? srso_return_thunk+0x5/0x5f\n ? ktime_get+0x47/0xb0\n\nFix this by using the non-coherent allocator instead, I think there\nmight be a better answer to this, but it involve ripping up some of\nAPIs using sg lists.(CVE-2024-45012)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0\n\nThe __vmap_pages_range_noflush() assumes its argument pages** contains\npages with the same page shift.  However, since commit e9c3cda4d86e (\u0026quot;mm,\nvmalloc: fix high order __GFP_NOFAIL allocations\u0026quot;), if gfp_flags includes\n__GFP_NOFAIL with high order in vm_area_alloc_pages() and page allocation\nfailed for high order, the pages** may contain two different page shifts\n(high order and order-0).  This could lead __vmap_pages_range_noflush() to\nperform incorrect mappings, potentially resulting in memory corruption.\n\nUsers might encounter this as follows (vmap_allow_huge = true, 2M is for\nPMD_SIZE):\n\nkvmalloc(2M, __GFP_NOFAIL|GFP_X)\n    __vmalloc_node_range_noprof(vm_flags=VM_ALLOW_HUGE_VMAP)\n        vm_area_alloc_pages(order=9) ---\u0026gt; order-9 allocation failed and fallback to order-0\n            vmap_pages_range()\n                vmap_pages_range_noflush()\n                    __vmap_pages_range_noflush(page_shift = 21) ----\u0026gt; wrong mapping happens\n\nWe can remove the fallback code because if a high-order allocation fails,\n__vmalloc_node_range_noprof() will retry with order-0.  Therefore, it is\nunnecessary to fallback to order-0 here.  Therefore, fix this by removing\nthe fallback code.(CVE-2024-45022)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion\n\nwpa_supplicant 2.11 sends since 1efdba5fdc2c (\u0026quot;Handle PMKSA flush in the\ndriver for SAE/OWE offload cases\u0026quot;) SSID based PMKSA del commands.\nbrcmfmac is not prepared and tries to dereference the NULL bssid and\npmkid pointers in cfg80211_pmksa. PMKID_V3 operations support SSID based\nupdates so copy the SSID.(CVE-2024-46672)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btnxpuart: Fix random crash seen while removing driver\n\nThis fixes the random kernel crash seen while removing the driver, when\nrunning the load/unload test over multiple iterations.\n\n1) modprobe btnxpuart\n2) hciconfig hci0 reset\n3) hciconfig (check hci0 interface up with valid BD address)\n4) modprobe -r btnxpuart\nRepeat steps 1 to 4\n\nThe ps_wakeup() call in btnxpuart_close() schedules the psdata-\u0026gt;work(),\nwhich gets scheduled after module is removed, causing a kernel crash.\n\nThis hidden issue got highlighted after enabling Power Save by default\nin 4183a7be7700 (Bluetooth: btnxpuart: Enable Power Save feature on\nstartup)\n\nThe new ps_cleanup() deasserts UART break immediately while closing\nserdev device, cancels any scheduled ps_work and destroys the ps_lock\nmutex.\n\n[   85.884604] Unable to handle kernel paging request at virtual address ffffd4a61638f258\n[   85.884624] Mem abort info:\n[   85.884625]   ESR = 0x0000000086000007\n[   85.884628]   EC = 0x21: IABT (current EL), IL = 32 bits\n[   85.884633]   SET = 0, FnV = 0\n[   85.884636]   EA = 0, S1PTW = 0\n[   85.884638]   FSC = 0x07: level 3 translation fault\n[   85.884642] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041dd0000\n[   85.884646] [ffffd4a61638f258] pgd=1000000095fff003, p4d=1000000095fff003, pud=100000004823d003, pmd=100000004823e003, pte=0000000000000000\n[   85.884662] Internal error: Oops: 0000000086000007 [#1] PREEMPT SMP\n[   85.890932] Modules linked in: algif_hash algif_skcipher af_alg overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_spdif snd_soc_fsl_micfil snd_soc_fsl_sai snd_soc_fsl_utils gpio_ir_recv rc_core fuse [last unloaded: btnxpuart(O)]\n[   85.927297] CPU: 1 PID: 67 Comm: kworker/1:3 Tainted: G           O       6.1.36+g937b1be4345a #1\n[   85.936176] Hardware name: FSL i.MX8MM EVK board (DT)\n[   85.936182] Workqueue: events 0xffffd4a61638f380\n[   85.936198] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   85.952817] pc : 0xffffd4a61638f258\n[   85.952823] lr : 0xffffd4a61638f258\n[   85.952827] sp : ffff8000084fbd70\n[   85.952829] x29: ffff8000084fbd70 x28: 0000000000000000 x27: 0000000000000000\n[   85.963112] x26: ffffd4a69133f000 x25: ffff4bf1c8540990 x24: ffff4bf215b87305\n[   85.963119] x23: ffff4bf215b87300 x22: ffff4bf1c85409d0 x21: ffff4bf1c8540970\n[   85.977382] x20: 0000000000000000 x19: ffff4bf1c8540880 x18: 0000000000000000\n[   85.977391] x17: 0000000000000000 x16: 0000000000000133 x15: 0000ffffe2217090\n[   85.977399] x14: 0000000000000001 x13: 0000000000000133 x12: 0000000000000139\n[   85.977407] x11: 0000000000000001 x10: 0000000000000a60 x9 : ffff8000084fbc50\n[   85.977417] x8 : ffff4bf215b7d000 x7 : ffff4bf215b83b40 x6 : 00000000000003e8\n[   85.977424] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : 0000000000000000\n[   85.977432] x2 : 0000000000000000 x1 : ffff4bf1c4265880 x0 : 0000000000000000\n[   85.977443] Call trace:\n[   85.977446]  0xffffd4a61638f258\n[   85.977451]  0xffffd4a61638f3e8\n[   85.977455]  process_one_work+0x1d4/0x330\n[   85.977464]  worker_thread+0x6c/0x430\n[   85.977471]  kthread+0x108/0x10c\n[   85.977476]  ret_from_fork+0x10/0x20\n[   85.977488] Code: bad PC value\n[   85.977491] ---[ end trace 0000000000000000 ]---\n\nPreset since v6.9.11(CVE-2024-46680)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoc: qcom: pmic_glink: Fix race during initialization\n\nAs pointed out by Stephen Boyd it is possible that during initialization\nof the pmic_glink child drivers, the protection-domain notifiers fires,\nand the associated work is scheduled, before the client registration\nreturns and as a result the local \u0026quot;client\u0026quot; pointer has been initialized.\n\nThe outcome of this is a NULL pointer dereference as the \u0026quot;client\u0026quot;\npointer is blindly dereferenced.\n\nTimeline provided by Stephen:\n CPU0                               CPU1\n ----                               ----\n ucsi-\u0026gt;client = NULL;\n devm_pmic_glink_register_client()\n  client-\u0026gt;pdr_notify(client-\u0026gt;priv, pg-\u0026gt;client_state)\n   pmic_glink_ucsi_pdr_notify()\n    schedule_work(\u0026amp;ucsi-\u0026gt;register_work)\n    \u0026lt;schedule away\u0026gt;\n                                    pmic_glink_ucsi_register()\n                                     ucsi_register()\n                                      pmic_glink_ucsi_read_version()\n                                       pmic_glink_ucsi_read()\n                                        pmic_glink_ucsi_read()\n                                         pmic_glink_send(ucsi-\u0026gt;client)\n                                         \u0026lt;client is NULL BAD\u0026gt;\n ucsi-\u0026gt;client = client // Too late!\n\nThis code is identical across the altmode, battery manager and usci\nchild drivers.\n\nResolve this by splitting the allocation of the \u0026quot;client\u0026quot; object and the\nregistration thereof into two operations.\n\nThis only happens if the protection domain registry is populated at the\ntime of registration, which by the introduction of commit \u0026apos;1ebcde047c54\n(\u0026quot;soc: qcom: add pd-mapper implementation\u0026quot;)\u0026apos; became much more likely.(CVE-2024-46693)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: avoid using null object of framebuffer\n\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.\n\n(cherry picked from commit 73dd0ad9e5dad53766ea3e631303430116f834b3)(CVE-2024-46694)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: fix ID 0 endp usage after multiple re-creations\n\n\u0026apos;local_addr_used\u0026apos; and \u0026apos;add_addr_accepted\u0026apos; are decremented for addresses\nnot related to the initial subflow (ID0), because the source and\ndestination addresses of the initial subflows are known from the\nbeginning: they don\u0026apos;t count as \u0026quot;additional local address being used\u0026quot; or\n\u0026quot;ADD_ADDR being accepted\u0026quot;.\n\nIt is then required not to increment them when the entrypoint used by\nthe initial subflow is removed and re-added during a connection. Without\nthis modification, this entrypoint cannot be removed and re-added more\nthan once.(CVE-2024-46711)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmisc: fastrpc: Fix double free of \u0026apos;buf\u0026apos; in error path\n\nsmatch warning:\ndrivers/misc/fastrpc.c:1926 fastrpc_req_mmap() error: double free of \u0026apos;buf\u0026apos;\n\nIn fastrpc_req_mmap() error path, the fastrpc buffer is freed in\nfastrpc_req_munmap_impl() if unmap is successful.\n\nBut in the end, there is an unconditional call to fastrpc_buf_free().\nSo the above case triggers the double free of fastrpc buf.(CVE-2024-46741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: void array out of bound when loop tnl_num\n\nWhen query reg inf of SSU, it loops tnl_num times. However, tnl_num comes\nfrom hardware and the length of array is a fixed value. To void array out\nof bound, make sure the loop time is not greater than the length of array(CVE-2024-46833)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: vmalloc: ensure vmap_block is initialised before adding to queue\n\nCommit 8c61291fd850 (\u0026quot;mm: fix incorrect vbq reference in\npurge_fragmented_block\u0026quot;) extended the \u0026apos;vmap_block\u0026apos; structure to contain a\n\u0026apos;cpu\u0026apos; field which is set at allocation time to the id of the initialising\nCPU.\n\nWhen a new \u0026apos;vmap_block\u0026apos; is being instantiated by new_vmap_block(), the\npartially initialised structure is added to the local \u0026apos;vmap_block_queue\u0026apos;\nxarray before the \u0026apos;cpu\u0026apos; field has been initialised.  If another CPU is\nconcurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it\nmay perform an out-of-bounds access to the remote queue thanks to an\nuninitialised index.\n\nThis has been observed as UBSAN errors in Android:\n\n | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP\n |\n | Call trace:\n |  purge_fragmented_block+0x204/0x21c\n |  _vm_unmap_aliases+0x170/0x378\n |  vm_unmap_aliases+0x1c/0x28\n |  change_memory_common+0x1dc/0x26c\n |  set_memory_ro+0x18/0x24\n |  module_enable_ro+0x98/0x238\n |  do_init_module+0x1b0/0x310\n\nMove the initialisation of \u0026apos;vb-\u0026gt;cpu\u0026apos; in new_vmap_block() ahead of the\naddition to the xarray.(CVE-2024-46847)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/hyperv: fix kexec crash due to VP assist page corruption\n\ncommit 9636be85cc5b (\u0026quot;x86/hyperv: Fix hyperv_pcpu_input_arg handling when\nCPUs go online/offline\u0026quot;) introduces a new cpuhp state for hyperv\ninitialization.\n\ncpuhp_setup_state() returns the state number if state is\nCPUHP_AP_ONLINE_DYN or CPUHP_BP_PREPARE_DYN and 0 for all other states.\nFor the hyperv case, since a new cpuhp state was introduced it would\nreturn 0. However, in hv_machine_shutdown(), the cpuhp_remove_state() call\nis conditioned upon \u0026quot;hyperv_init_cpuhp \u0026gt; 0\u0026quot;. This will never be true and\nso hv_cpu_die() won\u0026apos;t be called on all CPUs. This means the VP assist page\nwon\u0026apos;t be reset. When the kexec kernel tries to setup the VP assist page\nagain, the hypervisor corrupts the memory region of the old VP assist page\ncausing a panic in case the kexec kernel is using that memory elsewhere.\nThis was originally fixed in commit dfe94d4086e4 (\u0026quot;x86/hyperv: Fix kexec\npanic/hang issues\u0026quot;).\n\nGet rid of hyperv_init_cpuhp entirely since we are no longer using a\ndynamic cpuhp state and use CPUHP_AP_HYPERV_ONLINE directly with\ncpuhp_remove_state().(CVE-2024-46864)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfou: fix initialization of grc\n\nThe grc must be initialize first. There can be a condition where if\nfou is NULL, goto out will be executed and grc would be used\nuninitialized.(CVE-2024-46865)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - inject error before stopping queue\n\nThe master ooo cannot be completely closed when the\naccelerator core reports memory error. Therefore, the driver\nneeds to inject the qm error to close the master ooo. Currently,\nthe qm error is injected after stopping queue, memory may be\nreleased immediately after stopping queue, causing the device to\naccess the released memory. Therefore, error is injected to close master\nooo before stopping queue to ensure that the device does not access\nthe released memory.(CVE-2024-47730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled\n\nFix missuse of spin_lock_irq()/spin_unlock_irq() when\nspin_lock_irqsave()/spin_lock_irqrestore() was hold.\n\nThis was discovered through the lock debugging, and the corresponding\nlog is as follows:\n\nraw_local_irq_restore() called with IRQs enabled\nWARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40\n...\nCall trace:\n warn_bogus_irq_restore+0x30/0x40\n _raw_spin_unlock_irqrestore+0x84/0xc8\n add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2]\n hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2]\n hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2]\n create_qp+0x138/0x258\n ib_create_qp_kernel+0x50/0xe8\n create_mad_qp+0xa8/0x128\n ib_mad_port_open+0x218/0x448\n ib_mad_init_device+0x70/0x1f8\n add_client_context+0xfc/0x220\n enable_device_and_get+0xd0/0x140\n ib_register_device.part.0+0xf4/0x1c8\n ib_register_device+0x34/0x50\n hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2]\n hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2]\n __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2]\n hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2](CVE-2024-47735)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: Fix a race between socket set up and I/O thread creation\n\nIn rxrpc_open_socket(), it sets up the socket and then sets up the I/O\nthread that will handle it.  This is a problem, however, as there\u0026apos;s a gap\nbetween the two phases in which a packet may come into rxrpc_encap_rcv()\nfrom the UDP packet but we oops when trying to wake the not-yet created I/O\nthread.\n\nAs a quick fix, just make rxrpc_encap_rcv() discard the packet if there\u0026apos;s\nno I/O thread yet.\n\nA better, but more intrusive fix would perhaps be to rearrange things such\nthat the socket creation is done by the I/O thread.(CVE-2024-49864)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix a sdiv overflow issue\n\nZac Ecob reported a problem where a bpf program may cause kernel crash due\nto the following error:\n  Oops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI\n\nThe failure is due to the below signed divide:\n  LLONG_MIN/-1 where LLONG_MIN equals to -9,223,372,036,854,775,808.\nLLONG_MIN/-1 is supposed to give a positive number 9,223,372,036,854,775,808,\nbut it is impossible since for 64-bit system, the maximum positive\nnumber is 9,223,372,036,854,775,807. On x86_64, LLONG_MIN/-1 will\ncause a kernel exception. On arm64, the result for LLONG_MIN/-1 is\nLLONG_MIN.\n\nFurther investigation found all the following sdiv/smod cases may trigger\nan exception when bpf program is running on x86_64 platform:\n  - LLONG_MIN/-1 for 64bit operation\n  - INT_MIN/-1 for 32bit operation\n  - LLONG_MIN%-1 for 64bit operation\n  - INT_MIN%-1 for 32bit operation\nwhere -1 can be an immediate or in a register.\n\nOn arm64, there are no exceptions:\n  - LLONG_MIN/-1 = LLONG_MIN\n  - INT_MIN/-1 = INT_MIN\n  - LLONG_MIN%-1 = 0\n  - INT_MIN%-1 = 0\nwhere -1 can be an immediate or in a register.\n\nInsn patching is needed to handle the above cases and the patched codes\nproduced results aligned with above arm64 result. The below are pseudo\ncodes to handle sdiv/smod exceptions including both divisor -1 and divisor 0\nand the divisor is stored in a register.\n\nsdiv:\n      tmp = rX\n      tmp += 1 /* [-1, 0] -\u0026gt; [0, 1]\n      if tmp \u0026gt;(unsigned) 1 goto L2\n      if tmp == 0 goto L1\n      rY = 0\n  L1:\n      rY = -rY;\n      goto L3\n  L2:\n      rY /= rX\n  L3:\n\nsmod:\n      tmp = rX\n      tmp += 1 /* [-1, 0] -\u0026gt; [0, 1]\n      if tmp \u0026gt;(unsigned) 1 goto L1\n      if tmp == 1 (is64 ? goto L2 : goto L3)\n      rY = 0;\n      goto L2\n  L1:\n      rY %= rX\n  L2:\n      goto L4  // only when !is64\n  L3:\n      wY = wY  // only when !is64\n  L4:\n\n  [1] https://lore.kernel.org/bpf/tPJLTEh7S_DxFEqAI2Ji5MBSoZVg7_G-Py2iaZpAaWtM961fFTWtsnlzwvTbzBzaUzwQAoNATXKUlt0LZOFgnDcIyKCswAnAGdUF3LBrhGQ=@protonmail.com/(CVE-2024-49888)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu-tasks: Fix access non-existent percpu rtpcp variable in rcu_tasks_need_gpcb()\n\nFor kernels built with CONFIG_FORCE_NR_CPUS=y, the nr_cpu_ids is\ndefined as NR_CPUS instead of the number of possible cpus, this\nwill cause the following system panic:\n\nsmpboot: Allowing 4 CPUs, 0 hotplug CPUs\n...\nsetup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:512 nr_node_ids:1\n...\nBUG: unable to handle page fault for address: ffffffff9911c8c8\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 0 PID: 15 Comm: rcu_tasks_trace Tainted: G W\n6.6.21 #1 5dc7acf91a5e8e9ac9dcfc35bee0245691283ea6\nRIP: 0010:rcu_tasks_need_gpcb+0x25d/0x2c0\nRSP: 0018:ffffa371c00a3e60 EFLAGS: 00010082\nCR2: ffffffff9911c8c8 CR3: 000000040fa20005 CR4: 00000000001706f0\nCall Trace:\n\u0026lt;TASK\u0026gt;\n? __die+0x23/0x80\n? page_fault_oops+0xa4/0x180\n? exc_page_fault+0x152/0x180\n? asm_exc_page_fault+0x26/0x40\n? rcu_tasks_need_gpcb+0x25d/0x2c0\n? __pfx_rcu_tasks_kthread+0x40/0x40\nrcu_tasks_one_gp+0x69/0x180\nrcu_tasks_kthread+0x94/0xc0\nkthread+0xe8/0x140\n? __pfx_kthread+0x40/0x40\nret_from_fork+0x34/0x80\n? __pfx_kthread+0x40/0x40\nret_from_fork_asm+0x1b/0x80\n\u0026lt;/TASK\u0026gt;\n\nConsidering that there may be holes in the CPU numbers, use the\nmaximum possible cpu number, instead of nr_cpu_ids, for configuring\nenqueue and dequeue limits.\n\n[ neeraj.upadhyay: Fix htmldocs build error reported by Stephen Rothwell ](CVE-2024-49926)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: avoid to add interface to list twice when SER\n\nIf SER L2 occurs during the WoWLAN resume flow, the add interface flow\nis triggered by ieee80211_reconfig(). However, due to\nrtw89_wow_resume() return failure, it will cause the add interface flow\nto be executed again, resulting in a double add list and causing a kernel\npanic. Therefore, we have added a check to prevent double adding of the\nlist.\n\nlist_add double add: new=ffff99d6992e2010, prev=ffff99d6992e2010, next=ffff99d695302628.\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:37!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 9 Comm: kworker/0:1 Tainted: G        W  O       6.6.30-02659-gc18865c4dfbd #1 770df2933251a0e3c888ba69d1053a817a6376a7\nHardware name: HP Grunt/Grunt, BIOS Google_Grunt.11031.169.0 06/24/2021\nWorkqueue: events_freezable ieee80211_restart_work [mac80211]\nRIP: 0010:__list_add_valid_or_report+0x5e/0xb0\nCode: c7 74 18 48 39 ce 74 13 b0 01 59 5a 5e 5f 41 58 41 59 41 5a 5d e9 e2 d6 03 00 cc 48 c7 c7 8d 4f 17 83 48 89 c2 e8 02 c0 00 00 \u0026lt;0f\u0026gt; 0b 48 c7 c7 aa 8c 1c 83 e8 f4 bf 00 00 0f 0b 48 c7 c7 c8 bc 12\nRSP: 0018:ffffa91b8007bc50 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ffff99d6992e0900 RCX: a014d76c70ef3900\nRDX: ffffa91b8007bae8 RSI: 00000000ffffdfff RDI: 0000000000000001\nRBP: ffffa91b8007bc88 R08: 0000000000000000 R09: ffffa91b8007bae0\nR10: 00000000ffffdfff R11: ffffffff83a79800 R12: ffff99d695302060\nR13: ffff99d695300900 R14: ffff99d6992e1be0 R15: ffff99d6992e2010\nFS:  0000000000000000(0000) GS:ffff99d6aac00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000078fbdba43480 CR3: 000000010e464000 CR4: 00000000001506f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die_body+0x1f/0x70\n ? die+0x3d/0x60\n ? do_trap+0xa4/0x110\n ? __list_add_valid_or_report+0x5e/0xb0\n ? do_error_trap+0x6d/0x90\n ? __list_add_valid_or_report+0x5e/0xb0\n ? handle_invalid_op+0x30/0x40\n ? __list_add_valid_or_report+0x5e/0xb0\n ? exc_invalid_op+0x3c/0x50\n ? asm_exc_invalid_op+0x16/0x20\n ? __list_add_valid_or_report+0x5e/0xb0\n rtw89_ops_add_interface+0x309/0x310 [rtw89_core 7c32b1ee6854761c0321027c8a58c5160e41f48f]\n drv_add_interface+0x5c/0x130 [mac80211 83e989e6e616bd5b4b8a2b0a9f9352a2c385a3bc]\n ieee80211_reconfig+0x241/0x13d0 [mac80211 83e989e6e616bd5b4b8a2b0a9f9352a2c385a3bc]\n ? finish_wait+0x3e/0x90\n ? synchronize_rcu_expedited+0x174/0x260\n ? sync_rcu_exp_done_unlocked+0x50/0x50\n ? wake_bit_function+0x40/0x40\n ieee80211_restart_work+0xf0/0x140 [mac80211 83e989e6e616bd5b4b8a2b0a9f9352a2c385a3bc]\n process_scheduled_works+0x1e5/0x480\n worker_thread+0xea/0x1e0\n kthread+0xdb/0x110\n ? move_linked_works+0x90/0x90\n ? kthread_associate_blkcg+0xa0/0xa0\n ret_from_fork+0x3b/0x50\n ? kthread_associate_blkcg+0xa0/0xa0\n ret_from_fork_asm+0x11/0x20\n \u0026lt;/TASK\u0026gt;\nModules linked in: dm_integrity async_xor xor async_tx lz4 lz4_compress zstd zstd_compress zram zsmalloc rfcomm cmac uinput algif_hash algif_skcipher af_alg btusb btrtl iio_trig_hrtimer industrialio_sw_trigger btmtk industrialio_configfs btbcm btintel uvcvideo videobuf2_vmalloc iio_trig_sysfs videobuf2_memops videobuf2_v4l2 videobuf2_common uvc snd_hda_codec_hdmi veth snd_hda_intel snd_intel_dspcfg acpi_als snd_hda_codec industrialio_triggered_buffer kfifo_buf snd_hwdep industrialio i2c_piix4 snd_hda_core designware_i2s ip6table_nat snd_soc_max98357a xt_MASQUERADE xt_cgroup snd_soc_acp_rt5682_mach fuse rtw89_8922ae(O) rtw89_8922a(O) rtw89_pci(O) rtw89_core(O) 8021q mac80211(O) bluetooth ecdh_generic ecc cfg80211 r8152 mii joydev\ngsmi: Log Shutdown Reason 0x03\n---[ end trace 0000000000000000 ]---(CVE-2024-49939)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nppp: do not assume bh is held in ppp_channel_bridge_input()\n\nNetworking receive path is usually handled from BH handler.\nHowever, some protocols need to acquire the socket lock, and\npackets might be stored in the socket backlog is the socket was\nowned by a user process.\n\nIn this case, release_sock(), __release_sock(), and sk_backlog_rcv()\nmight call the sk-\u0026gt;sk_backlog_rcv() handler in process context.\n\nsybot caught ppp was not considering this case in\nppp_channel_bridge_input() :\n\nWARNING: inconsistent lock state\n6.11.0-rc7-syzkaller-g5f5673607153 #0 Not tainted\n--------------------------------\ninconsistent {SOFTIRQ-ON-W} -\u0026gt; {IN-SOFTIRQ-W} usage.\nksoftirqd/1/24 [HC0[0]:SC1[1]:HE1:SE0] takes:\n ffff0000db7f11e0 (\u0026amp;pch-\u0026gt;downl){+.?.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]\n ffff0000db7f11e0 (\u0026amp;pch-\u0026gt;downl){+.?.}-{2:2}, at: ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2272 [inline]\n ffff0000db7f11e0 (\u0026amp;pch-\u0026gt;downl){+.?.}-{2:2}, at: ppp_input+0x16c/0x854 drivers/net/ppp/ppp_generic.c:2304\n{SOFTIRQ-ON-W} state was registered at:\n   lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5759\n   __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]\n   _raw_spin_lock+0x48/0x60 kernel/locking/spinlock.c:154\n   spin_lock include/linux/spinlock.h:351 [inline]\n   ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2272 [inline]\n   ppp_input+0x16c/0x854 drivers/net/ppp/ppp_generic.c:2304\n   pppoe_rcv_core+0xfc/0x314 drivers/net/ppp/pppoe.c:379\n   sk_backlog_rcv include/net/sock.h:1111 [inline]\n   __release_sock+0x1a8/0x3d8 net/core/sock.c:3004\n   release_sock+0x68/0x1b8 net/core/sock.c:3558\n   pppoe_sendmsg+0xc8/0x5d8 drivers/net/ppp/pppoe.c:903\n   sock_sendmsg_nosec net/socket.c:730 [inline]\n   __sock_sendmsg net/socket.c:745 [inline]\n   __sys_sendto+0x374/0x4f4 net/socket.c:2204\n   __do_sys_sendto net/socket.c:2216 [inline]\n   __se_sys_sendto net/socket.c:2212 [inline]\n   __arm64_sys_sendto+0xd8/0xf8 net/socket.c:2212\n   __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]\n   invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49\n   el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132\n   do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151\n   el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712\n   el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730\n   el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598\nirq event stamp: 282914\n hardirqs last  enabled at (282914): [\u0026lt;ffff80008b42e30c\u0026gt;] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]\n hardirqs last  enabled at (282914): [\u0026lt;ffff80008b42e30c\u0026gt;] _raw_spin_unlock_irqrestore+0x38/0x98 kernel/locking/spinlock.c:194\n hardirqs last disabled at (282913): [\u0026lt;ffff80008b42e13c\u0026gt;] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]\n hardirqs last disabled at (282913): [\u0026lt;ffff80008b42e13c\u0026gt;] _raw_spin_lock_irqsave+0x2c/0x7c kernel/locking/spinlock.c:162\n softirqs last  enabled at (282904): [\u0026lt;ffff8000801f8e88\u0026gt;] softirq_handle_end kernel/softirq.c:400 [inline]\n softirqs last  enabled at (282904): [\u0026lt;ffff8000801f8e88\u0026gt;] handle_softirqs+0xa3c/0xbfc kernel/softirq.c:582\n softirqs last disabled at (282909): [\u0026lt;ffff8000801fbdf8\u0026gt;] run_ksoftirqd+0x70/0x158 kernel/softirq.c:928\n\nother info that might help us debug this:\n Possible unsafe locking scenario:\n\n       CPU0\n       ----\n  lock(\u0026amp;pch-\u0026gt;downl);\n  \u0026lt;Interrupt\u0026gt;\n    lock(\u0026amp;pch-\u0026gt;downl);\n\n *** DEADLOCK ***\n\n1 lock held by ksoftirqd/1/24:\n  #0: ffff80008f74dfa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:325\n\nstack backtrace:\nCPU: 1 UID: 0 PID: 24 Comm: ksoftirqd/1 Not tainted 6.11.0-rc7-syzkaller-g5f5673607153 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nCall trace:\n  dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:319\n  show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:326\n  __dump_sta\n---truncated---(CVE-2024-49946)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix possible crash on mgmt_index_removed\n\nIf mgmt_index_removed is called while there are commands queued on\ncmd_sync it could lead to crashes like the bellow trace:\n\n0x0000053D: __list_del_entry_valid_or_report+0x98/0xdc\n0x0000053D: mgmt_pending_remove+0x18/0x58 [bluetooth]\n0x0000053E: mgmt_remove_adv_monitor_complete+0x80/0x108 [bluetooth]\n0x0000053E: hci_cmd_sync_work+0xbc/0x164 [bluetooth]\n\nSo while handling mgmt_index_removed this attempts to dequeue\ncommands passed as user_data to cmd_sync.(CVE-2024-49951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice\n\nThe km.state is not checked in driver\u0026apos;s delayed work. When\nxfrm_state_check_expire() is called, the state can be reset to\nXFRM_STATE_EXPIRED, even if it is XFRM_STATE_DEAD already. This\nhappens when xfrm state is deleted, but not freed yet. As\n__xfrm_state_delete() is called again in xfrm timer, the following\ncrash occurs.\n\nTo fix this issue, skip xfrm_state_check_expire() if km.state is not\nXFRM_STATE_VALID.\n\n Oops: general protection fault, probably for non-canonical address 0xdead000000000108: 0000 [#1] SMP\n CPU: 5 UID: 0 PID: 7448 Comm: kworker/u102:2 Not tainted 6.11.0-rc2+ #1\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n Workqueue: mlx5e_ipsec: eth%d mlx5e_ipsec_handle_sw_limits [mlx5_core]\n RIP: 0010:__xfrm_state_delete+0x3d/0x1b0\n Code: 0f 84 8b 01 00 00 48 89 fd c6 87 c8 00 00 00 05 48 8d bb 40 10 00 00 e8 11 04 1a 00 48 8b 95 b8 00 00 00 48 8b 85 c0 00 00 00 \u0026lt;48\u0026gt; 89 42 08 48 89 10 48 8b 55 10 48 b8 00 01 00 00 00 00 ad de 48\n RSP: 0018:ffff88885f945ec8 EFLAGS: 00010246\n RAX: dead000000000122 RBX: ffffffff82afa940 RCX: 0000000000000036\n RDX: dead000000000100 RSI: 0000000000000000 RDI: ffffffff82afb980\n RBP: ffff888109a20340 R08: ffff88885f945ea0 R09: 0000000000000000\n R10: 0000000000000000 R11: ffff88885f945ff8 R12: 0000000000000246\n R13: ffff888109a20340 R14: ffff88885f95f420 R15: ffff88885f95f400\n FS:  0000000000000000(0000) GS:ffff88885f940000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f2163102430 CR3: 00000001128d6001 CR4: 0000000000370eb0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  ? die_addr+0x33/0x90\n  ? exc_general_protection+0x1a2/0x390\n  ? asm_exc_general_protection+0x22/0x30\n  ? __xfrm_state_delete+0x3d/0x1b0\n  ? __xfrm_state_delete+0x2f/0x1b0\n  xfrm_timer_handler+0x174/0x350\n  ? __xfrm_state_delete+0x1b0/0x1b0\n  __hrtimer_run_queues+0x121/0x270\n  hrtimer_run_softirq+0x88/0xd0\n  handle_softirqs+0xcc/0x270\n  do_softirq+0x3c/0x50\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n  __local_bh_enable_ip+0x47/0x50\n  mlx5e_ipsec_handle_sw_limits+0x7d/0x90 [mlx5_core]\n  process_one_work+0x137/0x2d0\n  worker_thread+0x28d/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n  \u0026lt;/TASK\u0026gt;(CVE-2024-49953)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpftool: Fix undefined behavior in qsort(NULL, 0, ...)\n\nWhen netfilter has no entry to display, qsort is called with\nqsort(NULL, 0, ...). This results in undefined behavior, as UBSan\nreports:\n\nnet.c:827:2: runtime error: null pointer passed as argument 1, which is declared to never be null\n\nAlthough the C standard does not explicitly state whether calling qsort\nwith a NULL pointer when the size is 0 constitutes undefined behavior,\nSection 7.1.4 of the C standard (Use of library functions) mentions:\n\n\u0026quot;Each of the following statements applies unless explicitly stated\notherwise in the detailed descriptions that follow: If an argument to a\nfunction has an invalid value (such as a value outside the domain of\nthe function, or a pointer outside the address space of the program, or\na null pointer, or a pointer to non-modifiable storage when the\ncorresponding parameter is not const-qualified) or a type (after\npromotion) not expected by a function with variable number of\narguments, the behavior is undefined.\u0026quot;\n\nTo avoid this, add an early return when nf_link_info is NULL to prevent\ncalling qsort with a NULL pointer.(CVE-2024-49987)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: add refcnt to ksmbd_conn struct\n\nWhen sending an oplock break request, opinfo-\u0026gt;conn is used,\nBut freed -\u0026gt;conn can be used on multichannel.\nThis patch add a reference count to the ksmbd_conn struct\nso that it can be freed when it is no longer used.(CVE-2024-49988)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: improve shutdown sequence\n\nAlexander Sverdlin presents 2 problems during shutdown with the\nlan9303 driver. One is specific to lan9303 and the other just happens\nto reproduce there.\n\nThe first problem is that lan9303 is unique among DSA drivers in that it\ncalls dev_get_drvdata() at \u0026quot;arbitrary runtime\u0026quot; (not probe, not shutdown,\nnot remove):\n\nphy_state_machine()\n-\u0026gt; ...\n   -\u0026gt; dsa_user_phy_read()\n      -\u0026gt; ds-\u0026gt;ops-\u0026gt;phy_read()\n         -\u0026gt; lan9303_phy_read()\n            -\u0026gt; chip-\u0026gt;ops-\u0026gt;phy_read()\n               -\u0026gt; lan9303_mdio_phy_read()\n                  -\u0026gt; dev_get_drvdata()\n\nBut we never stop the phy_state_machine(), so it may continue to run\nafter dsa_switch_shutdown(). Our common pattern in all DSA drivers is\nto set drvdata to NULL to suppress the remove() method that may come\nafterwards. But in this case it will result in an NPD.\n\nThe second problem is that the way in which we set\ndp-\u0026gt;conduit-\u0026gt;dsa_ptr = NULL; is concurrent with receive packet\nprocessing. dsa_switch_rcv() checks once whether dev-\u0026gt;dsa_ptr is NULL,\nbut afterwards, rather than continuing to use that non-NULL value,\ndev-\u0026gt;dsa_ptr is dereferenced again and again without NULL checks:\ndsa_conduit_find_user() and many other places. In between dereferences,\nthere is no locking to ensure that what was valid once continues to be\nvalid.\n\nBoth problems have the common aspect that closing the conduit interface\nsolves them.\n\nIn the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN\nevent in dsa_user_netdevice_event() which closes user ports as well.\ndsa_port_disable_rt() calls phylink_stop(), which synchronously stops\nthe phylink state machine, and ds-\u0026gt;ops-\u0026gt;phy_read() will thus no longer\ncall into the driver after this point.\n\nIn the second case, dev_close(conduit) should do this, as per\nDocumentation/networking/driver.rst:\n\n| Quiescence\n| ----------\n|\n| After the ndo_stop routine has been called, the hardware must\n| not receive or transmit any data.  All in flight packets must\n| be aborted. If necessary, poll or wait for completion of\n| any reset commands.\n\nSo it should be sufficient to ensure that later, when we zeroize\nconduit-\u0026gt;dsa_ptr, there will be no concurrent dsa_switch_rcv() call\non this conduit.\n\nThe addition of the netif_device_detach() function is to ensure that\nioctls, rtnetlinks and ethtool requests on the user ports no longer\npropagate down to the driver - we\u0026apos;re no longer prepared to handle them.\n\nThe race condition actually did not exist when commit 0650bf52b31f\n(\u0026quot;net: dsa: be compatible with masters which unregister on shutdown\u0026quot;)\nfirst introduced dsa_switch_shutdown(). It was created later, when we\nstopped unregistering the user interfaces from a bad spot, and we just\nreplaced that sequence with a racy zeroization of conduit-\u0026gt;dsa_ptr\n(one which doesn\u0026apos;t ensure that the interfaces aren\u0026apos;t up).(CVE-2024-49998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nppp: fix ppp_async_encode() illegal access\n\nsyzbot reported an issue in ppp_async_encode() [1]\n\nIn this case, pppoe_sendmsg() is called with a zero size.\nThen ppp_async_encode() is called with an empty skb.\n\nBUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]\n BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675\n  ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]\n  ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675\n  ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634\n  ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline]\n  ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304\n  pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379\n  sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113\n  __release_sock+0x1da/0x330 net/core/sock.c:3072\n  release_sock+0x6b/0x250 net/core/sock.c:3626\n  pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903\n  sock_sendmsg_nosec net/socket.c:729 [inline]\n  __sock_sendmsg+0x30f/0x380 net/socket.c:744\n  ____sys_sendmsg+0x903/0xb60 net/socket.c:2602\n  ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656\n  __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742\n  __do_sys_sendmmsg net/socket.c:2771 [inline]\n  __se_sys_sendmmsg net/socket.c:2768 [inline]\n  __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768\n  x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n  slab_post_alloc_hook mm/slub.c:4092 [inline]\n  slab_alloc_node mm/slub.c:4135 [inline]\n  kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187\n  kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587\n  __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678\n  alloc_skb include/linux/skbuff.h:1322 [inline]\n  sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732\n  pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867\n  sock_sendmsg_nosec net/socket.c:729 [inline]\n  __sock_sendmsg+0x30f/0x380 net/socket.c:744\n  ____sys_sendmsg+0x903/0xb60 net/socket.c:2602\n  ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656\n  __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742\n  __do_sys_sendmmsg net/socket.c:2771 [inline]\n  __se_sys_sendmmsg net/socket.c:2768 [inline]\n  __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768\n  x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: Fix multiple init when debugfs is disabled\n\nIf bt_debugfs is not created successfully, which happens if either\nCONFIG_DEBUG_FS or CONFIG_DEBUG_FS_ALLOW_ALL is unset, then iso_init()\nreturns early and does not set iso_inited to true. This means that a\nsubsequent call to iso_init() will result in duplicate calls to\nproto_register(), bt_sock_register(), etc.\n\nWith CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, the\nduplicate call to proto_register() triggers this BUG():\n\n  list_add double add: new=ffffffffc0b280d0, prev=ffffffffbab56250,\n    next=ffffffffc0b280d0.\n  ------------[ cut here ]------------\n  kernel BUG at lib/list_debug.c:35!\n  Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI\n  CPU: 2 PID: 887 Comm: bluetoothd Not tainted 6.10.11-1-ao-desktop #1\n  RIP: 0010:__list_add_valid_or_report+0x9a/0xa0\n  ...\n    __list_add_valid_or_report+0x9a/0xa0\n    proto_register+0x2b5/0x340\n    iso_init+0x23/0x150 [bluetooth]\n    set_iso_socket_func+0x68/0x1b0 [bluetooth]\n    kmem_cache_free+0x308/0x330\n    hci_sock_sendmsg+0x990/0x9e0 [bluetooth]\n    __sock_sendmsg+0x7b/0x80\n    sock_write_iter+0x9a/0x110\n    do_iter_readv_writev+0x11d/0x220\n    vfs_writev+0x180/0x3e0\n    do_writev+0xca/0x100\n  ...\n\nThis change removes the early return. The check for iso_debugfs being\nNULL was unnecessary, it is always NULL when iso_inited is false.(CVE-2024-50077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error\n\nThe `nouveau_dmem_copy_one` function ensures that the copy push command is\nsent to the device firmware but does not track whether it was executed\nsuccessfully.\n\nIn the case of a copy error (e.g., firmware or hardware failure), the\ncopy push command will be sent via the firmware channel, and\n`nouveau_dmem_copy_one` will likely report success, leading to the\n`migrate_to_ram` function returning a dirty HIGH_USER page to the user.\n\nThis can result in a security vulnerability, as a HIGH_USER page that may\ncontain sensitive or corrupted data could be returned to the user.\n\nTo prevent this vulnerability, we allocate a zero page. Thus, in case of\nan error, a non-dirty (zero) page will be returned to the user.(CVE-2024-50096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: fix one more kernel-infoleak in algo dumping\n\nDuring fuzz testing, the following issue was discovered:\n\nBUG: KMSAN: kernel-infoleak in _copy_to_iter+0x598/0x2a30\n _copy_to_iter+0x598/0x2a30\n __skb_datagram_iter+0x168/0x1060\n skb_copy_datagram_iter+0x5b/0x220\n netlink_recvmsg+0x362/0x1700\n sock_recvmsg+0x2dc/0x390\n __sys_recvfrom+0x381/0x6d0\n __x64_sys_recvfrom+0x130/0x200\n x64_sys_call+0x32c8/0x3cc0\n do_syscall_64+0xd8/0x1c0\n entry_SYSCALL_64_after_hwframe+0x79/0x81\n\nUninit was stored to memory at:\n copy_to_user_state_extra+0xcc1/0x1e00\n dump_one_state+0x28c/0x5f0\n xfrm_state_walk+0x548/0x11e0\n xfrm_dump_sa+0x1e0/0x840\n netlink_dump+0x943/0x1c40\n __netlink_dump_start+0x746/0xdb0\n xfrm_user_rcv_msg+0x429/0xc00\n netlink_rcv_skb+0x613/0x780\n xfrm_netlink_rcv+0x77/0xc0\n netlink_unicast+0xe90/0x1280\n netlink_sendmsg+0x126d/0x1490\n __sock_sendmsg+0x332/0x3d0\n ____sys_sendmsg+0x863/0xc30\n ___sys_sendmsg+0x285/0x3e0\n __x64_sys_sendmsg+0x2d6/0x560\n x64_sys_call+0x1316/0x3cc0\n do_syscall_64+0xd8/0x1c0\n entry_SYSCALL_64_after_hwframe+0x79/0x81\n\nUninit was created at:\n __kmalloc+0x571/0xd30\n attach_auth+0x106/0x3e0\n xfrm_add_sa+0x2aa0/0x4230\n xfrm_user_rcv_msg+0x832/0xc00\n netlink_rcv_skb+0x613/0x780\n xfrm_netlink_rcv+0x77/0xc0\n netlink_unicast+0xe90/0x1280\n netlink_sendmsg+0x126d/0x1490\n __sock_sendmsg+0x332/0x3d0\n ____sys_sendmsg+0x863/0xc30\n ___sys_sendmsg+0x285/0x3e0\n __x64_sys_sendmsg+0x2d6/0x560\n x64_sys_call+0x1316/0x3cc0\n do_syscall_64+0xd8/0x1c0\n entry_SYSCALL_64_after_hwframe+0x79/0x81\n\nBytes 328-379 of 732 are uninitialized\nMemory access of size 732 starts at ffff88800e18e000\nData copied to user address 00007ff30f48aff0\n\nCPU: 2 PID: 18167 Comm: syz-executor.0 Not tainted 6.8.11 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\n\nFixes copying of xfrm algorithms where some random\ndata of the structure fields can end up in userspace.\nPadding in structures may be filled with random (possibly sensitve)\ndata and should never be given directly to user-space.\n\nA similar issue was resolved in the commit\n8222d5910dae (\u0026quot;xfrm: Zero padding when dumping algos and encap\u0026quot;)\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2024-50110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Enable IRQ if do_ale() triggered in irq-enabled context\n\nUnaligned access exception can be triggered in irq-enabled context such\nas user mode, in this case do_ale() may call get_user() which may cause\nsleep. Then we will get:\n\n BUG: sleeping function called from invalid context at arch/loongarch/kernel/access-helper.h:7\n in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 129, name: modprobe\n preempt_count: 0, expected: 0\n RCU nest depth: 0, expected: 0\n CPU: 0 UID: 0 PID: 129 Comm: modprobe Tainted: G        W          6.12.0-rc1+ #1723\n Tainted: [W]=WARN\n Stack : 9000000105e0bd48 0000000000000000 9000000003803944 9000000105e08000\n         9000000105e0bc70 9000000105e0bc78 0000000000000000 0000000000000000\n         9000000105e0bc78 0000000000000001 9000000185e0ba07 9000000105e0b890\n         ffffffffffffffff 9000000105e0bc78 73924b81763be05b 9000000100194500\n         000000000000020c 000000000000000a 0000000000000000 0000000000000003\n         00000000000023f0 00000000000e1401 00000000072f8000 0000007ffbb0e260\n         0000000000000000 0000000000000000 9000000005437650 90000000055d5000\n         0000000000000000 0000000000000003 0000007ffbb0e1f0 0000000000000000\n         0000005567b00490 0000000000000000 9000000003803964 0000007ffbb0dfec\n         00000000000000b0 0000000000000007 0000000000000003 0000000000071c1d\n         ...\n Call Trace:\n [\u0026lt;9000000003803964\u0026gt;] show_stack+0x64/0x1a0\n [\u0026lt;9000000004c57464\u0026gt;] dump_stack_lvl+0x74/0xb0\n [\u0026lt;9000000003861ab4\u0026gt;] __might_resched+0x154/0x1a0\n [\u0026lt;900000000380c96c\u0026gt;] emulate_load_store_insn+0x6c/0xf60\n [\u0026lt;9000000004c58118\u0026gt;] do_ale+0x78/0x180\n [\u0026lt;9000000003801bc8\u0026gt;] handle_ale+0x128/0x1e0\n\nSo enable IRQ if unaligned access exception is triggered in irq-enabled\ncontext to fix it.(CVE-2024-50111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Unregister notifier on eswitch init failure\n\nIt otherwise remains registered and a subsequent attempt at eswitch\nenabling might trigger warnings of the sort:\n\n[  682.589148] ------------[ cut here ]------------\n[  682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered\n[  682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90\n[...snipped]\n[  682.610052] Call Trace:\n[  682.610369]  \u0026lt;TASK\u0026gt;\n[  682.610663]  ? __warn+0x7c/0x110\n[  682.611050]  ? notifier_chain_register+0x3e/0x90\n[  682.611556]  ? report_bug+0x148/0x170\n[  682.611977]  ? handle_bug+0x36/0x70\n[  682.612384]  ? exc_invalid_op+0x13/0x60\n[  682.612817]  ? asm_exc_invalid_op+0x16/0x20\n[  682.613284]  ? notifier_chain_register+0x3e/0x90\n[  682.613789]  atomic_notifier_chain_register+0x25/0x40\n[  682.614322]  mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core]\n[  682.614965]  mlx5_eswitch_enable+0xc9/0x100 [mlx5_core]\n[  682.615551]  mlx5_device_enable_sriov+0x25/0x340 [mlx5_core]\n[  682.616170]  mlx5_core_sriov_configure+0x50/0x170 [mlx5_core]\n[  682.616789]  sriov_numvfs_store+0xb0/0x1b0\n[  682.617248]  kernfs_fop_write_iter+0x117/0x1a0\n[  682.617734]  vfs_write+0x231/0x3f0\n[  682.618138]  ksys_write+0x63/0xe0\n[  682.618536]  do_syscall_64+0x4c/0x100\n[  682.618958]  entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2024-50136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix command bitmask initialization\n\nCommand bitmask have a dedicated bit for MANAGE_PAGES command, this bit\nisn\u0026apos;t Initialize during command bitmask Initialization, only during\nMANAGE_PAGES.\n\nIn addition, mlx5_cmd_trigger_completions() is trying to trigger\ncompletion for MANAGE_PAGES command as well.\n\nHence, in case health error occurred before any MANAGE_PAGES command\nhave been invoke (for example, during mlx5_enable_hca()),\nmlx5_cmd_trigger_completions() will try to trigger completion for\nMANAGE_PAGES command, which will result in null-ptr-deref error.[1]\n\nFix it by Initialize command bitmask correctly.\n\nWhile at it, re-write the code for better understanding.\n\n[1]\nBUG: KASAN: null-ptr-deref in mlx5_cmd_trigger_completions+0x1db/0x600 [mlx5_core]\nWrite of size 4 at addr 0000000000000214 by task kworker/u96:2/12078\nCPU: 10 PID: 12078 Comm: kworker/u96:2 Not tainted 6.9.0-rc2_for_upstream_debug_2024_04_07_19_01 #1\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\nWorkqueue: mlx5_health0000:08:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x7e/0xc0\n kasan_report+0xb9/0xf0\n kasan_check_range+0xec/0x190\n mlx5_cmd_trigger_completions+0x1db/0x600 [mlx5_core]\n mlx5_cmd_flush+0x94/0x240 [mlx5_core]\n enter_error_state+0x6c/0xd0 [mlx5_core]\n mlx5_fw_fatal_reporter_err_work+0xf3/0x480 [mlx5_core]\n process_one_work+0x787/0x1490\n ? lockdep_hardirqs_on_prepare+0x400/0x400\n ? pwq_dec_nr_in_flight+0xda0/0xda0\n ? assign_work+0x168/0x240\n worker_thread+0x586/0xd30\n ? rescuer_thread+0xae0/0xae0\n kthread+0x2df/0x3b0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x2d/0x70\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork_asm+0x11/0x20\n \u0026lt;/TASK\u0026gt;(CVE-2024-50147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: hda/cs8409: Fix possible NULL dereference\n\nIf snd_hda_gen_add_kctl fails to allocate memory and returns NULL, then\nNULL pointer dereference will occur in the next line.\n\nSince dolphin_fixups function is a hda_fixup function which is not supposed\nto return any errors, add simple check before dereference, ignore the fail.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-50160)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: qcom: camss: Remove use_count guard in stop_streaming\n\nThe use_count check was introduced so that multiple concurrent Raw Data\nInterfaces RDIs could be driven by different virtual channels VCs on the\nCSIPHY input driving the video pipeline.\n\nThis is an invalid use of use_count though as use_count pertains to the\nnumber of times a video entity has been opened by user-space not the number\nof active streams.\n\nIf use_count and stream-on count don\u0026apos;t agree then stop_streaming() will\nbreak as is currently the case and has become apparent when using CAMSS\nwith libcamera\u0026apos;s released softisp 0.3.\n\nThe use of use_count like this is a bit hacky and right now breaks regular\nusage of CAMSS for a single stream case. Stopping qcam results in the splat\nbelow, and then it cannot be started again and any attempts to do so fails\nwith -EBUSY.\n\n[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\n...\n[ 1265.510630] Call trace:\n[ 1265.510636]  __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\n[ 1265.510648]  vb2_core_streamoff+0x24/0xcc [videobuf2_common]\n[ 1265.510660]  vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2]\n[ 1265.510673]  v4l_streamoff+0x24/0x30 [videodev]\n[ 1265.510707]  __video_do_ioctl+0x190/0x3f4 [videodev]\n[ 1265.510732]  video_usercopy+0x304/0x8c4 [videodev]\n[ 1265.510757]  video_ioctl2+0x18/0x34 [videodev]\n[ 1265.510782]  v4l2_ioctl+0x40/0x60 [videodev]\n...\n[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state\n[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state\n[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st\n\nOne CAMSS specific way to handle multiple VCs on the same RDI might be:\n\n- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.\n- The video buffers are already associated with msm_vfeN_rdiX so\n  release video buffers when told to do so by stop_streaming.\n- Only release the power-domains for the CSIPHY, CSID and VFE when\n  their internal refcounts drop.\n\nEither way refusing to release video buffers based on use_count is\nerroneous and should be reverted. The silicon enabling code for selecting\nVCs is perfectly fine. Its a \u0026quot;known missing feature\u0026quot; that concurrent VCs\nwon\u0026apos;t work with CAMSS right now.\n\nInitial testing with this code didn\u0026apos;t show an error but, SoftISP and \u0026quot;real\u0026quot;\nusage with Google Hangouts breaks the upstream code pretty quickly, we need\nto do a partial revert and take another pass at VCs.\n\nThis commit partially reverts commit 89013969e232 (\u0026quot;media: camss: sm8250:\nPipeline starting and stopping for multiple virtual channels\u0026quot;)(CVE-2024-50175)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nremoteproc: k3-r5: Fix error handling when power-up failed\n\nBy simply bailing out, the driver was violating its rule and internal\nassumptions that either both or no rproc should be initialized. E.g.,\nthis could cause the first core to be available but not the second one,\nleading to crashes on its shutdown later on while trying to dereference\nthat second instance.(CVE-2024-50176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: imx: Remove CLK_SET_PARENT_GATE for DRAM mux for i.MX7D\n\nFor i.MX7D DRAM related mux clock, the clock source change should ONLY\nbe done done in low level asm code without accessing DRAM, and then\ncalling clk API to sync the HW clock status with clk tree, it should never\ntouch real clock source switch via clk API, so CLK_SET_PARENT_GATE flag\nshould NOT be added, otherwise, DRAM\u0026apos;s clock parent will be disabled when\nDRAM is active, and system will hang.(CVE-2024-50181)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Ensure DA_ID handling completion before deleting an NPIV instance\n\nDeleting an NPIV instance requires all fabric ndlps to be released before\nan NPIV\u0026apos;s resources can be torn down.  Failure to release fabric ndlps\nbeforehand opens kref imbalance race conditions.  Fix by forcing the DA_ID\nto complete synchronously with usage of wait_queue.(CVE-2024-50183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: amd_sfh: Switch to device-managed dmam_alloc_coherent()\n\nUsing the device-managed version allows to simplify clean-up in probe()\nerror path.\n\nAdditionally, this device-managed ensures proper cleanup, which helps to\nresolve memory errors, page faults, btrfs going read-only, and btrfs\ndisk corruption.(CVE-2024-50189)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfork: do not invoke uffd on fork if error occurs\n\nPatch series \u0026quot;fork: do not expose incomplete mm on fork\u0026quot;.\n\nDuring fork we may place the virtual memory address space into an\ninconsistent state before the fork operation is complete.\n\nIn addition, we may encounter an error during the fork operation that\nindicates that the virtual memory address space is invalidated.\n\nAs a result, we should not be exposing it in any way to external machinery\nthat might interact with the mm or VMAs, machinery that is not designed to\ndeal with incomplete state.\n\nWe specifically update the fork logic to defer khugepaged and ksm to the\nend of the operation and only to be invoked if no error arose, and\ndisallow uffd from observing fork events should an error have occurred.\n\n\nThis patch (of 2):\n\nCurrently on fork we expose the virtual address space of a process to\nuserland unconditionally if uffd is registered in VMAs, regardless of\nwhether an error arose in the fork.\n\nThis is performed in dup_userfaultfd_complete() which is invoked\nunconditionally, and performs two duties - invoking registered handlers\nfor the UFFD_EVENT_FORK event via dup_fctx(), and clearing down\nuserfaultfd_fork_ctx objects established in dup_userfaultfd().\n\nThis is problematic, because the virtual address space may not yet be\ncorrectly initialised if an error arose.\n\nThe change in commit d24062914837 (\u0026quot;fork: use __mt_dup() to duplicate\nmaple tree in dup_mmap()\u0026quot;) makes this more pertinent as we may be in a\nstate where entries in the maple tree are not yet consistent.\n\nWe address this by, on fork error, ensuring that we roll back state that\nwe would otherwise expect to clean up through the event being handled by\nuserland and perform the memory freeing duty otherwise performed by\ndup_userfaultfd_complete().\n\nWe do this by implementing a new function, dup_userfaultfd_fail(), which\nperforms the same loop, only decrementing reference counts.\n\nNote that we perform mmgrab() on the parent and child mm\u0026apos;s, however\nuserfaultfd_ctx_put() will mmdrop() this once the reference count drops to\nzero, so we will avoid memory leaks correctly here.(CVE-2024-50220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Vangogh: Fix kernel memory out of bounds write\n\nKASAN reports that the GPU metrics table allocated in\nvangogh_tables_init() is not large enough for the memset done in\nsmu_cmn_init_soft_gpu_metrics(). Condensed report follows:\n\n[   33.861314] BUG: KASAN: slab-out-of-bounds in smu_cmn_init_soft_gpu_metrics+0x73/0x200 [amdgpu]\n[   33.861799] Write of size 168 at addr ffff888129f59500 by task mangoapp/1067\n...\n[   33.861808] CPU: 6 UID: 1000 PID: 1067 Comm: mangoapp Tainted: G        W          6.12.0-rc4 #356 1a56f59a8b5182eeaf67eb7cb8b13594dd23b544\n[   33.861816] Tainted: [W]=WARN\n[   33.861818] Hardware name: Valve Galileo/Galileo, BIOS F7G0107 12/01/2023\n[   33.861822] Call Trace:\n[   33.861826]  \u0026lt;TASK\u0026gt;\n[   33.861829]  dump_stack_lvl+0x66/0x90\n[   33.861838]  print_report+0xce/0x620\n[   33.861853]  kasan_report+0xda/0x110\n[   33.862794]  kasan_check_range+0xfd/0x1a0\n[   33.862799]  __asan_memset+0x23/0x40\n[   33.862803]  smu_cmn_init_soft_gpu_metrics+0x73/0x200 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779]\n[   33.863306]  vangogh_get_gpu_metrics_v2_4+0x123/0xad0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779]\n[   33.864257]  vangogh_common_get_gpu_metrics+0xb0c/0xbc0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779]\n[   33.865682]  amdgpu_dpm_get_gpu_metrics+0xcc/0x110 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779]\n[   33.866160]  amdgpu_get_gpu_metrics+0x154/0x2d0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779]\n[   33.867135]  dev_attr_show+0x43/0xc0\n[   33.867147]  sysfs_kf_seq_show+0x1f1/0x3b0\n[   33.867155]  seq_read_iter+0x3f8/0x1140\n[   33.867173]  vfs_read+0x76c/0xc50\n[   33.867198]  ksys_read+0xfb/0x1d0\n[   33.867214]  do_syscall_64+0x90/0x160\n...\n[   33.867353] Allocated by task 378 on cpu 7 at 22.794876s:\n[   33.867358]  kasan_save_stack+0x33/0x50\n[   33.867364]  kasan_save_track+0x17/0x60\n[   33.867367]  __kasan_kmalloc+0x87/0x90\n[   33.867371]  vangogh_init_smc_tables+0x3f9/0x840 [amdgpu]\n[   33.867835]  smu_sw_init+0xa32/0x1850 [amdgpu]\n[   33.868299]  amdgpu_device_init+0x467b/0x8d90 [amdgpu]\n[   33.868733]  amdgpu_driver_load_kms+0x19/0xf0 [amdgpu]\n[   33.869167]  amdgpu_pci_probe+0x2d6/0xcd0 [amdgpu]\n[   33.869608]  local_pci_probe+0xda/0x180\n[   33.869614]  pci_device_probe+0x43f/0x6b0\n\nEmpirically we can confirm that the former allocates 152 bytes for the\ntable, while the latter memsets the 168 large block.\n\nRoot cause appears that when GPU metrics tables for v2_4 parts were added\nit was not considered to enlarge the table to fit.\n\nThe fix in this patch is rather \u0026quot;brute force\u0026quot; and perhaps later should be\ndone in a smarter way, by extracting and consolidating the part version to\nsize logic to a common helper, instead of brute forcing the largest\npossible allocation. Nevertheless, for now this works and fixes the out of\nbounds write.\n\nv2:\n * Drop impossible v3_0 case. (Mario)\n\n(cherry picked from commit 0880f58f9609f0200483a49429af0f050d281703)(CVE-2024-50221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: gts-helper: Fix memory leaks in iio_gts_build_avail_scale_table()\n\nmodprobe iio-test-gts and rmmod it, then the following memory leak\noccurs:\n\n\tunreferenced object 0xffffff80c810be00 (size 64):\n\t  comm \u0026quot;kunit_try_catch\u0026quot;, pid 1654, jiffies 4294913981\n\t  hex dump (first 32 bytes):\n\t    02 00 00 00 08 00 00 00 20 00 00 00 40 00 00 00  ........ ...@...\n\t    80 00 00 00 00 02 00 00 00 04 00 00 00 08 00 00  ................\n\t  backtrace (crc a63d875e):\n\t    [\u0026lt;0000000028c1b3c2\u0026gt;] kmemleak_alloc+0x34/0x40\n\t    [\u0026lt;000000001d6ecc87\u0026gt;] __kmalloc_noprof+0x2bc/0x3c0\n\t    [\u0026lt;00000000393795c1\u0026gt;] devm_iio_init_iio_gts+0x4b4/0x16f4\n\t    [\u0026lt;0000000071bb4b09\u0026gt;] 0xffffffdf052a62e0\n\t    [\u0026lt;000000000315bc18\u0026gt;] 0xffffffdf052a6488\n\t    [\u0026lt;00000000f9dc55b5\u0026gt;] kunit_try_run_case+0x13c/0x3ac\n\t    [\u0026lt;00000000175a3fd4\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec\n\t    [\u0026lt;00000000f505065d\u0026gt;] kthread+0x2e8/0x374\n\t    [\u0026lt;00000000bbfb0e5d\u0026gt;] ret_from_fork+0x10/0x20\n\tunreferenced object 0xffffff80cbfe9e70 (size 16):\n\t  comm \u0026quot;kunit_try_catch\u0026quot;, pid 1658, jiffies 4294914015\n\t  hex dump (first 16 bytes):\n\t    10 00 00 00 40 00 00 00 80 00 00 00 00 00 00 00  ....@...........\n\t  backtrace (crc 857f0cb4):\n\t    [\u0026lt;0000000028c1b3c2\u0026gt;] kmemleak_alloc+0x34/0x40\n\t    [\u0026lt;000000001d6ecc87\u0026gt;] __kmalloc_noprof+0x2bc/0x3c0\n\t    [\u0026lt;00000000393795c1\u0026gt;] devm_iio_init_iio_gts+0x4b4/0x16f4\n\t    [\u0026lt;0000000071bb4b09\u0026gt;] 0xffffffdf052a62e0\n\t    [\u0026lt;000000007d089d45\u0026gt;] 0xffffffdf052a6864\n\t    [\u0026lt;00000000f9dc55b5\u0026gt;] kunit_try_run_case+0x13c/0x3ac\n\t    [\u0026lt;00000000175a3fd4\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec\n\t    [\u0026lt;00000000f505065d\u0026gt;] kthread+0x2e8/0x374\n\t    [\u0026lt;00000000bbfb0e5d\u0026gt;] ret_from_fork+0x10/0x20\n\t......\n\nIt includes 5*5 times \u0026quot;size 64\u0026quot; memory leaks, which correspond to 5 times\ntest_init_iio_gain_scale() calls with gts_test_gains size 10 (10*size(int))\nand gts_test_itimes size 5. It also includes 5*1 times \u0026quot;size 16\u0026quot;\nmemory leak, which correspond to one time __test_init_iio_gain_scale()\ncall with gts_test_gains_gain_low size 3 (3*size(int)) and gts_test_itimes\nsize 5.\n\nThe reason is that the per_time_gains[i] is not freed which is allocated in\nthe \u0026quot;gts-\u0026gt;num_itime\u0026quot; for loop in iio_gts_build_avail_scale_table().(CVE-2024-50231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: adc: ad7124: fix division by zero in ad7124_set_channel_odr()\n\nIn the ad7124_write_raw() function, parameter val can potentially\nbe zero. This may lead to a division by zero when DIV_ROUND_CLOSEST()\nis called within ad7124_set_channel_odr(). The ad7124_write_raw()\nfunction is invoked through the sequence: iio_write_channel_raw() -\u0026gt;\niio_write_channel_attribute() -\u0026gt; iio_channel_write(), with no checks\nin place to ensure val is non-zero.(CVE-2024-50232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nphy: qcom: qmp-usb: fix NULL-deref on runtime suspend\n\nCommit 413db06c05e7 (\u0026quot;phy: qcom-qmp-usb: clean up probe initialisation\u0026quot;)\nremoved most users of the platform device driver data, but mistakenly\nalso removed the initialisation despite the data still being used in the\nruntime PM callbacks.\n\nRestore the driver data initialisation at probe to avoid a NULL-pointer\ndereference on runtime suspend.\n\nApparently no one uses runtime PM, which currently needs to be enabled\nmanually through sysfs, with this driver.(CVE-2024-50240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_ipip: Fix memory leak when changing remote IPv6 address\n\nThe device stores IPv6 addresses that are used for encapsulation in\nlinear memory that is managed by the driver.\n\nChanging the remote address of an ip6gre net device never worked\nproperly, but since cited commit the following reproducer [1] would\nresult in a warning [2] and a memory leak [3]. The problem is that the\nnew remote address is never added by the driver to its hash table (and\ntherefore the device) and the old address is never removed from it.\n\nFix by programming the new address when the configuration of the ip6gre\nnet device changes and removing the old one. If the address did not\nchange, then the above would result in increasing the reference count of\nthe address and then decreasing it.\n\n[1]\n # ip link add name bla up type ip6gre local 2001:db8:1::1 remote 2001:db8:2::1 tos inherit ttl inherit\n # ip link set dev bla type ip6gre remote 2001:db8:3::1\n # ip link del dev bla\n # devlink dev reload pci/0000:01:00.0\n\n[2]\nWARNING: CPU: 0 PID: 1682 at drivers/net/ethernet/mellanox/mlxsw/spectrum.c:3002 mlxsw_sp_ipv6_addr_put+0x140/0x1d0\nModules linked in:\nCPU: 0 UID: 0 PID: 1682 Comm: ip Not tainted 6.12.0-rc3-custom-g86b5b55bc835 #151\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nRIP: 0010:mlxsw_sp_ipv6_addr_put+0x140/0x1d0\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlxsw_sp_router_netdevice_event+0x55f/0x1240\n notifier_call_chain+0x5a/0xd0\n call_netdevice_notifiers_info+0x39/0x90\n unregister_netdevice_many_notify+0x63e/0x9d0\n rtnl_dellink+0x16b/0x3a0\n rtnetlink_rcv_msg+0x142/0x3f0\n netlink_rcv_skb+0x50/0x100\n netlink_unicast+0x242/0x390\n netlink_sendmsg+0x1de/0x420\n ____sys_sendmsg+0x2bd/0x320\n ___sys_sendmsg+0x9a/0xe0\n __sys_sendmsg+0x7a/0xd0\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n[3]\nunreferenced object 0xffff898081f597a0 (size 32):\n  comm \u0026quot;ip\u0026quot;, pid 1626, jiffies 4294719324\n  hex dump (first 32 bytes):\n    20 01 0d b8 00 02 00 00 00 00 00 00 00 00 00 01   ...............\n    21 49 61 83 80 89 ff ff 00 00 00 00 01 00 00 00  !Ia.............\n  backtrace (crc fd9be911):\n    [\u0026lt;00000000df89c55d\u0026gt;] __kmalloc_cache_noprof+0x1da/0x260\n    [\u0026lt;00000000ff2a1ddb\u0026gt;] mlxsw_sp_ipv6_addr_kvdl_index_get+0x281/0x340\n    [\u0026lt;000000009ddd445d\u0026gt;] mlxsw_sp_router_netdevice_event+0x47b/0x1240\n    [\u0026lt;00000000743e7757\u0026gt;] notifier_call_chain+0x5a/0xd0\n    [\u0026lt;000000007c7b9e13\u0026gt;] call_netdevice_notifiers_info+0x39/0x90\n    [\u0026lt;000000002509645d\u0026gt;] register_netdevice+0x5f7/0x7a0\n    [\u0026lt;00000000c2e7d2a9\u0026gt;] ip6gre_newlink_common.isra.0+0x65/0x130\n    [\u0026lt;0000000087cd6d8d\u0026gt;] ip6gre_newlink+0x72/0x120\n    [\u0026lt;000000004df7c7cc\u0026gt;] rtnl_newlink+0x471/0xa20\n    [\u0026lt;0000000057ed632a\u0026gt;] rtnetlink_rcv_msg+0x142/0x3f0\n    [\u0026lt;0000000032e0d5b5\u0026gt;] netlink_rcv_skb+0x50/0x100\n    [\u0026lt;00000000908bca63\u0026gt;] netlink_unicast+0x242/0x390\n    [\u0026lt;00000000cdbe1c87\u0026gt;] netlink_sendmsg+0x1de/0x420\n    [\u0026lt;0000000011db153e\u0026gt;] ____sys_sendmsg+0x2bd/0x320\n    [\u0026lt;000000003b6d53eb\u0026gt;] ___sys_sendmsg+0x9a/0xe0\n    [\u0026lt;00000000cae27c62\u0026gt;] __sys_sendmsg+0x7a/0xd0(CVE-2024-50252)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6()\n\nI got a syzbot report without a repro [1] crashing in nf_send_reset6()\n\nI think the issue is that dev-\u0026gt;hard_header_len is zero, and we attempt\nlater to push an Ethernet header.\n\nUse LL_MAX_HEADER, as other functions in net/ipv6/netfilter/nf_reject_ipv6.c.\n\n[1]\n\nskbuff: skb_under_panic: text:ffffffff89b1d008 len:74 put:14 head:ffff88803123aa00 data:ffff88803123a9f2 tail:0x3c end:0x140 dev:syz_tun\n kernel BUG at net/core/skbuff.c:206 !\nOops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 0 UID: 0 PID: 7373 Comm: syz.1.568 Not tainted 6.12.0-rc2-syzkaller-00631-g6d858708d465 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024\n RIP: 0010:skb_panic net/core/skbuff.c:206 [inline]\n RIP: 0010:skb_under_panic+0x14b/0x150 net/core/skbuff.c:216\nCode: 0d 8d 48 c7 c6 60 a6 29 8e 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 41 54 41 57 41 56 e8 ba 30 38 02 48 83 c4 20 90 \u0026lt;0f\u0026gt; 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3\nRSP: 0018:ffffc900045269b0 EFLAGS: 00010282\nRAX: 0000000000000088 RBX: dffffc0000000000 RCX: cd66dacdc5d8e800\nRDX: 0000000000000000 RSI: 0000000000000200 RDI: 0000000000000000\nRBP: ffff88802d39a3d0 R08: ffffffff8174afec R09: 1ffff920008a4ccc\nR10: dffffc0000000000 R11: fffff520008a4ccd R12: 0000000000000140\nR13: ffff88803123aa00 R14: ffff88803123a9f2 R15: 000000000000003c\nFS:  00007fdbee5ff6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 000000005d322000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_push+0xe5/0x100 net/core/skbuff.c:2636\n  eth_header+0x38/0x1f0 net/ethernet/eth.c:83\n  dev_hard_header include/linux/netdevice.h:3208 [inline]\n  nf_send_reset6+0xce6/0x1270 net/ipv6/netfilter/nf_reject_ipv6.c:358\n  nft_reject_inet_eval+0x3b9/0x690 net/netfilter/nft_reject_inet.c:48\n  expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]\n  nft_do_chain+0x4ad/0x1da0 net/netfilter/nf_tables_core.c:288\n  nft_do_chain_inet+0x418/0x6b0 net/netfilter/nft_chain_filter.c:161\n  nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]\n  nf_hook_slow+0xc3/0x220 net/netfilter/core.c:626\n  nf_hook include/linux/netfilter.h:269 [inline]\n  NF_HOOK include/linux/netfilter.h:312 [inline]\n  br_nf_pre_routing_ipv6+0x63e/0x770 net/bridge/br_netfilter_ipv6.c:184\n  nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]\n  nf_hook_bridge_pre net/bridge/br_input.c:277 [inline]\n  br_handle_frame+0x9fd/0x1530 net/bridge/br_input.c:424\n  __netif_receive_skb_core+0x13e8/0x4570 net/core/dev.c:5562\n  __netif_receive_skb_one_core net/core/dev.c:5666 [inline]\n  __netif_receive_skb+0x12f/0x650 net/core/dev.c:5781\n  netif_receive_skb_internal net/core/dev.c:5867 [inline]\n  netif_receive_skb+0x1e8/0x890 net/core/dev.c:5926\n  tun_rx_batched+0x1b7/0x8f0 drivers/net/tun.c:1550\n  tun_get_user+0x3056/0x47e0 drivers/net/tun.c:2007\n  tun_chr_write_iter+0x10d/0x1f0 drivers/net/tun.c:2053\n  new_sync_write fs/read_write.c:590 [inline]\n  vfs_write+0xa6d/0xc90 fs/read_write.c:683\n  ksys_write+0x183/0x2b0 fs/read_write.c:736\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7fdbeeb7d1ff\nCode: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 c9 8d 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 1c 8e 02 00 48\nRSP: 002b:00007fdbee5ff000 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 00007fdbeed36058 RCX: 00007fdbeeb7d1ff\nRDX: 000000000000008e RSI: 0000000020000040 RDI: 00000000000000c8\nRBP: 00007fdbeebf12be R08: 0000000\n---truncated---(CVE-2024-50256)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: arc: fix the device for dma_map_single/dma_unmap_single\n\nThe ndev-\u0026gt;dev and pdev-\u0026gt;dev aren\u0026apos;t the same device, use ndev-\u0026gt;dev.parent\nwhich has dma_mask, ndev-\u0026gt;dev.parent is just pdev-\u0026gt;dev.\nOr it would cause the following issue:\n\n[   39.933526] ------------[ cut here ]------------\n[   39.938414] WARNING: CPU: 1 PID: 501 at kernel/dma/mapping.c:149 dma_map_page_attrs+0x90/0x1f8(CVE-2024-50295)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: fix kernel crash when uninstalling driver\n\nWhen the driver is uninstalled and the VF is disabled concurrently, a\nkernel crash occurs. The reason is that the two actions call function\npci_disable_sriov(). The num_VFs is checked to determine whether to\nrelease the corresponding resources. During the second calling, num_VFs\nis not 0 and the resource release function is called. However, the\ncorresponding resource has been released during the first invoking.\nTherefore, the problem occurs:\n\n[15277.839633][T50670] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020\n...\n[15278.131557][T50670] Call trace:\n[15278.134686][T50670]  klist_put+0x28/0x12c\n[15278.138682][T50670]  klist_del+0x14/0x20\n[15278.142592][T50670]  device_del+0xbc/0x3c0\n[15278.146676][T50670]  pci_remove_bus_device+0x84/0x120\n[15278.151714][T50670]  pci_stop_and_remove_bus_device+0x6c/0x80\n[15278.157447][T50670]  pci_iov_remove_virtfn+0xb4/0x12c\n[15278.162485][T50670]  sriov_disable+0x50/0x11c\n[15278.166829][T50670]  pci_disable_sriov+0x24/0x30\n[15278.171433][T50670]  hnae3_unregister_ae_algo_prepare+0x60/0x90 [hnae3]\n[15278.178039][T50670]  hclge_exit+0x28/0xd0 [hclge]\n[15278.182730][T50670]  __se_sys_delete_module.isra.0+0x164/0x230\n[15278.188550][T50670]  __arm64_sys_delete_module+0x1c/0x30\n[15278.193848][T50670]  invoke_syscall+0x50/0x11c\n[15278.198278][T50670]  el0_svc_common.constprop.0+0x158/0x164\n[15278.203837][T50670]  do_el0_svc+0x34/0xcc\n[15278.207834][T50670]  el0_svc+0x20/0x30\n\nFor details, see the following figure.\n\n     rmmod hclge              disable VFs\n----------------------------------------------------\nhclge_exit()            sriov_numvfs_store()\n  ...                     device_lock()\n  pci_disable_sriov()     hns3_pci_sriov_configure()\n                            pci_disable_sriov()\n                              sriov_disable()\n    sriov_disable()             if !num_VFs :\n      if !num_VFs :               return;\n        return;                 sriov_del_vfs()\n      sriov_del_vfs()             ...\n        ...                       klist_put()\n        klist_put()               ...\n        ...                     num_VFs = 0;\n      num_VFs = 0;        device_unlock();\n\nIn this patch, when driver is removing, we get the device_lock()\nto protect num_VFs, just like sriov_numvfs_store().(CVE-2024-50296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find()\n\nThe per-netns IP tunnel hash table is protected by the RTNL mutex and\nip_tunnel_find() is only called from the control path where the mutex is\ntaken.\n\nAdd a lockdep expression to hlist_for_each_entry_rcu() in\nip_tunnel_find() in order to validate that the mutex is held and to\nsilence the suspicious RCU usage warning [1].\n\n[1]\nWARNING: suspicious RCU usage\n6.12.0-rc3-custom-gd95d9a31aceb #139 Not tainted\n-----------------------------\nnet/ipv4/ip_tunnel.c:221 RCU-list traversed in non-reader section!!\n\nother info that might help us debug this:\n\nrcu_scheduler_active = 2, debug_locks = 1\n1 lock held by ip/362:\n #0: ffffffff86fc7cb0 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x377/0xf60\n\nstack backtrace:\nCPU: 12 UID: 0 PID: 362 Comm: ip Not tainted 6.12.0-rc3-custom-gd95d9a31aceb #139\nHardware name: Bochs Bochs, BIOS Bochs 01/01/2011\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xba/0x110\n lockdep_rcu_suspicious.cold+0x4f/0xd6\n ip_tunnel_find+0x435/0x4d0\n ip_tunnel_newlink+0x517/0x7a0\n ipgre_newlink+0x14c/0x170\n __rtnl_newlink+0x1173/0x19c0\n rtnl_newlink+0x6c/0xa0\n rtnetlink_rcv_msg+0x3cc/0xf60\n netlink_rcv_skb+0x171/0x450\n netlink_unicast+0x539/0x7f0\n netlink_sendmsg+0x8c1/0xd80\n ____sys_sendmsg+0x8f9/0xc20\n ___sys_sendmsg+0x197/0x1e0\n __sys_sendmsg+0x122/0x1f0\n do_syscall_64+0xbb/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-50304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/hdcp: Add encoder check in intel_hdcp_get_capability\n\nSometimes during hotplug scenario or suspend/resume scenario encoder is\nnot always initialized when intel_hdcp_get_capability add\na check to avoid kernel null pointer dereference.(CVE-2024-53051)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data\n\nIn case the non-paged data of a SKB carries protocol header and protocol\npayload to be transmitted on a certain platform that the DMA AXI address\nwidth is configured to 40-bit/48-bit, or the size of the non-paged data\nis bigger than TSO_MAX_BUFF_SIZE on a certain platform that the DMA AXI\naddress width is configured to 32-bit, then this SKB requires at least\ntwo DMA transmit descriptors to serve it.\n\nFor example, three descriptors are allocated to split one DMA buffer\nmapped from one piece of non-paged data:\n    dma_desc[N + 0],\n    dma_desc[N + 1],\n    dma_desc[N + 2].\nThen three elements of tx_q-\u0026gt;tx_skbuff_dma[] will be allocated to hold\nextra information to be reused in stmmac_tx_clean():\n    tx_q-\u0026gt;tx_skbuff_dma[N + 0],\n    tx_q-\u0026gt;tx_skbuff_dma[N + 1],\n    tx_q-\u0026gt;tx_skbuff_dma[N + 2].\nNow we focus on tx_q-\u0026gt;tx_skbuff_dma[entry].buf, which is the DMA buffer\naddress returned by DMA mapping call. stmmac_tx_clean() will try to\nunmap the DMA buffer _ONLY_IF_ tx_q-\u0026gt;tx_skbuff_dma[entry].buf\nis a valid buffer address.\n\nThe expected behavior that saves DMA buffer address of this non-paged\ndata to tx_q-\u0026gt;tx_skbuff_dma[entry].buf is:\n    tx_q-\u0026gt;tx_skbuff_dma[N + 0].buf = NULL;\n    tx_q-\u0026gt;tx_skbuff_dma[N + 1].buf = NULL;\n    tx_q-\u0026gt;tx_skbuff_dma[N + 2].buf = dma_map_single();\nUnfortunately, the current code misbehaves like this:\n    tx_q-\u0026gt;tx_skbuff_dma[N + 0].buf = dma_map_single();\n    tx_q-\u0026gt;tx_skbuff_dma[N + 1].buf = NULL;\n    tx_q-\u0026gt;tx_skbuff_dma[N + 2].buf = NULL;\n\nOn the stmmac_tx_clean() side, when dma_desc[N + 0] is closed by the\nDMA engine, tx_q-\u0026gt;tx_skbuff_dma[N + 0].buf is a valid buffer address\nobviously, then the DMA buffer will be unmapped immediately.\nThere may be a rare case that the DMA engine does not finish the\npending dma_desc[N + 1], dma_desc[N + 2] yet. Now things will go\nhorribly wrong, DMA is going to access a unmapped/unreferenced memory\nregion, corrupted data will be transmited or iommu fault will be\ntriggered :(\n\nIn contrast, the for-loop that maps SKB fragments behaves perfectly\nas expected, and that is how the driver should do for both non-paged\ndata and paged frags actually.\n\nThis patch corrects DMA map/unmap sequences by fixing the array index\nfor tx_q-\u0026gt;tx_skbuff_dma[entry].buf when assigning DMA buffer address.\n\nTested and verified on DWXGMAC CORE 3.20a(CVE-2024-53058)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx\n\nAs the introduction of the support for vsock and unix sockets in sockmap,\ntls_sw_has_ctx_tx/rx cannot presume the socket passed in must be IS_ICSK.\nvsock and af_unix sockets have vsock_sock and unix_sock instead of\ninet_connection_sock. For these sockets, tls_get_ctx may return an invalid\npointer and cause page fault in function tls_sw_ctx_rx.\n\nBUG: unable to handle page fault for address: 0000000000040030\nWorkqueue: vsock-loopback vsock_loopback_work\nRIP: 0010:sk_psock_strp_data_ready+0x23/0x60\nCall Trace:\n ? __die+0x81/0xc3\n ? no_context+0x194/0x350\n ? do_page_fault+0x30/0x110\n ? async_page_fault+0x3e/0x50\n ? sk_psock_strp_data_ready+0x23/0x60\n virtio_transport_recv_pkt+0x750/0x800\n ? update_load_avg+0x7e/0x620\n vsock_loopback_work+0xd0/0x100\n process_one_work+0x1a7/0x360\n worker_thread+0x30/0x390\n ? create_worker+0x1a0/0x1a0\n kthread+0x112/0x130\n ? __kthread_cancel_work+0x40/0x40\n ret_from_fork+0x1f/0x40\n\nv2:\n  - Add IS_ICSK check\nv3:\n  - Update the commits in Fixes(CVE-2024-53091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: defer partition scanning\n\nWe need to suppress the partition scan from occuring within the\ncontroller\u0026apos;s scan_work context. If a path error occurs here, the IO will\nwait until a path becomes available or all paths are torn down, but that\naction also occurs within scan_work, so it would deadlock. Defer the\npartion scan to a different context that does not block scan_work.(CVE-2024-53093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/siw: Add sendpage_ok() check to disable MSG_SPLICE_PAGES\n\nWhile running ISER over SIW, the initiator machine encounters a warning\nfrom skb_splice_from_iter() indicating that a slab page is being used in\nsend_page. To address this, it is better to add a sendpage_ok() check\nwithin the driver itself, and if it returns 0, then MSG_SPLICE_PAGES flag\nshould be disabled before entering the network stack.\n\nA similar issue has been discussed for NVMe in this thread:\nhttps://lore.kernel.org/all/20240530142417.146696-1-ofir.gal@volumez.com/\n\n  WARNING: CPU: 0 PID: 5342 at net/core/skbuff.c:7140 skb_splice_from_iter+0x173/0x320\n  Call Trace:\n   tcp_sendmsg_locked+0x368/0xe40\n   siw_tx_hdt+0x695/0xa40 [siw]\n   siw_qp_sq_process+0x102/0xb00 [siw]\n   siw_sq_resume+0x39/0x110 [siw]\n   siw_run_sq+0x74/0x160 [siw]\n   kthread+0xd2/0x100\n   ret_from_fork+0x34/0x40\n   ret_from_fork_asm+0x1a/0x30(CVE-2024-53094)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: krealloc: Fix MTE false alarm in __do_krealloc\n\nThis patch addresses an issue introduced by commit 1a83a716ec233 (\u0026quot;mm:\nkrealloc: consider spare memory for __GFP_ZERO\u0026quot;) which causes MTE\n(Memory Tagging Extension) to falsely report a slab-out-of-bounds error.\n\nThe problem occurs when zeroing out spare memory in __do_krealloc. The\noriginal code only considered software-based KASAN and did not account\nfor MTE. It does not reset the KASAN tag before calling memset, leading\nto a mismatch between the pointer tag and the memory tag, resulting\nin a false positive.\n\nExample of the error:\n==================================================================\nswapper/0: BUG: KASAN: slab-out-of-bounds in __memset+0x84/0x188\nswapper/0: Write at addr f4ffff8005f0fdf0 by task swapper/0/1\nswapper/0: Pointer tag: [f4], memory tag: [fe]\nswapper/0:\nswapper/0: CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.\nswapper/0: Hardware name: MT6991(ENG) (DT)\nswapper/0: Call trace:\nswapper/0:  dump_backtrace+0xfc/0x17c\nswapper/0:  show_stack+0x18/0x28\nswapper/0:  dump_stack_lvl+0x40/0xa0\nswapper/0:  print_report+0x1b8/0x71c\nswapper/0:  kasan_report+0xec/0x14c\nswapper/0:  __do_kernel_fault+0x60/0x29c\nswapper/0:  do_bad_area+0x30/0xdc\nswapper/0:  do_tag_check_fault+0x20/0x34\nswapper/0:  do_mem_abort+0x58/0x104\nswapper/0:  el1_abort+0x3c/0x5c\nswapper/0:  el1h_64_sync_handler+0x80/0xcc\nswapper/0:  el1h_64_sync+0x68/0x6c\nswapper/0:  __memset+0x84/0x188\nswapper/0:  btf_populate_kfunc_set+0x280/0x3d8\nswapper/0:  __register_btf_kfunc_id_set+0x43c/0x468\nswapper/0:  register_btf_kfunc_id_set+0x48/0x60\nswapper/0:  register_nf_nat_bpf+0x1c/0x40\nswapper/0:  nf_nat_init+0xc0/0x128\nswapper/0:  do_one_initcall+0x184/0x464\nswapper/0:  do_initcall_level+0xdc/0x1b0\nswapper/0:  do_initcalls+0x70/0xc0\nswapper/0:  do_basic_setup+0x1c/0x28\nswapper/0:  kernel_init_freeable+0x144/0x1b8\nswapper/0:  kernel_init+0x20/0x1a8\nswapper/0:  ret_from_fork+0x10/0x20\n==================================================================(CVE-2024-53097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: tcp: avoid race between queue_lock lock and destroy\n\nCommit 76d54bf20cdc (\u0026quot;nvme-tcp: don\u0026apos;t access released socket during\nerror recovery\u0026quot;) added a mutex_lock() call for the queue-\u0026gt;queue_lock\nin nvme_tcp_get_address(). However, the mutex_lock() races with\nmutex_destroy() in nvme_tcp_free_queue(), and causes the WARN below.\n\nDEBUG_LOCKS_WARN_ON(lock-\u0026gt;magic != lock)\nWARNING: CPU: 3 PID: 34077 at kernel/locking/mutex.c:587 __mutex_lock+0xcf0/0x1220\nModules linked in: nvmet_tcp nvmet nvme_tcp nvme_fabrics iw_cm ib_cm ib_core pktcdvd nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables qrtr sunrpc ppdev 9pnet_virtio 9pnet pcspkr netfs parport_pc parport e1000 i2c_piix4 i2c_smbus loop fuse nfnetlink zram bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper xfs drm sym53c8xx floppy nvme scsi_transport_spi nvme_core nvme_auth serio_raw ata_generic pata_acpi dm_multipath qemu_fw_cfg [last unloaded: ib_uverbs]\nCPU: 3 UID: 0 PID: 34077 Comm: udisksd Not tainted 6.11.0-rc7 #319\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:__mutex_lock+0xcf0/0x1220\nCode: 08 84 d2 0f 85 c8 04 00 00 8b 15 ef b6 c8 01 85 d2 0f 85 78 f4 ff ff 48 c7 c6 20 93 ee af 48 c7 c7 60 91 ee af e8 f0 a7 6d fd \u0026lt;0f\u0026gt; 0b e9 5e f4 ff ff 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1\nRSP: 0018:ffff88811305f760 EFLAGS: 00010286\nRAX: 0000000000000000 RBX: ffff88812c652058 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001\nRBP: ffff88811305f8b0 R08: 0000000000000001 R09: ffffed1075c36341\nR10: ffff8883ae1b1a0b R11: 0000000000010498 R12: 0000000000000000\nR13: 0000000000000000 R14: dffffc0000000000 R15: ffff88812c652058\nFS:  00007f9713ae4980(0000) GS:ffff8883ae180000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fcd78483c7c CR3: 0000000122c38000 CR4: 00000000000006f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __warn.cold+0x5b/0x1af\n ? __mutex_lock+0xcf0/0x1220\n ? report_bug+0x1ec/0x390\n ? handle_bug+0x3c/0x80\n ? exc_invalid_op+0x13/0x40\n ? asm_exc_invalid_op+0x16/0x20\n ? __mutex_lock+0xcf0/0x1220\n ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp]\n ? __pfx___mutex_lock+0x10/0x10\n ? __lock_acquire+0xd6a/0x59e0\n ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp]\n nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp]\n ? __pfx_nvme_tcp_get_address+0x10/0x10 [nvme_tcp]\n nvme_sysfs_show_address+0x81/0xc0 [nvme_core]\n dev_attr_show+0x42/0x80\n ? __asan_memset+0x1f/0x40\n sysfs_kf_seq_show+0x1f0/0x370\n seq_read_iter+0x2cb/0x1130\n ? rw_verify_area+0x3b1/0x590\n ? __mutex_lock+0x433/0x1220\n vfs_read+0x6a6/0xa20\n ? lockdep_hardirqs_on+0x78/0x100\n ? __pfx_vfs_read+0x10/0x10\n ksys_read+0xf7/0x1d0\n ? __pfx_ksys_read+0x10/0x10\n ? __x64_sys_openat+0x105/0x1d0\n do_syscall_64+0x93/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? __pfx_ksys_read+0x10/0x10\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? do_syscall_64+0x9f/0x180\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7f9713f55cfa\nCode: 55 48 89 e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 e8 74 f8 ff 48 8b 55 e8 48 8b 75 f0 4\n---truncated---(CVE-2024-53100)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nima: fix buffer overrun in ima_eventdigest_init_common\n\nFunction ima_eventdigest_init() calls ima_eventdigest_init_common()\nwith HASH_ALGO__LAST which is then used to access the array\nhash_digest_size[] leading to buffer overrun. Have a conditional\nstatement to handle this.(CVE-2024-53106)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnommu: pass NULL argument to vma_iter_prealloc()\n\nWhen deleting a vma entry from a maple tree, it has to pass NULL to\nvma_iter_prealloc() in order to calculate internal state of the tree, but\nit passed a wrong argument.  As a result, nommu kernels crashed upon\naccessing a vma iterator, such as acct_collect() reading the size of vma\nentries after do_munmap().\n\nThis commit fixes this issue by passing a right argument to the\npreallocation call.(CVE-2024-53109)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: fix NULL pointer dereference in alloc_pages_bulk_noprof\n\nWe triggered a NULL pointer dereference for ac.preferred_zoneref-\u0026gt;zone in\nalloc_pages_bulk_noprof() when the task is migrated between cpusets.\n\nWhen cpuset is enabled, in prepare_alloc_pages(), ac-\u0026gt;nodemask may be\n\u0026amp;current-\u0026gt;mems_allowed.  when first_zones_zonelist() is called to find\npreferred_zoneref, the ac-\u0026gt;nodemask may be modified concurrently if the\ntask is migrated between different cpusets.  Assuming we have 2 NUMA Node,\nwhen traversing Node1 in ac-\u0026gt;zonelist, the nodemask is 2, and when\ntraversing Node2 in ac-\u0026gt;zonelist, the nodemask is 1.  As a result, the\nac-\u0026gt;preferred_zoneref points to NULL zone.\n\nIn alloc_pages_bulk_noprof(), for_each_zone_zonelist_nodemask() finds a\nallowable zone and calls zonelist_node_idx(ac.preferred_zoneref), leading\nto NULL pointer dereference.\n\n__alloc_pages_noprof() fixes this issue by checking NULL pointer in commit\nea57485af8f4 (\u0026quot;mm, page_alloc: fix check for NULL preferred_zone\u0026quot;) and\ncommit df76cee6bbeb (\u0026quot;mm, page_alloc: remove redundant checks from alloc\nfastpath\u0026quot;).\n\nTo fix it, check NULL pointer for preferred_zoneref-\u0026gt;zone.(CVE-2024-53113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio/vsock: Fix accept_queue memory leak\n\nAs the final stages of socket destruction may be delayed, it is possible\nthat virtio_transport_recv_listen() will be called after the accept_queue\nhas been flushed, but before the SOCK_DONE flag has been set. As a result,\nsockets enqueued after the flush would remain unremoved, leading to a\nmemory leak.\n\nvsock_release\n  __vsock_release\n    lock\n    virtio_transport_release\n      virtio_transport_close\n        schedule_delayed_work(close_work)\n    sk_shutdown = SHUTDOWN_MASK\n(!) flush accept_queue\n    release\n                                        virtio_transport_recv_pkt\n                                          vsock_find_bound_socket\n                                          lock\n                                          if flag(SOCK_DONE) return\n                                          virtio_transport_recv_listen\n                                            child = vsock_create_connected\n                                      (!)   vsock_enqueue_accept(child)\n                                          release\nclose_work\n  lock\n  virtio_transport_do_close\n    set_flag(SOCK_DONE)\n    virtio_transport_remove_sock\n      vsock_remove_sock\n        vsock_remove_bound\n  release\n\nIntroduce a sk_shutdown check to disallow vsock_enqueue_accept() during\nsocket destruction.\n\nunreferenced object 0xffff888109e3f800 (size 2040):\n  comm \u0026quot;kworker/5:2\u0026quot;, pid 371, jiffies 4294940105\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    28 00 0b 40 00 00 00 00 00 00 00 00 00 00 00 00  (..@............\n  backtrace (crc 9e5f4e84):\n    [\u0026lt;ffffffff81418ff1\u0026gt;] kmem_cache_alloc_noprof+0x2c1/0x360\n    [\u0026lt;ffffffff81d27aa0\u0026gt;] sk_prot_alloc+0x30/0x120\n    [\u0026lt;ffffffff81d2b54c\u0026gt;] sk_alloc+0x2c/0x4b0\n    [\u0026lt;ffffffff81fe049a\u0026gt;] __vsock_create.constprop.0+0x2a/0x310\n    [\u0026lt;ffffffff81fe6d6c\u0026gt;] virtio_transport_recv_pkt+0x4dc/0x9a0\n    [\u0026lt;ffffffff81fe745d\u0026gt;] vsock_loopback_work+0xfd/0x140\n    [\u0026lt;ffffffff810fc6ac\u0026gt;] process_one_work+0x20c/0x570\n    [\u0026lt;ffffffff810fce3f\u0026gt;] worker_thread+0x1bf/0x3a0\n    [\u0026lt;ffffffff811070dd\u0026gt;] kthread+0xdd/0x110\n    [\u0026lt;ffffffff81044fdd\u0026gt;] ret_from_fork+0x2d/0x50\n    [\u0026lt;ffffffff8100785a\u0026gt;] ret_from_fork_asm+0x1a/0x30(CVE-2024-53119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: CT: Fix null-ptr-deref in add rule err flow\n\nIn error flow of mlx5_tc_ct_entry_add_rule(), in case ct_rule_add()\ncallback returns error, zone_rule-\u0026gt;attr is used uninitiated. Fix it to\nuse attr which has the needed pointer value.\n\nKernel log:\n BUG: kernel NULL pointer dereference, address: 0000000000000110\n RIP: 0010:mlx5_tc_ct_entry_add_rule+0x2b1/0x2f0 [mlx5_core]\n…\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die+0x20/0x70\n  ? page_fault_oops+0x150/0x3e0\n  ? exc_page_fault+0x74/0x140\n  ? asm_exc_page_fault+0x22/0x30\n  ? mlx5_tc_ct_entry_add_rule+0x2b1/0x2f0 [mlx5_core]\n  ? mlx5_tc_ct_entry_add_rule+0x1d5/0x2f0 [mlx5_core]\n  mlx5_tc_ct_block_flow_offload+0xc6a/0xf90 [mlx5_core]\n  ? nf_flow_offload_tuple+0xd8/0x190 [nf_flow_table]\n  nf_flow_offload_tuple+0xd8/0x190 [nf_flow_table]\n  flow_offload_work_handler+0x142/0x320 [nf_flow_table]\n  ? finish_task_switch.isra.0+0x15b/0x2b0\n  process_one_work+0x16c/0x320\n  worker_thread+0x28c/0x3a0\n  ? __pfx_worker_thread+0x10/0x10\n  kthread+0xb8/0xf0\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x2d/0x50\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;(CVE-2024-53120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fs, lock FTE when checking if active\n\nThe referenced commits introduced a two-step process for deleting FTEs:\n\n- Lock the FTE, delete it from hardware, set the hardware deletion function\n  to NULL and unlock the FTE.\n- Lock the parent flow group, delete the software copy of the FTE, and\n  remove it from the xarray.\n\nHowever, this approach encounters a race condition if a rule with the same\nmatch value is added simultaneously. In this scenario, fs_core may set the\nhardware deletion function to NULL prematurely, causing a panic during\nsubsequent rule deletions.\n\nTo prevent this, ensure the active flag of the FTE is checked under a lock,\nwhich will prevent the fs_core layer from attaching a new steering rule to\nan FTE that is in the process of deletion.\n\n[  438.967589] MOSHE: 2496 mlx5_del_flow_rules del_hw_func\n[  438.968205] ------------[ cut here ]------------\n[  438.968654] refcount_t: decrement hit 0; leaking memory.\n[  438.969249] WARNING: CPU: 0 PID: 8957 at lib/refcount.c:31 refcount_warn_saturate+0xfb/0x110\n[  438.970054] Modules linked in: act_mirred cls_flower act_gact sch_ingress openvswitch nsh mlx5_vdpa vringh vhost_iotlb vdpa mlx5_ib mlx5_core xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm ib_uverbs ib_core zram zsmalloc fuse [last unloaded: cls_flower]\n[  438.973288] CPU: 0 UID: 0 PID: 8957 Comm: tc Not tainted 6.12.0-rc1+ #8\n[  438.973888] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n[  438.974874] RIP: 0010:refcount_warn_saturate+0xfb/0x110\n[  438.975363] Code: 40 66 3b 82 c6 05 16 e9 4d 01 01 e8 1f 7c a0 ff 0f 0b c3 cc cc cc cc 48 c7 c7 10 66 3b 82 c6 05 fd e8 4d 01 01 e8 05 7c a0 ff \u0026lt;0f\u0026gt; 0b c3 cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90\n[  438.976947] RSP: 0018:ffff888124a53610 EFLAGS: 00010286\n[  438.977446] RAX: 0000000000000000 RBX: ffff888119d56de0 RCX: 0000000000000000\n[  438.978090] RDX: ffff88852c828700 RSI: ffff88852c81b3c0 RDI: ffff88852c81b3c0\n[  438.978721] RBP: ffff888120fa0e88 R08: 0000000000000000 R09: ffff888124a534b0\n[  438.979353] R10: 0000000000000001 R11: 0000000000000001 R12: ffff888119d56de0\n[  438.979979] R13: ffff888120fa0ec0 R14: ffff888120fa0ee8 R15: ffff888119d56de0\n[  438.980607] FS:  00007fe6dcc0f800(0000) GS:ffff88852c800000(0000) knlGS:0000000000000000\n[  438.983984] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  438.984544] CR2: 00000000004275e0 CR3: 0000000186982001 CR4: 0000000000372eb0\n[  438.985205] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[  438.985842] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[  438.986507] Call Trace:\n[  438.986799]  \u0026lt;TASK\u0026gt;\n[  438.987070]  ? __warn+0x7d/0x110\n[  438.987426]  ? refcount_warn_saturate+0xfb/0x110\n[  438.987877]  ? report_bug+0x17d/0x190\n[  438.988261]  ? prb_read_valid+0x17/0x20\n[  438.988659]  ? handle_bug+0x53/0x90\n[  438.989054]  ? exc_invalid_op+0x14/0x70\n[  438.989458]  ? asm_exc_invalid_op+0x16/0x20\n[  438.989883]  ? refcount_warn_saturate+0xfb/0x110\n[  438.990348]  mlx5_del_flow_rules+0x2f7/0x340 [mlx5_core]\n[  438.990932]  __mlx5_eswitch_del_rule+0x49/0x170 [mlx5_core]\n[  438.991519]  ? mlx5_lag_is_sriov+0x3c/0x50 [mlx5_core]\n[  438.992054]  ? xas_load+0x9/0xb0\n[  438.992407]  mlx5e_tc_rule_unoffload+0x45/0xe0 [mlx5_core]\n[  438.993037]  mlx5e_tc_del_fdb_flow+0x2a6/0x2e0 [mlx5_core]\n[  438.993623]  mlx5e_flow_put+0x29/0x60 [mlx5_core]\n[  438.994161]  mlx5e_delete_flower+0x261/0x390 [mlx5_core]\n[  438.994728]  tc_setup_cb_destroy+0xb9/0x190\n[  438.995150]  fl_hw_destroy_filter+0x94/0xc0 [cls_flower]\n[  438.995650]  fl_change+0x11a4/0x13c0 [cls_flower]\n[  438.996105]  tc_new_tfilter+0x347/0xbc0\n[  438.996503]  ? __\n---truncated---(CVE-2024-53121)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: cope racing subflow creation in mptcp_rcv_space_adjust\n\nAdditional active subflows - i.e. created by the in kernel path\nmanager - are included into the subflow list before starting the\n3whs.\n\nA racing recvmsg() spooling data received on an already established\nsubflow would unconditionally call tcp_cleanup_rbuf() on all the\ncurrent subflows, potentially hitting a divide by zero error on\nthe newly created ones.\n\nExplicitly check that the subflow is in a suitable state before\ninvoking tcp_cleanup_rbuf().(CVE-2024-53122)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: error out earlier on disconnect\n\nEric reported a division by zero splat in the MPTCP protocol:\n\nOops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 1 UID: 0 PID: 6094 Comm: syz-executor317 Not tainted\n6.12.0-rc5-syzkaller-00291-g05b92660cdfe #0\nHardware name: Google Google Compute Engine/Google Compute Engine,\nBIOS Google 09/13/2024\nRIP: 0010:__tcp_select_window+0x5b4/0x1310 net/ipv4/tcp_output.c:3163\nCode: f6 44 01 e3 89 df e8 9b 75 09 f8 44 39 f3 0f 8d 11 ff ff ff e8\n0d 74 09 f8 45 89 f4 e9 04 ff ff ff e8 00 74 09 f8 44 89 f0 99 \u0026lt;f7\u0026gt; 7c\n24 14 41 29 d6 45 89 f4 e9 ec fe ff ff e8 e8 73 09 f8 48 89\nRSP: 0018:ffffc900041f7930 EFLAGS: 00010293\nRAX: 0000000000017e67 RBX: 0000000000017e67 RCX: ffffffff8983314b\nRDX: 0000000000000000 RSI: ffffffff898331b0 RDI: 0000000000000004\nRBP: 00000000005d6000 R08: 0000000000000004 R09: 0000000000017e67\nR10: 0000000000003e80 R11: 0000000000000000 R12: 0000000000003e80\nR13: ffff888031d9b440 R14: 0000000000017e67 R15: 00000000002eb000\nFS: 00007feb5d7f16c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007feb5d8adbb8 CR3: 0000000074e4c000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n\u0026lt;TASK\u0026gt;\n__tcp_cleanup_rbuf+0x3e7/0x4b0 net/ipv4/tcp.c:1493\nmptcp_rcv_space_adjust net/mptcp/protocol.c:2085 [inline]\nmptcp_recvmsg+0x2156/0x2600 net/mptcp/protocol.c:2289\ninet_recvmsg+0x469/0x6a0 net/ipv4/af_inet.c:885\nsock_recvmsg_nosec net/socket.c:1051 [inline]\nsock_recvmsg+0x1b2/0x250 net/socket.c:1073\n__sys_recvfrom+0x1a5/0x2e0 net/socket.c:2265\n__do_sys_recvfrom net/socket.c:2283 [inline]\n__se_sys_recvfrom net/socket.c:2279 [inline]\n__x64_sys_recvfrom+0xe0/0x1c0 net/socket.c:2279\ndo_syscall_x64 arch/x86/entry/common.c:52 [inline]\ndo_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83\nentry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7feb5d857559\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48\n89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d\n01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007feb5d7f1208 EFLAGS: 00000246 ORIG_RAX: 000000000000002d\nRAX: ffffffffffffffda RBX: 00007feb5d8e1318 RCX: 00007feb5d857559\nRDX: 000000800000000e RSI: 0000000000000000 RDI: 0000000000000003\nRBP: 00007feb5d8e1310 R08: 0000000000000000 R09: ffffffff81000000\nR10: 0000000000000100 R11: 0000000000000246 R12: 00007feb5d8e131c\nR13: 00007feb5d8ae074 R14: 000000800000000e R15: 00000000fffffdef\n\nand provided a nice reproducer.\n\nThe root cause is the current bad handling of racing disconnect.\nAfter the blamed commit below, sk_wait_data() can return (with\nerror) with the underlying socket disconnected and a zero rcv_mss.\n\nCatch the error and return without performing any additional\noperations on the current socket.(CVE-2024-53123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix data-races around sk-\u0026gt;sk_forward_alloc\n\nSyzkaller reported this warning:\n ------------[ cut here ]------------\n WARNING: CPU: 0 PID: 16 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x1c5/0x1e0\n Modules linked in:\n CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.12.0-rc5 #26\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\n RIP: 0010:inet_sock_destruct+0x1c5/0x1e0\n Code: 24 12 4c 89 e2 5b 48 c7 c7 98 ec bb 82 41 5c e9 d1 18 17 ff 4c 89 e6 5b 48 c7 c7 d0 ec bb 82 41 5c e9 bf 18 17 ff 0f 0b eb 83 \u0026lt;0f\u0026gt; 0b eb 97 0f 0b eb 87 0f 0b e9 68 ff ff ff 66 66 2e 0f 1f 84 00\n RSP: 0018:ffffc9000008bd90 EFLAGS: 00010206\n RAX: 0000000000000300 RBX: ffff88810b172a90 RCX: 0000000000000007\n RDX: 0000000000000002 RSI: 0000000000000300 RDI: ffff88810b172a00\n RBP: ffff88810b172a00 R08: ffff888104273c00 R09: 0000000000100007\n R10: 0000000000020000 R11: 0000000000000006 R12: ffff88810b172a00\n R13: 0000000000000004 R14: 0000000000000000 R15: ffff888237c31f78\n FS:  0000000000000000(0000) GS:ffff888237c00000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007ffc63fecac8 CR3: 000000000342e000 CR4: 00000000000006f0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __warn+0x88/0x130\n  ? inet_sock_destruct+0x1c5/0x1e0\n  ? report_bug+0x18e/0x1a0\n  ? handle_bug+0x53/0x90\n  ? exc_invalid_op+0x18/0x70\n  ? asm_exc_invalid_op+0x1a/0x20\n  ? inet_sock_destruct+0x1c5/0x1e0\n  __sk_destruct+0x2a/0x200\n  rcu_do_batch+0x1aa/0x530\n  ? rcu_do_batch+0x13b/0x530\n  rcu_core+0x159/0x2f0\n  handle_softirqs+0xd3/0x2b0\n  ? __pfx_smpboot_thread_fn+0x10/0x10\n  run_ksoftirqd+0x25/0x30\n  smpboot_thread_fn+0xdd/0x1d0\n  kthread+0xd3/0x100\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x34/0x50\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\n ---[ end trace 0000000000000000 ]---\n\nIts possible that two threads call tcp_v6_do_rcv()/sk_forward_alloc_add()\nconcurrently when sk-\u0026gt;sk_state == TCP_LISTEN with sk-\u0026gt;sk_lock unlocked,\nwhich triggers a data-race around sk-\u0026gt;sk_forward_alloc:\ntcp_v6_rcv\n    tcp_v6_do_rcv\n        skb_clone_and_charge_r\n            sk_rmem_schedule\n                __sk_mem_schedule\n                    sk_forward_alloc_add()\n            skb_set_owner_r\n                sk_mem_charge\n                    sk_forward_alloc_add()\n        __kfree_skb\n            skb_release_all\n                skb_release_head_state\n                    sock_rfree\n                        sk_mem_uncharge\n                            sk_forward_alloc_add()\n                            sk_mem_reclaim\n                                // set local var reclaimable\n                                __sk_mem_reclaim\n                                    sk_forward_alloc_add()\n\nIn this syzkaller testcase, two threads call\ntcp_v6_do_rcv() with skb-\u0026gt;truesize=768, the sk_forward_alloc changes like\nthis:\n (cpu 1)             | (cpu 2)             | sk_forward_alloc\n ...                 | ...                 | 0\n __sk_mem_schedule() |                     | +4096 = 4096\n                     | __sk_mem_schedule() | +4096 = 8192\n sk_mem_charge()     |                     | -768  = 7424\n                     | sk_mem_charge()     | -768  = 6656\n ...                 |    ...              |\n sk_mem_uncharge()   |                     | +768  = 7424\n reclaimable=7424    |                     |\n                     | sk_mem_uncharge()   | +768  = 8192\n                     | reclaimable=8192    |\n __sk_mem_reclaim()  |                     | -4096 = 4096\n                     | __sk_mem_reclaim()  | -8192 = -4096 != 0\n\nThe skb_clone_and_charge_r() should not be called in tcp_v6_do_rcv() when\nsk-\u0026gt;sk_state is TCP_LISTEN, it happens later in tcp_v6_syn_recv_sock().\nFix the same issue in dccp_v6_do_rcv().(CVE-2024-53124)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN\n\nHide KVM\u0026apos;s pt_mode module param behind CONFIG_BROKEN, i.e. disable support\nfor virtualizing Intel PT via guest/host mode unless BROKEN=y.  There are\nmyriad bugs in the implementation, some of which are fatal to the guest,\nand others which put the stability and health of the host at risk.\n\nFor guest fatalities, the most glaring issue is that KVM fails to ensure\ntracing is disabled, and *stays* disabled prior to VM-Enter, which is\nnecessary as hardware disallows loading (the guest\u0026apos;s) RTIT_CTL if tracing\nis enabled (enforced via a VMX consistency check).  Per the SDM:\n\n  If the logical processor is operating with Intel PT enabled (if\n  IA32_RTIT_CTL.TraceEn = 1) at the time of VM entry, the \u0026quot;load\n  IA32_RTIT_CTL\u0026quot; VM-entry control must be 0.\n\nOn the host side, KVM doesn\u0026apos;t validate the guest CPUID configuration\nprovided by userspace, and even worse, uses the guest configuration to\ndecide what MSRs to save/load at VM-Enter and VM-Exit.  E.g. configuring\nguest CPUID to enumerate more address ranges than are supported in hardware\nwill result in KVM trying to passthrough, save, and load non-existent MSRs,\nwhich generates a variety of WARNs, ToPA ERRORs in the host, a potential\ndeadlock, etc.(CVE-2024-53135)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: kTLS, Fix incorrect page refcounting\n\nThe kTLS tx handling code is using a mix of get_page() and\npage_ref_inc() APIs to increment the page reference. But on the release\npath (mlx5e_ktls_tx_handle_resync_dump_comp()), only put_page() is used.\n\nThis is an issue when using pages from large folios: the get_page()\nreferences are stored on the folio page while the page_ref_inc()\nreferences are stored directly in the given page. On release the folio\npage will be dereferenced too many times.\n\nThis was found while doing kTLS testing with sendfile() + ZC when the\nserved file was read from NFS on a kernel with NFS large folios support\n(commit 49b29a573da8 (\u0026quot;nfs: add support for large folios\u0026quot;)).(CVE-2024-53138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: fix possible UAF in sctp_v6_available()\n\nA lockdep report [1] with CONFIG_PROVE_RCU_LIST=y hints\nthat sctp_v6_available() is calling dev_get_by_index_rcu()\nand ipv6_chk_addr() without holding rcu.\n\n[1]\n =============================\n WARNING: suspicious RCU usage\n 6.12.0-rc5-virtme #1216 Tainted: G        W\n -----------------------------\n net/core/dev.c:876 RCU-list traversed in non-reader section!!\n\nother info that might help us debug this:\n\nrcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by sctp_hello/31495:\n #0: ffff9f1ebbdb7418 (sk_lock-AF_INET6){+.+.}-{0:0}, at: sctp_bind (./arch/x86/include/asm/jump_label.h:27 net/sctp/socket.c:315) sctp\n\nstack backtrace:\n CPU: 7 UID: 0 PID: 31495 Comm: sctp_hello Tainted: G        W          6.12.0-rc5-virtme #1216\n Tainted: [W]=WARN\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl (lib/dump_stack.c:123)\n lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822)\n dev_get_by_index_rcu (net/core/dev.c:876 (discriminator 7))\n sctp_v6_available (net/sctp/ipv6.c:701) sctp\n sctp_do_bind (net/sctp/socket.c:400 (discriminator 1)) sctp\n sctp_bind (net/sctp/socket.c:320) sctp\n inet6_bind_sk (net/ipv6/af_inet6.c:465)\n ? security_socket_bind (security/security.c:4581 (discriminator 1))\n __sys_bind (net/socket.c:1848 net/socket.c:1869)\n ? do_user_addr_fault (./include/linux/rcupdate.h:347 ./include/linux/rcupdate.h:880 ./include/linux/mm.h:729 arch/x86/mm/fault.c:1340)\n ? do_user_addr_fault (./arch/x86/include/asm/preempt.h:84 (discriminator 13) ./include/linux/rcupdate.h:98 (discriminator 13) ./include/linux/rcupdate.h:882 (discriminator 13) ./include/linux/mm.h:729 (discriminator 13) arch/x86/mm/fault.c:1340 (discriminator 13))\n __x64_sys_bind (net/socket.c:1877 (discriminator 1) net/socket.c:1875 (discriminator 1) net/socket.c:1875 (discriminator 1))\n do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1) arch/x86/entry/common.c:83 (discriminator 1))\n entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n RIP: 0033:0x7f59b934a1e7\n Code: 44 00 00 48 8b 15 39 8c 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 b8 31 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d 09 8c 0c 00 f7 d8 64 89 01 48\nAll code\n========\n   0:\t44 00 00             \tadd    %r8b,(%rax)\n   3:\t48 8b 15 39 8c 0c 00 \tmov    0xc8c39(%rip),%rdx        # 0xc8c43\n   a:\tf7 d8                \tneg    %eax\n   c:\t64 89 02             \tmov    %eax,%fs:(%rdx)\n   f:\tb8 ff ff ff ff       \tmov    $0xffffffff,%eax\n  14:\teb bd                \tjmp    0xffffffffffffffd3\n  16:\t66 2e 0f 1f 84 00 00 \tcs nopw 0x0(%rax,%rax,1)\n  1d:\t00 00 00\n  20:\t0f 1f 00             \tnopl   (%rax)\n  23:\tb8 31 00 00 00       \tmov    $0x31,%eax\n  28:\t0f 05                \tsyscall\n  2a:*\t48 3d 01 f0 ff ff    \tcmp    $0xfffffffffffff001,%rax\t\t\u0026lt;-- trapping instruction\n  30:\t73 01                \tjae    0x33\n  32:\tc3                   \tret\n  33:\t48 8b 0d 09 8c 0c 00 \tmov    0xc8c09(%rip),%rcx        # 0xc8c43\n  3a:\tf7 d8                \tneg    %eax\n  3c:\t64 89 01             \tmov    %eax,%fs:(%rcx)\n  3f:\t48                   \trex.W\n\nCode starting with the faulting instruction\n===========================================\n   0:\t48 3d 01 f0 ff ff    \tcmp    $0xfffffffffffff001,%rax\n   6:\t73 01                \tjae    0x9\n   8:\tc3                   \tret\n   9:\t48 8b 0d 09 8c 0c 00 \tmov    0xc8c09(%rip),%rcx        # 0xc8c19\n  10:\tf7 d8                \tneg    %eax\n  12:\t64 89 01             \tmov    %eax,%fs:(%rcx)\n  15:\t48                   \trex.W\n RSP: 002b:00007ffe2d0ad398 EFLAGS: 00000202 ORIG_RAX: 0000000000000031\n RAX: ffffffffffffffda RBX: 00007ffe2d0ad3d0 RCX: 00007f59b934a1e7\n RDX: 000000000000001c RSI: 00007ffe2d0ad3d0 RDI: 0000000000000005\n RBP: 0000000000000005 R08: 1999999999999999 R09: 0000000000000000\n R10: 00007f59b9253298 R11: 000000000000\n---truncated---(CVE-2024-53139)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetlink: terminate outstanding dump on socket close\n\nNetlink supports iterative dumping of data. It provides the families\nthe following ops:\n - start - (optional) kicks off the dumping process\n - dump  - actual dump helper, keeps getting called until it returns 0\n - done  - (optional) pairs with .start, can be used for cleanup\nThe whole process is asynchronous and the repeated calls to .dump\ndon\u0026apos;t actually happen in a tight loop, but rather are triggered\nin response to recvmsg() on the socket.\n\nThis gives the user full control over the dump, but also means that\nthe user can close the socket without getting to the end of the dump.\nTo make sure .start is always paired with .done we check if there\nis an ongoing dump before freeing the socket, and if so call .done.\n\nThe complication is that sockets can get freed from BH and .done\nis allowed to sleep. So we use a workqueue to defer the call, when\nneeded.\n\nUnfortunately this does not work correctly. What we defer is not\nthe cleanup but rather releasing a reference on the socket.\nWe have no guarantee that we own the last reference, if someone\nelse holds the socket they may release it in BH and we\u0026apos;re back\nto square one.\n\nThe whole dance, however, appears to be unnecessary. Only the user\ncan interact with dumps, so we can clean up when socket is closed.\nAnd close always happens in process context. Some async code may\nstill access the socket after close, queue notification skbs to it etc.\nbut no dumps can start, end or otherwise make progress.\n\nDelete the workqueue and flush the dump state directly from the release\nhandler. Note that further cleanup is possible in -next, for instance\nwe now always call .done before releasing the main module reference,\nso dump doesn\u0026apos;t have to take a reference of its own.(CVE-2024-53140)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE\n\nThis aligned BR/EDR JUST_WORKS method with LE which since 92516cd97fd4\n(\u0026quot;Bluetooth: Always request for user confirmation for Just Works\u0026quot;)\nalways request user confirmation with confirm_hint set since the\nlikes of bluetoothd have dedicated policy around JUST_WORKS method\n(e.g. main.conf:JustWorksRepairing).\n\nCVE: CVE-2024-8805(CVE-2024-53144)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: Fix potential integer overflow during physmem setup\n\nThis issue happens when the real map size is greater than LONG_MAX,\nwhich can be easily triggered on UML/i386.(CVE-2024-53145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock, bfq: fix bfqq uaf in bfq_limit_depth()\n\nSet new allocated bfqq to bic or remove freed bfqq from bic are both\nprotected by bfqd-\u0026gt;lock, however bfq_limit_depth() is deferencing bfqq\nfrom bic without the lock, this can lead to UAF if the io_context is\nshared by multiple tasks.\n\nFor example, test bfq with io_uring can trigger following UAF in v6.6:\n\n==================================================================\nBUG: KASAN: slab-use-after-free in bfqq_group+0x15/0x50\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x47/0x80\n print_address_description.constprop.0+0x66/0x300\n print_report+0x3e/0x70\n kasan_report+0xb4/0xf0\n bfqq_group+0x15/0x50\n bfqq_request_over_limit+0x130/0x9a0\n bfq_limit_depth+0x1b5/0x480\n __blk_mq_alloc_requests+0x2b5/0xa00\n blk_mq_get_new_requests+0x11d/0x1d0\n blk_mq_submit_bio+0x286/0xb00\n submit_bio_noacct_nocheck+0x331/0x400\n __block_write_full_folio+0x3d0/0x640\n writepage_cb+0x3b/0xc0\n write_cache_pages+0x254/0x6c0\n write_cache_pages+0x254/0x6c0\n do_writepages+0x192/0x310\n filemap_fdatawrite_wbc+0x95/0xc0\n __filemap_fdatawrite_range+0x99/0xd0\n filemap_write_and_wait_range.part.0+0x4d/0xa0\n blkdev_read_iter+0xef/0x1e0\n io_read+0x1b6/0x8a0\n io_issue_sqe+0x87/0x300\n io_wq_submit_work+0xeb/0x390\n io_worker_handle_work+0x24d/0x550\n io_wq_worker+0x27f/0x6c0\n ret_from_fork_asm+0x1b/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 808602:\n kasan_save_stack+0x1e/0x40\n kasan_set_track+0x21/0x30\n __kasan_slab_alloc+0x83/0x90\n kmem_cache_alloc_node+0x1b1/0x6d0\n bfq_get_queue+0x138/0xfa0\n bfq_get_bfqq_handle_split+0xe3/0x2c0\n bfq_init_rq+0x196/0xbb0\n bfq_insert_request.isra.0+0xb5/0x480\n bfq_insert_requests+0x156/0x180\n blk_mq_insert_request+0x15d/0x440\n blk_mq_submit_bio+0x8a4/0xb00\n submit_bio_noacct_nocheck+0x331/0x400\n __blkdev_direct_IO_async+0x2dd/0x330\n blkdev_write_iter+0x39a/0x450\n io_write+0x22a/0x840\n io_issue_sqe+0x87/0x300\n io_wq_submit_work+0xeb/0x390\n io_worker_handle_work+0x24d/0x550\n io_wq_worker+0x27f/0x6c0\n ret_from_fork+0x2d/0x50\n ret_from_fork_asm+0x1b/0x30\n\nFreed by task 808589:\n kasan_save_stack+0x1e/0x40\n kasan_set_track+0x21/0x30\n kasan_save_free_info+0x27/0x40\n __kasan_slab_free+0x126/0x1b0\n kmem_cache_free+0x10c/0x750\n bfq_put_queue+0x2dd/0x770\n __bfq_insert_request.isra.0+0x155/0x7a0\n bfq_insert_request.isra.0+0x122/0x480\n bfq_insert_requests+0x156/0x180\n blk_mq_dispatch_plug_list+0x528/0x7e0\n blk_mq_flush_plug_list.part.0+0xe5/0x590\n __blk_flush_plug+0x3b/0x90\n blk_finish_plug+0x40/0x60\n do_writepages+0x19d/0x310\n filemap_fdatawrite_wbc+0x95/0xc0\n __filemap_fdatawrite_range+0x99/0xd0\n filemap_write_and_wait_range.part.0+0x4d/0xa0\n blkdev_read_iter+0xef/0x1e0\n io_read+0x1b6/0x8a0\n io_issue_sqe+0x87/0x300\n io_wq_submit_work+0xeb/0x390\n io_worker_handle_work+0x24d/0x550\n io_wq_worker+0x27f/0x6c0\n ret_from_fork+0x2d/0x50\n ret_from_fork_asm+0x1b/0x30\n\nFix the problem by protecting bic_to_bfqq() with bfqd-\u0026gt;lock.(CVE-2024-53166)\n\nIn the Linux kernel, the following vulnerability has been resolved:drm/amd/display: Fix null check for pipe_ctx-\u0026gt;plane_state in dcn20_program_pipeThis commit addresses a null pointer dereference issue indcn20_program_pipe(). Previously, commit 8e4ed3cf1642 ( drm/amd/display:Add null check for pipe_ctx-\u0026gt;plane_state in dcn20_program_pipe )partially fixed the null pointer dereference issue. However, indcn20_update_dchubp_dpp(), the variable pipe_ctx is passed in, andplane_state is accessed again through pipe_ctx. Multiple if statementsdirectly call attributes of plane_state, leading to potential nullpointer dereference issues. This patch adds necessary null checks toensure stability.(CVE-2024-53201)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: Fix use-after-free of nreq in reqsk_timer_handler().\n\nThe cited commit replaced inet_csk_reqsk_queue_drop_and_put() with\n__inet_csk_reqsk_queue_drop() and reqsk_put() in reqsk_timer_handler().\n\nThen, oreq should be passed to reqsk_put() instead of req; otherwise\nuse-after-free of nreq could happen when reqsk is migrated but the\nretry attempt failed (e.g. due to timeout).\n\nLet\u0026apos;s pass oreq to reqsk_put().(CVE-2024-53206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix possible deadlocks\n\nThis fixes possible deadlocks like the following caused by\nhci_cmd_sync_dequeue causing the destroy function to run:\n\n INFO: task kworker/u19:0:143 blocked for more than 120 seconds.\n       Tainted: G        W  O        6.8.0-2024-03-19-intel-next-iLS-24ww14 #1\n \u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\n task:kworker/u19:0   state:D stack:0     pid:143   tgid:143   ppid:2      flags:0x00004000\n Workqueue: hci0 hci_cmd_sync_work [bluetooth]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __schedule+0x374/0xaf0\n  schedule+0x3c/0xf0\n  schedule_preempt_disabled+0x1c/0x30\n  __mutex_lock.constprop.0+0x3ef/0x7a0\n  __mutex_lock_slowpath+0x13/0x20\n  mutex_lock+0x3c/0x50\n  mgmt_set_connectable_complete+0xa4/0x150 [bluetooth]\n  ? kfree+0x211/0x2a0\n  hci_cmd_sync_dequeue+0xae/0x130 [bluetooth]\n  ? __pfx_cmd_complete_rsp+0x10/0x10 [bluetooth]\n  cmd_complete_rsp+0x26/0x80 [bluetooth]\n  mgmt_pending_foreach+0x4d/0x70 [bluetooth]\n  __mgmt_power_off+0x8d/0x180 [bluetooth]\n  ? _raw_spin_unlock_irq+0x23/0x40\n  hci_dev_close_sync+0x445/0x5b0 [bluetooth]\n  hci_set_powered_sync+0x149/0x250 [bluetooth]\n  set_powered_sync+0x24/0x60 [bluetooth]\n  hci_cmd_sync_work+0x90/0x150 [bluetooth]\n  process_one_work+0x13e/0x300\n  worker_thread+0x2f7/0x420\n  ? __pfx_worker_thread+0x10/0x10\n  kthread+0x107/0x140\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x3d/0x60\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1b/0x30\n  \u0026lt;/TASK\u0026gt;(CVE-2024-53207)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbnxt_en: Fix receive ring space parameters when XDP is active\n\nThe MTU setting at the time an XDP multi-buffer is attached\ndetermines whether the aggregation ring will be used and the\nrx_skb_func handler.  This is done in bnxt_set_rx_skb_mode().\n\nIf the MTU is later changed, the aggregation ring setting may need\nto be changed and it may become out-of-sync with the settings\ninitially done in bnxt_set_rx_skb_mode().  This may result in\nrandom memory corruption and crashes as the HW may DMA data larger\nthan the allocated buffer size, such as:\n\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 17 PID: 0 Comm: swapper/17 Kdump: loaded Tainted: G S         OE      6.1.0-226bf9805506 #1\nHardware name: Wiwynn Delta Lake PVT BZA.02601.0150/Delta Lake-Class1, BIOS F0E_3A12 08/26/2021\nRIP: 0010:bnxt_rx_pkt+0xe97/0x1ae0 [bnxt_en]\nCode: 8b 95 70 ff ff ff 4c 8b 9d 48 ff ff ff 66 41 89 87 b4 00 00 00 e9 0b f7 ff ff 0f b7 43 0a 49 8b 95 a8 04 00 00 25 ff 0f 00 00 \u0026lt;0f\u0026gt; b7 14 42 48 c1 e2 06 49 03 95 a0 04 00 00 0f b6 42 33f\nRSP: 0018:ffffa19f40cc0d18 EFLAGS: 00010202\nRAX: 00000000000001e0 RBX: ffff8e2c805c6100 RCX: 00000000000007ff\nRDX: 0000000000000000 RSI: ffff8e2c271ab990 RDI: ffff8e2c84f12380\nRBP: ffffa19f40cc0e48 R08: 000000000001000d R09: 974ea2fcddfa4cbf\nR10: 0000000000000000 R11: ffffa19f40cc0ff8 R12: ffff8e2c94b58980\nR13: ffff8e2c952d6600 R14: 0000000000000016 R15: ffff8e2c271ab990\nFS:  0000000000000000(0000) GS:ffff8e3b3f840000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000000003c0 CR3: 0000000e8580a004 CR4: 00000000007706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n __bnxt_poll_work+0x1c2/0x3e0 [bnxt_en]\n\nTo address the issue, we now call bnxt_set_rx_skb_mode() within\nbnxt_change_mtu() to properly set the AGG rings configuration and\nupdate rx_skb_func based on the new MTU value.\nAdditionally, BNXT_FLAG_NO_AGG_RINGS is cleared at the beginning of\nbnxt_set_rx_skb_mode() to make sure it gets set or cleared based on\nthe current MTU.(CVE-2024-53209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs\n\nBase clocks are the first in being probed and are real dependencies of the\nrest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880,\nRT305x and RT3883 \u0026apos;xtal\u0026apos; must be defined first since in any other case,\nwhen fixed clocks are probed they are delayed until \u0026apos;xtal\u0026apos; is probed so the\nfollowing warning appears:\n\n WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138\n Modules linked in:\n CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0\n Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000\n 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000\n 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000\n 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009\n 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000\n ...\n Call Trace:\n [\u0026lt;800065d0\u0026gt;] show_stack+0x64/0xf4\n [\u0026lt;804bca14\u0026gt;] dump_stack_lvl+0x38/0x60\n [\u0026lt;800218ac\u0026gt;] __warn+0x94/0xe4\n [\u0026lt;8002195c\u0026gt;] warn_slowpath_fmt+0x60/0x94\n [\u0026lt;80259ff8\u0026gt;] rt3883_bus_recalc_rate+0x98/0x138\n [\u0026lt;80254530\u0026gt;] __clk_register+0x568/0x688\n [\u0026lt;80254838\u0026gt;] of_clk_hw_register+0x18/0x2c\n [\u0026lt;8070b910\u0026gt;] rt2880_clk_of_clk_init_driver+0x18c/0x594\n [\u0026lt;8070b628\u0026gt;] of_clk_init+0x1c0/0x23c\n [\u0026lt;806fc448\u0026gt;] plat_time_init+0x58/0x18c\n [\u0026lt;806fdaf0\u0026gt;] time_init+0x10/0x6c\n [\u0026lt;806f9bc4\u0026gt;] start_kernel+0x458/0x67c\n\n ---[ end trace 0000000000000000 ]---\n\nWhen this driver was mainlined we could not find any active users of old\nralink SoCs so we cannot perform any real tests for them. Now, one user\nof a Belkin f9k1109 version 1 device which uses RT3883 SoC appeared and\nreported some issues in openWRT:\n- https://github.com/openwrt/openwrt/issues/16054\n\nThus, define a \u0026apos;rt2880_xtal_recalc_rate()\u0026apos; just returning the expected\nfrequency 40Mhz and use it along the old ralink SoCs to have a correct\nboot trace with no warnings and a working clock plan from the beggining.(CVE-2024-53223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: fix use-after-free in device_for_each_child()\n\nSyzbot has reported the following KASAN splat:\n\nBUG: KASAN: slab-use-after-free in device_for_each_child+0x18f/0x1a0\nRead of size 8 at addr ffff88801f605308 by task kbnepd bnep0/4980\n\nCPU: 0 UID: 0 PID: 4980 Comm: kbnepd bnep0 Not tainted 6.12.0-rc4-00161-gae90f6a6170d #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x100/0x190\n ? device_for_each_child+0x18f/0x1a0\n print_report+0x13a/0x4cb\n ? __virt_addr_valid+0x5e/0x590\n ? __phys_addr+0xc6/0x150\n ? device_for_each_child+0x18f/0x1a0\n kasan_report+0xda/0x110\n ? device_for_each_child+0x18f/0x1a0\n ? __pfx_dev_memalloc_noio+0x10/0x10\n device_for_each_child+0x18f/0x1a0\n ? __pfx_device_for_each_child+0x10/0x10\n pm_runtime_set_memalloc_noio+0xf2/0x180\n netdev_unregister_kobject+0x1ed/0x270\n unregister_netdevice_many_notify+0x123c/0x1d80\n ? __mutex_trylock_common+0xde/0x250\n ? __pfx_unregister_netdevice_many_notify+0x10/0x10\n ? trace_contention_end+0xe6/0x140\n ? __mutex_lock+0x4e7/0x8f0\n ? __pfx_lock_acquire.part.0+0x10/0x10\n ? rcu_is_watching+0x12/0xc0\n ? unregister_netdev+0x12/0x30\n unregister_netdevice_queue+0x30d/0x3f0\n ? __pfx_unregister_netdevice_queue+0x10/0x10\n ? __pfx_down_write+0x10/0x10\n unregister_netdev+0x1c/0x30\n bnep_session+0x1fb3/0x2ab0\n ? __pfx_bnep_session+0x10/0x10\n ? __pfx_lock_release+0x10/0x10\n ? __pfx_woken_wake_function+0x10/0x10\n ? __kthread_parkme+0x132/0x200\n ? __pfx_bnep_session+0x10/0x10\n ? kthread+0x13a/0x370\n ? __pfx_bnep_session+0x10/0x10\n kthread+0x2b7/0x370\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x48/0x80\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 4974:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0xaa/0xb0\n __kmalloc_noprof+0x1d1/0x440\n hci_alloc_dev_priv+0x1d/0x2820\n __vhci_create_device+0xef/0x7d0\n vhci_write+0x2c7/0x480\n vfs_write+0x6a0/0xfc0\n ksys_write+0x12f/0x260\n do_syscall_64+0xc7/0x250\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 4979:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x4f/0x70\n kfree+0x141/0x490\n hci_release_dev+0x4d9/0x600\n bt_host_release+0x6a/0xb0\n device_release+0xa4/0x240\n kobject_put+0x1ec/0x5a0\n put_device+0x1f/0x30\n vhci_release+0x81/0xf0\n __fput+0x3f6/0xb30\n task_work_run+0x151/0x250\n do_exit+0xa79/0x2c30\n do_group_exit+0xd5/0x2a0\n get_signal+0x1fcd/0x2210\n arch_do_signal_or_restart+0x93/0x780\n syscall_exit_to_user_mode+0x140/0x290\n do_syscall_64+0xd4/0x250\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nIn \u0026apos;hci_conn_del_sysfs()\u0026apos;, \u0026apos;device_unregister()\u0026apos; may be called when\nan underlying (kobject) reference counter is greater than 1. This\nmeans that reparenting (happened when the device is actually freed)\nis delayed and, during that delay, parent controller device (hciX)\nmay be deleted. Since the latter may create a dangling pointer to\nfreed parent, avoid that scenario by reparenting to NULL explicitly.(CVE-2024-53237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Fix WARN in ivpu_ipc_send_receive_internal()\n\nMove pm_runtime_set_active() to ivpu_pm_init() so when\nivpu_ipc_send_receive_internal() is executed before ivpu_pm_enable()\nit already has correct runtime state, even if last resume was\nnot successful..(CVE-2024-54193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: adc: ad7923: Fix buffer overflow for tx_buf and ring_xfer\n\nThe AD7923 was updated to support devices with 8 channels, but the size\nof tx_buf and ring_xfer was not increased accordingly, leading to a\npotential buffer overflow in ad7923_update_scan_mode().(CVE-2024-56557)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nad7780: fix division by zero in ad7780_write_raw()\n\nIn the ad7780_write_raw() , val2 can be zero, which might lead to a\ndivision by zero error in DIV_ROUND_CLOSEST(). The ad7780_write_raw()\nis based on iio_info\u0026apos;s write_raw. While val is explicitly declared that\ncan be zero (in read mode), val2 is not specified to be non-zero.(CVE-2024-56567)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: hisi_sas: Create all dump files during debugfs initialization\n\nFor the current debugfs of hisi_sas, after user triggers dump, the\ndriver allocate memory space to save the register information and create\ndebugfs files to display the saved information. In this process, the\ndebugfs files created after each dump.\n\nTherefore, when the dump is triggered while the driver is unbind, the\nfollowing hang occurs:\n\n[67840.853907] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a0\n[67840.862947] Mem abort info:\n[67840.865855]   ESR = 0x0000000096000004\n[67840.869713]   EC = 0x25: DABT (current EL), IL = 32 bits\n[67840.875125]   SET = 0, FnV = 0\n[67840.878291]   EA = 0, S1PTW = 0\n[67840.881545]   FSC = 0x04: level 0 translation fault\n[67840.886528] Data abort info:\n[67840.889524]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n[67840.895117]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[67840.900284]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[67840.905709] user pgtable: 4k pages, 48-bit VAs, pgdp=0000002803a1f000\n[67840.912263] [00000000000000a0] pgd=0000000000000000, p4d=0000000000000000\n[67840.919177] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP\n[67840.996435] pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[67841.003628] pc : down_write+0x30/0x98\n[67841.007546] lr : start_creating.part.0+0x60/0x198\n[67841.012495] sp : ffff8000b979ba20\n[67841.016046] x29: ffff8000b979ba20 x28: 0000000000000010 x27: 0000000000024b40\n[67841.023412] x26: 0000000000000012 x25: ffff20202b355ae8 x24: ffff20202b35a8c8\n[67841.030779] x23: ffffa36877928208 x22: ffffa368b4972240 x21: ffff8000b979bb18\n[67841.038147] x20: ffff00281dc1e3c0 x19: fffffffffffffffe x18: 0000000000000020\n[67841.045515] x17: 0000000000000000 x16: ffffa368b128a530 x15: ffffffffffffffff\n[67841.052888] x14: ffff8000b979bc18 x13: ffffffffffffffff x12: ffff8000b979bb18\n[67841.060263] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa368b1289b18\n[67841.067640] x8 : 0000000000000012 x7 : 0000000000000000 x6 : 00000000000003a9\n[67841.075014] x5 : 0000000000000000 x4 : ffff002818c5cb00 x3 : 0000000000000001\n[67841.082388] x2 : 0000000000000000 x1 : ffff002818c5cb00 x0 : 00000000000000a0\n[67841.089759] Call trace:\n[67841.092456]  down_write+0x30/0x98\n[67841.096017]  start_creating.part.0+0x60/0x198\n[67841.100613]  debugfs_create_dir+0x48/0x1f8\n[67841.104950]  debugfs_create_files_v3_hw+0x88/0x348 [hisi_sas_v3_hw]\n[67841.111447]  debugfs_snapshot_regs_v3_hw+0x708/0x798 [hisi_sas_v3_hw]\n[67841.118111]  debugfs_trigger_dump_v3_hw_write+0x9c/0x120 [hisi_sas_v3_hw]\n[67841.125115]  full_proxy_write+0x68/0xc8\n[67841.129175]  vfs_write+0xd8/0x3f0\n[67841.132708]  ksys_write+0x70/0x108\n[67841.136317]  __arm64_sys_write+0x24/0x38\n[67841.140440]  invoke_syscall+0x50/0x128\n[67841.144385]  el0_svc_common.constprop.0+0xc8/0xf0\n[67841.149273]  do_el0_svc+0x24/0x38\n[67841.152773]  el0_svc+0x38/0xd8\n[67841.156009]  el0t_64_sync_handler+0xc0/0xc8\n[67841.160361]  el0t_64_sync+0x1a4/0x1a8\n[67841.164189] Code: b9000882 d2800002 d2800023 f9800011 (c85ffc05)\n[67841.170443] ---[ end trace 0000000000000000 ]---\n\nTo fix this issue, create all directories and files during debugfs\ninitialization. In this way, the driver only needs to allocate memory\nspace to save information each time the user triggers dumping.(CVE-2024-56588)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: hisi_sas: Add cond_resched() for no forced preemption model\n\nFor no forced preemption model kernel, in the scenario where the\nexpander is connected to 12 high performance SAS SSDs, the following\ncall trace may occur:\n\n[  214.409199][  C240] watchdog: BUG: soft lockup - CPU#240 stuck for 22s! [irq/149-hisi_sa:3211]\n[  214.568533][  C240] pstate: 60400009 (nZCv daif +PAN -UAO -TCO BTYPE=--)\n[  214.575224][  C240] pc : fput_many+0x8c/0xdc\n[  214.579480][  C240] lr : fput+0x1c/0xf0\n[  214.583302][  C240] sp : ffff80002de2b900\n[  214.587298][  C240] x29: ffff80002de2b900 x28: ffff1082aa412000\n[  214.593291][  C240] x27: ffff3062a0348c08 x26: ffff80003a9f6000\n[  214.599284][  C240] x25: ffff1062bbac5c40 x24: 0000000000001000\n[  214.605277][  C240] x23: 000000000000000a x22: 0000000000000001\n[  214.611270][  C240] x21: 0000000000001000 x20: 0000000000000000\n[  214.617262][  C240] x19: ffff3062a41ae580 x18: 0000000000010000\n[  214.623255][  C240] x17: 0000000000000001 x16: ffffdb3a6efe5fc0\n[  214.629248][  C240] x15: ffffffffffffffff x14: 0000000003ffffff\n[  214.635241][  C240] x13: 000000000000ffff x12: 000000000000029c\n[  214.641234][  C240] x11: 0000000000000006 x10: ffff80003a9f7fd0\n[  214.647226][  C240] x9 : ffffdb3a6f0482fc x8 : 0000000000000001\n[  214.653219][  C240] x7 : 0000000000000002 x6 : 0000000000000080\n[  214.659212][  C240] x5 : ffff55480ee9b000 x4 : fffffde7f94c6554\n[  214.665205][  C240] x3 : 0000000000000002 x2 : 0000000000000020\n[  214.671198][  C240] x1 : 0000000000000021 x0 : ffff3062a41ae5b8\n[  214.677191][  C240] Call trace:\n[  214.680320][  C240]  fput_many+0x8c/0xdc\n[  214.684230][  C240]  fput+0x1c/0xf0\n[  214.687707][  C240]  aio_complete_rw+0xd8/0x1fc\n[  214.692225][  C240]  blkdev_bio_end_io+0x98/0x140\n[  214.696917][  C240]  bio_endio+0x160/0x1bc\n[  214.701001][  C240]  blk_update_request+0x1c8/0x3bc\n[  214.705867][  C240]  scsi_end_request+0x3c/0x1f0\n[  214.710471][  C240]  scsi_io_completion+0x7c/0x1a0\n[  214.715249][  C240]  scsi_finish_command+0x104/0x140\n[  214.720200][  C240]  scsi_softirq_done+0x90/0x180\n[  214.724892][  C240]  blk_mq_complete_request+0x5c/0x70\n[  214.730016][  C240]  scsi_mq_done+0x48/0xac\n[  214.734194][  C240]  sas_scsi_task_done+0xbc/0x16c [libsas]\n[  214.739758][  C240]  slot_complete_v3_hw+0x260/0x760 [hisi_sas_v3_hw]\n[  214.746185][  C240]  cq_thread_v3_hw+0xbc/0x190 [hisi_sas_v3_hw]\n[  214.752179][  C240]  irq_thread_fn+0x34/0xa4\n[  214.756435][  C240]  irq_thread+0xc4/0x130\n[  214.760520][  C240]  kthread+0x108/0x13c\n[  214.764430][  C240]  ret_from_fork+0x10/0x18\n\nThis is because in the hisi_sas driver, both the hardware interrupt\nhandler and the interrupt thread are executed on the same CPU. In the\nperformance test scenario, function irq_wait_for_interrupt() will always\nreturn 0 if lots of interrupts occurs and the CPU will be continuously\nconsumed. As a result, the CPU cannot run the watchdog thread. When the\nwatchdog time exceeds the specified time, call trace occurs.\n\nTo fix it, add cond_resched() to execute the watchdog thread.(CVE-2024-56589)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Fix not checking skb length on hci_acldata_packet\n\nThis fixes not checking if skb really contains an ACL header otherwise\nthe code may attempt to access some uninitilized/invalid memory past the\nvalid skb-\u0026gt;data.(CVE-2024-56590)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxsk: fix OOB map writes when deleting elements\n\nJordy says:\n\n\u0026quot;\nIn the xsk_map_delete_elem function an unsigned integer\n(map-\u0026gt;max_entries) is compared with a user-controlled signed integer\n(k). Due to implicit type conversion, a large unsigned value for\nmap-\u0026gt;max_entries can bypass the intended bounds check:\n\n\tif (k \u0026gt;= map-\u0026gt;max_entries)\n\t\treturn -EINVAL;\n\nThis allows k to hold a negative value (between -2147483648 and -2),\nwhich is then used as an array index in m-\u0026gt;xsk_map[k], which results\nin an out-of-bounds access.\n\n\tspin_lock_bh(\u0026amp;m-\u0026gt;lock);\n\tmap_entry = \u0026amp;m-\u0026gt;xsk_map[k]; // Out-of-bounds map_entry\n\told_xs = unrcu_pointer(xchg(map_entry, NULL));  // Oob write\n\tif (old_xs)\n\t\txsk_map_sock_delete(old_xs, map_entry);\n\tspin_unlock_bh(\u0026amp;m-\u0026gt;lock);\n\nThe xchg operation can then be used to cause an out-of-bounds write.\nMoreover, the invalid map_entry passed to xsk_map_sock_delete can lead\nto further memory corruption.\n\u0026quot;\n\nIt indeed results in following splat:\n\n[76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108\n[76612.904330] #PF: supervisor write access in kernel mode\n[76612.909639] #PF: error_code(0x0002) - not-present page\n[76612.914855] PGD 0 P4D 0\n[76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP\n[76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470\n[76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019\n[76612.939781] RIP: 0010:xsk_map_delete_elem+0x2d/0x60\n[76612.944738] Code: 00 00 41 54 55 53 48 63 2e 3b 6f 24 73 38 4c 8d a7 f8 00 00 00 48 89 fb 4c 89 e7 e8 2d bf 05 00 48 8d b4 eb 00 01 00 00 31 ff \u0026lt;48\u0026gt; 87 3e 48 85 ff 74 05 e8 16 ff ff ff 4c 89 e7 e8 3e bc 05 00 31\n[76612.963774] RSP: 0018:ffffc9002e407df8 EFLAGS: 00010246\n[76612.969079] RAX: 0000000000000000 RBX: ffffc9002e461000 RCX: 0000000000000000\n[76612.976323] RDX: 0000000000000001 RSI: ffffc8fc2e461108 RDI: 0000000000000000\n[76612.983569] RBP: ffffffff80000001 R08: 0000000000000000 R09: 0000000000000007\n[76612.990812] R10: ffffc9002e407e18 R11: ffff888108a38858 R12: ffffc9002e4610f8\n[76612.998060] R13: ffff888108a38858 R14: 00007ffd1ae0ac78 R15: ffffc9002e4610c0\n[76613.005303] FS:  00007f80b6f59740(0000) GS:ffff8897e0ec0000(0000) knlGS:0000000000000000\n[76613.013517] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[76613.019349] CR2: ffffc8fc2e461108 CR3: 000000011e3ef001 CR4: 00000000007726f0\n[76613.026595] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[76613.033841] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[76613.041086] PKRU: 55555554\n[76613.043842] Call Trace:\n[76613.046331]  \u0026lt;TASK\u0026gt;\n[76613.048468]  ? __die+0x20/0x60\n[76613.051581]  ? page_fault_oops+0x15a/0x450\n[76613.055747]  ? search_extable+0x22/0x30\n[76613.059649]  ? search_bpf_extables+0x5f/0x80\n[76613.063988]  ? exc_page_fault+0xa9/0x140\n[76613.067975]  ? asm_exc_page_fault+0x22/0x30\n[76613.072229]  ? xsk_map_delete_elem+0x2d/0x60\n[76613.076573]  ? xsk_map_delete_elem+0x23/0x60\n[76613.080914]  __sys_bpf+0x19b7/0x23c0\n[76613.084555]  __x64_sys_bpf+0x1a/0x20\n[76613.088194]  do_syscall_64+0x37/0xb0\n[76613.091832]  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[76613.096962] RIP: 0033:0x7f80b6d1e88d\n[76613.100592] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 b5 0f 00 f7 d8 64 89 01 48\n[76613.119631] RSP: 002b:00007ffd1ae0ac68 EFLAGS: 00000206 ORIG_RAX: 0000000000000141\n[76613.131330] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f80b6d1e88d\n[76613.142632] RDX: 0000000000000098 RSI: 00007ffd1ae0ad20 RDI: 0000000000000003\n[76613.153967] RBP: 00007ffd1ae0adc0 R08: 0000000000000000 R09: 0000000000000000\n[76613.166030] R10: 00007f80b6f77040 R11: 0000000000000206 R12: 00007ffd1ae0aed8\n[76613.177130] R13: 000055ddf42ce1e9 R14: 000055ddf42d0d98 R15: 00\n---truncated---(CVE-2024-56614)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix use after free on unload\n\nSystem crash is observed with stack trace warning of use after\nfree. There are 2 signals to tell dpc_thread to terminate (UNLOADING\nflag and kthread_stop).\n\nOn setting the UNLOADING flag when dpc_thread happens to run at the time\nand sees the flag, this causes dpc_thread to exit and clean up\nitself. When kthread_stop is called for final cleanup, this causes use\nafter free.\n\nRemove UNLOADING signal to terminate dpc_thread.  Use the kthread_stop\nas the main signal to exit dpc_thread.\n\n[596663.812935] kernel BUG at mm/slub.c:294!\n[596663.812950] invalid opcode: 0000 [#1] SMP PTI\n[596663.812957] CPU: 13 PID: 1475935 Comm: rmmod Kdump: loaded Tainted: G          IOE    --------- -  - 4.18.0-240.el8.x86_64 #1\n[596663.812960] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 08/20/2012\n[596663.812974] RIP: 0010:__slab_free+0x17d/0x360\n\n...\n[596663.813008] Call Trace:\n[596663.813022]  ? __dentry_kill+0x121/0x170\n[596663.813030]  ? _cond_resched+0x15/0x30\n[596663.813034]  ? _cond_resched+0x15/0x30\n[596663.813039]  ? wait_for_completion+0x35/0x190\n[596663.813048]  ? try_to_wake_up+0x63/0x540\n[596663.813055]  free_task+0x5a/0x60\n[596663.813061]  kthread_stop+0xf3/0x100\n[596663.813103]  qla2x00_remove_one+0x284/0x440 [qla2xxx](CVE-2024-56623)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix LGR and link use-after-free issue\n\nWe encountered a LGR/link use-after-free issue, which manifested as\nthe LGR/link refcnt reaching 0 early and entering the clear process,\nmaking resource access unsafe.\n\n refcount_t: addition on 0; use-after-free.\n WARNING: CPU: 14 PID: 107447 at lib/refcount.c:25 refcount_warn_saturate+0x9c/0x140\n Workqueue: events smc_lgr_terminate_work [smc]\n Call trace:\n  refcount_warn_saturate+0x9c/0x140\n  __smc_lgr_terminate.part.45+0x2a8/0x370 [smc]\n  smc_lgr_terminate_work+0x28/0x30 [smc]\n  process_one_work+0x1b8/0x420\n  worker_thread+0x158/0x510\n  kthread+0x114/0x118\n\nor\n\n refcount_t: underflow; use-after-free.\n WARNING: CPU: 6 PID: 93140 at lib/refcount.c:28 refcount_warn_saturate+0xf0/0x140\n Workqueue: smc_hs_wq smc_listen_work [smc]\n Call trace:\n  refcount_warn_saturate+0xf0/0x140\n  smcr_link_put+0x1cc/0x1d8 [smc]\n  smc_conn_free+0x110/0x1b0 [smc]\n  smc_conn_abort+0x50/0x60 [smc]\n  smc_listen_find_device+0x75c/0x790 [smc]\n  smc_listen_work+0x368/0x8a0 [smc]\n  process_one_work+0x1b8/0x420\n  worker_thread+0x158/0x510\n  kthread+0x114/0x118\n\nIt is caused by repeated release of LGR/link refcnt. One suspect is that\nsmc_conn_free() is called repeatedly because some smc_conn_free() from\nserver listening path are not protected by sock lock.\n\ne.g.\n\nCalls under socklock        | smc_listen_work\n-------------------------------------------------------\nlock_sock(sk)               | smc_conn_abort\nsmc_conn_free               | \\- smc_conn_free\n\\- smcr_link_put            |    \\- smcr_link_put (duplicated)\nrelease_sock(sk)\n\nSo here add sock lock protection in smc_listen_work() path, making it\nexclusive with other connection operations.(CVE-2024-56640)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: initialize close_work early to avoid warning\n\nWe encountered a warning that close_work was canceled before\ninitialization.\n\n  WARNING: CPU: 7 PID: 111103 at kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0\n  Workqueue: events smc_lgr_terminate_work [smc]\n  RIP: 0010:__flush_work+0x19e/0x1b0\n  Call Trace:\n   ? __wake_up_common+0x7a/0x190\n   ? work_busy+0x80/0x80\n   __cancel_work_timer+0xe3/0x160\n   smc_close_cancel_work+0x1a/0x70 [smc]\n   smc_close_active_abort+0x207/0x360 [smc]\n   __smc_lgr_terminate.part.38+0xc8/0x180 [smc]\n   process_one_work+0x19e/0x340\n   worker_thread+0x30/0x370\n   ? process_one_work+0x340/0x340\n   kthread+0x117/0x130\n   ? __kthread_cancel_work+0x50/0x50\n   ret_from_fork+0x22/0x30\n\nThis is because when smc_close_cancel_work is triggered, e.g. the RDMA\ndriver is rmmod and the LGR is terminated, the conn-\u0026gt;close_work is\nflushed before initialization, resulting in WARN_ON(!work-\u0026gt;func).\n\n__smc_lgr_terminate             | smc_connect_{rdma|ism}\n-------------------------------------------------------------\n                                | smc_conn_create\n\t\t\t\t| \\- smc_lgr_register_conn\nfor conn in lgr-\u0026gt;conns_all      |\n\\- smc_conn_kill                |\n   \\- smc_close_active_abort    |\n      \\- smc_close_cancel_work  |\n         \\- cancel_work_sync    |\n            \\- __flush_work     |\n\t         (close_work)   |\n\t                        | smc_close_init\n\t                        | \\- INIT_WORK(\u0026amp;close_work)\n\nSo fix this by initializing close_work before establishing the\nconnection.(CVE-2024-56641)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btmtk: avoid UAF in btmtk_process_coredump\n\nhci_devcd_append may lead to the release of the skb, so it cannot be\naccessed once it is called.\n\n==================================================================\nBUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk]\nRead of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82\n\nCPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G     U             6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688c\nHardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024\nWorkqueue: events btusb_rx_work [btusb]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xfd/0x150\n print_report+0x131/0x780\n kasan_report+0x177/0x1c0\n btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01]\n btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec]\n btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec]\n worker_thread+0xe44/0x2cc0\n kthread+0x2ff/0x3a0\n ret_from_fork+0x51/0x80\n ret_from_fork_asm+0x1b/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 82:\n stack_trace_save+0xdc/0x190\n kasan_set_track+0x4e/0x80\n __kasan_slab_alloc+0x4e/0x60\n kmem_cache_alloc+0x19f/0x360\n skb_clone+0x132/0xf70\n btusb_recv_acl_mtk+0x104/0x1a0 [btusb]\n btusb_rx_work+0x9e/0xe0 [btusb]\n worker_thread+0xe44/0x2cc0\n kthread+0x2ff/0x3a0\n ret_from_fork+0x51/0x80\n ret_from_fork_asm+0x1b/0x30\n\nFreed by task 1733:\n stack_trace_save+0xdc/0x190\n kasan_set_track+0x4e/0x80\n kasan_save_free_info+0x28/0xb0\n ____kasan_slab_free+0xfd/0x170\n kmem_cache_free+0x183/0x3f0\n hci_devcd_rx+0x91a/0x2060 [bluetooth]\n worker_thread+0xe44/0x2cc0\n kthread+0x2ff/0x3a0\n ret_from_fork+0x51/0x80\n ret_from_fork_asm+0x1b/0x30\n\nThe buggy address belongs to the object at ffff888033cfab40\n which belongs to the cache skbuff_head_cache of size 232\nThe buggy address is located 112 bytes inside of\n freed 232-byte region [ffff888033cfab40, ffff888033cfac28)\n\nThe buggy address belongs to the physical page:\npage:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfa\nhead:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0\nanon flags: 0x4000000000000840(slab|head|zone=1)\npage_type: 0xffffffff()\nraw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001\nraw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n\nMemory state around the buggy address:\n ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc\n ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb\n\u0026gt;ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                                     ^\n ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc\n ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n==================================================================\n\nCheck if we need to call hci_devcd_complete before calling\nhci_devcd_append. That requires that we check data-\u0026gt;cd_info.cnt \u0026gt;=\nMTK_COREDUMP_NUM instead of data-\u0026gt;cd_info.cnt \u0026gt; MTK_COREDUMP_NUM, as we\nincrement data-\u0026gt;cd_info.cnt only once the call to hci_devcd_append\nsucceeds.(CVE-2024-56653)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/fadump: Move fadump_cma_init to setup_arch() after initmem_init()\n\nDuring early init CMA_MIN_ALIGNMENT_BYTES can be PAGE_SIZE,\nsince pageblock_order is still zero and it gets initialized\nlater during initmem_init() e.g.\nsetup_arch() -\u0026gt; initmem_init() -\u0026gt; sparse_init() -\u0026gt; set_pageblock_order()\n\nOne such use case where this causes issue is -\nearly_setup() -\u0026gt; early_init_devtree() -\u0026gt; fadump_reserve_mem() -\u0026gt; fadump_cma_init()\n\nThis causes CMA memory alignment check to be bypassed in\ncma_init_reserved_mem(). Then later cma_activate_area() can hit\na VM_BUG_ON_PAGE(pfn \u0026amp; ((1 \u0026lt;\u0026lt; order) - 1)) if the reserved memory\narea was not pageblock_order aligned.\n\nFix it by moving the fadump_cma_init() after initmem_init(),\nwhere other such cma reservations also gets called.\n\n\u0026lt;stack trace\u0026gt;\n==============\npage: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10010\nflags: 0x13ffff800000000(node=1|zone=0|lastcpupid=0x7ffff) CMA\nraw: 013ffff800000000 5deadbeef0000100 5deadbeef0000122 0000000000000000\nraw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000\npage dumped because: VM_BUG_ON_PAGE(pfn \u0026amp; ((1 \u0026lt;\u0026lt; order) - 1))\n------------[ cut here ]------------\nkernel BUG at mm/page_alloc.c:778!\n\nCall Trace:\n__free_one_page+0x57c/0x7b0 (unreliable)\nfree_pcppages_bulk+0x1a8/0x2c8\nfree_unref_page_commit+0x3d4/0x4e4\nfree_unref_page+0x458/0x6d0\ninit_cma_reserved_pageblock+0x114/0x198\ncma_init_reserved_areas+0x270/0x3e0\ndo_one_initcall+0x80/0x2f8\nkernel_init_freeable+0x33c/0x530\nkernel_init+0x34/0x26c\nret_from_kernel_user_thread+0x14/0x1c(CVE-2024-56677)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: musb: Fix hardware lockup on first Rx endpoint request\n\nThere is a possibility that a request\u0026apos;s callback could be invoked from\nusb_ep_queue() (call trace below, supplemented with missing calls):\n\nreq-\u0026gt;complete from usb_gadget_giveback_request\n\t(drivers/usb/gadget/udc/core.c:999)\nusb_gadget_giveback_request from musb_g_giveback\n\t(drivers/usb/musb/musb_gadget.c:147)\nmusb_g_giveback from rxstate\n\t(drivers/usb/musb/musb_gadget.c:784)\nrxstate from musb_ep_restart\n\t(drivers/usb/musb/musb_gadget.c:1169)\nmusb_ep_restart from musb_ep_restart_resume_work\n\t(drivers/usb/musb/musb_gadget.c:1176)\nmusb_ep_restart_resume_work from musb_queue_resume_work\n\t(drivers/usb/musb/musb_core.c:2279)\nmusb_queue_resume_work from musb_gadget_queue\n\t(drivers/usb/musb/musb_gadget.c:1241)\nmusb_gadget_queue from usb_ep_queue\n\t(drivers/usb/gadget/udc/core.c:300)\n\nAccording to the docstring of usb_ep_queue(), this should not happen:\n\n\u0026quot;Note that @req\u0026apos;s -\u0026gt;complete() callback must never be called from within\nusb_ep_queue() as that can create deadlock situations.\u0026quot;\n\nIn fact, a hardware lockup might occur in the following sequence:\n\n1. The gadget is initialized using musb_gadget_enable().\n2. Meanwhile, a packet arrives, and the RXPKTRDY flag is set, raising an\n   interrupt.\n3. If IRQs are enabled, the interrupt is handled, but musb_g_rx() finds an\n   empty queue (next_request() returns NULL). The interrupt flag has\n   already been cleared by the glue layer handler, but the RXPKTRDY flag\n   remains set.\n4. The first request is enqueued using usb_ep_queue(), leading to the call\n   of req-\u0026gt;complete(), as shown in the call trace above.\n5. If the callback enables IRQs and another packet is waiting, step (3)\n   repeats. The request queue is empty because usb_g_giveback() removes the\n   request before invoking the callback.\n6. The endpoint remains locked up, as the interrupt triggered by hardware\n   setting the RXPKTRDY flag has been handled, but the flag itself remains\n   set.\n\nFor this scenario to occur, it is only necessary for IRQs to be enabled at\nsome point during the complete callback. This happens with the USB Ethernet\ngadget, whose rx_complete() callback calls netif_rx(). If called in the\ntask context, netif_rx() disables the bottom halves (BHs). When the BHs are\nre-enabled, IRQs are also enabled to allow soft IRQs to be processed. The\ngadget itself is initialized at module load (or at boot if built-in), but\nthe first request is enqueued when the network interface is brought up,\ntriggering rx_complete() in the task context via ioctl(). If a packet\narrives while the interface is down, it can prevent the interface from\nreceiving any further packets from the USB host.\n\nThe situation is quite complicated with many parties involved. This\nparticular issue can be resolved in several possible ways:\n\n1. Ensure that callbacks never enable IRQs. This would be difficult to\n   enforce, as discovering how netif_rx() interacts with interrupts was\n   already quite challenging and u_ether is not the only function driver.\n   Similar \u0026quot;bugs\u0026quot; could be hidden in other drivers as well.\n2. Disable MUSB interrupts in musb_g_giveback() before calling the callback\n   and re-enable them afterwars (by calling musb_{dis,en}able_interrupts(),\n   for example). This would ensure that MUSB interrupts are not handled\n   during the callback, even if IRQs are enabled. In fact, it would allow\n   IRQs to be enabled when releasing the lock. However, this feels like an\n   inelegant hack.\n3. Modify the interrupt handler to clear the RXPKTRDY flag if the request\n   queue is empty. While this approach also feels like a hack, it wastes\n   CPU time by attempting to handle incoming packets when the software is\n   not ready to process them.\n4. Flush the Rx FIFO instead of calling rxstate() in musb_ep_restart().\n   This ensures that the hardware can receive packets when there is at\n   least one request in the queue. Once I\n---truncated---(CVE-2024-56687)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport\n\nSince transport-\u0026gt;sock has been set to NULL during reset transport,\nXPRT_SOCK_UPD_TIMEOUT also needs to be cleared. Otherwise, the\nxs_tcp_set_socket_timeouts() may be triggered in xs_tcp_send_request()\nto dereference the transport-\u0026gt;sock that has been set to NULL.(CVE-2024-56688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/pseries: Fix dtl_access_lock to be a rw_semaphore\n\nThe dtl_access_lock needs to be a rw_sempahore, a sleeping lock, because\nthe code calls kmalloc() while holding it, which can sleep:\n\n  # echo 1 \u0026gt; /proc/powerpc/vcpudispatch_stats\n  BUG: sleeping function called from invalid context at include/linux/sched/mm.h:337\n  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 199, name: sh\n  preempt_count: 1, expected: 0\n  3 locks held by sh/199:\n   #0: c00000000a0743f8 (sb_writers#3){.+.+}-{0:0}, at: vfs_write+0x324/0x438\n   #1: c0000000028c7058 (dtl_enable_mutex){+.+.}-{3:3}, at: vcpudispatch_stats_write+0xd4/0x5f4\n   #2: c0000000028c70b8 (dtl_access_lock){+.+.}-{2:2}, at: vcpudispatch_stats_write+0x220/0x5f4\n  CPU: 0 PID: 199 Comm: sh Not tainted 6.10.0-rc4 #152\n  Hardware name: IBM pSeries (emulated by qemu) POWER9 (raw) 0x4e1202 0xf000005 of:SLOF,HEAD hv:linux,kvm pSeries\n  Call Trace:\n    dump_stack_lvl+0x130/0x148 (unreliable)\n    __might_resched+0x174/0x410\n    kmem_cache_alloc_noprof+0x340/0x3d0\n    alloc_dtl_buffers+0x124/0x1ac\n    vcpudispatch_stats_write+0x2a8/0x5f4\n    proc_reg_write+0xf4/0x150\n    vfs_write+0xfc/0x438\n    ksys_write+0x88/0x148\n    system_call_exception+0x1c4/0x5a0\n    system_call_common+0xf4/0x258(CVE-2024-56701)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: protect link down work from execute after lgr freed\n\nlink down work may be scheduled before lgr freed but execute\nafter lgr freed, which may result in crash. So it is need to\nhold a reference before shedule link down work, and put the\nreference after work executed or canceled.\n\nThe relevant crash call stack as follows:\n list_del corruption. prev-\u0026gt;next should be ffffb638c9c0fe20,\n    but was 0000000000000000\n ------------[ cut here ]------------\n kernel BUG at lib/list_debug.c:51!\n invalid opcode: 0000 [#1] SMP NOPTI\n CPU: 6 PID: 978112 Comm: kworker/6:119 Kdump: loaded Tainted: G #1\n Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 2221b89 04/01/2014\n Workqueue: events smc_link_down_work [smc]\n RIP: 0010:__list_del_entry_valid.cold+0x31/0x47\n RSP: 0018:ffffb638c9c0fdd8 EFLAGS: 00010086\n RAX: 0000000000000054 RBX: ffff942fb75e5128 RCX: 0000000000000000\n RDX: ffff943520930aa0 RSI: ffff94352091fc80 RDI: ffff94352091fc80\n RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb638c9c0fc38\n R10: ffffb638c9c0fc30 R11: ffffffffa015eb28 R12: 0000000000000002\n R13: ffffb638c9c0fe20 R14: 0000000000000001 R15: ffff942f9cd051c0\n FS:  0000000000000000(0000) GS:ffff943520900000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f4f25214000 CR3: 000000025fbae004 CR4: 00000000007706e0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 55555554\n Call Trace:\n  rwsem_down_write_slowpath+0x17e/0x470\n  smc_link_down_work+0x3c/0x60 [smc]\n  process_one_work+0x1ac/0x350\n  worker_thread+0x49/0x2f0\n  ? rescuer_thread+0x360/0x360\n  kthread+0x118/0x140\n  ? __kthread_bind_mask+0x60/0x60\n  ret_from_fork+0x1f/0x30(CVE-2024-56718)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: Initialize cfid-\u0026gt;tcon before performing network ops\n\nAvoid leaking a tcon ref when a lease break races with opening the\ncached directory. Processing the leak break might take a reference to\nthe tcon in cached_dir_lease_break() and then fail to release the ref in\ncached_dir_offload_close, since cfid-\u0026gt;tcon is still NULL.(CVE-2024-56729)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: check folio mapping after unlock in relocate_one_folio()\n\nWhen we call btrfs_read_folio() to bring a folio uptodate, we unlock the\nfolio. The result of that is that a different thread can modify the\nmapping (like remove it with invalidate) before we call folio_lock().\nThis results in an invalid page and we need to try again.\n\nIn particular, if we are relocating concurrently with aborting a\ntransaction, this can result in a crash like the following:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000000\n  PGD 0 P4D 0\n  Oops: 0000 [#1] SMP\n  CPU: 76 PID: 1411631 Comm: kworker/u322:5\n  Workqueue: events_unbound btrfs_reclaim_bgs_work\n  RIP: 0010:set_page_extent_mapped+0x20/0xb0\n  RSP: 0018:ffffc900516a7be8 EFLAGS: 00010246\n  RAX: ffffea009e851d08 RBX: ffffea009e0b1880 RCX: 0000000000000000\n  RDX: 0000000000000000 RSI: ffffc900516a7b90 RDI: ffffea009e0b1880\n  RBP: 0000000003573000 R08: 0000000000000001 R09: ffff88c07fd2f3f0\n  R10: 0000000000000000 R11: 0000194754b575be R12: 0000000003572000\n  R13: 0000000003572fff R14: 0000000000100cca R15: 0000000005582fff\n  FS:  0000000000000000(0000) GS:ffff88c07fd00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 0000000000000000 CR3: 000000407d00f002 CR4: 00000000007706f0\n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n  PKRU: 55555554\n  Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die+0x78/0xc0\n  ? page_fault_oops+0x2a8/0x3a0\n  ? __switch_to+0x133/0x530\n  ? wq_worker_running+0xa/0x40\n  ? exc_page_fault+0x63/0x130\n  ? asm_exc_page_fault+0x22/0x30\n  ? set_page_extent_mapped+0x20/0xb0\n  relocate_file_extent_cluster+0x1a7/0x940\n  relocate_data_extent+0xaf/0x120\n  relocate_block_group+0x20f/0x480\n  btrfs_relocate_block_group+0x152/0x320\n  btrfs_relocate_chunk+0x3d/0x120\n  btrfs_reclaim_bgs_work+0x2ae/0x4e0\n  process_scheduled_works+0x184/0x370\n  worker_thread+0xc6/0x3e0\n  ? blk_add_timer+0xb0/0xb0\n  kthread+0xae/0xe0\n  ? flush_tlb_kernel_range+0x90/0x90\n  ret_from_fork+0x2f/0x40\n  ? flush_tlb_kernel_range+0x90/0x90\n  ret_from_fork_asm+0x11/0x20\n  \u0026lt;/TASK\u0026gt;\n\nThis occurs because cleanup_one_transaction() calls\ndestroy_delalloc_inodes() which calls invalidate_inode_pages2() which\ntakes the folio_lock before setting mapping to NULL. We fail to check\nthis, and subsequently call set_extent_mapping(), which assumes that\nmapping != NULL (in fact it asserts that in debug mode)\n\nNote that the \u0026quot;fixes\u0026quot; patch here is not the one that introduced the\nrace (the very first iteration of this code from 2009) but a more recent\nchange that made this particular crash happen in practice..(CVE-2024-56758)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg\n\nSyzbot reports [1] an uninitialized value issue found by KMSAN in\ndib3000_read_reg().\n\nLocal u8 rb[2] is used in i2c_transfer() as a read buffer; in case\nthat call fails, the buffer may end up with some undefined values.\n\nSince no elaborate error handling is expected in dib3000_write_reg(),\nsimply zero out rb buffer to mitigate the problem.\n\n[1] Syzkaller report\ndvb-usb: bulk message failed: -22 (6/0)\n=====================================================\nBUG: KMSAN: uninit-value in dib3000mb_attach+0x2d8/0x3c0 drivers/media/dvb-frontends/dib3000mb.c:758\n dib3000mb_attach+0x2d8/0x3c0 drivers/media/dvb-frontends/dib3000mb.c:758\n dibusb_dib3000mb_frontend_attach+0x155/0x2f0 drivers/media/usb/dvb-usb/dibusb-mb.c:31\n dvb_usb_adapter_frontend_init+0xed/0x9a0 drivers/media/usb/dvb-usb/dvb-usb-dvb.c:290\n dvb_usb_adapter_init drivers/media/usb/dvb-usb/dvb-usb-init.c:90 [inline]\n dvb_usb_init drivers/media/usb/dvb-usb/dvb-usb-init.c:186 [inline]\n dvb_usb_device_init+0x25a8/0x3760 drivers/media/usb/dvb-usb/dvb-usb-init.c:310\n dibusb_probe+0x46/0x250 drivers/media/usb/dvb-usb/dibusb-mb.c:110\n...\nLocal variable rb created at:\n dib3000_read_reg+0x86/0x4e0 drivers/media/dvb-frontends/dib3000mb.c:54\n dib3000mb_attach+0x123/0x3c0 drivers/media/dvb-frontends/dib3000mb.c:758\n...(CVE-2024-56769)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur\n\nThe action force umount(umount -f) will attempt to kill all rpc_task even\numount operation may ultimately fail if some files remain open.\nConsequently, if an action attempts to open a file, it can potentially\nsend two rpc_task to nfs server.\n\n                   NFS CLIENT\nthread1                             thread2\nopen(\u0026quot;file\u0026quot;)\n...\nnfs4_do_open\n _nfs4_do_open\n  _nfs4_open_and_get_state\n   _nfs4_proc_open\n    nfs4_run_open_task\n     /* rpc_task1 */\n     rpc_run_task\n     rpc_wait_for_completion_task\n\n                                    umount -f\n                                    nfs_umount_begin\n                                     rpc_killall_tasks\n                                      rpc_signal_task\n     rpc_task1 been wakeup\n     and return -512\n _nfs4_do_open // while loop\n    ...\n    nfs4_run_open_task\n     /* rpc_task2 */\n     rpc_run_task\n     rpc_wait_for_completion_task\n\nWhile processing an open request, nfsd will first attempt to find or\nallocate an nfs4_openowner. If it finds an nfs4_openowner that is not\nmarked as NFS4_OO_CONFIRMED, this nfs4_openowner will released. Since\ntwo rpc_task can attempt to open the same file simultaneously from the\nclient to server, and because two instances of nfsd can run\nconcurrently, this situation can lead to lots of memory leak.\nAdditionally, when we echo 0 to /proc/fs/nfsd/threads, warning will be\ntriggered.\n\n                    NFS SERVER\nnfsd1                  nfsd2       echo 0 \u0026gt; /proc/fs/nfsd/threads\n\nnfsd4_open\n nfsd4_process_open1\n  find_or_alloc_open_stateowner\n   // alloc oo1, stateid1\n                       nfsd4_open\n                        nfsd4_process_open1\n                        find_or_alloc_open_stateowner\n                        // find oo1, without NFS4_OO_CONFIRMED\n                         release_openowner\n                          unhash_openowner_locked\n                          list_del_init(\u0026amp;oo-\u0026gt;oo_perclient)\n                          // cannot find this oo\n                          // from client, LEAK!!!\n                         alloc_stateowner // alloc oo2\n\n nfsd4_process_open2\n  init_open_stateid\n  // associate oo1\n  // with stateid1, stateid1 LEAK!!!\n  nfs4_get_vfs_file\n  // alloc nfsd_file1 and nfsd_file_mark1\n  // all LEAK!!!\n\n                         nfsd4_process_open2\n                         ...\n\n                                    write_threads\n                                     ...\n                                     nfsd_destroy_serv\n                                      nfsd_shutdown_net\n                                       nfs4_state_shutdown_net\n                                        nfs4_state_destroy_net\n                                         destroy_client\n                                          __destroy_client\n                                          // won\u0026apos;t find oo1!!!\n                                     nfsd_shutdown_generic\n                                      nfsd_file_cache_shutdown\n                                       kmem_cache_destroy\n                                       for nfsd_file_slab\n                                       and nfsd_file_mark_slab\n                                       // bark since nfsd_file1\n                                       // and nfsd_file_mark1\n                                       // still alive\n\n=======================================================================\nBUG nfsd_file (Not tainted): Objects remaining in nfsd_file on\n__kmem_cache_shutdown()\n-----------------------------------------------------------------------\n\nSlab 0xffd4000004438a80 objects=34 used=1 fp=0xff11000110e2ad28\nflags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff)\nCPU: 4 UID: 0 PID: 757 Comm: sh Not tainted 6.12.0-rc6+ #19\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.16.1-2.fc37 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dum\n---truncated---(CVE-2024-56779)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: imx6: Fix suspend/resume support on i.MX6QDL\n\nThe suspend/resume functionality is currently broken on the i.MX6QDL\nplatform, as documented in the NXP errata (ERR005723):\n\n  https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf\n\nThis patch addresses the issue by sharing most of the suspend/resume\nsequences used by other i.MX devices, while avoiding modifications to\ncritical registers that disrupt the PCIe functionality. It targets the\nsame problem as the following downstream commit:\n\n  https://github.com/nxp-imx/linux-imx/commit/4e92355e1f79d225ea842511fcfd42b343b32995\n\nUnlike the downstream commit, this patch also resets the connected PCIe\ndevice if possible. Without this reset, certain drivers, such as ath10k\nor iwlwifi, will crash on resume. The device reset is also done by the\ndriver on other i.MX platforms, making this patch consistent with\nexisting practices.\n\nUpon resuming, the kernel will hang and display an error. Here\u0026apos;s an\nexample of the error encountered with the ath10k driver:\n\n  ath10k_pci 0000:01:00.0: Unable to change power state from D3hot to D0, device inaccessible\n  Unhandled fault: imprecise external abort (0x1406) at 0x0106f944\n\nWithout this patch, suspend/resume will fail on i.MX6QDL devices if a\nPCIe device is connected.\n\n[kwilczynski: commit log, added tag for stable releases](CVE-2024-57809)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL\n\nCurrently tagged_addr_ctrl_set() doesn\u0026apos;t initialize the temporary \u0026apos;ctrl\u0026apos;\nvariable, and a SETREGSET call with a length of zero will leave this\nuninitialized. Consequently tagged_addr_ctrl_set() will consume an\narbitrary value, potentially leaking up to 64 bits of memory from the\nkernel stack. The read is limited to a specific slot on the stack, and\nthe issue does not provide a write mechanism.\n\nAs set_tagged_addr_ctrl() only accepts values where bits [63:4] zero and\nrejects other values, a partial SETREGSET attempt will randomly succeed\nor fail depending on the value of the uninitialized value, and the\nexposure is significantly limited.\n\nFix this by initializing the temporary value before copying the regset\nfrom userspace, as for other regsets (e.g. NT_PRSTATUS, NT_PRFPREG,\nNT_ARM_SYSTEM_CALL). In the case of a zero-length write, the existing\nvalue of the tagged address ctrl will be retained.\n\nThe NT_ARM_TAGGED_ADDR_CTRL regset is only visible in the\nuser_aarch64_view used by a native AArch64 task to manipulate another\nnative AArch64 task. As get_tagged_addr_ctrl() only returns an error\nvalue when called for a compat task, tagged_addr_ctrl_get() and\ntagged_addr_ctrl_set() should never observe an error value from\nget_tagged_addr_ctrl(). Add a WARN_ON_ONCE() to both to indicate that\nsuch an error would be unexpected, and error handlnig is not missing in\neither case.(CVE-2024-57874)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix slab-use-after-free due to dangling pointer dqi_priv\n\nWhen mounting ocfs2 and then remounting it as read-only, a\nslab-use-after-free occurs after the user uses a syscall to\nquota_getnextquota.  Specifically, sb_dqinfo(sb, type)-\u0026gt;dqi_priv is the\ndangling pointer.\n\nDuring the remounting process, the pointer dqi_priv is freed but is never\nset as null leaving it to be accessed.  Additionally, the read-only option\nfor remounting sets the DQUOT_SUSPENDED flag instead of setting the\nDQUOT_USAGE_ENABLED flags.  Moreover, later in the process of getting the\nnext quota, the function ocfs2_get_next_id is called and only checks the\nquota usage flags and not the quota suspended flags.\n\nTo fix this, I set dqi_priv to null when it is freed after remounting with\nread-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id.\n\n[akpm@linux-foundation.org: coding-style cleanups](CVE-2024-57892)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: adc: ti-ads8688: fix information leak in triggered buffer\n\nThe \u0026apos;buffer\u0026apos; local array is used to push data to user space from a\ntriggered buffer, but it does not set values for inactive channels, as\nit only uses iio_for_each_active_channel() to assign new values.\n\nInitialize the array to zero before using it to avoid pushing\nuninitialized information to userspace.(CVE-2024-57906)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: light: vcnl4035: fix information leak in triggered buffer\n\nThe \u0026apos;buffer\u0026apos; local array is used to push data to userspace from a\ntriggered buffer, but it does not set an initial value for the single\ndata element, which is an u16 aligned to 8 bytes. That leaves at least\n4 bytes uninitialized even after writing an integer value with\nregmap_read().\n\nInitialize the array to zero before using it to avoid pushing\nuninitialized information to userspace.(CVE-2024-57910)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntopology: Keep the cpumask unchanged when printing cpumap\n\nDuring fuzz testing, the following warning was discovered:\n\n different return values (15 and 11) from vsnprintf(\u0026quot;%*pbl\n \u0026quot;, ...)\n\n test:keyward is WARNING in kvasprintf\n WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130\n Call Trace:\n  kvasprintf+0x121/0x130\n  kasprintf+0xa6/0xe0\n  bitmap_print_to_buf+0x89/0x100\n  core_siblings_list_read+0x7e/0xb0\n  kernfs_file_read_iter+0x15b/0x270\n  new_sync_read+0x153/0x260\n  vfs_read+0x215/0x290\n  ksys_read+0xb9/0x160\n  do_syscall_64+0x56/0x100\n  entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nThe call trace shows that kvasprintf() reported this warning during the\nprinting of core_siblings_list. kvasprintf() has several steps:\n\n (1) First, calculate the length of the resulting formatted string.\n\n (2) Allocate a buffer based on the returned length.\n\n (3) Then, perform the actual string formatting.\n\n (4) Check whether the lengths of the formatted strings returned in\n     steps (1) and (2) are consistent.\n\nIf the core_cpumask is modified between steps (1) and (3), the lengths\nobtained in these two steps may not match. Indeed our test includes cpu\nhotplugging, which should modify core_cpumask while printing.\n\nTo fix this issue, cache the cpumask into a temporary variable before\ncalling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged\nduring the printing process.(CVE-2024-57917)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Add check for granularity in dml ceil/floor helpers\n\n[Why]\nWrapper functions for dcn_bw_ceil2() and dcn_bw_floor2()\nshould check for granularity is non zero to avoid assert and\ndivide-by-zero error in dcn_bw_ functions.\n\n[How]\nAdd check for granularity 0.\n\n(cherry picked from commit f6e09701c3eb2ccb8cb0518e0b67f1c69742a4ec)(CVE-2024-57922)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Set private-\u0026gt;all_drm_private[i]-\u0026gt;drm to NULL if mtk_drm_bind returns err\n\nThe pointer need to be set to NULL, otherwise KASAN complains about\nuse-after-free. Because in mtk_drm_bind, all private\u0026apos;s drm are set\nas follows.\n\nprivate-\u0026gt;all_drm_private[i]-\u0026gt;drm = drm;\n\nAnd drm will be released by drm_dev_put in case mtk_drm_kms_init returns\nfailure. However, the shutdown path still accesses the previous allocated\nmemory in drm_atomic_helper_shutdown.\n\n[   84.874820] watchdog: watchdog0: watchdog did not stop!\n[   86.512054] ==================================================================\n[   86.513162] BUG: KASAN: use-after-free in drm_atomic_helper_shutdown+0x33c/0x378\n[   86.514258] Read of size 8 at addr ffff0000d46fc068 by task shutdown/1\n[   86.515213]\n[   86.515455] CPU: 1 UID: 0 PID: 1 Comm: shutdown Not tainted 6.13.0-rc1-mtk+gfa1a78e5d24b-dirty #55\n[   86.516752] Hardware name: Unknown Product/Unknown Product, BIOS 2022.10 10/01/2022\n[   86.517960] Call trace:\n[   86.518333]  show_stack+0x20/0x38 (C)\n[   86.518891]  dump_stack_lvl+0x90/0xd0\n[   86.519443]  print_report+0xf8/0x5b0\n[   86.519985]  kasan_report+0xb4/0x100\n[   86.520526]  __asan_report_load8_noabort+0x20/0x30\n[   86.521240]  drm_atomic_helper_shutdown+0x33c/0x378\n[   86.521966]  mtk_drm_shutdown+0x54/0x80\n[   86.522546]  platform_shutdown+0x64/0x90\n[   86.523137]  device_shutdown+0x260/0x5b8\n[   86.523728]  kernel_restart+0x78/0xf0\n[   86.524282]  __do_sys_reboot+0x258/0x2f0\n[   86.524871]  __arm64_sys_reboot+0x90/0xd8\n[   86.525473]  invoke_syscall+0x74/0x268\n[   86.526041]  el0_svc_common.constprop.0+0xb0/0x240\n[   86.526751]  do_el0_svc+0x4c/0x70\n[   86.527251]  el0_svc+0x4c/0xc0\n[   86.527719]  el0t_64_sync_handler+0x144/0x168\n[   86.528367]  el0t_64_sync+0x198/0x1a0\n[   86.528920]\n[   86.529157] The buggy address belongs to the physical page:\n[   86.529972] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff0000d46fd4d0 pfn:0x1146fc\n[   86.531319] flags: 0xbfffc0000000000(node=0|zone=2|lastcpupid=0xffff)\n[   86.532267] raw: 0bfffc0000000000 0000000000000000 dead000000000122 0000000000000000\n[   86.533390] raw: ffff0000d46fd4d0 0000000000000000 00000000ffffffff 0000000000000000\n[   86.534511] page dumped because: kasan: bad access detected\n[   86.535323]\n[   86.535559] Memory state around the buggy address:\n[   86.536265]  ffff0000d46fbf00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.537314]  ffff0000d46fbf80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.538363] \u0026gt;ffff0000d46fc000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.544733]                                                           ^\n[   86.551057]  ffff0000d46fc080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.557510]  ffff0000d46fc100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.563928] ==================================================================\n[   86.571093] Disabling lock debugging due to kernel taint\n[   86.577642] Unable to handle kernel paging request at virtual address e0e9c0920000000b\n[   86.581834] KASAN: maybe wild-memory-access in range [0x0752049000000058-0x075204900000005f]\n...(CVE-2024-57926)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure shadow stack is active before \u0026quot;getting\u0026quot; registers\n\nThe x86 shadow stack support has its own set of registers. Those registers\nare XSAVE-managed, but they are \u0026quot;supervisor state components\u0026quot; which means\nthat userspace can not touch them with XSAVE/XRSTOR.  It also means that\nthey are not accessible from the existing ptrace ABI for XSAVE state.\nThus, there is a new ptrace get/set interface for it.\n\nThe regset code that ptrace uses provides an -\u0026gt;active() handler in\naddition to the get/set ones. For shadow stack this -\u0026gt;active() handler\nverifies that shadow stack is enabled via the ARCH_SHSTK_SHSTK bit in the\nthread struct. The -\u0026gt;active() handler is checked from some call sites of\nthe regset get/set handlers, but not the ptrace ones. This was not\nunderstood when shadow stack support was put in place.\n\nAs a result, both the set/get handlers can be called with\nXFEATURE_CET_USER in its init state, which would cause get_xsave_addr() to\nreturn NULL and trigger a WARN_ON(). The ssp_set() handler luckily has an\nssp_active() check to avoid surprising the kernel with shadow stack\nbehavior when the kernel is not ready for it (ARCH_SHSTK_SHSTK==0). That\ncheck just happened to avoid the warning.\n\nBut the -\u0026gt;get() side wasn\u0026apos;t so lucky. It can be called with shadow stacks\ndisabled, triggering the warning in practice, as reported by Christina\nSchimpe:\n\nWARNING: CPU: 5 PID: 1773 at arch/x86/kernel/fpu/regset.c:198 ssp_get+0x89/0xa0\n[...]\nCall Trace:\n\u0026lt;TASK\u0026gt;\n? show_regs+0x6e/0x80\n? ssp_get+0x89/0xa0\n? __warn+0x91/0x150\n? ssp_get+0x89/0xa0\n? report_bug+0x19d/0x1b0\n? handle_bug+0x46/0x80\n? exc_invalid_op+0x1d/0x80\n? asm_exc_invalid_op+0x1f/0x30\n? __pfx_ssp_get+0x10/0x10\n? ssp_get+0x89/0xa0\n? ssp_get+0x52/0xa0\n__regset_get+0xad/0xf0\ncopy_regset_to_user+0x52/0xc0\nptrace_regset+0x119/0x140\nptrace_request+0x13c/0x850\n? wait_task_inactive+0x142/0x1d0\n? do_syscall_64+0x6d/0x90\narch_ptrace+0x102/0x300\n[...]\n\nEnsure that shadow stacks are active in a thread before looking them up\nin the XSAVE buffer. Since ARCH_SHSTK_SHSTK and user_ssp[SHSTK_EN] are\nset at the same time, the active check ensures that there will be\nsomething to find in the XSAVE buffer.\n\n[ dhansen: changelog/subject tweaks ](CVE-2025-21632)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: avoid NULL pointer dereference if no valid extent tree\n\n[BUG]\nSyzbot reported a crash with the following call trace:\n\n  BTRFS info (device loop0): scrub: started on devid 1\n  BUG: kernel NULL pointer dereference, address: 0000000000000208\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 106e70067 P4D 106e70067 PUD 107143067 PMD 0\n  Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 UID: 0 PID: 689 Comm: repro Kdump: loaded Tainted: G           O       6.13.0-rc4-custom+ #206\n  Tainted: [O]=OOT_MODULE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022\n  RIP: 0010:find_first_extent_item+0x26/0x1f0 [btrfs]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   scrub_find_fill_first_stripe+0x13d/0x3b0 [btrfs]\n   scrub_simple_mirror+0x175/0x260 [btrfs]\n   scrub_stripe+0x5d4/0x6c0 [btrfs]\n   scrub_chunk+0xbb/0x170 [btrfs]\n   scrub_enumerate_chunks+0x2f4/0x5f0 [btrfs]\n   btrfs_scrub_dev+0x240/0x600 [btrfs]\n   btrfs_ioctl+0x1dc8/0x2fa0 [btrfs]\n   ? do_sys_openat2+0xa5/0xf0\n   __x64_sys_ioctl+0x97/0xc0\n   do_syscall_64+0x4f/0x120\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\n[CAUSE]\nThe reproducer is using a corrupted image where extent tree root is\ncorrupted, thus forcing to use \u0026quot;rescue=all,ro\u0026quot; mount option to mount the\nimage.\n\nThen it triggered a scrub, but since scrub relies on extent tree to find\nwhere the data/metadata extents are, scrub_find_fill_first_stripe()\nrelies on an non-empty extent root.\n\nBut unfortunately scrub_find_fill_first_stripe() doesn\u0026apos;t really expect\nan NULL pointer for extent root, it use extent_root to grab fs_info and\ntriggered a NULL pointer dereference.\n\n[FIX]\nAdd an extra check for a valid extent root at the beginning of\nscrub_find_fill_first_stripe().\n\nThe new error path is introduced by 42437a6386ff (\u0026quot;btrfs: introduce\nmount option rescue=ignorebadroots\u0026quot;), but that\u0026apos;s pretty old, and later\ncommit b979547513ff (\u0026quot;btrfs: scrub: introduce helper to find and fill\nsector info for a scrub_stripe\u0026quot;) changed how we do scrub.\n\nSo for kernels older than 6.6, the fix will need manual backport.(CVE-2025-21658)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/bpf: return early if transport is not assigned\n\nSome of the core functions can only be called if the transport\nhas been assigned.\n\nAs Michal reported, a socket might have the transport at NULL,\nfor example after a failed connect(), causing the following trace:\n\n    BUG: kernel NULL pointer dereference, address: 00000000000000a0\n    #PF: supervisor read access in kernel mode\n    #PF: error_code(0x0000) - not-present page\n    PGD 12faf8067 P4D 12faf8067 PUD 113670067 PMD 0\n    Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI\n    CPU: 15 UID: 0 PID: 1198 Comm: a.out Not tainted 6.13.0-rc2+\n    RIP: 0010:vsock_connectible_has_data+0x1f/0x40\n    Call Trace:\n     vsock_bpf_recvmsg+0xca/0x5e0\n     sock_recvmsg+0xb9/0xc0\n     __sys_recvfrom+0xb3/0x130\n     __x64_sys_recvfrom+0x20/0x30\n     do_syscall_64+0x93/0x180\n     entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nSo we need to check the `vsk-\u0026gt;transport` in vsock_bpf_recvmsg(),\nespecially for connected sockets (stream/seqpacket) as we already\ndo in __vsock_connectible_recvmsg().(CVE-2025-21670)","status":"published","published":"2025-02-08T11:08:11Z","modified":"2026-08-18T01:18:47.021739645Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"RHSA-2024: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":"ROOT-OS-DEBIAN-11-CVE-2024-40965","title":"CVE-2024-40965 in linux - Patched by Root","description":"Root has patched CVE-2024-40965 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:19:37.740297516Z","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:53:29.077857Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2024-40965","title":"CVE-2024-40965 in linux - Patched by Root","description":"Root has patched CVE-2024-40965 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:17:38.01754876Z","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:53:30.70924Z"},{"id":"UBUNTU-CVE-2024-40965","description":"In the Linux kernel, the following vulnerability has been resolved: i2c: lpi2c: Avoid calling clk_get_rate during transfer Instead of repeatedly calling clk_get_rate for each transfer, lock the clock rate and cache the value. A deadlock has been observed while adding tlv320aic32x4 audio codec to the system. When this clock provider adds its clock, the clk mutex is locked already, it needs to access i2c, which in return needs the mutex for clk_get_rate as well.","status":"published","published":"2024-07-12T13:15:00Z","modified":"2026-11-10T02:49:08.431134504Z","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-10T03:17:56.57255Z"},{"id":"CVE-2024-40965","title":"i2c: lpi2c: Avoid calling clk_get_rate during transfer","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: lpi2c: Avoid calling clk_get_rate during transfer\n\nInstead of repeatedly calling clk_get_rate for each transfer, lock\nthe clock rate and cache the value.\nA deadlock has been observed while adding tlv320aic32x4 audio codec to\nthe system. When this clock provider adds its clock, the clk mutex is\nlocked already, it needs to access i2c, which in return needs the mutex\nfor clk_get_rate as well.","status":"published","published":"2024-07-12T12:32:05.453Z","modified":"2026-10-28T02:30:34.265556473Z","updated_at":"2026-11-02T15:44:41.618074Z"},{"id":"SUSE-SU-2024:3551-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- Drop soundwire patch that caused a regression (bsc#1230350)\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- Move s390 kabi patch into the kabi section\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- Revert 'drm/amdgpu: align pp_power_profile_mode with kernel docs' (stable-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section'  (bsc#1230413)\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage' (bsc#1230413)\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()' (bsc#1230413)\n- Split kabi part of dm_blk_ioctl-implement-path-failover-for-SG_IO.patch\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) Move patch into the sorted section.\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Split kABI out of 'io_uring/kbuf: get rid of bl-\u003eis_ready'\n- kABI: Split kABI out of 'io_uring: Re-add dummy_ubuf for kABI purposes'\n- kABI: Split kABI out of io_uring/kbuf: protect io_buffer_list teardown with a reference\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-08T15:03:16Z","modified":"2026-02-04T03:53:54.665546Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3553-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 CoCo kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46727: Fixed NULL pointer dereference in resource_log_pipe_topology_update (bsc#1230707).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- Drop soundwire patch that caused a regression (bsc#1230350) \n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) \n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section' \n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage' \n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- Squashfs: sanity check symbolic link size (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-08T15:10:23Z","modified":"2026-02-04T02:15:47.571482Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3561-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- Revert 'drm/amdgpu: align pp_power_profile_mode with kernel docs' (stable-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage'\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()'\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-09T08:45:13Z","modified":"2026-02-04T03:42:46.6666Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3564-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Merge branch 'SLE15-SP6' (ea7c56db3e5d) into 'SLE15-SP6-RT'\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- No -rt specific changes this merge.\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for 'dra7xx-pcie-main' IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert 'Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE' (git-fixes).\n- Revert 'PCI: Extend ACS configurability (bsc#1228090).' (bsc#1229019)\n- Revert 'drm/amdgpu: align pp_power_profile_mode with kernel docs' (stable-fixes).\n- Revert 'media: tuners: fix error return code of hybrid_tuner_request_state()' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section'\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage'\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()'\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Split kABI out of 'io_uring/kbuf: get rid of bl-\u003eis_ready'\n- kABI: Split kABI out of 'io_uring: Re-add dummy_ubuf for kABI purposes'\n- kABI: Split kABI out of io_uring/kbuf: protect io_buffer_list teardown with a reference\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for '/tmp/perf-$PID.map' files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2024-10-09T09:09:06Z","modified":"2026-02-04T02:58:51.061674Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3983-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48879: efi: fix NULL-deref in init error path (bsc#1229556).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48957: dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove() (bsc#1231973).\n- CVE-2022-48958: ethernet: aeroflex: fix potential skb leak in greth_init_rings() (bsc#1231889).\n- CVE-2022-48959: net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions() (bsc#1231976).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48966: net: mvneta: Fix an out of bounds check (bsc#1232191).\n- CVE-2022-48980: net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing() (bsc#1232233).\n- CVE-2022-48991: mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma (bsc#1232070 git-fix prerequisity).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2022-49017: tipc: re-fetch skb cb after tipc_msg_validate (bsc#1232004).\n- CVE-2022-49020: net/9p: Fix a potential socket leak in p9_socket_open (bsc#1232175).\n- CVE-2024-36244: net/sched: taprio: extend minimum interval restriction to entire cycle too (bsc#1226797).\n- CVE-2024-36957: octeontx2-af: avoid off-by-one read from userspace (bsc#1225762).\n- CVE-2024-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (bsc#1227437).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-42226: Prevent potential failure in handle_tx_event() for Transfer events without TRB (bsc#1228709).\n- CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race (bsc#1229005 stable-fixes).\n- CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc() (bsc#1229837 stable-fixes).\n- CVE-2024-44958: sched/smt: Fix unbalance sched_smt_present dec/inc (bsc#1230179).\n- CVE-2024-45016: netem: fix return value if duplicate enqueue fails (bsc#1230429).\n- CVE-2024-45025: fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE (bsc#1230456).\n- CVE-2024-46716: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (bsc#1230715).\n- CVE-2024-46754: bpf: Remove tst_run from lwt_seg6local_prog_ops (bsc#1230801).\n- CVE-2024-46777: udf: Avoid excessive partition lengths (bsc#1230773).\n- CVE-2024-46809: drm/amd/display: Check BIOS images before it is used (bsc#1231148).\n- CVE-2024-46811: drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (bsc#1231179).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46814: drm/amd/display: Check msg_id before processing transcation (bsc#1231193).\n- CVE-2024-46815: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets (bsc#1231195).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46817: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (bsc#1231200).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46828: uprobes: fix kernel info leak via '[uprobes]' vma (bsc#1231114).\n- CVE-2024-46834: ethtool: fail closed if we can't get max channel used in indirection tables (bsc#1231096).\n- CVE-2024-46840: btrfs: clean up our handling of refs == 0 in snapshot delete (bsc#1231105).\n- CVE-2024-46841: btrfs: do not BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (bsc#1231094).\n- CVE-2024-46848: perf/x86/intel: Limit the period on Haswell (bsc#1231072).\n- CVE-2024-46849: ASoC: meson: axg-card: fix 'use-after-free' (bsc#1231073).\n- CVE-2024-47660: fsnotify: clear PARENT_WATCHED flags lazily (bsc#1231439).\n- CVE-2024-47661: drm/amd/display: Avoid overflow from uint32_t to uint8_t (bsc#1231496).\n- CVE-2024-47664: spi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware (bsc#1231442).\n- CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (bsc#1231502).\n- CVE-2024-47672: wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (bsc#1231540).\n- CVE-2024-47673: wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (bsc#1231539).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47685: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() (bsc#1231998).\n- CVE-2024-47692: nfsd: return -EINVAL when namelen is 0 (bsc#1231857).\n- CVE-2024-47704: drm/amd/display: Check link_res-\u003ehpo_dp_link_enc before using it (bsc#1231944).\n- CVE-2024-47705: block: fix potential invalid pointer dereference in blk_add_partition (bsc#1231872).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47707: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (bsc#1231935).\n- CVE-2024-47710: sock_map: Add a cond_resched() in sock_hash_free() (bsc#1232049).\n- CVE-2024-47720: drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (bsc#1232043).\n- CVE-2024-47727: x86/tdx: Fix 'in-kernel MMIO' check (bsc#1232116).\n- CVE-2024-47730: crypto: hisilicon/qm - inject error before stopping queue (bsc#1232075).\n- CVE-2024-47738: wifi: mac80211: do not use rate mask for offchannel TX either (bsc#1232114).\n- CVE-2024-47739: padata: use integer wrap around to prevent deadlock on seq_nr overflow (bsc#1232124).\n- CVE-2024-47745: mm: split critical region in remap_file_pages() and invoke LSMs in between (bsc#1232135).\n- CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition (bsc#1232145).\n- CVE-2024-47748: vhost_vdpa: assign irq bypass producer token correctly (bsc#1232174).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49866: tracing/timerlat: Fix a race during cpuhp processing (bsc#1232259).\n- CVE-2024-49881: ext4: update orig_path in ext4_find_extent() (bsc#1232201).\n- CVE-2024-49882: ext4: fix double brelse() the buffer of the extents path (bsc#1232200).\n- CVE-2024-49883: ext4: aovid use-after-free in ext4_ext_insert_extent() (bsc#1232199).\n- CVE-2024-49886: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug (bsc#1232196).\n- CVE-2024-49890: drm/amd/pm: ensure the fw_info is not null before using it (bsc#1232217).\n- CVE-2024-49892: drm/amd/display: Initialize get_bytes_per_element's default to 1 (bsc#1232220).\n- CVE-2024-49896: drm/amd/display: Check stream before comparing them (bsc#1232221).\n- CVE-2024-49897: drm/amd/display: Check phantom_stream before it is used (bsc#1232355).\n- CVE-2024-49899: drm/amd/display: Initialize denominators' default to 1 (bsc#1232358).\n- CVE-2024-49901: drm/msm/adreno: Assign msm_gpu-\u003epdev earlier to avoid nullptrs (bsc#1232305).\n- CVE-2024-49906: drm/amd/display: Check null pointer before try to access it (bsc#1232332).\n- CVE-2024-49909: drm/amd/display: Add NULL check for function pointer in dcn32_set_output_transfer_func (bsc#1232337).\n- CVE-2024-49911: drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func (bsc#1232366).\n- CVE-2024-49914: drm/amd/display: Add null check for pipe_ctx-\u003eplane_state in (bsc#1232369).\n- CVE-2024-49917: drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u003efuncs in dcn30_init_hw (bsc#1231965).\n- CVE-2024-49918: drm/amd/display: Add null check for head_pipe in dcn32_acquire_idle_pipe_for_head_pipe_in_layer (bsc#1231967).\n- CVE-2024-49919: drm/amd/display: Add null check for head_pipe in dcn201_acquire_free_pipe_for_layer (bsc#1231968).\n- CVE-2024-49920: drm/amd/display: Check null pointers before multiple uses (bsc#1232313).\n- CVE-2024-49922: drm/amd/display: Check null pointers before using them (bsc#1232374).\n- CVE-2024-49923: drm/amd/display: Pass non-null to dcn20_validate_apply_pipe_split_flags (bsc#1232361).\n- CVE-2024-49929: wifi: iwlwifi: mvm: avoid NULL pointer dereference (bsc#1232253).\n- CVE-2024-49930: wifi: ath11k: fix array out-of-bound access in SoC stats (bsc#1232260).\n- CVE-2024-49933: blk_iocost: fix more out of bound shifts (bsc#1232368).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49939: wifi: rtw89: avoid to add interface to list twice when SER (bsc#1232381).\n- CVE-2024-49946: ppp: do not assume bh is held in ppp_channel_bridge_input() (bsc#1232164).\n- CVE-2024-49949: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (bsc#1232160).\n- CVE-2024-49954: static_call: Replace pointless WARN_ON() in static_call_module_notify() (bsc#1232155).\n- CVE-2024-49955: ACPI: battery: Fix possible crash when unregistering a battery hook (bsc#1232154).\n- CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree (bsc#1232151).\n- CVE-2024-49959: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error (bsc#1232149).\n- CVE-2024-49960: ext4: fix timer use-after-free on failed mount (bsc#1232395).\n- CVE-2024-49967: ext4: no need to continue when the number of entries is 1 (bsc#1232140).\n- CVE-2024-49969: drm/amd/display: Fix index out of bounds in DCN30 color transformation (bsc#1232519).\n- CVE-2024-49973: r8169: add tally counter fields added with RTL8125 (bsc#1232105).\n- CVE-2024-49974: NFSD: Force all NFSv4.2 COPY requests to be synchronous (bsc#1232383).\n- CVE-2024-49975: uprobes: fix kernel info leak via '[uprobes]' vma (bsc#1232104).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49993: iommu/vt-d: Fix potential lockup if qi_submit_sync called with 0 count (bsc#1232316).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-50000: net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() (bsc#1232085).\n- CVE-2024-50001: net/mlx5: Fix error path in multi-packet WQE transmit (bsc#1232084).\n- CVE-2024-50002: static_call: Handle module init failure correctly in static_call_del_module() (bsc#1232083).\n- CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate() (bsc#1232442).\n- CVE-2024-50014: ext4: fix access to uninitialised lock in fc replay path (bsc#1232446).\n- CVE-2024-50019: kthread: unpark only parked kthread (bsc#1231990).\n- CVE-2024-50024: net: Fix an unsafe loop on the list (bsc#1231954).\n- CVE-2024-50028: thermal: core: Reference count the zone in thermal_zone_get_by_id() (bsc#1231950).\n- CVE-2024-50033: slip: make slhc_remember() more robust against malicious packets (bsc#1231914).\n- CVE-2024-50035: ppp: fix ppp_async_encode() illegal access (bsc#1232392).\n- CVE-2024-50041: i40e: Fix macvlan leak by synchronizing access to mac_filter_hash (bsc#1231907).\n- CVE-2024-50045: netfilter: br_netfilter: fix panic with metadata_dst skb (bsc#1231903).\n- CVE-2024-50046: kabi fix for NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() (bsc#1231902).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n- CVE-2024-50048: fbcon: Fix a NULL pointer dereference issue in fbcon_putcs (bsc#1232310).\n- CVE-2024-50055: driver core: bus: Fix double free in driver API bus_register() (bsc#1232329).\n- CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too (bsc#1232285).\n- CVE-2024-50059: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition (bsc#1232345).\n- CVE-2024-50061: i3c: master: cdns: Fix use after free vulnerability in cdns_i3c_master Driver Due to Race Condition (bsc#1232263).\n- CVE-2024-50063: kABI: bpf: struct bpf_map kABI workaround (bsc#1232435).\n- CVE-2024-50081: blk-mq: setup queue -\u003etag_set before initializing hctx (bsc#1232501).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: Do not release locks during operation region accesses (stable-fixes).\n- ACPI: PAD: fix crash in exit_round_robin() (stable-fixes).\n- ACPI: PRM: Clean up guid type in struct prm_handler_info (git-fixes).\n- ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context (git-fixes).\n- ACPI: battery: Call power_supply_changed() when adding hooks (bsc#1232154)\n- ACPI: battery: Simplify battery hook locking (bsc#1232154)\n- ACPI: resource: Add Asus ExpertBook B2502CVA to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add Asus Vivobook X1704VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add another DMI match for the TongFang GMxXGxx (stable-fixes).\n- ACPICA: Fix memory leak if acpi_ps_get_next_field() fails (stable-fixes).\n- ACPICA: Fix memory leak if acpi_ps_get_next_namepath() fails (stable-fixes).\n- ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (stable-fixes).\n- ACPICA: iasl: handle empty connection_node (stable-fixes).\n- ALSA: asihpi: Fix potential OOB array access (stable-fixes).\n- ALSA: core: add isascii() check to card ID generator (stable-fixes).\n- ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() (git-fixes).\n- ALSA: hda/conexant - Fix audio routing for HP EliteOne 1000 G2 (stable-fixes).\n- ALSA: hda/conexant - Use cached pin control for Node 0x1d on HP EliteOne 1000 G2 (git-fixes).\n- ALSA: hda/conexant: Fix conflicting quirk for System76 Pangolin (git-fixes).\n- ALSA: hda/cs8409: Fix possible NULL dereference (git-fixes).\n- ALSA: hda/generic: Unconditionally prefer preferred_dacs pairs (git-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 a quirk for HP Pavilion 15z-ec200 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Huawei MateBook 13 KLV-WX9 (stable-fixes).\n- ALSA: hda/realtek: Fix the push button function for the ALC257 (git-fixes).\n- ALSA: hda/realtek: Update default depop procedure (git-fixes).\n- ALSA: hda: Fix kctl-\u003eid initialization (git-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ALSA: hdsp: Break infinite MIDI input flush loop (stable-fixes).\n- ALSA: line6: add hw monitor volume control to POD HD500X (stable-fixes).\n- ALSA: mixer_oss: Remove some incorrect kfree_const() usages (git-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C HEADSET (stable-fixes).\n- ALSA: usb-audio: Add input value sanity checks for standard types (stable-fixes).\n- ALSA: usb-audio: Add logitech Audio profile quirk (stable-fixes).\n- ALSA: usb-audio: Add native DSD support for Luxman D-08u (stable-fixes).\n- ALSA: usb-audio: Define macros for quirk table entries (stable-fixes).\n- ALSA: usb-audio: Replace complex quirk lines with macros (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: imx-card: Set card.owner to avoid a warning calltrace if SND=m (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: qcom: Fix NULL Dereference in asoc_qcom_lpass_cpu_platform_probe() (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-pcm: Do not zero TDM masks in __soc_pcm_open() (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- Bluetooth: Call iso_exit() on module unload (git-fixes).\n- Bluetooth: ISO: Fix multiple init when debugfs is disabled (git-fixes).\n- Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change (git-fixes).\n- Bluetooth: Remove debugfs directory on module init failure (git-fixes).\n- Bluetooth: bnep: fix wild-memory-access in proto_unregister (git-fixes).\n- Bluetooth: btmrvl: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Bluetooth: btusb: Fix regression with fake CSR controllers 0a12:0001 (git-fixes).\n- Bluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE (git-fixes).\n- HID: amd_sfh: Switch to device-managed dmam_alloc_coherent() (git-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: multitouch: Add support for Thinkpad X12 Gen 2 Kbd Portfolio (stable-fixes).\n- HID: plantronics: Workaround for an unexcepted opposite volume key (stable-fixes).\n- Input: adp5589-keys - fix NULL pointer dereference (git-fixes).\n- Input: adp5589-keys - fix adp5589_gpio_get_value() (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: goodix - use the new soc_intel_is_byt() helper (stable-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- KVM: Fix coalesced_mmio_has_room() to avoid premature userspace exit (git-fixes).\n- KVM: Fix lockdep false negative during host resume (git-fixes).\n- KVM: Grab a reference to KVM for VM and vCPU stats file descriptors (git-fixes).\n- KVM: Optimize kvm_make_vcpus_request_mask() a bit (git-fixes).\n- KVM: Pre-allocate cpumasks for kvm_make_all_cpus_request_except() (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: SVM: Disallow guest from changing userspace's MSR_AMD64_DE_CFG value (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: Unconditionally get a ref to /dev/kvm module when creating a VM (git-fixes).\n- KVM: Write the per-page 'segment' when clearing (part of) a guest page (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: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Preserve PSTATE.SS for the guest while single-step is enabled (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: mixed-width check should be skipped for uninitialized vCPUs (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: Check for non-NULL vCPU in vgic_v2_parse_attr() (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: eventfd: Fix false positive RCU usage warning (git-fixes).\n- KVM: fix memoryleak in kvm_init() (git-fixes).\n- KVM: s390: Change virtual to physical address access in diag 0x258 handler (git-fixes bsc#1232631).\n- KVM: s390: gaccess: Check if guest address is in memslot (git-fixes bsc#1232630).\n- KVM: x86/mmu: Fold rmap_recycle into rmap_add (git-fixes).\n- KVM: x86/mmu: Rename slot_handle_leaf to slot_handle_level_4k (git-fixes).\n- KVM: x86: Use a stable condition around all VT-d PI paths (git-fixes).\n- Makefile.compiler: replace cc-ifversion with compiler-specific macros (bsc#1230414 bsc#1229450).\n- NFS: Avoid unnecessary rescanning of the per-server delegation list (git-fixes).\n- NFSD: Fix NFSv4's PUTPUBFH operation (git-fixes).\n- NFSD: Mark filecache 'down' if init fails (git-fixes).\n- NFSv3: only use NFS timeout for MOUNT when protocols are compatible (bsc#1231016).\n- NFSv4: Fix clearing of layout segments in layoutreturn (git-fixes).\n- PCI: Add ACS quirk for Qualcomm SA8775P (stable-fixes).\n- PCI: Add function 0 DMA alias quirk for Glenfly Arise chip (stable-fixes).\n- PCI: Fix pci_enable_acs() support for the ACS quirks (bsc#1229019).\n- PCI: Mark Creative Labs EMU20k2 INTx masking as broken (stable-fixes).\n- RDMA/bnxt_re: Add a check for memory allocation (git-fixes)\n- RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages (git-fixes)\n- RDMA/bnxt_re: Fix incorrect AVID type in WQE structure (git-fixes)\n- RDMA/bnxt_re: Fix the GID table length (git-fixes)\n- RDMA/bnxt_re: Fix the max CQ WQEs for older adapters (git-fixes)\n- RDMA/bnxt_re: Fix the usage of control path spin locks (git-fixes)\n- RDMA/bnxt_re: Return more meaningful error (git-fixes)\n- RDMA/bnxt_re: synchronize the qp-handle table array (git-fixes)\n- RDMA/cxgb4: Dump vendor specific QP details (git-fixes)\n- RDMA/cxgb4: Fix RDMA_CM_EVENT_UNREACHABLE error for iWARP (git-fixes)\n- RDMA/hns: Remove unused abnormal interrupt of type RAS (git-fixes)\n- RDMA/irdma: Fix misspelling of 'accept*' (git-fixes)\n- RDMA/mad: Improve handling of timed out WRs of mad agent (git-fixes)\n- RDMA/mana_ib: use the correct page size for mapping user-mode doorbell page (git-fixes).\n- RDMA/mana_ib: use the correct page table index based on hardware page size (git-fixes).\n- RDMA/mlx5: Round max_rd_atomic/max_dest_rd_atomic up instead of down (git-fixes)\n- RDMA/rtrs-srv: Avoid null pointer deref during path establishment (git-fixes)\n- RDMA/srpt: Make slab cache names unique (git-fixes)\n- SUNRPC: Fix integer overflow in decode_rc_list() (git-fixes).\n- SUNRPC: Fixup gss_status tracepoint error output (git-fixes).\n- SUNRPC: clnt.c: Remove misleading comment (git-fixes).\n- USB: appledisplay: close race between probe and completion handler (stable-fixes).\n- USB: misc: cypress_cy7c63: check for short transfer (stable-fixes).\n- USB: misc: yurex: fix race between read and write (stable-fixes).\n- USB: serial: option: add Telit FN920C04 MBIM compositions (stable-fixes).\n- USB: serial: option: add support for Quectel EG916Q-GL (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- Use pahole -j1 option for reproducible builds (bsc#1230414 bsc#1229450).\n- add bug reference for a mana change (bsc#1229769).\n- add bug references to existing mana changes (bsc#1232033, bsc#1232034, bsc#1232036).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64: cputype: Add Neoverse-N3 definitions (git-fixes)\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: errata: Expand speculative SSBS workaround once more (git-fixes)\n- arm64: esr: Define ESR_ELx_EC_* constants as UL (git-fixes)\n- arm64: probes: Fix simulate_ldr*_literal() (git-fixes)\n- arm64: probes: Fix uprobes for big-endian kernels (git-fixes)\n- arm64: probes: Remove broken LDR (literal) uprobe support (git-fixes)\n- block: print symbolic error name instead of error code (bsc#1231872).\n- bpf, lsm: Add disabled BPF LSM hook list (git-fixes).\n- bpf, net: Fix a potential race in do_sock_getsockopt() (git-fixes).\n- bpf, verifier: Correct tail_call_reachable for bpf prog (git-fixes).\n- bpf, x64: Remove tail call detection (git-fixes).\n- bpf,perf: Fix perf_event_detach_bpf_prog error handling (git-fixes).\n- bpf: Add --skip_encoding_btf_inconsistent_proto, --btf_gen_optimized to pahole flags for v1.25 (bsc#1230414 bsc#1229450).\n- bpf: Allow helpers to accept pointers with a fixed size (git-fixes).\n- bpf: Check for helper calls in check_subprogs() (git-fixes).\n- bpf: Fix bpf_strtol and bpf_strtoul helpers for 32bit (git-fixes).\n- bpf: Fix helper writes to read-only maps (git-fixes).\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- bpf: Fix tailcall cases in test_bpf (git-fixes).\n- bpf: Improve check_raw_mode_ok test for MEM_UNINIT-tagged types (git-fixes).\n- bpf: Remove truncation test in bpf_strtol and bpf_strtoul helpers (git-fixes).\n- bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error (git-fixes).\n- bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos (git-fixes).\n- btf, scripts: Exclude Rust CUs with pahole (bsc#1230414 bsc#1229450).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- ceph: fix cap ref leak via netfs init_request (bsc#1231383).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- comedi: ni_routing: tools: Check when the file could not be opened (stable-fixes).\n- cpufreq/amd-pstate: Fix amd_pstate mode switch on shared memory systems (git-fixes).\n- crypto: hisilicon - Remove pci_aer_clear_nonfatal_status() call (bsc#1232075)\n- crypto: hisilicon/qm - re-enable communicate interrupt before notifying PF (bsc#1232075)\n- debugfs: fix automount d_fsdata usage (git-fixes).\n- dn_route: set rt neigh to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- drbd: Add NULL check for net_conf to prevent dereference in state validation (git-fixes).\n- drbd: Fix atomicity violation in drbd_uuid_set_bm() (git-fixes).\n- driver core: bus: Return -EIO instead of 0 when show/store invalid bus attribute (stable-fixes).\n- drm/amd/amdgpu: Fix double unlock in amdgpu_mes_add_ring (git-fixes).\n- drm/amd/display: Add null check for 'afb' in amdgpu_dm_plane_handle_cursor_update (v2) (stable-fixes).\n- drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Check link_res-\u003ehpo_dp_link_enc before using it (bsc#1231944)\n- drm/amd/display: Check null pointer before dereferencing se (stable-fixes).\n- drm/amd/display: Check null pointers before using dc-\u003eclk_mgr (stable-fixes).\n- drm/amd/display: Check stream before comparing them (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix index out of bounds in DCN30 color transformation (stable-fixes).\n- drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation (stable-fixes).\n- drm/amd/display: Fix index out of bounds in degamma hardware format translation (stable-fixes).\n- drm/amd/display: Fix system hang while resume with TBT monitor (stable-fixes).\n- drm/amd/display: Handle null 'stream_status' in 'planes_changed_for_existing_stream' (stable-fixes).\n- drm/amd/display: Initialize get_bytes_per_element's default to 1 (stable-fixes).\n- drm/amd/display: Round calculated vtotal (stable-fixes).\n- drm/amd/display: Validate backlight caps are sane (stable-fixes).\n- drm/amd/pm: ensure the fw_info is not null before using it (stable-fixes).\n- drm/amd: Guard against bad data for ATIF ACPI method (git-fixes).\n- drm/amdgpu: Replace one-element array with flexible-array member (stable-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/msm/dpu: do not always program merge_3d block (git-fixes).\n- drm/msm/dpu: make sure phys resources are properly initialized (git-fixes).\n- drm/msm/dsi: fix 32-bit signed integer extension in pclk_rate calculation (git-fixes).\n- drm/msm: Allocate memory for disp snapshot with kvzalloc() (git-fixes).\n- drm/msm: Avoid NULL dereference in msm_disp_state_print_regs() (git-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/radeon: Fix encoder-\u003epossible_clones (git-fixes).\n- drm/radeon: Replace one-element array with flexible-array member (stable-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: define gamma registers for RK3399 (stable-fixes).\n- drm/rockchip: support gamma control on RK3399 (stable-fixes).\n- drm/sched: Add locking to drm_sched_entity_modify_sched (git-fixes).\n- drm/v3d: Stop the active perfmon before being destroyed (git-fixes).\n- drm/vc4: Stop the active perfmon before being destroyed (git-fixes).\n- drm/vmwgfx: Handle surface check failure correctly (git-fixes).\n- drm: Consistently use struct drm_mode_rect for FB_DAMAGE_CLIPS (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption (stable-fixes).\n- erofs: avoid consecutive detection for Highmem memory (git-fixes).\n- erofs: avoid infinite loop in z_erofs_do_read_page() when reading beyond EOF (git-fixes).\n- erofs: fix pcluster use-after-free on UP platforms (git-fixes).\n- erofs: fix potential overflow calculating xattr_isize (git-fixes).\n- erofs: stop parsing non-compact HEAD index if clusterofs is invalid (git-fixes).\n- exportfs: use pr_debug for unreachable debug statements (git-fixes).\n- ext4: fix slab-use-after-free in ext4_split_extent_at() (bsc#1232201)\n- fat: fix uninitialized variable (git-fixes).\n- fbdev: pxafb: Fix possible use after free in pxafb_task() (stable-fixes).\n- fbdev: sisfb: Fix strbuf array overflow (stable-fixes).\n- fgraph: Change the name of cpuhp state to 'fgraph:online' (git-fixes).\n- fgraph: Fix missing unlock in register_ftrace_graph() (git-fixes).\n- fgraph: Use CPU hotplug mechanism to initialize idle shadow stacks (git-fixes).\n- filelock: fix potential use-after-free in posix_lock_inode (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- fs/namespace: fnic: Switch to use %ptTd (git-fixes).\n- fs/pipe: Fix lockdep false-positive in watchqueue pipe_write() (git-fixes).\n- fs: Fix file_set_fowner LSM hook inconsistencies (git-fixes).\n- gpio: aspeed: Add the flush write to ensure the write complete (git-fixes).\n- gpio: aspeed: Use devm_clk api to manage clock source (git-fixes).\n- gpio: davinci: fix lazy disable (git-fixes).\n- hid: intel-ish-hid: Fix uninitialized variable 'rv' in ish_fw_xfer_direct_dma (git-fixes).\n- hv_netvsc: Fix VF namespace also in synthetic NIC NETDEV_REGISTER event (git-fixes).\n- hwmon: (adm9240) Add missing dependency on REGMAP_I2C (git-fixes).\n- hwmon: (tmp513) Add missing dependency on REGMAP_I2C (git-fixes).\n- i2c: i801: Use a different adapter-name for IDF adapters (stable-fixes).\n- i2c: imx-lpi2c: return -EINVAL when i2c peripheral clk does not work (bsc#1227885).\n- i2c: imx-lpi2c: use bulk clk API (bsc#1227885).\n- i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume (git-fixes).\n- i2c: xiic: Fix RX IRQ busy check (stable-fixes).\n- i2c: xiic: Fix broken locking on tx_msg (stable-fixes).\n- i2c: xiic: Fix pm_runtime_set_suspended() with runtime pm enabled (git-fixes).\n- i2c: xiic: Switch from waitqueue to completion (stable-fixes).\n- i2c: xiic: Try re-initialization on bus busy timeout (git-fixes).\n- i2c: xiic: Use devm_clk_get_enabled() (stable-fixes).\n- i2c: xiic: improve error message when transfer fails to start (stable-fixes).\n- i2c: xiic: xiic_xfer(): Fix runtime PM leak on error path (git-fixes).\n- ice: Unbind the workqueue (bsc#1231344).\n- iio: dac: ad5770r: add missing select REGMAP_SPI in Kconfig (git-fixes).\n- iio: dac: ltc1660: add missing select REGMAP_SPI in Kconfig (git-fixes).\n- iio: dac: stm32-dac-core: add missing select REGMAP_MMIO in Kconfig (git-fixes).\n- iio: hid-sensors: Fix an error handling path in _hid_sensor_set_report_latency() (git-fixes).\n- iio: light: opt3001: add missing full-scale range value (git-fixes).\n- iio: light: veml6030: fix ALS sensor resolution (git-fixes).\n- iio: light: veml6030: fix IIO device retrieval from embedded device (git-fixes).\n- iio: proximity: mb1232: add missing select IIO_(TRIGGERED_)BUFFER in Kconfig (git-fixes).\n- iommu/vt-d: Always reserve a domain ID for identity setup (git-fixes).\n- ipv6: blackhole_netdev needs snmp6 counters (bsc#1216813).\n- ipv6: give an IPv6 dev to blackhole_netdev (bsc#1216813).\n- jfs: Fix sanity check in dbMount (git-fixes).\n- jfs: Fix uaf in dbFreeBits (git-fixes).\n- jfs: Fix uninit-value access of new_ea in ea_buffer (git-fixes).\n- jfs: UBSAN: shift-out-of-bounds in dbFindBits (git-fixes).\n- jfs: check if leafidx greater than num leaves per dmap tree (git-fixes).\n- kABI: bpf: enum bpf_{type_flag,arg_type} kABI workaround (git-fixes).\n- kABI: bpf: struct bpf_func_proto kABI workaround (git-fixes).\n- kab: fix after net: add more sanity check in virtio_net_hdr_to_skb() (git-fixes).\n- kabi fix of KVM: arm64: Preserve PSTATE.SS for the guest while single-step is enabled (git-fixes).\n- kabi: fix after KVM: arm64: mixed-width check should be skipped for uninitialized vCPUs (git-fixes).\n- kabi: fix after kvm: add guest_state_{enter,exit}_irqoff() (git-fixes).\n- kbuild, bpf: Use test-ge check for v1.25-only pahole (bsc#1230414 bsc#1229450).\n- kbuild,bpf: Add module-specific pahole flags for distilled base BTF (bsc#1230414 bsc#1229450).\n- kbuild,bpf: Switch to using --btf_features for pahole v1.26 and later (bsc#1230414 bsc#1229450).\n- kbuild: add test-{ge,gt,le,lt} macros (bsc#1230414 bsc#1229450).\n- kbuild: avoid too many execution of scripts/pahole-flags.sh (bsc#1230414 bsc#1229450).\n- kbuild: bpf: Tell pahole to DECL_TAG kfuncs (bsc#1230414 bsc#1229450).\n- kvm/arm64: rework guest entry logic (git-fixes).\n- kvm: Add support for arch compat vm ioctls (git-fixes).\n- kvm: add guest_state_{enter,exit}_irqoff() (git-fixes).\n- media: videobuf2-core: clear memory related fields in __vb2_plane_dmabuf_put() (stable-fixes).\n- module: abort module loading when sysfs setup suffer errors (git-fixes).\n- nbd: fix race between timeout and normal completion (bsc#1230918).\n- net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX (bsc#1226797)\n- net: add more sanity check in virtio_net_hdr_to_skb() (git-fixes).\n- net: socket: suppress unused warning (git-fixes).\n- net: test for not too small csum_start in virtio_net_hdr_to_skb() (git-fixes).\n- net: usb: usbnet: fix name regression (git-fixes).\n- netdevsim: use cond_resched() in nsim_dev_trap_report_work() (git-fixes).\n- nfs: fix memory leak in error path of nfs4_do_reclaim (git-fixes).\n- nfsd: call cache_put if xdr_reserve_space returns NULL (git-fixes).\n- nfsd: fix delegation_blocked() to block correctly for at least 30 seconds (git-fixes).\n- nfsd: fix refcount leak when file is unhashed after being found (git-fixes).\n- nfsd: map the EBADMSG to nfserr_io to avoid warning (git-fixes).\n- nfsd: remove unneeded EEXIST error check in nfsd_do_file_acquire (git-fixes).\n- nfsd: return -EINVAL when namelen is 0 (git-fixes).\n- nilfs2: fix kernel bug due to missing clearing of buffer delay flag (git-fixes).\n- nouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error (git-fixes).\n- ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() (git-fixes).\n- ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition (stable-fixes).\n- nvme-multipath: system fails to create generic nvme device (git-fixes).\n- nvme-pci: qdepth 1 quirk (git-fixes).\n- nvmet-auth: assign dh_key to NULL after kfree_sensitive (git-fixes).\n- ocfs2: fix the la space leak when unmounting an ocfs2 volume (git-fixes).\n- ocfs2: fix uninit-value in ocfs2_get_block() (git-fixes).\n- ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow (git-fixes).\n- parport: Proper fix for array out-of-bounds access (git-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: touchscreen_dmi: add nanote-next quirk (stable-fixes).\n- power: reset: brcmstb: Do not go into infinite loop if reset fails (stable-fixes).\n- s390/sclp_vt220: Convert newlines to CRLF instead of LFCR (git-fixes bsc#1232632).\n- scsi: NCR5380: Check for phase match during PDMA fixup (git-fixes).\n- scsi: aacraid: Rearrange order of struct aac_srb_unit (git-fixes).\n- scsi: core: Fix the return value of scsi_logical_block_count() (git-fixes).\n- scsi: core: Handle devices which return an unusually large VPD page count (git-fixes).\n- scsi: core: alua: I/O errors for ALUA state transitions (git-fixes).\n- scsi: elx: libefc: Fix potential use after free in efc_nport_vport_del() (git-fixes).\n- scsi: hpsa: Fix allocation size for Scsi_Host private data (git-fixes).\n- scsi: libsas: Fix exp-attached device scan after probe failure scanned in again after probe failed (git-fixes).\n- scsi: libsas: Fix the failure of adding phy with zero-address to port (git-fixes).\n- scsi: lpfc: Add ELS_RSP cmd to the list of WQEs to flush in lpfc_els_flush_cmd() (bsc#1232757).\n- scsi: lpfc: Ensure DA_ID handling completion before deleting an NPIV instance (bsc#1232757).\n- scsi: lpfc: Fix kref imbalance on fabric ndlps from dev_loss_tmo handler (bsc#1232757).\n- scsi: lpfc: Remove trailing space after \\n newline (bsc#1232757).\n- scsi: lpfc: Restrict support for 32 byte CDBs to specific HBAs (git-fixes).\n- scsi: lpfc: Revise TRACE_EVENT log flag severities from KERN_ERR to KERN_WARNING (bsc#1232757).\n- scsi: lpfc: Support loopback tests with VMID enabled (bsc#1232757).\n- scsi: lpfc: Update lpfc version to 14.4.0.5 (bsc#1232757).\n- scsi: lpfc: Update phba link state conditional before sending CMF_SYNC_WQE (bsc#1232757).\n- scsi: mac_scsi: Disallow bus errors during PDMA send (git-fixes).\n- scsi: mac_scsi: Refactor polling loop (git-fixes).\n- scsi: mac_scsi: Revise printk(KERN_DEBUG ...) messages (git-fixes).\n- scsi: mpi3mr: Avoid IOMMU page faults on REPORT ZONES (git-fixes).\n- scsi: mpi3mr: Fix ATA NCQ priority support (git-fixes).\n- scsi: mpt3sas: Avoid IOMMU page faults on REPORT ZONES (git-fixes).\n- scsi: qedf: Set qed_slowpath_params to zero before use (git-fixes).\n- scsi: smartpqi: correct stream detection (git-fixes).\n- scsi: smartpqi: revert propagate-the-multipath-failure-to-SML-quickly (git-fixes).\n- scsi: spi: Fix sshdr use (git-fixes).\n- scsi: wd33c93: Do not use stale scsi_pointer value (git-fixes).\n- selftests/bpf: Add a test case to write mtu result into .rodata (git-fixes).\n- selftests/bpf: Add a test case to write strtol result into .rodata (git-fixes).\n- selftests/bpf: Fix ARG_PTR_TO_LONG {half-,}uninitialized test (git-fixes).\n- selftests/bpf: Rename ARG_PTR_TO_LONG test description (git-fixes).\n- selftests/bpf: test for malformed BPF_CORE_TYPE_ID_LOCAL relocation (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: lpspi: Silence error message upon deferred probe (stable-fixes).\n- spi: lpspi: Simplify some error message (git-fixes).\n- spi: lpspi: release requested DMA channels (stable-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: s3c64xx: fix timeout counters in flush_fifo (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spi-imx: Fix pm_runtime_set_suspended() with runtime pm enabled (git-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- static_call: Do not make __static_call_return0 static (git-fixes).\n- tracing/hwlat: Fix a race during cpuhp processing (git-fixes).\n- tracing/uprobes: Use trace_event_buffer_reserve() helper (git-fixes).\n- tracing: Consider the NULL character when validating the event length (git-fixes).\n- uprobe: avoid out-of-bounds memory access of fetching args (git-fixes).\n- uprobes: encapsulate preparation of uprobe args buffer (git-fixes).\n- usb: chipidea: udc: enable suspend interrupt after usb reset (stable-fixes).\n- usb: dwc2: Adjust the timing of USB Driver Interrupt Registration in the Crashkernel Scenario (stable-fixes).\n- usb: dwc3: core: Stop processing of pending events if controller is halted (git-fixes).\n- usb: gadget: core: force synchronous registration (git-fixes).\n- usb: storage: ignore bogus device raised by JieLi BR21 USB sound chip (stable-fixes).\n- usb: typec: altmode should keep reference to parent (git-fixes).\n- usb: xhci: Fix problem with xhci resume from suspend (stable-fixes).\n- usb: yurex: Fix inconsistent locking bug in yurex_read() (git-fixes).\n- usb: yurex: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (stable-fixes).\n- vhost/scsi: null-ptr-dereference in vhost_scsi_get_req() (git-fixes).\n- vhost_vdpa: assign irq bypass producer token correctly (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_console: fix misc probe bugs (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- vmxnet3: add command to allow disabling of offloads (bsc#1226498).\n- vmxnet3: add latency measurement support in vmxnet3 (bsc#1226498).\n- vmxnet3: prepare for version 9 changes (bsc#1226498).\n- vmxnet3: update to version 9 (bsc#1226498).\n- vsock/virtio: fix packet delivery to tap device (git-fixes).\n- wifi: ath11k: fix array out-of-bound access in SoC stats (stable-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: ath9k: fix parameter check in ath9k_init_debug() (stable-fixes).\n- wifi: ath9k: fix possible integer overflow in ath9k_get_et_stats() (stable-fixes).\n- wifi: ath9k_htc: Use __skb_set_length() for resetting urb before resubmit (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() (stable-fixes).\n- wifi: rtw88: select WANT_DEV_COREDUMP (stable-fixes).\n- x86/bugs: Do not use UNTRAIN_RET with IBPB on entry (git-fixes).\n- x86/bugs: Skip RSB fill at VMEXIT (git-fixes).\n- x86/cpufeatures: Add a IBPB_NO_RET BUG flag (git-fixes).\n- x86/cpufeatures: Define X86_FEATURE_AMD_IBPB_RET (git-fixes).\n- x86/entry: Have entry_ibpb() invalidate return predictions (git-fixes).\n- x86/hyperv: Set X86_FEATURE_TSC_KNOWN_FREQ when Hyper-V provides frequency (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1230405).\n- xfrm: set dst dev to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- xhci: Fix incorrect stream context type macro (git-fixes).\n- xhci: Mitigate failed set dequeue pointer commands (git-fixes).\n","status":"published","published":"2024-11-13T10:12:30Z","modified":"2026-02-04T02:17:08.867217Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3985-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-48879: efi: fix NULL-deref in init error path (bsc#1229556).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48957: dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove() (bsc#1231973).\n- CVE-2022-48958: ethernet: aeroflex: fix potential skb leak in greth_init_rings() (bsc#1231889).\n- CVE-2022-48959: net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions() (bsc#1231976).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48966: net: mvneta: Fix an out of bounds check (bsc#1232191).\n- CVE-2022-48980: net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing() (bsc#1232233).\n- CVE-2022-48991: mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma (bsc#1232070).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2022-49017: tipc: re-fetch skb cb after tipc_msg_validate (bsc#1232004).\n- CVE-2022-49020: net/9p: Fix a potential socket leak in p9_socket_open (bsc#1232175).\n- CVE-2024-36244: net/sched: taprio: extend minimum interval restriction to entire cycle too (bsc#1226797).\n- CVE-2024-36957: octeontx2-af: avoid off-by-one read from userspace (bsc#1225762).\n- CVE-2024-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (bsc#1227437).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-42226: Prevent potential failure in handle_tx_event() for Transfer events without TRB (bsc#1228709).\n- CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race (bsc#1229005).\n- CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc() (bsc#1229837).\n- CVE-2024-44958: sched/smt: Fix unbalance sched_smt_present dec/inc (bsc#1230179).\n- CVE-2024-45016: netem: fix return value if duplicate enqueue fails (bsc#1230429).\n- CVE-2024-45025: fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE (bsc#1230456).\n- CVE-2024-46678: bonding: change ipsec_lock from spin lock to mutex (bsc#1230550).\n- CVE-2024-46716: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (bsc#1230715).\n- CVE-2024-46754: bpf: Remove tst_run from lwt_seg6local_prog_ops (bsc#1230801).\n- CVE-2024-46770: ice: Add netif_device_attach/detach into PF reset flow (bsc#1230763).\n- CVE-2024-46775: drm/amd/display: Validate function returns (bsc#1230774).\n- CVE-2024-46777: udf: Avoid excessive partition lengths (bsc#1230773).\n- CVE-2024-46809: drm/amd/display: Check BIOS images before it is used (bsc#1231148).\n- CVE-2024-46811: drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (bsc#1231179).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46814: drm/amd/display: Check msg_id before processing transcation (bsc#1231193).\n- CVE-2024-46815: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets (bsc#1231195).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46817: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (bsc#1231200).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46826: ELF: fix kernel.randomize_va_space double read (bsc#1231115).\n- CVE-2024-46828: uprobes: fix kernel info leak via '[uprobes]' vma (bsc#1231114).\n- CVE-2024-46834: ethtool: fail closed if we can't get max channel used in indirection tables (bsc#1231096).\n- CVE-2024-46840: btrfs: clean up our handling of refs == 0 in snapshot delete (bsc#1231105).\n- CVE-2024-46841: btrfs: do not BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (bsc#1231094).\n- CVE-2024-46848: perf/x86/intel: Limit the period on Haswell (bsc#1231072).\n- CVE-2024-46849: ASoC: meson: axg-card: fix 'use-after-free' (bsc#1231073).\n- CVE-2024-46854: net: dpaa: Pad packets to ETH_ZLEN (bsc#1231084).\n- CVE-2024-46855: netfilter: nft_socket: fix sk refcount leaks (bsc#1231085).\n- CVE-2024-46857: net/mlx5: Fix bridge mode operations when there are no VFs (bsc#1231087).\n- CVE-2024-47660: fsnotify: clear PARENT_WATCHED flags lazily (bsc#1231439).\n- CVE-2024-47661: drm/amd/display: Avoid overflow from uint32_t to uint8_t (bsc#1231496).\n- CVE-2024-47664: spi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware (bsc#1231442).\n- CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (bsc#1231502).\n- CVE-2024-47672: wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (bsc#1231540).\n- CVE-2024-47673: wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (bsc#1231539).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47685: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() (bsc#1231998).\n- CVE-2024-47692: nfsd: return -EINVAL when namelen is 0 (bsc#1231857).\n- CVE-2024-47704: drm/amd/display: Check link_res-\u003ehpo_dp_link_enc before using it (bsc#1231944).\n- CVE-2024-47705: block: fix potential invalid pointer dereference in blk_add_partition (bsc#1231872).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47707: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (bsc#1231935).\n- CVE-2024-47710: sock_map: Add a cond_resched() in sock_hash_free() (bsc#1232049).\n- CVE-2024-47720: drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (bsc#1232043).\n- CVE-2024-47727: x86/tdx: Fix 'in-kernel MMIO' check (bsc#1232116).\n- CVE-2024-47730: crypto: hisilicon/qm - inject error before stopping queue (bsc#1232075).\n- CVE-2024-47738: wifi: mac80211: do not use rate mask for offchannel TX either (bsc#1232114).\n- CVE-2024-47739: padata: use integer wrap around to prevent deadlock on seq_nr overflow (bsc#1232124).\n- CVE-2024-47745: mm: split critical region in remap_file_pages() and invoke LSMs in between (bsc#1232135).\n- CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition (bsc#1232145).\n- CVE-2024-47748: vhost_vdpa: assign irq bypass producer token correctly (bsc#1232174).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49866: tracing/timerlat: Fix a race during cpuhp processing (bsc#1232259).\n- CVE-2024-49881: ext4: update orig_path in ext4_find_extent() (bsc#1232201).\n- CVE-2024-49882: ext4: fix double brelse() the buffer of the extents path (bsc#1232200).\n- CVE-2024-49883: ext4: aovid use-after-free in ext4_ext_insert_extent() (bsc#1232199).\n- CVE-2024-49886: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug (bsc#1232196).\n- CVE-2024-49890: drm/amd/pm: ensure the fw_info is not null before using it (bsc#1232217).\n- CVE-2024-49892: drm/amd/display: Initialize get_bytes_per_element's default to 1 (bsc#1232220).\n- CVE-2024-49894: drm/amd/display: Fix index out of bounds in degamma hardware format translation (bsc#1232354).\n- CVE-2024-49896: drm/amd/display: Check stream before comparing them (bsc#1232221).\n- CVE-2024-49897: drm/amd/display: Check phantom_stream before it is used (bsc#1232355).\n- CVE-2024-49899: drm/amd/display: Initialize denominators' default to 1 (bsc#1232358).\n- CVE-2024-49901: drm/msm/adreno: Assign msm_gpu-\u003epdev earlier to avoid nullptrs (bsc#1232305).\n- CVE-2024-49906: drm/amd/display: Check null pointer before try to access it (bsc#1232332).\n- CVE-2024-49909: drm/amd/display: Add NULL check for function pointer in dcn32_set_output_transfer_func (bsc#1232337).\n- CVE-2024-49911: drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func (bsc#1232366).\n- CVE-2024-49914: drm/amd/display: Add null check for pipe_ctx-\u003eplane_state in (bsc#1232369).\n- CVE-2024-49917: drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u003efuncs in dcn30_init_hw (bsc#1231965).\n- CVE-2024-49918: drm/amd/display: Add null check for head_pipe in dcn32_acquire_idle_pipe_for_head_pipe_in_layer (bsc#1231967).\n- CVE-2024-49919: drm/amd/display: Add null check for head_pipe in dcn201_acquire_free_pipe_for_layer (bsc#1231968).\n- CVE-2024-49920: drm/amd/display: Check null pointers before multiple uses (bsc#1232313).\n- CVE-2024-49922: drm/amd/display: Check null pointers before using them (bsc#1232374).\n- CVE-2024-49923: drm/amd/display: Pass non-null to dcn20_validate_apply_pipe_split_flags (bsc#1232361).\n- CVE-2024-49929: wifi: iwlwifi: mvm: avoid NULL pointer dereference (bsc#1232253).\n- CVE-2024-49930: wifi: ath11k: fix array out-of-bound access in SoC stats (bsc#1232260).\n- CVE-2024-49933: blk_iocost: fix more out of bound shifts (bsc#1232368).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49939: wifi: rtw89: avoid to add interface to list twice when SER (bsc#1232381).\n- CVE-2024-49946: ppp: do not assume bh is held in ppp_channel_bridge_input() (bsc#1232164).\n- CVE-2024-49949: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (bsc#1232160).\n- CVE-2024-49954: static_call: Replace pointless WARN_ON() in static_call_module_notify() (bsc#1232155).\n- CVE-2024-49955: ACPI: battery: Fix possible crash when unregistering a battery hook (bsc#1232154).\n- CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree (bsc#1232151).\n- CVE-2024-49959: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error (bsc#1232149).\n- CVE-2024-49960: ext4: fix timer use-after-free on failed mount (bsc#1232395).\n- CVE-2024-49962: ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (bsc#1232314).\n- CVE-2024-49967: ext4: no need to continue when the number of entries is 1 (bsc#1232140).\n- CVE-2024-49969: drm/amd/display: Fix index out of bounds in DCN30 color transformation (bsc#1232519).\n- CVE-2024-49973: r8169: add tally counter fields added with RTL8125 (bsc#1232105).\n- CVE-2024-49974: NFSD: Force all NFSv4.2 COPY requests to be synchronous (bsc#1232383).\n- CVE-2024-49975: uprobes: fix kernel info leak via '[uprobes]' vma (bsc#1232104).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49993: iommu/vt-d: Fix potential lockup if qi_submit_sync called with 0 count (bsc#1232316).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-50000: net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() (bsc#1232085).\n- CVE-2024-50001: net/mlx5: Fix error path in multi-packet WQE transmit (bsc#1232084).\n- CVE-2024-50002: static_call: Handle module init failure correctly in static_call_del_module() (bsc#1232083).\n- CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate() (bsc#1232442).\n- CVE-2024-50014: ext4: fix access to uninitialised lock in fc replay path (bsc#1232446).\n- CVE-2024-50019: kthread: unpark only parked kthread (bsc#1231990).\n- CVE-2024-50024: net: Fix an unsafe loop on the list (bsc#1231954).\n- CVE-2024-50028: thermal: core: Reference count the zone in thermal_zone_get_by_id() (bsc#1231950).\n- CVE-2024-50033: slip: make slhc_remember() more robust against malicious packets (bsc#1231914).\n- CVE-2024-50035: ppp: fix ppp_async_encode() illegal access (bsc#1232392).\n- CVE-2024-50041: i40e: Fix macvlan leak by synchronizing access to mac_filter_hash (bsc#1231907).\n- CVE-2024-50045: netfilter: br_netfilter: fix panic with metadata_dst skb (bsc#1231903).\n- CVE-2024-50046: kabi fix for NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() (bsc#1231902).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n- CVE-2024-50048: fbcon: Fix a NULL pointer dereference issue in fbcon_putcs (bsc#1232310).\n- CVE-2024-50055: driver core: bus: Fix double free in driver API bus_register() (bsc#1232329).\n- CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too (bsc#1232285).\n- CVE-2024-50059: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition (bsc#1232345).\n- CVE-2024-50061: i3c: master: cdns: Fix use after free vulnerability in cdns_i3c_master Driver Due to Race Condition (bsc#1232263).\n- CVE-2024-50063: kABI: bpf: struct bpf_map kABI workaround (bsc#1232435).\n- CVE-2024-50081: blk-mq: setup queue -\u003etag_set before initializing hctx (bsc#1232501).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: Do not release locks during operation region accesses (stable-fixes).\n- ACPI: PAD: fix crash in exit_round_robin() (stable-fixes).\n- ACPI: PRM: Clean up guid type in struct prm_handler_info (git-fixes).\n- ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context (git-fixes).\n- ACPI: battery: Call power_supply_changed() when adding hooks (bsc#1232154)\n- ACPI: battery: Simplify battery hook locking (bsc#1232154)\n- ACPI: resource: Add Asus ExpertBook B2502CVA to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add Asus Vivobook X1704VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add another DMI match for the TongFang GMxXGxx (stable-fixes).\n- ACPICA: Fix memory leak if acpi_ps_get_next_field() fails (stable-fixes).\n- ACPICA: Fix memory leak if acpi_ps_get_next_namepath() fails (stable-fixes).\n- ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (stable-fixes).\n- ACPICA: iasl: handle empty connection_node (stable-fixes).\n- ALSA: asihpi: Fix potential OOB array access (stable-fixes).\n- ALSA: core: add isascii() check to card ID generator (stable-fixes).\n- ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() (git-fixes).\n- ALSA: hda/conexant - Fix audio routing for HP EliteOne 1000 G2 (stable-fixes).\n- ALSA: hda/conexant - Use cached pin control for Node 0x1d on HP EliteOne 1000 G2 (git-fixes).\n- ALSA: hda/conexant: Fix conflicting quirk for System76 Pangolin (git-fixes).\n- ALSA: hda/cs8409: Fix possible NULL dereference (git-fixes).\n- ALSA: hda/generic: Unconditionally prefer preferred_dacs pairs (git-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 a quirk for HP Pavilion 15z-ec200 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Huawei MateBook 13 KLV-WX9 (stable-fixes).\n- ALSA: hda/realtek: Fix the push button function for the ALC257 (git-fixes).\n- ALSA: hda/realtek: Update default depop procedure (git-fixes).\n- ALSA: hda: Fix kctl-\u003eid initialization (git-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ALSA: hdsp: Break infinite MIDI input flush loop (stable-fixes).\n- ALSA: line6: add hw monitor volume control to POD HD500X (stable-fixes).\n- ALSA: mixer_oss: Remove some incorrect kfree_const() usages (git-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C HEADSET (stable-fixes).\n- ALSA: usb-audio: Add input value sanity checks for standard types (stable-fixes).\n- ALSA: usb-audio: Add logitech Audio profile quirk (stable-fixes).\n- ALSA: usb-audio: Add native DSD support for Luxman D-08u (stable-fixes).\n- ALSA: usb-audio: Define macros for quirk table entries (stable-fixes).\n- ALSA: usb-audio: Replace complex quirk lines with macros (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: imx-card: Set card.owner to avoid a warning calltrace if SND=m (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: qcom: Fix NULL Dereference in asoc_qcom_lpass_cpu_platform_probe() (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-pcm: Do not zero TDM masks in __soc_pcm_open() (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- Bluetooth: Call iso_exit() on module unload (git-fixes).\n- Bluetooth: ISO: Fix multiple init when debugfs is disabled (git-fixes).\n- Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change (git-fixes).\n- Bluetooth: Remove debugfs directory on module init failure (git-fixes).\n- Bluetooth: bnep: fix wild-memory-access in proto_unregister (git-fixes).\n- Bluetooth: btmrvl: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Bluetooth: btusb: Fix regression with fake CSR controllers 0a12:0001 (git-fixes).\n- Bluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE (git-fixes).\n- Drop HD-audio conexant patch that caused a regression on Thinkpad (bsc#1228269)\n- Drop USB dwc2 patch that caused a regression on RPi3 (bsc#1232342)\n- HID: amd_sfh: Switch to device-managed dmam_alloc_coherent() (git-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: multitouch: Add support for Thinkpad X12 Gen 2 Kbd Portfolio (stable-fixes).\n- HID: plantronics: Workaround for an unexcepted opposite volume key (stable-fixes).\n- Input: adp5589-keys - fix NULL pointer dereference (git-fixes).\n- Input: adp5589-keys - fix adp5589_gpio_get_value() (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: goodix - use the new soc_intel_is_byt() helper (stable-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- KVM: Fix coalesced_mmio_has_room() to avoid premature userspace exit (git-fixes).\n- KVM: Fix lockdep false negative during host resume (git-fixes).\n- KVM: Grab a reference to KVM for VM and vCPU stats file descriptors (git-fixes).\n- KVM: Optimize kvm_make_vcpus_request_mask() a bit (git-fixes).\n- KVM: Pre-allocate cpumasks for kvm_make_all_cpus_request_except() (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: SVM: Disallow guest from changing userspace's MSR_AMD64_DE_CFG value (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: Unconditionally get a ref to /dev/kvm module when creating a VM (git-fixes).\n- KVM: Write the per-page 'segment' when clearing (part of) a guest page (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: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Preserve PSTATE.SS for the guest while single-step is enabled (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: mixed-width check should be skipped for uninitialized vCPUs (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: Check for non-NULL vCPU in vgic_v2_parse_attr() (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: eventfd: Fix false positive RCU usage warning (git-fixes).\n- KVM: fix memoryleak in kvm_init() (git-fixes).\n- KVM: s390: Change virtual to physical address access in diag 0x258 handler (git-fixes bsc#1232631).\n- KVM: s390: Fix SORTL and DFLTCC instruction format error in __insn32_query (git-fixes bsc#1231277).\n- KVM: s390: gaccess: Check if guest address is in memslot (git-fixes bsc#1232630).\n- KVM: x86/mmu: Fold rmap_recycle into rmap_add (git-fixes).\n- KVM: x86/mmu: Rename slot_handle_leaf to slot_handle_level_4k (git-fixes).\n- KVM: x86: Use a stable condition around all VT-d PI paths (git-fixes).\n- Makefile.compiler: replace cc-ifversion with compiler-specific macros (bsc#1230414 bsc#1229450).\n- NFS: Avoid unnecessary rescanning of the per-server delegation list (git-fixes).\n- NFSD: Fix NFSv4's PUTPUBFH operation (git-fixes).\n- NFSD: Mark filecache 'down' if init fails (git-fixes).\n- NFSv3: only use NFS timeout for MOUNT when protocols are compatible (bsc#1231016).\n- NFSv4: Fix clearing of layout segments in layoutreturn (git-fixes).\n- PCI: Add ACS quirk for Qualcomm SA8775P (stable-fixes).\n- PCI: Add function 0 DMA alias quirk for Glenfly Arise chip (stable-fixes).\n- PCI: Fix pci_enable_acs() support for the ACS quirks (bsc#1229019).\n- PCI: Mark Creative Labs EMU20k2 INTx masking as broken (stable-fixes).\n- RDMA/bnxt_re: Add a check for memory allocation (git-fixes)\n- RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages (git-fixes)\n- RDMA/bnxt_re: Fix incorrect AVID type in WQE structure (git-fixes)\n- RDMA/bnxt_re: Fix the GID table length (git-fixes)\n- RDMA/bnxt_re: Fix the max CQ WQEs for older adapters (git-fixes)\n- RDMA/bnxt_re: Fix the usage of control path spin locks (git-fixes)\n- RDMA/bnxt_re: Return more meaningful error (git-fixes)\n- RDMA/bnxt_re: synchronize the qp-handle table array (git-fixes)\n- RDMA/cxgb4: Dump vendor specific QP details (git-fixes)\n- RDMA/cxgb4: Fix RDMA_CM_EVENT_UNREACHABLE error for iWARP (git-fixes)\n- RDMA/hns: Remove unused abnormal interrupt of type RAS (git-fixes)\n- RDMA/irdma: Fix misspelling of 'accept*' (git-fixes)\n- RDMA/mad: Improve handling of timed out WRs of mad agent (git-fixes)\n- RDMA/mana_ib: use the correct page size for mapping user-mode doorbell page (git-fixes).\n- RDMA/mana_ib: use the correct page table index based on hardware page size (git-fixes).\n- RDMA/mlx5: Round max_rd_atomic/max_dest_rd_atomic up instead of down (git-fixes)\n- RDMA/rtrs-srv: Avoid null pointer deref during path establishment (git-fixes)\n- RDMA/srpt: Make slab cache names unique (git-fixes)\n- SUNRPC: Fix integer overflow in decode_rc_list() (git-fixes).\n- SUNRPC: Fixup gss_status tracepoint error output (git-fixes).\n- SUNRPC: clnt.c: Remove misleading comment (git-fixes).\n- USB: appledisplay: close race between probe and completion handler (stable-fixes).\n- USB: misc: cypress_cy7c63: check for short transfer (stable-fixes).\n- USB: misc: yurex: fix race between read and write (stable-fixes).\n- USB: serial: option: add Telit FN920C04 MBIM compositions (stable-fixes).\n- USB: serial: option: add support for Quectel EG916Q-GL (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- Use pahole -j1 option for reproducible builds (bsc#1230414 bsc#1229450).\n- add bug reference for a mana change (bsc#1229769).\n- add bug references to existing mana changes (bsc#1232033, bsc#1232034, bsc#1232036).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- arm64: cputype: Add Neoverse-N3 definitions (git-fixes)\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: errata: Expand speculative SSBS workaround once more (git-fixes)\n- arm64: esr: Define ESR_ELx_EC_* constants as UL (git-fixes)\n- arm64: probes: Fix simulate_ldr*_literal() (git-fixes)\n- arm64: probes: Fix uprobes for big-endian kernels (git-fixes)\n- arm64: probes: Remove broken LDR (literal) uprobe support (git-fixes)\n- block: print symbolic error name instead of error code (bsc#1231872).\n- bpf, lsm: Add disabled BPF LSM hook list (git-fixes).\n- bpf, net: Fix a potential race in do_sock_getsockopt() (git-fixes).\n- bpf, verifier: Correct tail_call_reachable for bpf prog (git-fixes).\n- bpf, x64: Remove tail call detection (git-fixes).\n- bpf,perf: Fix perf_event_detach_bpf_prog error handling (git-fixes).\n- bpf: Add --skip_encoding_btf_inconsistent_proto, --btf_gen_optimized to pahole flags for v1.25 (bsc#1230414 bsc#1229450).\n- bpf: Allow helpers to accept pointers with a fixed size (git-fixes).\n- bpf: Check for helper calls in check_subprogs() (git-fixes).\n- bpf: Fix bpf_strtol and bpf_strtoul helpers for 32bit (git-fixes).\n- bpf: Fix helper writes to read-only maps (git-fixes).\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- bpf: Fix tailcall cases in test_bpf (git-fixes).\n- bpf: Improve check_raw_mode_ok test for MEM_UNINIT-tagged types (git-fixes).\n- bpf: Remove truncation test in bpf_strtol and bpf_strtoul helpers (git-fixes).\n- bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error (git-fixes).\n- bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos (git-fixes).\n- btf, scripts: Exclude Rust CUs with pahole (bsc#1230414 bsc#1229450).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- ceph: fix cap ref leak via netfs init_request (bsc#1231383).\n- char: tpm: Fix possible memory leak in tpm_bios_measurements_open() (git-fixes).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- comedi: ni_routing: tools: Check when the file could not be opened (stable-fixes).\n- cpufreq/amd-pstate: Fix amd_pstate mode switch on shared memory systems (git-fixes).\n- crypto: hisilicon - Remove pci_aer_clear_nonfatal_status() call (bsc#1232075)\n- crypto: hisilicon/qm - re-enable communicate interrupt before notifying PF (bsc#1232075)\n- debugfs: fix automount d_fsdata usage (git-fixes).\n- dn_route: set rt neigh to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- drbd: Add NULL check for net_conf to prevent dereference in state validation (git-fixes).\n- drbd: Fix atomicity violation in drbd_uuid_set_bm() (git-fixes).\n- driver core: bus: Return -EIO instead of 0 when show/store invalid bus attribute (stable-fixes).\n- drm/amd/amdgpu: Fix double unlock in amdgpu_mes_add_ring (git-fixes).\n- drm/amd/display: Add null check for 'afb' in amdgpu_dm_plane_handle_cursor_update (v2) (stable-fixes).\n- drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Check link_res-\u003ehpo_dp_link_enc before using it (bsc#1231944)\n- drm/amd/display: Check null pointer before dereferencing se (stable-fixes).\n- drm/amd/display: Check null pointers before using dc-\u003eclk_mgr (stable-fixes).\n- drm/amd/display: Check stream before comparing them (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix index out of bounds in DCN30 color transformation (stable-fixes).\n- drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation (stable-fixes).\n- drm/amd/display: Fix index out of bounds in degamma hardware format translation (stable-fixes).\n- drm/amd/display: Fix system hang while resume with TBT monitor (stable-fixes).\n- drm/amd/display: Handle null 'stream_status' in 'planes_changed_for_existing_stream' (stable-fixes).\n- drm/amd/display: Initialize get_bytes_per_element's default to 1 (stable-fixes).\n- drm/amd/display: Round calculated vtotal (stable-fixes).\n- drm/amd/display: Validate backlight caps are sane (stable-fixes).\n- drm/amd/pm: ensure the fw_info is not null before using it (stable-fixes).\n- drm/amd: Guard against bad data for ATIF ACPI method (git-fixes).\n- drm/amdgpu: Replace one-element array with flexible-array member (stable-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/msm/dpu: do not always program merge_3d block (git-fixes).\n- drm/msm/dpu: make sure phys resources are properly initialized (git-fixes).\n- drm/msm/dsi: fix 32-bit signed integer extension in pclk_rate calculation (git-fixes).\n- drm/msm: Allocate memory for disp snapshot with kvzalloc() (git-fixes).\n- drm/msm: Avoid NULL dereference in msm_disp_state_print_regs() (git-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/radeon: Fix encoder-\u003epossible_clones (git-fixes).\n- drm/radeon: Replace one-element array with flexible-array member (stable-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: define gamma registers for RK3399 (stable-fixes).\n- drm/rockchip: support gamma control on RK3399 (stable-fixes).\n- drm/sched: Add locking to drm_sched_entity_modify_sched (git-fixes).\n- drm/v3d: Stop the active perfmon before being destroyed (git-fixes).\n- drm/vc4: Stop the active perfmon before being destroyed (git-fixes).\n- drm/vmwgfx: Handle surface check failure correctly (git-fixes).\n- drm: Consistently use struct drm_mode_rect for FB_DAMAGE_CLIPS (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption (stable-fixes).\n- erofs: avoid consecutive detection for Highmem memory (git-fixes).\n- erofs: avoid infinite loop in z_erofs_do_read_page() when reading beyond EOF (git-fixes).\n- erofs: fix pcluster use-after-free on UP platforms (git-fixes).\n- erofs: fix potential overflow calculating xattr_isize (git-fixes).\n- erofs: stop parsing non-compact HEAD index if clusterofs is invalid (git-fixes).\n- exportfs: use pr_debug for unreachable debug statements (git-fixes).\n- ext4: fix slab-use-after-free in ext4_split_extent_at() (bsc#1232201)\n- fat: fix uninitialized variable (git-fixes).\n- fbdev: pxafb: Fix possible use after free in pxafb_task() (stable-fixes).\n- fbdev: sisfb: Fix strbuf array overflow (stable-fixes).\n- fgraph: Change the name of cpuhp state to 'fgraph:online' (git-fixes).\n- fgraph: Fix missing unlock in register_ftrace_graph() (git-fixes).\n- fgraph: Use CPU hotplug mechanism to initialize idle shadow stacks (git-fixes).\n- filelock: fix potential use-after-free in posix_lock_inode (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- fs/namespace: fnic: Switch to use %ptTd (git-fixes).\n- fs/pipe: Fix lockdep false-positive in watchqueue pipe_write() (git-fixes).\n- fs: Fix file_set_fowner LSM hook inconsistencies (git-fixes).\n- gpio: aspeed: Add the flush write to ensure the write complete (git-fixes).\n- gpio: aspeed: Use devm_clk api to manage clock source (git-fixes).\n- gpio: davinci: fix lazy disable (git-fixes).\n- hid: intel-ish-hid: Fix uninitialized variable 'rv' in ish_fw_xfer_direct_dma (git-fixes).\n- hv_netvsc: Fix VF namespace also in synthetic NIC NETDEV_REGISTER event (git-fixes).\n- hwmon: (adm9240) Add missing dependency on REGMAP_I2C (git-fixes).\n- hwmon: (tmp513) Add missing dependency on REGMAP_I2C (git-fixes).\n- i2c: i801: Use a different adapter-name for IDF adapters (stable-fixes).\n- i2c: imx-lpi2c: return -EINVAL when i2c peripheral clk does not work (bsc#1227885).\n- i2c: imx-lpi2c: use bulk clk API (bsc#1227885).\n- i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume (git-fixes).\n- i2c: xiic: Fix RX IRQ busy check (stable-fixes).\n- i2c: xiic: Fix broken locking on tx_msg (stable-fixes).\n- i2c: xiic: Fix pm_runtime_set_suspended() with runtime pm enabled (git-fixes).\n- i2c: xiic: Switch from waitqueue to completion (stable-fixes).\n- i2c: xiic: Try re-initialization on bus busy timeout (git-fixes).\n- i2c: xiic: Use devm_clk_get_enabled() (stable-fixes).\n- i2c: xiic: improve error message when transfer fails to start (stable-fixes).\n- i2c: xiic: xiic_xfer(): Fix runtime PM leak on error path (git-fixes).\n- ice: Unbind the workqueue (bsc#1231344).\n- iio: dac: ad5770r: add missing select REGMAP_SPI in Kconfig (git-fixes).\n- iio: dac: ltc1660: add missing select REGMAP_SPI in Kconfig (git-fixes).\n- iio: dac: stm32-dac-core: add missing select REGMAP_MMIO in Kconfig (git-fixes).\n- iio: hid-sensors: Fix an error handling path in _hid_sensor_set_report_latency() (git-fixes).\n- iio: light: opt3001: add missing full-scale range value (git-fixes).\n- iio: light: veml6030: fix ALS sensor resolution (git-fixes).\n- iio: light: veml6030: fix IIO device retrieval from embedded device (git-fixes).\n- iio: proximity: mb1232: add missing select IIO_(TRIGGERED_)BUFFER in Kconfig (git-fixes).\n- iommu/vt-d: Always reserve a domain ID for identity setup (git-fixes).\n- ipv6: blackhole_netdev needs snmp6 counters (bsc#1216813).\n- ipv6: give an IPv6 dev to blackhole_netdev (bsc#1216813).\n- jfs: Fix sanity check in dbMount (git-fixes).\n- jfs: Fix uaf in dbFreeBits (git-fixes).\n- jfs: Fix uninit-value access of new_ea in ea_buffer (git-fixes).\n- jfs: UBSAN: shift-out-of-bounds in dbFindBits (git-fixes).\n- jfs: check if leafidx greater than num leaves per dmap tree (git-fixes).\n- kABI: bpf: enum bpf_{type_flag,arg_type} kABI workaround (git-fixes).\n- kABI: bpf: struct bpf_func_proto kABI workaround (git-fixes).\n- kab: fix after net: add more sanity check in virtio_net_hdr_to_skb() (git-fixes).\n- kabi fix of KVM: arm64: Preserve PSTATE.SS for the guest while single-step is enabled (git-fixes).\n- kabi: fix after KVM: arm64: mixed-width check should be skipped for uninitialized vCPUs (git-fixes).\n- kabi: fix after kvm: add guest_state_{enter,exit}_irqoff() (git-fixes).\n- kbuild, bpf: Use test-ge check for v1.25-only pahole (bsc#1230414 bsc#1229450).\n- kbuild,bpf: Add module-specific pahole flags for distilled base BTF (bsc#1230414 bsc#1229450).\n- kbuild,bpf: Switch to using --btf_features for pahole v1.26 and later (bsc#1230414 bsc#1229450).\n- kbuild: add test-{ge,gt,le,lt} macros (bsc#1230414 bsc#1229450).\n- kbuild: avoid too many execution of scripts/pahole-flags.sh (bsc#1230414 bsc#1229450).\n- kbuild: bpf: Tell pahole to DECL_TAG kfuncs (bsc#1230414 bsc#1229450).\n- kvm/arm64: rework guest entry logic (git-fixes).\n- kvm: Add support for arch compat vm ioctls (git-fixes).\n- kvm: add guest_state_{enter,exit}_irqoff() (git-fixes).\n- media: videobuf2-core: clear memory related fields in __vb2_plane_dmabuf_put() (stable-fixes).\n- module: abort module loading when sysfs setup suffer errors (git-fixes).\n- nbd: fix race between timeout and normal completion (bsc#1230918).\n- net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX (bsc#1226797)\n- net: add more sanity check in virtio_net_hdr_to_skb() (git-fixes).\n- net: mana: Implement get_ringparam/set_ringparam for mana (bsc#1229891).\n- net: mana: Improve mana_set_channels() in low mem conditions (bsc#1230289).\n- net: socket: suppress unused warning (git-fixes).\n- net: test for not too small csum_start in virtio_net_hdr_to_skb() (git-fixes).\n- net: usb: usbnet: fix name regression (git-fixes).\n- netdevsim: use cond_resched() in nsim_dev_trap_report_work() (git-fixes).\n- nfs: fix memory leak in error path of nfs4_do_reclaim (git-fixes).\n- nfsd: call cache_put if xdr_reserve_space returns NULL (git-fixes).\n- nfsd: fix delegation_blocked() to block correctly for at least 30 seconds (git-fixes).\n- nfsd: fix refcount leak when file is unhashed after being found (git-fixes).\n- nfsd: map the EBADMSG to nfserr_io to avoid warning (git-fixes).\n- nfsd: remove unneeded EEXIST error check in nfsd_do_file_acquire (git-fixes).\n- nfsd: return -EINVAL when namelen is 0 (git-fixes).\n- nilfs2: fix kernel bug due to missing clearing of buffer delay flag (git-fixes).\n- nouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error (git-fixes).\n- ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() (git-fixes).\n- ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition (stable-fixes).\n- nvme-multipath: system fails to create generic nvme device (git-fixes).\n- nvme-pci: qdepth 1 quirk (git-fixes).\n- nvmet-auth: assign dh_key to NULL after kfree_sensitive (git-fixes).\n- ocfs2: fix the la space leak when unmounting an ocfs2 volume (git-fixes).\n- ocfs2: fix uninit-value in ocfs2_get_block() (git-fixes).\n- ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow (git-fixes).\n- parport: Proper fix for array out-of-bounds access (git-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: touchscreen_dmi: add nanote-next quirk (stable-fixes).\n- power: reset: brcmstb: Do not go into infinite loop if reset fails (stable-fixes).\n- powerpc/64: Convert patch_instruction() to patch_u32() (bsc#1194869).\n- powerpc/boot: Handle allocation failure in simple_realloc() (bsc#1194869).\n- powerpc/boot: Only free if realloc() succeeds (bsc#1194869).\n- powerpc/code-patching: Add generic memory patching (bsc#1194869).\n- powerpc/code-patching: Consolidate and cache per-cpu patching context (bsc#1194869).\n- powerpc/code-patching: Do not call is_vmalloc_or_module_addr() without CONFIG_MODULES (bsc#1194869).\n- powerpc/code-patching: Fix error handling in do_patch_instruction() (bsc#1194869).\n- powerpc/code-patching: Fix oops with DEBUG_VM enabled (bsc#1194869).\n- powerpc/code-patching: Fix unmap_patch_area() error handling (bsc#1194869).\n- powerpc/code-patching: Perform hwsync in __patch_instruction() in case of failure (bsc#1194869).\n- powerpc/code-patching: Pre-map patch area (bsc#1194869).\n- powerpc/code-patching: Remove #ifdef CONFIG_STRICT_KERNEL_RWX (bsc#1194869).\n- powerpc/code-patching: Remove pr_debug()/pr_devel() messages and fix check() (bsc#1194869).\n- powerpc/code-patching: Reorganise do_patch_instruction() to ease error handling (bsc#1194869).\n- powerpc/code-patching: Speed up page mapping/unmapping (bsc#1194869).\n- powerpc/code-patching: Use WARN_ON and fix check in poking_init (bsc#1194869).\n- powerpc/code-patching: Use jump_label to check if poking_init() is done (bsc#1194869).\n- powerpc/code-patching: Use temporary mm for Radix MMU (bsc#1194869).\n- powerpc/code-patching: introduce patch_instructions() (bsc#1194869).\n- powerpc/ftrace: Use patch_instruction() return directly (bsc#1194869).\n- powerpc/imc-pmu: Fix use of mutex in IRQs disabled section (bsc#1054914 git-fixes).\n- powerpc/imc-pmu: Use the correct spinlock initializer (bsc#1054914 git-fixes).\n- powerpc/inst: Refactor ___get_user_instr() (bsc#1194869).\n- powerpc/lib: Add __init attribute to eligible functions (bsc#1194869).\n- powerpc/tlb: Add local flush for page given mm_struct and psize (bsc#1194869).\n- powerpc/vdso: Fix VDSO data access when running in a non-root time namespace (bsc#1194869).\n- powerpc/vdso: Merge vdso64 and vdso32 into a single directory (bsc#1194869).\n- powerpc/vdso: Rework VDSO32 makefile to add a prefix to object files (bsc#1194869).\n- powerpc/vdso: augment VDSO32 functions to support 64 bits build (bsc#1194869).\n- powerpc/xics: Check return value of kasprintf in icp_native_map_one_cpu (bsc#1194869).\n- powerpc/xmon: Fix disassembly CPU feature checks (bsc#1065729).\n- powerpc: Allow clearing and restoring registers independent of saved breakpoint state (bsc#1194869).\n- rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow (bsc#1226631).\n- rcu: Add rcutree.nohz_full_patience_delay to reduce nohz_full (bsc#1231327)\n- s390/mm: Add cond_resched() to cmm_alloc/free_pages() (bsc#1228747).\n- s390/sclp_vt220: Convert newlines to CRLF instead of LFCR (git-fixes bsc#1232632).\n- sched/isolation: Prevent boot crash when the boot CPU is (bsc#1231327)\n- scsi: NCR5380: Check for phase match during PDMA fixup (git-fixes).\n- scsi: aacraid: Rearrange order of struct aac_srb_unit (git-fixes).\n- scsi: core: Fix the return value of scsi_logical_block_count() (git-fixes).\n- scsi: core: Handle devices which return an unusually large VPD page count (git-fixes).\n- scsi: core: alua: I/O errors for ALUA state transitions (git-fixes).\n- scsi: elx: libefc: Fix potential use after free in efc_nport_vport_del() (git-fixes).\n- scsi: fnic: Move flush_work initialization out of if block (bsc#1230055).\n- scsi: hpsa: Fix allocation size for Scsi_Host private data (git-fixes).\n- scsi: libsas: Fix exp-attached device scan after probe failure scanned in again after probe failed (git-fixes).\n- scsi: libsas: Fix the failure of adding phy with zero-address to port (git-fixes).\n- scsi: lpfc: Add ELS_RSP cmd to the list of WQEs to flush in lpfc_els_flush_cmd() (bsc#1232757).\n- scsi: lpfc: Ensure DA_ID handling completion before deleting an NPIV instance (bsc#1232757).\n- scsi: lpfc: Fix kref imbalance on fabric ndlps from dev_loss_tmo handler (bsc#1232757).\n- scsi: lpfc: Remove trailing space after \\n newline (bsc#1232757).\n- scsi: lpfc: Restrict support for 32 byte CDBs to specific HBAs (git-fixes).\n- scsi: lpfc: Revise TRACE_EVENT log flag severities from KERN_ERR to KERN_WARNING (bsc#1232757).\n- scsi: lpfc: Support loopback tests with VMID enabled (bsc#1232757).\n- scsi: lpfc: Update lpfc version to 14.4.0.5 (bsc#1232757).\n- scsi: lpfc: Update phba link state conditional before sending CMF_SYNC_WQE (bsc#1232757).\n- scsi: mac_scsi: Disallow bus errors during PDMA send (git-fixes).\n- scsi: mac_scsi: Refactor polling loop (git-fixes).\n- scsi: mac_scsi: Revise printk(KERN_DEBUG ...) messages (git-fixes).\n- scsi: mpi3mr: Avoid IOMMU page faults on REPORT ZONES (git-fixes).\n- scsi: mpi3mr: Fix ATA NCQ priority support (git-fixes).\n- scsi: mpt3sas: Avoid IOMMU page faults on REPORT ZONES (git-fixes).\n- scsi: qedf: Set qed_slowpath_params to zero before use (git-fixes).\n- scsi: smartpqi: correct stream detection (git-fixes).\n- scsi: smartpqi: revert propagate-the-multipath-failure-to-SML-quickly (git-fixes).\n- scsi: spi: Fix sshdr use (git-fixes).\n- scsi: wd33c93: Do not use stale scsi_pointer value (git-fixes).\n- selftests/bpf: Add a test case to write mtu result into .rodata (git-fixes).\n- selftests/bpf: Add a test case to write strtol result into .rodata (git-fixes).\n- selftests/bpf: Fix ARG_PTR_TO_LONG {half-,}uninitialized test (git-fixes).\n- selftests/bpf: Rename ARG_PTR_TO_LONG test description (git-fixes).\n- selftests/bpf: test for malformed BPF_CORE_TYPE_ID_LOCAL relocation (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: lpspi: Silence error message upon deferred probe (stable-fixes).\n- spi: lpspi: Simplify some error message (git-fixes).\n- spi: lpspi: release requested DMA channels (stable-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: s3c64xx: fix timeout counters in flush_fifo (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spi-imx: Fix pm_runtime_set_suspended() with runtime pm enabled (git-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- static_call: Do not make __static_call_return0 static (git-fixes).\n- tracing/hwlat: Fix a race during cpuhp processing (git-fixes).\n- tracing/uprobes: Use trace_event_buffer_reserve() helper (git-fixes).\n- tracing: Consider the NULL character when validating the event length (git-fixes).\n- uprobe: avoid out-of-bounds memory access of fetching args (git-fixes).\n- uprobes: encapsulate preparation of uprobe args buffer (git-fixes).\n- usb: chipidea: udc: enable suspend interrupt after usb reset (stable-fixes).\n- usb: dwc2: Adjust the timing of USB Driver Interrupt Registration in the Crashkernel Scenario (stable-fixes).\n- usb: dwc3: core: Stop processing of pending events if controller is halted (git-fixes).\n- usb: gadget: core: force synchronous registration (git-fixes).\n- usb: storage: ignore bogus device raised by JieLi BR21 USB sound chip (stable-fixes).\n- usb: typec: altmode should keep reference to parent (git-fixes).\n- usb: xhci: Fix problem with xhci resume from suspend (stable-fixes).\n- usb: yurex: Fix inconsistent locking bug in yurex_read() (git-fixes).\n- usb: yurex: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (stable-fixes).\n- vhost/scsi: null-ptr-dereference in vhost_scsi_get_req() (git-fixes).\n- vhost_vdpa: assign irq bypass producer token correctly (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_console: fix misc probe bugs (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- vmxnet3: add command to allow disabling of offloads (bsc#1226498).\n- vmxnet3: add latency measurement support in vmxnet3 (bsc#1226498).\n- vmxnet3: prepare for version 9 changes (bsc#1226498).\n- vmxnet3: update to version 9 (bsc#1226498).\n- vsock/virtio: fix packet delivery to tap device (git-fixes).\n- wifi: ath11k: fix array out-of-bound access in SoC stats (stable-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: ath9k: fix parameter check in ath9k_init_debug() (stable-fixes).\n- wifi: ath9k: fix possible integer overflow in ath9k_get_et_stats() (stable-fixes).\n- wifi: ath9k_htc: Use __skb_set_length() for resetting urb before resubmit (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() (stable-fixes).\n- wifi: rtw88: select WANT_DEV_COREDUMP (stable-fixes).\n- workqueue: Avoid using isolated cpus' timers on (bsc#1231327)\n- workqueue: mark power efficient workqueue as unbounded if (bsc#1231327)\n- x86/bugs: Do not use UNTRAIN_RET with IBPB on entry (git-fixes).\n- x86/bugs: Skip RSB fill at VMEXIT (git-fixes).\n- x86/cpufeatures: Add a IBPB_NO_RET BUG flag (git-fixes).\n- x86/cpufeatures: Define X86_FEATURE_AMD_IBPB_RET (git-fixes).\n- x86/entry: Have entry_ibpb() invalidate return predictions (git-fixes).\n- x86/hyperv: Set X86_FEATURE_TSC_KNOWN_FREQ when Hyper-V provides frequency (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1230405).\n- xfrm: set dst dev to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- xhci: Fix incorrect stream context type macro (git-fixes).\n- xhci: Mitigate failed set dequeue pointer commands (git-fixes).\n","status":"published","published":"2024-11-13T10:13:36Z","modified":"2026-02-04T04:35:48.847859Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4100-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\nThe Linux Enterprise 12 SP5 kernel turned LTSS (Extended Security)\n\nThe following security bugs were fixed:\n\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47163: kABI fix for tipc: wait and exit until all work queues are done (bsc#1221980).\n- CVE-2021-47612: nfc: fix segfault in nfc_genl_dump_devices_done (bsc#1226585).\n- CVE-2022-48809: net: fix a memleak when uncloning an skb dst and its metadata (bsc#1227947).\n- CVE-2022-48951: ASoC: ops: Correct bounds check for second channel on SX controls (bsc#1231929).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48958: ethernet: aeroflex: fix potential skb leak in greth_init_rings() (bsc#1231889).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48966: net: mvneta: Fix an out of bounds check (bsc#1232191).\n- CVE-2022-48967: NFC: nci: Bounds check struct nfc_target arrays (bsc#1232304).\n- CVE-2022-48971: Bluetooth: Fix not cleanup led when bt_init fails (bsc#1232037).\n- CVE-2022-48972: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (bsc#1232025).\n- CVE-2022-48973: gpio: amd8111: Fix PCI device reference count leak (bsc#1232039).\n- CVE-2022-48978: HID: core: fix shift-out-of-bounds in hid_report_raw_event (bsc#1232038).\n- CVE-2022-48991: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (bsc#1232070).\n- CVE-2022-48992: ASoC: soc-pcm: Add NULL check in BE reparenting (bsc#1232071).\n- CVE-2022-49000: iommu/vt-d: Fix PCI device refcount leak in has_external_pci() (bsc#1232123).\n- CVE-2022-49002: iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() (bsc#1232133).\n- CVE-2022-49010: hwmon: (coretemp) Check for null before removing sysfs attrs (bsc#1232172).\n- CVE-2022-49011: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() (bsc#1232006).\n- CVE-2022-49014: net: tun: Fix use-after-free in tun_detach() (bsc#1231890).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2022-49020: net/9p: Fix a potential socket leak in p9_socket_open (bsc#1232175).\n- CVE-2022-49021: net: phy: fix null-ptr-deref while probe() failed (bsc#1231939).\n- CVE-2022-49026: e100: Fix possible use after free in e100_xmit_prepare (bsc#1231997).\n- CVE-2022-49027: iavf: Fix error handling in iavf_init_module() (bsc#1232007).\n- CVE-2022-49028: ixgbevf: Fix resource leak in ixgbevf_init_module() (bsc#1231996).\n- CVE-2022-49029: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails (bsc#1231995).\n- CVE-2023-52898: xhci: Fix null pointer dereference when host dies (bsc#1229568).\n- CVE-2023-52918: media: pci: cx23885: check cx23885_vdev_init() return (bsc#1232047).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (bsc#1227437).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command  (bsc#1228620).\n- CVE-2024-42114: netlink: extend policy range validation (bsc#1228564 prerequisite).\n- CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race (bsc#1229005 stable-fixes).\n- CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc() (bsc#1229837 stable-fixes).\n- CVE-2024-44958: sched/smt: Fix unbalance sched_smt_present dec/inc (bsc#1230179).\n- CVE-2024-46724: drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (bsc#1230725).\n- CVE-2024-46755: wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (bsc#1230802).\n- CVE-2024-46802: drm/amd/display: added NULL check at start of dc_validate_stream (bsc#1231111).\n- CVE-2024-46809: drm/amd/display: Check BIOS images before it is used (bsc#1231148).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46826: ELF: fix kernel.randomize_va_space double read (bsc#1231115).\n- CVE-2024-46834: ethtool: fail closed if we can't get max channel used in indirection tables (bsc#1231096).\n- CVE-2024-46840: btrfs: clean up our handling of refs == 0 in snapshot delete (bsc#1231105).\n- CVE-2024-46841: btrfs: do not BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (bsc#1231094).\n- CVE-2024-46848: perf/x86/intel: Limit the period on Haswell (bsc#1231072).\n- CVE-2024-47672: wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (bsc#1231540).\n- CVE-2024-47673: wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (bsc#1231539).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47685: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() (bsc#1231998).\n- CVE-2024-47697: drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (bsc#1231858).\n- CVE-2024-47698: drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (bsc#1231859).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47707: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (bsc#1231935).\n- CVE-2024-47713: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (bsc#1232016).\n- CVE-2024-47735: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (bsc#1232111).\n- CVE-2024-47737: nfsd: call cache_put if xdr_reserve_space returns NULL (bsc#1232056).\n- CVE-2024-47742: firmware_loader: Block path traversal (bsc#1232126).\n- CVE-2024-47745: mm: split critical region in remap_file_pages() and invoke LSMs in between (bsc#1232135).\n- CVE-2024-49851: tpm: Clean up TPM space after command failure (bsc#1232134).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49881: ext4: update orig_path in ext4_find_extent() (bsc#1232201).\n- CVE-2024-49882: ext4: fix double brelse() the buffer of the extents path (bsc#1232200).\n- CVE-2024-49883: ext4: aovid use-after-free in ext4_ext_insert_extent() (bsc#1232199).\n- CVE-2024-49890: drm/amd/pm: ensure the fw_info is not null before using it (bsc#1232217).\n- CVE-2024-49891: scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1232218).\n- CVE-2024-49894: drm/amd/display: Fix index out of bounds in degamma hardware format translation (bsc#1232354).\n- CVE-2024-49896: drm/amd/display: Check stream before comparing them (bsc#1232221).\n- CVE-2024-49901: drm/msm/adreno: Assign msm_gpu-\u003epdev earlier to avoid nullptrs (bsc#1232305).\n- CVE-2024-49920: drm/amd/display: Check null pointers before multiple uses (bsc#1232313).\n- CVE-2024-49929: wifi: iwlwifi: mvm: avoid NULL pointer dereference (bsc#1232253).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49949: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (bsc#1232160).\n- CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree (bsc#1232151).\n- CVE-2024-49959: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error (bsc#1232149).\n- CVE-2024-49962: ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (bsc#1232314).\n- CVE-2024-49966: ocfs2: cancel dqi_sync_work before freeing oinfo (bsc#1232141).\n- CVE-2024-49967: ext4: no need to continue when the number of entries is 1 (bsc#1232140).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate() (bsc#1232442).\n- CVE-2024-50007: ALSA: asihpi: Fix potential OOB array access (bsc#1232394).\n- CVE-2024-50024: net: Fix an unsafe loop on the list (bsc#1231954).\n- CVE-2024-50033: slip: make slhc_remember() more robust against malicious packets (bsc#1231914).\n- CVE-2024-50035: ppp: fix ppp_async_encode() illegal access (bsc#1232392).\n- CVE-2024-50045: netfilter: br_netfilter: fix panic with metadata_dst skb (bsc#1231903).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n- CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too (bsc#1232285).\n\nThe following non-security bugs were fixed:\n\n- arm64: esr: Define ESR_ELx_EC_* constants as UL (git-fixes)\n- arm64: probes: Fix simulate_ldr*_literal() (git-fixes)\n- arm64: probes: Fix uprobes for big-endian kernels (git-fixes)\n- arm64: probes: Remove broken LDR (literal) uprobe support (git-fixes)\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- drbd: Add NULL check for net_conf to prevent dereference in state validation (git-fixes).\n- drbd: Fix atomicity violation in drbd_uuid_set_bm() (git-fixes).\n- ext4: fix slab-use-after-free in ext4_split_extent_at() (bsc#1232201)\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- net: usb: usbnet: fix name regression (get-fixes).\n- nfs: fix memory leak in error path of nfs4_do_reclaim (git-fixes).\n- nfsd: fix delegation_blocked() to block correctly for at least 30 seconds (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1230405).\n","status":"published","published":"2024-11-28T12:42:12Z","modified":"2026-02-04T02:21:54.049545Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4364-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47594: mptcp: never allow the PM to close a listener subflow (bsc#1226560).\n- CVE-2022-48879: efi: fix NULL-deref in init error path (bsc#1229556).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48957: dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove() (bsc#1231973).\n- CVE-2022-48958: ethernet: aeroflex: fix potential skb leak in greth_init_rings() (bsc#1231889).\n- CVE-2022-48959: net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions() (bsc#1231976).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48966: net: mvneta: Fix an out of bounds check (bsc#1232191).\n- CVE-2022-48980: net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing() (bsc#1232233).\n- CVE-2022-48983: io_uring: Fix a null-ptr-deref in io_tctx_exit_cb() (bsc#1231959).\n- CVE-2022-48991: mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma (bsc#1232070).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2022-49017: tipc: re-fetch skb cb after tipc_msg_validate (bsc#1232004).\n- CVE-2022-49020: net/9p: Fix a potential socket leak in p9_socket_open (bsc#1232175).\n- CVE-2024-26782: mptcp: fix double-free on socket dismantle (bsc#1222590).\n- CVE-2024-26906: Fixed invalid vsyscall page read for copy_from_kernel_nofault() (bsc#1223202).\n- CVE-2024-26953: net: esp: fix bad handling of pages from page_pool (bsc#1223656).\n- CVE-2024-35888: erspan: make sure erspan_base_hdr is present in skb-\u003ehead (bsc#1224518).\n- CVE-2024-35937: wifi: cfg80211: check A-MSDU format more carefully (bsc#1224526).\n- CVE-2024-36244: net/sched: taprio: extend minimum interval restriction to entire cycle too (bsc#1226797).\n- CVE-2024-36883: net: fix out-of-bounds access in ops_init (bsc#1225725).\n- CVE-2024-36886: tipc: fix UAF in error path (bsc#1225730).\n- CVE-2024-36905: tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets (bsc#1225742).\n- CVE-2024-36954: tipc: fix a possible memleak in tipc_buf_append (bsc#1225764).\n- CVE-2024-36957: octeontx2-af: avoid off-by-one read from userspace (bsc#1225762).\n- CVE-2024-38589: netrom: fix possible dead-lock in nr_rt_ioctl() (bsc#1226748).\n- CVE-2024-38615: cpufreq: exit() callback is optional (bsc#1226592).\n- CVE-2024-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (bsc#1227437).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40997: cpufreq: amd-pstate: fix memory leak on CPU EPP exit (bsc#1227853).\n- CVE-2024-41023: sched/deadline: Fix task_struct reference leak (bsc#1228430).\n- CVE-2024-42226: Prevent potential failure in handle_tx_event() for Transfer events without TRB (bsc#1228709).\n- CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race (bsc#1229005).\n- CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc() (bsc#1229837).\n- CVE-2024-44932: idpf: fix UAFs when destroying the queues (bsc#1229808).\n- CVE-2024-44958: sched/smt: Fix unbalance sched_smt_present dec/inc (bsc#1230179).\n- CVE-2024-44964: idpf: fix memory leaks and crashes while performing a soft reset (bsc#1230220).\n- CVE-2024-44995: net: hns3: fix a deadlock problem when config TC during resetting (bsc#1230231).\n- CVE-2024-45016: netem: fix return value if duplicate enqueue fails (bsc#1230429).\n- CVE-2024-45025: fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE (bsc#1230456).\n- CVE-2024-46678: bonding: change ipsec_lock from spin lock to mutex (bsc#1230550).\n- CVE-2024-46681: pktgen: use cpus_read_lock() in pg_net_init() (bsc#1230558).\n- CVE-2024-46716: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (bsc#1230715).\n- CVE-2024-46754: bpf: Remove tst_run from lwt_seg6local_prog_ops (bsc#1230801).\n- CVE-2024-46770: ice: Add netif_device_attach/detach into PF reset flow (bsc#1230763).\n- CVE-2024-46775: drm/amd/display: Validate function returns (bsc#1230774).\n- CVE-2024-46777: udf: Avoid excessive partition lengths (bsc#1230773).\n- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).\n- CVE-2024-46809: drm/amd/display: Check BIOS images before it is used (bsc#1231148).\n- CVE-2024-46811: drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (bsc#1231179).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46814: drm/amd/display: Check msg_id before processing transcation (bsc#1231193).\n- CVE-2024-46815: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets (bsc#1231195).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46817: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (bsc#1231200).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46826: ELF: fix kernel.randomize_va_space double read (bsc#1231115).\n- CVE-2024-46828: uprobes: fix kernel info leak via '[uprobes]' vma (bsc#1231114).\n- CVE-2024-46834: ethtool: fail closed if we can't get max channel used in indirection tables (bsc#1231096).\n- CVE-2024-46840: btrfs: clean up our handling of refs == 0 in snapshot delete (bsc#1231105).\n- CVE-2024-46841: btrfs: do not BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (bsc#1231094).\n- CVE-2024-46848: perf/x86/intel: Limit the period on Haswell (bsc#1231072).\n- CVE-2024-46849: ASoC: meson: axg-card: fix 'use-after-free' (bsc#1231073).\n- CVE-2024-46854: net: dpaa: Pad packets to ETH_ZLEN (bsc#1231084).\n- CVE-2024-46855: netfilter: nft_socket: fix sk refcount leaks (bsc#1231085).\n- CVE-2024-46857: net/mlx5: Fix bridge mode operations when there are no VFs (bsc#1231087).\n- CVE-2024-47660: fsnotify: clear PARENT_WATCHED flags lazily (bsc#1231439).\n- CVE-2024-47661: drm/amd/display: Avoid overflow from uint32_t to uint8_t (bsc#1231496).\n- CVE-2024-47664: spi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware (bsc#1231442).\n- CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (bsc#1231502).\n- CVE-2024-47672: wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (bsc#1231540).\n- CVE-2024-47673: wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (bsc#1231539).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47679: vfs: fix race between evice_inodes() and find_inode()\u0026iput() (bsc#1231930).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47685: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() (bsc#1231998).\n- CVE-2024-47692: nfsd: return -EINVAL when namelen is 0 (bsc#1231857).\n- CVE-2024-47701: ext4: explicitly exit when ext4_find_inline_entry returns an error (bsc#1231920).\n- CVE-2024-47704: drm/amd/display: Check link_res-\u003ehpo_dp_link_enc before using it (bsc#1231944).\n- CVE-2024-47705: block: fix potential invalid pointer dereference in blk_add_partition (bsc#1231872).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47707: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (bsc#1231935).\n- CVE-2024-47710: sock_map: Add a cond_resched() in sock_hash_free() (bsc#1232049).\n- CVE-2024-47720: drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (bsc#1232043).\n- CVE-2024-47727: x86/tdx: Fix 'in-kernel MMIO' check (bsc#1232116).\n- CVE-2024-47730: crypto: hisilicon/qm - inject error before stopping queue (bsc#1232075).\n- CVE-2024-47738: wifi: mac80211: do not use rate mask for offchannel TX either (bsc#1232114).\n- CVE-2024-47739: padata: use integer wrap around to prevent deadlock on seq_nr overflow (bsc#1232124).\n- CVE-2024-47745: mm: split critical region in remap_file_pages() and invoke LSMs in between (bsc#1232135).\n- CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition (bsc#1232145).\n- CVE-2024-47748: vhost_vdpa: assign irq bypass producer token correctly (bsc#1232174).\n- CVE-2024-47757: nilfs2: fix potential oob read in nilfs_btree_check_delete() (bsc#1232187).\n- CVE-2024-49858: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption (bsc#1232251).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49866: tracing/timerlat: Fix a race during cpuhp processing (bsc#1232259).\n- CVE-2024-49868: btrfs: fix a NULL pointer dereference when failed to start a new trasacntion (bsc#1232272).\n- CVE-2024-49881: ext4: update orig_path in ext4_find_extent() (bsc#1232201).\n- CVE-2024-49882: ext4: fix double brelse() the buffer of the extents path (bsc#1232200).\n- CVE-2024-49883: ext4: aovid use-after-free in ext4_ext_insert_extent() (bsc#1232199).\n- CVE-2024-49886: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug (bsc#1232196).\n- CVE-2024-49890: drm/amd/pm: ensure the fw_info is not null before using it (bsc#1232217).\n- CVE-2024-49892: drm/amd/display: Initialize get_bytes_per_element's default to 1 (bsc#1232220).\n- CVE-2024-49896: drm/amd/display: Check stream before comparing them (bsc#1232221).\n- CVE-2024-49897: drm/amd/display: Check phantom_stream before it is used (bsc#1232355).\n- CVE-2024-49899: drm/amd/display: Initialize denominators' default to 1 (bsc#1232358).\n- CVE-2024-49901: drm/msm/adreno: Assign msm_gpu-\u003epdev earlier to avoid nullptrs (bsc#1232305).\n- CVE-2024-49906: drm/amd/display: Check null pointer before try to access it (bsc#1232332).\n- CVE-2024-49909: drm/amd/display: Add NULL check for function pointer in dcn32_set_output_transfer_func (bsc#1232337).\n- CVE-2024-49911: drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func (bsc#1232366).\n- CVE-2024-49914: drm/amd/display: Add null check for pipe_ctx-\u003eplane_state in (bsc#1232369).\n- CVE-2024-49917: drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u003efuncs in dcn30_init_hw (bsc#1231965).\n- CVE-2024-49918: drm/amd/display: Add null check for head_pipe in dcn32_acquire_idle_pipe_for_head_pipe_in_layer (bsc#1231967).\n- CVE-2024-49919: drm/amd/display: Add null check for head_pipe in dcn201_acquire_free_pipe_for_layer (bsc#1231968).\n- CVE-2024-49920: drm/amd/display: Check null pointers before multiple uses (bsc#1232313).\n- CVE-2024-49921: drm/amd/display: Check null pointers before used (bsc#1232371).\n- CVE-2024-49922: drm/amd/display: Check null pointers before using them (bsc#1232374).\n- CVE-2024-49923: drm/amd/display: Pass non-null to dcn20_validate_apply_pipe_split_flags (bsc#1232361).\n- CVE-2024-49925: fbdev: efifb: Register sysfs groups through driver core (bsc#1232224)\n- CVE-2024-49929: wifi: iwlwifi: mvm: avoid NULL pointer dereference (bsc#1232253).\n- CVE-2024-49930: wifi: ath11k: fix array out-of-bound access in SoC stats (bsc#1232260).\n- CVE-2024-49933: blk_iocost: fix more out of bound shifts (bsc#1232368).\n- CVE-2024-49934: fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name (bsc#1232387).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49939: wifi: rtw89: avoid to add interface to list twice when SER (bsc#1232381).\n- CVE-2024-49945: net/ncsi: Disable the ncsi work before freeing the associated structure (bsc#1232165).\n- CVE-2024-49946: ppp: do not assume bh is held in ppp_channel_bridge_input() (bsc#1232164).\n- CVE-2024-49949: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (bsc#1232160).\n- CVE-2024-49950: Bluetooth: L2CAP: Fix uaf in l2cap_connect (bsc#1232159).\n- CVE-2024-49954: static_call: Replace pointless WARN_ON() in static_call_module_notify() (bsc#1232155).\n- CVE-2024-49955: ACPI: battery: Fix possible crash when unregistering a battery hook (bsc#1232154).\n- CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree (bsc#1232151).\n- CVE-2024-49959: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error (bsc#1232149).\n- CVE-2024-49960: ext4: fix timer use-after-free on failed mount (bsc#1232395).\n- CVE-2024-49967: ext4: no need to continue when the number of entries is 1 (bsc#1232140).\n- CVE-2024-49968: ext4: fix error message when rejecting the default hash (bsc#1232264).\n- CVE-2024-49969: drm/amd/display: Fix index out of bounds in DCN30 color transformation (bsc#1232519).\n- CVE-2024-49973: r8169: add tally counter fields added with RTL8125 (bsc#1232105).\n- CVE-2024-49974: NFSD: Force all NFSv4.2 COPY requests to be synchronous (bsc#1232383).\n- CVE-2024-49975: uprobes: fix kernel info leak via '[uprobes]' vma (bsc#1232104).\n- CVE-2024-49983: ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free (bsc#1232096).\n- CVE-2024-49989: drm/amd/display: fix double free issue during amdgpu module unload (bsc#1232483).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49993: iommu/vt-d: Fix potential lockup if qi_submit_sync called with 0 count (bsc#1232316).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-50000: net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() (bsc#1232085).\n- CVE-2024-50001: net/mlx5: Fix error path in multi-packet WQE transmit (bsc#1232084).\n- CVE-2024-50002: static_call: Handle module init failure correctly in static_call_del_module() (bsc#1232083).\n- CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate() (bsc#1232442).\n- CVE-2024-50009: cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value (bsc#1232318).\n- CVE-2024-50014: ext4: fix access to uninitialised lock in fc replay path (bsc#1232446).\n- CVE-2024-50019: kthread: unpark only parked kthread (bsc#1231990).\n- CVE-2024-50024: net: Fix an unsafe loop on the list (bsc#1231954).\n- CVE-2024-50028: thermal: core: Reference count the zone in thermal_zone_get_by_id() (bsc#1231950).\n- CVE-2024-50033: slip: make slhc_remember() more robust against malicious packets (bsc#1231914).\n- CVE-2024-50035: ppp: fix ppp_async_encode() illegal access (bsc#1232392).\n- CVE-2024-50041: i40e: Fix macvlan leak by synchronizing access to mac_filter_hash (bsc#1231907).\n- CVE-2024-50045: netfilter: br_netfilter: fix panic with metadata_dst skb (bsc#1231903).\n- CVE-2024-50046: kabi fix for NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() (bsc#1231902).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n- CVE-2024-50048: fbcon: Fix a NULL pointer dereference issue in fbcon_putcs (bsc#1232310).\n- CVE-2024-50055: driver core: bus: Fix double free in driver API bus_register() (bsc#1232329).\n- CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too (bsc#1232285).\n- CVE-2024-50059: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition (bsc#1232345).\n- CVE-2024-50061: i3c: master: cdns: Fix use after free vulnerability in cdns_i3c_master Driver Due to Race Condition (bsc#1232263).\n- CVE-2024-50063: kABI: bpf: struct bpf_map kABI workaround (bsc#1232435).\n- CVE-2024-50073: tty: n_gsm: Fix use-after-free in gsm_cleanup_mux (bsc#1232520).\n- CVE-2024-50081: blk-mq: setup queue -\u003etag_set before initializing hctx (bsc#1232501).\n- CVE-2024-50082: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race (bsc#1232500).\n- CVE-2024-50089: unicode: Do not special case ignorable code points (bsc#1232860).\n- CVE-2024-50093: thermal: intel: int340x: processor: Fix warning during module unload (bsc#1232877).\n- CVE-2024-50098: scsi: ufs: core: Set SDEV_OFFLINE when UFS is shut down (bsc#1232881).\n- CVE-2024-50108: drm/amd/display: Disable PSR-SU on Parade 08-01 TCON too (bsc#1232884).\n- CVE-2024-50110: xfrm: fix one more kernel-infoleak in algo dumping (bsc#1232885).\n- CVE-2024-50115: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory (bsc#1232919).\n- CVE-2024-50125: Bluetooth: SCO: Fix UAF on sco_sock_timeout (bsc#1232928).\n- CVE-2024-50127: net: sched: fix use-after-free in taprio_change() (bsc#1232907).\n- CVE-2024-50128: net: wwan: fix global oob in wwan_rtnl_policy (bsc#1232905).\n- CVE-2024-50134: drm/vboxvideo: Replace fake VLA at end of vbva_mouse_pointer_shape (bsc#1232890).\n- CVE-2024-50135: nvme-pci: fix race condition between reset and nvme_dev_disable() (bsc#1232888).\n- CVE-2024-50138: bpf: Use raw_spinlock_t in ringbuf (bsc#1232935).\n- CVE-2024-50146: net/mlx5e: Do not call cleanup on profile rollback failure (bsc#1233056).\n- CVE-2024-50147: net/mlx5: Fix command bitmask initialization (bsc#1233067).\n- CVE-2024-50153: scsi: target: core: Fix null-ptr-deref in target_alloc_device() (bsc#1233061).\n- CVE-2024-50154: tcp: Fix use-after-free of nreq in reqsk_timer_handler() (bsc#1233070).\n- CVE-2024-50167: be2net: fix potential memory leak in be_xmit() (bsc#1233049).\n- CVE-2024-50171: net: systemport: fix potential memory leak in bcm_sysport_xmit() (bsc#1233057).\n- CVE-2024-50182: secretmem: disable memfd_secret() if arch cannot set direct map (bsc#1233129).\n- CVE-2024-50184: virtio_pmem: Check device status before requesting flush (bsc#1233135).\n- CVE-2024-50186: net: explicitly clear the sk pointer, when pf-\u003ecreate fails (bsc#1233110).\n- CVE-2024-50188: net: phy: dp83869: fix memory corruption when enabling fiber (bsc#1233107).\n- CVE-2024-50192: irqchip/gic-v4: Correctly deal with set_affinity on lazily-mapped VPEs (bsc#1233106).\n- CVE-2024-50195: posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime() (bsc#1233103).\n- CVE-2024-50196: pinctrl: ocelot: fix system hang on level based interrupts (bsc#1233113).\n- CVE-2024-50205: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() (bsc#1233293).\n- CVE-2024-50208: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages (bsc#1233117).\n- CVE-2024-50229: nilfs2: fix potential deadlock with newly created symlinks (bsc#1233205).\n- CVE-2024-50230: nilfs2: fix kernel bug due to missing clearing of checked flag (bsc#1233206).\n- CVE-2024-50259: netdevsim: Add trailing zero to terminate the string in nsim_nexthop_bucket_activity_write() (bsc#1233214).\n- CVE-2024-50261: macsec: Fix use-after-free while sending the offloading packet (bsc#1233253).\n- CVE-2024-50264: vsock/virtio: Initialization of the dangling pointer occurring in vsk-\u003etrans (bsc#1233453).\n- CVE-2024-50267: usb: serial: io_edgeport: fix use after free in debug printk (bsc#1233456).\n- CVE-2024-50271: signal: restore the override_rlimit logic (bsc#1233460).\n- CVE-2024-50273: btrfs: reinitialize delayed ref list after deleting it from the list (bsc#1233462).\n- CVE-2024-50274: idpf: avoid vport access in idpf_get_link_ksettings (bsc#1233463).\n- CVE-2024-50279: dm cache: fix out-of-bounds access to the dirty bitset when resizing (bsc#1233468).\n- CVE-2024-50289: media: av7110: fix a spectre vulnerability (bsc#1233478).\n- CVE-2024-50295: net: arc: fix the device for dma_map_single/dma_unmap_single (bsc#1233484).\n- CVE-2024-50298: net: enetc: allocate vf_state during PF probes (bsc#1233487).\n- CVE-2024-53052: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (bsc#1233548).\n- CVE-2024-53058: net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data (bsc#1233552).\n- CVE-2024-53061: media: s5p-jpeg: prevent buffer overflows (bsc#1233555).\n- CVE-2024-53063: media: dvbdev: prevent the risk of out of memory access (bsc#1233557).\n- CVE-2024-53068: firmware: arm_scmi: Fix slab-use-after-free in scmi_bus_notifier() (bsc#1233561).\n- CVE-2024-53079: mm/thp: fix deferred split unqueue naming and locking (bsc#1233570).\n- CVE-2024-53088: i40e: fix race condition by adding filter's intermediate sync state (bsc#1233580).\n- CVE-2024-53104: media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format (bsc#1234025).\n- CVE-2024-53110: vp_vdpa: fix id_table array not null terminated error (bsc#1234085).\n\nThe following non-security bugs were fixed:\n\n- acpi: battery: Call power_supply_changed() when adding hooks (bsc#1232154)\n- acpi: battery: Simplify battery hook locking (bsc#1232154)\n- acpi: button: Add DMI quirk for Samsung Galaxy Book2 to fix initial lid detection issue (stable-fixes).\n- acpi: CPPC: Fix _CPC register setting issue (git-fixes).\n- acpi: CPPC: Make rmw_lock a raw_spin_lock (git-fixes).\n- acpi: EC: Do not release locks during operation region accesses (stable-fixes).\n- acpi: PAD: fix crash in exit_round_robin() (stable-fixes).\n- acpi: PRM: Clean up guid type in struct prm_handler_info (git-fixes).\n- acpi: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context (git-fixes).\n- acpi: resource: Add another DMI match for the TongFang GMxXGxx (stable-fixes).\n- acpi: resource: Add Asus ExpertBook B2502CVA to irq1_level_low_skip_override[] (stable-fixes).\n- acpi: resource: Add Asus Vivobook X1704VAP to irq1_level_low_skip_override[] (stable-fixes).\n- acpi: resource: Add LG 16T90SP to irq1_level_low_skip_override[] (stable-fixes).\n- acpica: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (stable-fixes).\n- acpica: Fix memory leak if acpi_ps_get_next_field() fails (stable-fixes).\n- acpica: Fix memory leak if acpi_ps_get_next_namepath() fails (stable-fixes).\n- acpica: iasl: handle empty connection_node (stable-fixes).\n- ad7780: fix division by zero in ad7780_write_raw() (git-fixes).\n- adapt same struct naming as similar kABI workaround in SLE15-SP6 (prefixed with 'suse_' to make it more obvious its a downstream thing.\n- add bug reference for a mana change (bsc#1229769).\n- add bug references to existing mana changes (bsc#1232033, bsc#1232034, bsc#1232036).\n- add bugreference to a hv_netvsc patch (bsc#1232413).\n- afs: Revert 'afs: Hide silly-rename files from userspace' (git-fixes).\n- alsa: 6fire: Release resources at card release (git-fixes).\n- alsa: ac97: bus: Fix the mistake in the comment (git-fixes).\n- alsa: asihpi: Fix potential OOB array access (stable-fixes).\n- alsa: caiaq: Use snd_card_free_when_closed() at disconnection (git-fixes).\n- alsa: core: add isascii() check to card ID generator (stable-fixes).\n- alsa: firewire-lib: Avoid division by zero in apply_constraint_to_size() (git-fixes).\n- alsa: firewire-lib: fix return value on fail in amdtp_tscm_init() (git-fixes).\n- alsa: hda: cs35l41: fix module autoloading (git-fixes).\n- alsa: hda: Fix kctl-\u003eid initialization (git-fixes).\n- alsa: hda/conexant - Fix audio routing for HP EliteOne 1000 G2 (stable-fixes).\n- alsa: hda/conexant - Use cached pin control for Node 0x1d on HP EliteOne 1000 G2 (git-fixes).\n- alsa: hda/conexant: Fix conflicting quirk for System76 Pangolin (git-fixes).\n- alsa: hda/cs8409: Fix possible NULL dereference (git-fixes).\n- alsa: hda/generic: Unconditionally prefer preferred_dacs pairs (git-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 - Fixed Clevo platform headset Mic issue (stable-fixes).\n- alsa: hda/realtek: Add a quirk for HP Pavilion 15z-ec200 (stable-fixes).\n- alsa: hda/realtek: Add quirk for Huawei MateBook 13 KLV-WX9 (stable-fixes).\n- alsa: hda/realtek: Add subwoofer quirk for Acer Predator G9-593 (stable-fixes).\n- alsa: hda/realtek: Fix headset mic on TUXEDO Gemini 17 Gen3 (stable-fixes).\n- alsa: hda/realtek: Fix headset mic on TUXEDO Stellaris 16 Gen6 mb1 (stable-fixes).\n- alsa: hda/realtek: fix mute/micmute LEDs for a HP EliteBook 645 G10 (stable-fixes).\n- alsa: hda/realtek: Fix the push button function for the ALC257 (git-fixes).\n- alsa: hda/realtek: Limit internal Mic boost on Dell platform (stable-fixes).\n- alsa: hda/realtek: Update ALC225 depop procedure (git-fixes).\n- alsa: hda/realtek: Update ALC256 depop procedure (git-fixes).\n- alsa: hda/realtek: Update default depop procedure (git-fixes).\n- alsa: hdsp: Break infinite MIDI input flush loop (stable-fixes).\n- alsa: line6: add hw monitor volume control to POD HD500X (stable-fixes).\n- alsa: mixer_oss: Remove some incorrect kfree_const() usages (git-fixes).\n- alsa: us122l: Use snd_card_free_when_closed() at disconnection (git-fixes).\n- alsa: usb-audio: Add delay quirk for VIVO USB-C HEADSET (stable-fixes).\n- alsa: usb-audio: Add input value sanity checks for standard types (stable-fixes).\n- alsa: usb-audio: Add logitech Audio profile quirk (stable-fixes).\n- alsa: usb-audio: Add native DSD support for Luxman D-08u (stable-fixes).\n- alsa: usb-audio: Add quirk for HP 320 FHD Webcam (stable-fixes).\n- alsa: usb-audio: Add quirks for Dell WD19 dock (stable-fixes).\n- alsa: usb-audio: Define macros for quirk table entries (stable-fixes).\n- alsa: usb-audio: Replace complex quirk lines with macros (stable-fixes).\n- alsa: usx2y: Use snd_card_free_when_closed() at disconnection (git-fixes).\n- amd-pstate: Set min_perf to nominal_perf for active mode performance gov (git-fixes).\n- arm64: cputype: Add Neoverse-N3 definitions (git-fixes)\n- arm64: dts: imx8mp: correct sdhc ipg clk (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: errata: Expand speculative SSBS workaround once more (git-fixes)\n- arm64: esr: Define ESR_ELx_EC_* constants as UL (git-fixes)\n- arm64: fix .data.rel.ro size assertion when CONFIG_LTO_CLANG (git-fixes)\n- arm64: Force position-independent veneers (git-fixes).\n- arm64: probes: Fix simulate_ldr*_literal() (git-fixes)\n- arm64: probes: Fix uprobes for big-endian kernels (git-fixes)\n- arm64: probes: Remove broken LDR (literal) uprobe support (git-fixes)\n- arm64: smccc: Remove broken support for SMCCCv1.3 SVE discard hint (git-fixes)\n- arm64: smccc: replace custom COUNT_ARGS() \u0026 CONCATENATE() (git-fixes)\n- arm64: tls: Fix context-switching of tpidrro_el0 when kpti is enabled (git-fixes)\n- arm64:uprobe fix the uprobe SWBP_INSN in big-endian (git-fixes)\n- arm64/sve: Discard stale CPU state when handling SVE traps (git-fixes)\n- asoc: allow module autoloading for table db1200_pids (stable-fixes).\n- asoc: amd: yc: Fix for enabling DMIC on acp6x via _DSD entry (git-fixes).\n- asoc: codecs: Fix atomicity violation in snd_soc_component_get_drvdata() (git-fixes).\n- asoc: codecs: lpass-rx-macro: add missing CDC_RX_BCL_VBAT_RF_PROC2 to default regs values (stable-fixes).\n- asoc: cs42l51: Fix some error handling paths in cs42l51_probe() (git-fixes).\n- asoc: fsl_sai: Enable 'FIFO continue on error' FCONT bit (stable-fixes).\n- asoc: imx-card: Set card.owner to avoid a warning calltrace if SND=m (git-fixes).\n- asoc: intel: fix module autoloading (stable-fixes).\n- asoc: qcom: Fix NULL Dereference in asoc_qcom_lpass_cpu_platform_probe() (git-fixes).\n- asoc: qcom: sm8250: add qrb4210-rb2-sndcard compatible string (stable-fixes).\n- asoc: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- asoc: soc-pcm: Do not zero TDM masks in __soc_pcm_open() (git-fixes).\n- asoc: stm32: spdifrx: fix dma channel release in stm32_spdifrx_remove (git-fixes).\n- asoc: tda7419: fix module autoloading (stable-fixes).\n- blk-throttle: Fix io statistics for cgroup v1 (bsc#1233528).\n- block: Avoid leaking hctx-\u003enr_active counter on batched completion (bsc#1231923).\n- block: print symbolic error name instead of error code (bsc#1231872).\n- bluetooth: bnep: fix wild-memory-access in proto_unregister (git-fixes).\n- bluetooth: btmrvl: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- bluetooth: btusb: Fix regression with fake CSR controllers 0a12:0001 (git-fixes).\n- bluetooth: Call iso_exit() on module unload (git-fixes).\n- bluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE (git-fixes).\n- bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs (git-fixes).\n- bluetooth: ISO: Fix multiple init when debugfs is disabled (git-fixes).\n- bluetooth: MGMT: Fix slab-use-after-free Read in set_powered_sync (git-fixes).\n- bluetooth: Remove debugfs directory on module init failure (git-fixes).\n- bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change (git-fixes).\n- bnxt_en: Fix the PCI-AER routines (git-fixes).\n- bnxt_en: refactor reset close code (git-fixes).\n- bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters() (git-fixes).\n- bnxt_en: Reserve rings after PCIe AER recovery if NIC interface is down (git-fixes).\n- bnxt_en: Reset PTP tx_avail after possible firmware reset (git-fixes).\n- bnxt_en: Restore PTP tx_avail count in case of skb_pad() error (git-fixes).\n- bnxt_en: Wait for FLR to complete during probe (git-fixes).\n- bpf, lsm: Add disabled BPF LSM hook list (git-fixes).\n- bpf, net: Fix a potential race in do_sock_getsockopt() (git-fixes).\n- bpf, verifier: Correct tail_call_reachable for bpf prog (git-fixes).\n- bpf, x64: Remove tail call detection (git-fixes).\n- bpf,perf: Fix perf_event_detach_bpf_prog error handling (git-fixes).\n- bpf: Add --skip_encoding_btf_inconsistent_proto, --btf_gen_optimized to pahole flags for v1.25 (bsc#1230414 bsc#1229450).\n- bpf: Allow helpers to accept pointers with a fixed size (git-fixes).\n- bpf: Check for helper calls in check_subprogs() (git-fixes).\n- bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos (git-fixes).\n- bpf: Fix bpf_strtol and bpf_strtoul helpers for 32bit (git-fixes).\n- bpf: Fix helper writes to read-only maps (git-fixes).\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- bpf: Fix tailcall cases in test_bpf (git-fixes).\n- bpf: Improve check_raw_mode_ok test for MEM_UNINIT-tagged types (git-fixes).\n- bpf: Remove truncation test in bpf_strtol and bpf_strtoul helpers (git-fixes).\n- bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error (git-fixes).\n- btf, scripts: Exclude Rust CUs with pahole (bsc#1230414 bsc#1229450).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- can: c_can: c_can_handle_bus_err(): update statistics if skb allocation fails (git-fixes).\n- can: c_can: fix {rx,tx}_errors statistics (git-fixes).\n- can: ems_usb: ems_usb_rx_err(): fix {rx,tx}_errors statistics (git-fixes).\n- can: ifi_canfd: ifi_canfd_handle_lec_err(): fix {rx,tx}_errors statistics (git-fixes).\n- can: j1939: j1939_session_new(): fix skb reference counting (git-fixes).\n- can: m_can: m_can_handle_lec_err(): fix {rx,tx}_errors statistics (git-fixes).\n- can: sun4i_can: sun4i_can_err(): call can_change_state() even if cf is NULL (git-fixes).\n- can: sun4i_can: sun4i_can_err(): fix {rx,tx}_errors statistics (git-fixes).\n- ceph: fix cap ref leak via netfs init_request (bsc#1231383).\n- cgroup/bpf: only cgroup v2 can be attached by bpf programs (bsc#1234108).\n- char: tpm: Fix possible memory leak in tpm_bios_measurements_open() (git-fixes).\n- chtls: fix tp-\u003ercv_tstamp initialization (git-fixes).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- comedi: Flush partial mappings in error case (git-fixes).\n- comedi: ni_routing: tools: Check when the file could not be opened (stable-fixes).\n- cpufreq/amd-pstate: Fix amd_pstate mode switch on shared memory systems (git-fixes).\n- crypto: bcm - add error check in the ahash_hmac_init function (git-fixes).\n- crypto: caam - add error check to caam_rsa_set_priv_key_form (git-fixes).\n- crypto: caam - Fix the pointer passed to caam_qi_shutdown() (git-fixes).\n- crypto: cavium - Fix an error handling path in cpt_ucode_load_fw() (git-fixes).\n- crypto: cavium - Fix the if condition to exit loop after timeout (git-fixes).\n- crypto: hisilicon - Remove pci_aer_clear_nonfatal_status() call (bsc#1232075)\n- crypto: hisilicon/qm - re-enable communicate interrupt before notifying PF (bsc#1232075)\n- crypto: inside-secure - Fix the return value of safexcel_xcbcmac_cra_init() (git-fixes).\n- crypto: x86/aegis128 - access 32-bit arguments as 32-bit (git-fixes).\n- cxgb4: add forgotten u64 ivlan cast before shift (git-fixes).\n- cxgb4: Properly lock TX queue for the selftest (git-fixes).\n- cxgb4: unnecessary check for 0 in the free_sge_txq_uld() function (git-fixes).\n- debugfs: fix automount d_fsdata usage (git-fixes).\n- dn_route: set rt neigh to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- drbd: Add NULL check for net_conf to prevent dereference in state validation (git-fixes).\n- drbd: Fix atomicity violation in drbd_uuid_set_bm() (git-fixes).\n- driver core: bus: Return -EIO instead of 0 when show/store invalid bus attribute (stable-fixes).\n- drivers: net: prevent tun_build_skb() to exceed the packet size limit (git-fixes).\n- drm: Consistently use struct drm_mode_rect for FB_DAMAGE_CLIPS (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm/amd: Fix initialization mistake for NBIO 7.7.0 (stable-fixes).\n- drm/amd: Guard against bad data for ATIF ACPI method (git-fixes).\n- drm/amd/amdgpu: Fix double unlock in amdgpu_mes_add_ring (git-fixes).\n- drm/amd/display: Add null check for 'afb' in amdgpu_dm_plane_handle_cursor_update (v2) (stable-fixes).\n- drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Check link_res-\u003ehpo_dp_link_enc before using it (bsc#1231944)\n- drm/amd/display: Check null pointer before dereferencing se (stable-fixes).\n- drm/amd/display: Check null pointers before using dc-\u003eclk_mgr (stable-fixes).\n- drm/amd/display: Check stream before comparing them (stable-fixes).\n- drm/amd/display: Fix index out of bounds in DCN30 color transformation (stable-fixes).\n- drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation (stable-fixes).\n- drm/amd/display: Fix index out of bounds in degamma hardware format translation (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix system hang while resume with TBT monitor (stable-fixes).\n- drm/amd/display: Handle null 'stream_status' in 'planes_changed_for_existing_stream' (stable-fixes).\n- drm/amd/display: Initialize get_bytes_per_element's default to 1 (stable-fixes).\n- drm/amd/display: Round calculated vtotal (stable-fixes).\n- drm/amd/display: Validate backlight caps are sane (stable-fixes).\n- drm/amd/pm: ensure the fw_info is not null before using it (stable-fixes).\n- drm/amdgpu: add missing size check in amdgpu_debugfs_gprwave_read() (stable-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: Adjust debugfs eviction and IB access permissions (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: prevent NULL pointer dereference if ATIF is not supported (git-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: Replace one-element array with flexible-array member (stable-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/bridge: anx7625: Drop EDID cache on bridge power off (git-fixes).\n- drm/bridge: tc358767: Fix link properties discovery (git-fixes).\n- drm/bridge: tc358768: Fix DSI command tx (git-fixes).\n- drm/etnaviv: Request pages from DMA32 zone on addressing_limited (git-fixes).\n- drm/imx/dcss: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- drm/mm: Mark drm_mm_interval_tree*() functions with __maybe_unused (git-fixes).\n- drm/msm: Allocate memory for disp snapshot with kvzalloc() (git-fixes).\n- drm/msm: Avoid NULL dereference in msm_disp_state_print_regs() (git-fixes).\n- drm/msm/adreno: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- drm/msm/dpu: cast crtc_clk calculation to u64 in _dpu_core_perf_calc_clk() (git-fixes).\n- drm/msm/dpu: do not always program merge_3d block (git-fixes).\n- drm/msm/dpu: make sure phys resources are properly initialized (git-fixes).\n- drm/msm/dsi: fix 32-bit signed integer extension in pclk_rate calculation (git-fixes).\n- drm/omap: Fix locking in omap_gem_new_dmabuf() (git-fixes).\n- drm/omap: Fix possible NULL dereference (git-fixes).\n- drm/panfrost: Remove unused id_mask from struct panfrost_model (git-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon: Fix encoder-\u003epossible_clones (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/radeon: Replace one-element array with flexible-array member (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/rockchip: define gamma registers for RK3399 (stable-fixes).\n- drm/rockchip: support gamma control on RK3399 (stable-fixes).\n- drm/rockchip: vop: Fix a dereferenced before check warning (git-fixes).\n- drm/sched: Add locking to drm_sched_entity_modify_sched (git-fixes).\n- drm/sti: avoid potential dereference of error pointers (git-fixes).\n- drm/sti: avoid potential dereference of error pointers in sti_gdp_atomic_check (git-fixes).\n- drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check (git-fixes).\n- drm/v3d: Address race-condition in MMU flush (git-fixes).\n- drm/v3d: Stop the active perfmon before being destroyed (git-fixes).\n- drm/vboxvideo: Replace fake VLA at end of vbva_mouse_pointer_shape with real VLA (stable-fixes).\n- drm/vc4: hvs: Do not write gamma luts on 2711 (git-fixes).\n- drm/vc4: hvs: Fix dlist debug not resetting the next entry pointer (git-fixes).\n- drm/vc4: hvs: Remove incorrect limit from hvs_dlist debugfs function (git-fixes).\n- drm/vc4: Stop the active perfmon before being destroyed (git-fixes).\n- drm/vmwgfx: Handle surface check failure correctly (git-fixes).\n- drm/vmwgfx: Limit display layout ioctl array size to VMWGFX_NUM_DISPLAY_UNITS (stable-fixes).\n- drop HD-audio conexant patch that caused a regression on Thinkpad (bsc#1228269)\n- Drop OCFS2 patch causing a regression (bsc#1233255) \n- drop USB dwc2 patch that caused a regression on RPi3 (bsc#1232342)\n- e1000e: Fix S0ix residency on corporate systems (git-fixes).\n- efi/memattr: Ignore table if the size is clearly bogus (bsc#1231465).\n- efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption (stable-fixes).\n- erofs: avoid consecutive detection for Highmem memory (git-fixes).\n- erofs: avoid infinite loop in z_erofs_do_read_page() when reading beyond EOF (git-fixes).\n- erofs: fix pcluster use-after-free on UP platforms (git-fixes).\n- erofs: fix potential overflow calculating xattr_isize (git-fixes).\n- erofs: stop parsing non-compact HEAD index if clusterofs is invalid (git-fixes).\n- eth: bnxt: fix counting packets discarded due to OOM and netpoll (git-fixes).\n- exportfs: use pr_debug for unreachable debug statements (git-fixes).\n- ext4: fix slab-use-after-free in ext4_split_extent_at() (bsc#1232201)\n- fat: fix uninitialized variable (git-fixes).\n- fbdev: pxafb: Fix possible use after free in pxafb_task() (stable-fixes).\n- fbdev: sisfb: Fix strbuf array overflow (stable-fixes).\n- fgraph: Change the name of cpuhp state to 'fgraph:online' (git-fixes).\n- fgraph: Fix missing unlock in register_ftrace_graph() (git-fixes).\n- fgraph: Use CPU hotplug mechanism to initialize idle shadow stacks (git-fixes).\n- filelock: fix potential use-after-free in posix_lock_inode (git-fixes).\n- firmware: google: Unregister driver_info on failure (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- Fix regression on AMDGPU driver (bsc#1233134) \n- fs: Fix file_set_fowner LSM hook inconsistencies (git-fixes).\n- fs/namespace: fnic: Switch to use %ptTd (git-fixes).\n- fs/pipe: Fix lockdep false-positive in watchqueue pipe_write() (git-fixes).\n- genirq/msi: Fix off-by-one error in msi_domain_alloc() (git-fixes).\n- goldfish: Fix unused const variable 'goldfish_pipe_acpi_match' (git-fixes).\n- gpio: aspeed: Add the flush write to ensure the write complete (git-fixes).\n- gpio: aspeed: Use devm_clk api to manage clock source (git-fixes).\n- gpio: davinci: fix lazy disable (git-fixes).\n- gve: Fix an edge case for TSO skb validity check (git-fixes).\n- gve: Fix skb truesize underestimation (git-fixes).\n- gve: Fix XDP TX completion handling when counters overflow (git-fixes).\n- gve: ignore nonrelevant GSO type bits when processing TSO headers (git-fixes).\n- hid: amd_sfh: Switch to device-managed dmam_alloc_coherent() (git-fixes).\n- hid: core: zero-initialize the report buffer (git-fixes).\n- hid: intel-ish-hid: Fix uninitialized variable 'rv' in ish_fw_xfer_direct_dma (git-fixes).\n- hid: lenovo: Add support for Thinkpad X1 Tablet Gen 3 keyboard (stable-fixes).\n- hid: multitouch: Add quirk for HONOR MagicBook Art 14 touchpad (stable-fixes).\n- hid: multitouch: Add quirk for Logitech Bolt receiver w/ Casa touchpad (stable-fixes).\n- hid: multitouch: Add support for B2402FVA track point (stable-fixes).\n- hid: multitouch: Add support for GT7868Q (stable-fixes).\n- hid: multitouch: Add support for Thinkpad X12 Gen 2 Kbd Portfolio (stable-fixes).\n- hid: plantronics: Workaround for an unexcepted opposite volume key (stable-fixes).\n- hid: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- hid: wacom: fix when get product name maybe null pointer (git-fixes).\n- hid: wacom: Interpret tilt data from Intuos Pro BT as signed values (git-fixes).\n- hv_netvsc: Fix VF namespace also in synthetic NIC NETDEV_REGISTER event (git-fixes).\n- hv_sock: Initializing vsk-\u003etrans to NULL to prevent a dangling pointer (git-fixes).\n- hwmon: (adm9240) Add missing dependency on REGMAP_I2C (git-fixes).\n- hwmon: (tmp513) Add missing dependency on REGMAP_I2C (git-fixes).\n- hwmon: (tps23861) Fix reporting of negative temperatures (git-fixes).\n- i2c: i801: Use a different adapter-name for IDF adapters (stable-fixes).\n- i2c: imx-lpi2c: return -EINVAL when i2c peripheral clk does not work (bsc#1227885).\n- i2c: imx-lpi2c: use bulk clk API (bsc#1227885).\n- i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume (git-fixes).\n- i2c: xiic: Fix broken locking on tx_msg (stable-fixes).\n- i2c: xiic: Fix pm_runtime_set_suspended() with runtime pm enabled (git-fixes).\n- i2c: xiic: Fix RX IRQ busy check (stable-fixes).\n- i2c: xiic: improve error message when transfer fails to start (stable-fixes).\n- i2c: xiic: Switch from waitqueue to completion (stable-fixes).\n- i2c: xiic: Try re-initialization on bus busy timeout (git-fixes).\n- i2c: xiic: Use devm_clk_get_enabled() (stable-fixes).\n- i2c: xiic: xiic_xfer(): Fix runtime PM leak on error path (git-fixes).\n- i3c: master: Fix miss free init_dyn_addr at i3c_master_put_i3c_addrs() (git-fixes).\n- i40e: avoid double calling i40e_pf_rxq_wait() (git-fixes).\n- i40e: disable NAPI right after disabling irqs when handling xsk_pool (git-fixes).\n- i40e: Fix filter input checks to prevent config with invalid values (git-fixes).\n- i40e: fix use-after-free in i40e_aqc_add_filters() (git-fixes).\n- i40e: Fix waiting for queues of all VSIs to be disabled (git-fixes).\n- i40e: Fix XDP program unloading while removing the driver (git-fixes).\n- i40e: Report MFS in decimal base instead of hex (git-fixes).\n- i40e: Restore VF MSI-X state during PCI reset (git-fixes).\n- i40e: take into account XDP Tx queues when stopping rings (git-fixes).\n- iavf: do not process adminq tasks when __IAVF_IN_REMOVE_TASK is set (git-fixes).\n- iavf: fix FDIR rule fields masks validation (git-fixes).\n- iavf: Fix promiscuous mode configuration flow messages (git-fixes).\n- iavf: Fix TC config comparison with existing adapter TC config (git-fixes).\n- iavf: in iavf_down, disable queues when removing the driver (git-fixes).\n- iavf: initialize waitqueues before starting watchdog_task (git-fixes).\n- iavf: Introduce new state machines for flow director (git-fixes).\n- iavf: send VLAN offloading caps once after VFR (git-fixes).\n- iavf: validate tx_coalesce_usecs even if rx_coalesce_usecs is zero (git-fixes).\n- ibmvnic: Do partial reset on login failure (bsc#1233150).\n- ibmvnic: Enforce stronger sanity checks on login response (bsc#1233150).\n- ibmvnic: Ensure login failure recovery is safe from other resets (bsc#1233150).\n- ibmvnic: Handle DMA unmapping of login buffs in release functions (bsc#1233150).\n- ibmvnic: Unmap DMA login rsp buffer on send login fail (bsc#1233150).\n- ice: avoid executing commands on other ports when driving sync (git-fixes).\n- ice: Block switchdev mode when ADQ is active and vice versa (git-fixes).\n- ice: change q_index variable type to s16 to store -1 value (git-fixes).\n- ice: fix accounting for filters shared by multiple VSIs (git-fixes).\n- ice: fix accounting if a VLAN already exists (git-fixes).\n- ice: fix ICE_LAST_OFFSET formula (git-fixes).\n- ice: Fix link_down_on_close message (git-fixes).\n- ice: Fix netif_is_ice() in Safe Mode (git-fixes).\n- ice: Fix NULL pointer deref during VF reset (git-fixes).\n- ice: fix over-shifted variable (git-fixes).\n- ice: fix receive buffer size miscalculation (git-fixes).\n- ice: fix VLAN replay after reset (git-fixes).\n- ice: Fix VSI list rule with ICE_SW_LKUP_LAST type (git-fixes).\n- ice: ice_aq_check_events: fix off-by-one check when filling buffer (git-fixes).\n- ice: Interpret .set_channels() input differently (git-fixes).\n- ice: reset first in crash dump kernels (git-fixes).\n- ice: respect netif readiness in AF_XDP ZC related ndo's (git-fixes).\n- ice: Shut down VSI with 'link-down-on-close' enabled (git-fixes).\n- ice: tc: allow zero flags in parsing tc flower (git-fixes).\n- ice: Unbind the workqueue (bsc#1231344).\n- ice: virtchnl: stop pretending to support RSS over AQ or registers (git-fixes).\n- idpf: avoid compiler introduced padding in virtchnl2_rss_key struct (git-fixes).\n- idpf: avoid compiler padding in virtchnl2_ptype struct (git-fixes).\n- idpf: disable local BH when scheduling napi for marker packets (git-fixes).\n- idpf: distinguish vports by the dev_port attribute (git-fixes).\n- idpf: do not enable NAPI and interrupts prior to allocating Rx buffers (git-fixes).\n- idpf: fix corrupted frames and skb leaks in singleq mode (git-fixes).\n- idpf: fix memleak in vport interrupt configuration (git-fixes).\n- idpf: fix memory leaks and crashes while performing a soft reset (git-fixes).\n- idpf: fix UAFs when destroying the queues (git-fixes).\n- idpf: Interpret .set_channels() input differently (git-fixes).\n- igb: Always call igb_xdp_ring_update_tail() under Tx lock (git-fixes).\n- igb: extend PTP timestamp adjustments to i211 (git-fixes).\n- igb: Fix missing time sync events (git-fixes).\n- igb: Fix not clearing TimeSync interrupts for 82580 (git-fixes).\n- igc: Check VLAN EtherType mask (git-fixes).\n- igc: Check VLAN TCI mask (git-fixes).\n- igc: Fix hicredit calculation (git-fixes).\n- igc: Fix missing time sync events (git-fixes).\n- igc: Remove temporary workaround (git-fixes).\n- igc: Report VLAN EtherType matching back to user (git-fixes).\n- igc: Unlock on error in igc_io_resume() (git-fixes).\n- iio: adc: ad7124: fix division by zero in ad7124_set_channel_odr() (git-fixes).\n- iio: adc: ad7606: Fix typo in the driver name (git-fixes).\n- iio: adc: ad7923: Fix buffer overflow for tx_buf and ring_xfer (git-fixes).\n- iio: dac: ad5770r: add missing select REGMAP_SPI in Kconfig (git-fixes).\n- iio: dac: ltc1660: add missing select REGMAP_SPI in Kconfig (git-fixes).\n- iio: dac: stm32-dac-core: add missing select REGMAP_MMIO in Kconfig (git-fixes).\n- iio: hid-sensors: Fix an error handling path in _hid_sensor_set_report_latency() (git-fixes).\n- iio: light: al3010: Fix an error handling path in al3010_probe() (git-fixes).\n- iio: light: opt3001: add missing full-scale range value (git-fixes).\n- iio: light: veml6030: fix ALS sensor resolution (git-fixes).\n- iio: light: veml6030: fix IIO device retrieval from embedded device (git-fixes).\n- iio: light: veml6030: fix microlux value calculation (git-fixes).\n- iio: proximity: mb1232: add missing select IIO_(TRIGGERED_)BUFFER in Kconfig (git-fixes).\n- initramfs: avoid filename buffer overrun (bsc#1232436).\n- input: adp5589-keys - fix adp5589_gpio_get_value() (git-fixes).\n- input: adp5589-keys - fix NULL pointer dereference (git-fixes).\n- input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- input: goodix - use the new soc_intel_is_byt() helper (stable-fixes).\n- input: i8042 - add another board name for TUXEDO Stellaris Gen5 AMD line (git-fixes).\n- input: i8042 - add Ayaneo Kun to i8042 quirk table (git-fixes).\n- input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (git-fixes).\n- input: i8042 - add TUXEDO Stellaris 15 Slim Gen6 AMD to i8042 quirk table (git-fixes).\n- input: i8042 - add TUXEDO Stellaris 16 Gen5 AMD to i8042 quirk table (git-fixes).\n- input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- iommu/vt-d: Always reserve a domain ID for identity setup (git-fixes).\n- ipv6: blackhole_netdev needs snmp6 counters (bsc#1216813).\n- ipv6: give an IPv6 dev to blackhole_netdev (bsc#1216813).\n- irqchip/gic-v3-its: Avoid explicit cpumask allocation on stack (git-fixes).\n- irqchip/gic-v3-its: Fix VSYNC referencing an unmapped VPE on GIC v4.1 (git-fixes).\n- itco_wdt: mask NMI_NOW bit for update_no_reboot_bit() call (git-fixes).\n- ixgbe: {dis, en}able irqs in ixgbe_txrx_ring_{dis, en}able (git-fixes).\n- ixgbe: avoid sleeping allocation in ixgbe_ipsec_vf_add_sa() (git-fixes).\n- ixgbe: fix crash with empty VF macvlan list (git-fixes).\n- ixgbe: fix timestamp configuration code (git-fixes).\n- jfs: check if leafidx greater than num leaves per dmap tree (git-fixes).\n- jfs: Fix sanity check in dbMount (git-fixes).\n- jfs: Fix uaf in dbFreeBits (git-fixes).\n- jfs: Fix uninit-value access of new_ea in ea_buffer (git-fixes).\n- jfs: UBSAN: shift-out-of-bounds in dbFindBits (git-fixes).\n- kab: fix after net: add more sanity check in virtio_net_hdr_to_skb() (git-fixes).\n- kabi fix of KVM: arm64: Preserve PSTATE.SS for the guest while single-step is enabled (git-fixes).\n- kABI: bpf: enum bpf_{type_flag,arg_type} kABI workaround (git-fixes).\n- kABI: bpf: struct bpf_func_proto kABI workaround (git-fixes).\n- kabi: fix after kvm: add guest_state_{enter,exit}_irqoff() (git-fixes).\n- kabi: fix after KVM: arm64: mixed-width check should be skipped for uninitialized vCPUs (git-fixes).\n- kabi: Restore exported __arm_smccc_sve_check (git-fixes)\n- kbuild, bpf: Use test-ge check for v1.25-only pahole (bsc#1230414 bsc#1229450).\n- kbuild,bpf: Add module-specific pahole flags for distilled base BTF (bsc#1230414 bsc#1229450).\n- kbuild,bpf: Switch to using --btf_features for pahole v1.26 and later (bsc#1230414 bsc#1229450).\n- kbuild: add test-{ge,gt,le,lt} macros (bsc#1230414 bsc#1229450).\n- kbuild: avoid too many execution of scripts/pahole-flags.sh (bsc#1230414 bsc#1229450).\n- kbuild: bpf: Tell pahole to DECL_TAG kfuncs (bsc#1230414 bsc#1229450).\n- kernel-binary: Enable livepatch package only when livepatch is enabled Otherwise the filelist may be empty failing the build (bsc#1218644).\n- kernel.h: split out COUNT_ARGS() and CONCATENATE() to args.h (git-fixes)\n- kexec: fix a memory leak in crash_shrink_memory() (git-fixes).\n- kvm: add guest_state_{enter,exit}_irqoff() (git-fixes).\n- kvm: Add support for arch compat vm ioctls (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: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- kvm: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- kvm: arm64: mixed-width check should be skipped for uninitialized vCPUs (git-fixes).\n- kvm: arm64: Preserve PSTATE.SS for the guest while single-step is enabled (git-fixes).\n- kvm: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (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: Check for non-NULL vCPU in vgic_v2_parse_attr() (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: eventfd: Fix false positive RCU usage warning (git-fixes).\n- kvm: Fix coalesced_mmio_has_room() to avoid premature userspace exit (git-fixes).\n- kvm: Fix lockdep false negative during host resume (git-fixes).\n- kvm: fix memoryleak in kvm_init() (git-fixes).\n- kvm: Grab a reference to KVM for VM and vCPU stats file descriptors (git-fixes).\n- kvm: Optimize kvm_make_vcpus_request_mask() a bit (git-fixes).\n- kvm: PPC: Book3S HV: remove unused varible (bsc#1194869).\n- kvm: Pre-allocate cpumasks for kvm_make_all_cpus_request_except() (git-fixes).\n- kvm: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- kvm: s390: Change virtual to physical address access in diag 0x258 handler (git-fixes bsc#1232631).\n- kvm: s390: Fix SORTL and DFLTCC instruction format error in __insn32_query (git-fixes bsc#1231277).\n- kvm: s390: gaccess: Check if guest address is in memslot (git-fixes bsc#1232630).\n- kvm: SVM: Disallow guest from changing userspace's MSR_AMD64_DE_CFG value (git-fixes).\n- kvm: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- kvm: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- kvm: Unconditionally get a ref to /dev/kvm module when creating a VM (git-fixes).\n- kvm: Write the per-page 'segment' when clearing (part of) a guest page (git-fixes).\n- kvm: x86: Use a stable condition around all VT-d PI paths (git-fixes).\n- kvm: x86/mmu: Fold rmap_recycle into rmap_add (git-fixes).\n- kvm: x86/mmu: Rename slot_handle_leaf to slot_handle_level_4k (git-fixes).\n- kvm/arm64: rework guest entry logic (git-fixes).\n- mac80211: MAC80211_MESSAGE_TRACING should depend on TRACING (git-fixes).\n- Makefile.compiler: replace cc-ifversion with compiler-specific macros (bsc#1230414 bsc#1229450).\n- media: adv7604: prevent underflow condition when reporting colorspace (git-fixes).\n- media: cx24116: prevent overflows on SNR calculus (git-fixes).\n- media: dvb_frontend: do not play tricks with underflow values (git-fixes).\n- media: dvb-usb-v2: af9035: fix missing unlock (git-fixes).\n- media: dvb-usb-v2: af9035: Fix null-ptr-deref in af9035_i2c_master_xfer (stable-fixes).\n- media: dvbdev: prevent the risk of out of memory access (git-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: pulse8-cec: fix data timestamp at pulse8_setup() (git-fixes).\n- media: stb0899_algo: initialize cfr before using it (git-fixes).\n- media: v4l2-ctrls-api: fix error handling for v4l2_g_ctrl() (git-fixes).\n- media: v4l2-tpg: prevent the risk of a division by zero (git-fixes).\n- media: videobuf2-core: clear memory related fields in __vb2_plane_dmabuf_put() (stable-fixes).\n- mei: use kvmalloc for read buffer (git-fixes).\n- misc: apds990x: Fix missing pm_runtime_disable() (git-fixes).\n- mm/hugetlb: fix nodes huge page allocation when there are surplus pages (bsc#1234012).\n- mm/memory: add non-anonymous page check in the copy_present_page() (bsc#1231646).\n- modpost: remove incorrect code in do_eisa_entry() (git-fixes).\n- module: abort module loading when sysfs setup suffer errors (git-fixes).\n- nbd: fix race between timeout and normal completion (bsc#1230918).\n- net: add more sanity check in virtio_net_hdr_to_skb() (git-fixes).\n- net: ena: Fix potential sign extension issue (git-fixes).\n- net: ena: Remove ena_select_queue (git-fixes).\n- net: ena: Wrong missing IO completions check order (git-fixes).\n- net: mana: Implement get_ringparam/set_ringparam for mana (bsc#1229891).\n- net: mana: Improve mana_set_channels() in low mem conditions (bsc#1230289).\n- net: qede: use return from qede_parse_flow_attr() for flow_spec (git-fixes).\n- net: relax socket state check at accept time (git-fixes).\n- net: socket: suppress unused warning (git-fixes).\n- net: test for not too small csum_start in virtio_net_hdr_to_skb() (git-fixes).\n- net: usb: lan78xx: Fix memory leak on device unplug by freeing PHY device (git-fixes).\n- net: usb: lan78xx: Fix refcounting and autosuspend on invalid WoL configuration (git-fixes).\n- net: usb: qmi_wwan: add Fibocom FG132 0x0112 composition (stable-fixes).\n- net: usb: usbnet: fix name regression (git-fixes).\n- net: usb: usbnet: fix race in probe failure (git-fixes).\n- net/mlx5: Add missing masks and QoS bit masks for scheduling elements (git-fixes).\n- net/mlx5: Added cond_resched() to crdump collection (git-fixes).\n- net/mlx5: Allow 0 for total host VFs (git-fixes).\n- net/mlx5: Correctly compare pkt reformat ids (git-fixes).\n- net/mlx5: DR, Can't go to uplink vport on RX rule (git-fixes).\n- net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx (git-fixes).\n- net/mlx5: DR, Use the right GVMI number for drop action (git-fixes).\n- net/mlx5: Drain health before unregistering devlink (git-fixes).\n- net/mlx5: E-switch, register event handler before arming the event (git-fixes).\n- net/mlx5: Explicitly set scheduling element and TSAR type (git-fixes).\n- net/mlx5: Fix fw tracer first block check (git-fixes).\n- net/mlx5: fix potential memory leak in mlx5e_init_rep_rx (git-fixes).\n- net/mlx5: fs, lock FTE when checking if active (git-fixes).\n- net/mlx5: Handle fw tracer change ownership event based on MTRC (git-fixes).\n- net/mlx5: LAG, Check correct bucket when modifying LAG (git-fixes).\n- net/mlx5: Lag, do bond only if slaves agree on roce state (git-fixes).\n- net/mlx5: Lag, do not use the hardcoded value of the first port (git-fixes).\n- net/mlx5: Lag, restore buckets number to default after hash LAG deactivation (git-fixes).\n- net/mlx5: Skip clock update work when device is in error state (git-fixes).\n- net/mlx5: Unregister notifier on eswitch init failure (git-fixes).\n- net/mlx5: Update the list of the PCI supported devices (git-fixes).\n- net/mlx5: Use mlx5 device constant for selecting CQ period mode for ASO (git-fixes).\n- net/mlx5: Use recovery timeout on sync reset flow (git-fixes).\n- net/mlx5: Use RMW accessors for changing LNKCTL (git-fixes).\n- net/mlx5e: Add a check for the return value from mlx5_port_set_eth_ptys (git-fixes).\n- net/mlx5e: Add missing link modes to ptys2ethtool_map (git-fixes).\n- net/mlx5e: Add mqprio_rl cleanup and free in mlx5e_priv_cleanup() (git-fixes).\n- net/mlx5e: Again mutually exclude RX-FCS and RX-port-timestamp (git-fixes).\n- net/mlx5e: Allow software parsing when IPsec crypto is enabled (git-fixes).\n- net/mlx5e: Change the warning when ignore_flow_level is not supported (git-fixes).\n- net/mlx5e: Check return value of snprintf writing to fw_version buffer (git-fixes).\n- net/mlx5e: Check return value of snprintf writing to fw_version buffer for representors (git-fixes).\n- net/mlx5e: Correct snprintf truncation handling for fw_version buffer (git-fixes).\n- net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by representors (git-fixes).\n- net/mlx5e: Correctly report errors for ethtool rx flows (git-fixes).\n- net/mlx5e: CT: Fix null-ptr-deref in add rule err flow (git-fixes).\n- net/mlx5e: Do not offload internal port if filter device is out device (git-fixes).\n- net/mlx5e: fix a potential double-free in fs_udp_create_groups (git-fixes).\n- net/mlx5e: Fix crash moving to switchdev mode when ntuple offload is set (git-fixes).\n- net/mlx5e: fix double free in macsec_fs_tx_create_crypto_table_groups (git-fixes).\n- net/mlx5e: fix double free of encap_header (git-fixes).\n- net/mlx5e: Fix features validation check for tunneled UDP (non-VXLAN) packets (git-fixes).\n- net/mlx5e: Fix IPsec tunnel mode offload feature check (git-fixes).\n- net/mlx5e: Fix pedit endianness (git-fixes).\n- net/mlx5e: Fix possible deadlock on mlx5e_tx_timeout_work (git-fixes).\n- net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer() (git-fixes).\n- net/mlx5e: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list() (git-fixes).\n- net/mlx5e: Fix UDP GSO for encapsulated packets (git-fixes).\n- net/mlx5e: HTB, Fix inconsistencies with QoS SQs number (git-fixes).\n- net/mlx5e: kTLS, Fix incorrect page refcounting (git-fixes).\n- net/mlx5e: Move representor neigh cleanup to profile cleanup_tx (git-fixes).\n- net/mlx5e: Reduce the size of icosq_str (git-fixes).\n- net/mlx5e: Take state lock during tx timeout reporter (git-fixes).\n- net/mlx5e: Use rx_missed_errors instead of rx_dropped for reporting buffer exhaustion (git-fixes).\n- net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX (bsc#1226797)\n- netdevsim: use cond_resched() in nsim_dev_trap_report_work() (git-fixes).\n- nfs: Avoid unnecessary rescanning of the per-server delegation list (git-fixes).\n- nfs: Fix KMSAN warning in decode_getfattr_attrs() (git-fixes).\n- nfs: fix memory leak in error path of nfs4_do_reclaim (git-fixes).\n- nfsd: call cache_put if xdr_reserve_space returns NULL (git-fixes).\n- nfsd: fix delegation_blocked() to block correctly for at least 30 seconds (git-fixes).\n- nfsd: Fix NFSv4's PUTPUBFH operation (git-fixes).\n- nfsd: fix refcount leak when file is unhashed after being found (git-fixes).\n- nfsd: map the EBADMSG to nfserr_io to avoid warning (git-fixes).\n- nfsd: Mark filecache 'down' if init fails (git-fixes).\n- nfsd: remove unneeded EEXIST error check in nfsd_do_file_acquire (git-fixes).\n- nfsd: return -EINVAL when namelen is 0 (git-fixes).\n- nfsv3: only use NFS timeout for MOUNT when protocols are compatible (bsc#1231016).\n- nfsv4: Fix clearing of layout segments in layoutreturn (git-fixes).\n- nilfs2: fix kernel bug due to missing clearing of buffer delay flag (git-fixes).\n- nouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error (git-fixes).\n- ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() (git-fixes).\n- ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition (stable-fixes).\n- nvme-fabrics: fix kernel crash while shutting down controller (git-fixes).\n- nvme-multipath: system fails to create generic nvme device (git-fixes).\n- nvme-pci: fix freeing of the HMB descriptor table (git-fixes).\n- nvme-pci: qdepth 1 quirk (git-fixes).\n- nvme-pci: reverse request order in nvme_queue_rqs (git-fixes).\n- nvmet-auth: assign dh_key to NULL after kfree_sensitive (git-fixes).\n- ocfs2: fix the la space leak when unmounting an ocfs2 volume (git-fixes).\n- ocfs2: fix uninit-value in ocfs2_get_block() (git-fixes).\n- ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow (git-fixes).\n- ocfs2: remove entry once instead of null-ptr-dereference in ocfs2_xa_remove() (git-fixes).\n- parport: Proper fix for array out-of-bounds access (git-fixes).\n- pci: Add ACS quirk for Qualcomm SA8775P (stable-fixes).\n- pci: Add function 0 DMA alias quirk for Glenfly Arise chip (stable-fixes).\n- pci: Add T_PVPERL macro (git-fixes).\n- pci: endpoint: Clear secondary (not primary) EPC in pci_epc_remove_epf() (git-fixes).\n- pci: Fix pci_enable_acs() support for the ACS quirks (bsc#1229019).\n- pci: Fix reset_method_store() memory leak (git-fixes).\n- pci: j721e: Deassert PERST# after a delay of PCIE_T_PVPERL_MS milliseconds (git-fixes).\n- pci: keystone: Add link up check to ks_pcie_other_map_bus() (git-fixes).\n- pci: keystone: Set mode as Root Complex for 'ti,keystone-pcie' compatible (git-fixes).\n- pci: Mark Creative Labs EMU20k2 INTx masking as broken (stable-fixes).\n- pci: rockchip-ep: Fix address translation unit programming (git-fixes).\n- phy: tegra: xusb: Add error pointer check in xusb.c (git-fixes).\n- platform/chrome: cros_ec_typec: fix missing fwnode reference decrement (git-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86: dell-sysman: add support for alienware products (stable-fixes).\n- platform/x86: dell-wmi: Ignore suspend notifications (stable-fixes).\n- platform/x86: touchscreen_dmi: add nanote-next quirk (stable-fixes).\n- posix-cpu-timers: Clear TICK_DEP_BIT_POSIX_TIMER on clone (bsc#1234098).\n- power: reset: brcmstb: Do not go into infinite loop if reset fails (stable-fixes).\n- power: supply: bq27xxx: Fix registers of bq27426 (git-fixes).\n- power: supply: core: Remove might_sleep() from power_supply_put() (git-fixes).\n- powerpc: Allow clearing and restoring registers independent of saved breakpoint state (bsc#1194869).\n- powerpc: remove GCC version check for UPD_CONSTR (bsc#1194869).\n- powerpc/64: Convert patch_instruction() to patch_u32() (bsc#1194869).\n- powerpc/asm: Remove UPD_CONSTR after GCC 4.9 removal (bsc#1194869).\n- powerpc/atomic: Use YZ constraints for DS-form instructions (bsc#1194869).\n- powerpc/boot: Handle allocation failure in simple_realloc() (bsc#1194869).\n- powerpc/boot: Only free if realloc() succeeds (bsc#1194869).\n- powerpc/code-patching: Add generic memory patching (bsc#1194869).\n- powerpc/code-patching: Consolidate and cache per-cpu patching context (bsc#1194869).\n- powerpc/code-patching: Do not call is_vmalloc_or_module_addr() without CONFIG_MODULES (bsc#1194869).\n- powerpc/code-patching: Fix error handling in do_patch_instruction() (bsc#1194869).\n- powerpc/code-patching: Fix oops with DEBUG_VM enabled (bsc#1194869).\n- powerpc/code-patching: Fix unmap_patch_area() error handling (bsc#1194869).\n- powerpc/code-patching: introduce patch_instructions() (bsc#1194869).\n- powerpc/code-patching: Perform hwsync in __patch_instruction() in case of failure (bsc#1194869).\n- powerpc/code-patching: Pre-map patch area (bsc#1194869).\n- powerpc/code-patching: Remove #ifdef CONFIG_STRICT_KERNEL_RWX (bsc#1194869).\n- powerpc/code-patching: Remove pr_debug()/pr_devel() messages and fix check() (bsc#1194869).\n- powerpc/code-patching: Reorganise do_patch_instruction() to ease error handling (bsc#1194869).\n- powerpc/code-patching: Speed up page mapping/unmapping (bsc#1194869).\n- powerpc/code-patching: Use jump_label to check if poking_init() is done (bsc#1194869).\n- powerpc/code-patching: Use temporary mm for Radix MMU (bsc#1194869).\n- powerpc/code-patching: Use WARN_ON and fix check in poking_init (bsc#1194869).\n- powerpc/ftrace: Use patch_instruction() return directly (bsc#1194869).\n- powerpc/imc-pmu: Fix use of mutex in IRQs disabled section (bsc#1054914 git-fixes).\n- powerpc/imc-pmu: Use the correct spinlock initializer (bsc#1054914 git-fixes).\n- powerpc/inst: Refactor ___get_user_instr() (bsc#1194869).\n- powerpc/kexec: Fix return of uninitialized variable (bsc#1194869).\n- powerpc/lib: Add __init attribute to eligible functions (bsc#1194869).\n- powerpc/mm: Fix boot crash with FLATMEM (bsc#1194869).\n- powerpc/mm: Fix boot warning with hugepages and CONFIG_DEBUG_VIRTUAL (bsc#1194869).\n- powerpc/mm/fault: Fix kfence page fault reporting (bsc#1194869).\n- powerpc/powernv: Free name on error in opal_event_init() (bsc#1194869).\n- powerpc/pseries: Fix dtl_access_lock to be a rw_semaphore (bsc#1194869).\n- powerpc/pseries: Fix KVM guest detection for disabling hardlockup detector (bsc#1194869).\n- powerpc/tlb: Add local flush for page given mm_struct and psize (bsc#1194869).\n- powerpc/vdso: augment VDSO32 functions to support 64 bits build (bsc#1194869).\n- powerpc/vdso: Fix VDSO data access when running in a non-root time namespace (bsc#1194869).\n- powerpc/vdso: Merge vdso64 and vdso32 into a single directory (bsc#1194869).\n- powerpc/vdso: Rework VDSO32 makefile to add a prefix to object files (bsc#1194869).\n- powerpc/xics: Check return value of kasprintf in icp_native_map_one_cpu (bsc#1194869).\n- powerpc/xmon: Fix disassembly CPU feature checks (bsc#1065729).\n- qed: avoid truncating work queue length (git-fixes).\n- rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow (bsc#1226631).\n- rcu: Add rcutree.nohz_full_patience_delay to reduce nohz_full (bsc#1231327)\n- rdma/bnxt_re: Add a check for memory allocation (git-fixes)\n- rdma/bnxt_re: Check cqe flags to know imm_data vs inv_irkey (git-fixes)\n- rdma/bnxt_re: Fix a bug while setting up Level-2 PBL pages (git-fixes)\n- rdma/bnxt_re: Fix incorrect AVID type in WQE structure (git-fixes)\n- rdma/bnxt_re: Fix the GID table length (git-fixes)\n- rdma/bnxt_re: Fix the max CQ WQEs for older adapters (git-fixes)\n- rdma/bnxt_re: Fix the usage of control path spin locks (git-fixes)\n- rdma/bnxt_re: Return more meaningful error (git-fixes)\n- rdma/bnxt_re: synchronize the qp-handle table array (git-fixes)\n- rdma/cxgb4: Dump vendor specific QP details (git-fixes)\n- rdma/cxgb4: Fix RDMA_CM_EVENT_UNREACHABLE error for iWARP (git-fixes)\n- rdma/hns: Add clear_hem return value to log (git-fixes)\n- rdma/hns: Add mutex_destroy() (git-fixes)\n- rdma/hns: Fix an AEQE overflow error caused by untimely update of eq_db_ci (git-fixes)\n- rdma/hns: Fix cpu stuck caused by printings during reset (git-fixes)\n- rdma/hns: Fix different dgids mapping to the same dip_idx (git-fixes)\n- rdma/hns: Fix flush cqe error when racing with destroy qp (git-fixes)\n- rdma/hns: Fix NULL pointer derefernce in hns_roce_map_mr_sg() (git-fixes)\n- rdma/hns: Fix out-of-order issue of requester when setting FENCE (git-fixes)\n- rdma/hns: Remove unnecessary QP type checks (git-fixes)\n- rdma/hns: Remove unused abnormal interrupt of type RAS (git-fixes)\n- rdma/hns: Use dev_* printings in hem code instead of ibdev_* (git-fixes)\n- rdma/hns: Use macro instead of magic number (git-fixes)\n- rdma/irdma: Fix misspelling of 'accept*' (git-fixes)\n- rdma/mad: Improve handling of timed out WRs of mad agent (git-fixes)\n- rdma/mana_ib: use the correct page size for mapping user-mode doorbell page (git-fixes).\n- rdma/mana_ib: use the correct page table index based on hardware page size (git-fixes).\n- rdma/mlx5: Move events notifier registration to be after device registration (git-fixes)\n- rdma/mlx5: Round max_rd_atomic/max_dest_rd_atomic up instead of down (git-fixes)\n- rdma/mlx5: Use sq timestamp as QP timestamp when RoCE is disabled (git-fixes).\n- rdma/rtrs-srv: Avoid null pointer deref during path establishment (git-fixes)\n- rdma/rxe: Fix the qp flush warnings in req (git-fixes)\n- rdma/rxe: Set queue pair cur_qp_state when being queried (git-fixes)\n- rdma/srpt: Make slab cache names unique (git-fixes)\n- Removed the duplicated check of static_assert(sizeof(struct work_struct) \u003e= sizeof(struct rcu_head)).\n- Removed unnecessary white-space change in kernel/bpf/syscall.c\n- Revert 'cgroup: Fix memory leak caused by missing cgroup_bpf_offline' (bsc#1234108).\n- Revert 'ixgbe: Manual AN-37 for troublesome link partners for X550 SFI' (git-fixes).\n- Revert 'KVM: Prevent module exit until all VMs are freed' (git-fixes).\n- Revert 'mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K' (git-fixes).\n- Revert 'usb: gadget: composite: fix OS descriptors w_value logic' (git-fixes).\n- Revert 'usb: yurex: Replace snprintf() with the safer scnprintf() variant' (stable-fixes).\n- Revert PM changes that caused a regression on S4 resume (bsc#1231578).\n- rpm/check-for-config-changes: add HAVE_RUST and RUSTC_SUPPORTS_ to IGNORED_CONFIGS_RE They depend on SHADOW_CALL_STACK.\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rpm/release-projects: Add SLFO projects (bsc#1231293).\n- rpm/scripts: Remove obsolete Symbols.list Symbols.list is not longer needed by the new klp-convert implementation. (bsc#1218644)\n- rtc: ab-eoz9: do not fail temperature reads on undervoltage notification (git-fixes).\n- rtc: abx80x: Fix WDT bit position of the status register (git-fixes).\n- rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (git-fixes).\n- rtc: st-lpc: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- s390/mm: Add cond_resched() to cmm_alloc/free_pages() (bsc#1228747).\n- s390/sclp_vt220: Convert newlines to CRLF instead of LFCR (git-fixes bsc#1232632).\n- sched/isolation: Prevent boot crash when the boot CPU is (bsc#1231327)\n- scsi: aacraid: Rearrange order of struct aac_srb_unit (git-fixes).\n- scsi: core: alua: I/O errors for ALUA state transitions (git-fixes).\n- scsi: core: Fix the return value of scsi_logical_block_count() (git-fixes).\n- scsi: core: Handle devices which return an unusually large VPD page count (git-fixes).\n- scsi: elx: libefc: Fix potential use after free in efc_nport_vport_del() (git-fixes).\n- scsi: fnic: Move flush_work initialization out of if block (bsc#1230055).\n- scsi: hpsa: Fix allocation size for Scsi_Host private data (git-fixes).\n- scsi: libsas: Fix exp-attached device scan after probe failure scanned in again after probe failed (git-fixes).\n- scsi: libsas: Fix the failure of adding phy with zero-address to port (git-fixes).\n- scsi: lpfc: Add cleanup of nvmels_wq after HBA reset (bsc#1233241).\n- scsi: lpfc: Add ELS_RSP cmd to the list of WQEs to flush in lpfc_els_flush_cmd() (bsc#1232757).\n- scsi: lpfc: Call lpfc_sli4_queue_unset() in restart and rmmod paths (bsc#1233241).\n- scsi: lpfc: Change lpfc_nodelist nlp_flag member into a bitmask (bsc#1233241).\n- scsi: lpfc: Check devloss callbk done flag for potential stale NDLP ptrs (bsc#1233241).\n- scsi: lpfc: Check SLI_ACTIVE flag in FDMI cmpl before submitting follow up FDMI (bsc#1233241).\n- scsi: lpfc: Copyright updates for 14.4.0.6 patches (bsc#1233241).\n- scsi: lpfc: Ensure DA_ID handling completion before deleting an NPIV instance (bsc#1232757).\n- scsi: lpfc: Fix kref imbalance on fabric ndlps from dev_loss_tmo handler (bsc#1232757).\n- scsi: lpfc: Modify CGN warning signal calculation based on EDC response (bsc#1233241).\n- scsi: lpfc: Prevent NDLP reference count underflow in dev_loss_tmo callback (bsc#1233241).\n- scsi: lpfc: Remove NLP_RELEASE_RPI flag from nodelist structure (bsc#1233241).\n- scsi: lpfc: Remove trailing space after \\n newline (bsc#1232757).\n- scsi: lpfc: Restrict support for 32 byte CDBs to specific HBAs (git-fixes).\n- scsi: lpfc: Revise TRACE_EVENT log flag severities from KERN_ERR to KERN_WARNING (bsc#1232757).\n- scsi: lpfc: Support loopback tests with VMID enabled (bsc#1232757).\n- scsi: lpfc: Update lpfc version to 14.4.0.5 (bsc#1232757).\n- scsi: lpfc: Update lpfc version to 14.4.0.6 (bsc#1233241).\n- scsi: lpfc: Update lpfc_els_flush_cmd() to check for SLI_ACTIVE before BSG flag (bsc#1233241).\n- scsi: lpfc: Update phba link state conditional before sending CMF_SYNC_WQE (bsc#1232757).\n- scsi: mac_scsi: Disallow bus errors during PDMA send (git-fixes).\n- scsi: mac_scsi: Refactor polling loop (git-fixes).\n- scsi: mac_scsi: Revise printk(KERN_DEBUG ...) messages (git-fixes).\n- scsi: mpi3mr: Avoid IOMMU page faults on REPORT ZONES (git-fixes).\n- scsi: mpi3mr: Fix ATA NCQ priority support (git-fixes).\n- scsi: mpt3sas: Avoid IOMMU page faults on REPORT ZONES (git-fixes).\n- scsi: NCR5380: Check for phase match during PDMA fixup (git-fixes).\n- scsi: qedf: Set qed_slowpath_params to zero before use (git-fixes).\n- scsi: scsi_transport_fc: Allow setting rport state to current state (git-fixes).\n- scsi: sd_zbc: Use kvzalloc() to allocate REPORT ZONES buffer (git-fixes).\n- scsi: smartpqi: correct stream detection (git-fixes).\n- scsi: smartpqi: revert propagate-the-multipath-failure-to-SML-quickly (git-fixes).\n- scsi: spi: Fix sshdr use (git-fixes).\n- scsi: wd33c93: Do not use stale scsi_pointer value (git-fixes).\n- security/keys: fix slab-out-of-bounds in key_task_permission (git-fixes).\n- selftests/bpf: Add a test case to write mtu result into .rodata (git-fixes).\n- selftests/bpf: Add a test case to write strtol result into .rodata (git-fixes).\n- selftests/bpf: Fix ARG_PTR_TO_LONG {half-,}uninitialized test (git-fixes).\n- selftests/bpf: Rename ARG_PTR_TO_LONG test description (git-fixes).\n- selftests/bpf: test for malformed BPF_CORE_TYPE_ID_LOCAL relocation (git-fixes).\n- serial: 8250: omap: Move pm_runtime_get_sync (git-fixes).\n- sfc: Check firmware supports Ethernet PTP filter (git-fixes).\n- sfc: do not unregister flow_indr if it was never registered (git-fixes).\n- sfc: fix a double-free bug in efx_probe_filters (git-fixes).\n- signal: Replace BUG_ON()s (bsc#1234093).\n- spi: atmel-quadspi: Fix register name in verbose logging function (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: Fix acpi deferred irq probe (git-fixes).\n- spi: lpspi: release requested DMA channels (stable-fixes).\n- spi: lpspi: Silence error message upon deferred probe (stable-fixes).\n- spi: lpspi: Simplify some error message (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: s3c64xx: fix timeout counters in flush_fifo (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spi-imx: Fix pm_runtime_set_suspended() with runtime pm enabled (git-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9832: fix division by zero in ad9832_calc_freqreg() (git-fixes).\n- static_call: Do not make __static_call_return0 static (git-fixes).\n- sunrpc: clnt.c: Remove misleading comment (git-fixes).\n- sunrpc: Fix integer overflow in decode_rc_list() (git-fixes).\n- sunrpc: Fixup gss_status tracepoint error output (git-fixes).\n- thermal: core: Initialize thermal zones before registering them (git-fixes).\n- thermal: intel: int340x: processor: Fix warning during module unload (git-fixes).\n- tpm: Lock TPM chip in tpm_pm_suspend() first (bsc#1082555 git-fixes).\n- tracing: Consider the NULL character when validating the event length (git-fixes).\n- tracing/hwlat: Fix a race during cpuhp processing (git-fixes).\n- tracing/uprobes: Use trace_event_buffer_reserve() helper (git-fixes).\n- tun: Fix xdp_rxq_info's queue_index when detaching (git-fixes).\n- tun: prevent negative ifindex (git-fixes).\n- ucounts: fix counter leak in inc_rlimit_get_ucounts() (bsc#1233460).\n- Update config files (bsc#1218644). LIVEPATCH_IPA_CLONES=n =\u003e LIVEPATCH=n\n- Update config files. Enabled IDPF for ARM64 (bsc#1221309)\n- uprobe: avoid out-of-bounds memory access of fetching args (git-fixes).\n- uprobes: encapsulate preparation of uprobe args buffer (git-fixes).\n- usb: appledisplay: close race between probe and completion handler (stable-fixes).\n- usb: chaoskey: fail open after removal (git-fixes).\n- usb: chaoskey: Fix possible deadlock chaoskey_list_lock (git-fixes).\n- usb: chipidea: udc: enable suspend interrupt after usb reset (stable-fixes).\n- usb: dwc2: Adjust the timing of USB Driver Interrupt Registration in the Crashkernel Scenario (stable-fixes).\n- usb: dwc3: core: Stop processing of pending events if controller is halted (git-fixes).\n- usb: dwc3: gadget: Add missing check for single port RAM in TxFIFO resizing logic (git-fixes).\n- usb: dwc3: gadget: Fix checking for number of TRBs left (git-fixes).\n- usb: dwc3: gadget: Fix looping of queued SG entries (git-fixes).\n- usb: ehci-spear: fix call balance of sehci clk handling routines (git-fixes).\n- usb: gadget: core: force synchronous registration (git-fixes).\n- usb: misc: cypress_cy7c63: check for short transfer (stable-fixes).\n- usb: misc: yurex: fix race between read and write (stable-fixes).\n- usb: musb: sunxi: Fix accessing an released usb phy (git-fixes).\n- usb: phy: Fix API devm_usb_put_phy() can not release the phy (git-fixes).\n- usb: serial: ftdi_sio: Fix atomicity violation in get_serial_info() (git-fixes).\n- usb: serial: io_edgeport: fix use after free in debug printk (git-fixes).\n- usb: serial: option: add Fibocom FG132 0x0112 composition (stable-fixes).\n- usb: serial: option: add Quectel RG650V (stable-fixes).\n- usb: serial: option: add support for Quectel EG916Q-GL (stable-fixes).\n- usb: serial: option: add Telit FN920C04 MBIM compositions (stable-fixes).\n- usb: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- usb: serial: qcserial: add support for Sierra Wireless EM86xx (stable-fixes).\n- usb: storage: ignore bogus device raised by JieLi BR21 USB sound chip (stable-fixes).\n- usb: typec: altmode should keep reference to parent (git-fixes).\n- usb: typec: fix potential out of bounds in ucsi_ccg_update_set_new_cam_cmd() (git-fixes).\n- usb: typec: fix unreleased fwnode_handle in typec_port_register_altmodes() (git-fixes).\n- usb: using mutex lock and supporting O_NONBLOCK flag in iowarrior_read() (git-fixes).\n- usb: xhci: Fix problem with xhci resume from suspend (stable-fixes).\n- usb: xhci: Fix TD invalidation under pending Set TR Dequeue (git-fixes).\n- usb: yurex: Fix inconsistent locking bug in yurex_read() (git-fixes).\n- usb: yurex: make waiting on yurex_write interruptible (git-fixes).\n- usb: yurex: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usbip: tools: Fix detach_port() invalid port error path (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (stable-fixes).\n- Use pahole -j1 option for reproducible builds (bsc#1230414 bsc#1229450).\n- vdpa/mlx5: preserve CVQ vringh index (git-fixes).\n- vhost_vdpa: assign irq bypass producer token correctly (git-fixes).\n- vhost/scsi: null-ptr-dereference in vhost_scsi_get_req() (git-fixes).\n- virtio_console: fix misc probe bugs (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- vmxnet3: add command to allow disabling of offloads (bsc#1226498).\n- vmxnet3: add latency measurement support in vmxnet3 (bsc#1226498).\n- vmxnet3: prepare for version 9 changes (bsc#1226498).\n- vmxnet3: update to version 9 (bsc#1226498).\n- vsock/virtio: fix packet delivery to tap device (git-fixes).\n- watchdog: mediatek: Make sure system reset gets asserted in mtk_wdt_restart() (git-fixes).\n- watchdog: rti: of: honor timeout-sec property (git-fixes).\n- wifi: ath10k: fix invalid VHT parameters in supported_vht_mcs_rate_nss1 (git-fixes).\n- wifi: ath10k: fix invalid VHT parameters in supported_vht_mcs_rate_nss2 (git-fixes).\n- wifi: ath10k: Fix memory leak in management tx (git-fixes).\n- wifi: ath11k: fix array out-of-bound access in SoC stats (stable-fixes).\n- wifi: ath11k: Fix invalid ring usage in full monitor mode (git-fixes).\n- wifi: ath9k_htc: Use __skb_set_length() for resetting urb before resubmit (stable-fixes).\n- wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service() (git-fixes).\n- wifi: ath9k: fix parameter check in ath9k_init_debug() (stable-fixes).\n- wifi: ath9k: fix possible integer overflow in ath9k_get_et_stats() (stable-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcm80211: BRCM_TRACING should depend on TRACING (git-fixes).\n- wifi: iwlegacy: Clear stale interrupts before resuming device (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: disconnect station vifs if recovery failed (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: Fix response handling in iwl_mvm_send_recovery_cmd() (git-fixes).\n- wifi: mac80211: do not pass a stopped vif to the driver in .get_txpower (git-fixes).\n- wifi: mac80211: skip non-uploaded keys in ieee80211_iter_keys (git-fixes).\n- wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() (stable-fixes).\n- wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan() (git-fixes).\n- wifi: mwifiex: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- wifi: p54: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- wifi: rtw88: select WANT_DEV_COREDUMP (stable-fixes).\n- workqueue: Avoid using isolated cpus' timers on (bsc#1231327)\n- workqueue: mark power efficient workqueue as unbounded if (bsc#1231327)\n- x86/bugs: Do not use UNTRAIN_RET with IBPB on entry (git-fixes).\n- x86/bugs: Skip RSB fill at VMEXIT (git-fixes).\n- x86/cpufeatures: Add a IBPB_NO_RET BUG flag (git-fixes).\n- x86/cpufeatures: Define X86_FEATURE_AMD_IBPB_RET (git-fixes).\n- x86/entry: Have entry_ibpb() invalidate return predictions (git-fixes).\n- x86/hyperv: Set X86_FEATURE_TSC_KNOWN_FREQ when Hyper-V provides frequency (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1230405).\n- x86/kvm: fix is_stale_page_fault() (bsc#1221333).\n- xfrm: set dst dev to blackhole_netdev instead of loopback_dev in ifdown (bsc#1216813).\n- xhci: Fix incorrect stream context type macro (git-fixes).\n- xhci: Fix Link TRB DMA in command ring stopped completion event (git-fixes).\n- xhci: Mitigate failed set dequeue pointer commands (git-fixes).\n- xhci: Separate PORT and CAPs macros into dedicated file (stable-fixes).\n- xhci: Use pm_runtime_get to prevent RPM on unsupported systems (git-fixes).\n","status":"published","published":"2024-12-17T15:57:44Z","modified":"2026-02-04T03:18:12.620291Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:0034-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\nThe Linux Enterprise 12 SP5 kernel turned LTSS (Extended Security)\n\nThe following security bugs were fixed:\n\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47163: kABI fix for tipc: wait and exit until all work queues are done (bsc#1221980).\n- CVE-2021-47612: nfc: fix segfault in nfc_genl_dump_devices_done (bsc#1226585).\n- CVE-2022-48809: net: fix a memleak when uncloning an skb dst and its metadata (bsc#1227947).\n- CVE-2022-48951: ASoC: ops: Correct bounds check for second channel on SX controls (bsc#1231929).\n- CVE-2022-48956: ipv6: avoid use-after-free in ip6_fragment() (bsc#1231893).\n- CVE-2022-48958: ethernet: aeroflex: fix potential skb leak in greth_init_rings() (bsc#1231889).\n- CVE-2022-48960: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() (bsc#1231979).\n- CVE-2022-48962: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() (bsc#1232286).\n- CVE-2022-48966: net: mvneta: Fix an out of bounds check (bsc#1232191).\n- CVE-2022-48967: NFC: nci: Bounds check struct nfc_target arrays (bsc#1232304).\n- CVE-2022-48971: Bluetooth: Fix not cleanup led when bt_init fails (bsc#1232037).\n- CVE-2022-48972: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (bsc#1232025).\n- CVE-2022-48973: gpio: amd8111: Fix PCI device reference count leak (bsc#1232039).\n- CVE-2022-48978: HID: core: fix shift-out-of-bounds in hid_report_raw_event (bsc#1232038).\n- CVE-2022-48991: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (bsc#1232070).\n- CVE-2022-48992: ASoC: soc-pcm: Add NULL check in BE reparenting (bsc#1232071).\n- CVE-2022-49000: iommu/vt-d: Fix PCI device refcount leak in has_external_pci() (bsc#1232123).\n- CVE-2022-49002: iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() (bsc#1232133).\n- CVE-2022-49010: hwmon: (coretemp) Check for null before removing sysfs attrs (bsc#1232172).\n- CVE-2022-49011: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() (bsc#1232006).\n- CVE-2022-49014: net: tun: Fix use-after-free in tun_detach() (bsc#1231890).\n- CVE-2022-49015: net: hsr: Fix potential use-after-free (bsc#1231938).\n- CVE-2022-49020: net/9p: Fix a potential socket leak in p9_socket_open (bsc#1232175).\n- CVE-2022-49021: net: phy: fix null-ptr-deref while probe() failed (bsc#1231939).\n- CVE-2022-49026: e100: Fix possible use after free in e100_xmit_prepare (bsc#1231997).\n- CVE-2022-49027: iavf: Fix error handling in iavf_init_module() (bsc#1232007).\n- CVE-2022-49028: ixgbevf: Fix resource leak in ixgbevf_init_module() (bsc#1231996).\n- CVE-2022-49029: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails (bsc#1231995).\n- CVE-2023-52898: xhci: Fix null pointer dereference when host dies (bsc#1229568).\n- CVE-2023-52918: media: pci: cx23885: check cx23885_vdev_init() return (bsc#1232047).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (bsc#1227437).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command  (bsc#1228620).\n- CVE-2024-42114: netlink: extend policy range validation (bsc#1228564 prerequisite).\n- CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race (bsc#1229005 stable-fixes).\n- CVE-2024-44931: gpio: prevent potential speculation leaks in gpio_device_get_desc() (bsc#1229837 stable-fixes).\n- CVE-2024-44958: sched/smt: Fix unbalance sched_smt_present dec/inc (bsc#1230179).\n- CVE-2024-46724: drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (bsc#1230725).\n- CVE-2024-46755: wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (bsc#1230802).\n- CVE-2024-46802: drm/amd/display: added NULL check at start of dc_validate_stream (bsc#1231111).\n- CVE-2024-46809: drm/amd/display: Check BIOS images before it is used (bsc#1231148).\n- CVE-2024-46813: drm/amd/display: Check link_index before accessing dc-\u003elinks (bsc#1231191).\n- CVE-2024-46816: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links (bsc#1231197).\n- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231203).\n- CVE-2024-46826: ELF: fix kernel.randomize_va_space double read (bsc#1231115).\n- CVE-2024-46834: ethtool: fail closed if we can't get max channel used in indirection tables (bsc#1231096).\n- CVE-2024-46840: btrfs: clean up our handling of refs == 0 in snapshot delete (bsc#1231105).\n- CVE-2024-46841: btrfs: do not BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (bsc#1231094).\n- CVE-2024-46848: perf/x86/intel: Limit the period on Haswell (bsc#1231072).\n- CVE-2024-47672: wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (bsc#1231540).\n- CVE-2024-47673: wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (bsc#1231539).\n- CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case (bsc#1231673).\n- CVE-2024-47684: tcp: check skb is non-NULL in tcp_rto_delta_us() (bsc#1231987).\n- CVE-2024-47685: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() (bsc#1231998).\n- CVE-2024-47697: drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (bsc#1231858).\n- CVE-2024-47698: drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (bsc#1231859).\n- CVE-2024-47706: block, bfq: fix possible UAF for bfqq-\u003ebic with merge chain (bsc#1231942).\n- CVE-2024-47707: ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (bsc#1231935).\n- CVE-2024-47713: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (bsc#1232016).\n- CVE-2024-47735: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (bsc#1232111).\n- CVE-2024-47737: nfsd: call cache_put if xdr_reserve_space returns NULL (bsc#1232056).\n- CVE-2024-47742: firmware_loader: Block path traversal (bsc#1232126).\n- CVE-2024-47745: mm: split critical region in remap_file_pages() and invoke LSMs in between (bsc#1232135).\n- CVE-2024-49851: tpm: Clean up TPM space after command failure (bsc#1232134).\n- CVE-2024-49860: ACPI: sysfs: validate return type of _STR method (bsc#1231861).\n- CVE-2024-49881: ext4: update orig_path in ext4_find_extent() (bsc#1232201).\n- CVE-2024-49882: ext4: fix double brelse() the buffer of the extents path (bsc#1232200).\n- CVE-2024-49883: ext4: aovid use-after-free in ext4_ext_insert_extent() (bsc#1232199).\n- CVE-2024-49890: drm/amd/pm: ensure the fw_info is not null before using it (bsc#1232217).\n- CVE-2024-49891: scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1232218).\n- CVE-2024-49894: drm/amd/display: Fix index out of bounds in degamma hardware format translation (bsc#1232354).\n- CVE-2024-49896: drm/amd/display: Check stream before comparing them (bsc#1232221).\n- CVE-2024-49901: drm/msm/adreno: Assign msm_gpu-\u003epdev earlier to avoid nullptrs (bsc#1232305).\n- CVE-2024-49920: drm/amd/display: Check null pointers before multiple uses (bsc#1232313).\n- CVE-2024-49929: wifi: iwlwifi: mvm: avoid NULL pointer dereference (bsc#1232253).\n- CVE-2024-49936: net/xen-netback: prevent UAF in xenvif_flush_hash() (bsc#1232424).\n- CVE-2024-49949: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (bsc#1232160).\n- CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree (bsc#1232151).\n- CVE-2024-49959: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error (bsc#1232149).\n- CVE-2024-49962: ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() (bsc#1232314).\n- CVE-2024-49966: ocfs2: cancel dqi_sync_work before freeing oinfo (bsc#1232141).\n- CVE-2024-49967: ext4: no need to continue when the number of entries is 1 (bsc#1232140).\n- CVE-2024-49991: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer (bsc#1232282).\n- CVE-2024-49995: tipc: guard against string buffer overrun (bsc#1232432).\n- CVE-2024-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate() (bsc#1232442).\n- CVE-2024-50007: ALSA: asihpi: Fix potential OOB array access (bsc#1232394).\n- CVE-2024-50024: net: Fix an unsafe loop on the list (bsc#1231954).\n- CVE-2024-50033: slip: make slhc_remember() more robust against malicious packets (bsc#1231914).\n- CVE-2024-50035: ppp: fix ppp_async_encode() illegal access (bsc#1232392).\n- CVE-2024-50045: netfilter: br_netfilter: fix panic with metadata_dst skb (bsc#1231903).\n- CVE-2024-50047: smb: client: fix UAF in async decryption (bsc#1232418).\n- CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too (bsc#1232285).\n\nThe following non-security bugs were fixed:\n\n- arm64: esr: Define ESR_ELx_EC_* constants as UL (git-fixes)\n- arm64: probes: Fix simulate_ldr*_literal() (git-fixes)\n- arm64: probes: Fix uprobes for big-endian kernels (git-fixes)\n- arm64: probes: Remove broken LDR (literal) uprobe support (git-fixes)\n- bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (bsc#1231375).\n- drbd: Add NULL check for net_conf to prevent dereference in state validation (git-fixes).\n- drbd: Fix atomicity violation in drbd_uuid_set_bm() (git-fixes).\n- ext4: fix slab-use-after-free in ext4_split_extent_at() (bsc#1232201)\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- net: usb: usbnet: fix name regression (get-fixes).\n- nfs: fix memory leak in error path of nfs4_do_reclaim (git-fixes).\n- nfsd: fix delegation_blocked() to block correctly for at least 30 seconds (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1230405).\n","status":"published","published":"2025-01-08T09:47:28Z","modified":"2026-02-04T04:37:46.913821Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:20073-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- Drop mm patches that caused regressions (bsc#1230413)\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Move fixes into sorted section (bsc#1230119)\n- Move s390 kabi patch into the kabi section\n- Move upstreamed SCSI patches into sorted section\n- Move upstreamed input patch into sorted section\n- Move upstreamed kaslr patch into sorted section\n- Move upstreamed nvme patches into sorted section\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for \"dra7xx-pcie-main\" IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert \"afs: Hide silly-rename files from userspace\" (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Split kABI out of 'io_uring/kbuf: get rid of bl-\u003eis_ready'\n- kABI: Split kABI out of 'io_uring: Re-add dummy_ubuf for kABI purposes'\n- kABI: Split kABI out of io_uring/kbuf: protect io_buffer_list teardown with a reference \n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for \"/tmp/perf-$PID.map\" files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2025-02-03T09:04:16Z","modified":"2026-03-23T04:50:03.63945Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20077-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).\n- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).\n- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).\n- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).\n- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).\n- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).\n- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).\n- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).\n- CVE-2024-40965: i2c: lpi2c: Avoid calling clk_get_rate during transfer (bsc#1227885).\n- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).\n- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).\n- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).\n- CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray (bsc#1229001).\n- CVE-2024-42252: closures: Change BUG_ON() to WARN_ON() (bsc#1229004).\n- CVE-2024-42265: protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions (bsc#1229334).\n- CVE-2024-42294: block: fix deadlock between sd_remove \u0026 sd_release (bsc#1229371).\n- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).\n- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).\n- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).\n- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).\n- CVE-2024-43832: s390/uv: Do not call folio_wait_writeback() without a folio reference (bsc#1229380).\n- CVE-2024-43845: udf: Fix bogus checksum computation in udf_rename() (bsc#1229389).\n- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).\n- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).\n- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).\n- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).\n- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).\n- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).\n- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).\n- CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption (bsc#1230181).\n- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).\n- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).\n- CVE-2024-44984: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT (bsc#1230240).\n- CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit() (bsc#1230206).\n- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).\n- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).\n- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).\n- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).\n- CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch (bsc#1230195).\n- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).\n- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit() (bsc#1230233).\n- CVE-2024-45002: rtla/osnoise: Prevent NULL dereference in error handling (bsc#1230169).\n- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).\n- CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() (bsc#1230442).\n- CVE-2024-45017: net/mlx5: Fix IPsec RoCE MPV trace call (bsc#1230430).\n- CVE-2024-45018: netfilter: flowtable: initialise extack before use (bsc#1230431).\n- CVE-2024-45019: net/mlx5e: Take state lock during tx timeout reporter (bsc#1230432).\n- CVE-2024-45021: memcg_write_event_control(): fix a user-triggerable oops (bsc#1230434).\n- CVE-2024-45022: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 (bsc#1230435).\n- CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk (bsc#1230455).\n- CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe (bsc#1230451).\n- CVE-2024-45030: igb: cope with large MAX_SKB_FRAGS (bsc#1230457).\n- CVE-2024-46673: scsi: aacraid: Fix double-free on probe failure (bsc#1230506).\n- CVE-2024-46677: gtp: fix a potential NULL pointer dereference (bsc#1230549).\n- CVE-2024-46679: ethtool: check device is present when getting link settings (bsc#1230556).\n- CVE-2024-46686: smb/client: avoid dereferencing rdata=NULL in smb2_new_read_req() (bsc#1230517).\n- CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk() (bsc#1230518).\n- CVE-2024-46691: usb: typec: ucsi: Move unregister out of atomic section (bsc#1230526).\n- CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call (bsc#1230520).\n- CVE-2024-46693: kABI workaround for soc-qcom pmic_glink changes (bsc#1230521).\n- CVE-2024-46710: drm/vmwgfx: Prevent unmapping active read buffers (bsc#1230540).\n- CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release (bsc#1230719).\n- CVE-2024-46729: drm/amd/display: Fix incorrect size calculation for loop (bsc#1230704).\n- CVE-2024-46735: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() (bsc#1230727).\n- CVE-2024-46743: of/irq: Prevent device address out-of-bounds read in interrupt map walk (bsc#1230756).\n- CVE-2024-46751: btrfs: do not BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (bsc#1230786).\n- CVE-2024-46752: btrfs: reduce nesting for extent processing at btrfs_lookup_extent_info() (bsc#1230794).\n- CVE-2024-46753: btrfs: handle errors from btrfs_dec_ref() properly (bsc#1230796).\n- CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used (bsc#1230772).\n- CVE-2024-46783: tcp_bpf: fix return value of tcp_bpf_sendmsg() (bsc#1230810).\n- CVE-2024-46787: userfaultfd: fix checks for huge PMDs (bsc#1230815).\n- CVE-2024-46794: x86/tdx: Fix data leak in mmio_read() (bsc#1230825).\n- CVE-2024-46822: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry (bsc#1231120).\n\nThe following non-security bugs were fixed:\n\n- ABI: testing: fix admv8818 attr description (git-fixes).\n- ACPI: CPPC: Add helper to get the highest performance value (stable-fixes).\n- ACPI: CPPC: Fix MASK_VAL() usage (git-fixes).\n- ACPI: PMIC: Remove unneeded check in tps68470_pmic_opregion_probe() (git-fixes).\n- ACPI: processor: Fix memory leaks in error paths of processor_add() (stable-fixes).\n- ACPI: processor: Return an error if acpi_processor_get_info() fails in processor_add() (stable-fixes).\n- ACPI: sysfs: validate return type of _STR method (git-fixes).\n- ACPICA: Implement ACPI_WARNING_ONCE and ACPI_ERROR_ONCE (stable-fixes).\n- ACPICA: executer/exsystem: Do not nag user about every Stall() violating the spec (git-fixes).\n- ALSA: control: Apply sanity check of input values for user elements (stable-fixes).\n- ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices (stable-fixes).\n- ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP (stable-fixes).\n- ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx (stable-fixes).\n- ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx (stable-fixes).\n- ALSA: hda/realtek: add patch for internal mic in Lenovo V145 (stable-fixes).\n- ALSA: hda/realtek: extend quirks for Clevo V5[46]0 (stable-fixes).\n- ALSA: hda: Add input value sanity checks to HDMI channel map controls (stable-fixes).\n- ALSA: hda: add HDMI codec ID for Intel PTL (stable-fixes).\n- ALSA: hda: cs35l41: fix module autoloading (git-fixes).\n- ARM: 9406/1: Fix callchain_trace() return value (git-fixes).\n- ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) (stable-fixes).\n- ASoC: codecs: avoid possible garbage value in peb2466_reg_read() (git-fixes).\n- ASoC: cs42l42: Convert comma to semicolon (git-fixes).\n- ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object (git-fixes).\n- ASoC: intel: fix module autoloading (stable-fixes).\n- ASoC: meson: Remove unused declartion in header file (git-fixes).\n- ASoC: meson: axg-card: fix 'use-after-free' (git-fixes).\n- ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: rt5682s: Return devm_of_clk_add_hw_provider to transfer the error (git-fixes).\n- ASoC: soc-ac97: Fix the incorrect description (git-fixes).\n- ASoC: sunxi: sun4i-i2s: fix LRCLK polarity in i2s mode (git-fixes).\n- ASoC: tas2781-i2c: Get the right GPIO line (git-fixes).\n- ASoC: tda7419: fix module autoloading (stable-fixes).\n- ASoC: tegra: Fix CBB error during probe() (git-fixes).\n- ASoC: topology: Properly initialize soc_enum values (stable-fixes).\n- ASoc: SOF: topology: Clear SOF link platform name upon unload (git-fixes).\n- ASoc: TAS2781: replace beXX_to_cpup with get_unaligned_beXX for potentially broken alignment (stable-fixes).\n- Bluetooth: MGMT: Ignore keys being loaded with invalid type (git-fixes).\n- Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() (stable-fixes).\n- Bluetooth: btusb: Fix not handling ZPL/short-transfer (git-fixes).\n- Bluetooth: hci_core: Fix sending MGMT_EV_CONNECT_FAILED (git-fixes).\n- Bluetooth: hci_event: Use HCI error defines instead of magic values (stable-fixes).\n- Bluetooth: hci_sync: Add helper functions to manipulate cmd_sync queue (stable-fixes).\n- Bluetooth: hci_sync: Ignore errors from HCI_OP_REMOTE_NAME_REQ_CANCEL (git-fixes).\n- Detect memory allocation failure in annotated_source__alloc_histograms (bsc#1227962).\n- Documentation: ioctl: document 0x07 ioctl code (git-fixes).\n- Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic (git-fixes).\n- Drivers: hv: vmbus: Fix the misplaced function description (git-fixes).\n- Drop mm patches that caused regressions (bsc#1230413)\n- Enable livepatching related packages on -RT (jsc#PED-1706)\n- HID: amd_sfh: free driver_data after destroying hid device (stable-fixes).\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup (stable-fixes).\n- HID: multitouch: Add support for GT7868Q (stable-fixes).\n- HID: wacom: Do not warn about dropped packets for first packet (git-fixes).\n- HID: wacom: Support sequence numbers smaller than 16-bit (git-fixes).\n- IB/core: Fix ib_cache_setup_one error flow cleanup (git-fixes)\n- Input: adp5588-keys - fix check on return code (git-fixes).\n- Input: ads7846 - ratelimit the spi_sync error message (stable-fixes).\n- Input: ili210x - use kvmalloc() to allocate buffer for firmware update (stable-fixes).\n- Input: ilitek_ts_i2c - avoid wrong input subsystem sync (git-fixes).\n- Input: ps2-gpio - use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- Input: synaptics - enable SMBus for HP Elitebook 840 G2 (stable-fixes).\n- Input: tsc2004/5 - do not hard code interrupt trigger (git-fixes).\n- Input: tsc2004/5 - fix reset handling on probe (git-fixes).\n- Input: tsc2004/5 - use device core to create driver-specific device attributes (git-fixes).\n- Input: uinput - reject requests with unreasonable number of slots (stable-fixes).\n- KEYS: prevent NULL pointer dereference in find_asymmetric_key() (git-fixes).\n- KVM: SVM: Do not advertise Bus Lock Detect to guest if SVM support is missing (git-fixes).\n- KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE (git-fixes).\n- KVM: arm64: Block unsafe FF-A calls from the host (git-fixes).\n- KVM: arm64: Disallow copying MTE to guest memory while KVM is dirty logging (git-fixes).\n- KVM: arm64: Do not pass a TLBI level hint when zapping table entries (git-fixes).\n- KVM: arm64: Do not re-initialize the KVM lock (git-fixes).\n- KVM: arm64: Invalidate EL1\u00260 TLB entries for all VMIDs in nvhe hyp init (git-fixes).\n- KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 (git-fixes).\n- KVM: arm64: Release pfn, i.e. put page, if copying MTE tags hits ZONE_DEVICE (git-fixes).\n- KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (git-fixes).\n- KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr() (git-fixes).\n- KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS (git-fixes).\n- Merge branch 'ALP-current' (0e26fa94003b) into 'ALP-current-RT'\n- Move fixes into sorted section (bsc#1230119)\n- Move s390 kabi patch into the kabi section\n- Move upstreamed SCSI patches into sorted section\n- Move upstreamed input patch into sorted section\n- Move upstreamed kaslr patch into sorted section\n- Move upstreamed nvme patches into sorted section\n- NFS: never reuse a NFSv4.0 lock-owner (bsc#1227726).\n- NFSD: Fix frame size warning in svc_export_parse() (git-fixes).\n- NFSD: Rewrite synopsis of nfsd_percpu_counters_init() (git-fixes).\n- NFSv4: Add missing rescheduling points in nfs_client_return_marked_delegations (git-fixes).\n- No -rt specific changes this merge.\n- PCI: Add missing bridge lock to pci_bus_lock() (stable-fixes).\n- PCI: Wait for Link before restoring Downstream Buses (git-fixes).\n- PCI: al: Check IORESOURCE_BUS existence during probe (stable-fixes).\n- PCI: dra7xx: Fix error handling when IRQ request fails in probe (git-fixes).\n- PCI: dra7xx: Fix threaded IRQ request for \"dra7xx-pcie-main\" IRQ (git-fixes).\n- PCI: dwc: Expose dw_pcie_ep_exit() to module (git-fixes).\n- PCI: imx6: Fix missing call to phy_power_off() in error handling (git-fixes).\n- PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0) (stable-fixes).\n- PCI: keystone: Fix if-statement expression in ks_pcie_quirk() (git-fixes).\n- PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() (git-fixes).\n- PCI: qcom-ep: Enable controller resources like PHY only after refclk is available (git-fixes).\n- PCI: xilinx-nwl: Clean up clock on probe failure/removal (git-fixes).\n- PCI: xilinx-nwl: Fix off-by-one in INTx IRQ handler (git-fixes).\n- PKCS#7: Check codeSigning EKU of certificates in PKCS#7 (bsc#1226666).\n- RDMA/core: Remove unused declaration rdma_resolve_ip_route() (git-fixes)\n- RDMA/cxgb4: Added NULL check for lookup_atid (git-fixes)\n- RDMA/efa: Properly handle unexpected AQ completions (git-fixes)\n- RDMA/erdma: Return QP state in erdma_query_qp (git-fixes)\n- RDMA/hns: Do not modify rq next block addr in HIP09 QPC (git-fixes)\n- RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS (git-fixes)\n- RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 (git-fixes)\n- RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler (git-fixes)\n- RDMA/hns: Fix ah error counter in sw stat not increasing (git-fixes)\n- RDMA/hns: Fix restricted __le16 degrades to integer issue (git-fixes)\n- RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled (git-fixes)\n- RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() (git-fixes)\n- RDMA/hns: Optimize hem allocation performance (git-fixes)\n- RDMA/irdma: fix error message in irdma_modify_qp_roce() (git-fixes)\n- RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency (git-fixes)\n- RDMA/mlx5: Drop redundant work canceling from clean_keys() (git-fixes)\n- RDMA/mlx5: Fix MR cache temp entries cleanup (git-fixes)\n- RDMA/mlx5: Fix counter update on MR cache mkey creation (git-fixes)\n- RDMA/mlx5: Limit usage of over-sized mkeys from the MR cache (git-fixes)\n- RDMA/mlx5: Obtain upper net device only when needed (git-fixes)\n- RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds (git-fixes)\n- RDMA/rtrs: Reset hb_missed_cnt after receiving other traffic from peer (git-fixes)\n- Replace git-fixes tag by bsc#1226507, patches.suse/md-Don-t-wait-for-MD_RECOVERY_NEEDED-for-HOT_REMOVE_DISK-ioctl-a1fd.patch (bsc#1226507).\n- Resort io_uring kABI patches These ended up in the wrong section. Push them to the right place, next to the other io_uring kabi patches.\n- Restore dropped fields for bluetooth MGMT/SMP structs (git-fixes).\n- Revert \"Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE\" (git-fixes).\n- Revert \"PCI: Extend ACS configurability (bsc#1228090).\" (bsc#1229019) This reverts commit 571e4310e81312c847a5caee7e45e66aeea2a169. It breaks ACS on certain platforms. Even 6.11 is affected. So drop for now and investigate.\n- Revert \"drm/amdgpu: align pp_power_profile_mode with kernel docs\" (stable-fixes).\n- Revert \"media: tuners: fix error return code of hybrid_tuner_request_state()\" (git-fixes).\n- Revert \"mm, kmsan: fix infinite recursion due to RCU critical section\" This reverts commit 16ad73a9f4c2888f3bc28513f5e9a88d753f8741.\n- Revert \"mm/sparsemem: fix race in accessing memory_section-\u003eusage\" This reverts commit 6aa8957889611fbe7f06353f917cfb3d9620a680.\n- Revert \"mm: prevent derefencing NULL ptr in pfn_section_valid()\" This reverts commit 35f619d3c421219e07bc89d2d6a37fbff25519fe.\n- Split kabi part of dm_blk_ioctl-implement-path-failover-for-SG_IO.patch\n- Squashfs: sanity check symbolic link size (git-fixes).\n- USB: class: CDC-ACM: fix race between get_serial and set_serial (git-fixes).\n- USB: serial: kobil_sct: restore initial terminal settings (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (git-fixes).\n- USB: serial: option: add MeiG Smart SRM825L (stable-fixes).\n- USB: serial: pl2303: add device id for Macrosilicon MS3020 (stable-fixes).\n- USB: usbtmc: prevent kernel-usb-infoleak (git-fixes).\n- Update patches.suse/af_unix-Fix-data-races-around-sk-sk_shutdown.patch (git-fixes bsc#1226846).\n- Update patches.suse/gfs2-Fix-NULL-pointer-dereference-in-gfs2_log_flush.patch (bsc#1230948)\n- Update patches.suse/powerpc-pseries-make-max-polling-consistent-for-long.patch (bsc#1215199 jsc#PED-10954).\n- Update patches.suse/security-integrity-fix-pointer-to-ESL-data-and-.patch (bsc#1012628 jsc#PED-5085 jsc#PED-10954).\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- afs: Revert \"afs: Hide silly-rename files from userspace\" (git-fixes).\n- arm64/mm: Modify range-based tlbi to decrement scale (bsc#1229585)\n- arm64/mm: Update tlb invalidation routines for FEAT_LPA2 (bsc#1229585)\n- arm64: acpi: Move get_cpu_for_acpi_id() to a header (git-fixes).\n- arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes (git-fixes).\n- arm64: dts: exynos: exynos7885-jackpotlte: Correct RAM amount to 4GB (git-fixes).\n- arm64: dts: imx8-ss-dma: Fix adc0 closing brace location (git-fixes).\n- arm64: dts: rockchip: Correct the Pinebook Pro battery design capacity (git-fixes).\n- arm64: dts: rockchip: Correct vendor prefix for Hardkernel ODROID-M1 (git-fixes).\n- arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency (git-fixes).\n- arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E (git-fixes).\n- arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma (git-fixes).\n- arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma (git-fixes).\n- arm64: signal: Fix some under-bracketed UAPI macros (git-fixes).\n- arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES (bsc#1229585)\n- arm64: tlb: Fix TLBI RANGE operand (bsc#1229585)\n- arm64: tlb: Improve __TLBI_VADDR_RANGE() (bsc#1229585)\n- ata: libata-scsi: Fix ata_msense_control() CDL page reporting (git-fixes).\n- ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data (git-fixes).\n- ata: libata: Fix memory leak for error path in ata_host_alloc() (git-fixes).\n- ata: pata_macio: Use WARN instead of BUG (stable-fixes).\n- blacklist.conf: (\"KVM: arm64: Use TLBI_TTL_UNKNOWN in __kvm_tlb_flush_vmid_range()\") (bsc#1229585)\n- blk-mq: add helper for checking if one CPU is mapped to specified hctx (bsc#1223600).\n- blk-mq: do not schedule block kworker on isolated CPUs (bsc#1223600).\n- bpf, events: Use prog to emit ksymbol event for main program (git-fixes).\n- bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (git-fixes).\n- btrfs: fix race between direct IO write and fsync when using same fd (git-fixes).\n- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1230854).\n- bus: integrator-lm: fix OF node leak in probe() (git-fixes).\n- cachefiles: Fix non-taking of sb_writers around set/removexattr (bsc#1231008).\n- cachefiles: fix dentry leak in cachefiles_open_file() (bsc#1231183).\n- can: bcm: Clear bo-\u003ebcm_proc_read after remove_proc_entry() (git-fixes).\n- can: bcm: Remove proc entry when dev is unregistered (git-fixes).\n- can: j1939: use correct function name in comment (git-fixes).\n- can: kvaser_pciefd: Skip redundant NULL pointer check in ISR (stable-fixes).\n- can: m_can: Release irq on error in m_can_open (git-fixes).\n- can: m_can: enable NAPI before enabling interrupts (git-fixes).\n- can: m_can: m_can_close(): stop clocks after device has been shut down (git-fixes).\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open (git-fixes).\n- can: mcp251xfd: clarify the meaning of timestamp (stable-fixes).\n- can: mcp251xfd: fix ring configuration when switching from CAN-CC to CAN-FD mode (git-fixes).\n- can: mcp251xfd: mcp251xfd_handle_rxif_ring_uinc(): factor out in separate function (stable-fixes).\n- can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration (stable-fixes).\n- can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() (stable-fixes).\n- can: mcp251xfd: properly indent labels (stable-fixes).\n- can: mcp251xfd: rx: add workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- can: mcp251xfd: rx: prepare to workaround broken RX FIFO head index erratum (stable-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (git-fixes).\n- cdc-acm: Add DISABLE_ECHO quirk for GE HealthCare UI Controller (stable-fixes).\n- ceph: remove the incorrect Fw reference check when dirtying pages (bsc#1231182).\n- clk: Add a devm variant of clk_rate_exclusive_get() (bsc#1227885).\n- clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get() (bsc#1227885).\n- clk: qcom: clk-alpha-pll: Fix the pll post div mask (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API (git-fixes).\n- clk: qcom: clk-alpha-pll: Fix zonda set_rate failure when PLL is disabled (git-fixes).\n- clk: qcom: gcc-sc8280xp: do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: gcc-sm8550: Do not park the USB RCG at registration time (git-fixes).\n- clk: qcom: gcc-sm8550: Do not use parking clk_ops for QUPs (git-fixes).\n- clk: qcom: ipq9574: Update the alpha PLL type for GPLLs (git-fixes).\n- clk: ti: dra7-atl: Fix leak of of_nodes (git-fixes).\n- clocksource/drivers/imx-tpm: Fix next event not taking effect sometime (git-fixes).\n- clocksource/drivers/imx-tpm: Fix return -ETIME when delta exceeds INT_MAX (git-fixes).\n- clocksource/drivers/qcom: Add missing iounmap() on errors in msm_dt_timer_init() (git-fixes).\n- cpufreq: amd-pstate: Enable amd-pstate preferred core support (stable-fixes).\n- cpufreq: amd-pstate: fix the highest frequency issue which limits performance (git-fixes).\n- cpufreq: scmi: Avoid overflow of target_freq in fast switch (stable-fixes).\n- cpufreq: ti-cpufreq: Introduce quirks to handle syscon fails appropriately (git-fixes).\n- crypto: ccp - Properly unregister /dev/sev on sev PLATFORM_STATUS failure (git-fixes).\n- crypto: ccp - do not request interrupt on cmd completion when irqs disabled (git-fixes).\n- crypto: iaa - Fix potential use after free bug (git-fixes).\n- crypto: qat - fix unintentional re-enabling of error interrupts (stable-fixes).\n- crypto: xor - fix template benchmarking (git-fixes).\n- cxl/core: Fix incorrect vendor debug UUID define (git-fixes).\n- cxl/pci: Fix to record only non-zero ranges (git-fixes).\n- devres: Initialize an uninitialized struct member (stable-fixes).\n- dma-buf: heaps: Fix off-by-one in CMA heap fault handler (git-fixes).\n- dma-debug: avoid deadlock between dma debug vs printk and netconsole (stable-fixes).\n- dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor (stable-fixes).\n- dmaengine: altera-msgdma: use irq variant of spin_lock/unlock while invoking callbacks (stable-fixes).\n- driver core: Fix a potential null-ptr-deref in module_add_driver() (git-fixes).\n- driver core: Fix error handling in driver API device_rename() (git-fixes).\n- driver: iio: add missing checks on iio_info's callback access (stable-fixes).\n- drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error (git-fixes).\n- drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error (git-fixes).\n- drivers:drm:exynos_drm_gsc:Fix wrong assignment in gsc_bind() (git-fixes).\n- drm/amd/amdgpu: Check tbo resource pointer (stable-fixes).\n- drm/amd/amdgpu: Properly tune the size of struct (git-fixes).\n- drm/amd/display: Add array index check for hdcp ddc access (stable-fixes).\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func (git-fixes).\n- drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing (stable-fixes).\n- drm/amd/display: Assign linear_pitch_alignment even for VM (stable-fixes).\n- drm/amd/display: Avoid overflow from uint32_t to uint8_t (stable-fixes).\n- drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() (git-fixes).\n- drm/amd/display: Check BIOS images before it is used (stable-fixes).\n- drm/amd/display: Check HDCP returned status (stable-fixes).\n- drm/amd/display: Check UnboundedRequestEnabled's value (stable-fixes).\n- drm/amd/display: Check denominator pbn_div before used (stable-fixes).\n- drm/amd/display: Check gpio_id before used as array index (stable-fixes).\n- drm/amd/display: Check index for aux_rd_interval before using (stable-fixes).\n- drm/amd/display: Check msg_id before processing transcation (stable-fixes).\n- drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] (stable-fixes).\n- drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX (stable-fixes).\n- drm/amd/display: Defer handling mst up request in resume (stable-fixes).\n- drm/amd/display: Disable error correction if it's not supported (stable-fixes).\n- drm/amd/display: Do not use fsleep for PSR exit waits on dmub replay (stable-fixes).\n- drm/amd/display: Ensure array index tg_inst won't be -1 (stable-fixes).\n- drm/amd/display: Ensure index calculation will not overflow (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create (stable-fixes).\n- drm/amd/display: Fix Coverity INTEGER_OVERFLOW within decide_fallback_link_setting_max_bw_policy (stable-fixes).\n- drm/amd/display: Fix Coverity INTERGER_OVERFLOW within construct_integrated_info (stable-fixes).\n- drm/amd/display: Fix FEC_READY write on DP LT (stable-fixes).\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box (stable-fixes).\n- drm/amd/display: Fix pipe addition logic in calc_blocks_to_ungate DCN35 (stable-fixes).\n- drm/amd/display: Handle the case which quad_part is equal 0 (stable-fixes).\n- drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection (stable-fixes).\n- drm/amd/display: Replace dm_execute_dmub_cmd with dc_wake_and_execute_dmub_cmd (git-fixes).\n- drm/amd/display: Run DC_LOG_DC after checking link-\u003elink_enc (stable-fixes).\n- drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration (stable-fixes).\n- drm/amd/display: Skip wbscl_set_scaler_filter if filter is null (stable-fixes).\n- drm/amd/display: Solve mst monitors blank out problem after resume (git-fixes).\n- drm/amd/display: Spinlock before reading event (stable-fixes).\n- drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 (stable-fixes).\n- drm/amd/display: Wake DMCUB before sending a command for replay feature (stable-fixes).\n- drm/amd/display: added NULL check at start of dc_validate_stream (stable-fixes).\n- drm/amd/display: handle nulled pipe context in DCE110's set_drr() (git-fixes).\n- drm/amd/display: use preferred link settings for dp signal only (stable-fixes).\n- drm/amd/pm: Fix negative array index read (stable-fixes).\n- drm/amd/pm: check negtive return for table entries (stable-fixes).\n- drm/amd/pm: check specific index for aldebaran (stable-fixes).\n- drm/amd/pm: check specific index for smu13 (stable-fixes).\n- drm/amd/pm: fix the Out-of-bounds read warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vangogh_ppt (stable-fixes).\n- drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr (stable-fixes).\n- drm/amd/pm: fix warning using uninitialized value of max_vid_step (stable-fixes).\n- drm/amd: Add gfx12 swizzle mode defs (stable-fixes).\n- drm/amdgpu/atomfirmware: Silence UBSAN warning (stable-fixes).\n- drm/amdgpu/display: handle gfx12 in amdgpu_dm_plane_format_mod_supported (stable-fixes).\n- drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs (stable-fixes).\n- drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable agc_btc_response (stable-fixes).\n- drm/amdgpu/pm: Fix uninitialized variable warning for smu10 (stable-fixes).\n- drm/amdgpu/swsmu: always force a state reprogram on init (stable-fixes).\n- drm/amdgpu: Fix get each xcp macro (git-fixes).\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number (stable-fixes).\n- drm/amdgpu: Fix out-of-bounds write warning (stable-fixes).\n- drm/amdgpu: Fix smatch static checker warning (stable-fixes).\n- drm/amdgpu: Fix the uninitialized variable warning (stable-fixes).\n- drm/amdgpu: Fix the warning division or modulo by zero (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr (stable-fixes).\n- drm/amdgpu: Fix uninitialized variable warning in amdgpu_info_ioctl (stable-fixes).\n- drm/amdgpu: Handle sg size limit for contiguous allocation (stable-fixes).\n- drm/amdgpu: Set no_hw_access when VF request full GPU fails (stable-fixes).\n- drm/amdgpu: add lock in amdgpu_gart_invalidate_tlb (stable-fixes).\n- drm/amdgpu: add lock in kfd_process_dequeue_from_device (stable-fixes).\n- drm/amdgpu: add missing error handling in function amdgpu_gmc_flush_gpu_tlb_pasid (stable-fixes).\n- drm/amdgpu: add skip_hw_access checks for sriov (stable-fixes).\n- drm/amdgpu: align pp_power_profile_mode with kernel docs (stable-fixes).\n- drm/amdgpu: avoid reading vf2pf info size from FB (stable-fixes).\n- drm/amdgpu: check for LINEAR_ALIGNED correctly in check_tiling_flags_gfx6 (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts (stable-fixes).\n- drm/amdgpu: fix a possible null pointer dereference (git-fixes).\n- drm/amdgpu: fix contiguous handling for IB parsing v2 (git-fixes).\n- drm/amdgpu: fix dereference after null check (stable-fixes).\n- drm/amdgpu: fix mc_data out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix overflowed array index read warning (stable-fixes).\n- drm/amdgpu: fix overflowed constant warning in mmhub_set_clockgating() (stable-fixes).\n- drm/amdgpu: fix the waring dereferencing hive (stable-fixes).\n- drm/amdgpu: fix ucode out-of-bounds read warning (stable-fixes).\n- drm/amdgpu: fix uninitialized scalar variable warning (stable-fixes).\n- drm/amdgpu: handle gfx12 in amdgpu_display_verify_sizes (stable-fixes).\n- drm/amdgpu: properly handle vbios fake edid sizing (git-fixes).\n- drm/amdgpu: reject gang submit on reserved VMIDs (stable-fixes).\n- drm/amdgpu: the warning dereferencing obj for nbio_v7_4 (stable-fixes).\n- drm/amdgpu: update type of buf size to u32 for eeprom functions (stable-fixes).\n- drm/amdgu: fix Unintentional integer overflow for mall size (stable-fixes).\n- drm/amdkfd: Check debug trap enable before write dbg_ev_file (stable-fixes).\n- drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device (stable-fixes).\n- drm/bridge: lontium-lt8912b: Validate mode in drm_bridge_funcs::mode_valid() (git-fixes).\n- drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ (stable-fixes).\n- drm/drm-bridge: Drop conditionals around of_node pointers (stable-fixes).\n- drm/fb-helper: Do not schedule_work() to flush frame buffer during panic() (stable-fixes).\n- drm/gpuvm: fix missing dependency to DRM_EXEC (git-fixes).\n- drm/i915/fence: Mark debug_fence_free() with __maybe_unused (git-fixes).\n- drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused (git-fixes).\n- drm/i915/guc: prevent a possible int overflow in wq offsets (git-fixes).\n- drm/i915: Do not attempt to load the GSC multiple times (git-fixes).\n- drm/kfd: Correct pinned buffer handling at kfd restore and validate process (stable-fixes).\n- drm/mediatek: Set sensible cursor width/height values to fix crash (stable-fixes).\n- drm/mediatek: ovl_adaptor: Add missing of_node_put() (git-fixes).\n- drm/meson: plane: Add error handling (stable-fixes).\n- drm/msm/a5xx: disable preemption in submits by default (git-fixes).\n- drm/msm/a5xx: fix races in preemption evaluation stage (git-fixes).\n- drm/msm/a5xx: properly clear preemption records on resume (git-fixes).\n- drm/msm/a5xx: workaround early ring-buffer emptiness check (git-fixes).\n- drm/msm/adreno: Fix error return if missing firmware-name (stable-fixes).\n- drm/msm/dsi: correct programming sequence for SM8350 / SM8450 (git-fixes).\n- drm/msm: Fix incorrect file name output in adreno_request_fw() (git-fixes).\n- drm/msm: fix %s null argument error (git-fixes).\n- drm/nouveau/fb: restore init() for ramgp102 (git-fixes).\n- drm/radeon/evergreen_cs: fix int overflow errors in cs track offsets (git-fixes).\n- drm/radeon: fix null pointer dereference in radeon_add_common_modes (git-fixes).\n- drm/radeon: properly handle vbios fake edid sizing (git-fixes).\n- drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode (git-fixes).\n- drm/rockchip: vop: Allow 4096px width scaling (git-fixes).\n- drm/rockchip: vop: clear DMA stop bit on RK3066 (git-fixes).\n- drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB on RK3066 (git-fixes).\n- drm/stm: Fix an error handling path in stm_drm_platform_probe() (git-fixes).\n- drm/stm: ltdc: check memory returned by devm_kzalloc() (git-fixes).\n- drm/syncobj: Fix syncobj leak in drm_syncobj_eventfd_ioctl (git-fixes).\n- drm/vc4: hdmi: Handle error case of pm_runtime_resume_and_get (git-fixes).\n- drm: komeda: Fix an issue related to normalized zpos (stable-fixes).\n- drm: omapdrm: Add missing check for alloc_ordered_workqueue (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Max (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Ayn Loki Zero (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() (git-fixes).\n- erofs: fix incorrect symlink detection in fast symlink (git-fixes).\n- exfat: fix memory leak in exfat_load_bitmap() (git-fixes).\n- fbdev: hpfb: Fix an error handling path in hpfb_dio_probe() (git-fixes).\n- firmware: arm_scmi: Fix double free in OPTEE transport (git-fixes).\n- firmware: tegra: bpmp: Drop unused mbox_client_to_bpmp() (git-fixes).\n- firmware_loader: Block path traversal (git-fixes).\n- fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (bsc#1230602).\n- fuse: fix memory leak in fuse_create_open (bsc#1230124).\n- fuse: update stats for pages in dropped aux writeback list (bsc#1230125).\n- fuse: use unsigned type for getxattr/listxattr size truncation (bsc#1230123).\n- gpio: modepin: Enable module autoloading (git-fixes).\n- gpio: rockchip: fix OF node leak in probe() (git-fixes).\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING (stable-fixes).\n- hwmon: (k10temp) Check return value of amd_smn_read() (stable-fixes).\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (max16065) Fix overflows seen when writing limits (git-fixes).\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwmon: (ntc_thermistor) fix module autoloading (git-fixes).\n- hwmon: (pmbus) Conditionally clear individual status bits for pmbus rev \u003e= 1.2 (git-fixes).\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes (stable-fixes).\n- hwrng: bcm2835 - Add missing clk_disable_unprepare in bcm2835_rng_init (git-fixes).\n- hwrng: cctrng - Add missing clk_disable_unprepare in cctrng_resume (git-fixes).\n- hwrng: mtk - Use devm_pm_runtime_enable (git-fixes).\n- i2c: aspeed: Update the stop sw state when the bus recovery occurs (git-fixes).\n- i2c: designware: fix controller is holding SCL low while ENABLE bit is disabled (git-fixes).\n- i2c: isch: Add missed 'else' (git-fixes).\n- i2c: qcom-geni: Use IRQF_NO_AUTOEN flag in request_irq() (git-fixes).\n- i2c: xiic: Wait for TX empty to avoid missed TX NAKs (git-fixes).\n- i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition (git-fixes).\n- i3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup (stable-fixes).\n- iio: adc: ad7124: fix chip ID mismatch (git-fixes).\n- iio: adc: ad7124: fix config comparison (git-fixes).\n- iio: adc: ad7606: fix oversampling gpio array (git-fixes).\n- iio: adc: ad7606: fix standby gpio state to match the documentation (git-fixes).\n- iio: adc: ad7606: remove frstdata check for serial mode (git-fixes).\n- iio: buffer-dmaengine: fix releasing dma channel on error (git-fixes).\n- iio: chemical: bme680: Fix read/write ops to device by adding mutexes (git-fixes).\n- iio: fix scale application in iio_convert_raw_to_processed_unlocked (git-fixes).\n- iio: magnetometer: ak8975: Fix reading for ak099xx sensors (git-fixes).\n- ipmi: docs: do not advertise deprecated sysfs entries (git-fixes).\n- ipmi:ssif: Improve detecting during probing (bsc#1228771)\n- ipmi:ssif: Improve detecting during probing (bsc#1228771) Move patch into the sorted section.\n- ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230206)\n- jfs: fix out-of-bounds in dbNextAG() and diAlloc() (git-fixes).\n- kABI workaround for cros_ec stuff (git-fixes).\n- kABI: Workaround kABI change in patches.suse/iommu-dma-Trace-bounce-buffer-usage-when-mapping-buf.patch (git-fixes).\n- kabi: dm_blk_ioctl: implement path failover for SG_IO (bsc#1183045, bsc#1216776).\n- kselftests: dmabuf-heaps: Ensure the driver name is null-terminated (stable-fixes).\n- kthread: Fix task state in kthread worker if being frozen (bsc#1231146).\n- leds: spi-byte: Call of_node_put() on error path (stable-fixes).\n- lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (stable-fixes).\n- lirc: rc_dev_get_from_fd(): fix file leak (git-fixes).\n- mailbox: bcm2835: Fix timeout during suspend mode (git-fixes).\n- mailbox: rockchip: fix a typo in module autoloading (git-fixes).\n- media: i2c: ar0521: Use cansleep version of gpiod_set_value() (git-fixes).\n- media: ov5675: Fix power on/off delay timings (git-fixes).\n- media: platform: rzg2l-cru: rzg2l-csi2: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- media: qcom: camss: Add check for v4l2_fwnode_endpoint_parse (stable-fixes).\n- media: qcom: camss: Remove use_count guard in stop_streaming (git-fixes).\n- media: sun4i_csi: Implement link validate for sun4i_csi subdev (git-fixes).\n- media: uapi/linux/cec.h: cec_msg_set_reply_to: zero flags (git-fixes).\n- media: uvcvideo: Enforce alignment of frame and interval (stable-fixes).\n- media: venus: fix use after free bug in venus_remove due to race condition (git-fixes).\n- media: vicodec: allow en/decoder cmd w/o CAPTURE (git-fixes).\n- media: vivid: do not set HDMI TX controls if there are no HDMI outputs (stable-fixes).\n- media: vivid: fix wrong sizeimage value for mplane (stable-fixes).\n- memory: mtk-smi: Use devm_clk_get_enabled() (git-fixes).\n- memory: tegra186-emc: drop unused to_tegra186_emc() (git-fixes).\n- minmax: reduce min/max macro expansion in atomisp driver (git-fixes).\n- misc: fastrpc: Fix double free of 'buf' in error path (git-fixes).\n- mmc: core: apply SD quirks earlier during probe (git-fixes).\n- mmc: cqhci: Fix checking of CQHCI_HALT state (git-fixes).\n- mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K (git-fixes).\n- mmc: sdhci-of-aspeed: fix module autoloading (git-fixes).\n- module: Fix KCOV-ignored file name (git-fixes).\n- mtd: powernv: Add check devm_kasprintf() returned value (git-fixes).\n- mtd: slram: insert break after errors in parsing the map (git-fixes).\n- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (git-fixes).\n- net: phy: Fix missing of_node_put() for leds (git-fixes).\n- net: phy: vitesse: repair vsc73xx autonegotiation (stable-fixes).\n- net: tighten bad gso csum offset check in virtio_net_hdr (git-fixes).\n- net: usb: qmi_wwan: add MeiG Smart SRM825L (stable-fixes).\n- nfsd: Do not leave work of closing files to a work queue (bsc#1228140).\n- nilfs2: determine empty node blocks as corrupted (git-fixes).\n- nilfs2: fix missing cleanup on rollforward recovery error (git-fixes).\n- nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() (git-fixes).\n- nilfs2: fix potential oob read in nilfs_btree_check_delete() (git-fixes).\n- nilfs2: fix state management in error path of log writing function (git-fixes).\n- nilfs2: protect references to superblock parameters exposed in sysfs (git-fixes).\n- nouveau: fix the fwsec sb verification register (git-fixes).\n- nvme-multipath: avoid hang on inaccessible namespaces (bsc#1228244).\n- nvme-multipath: system fails to create generic nvme device (bsc#1228244).\n- nvme-pci: Add sleep quirk for Samsung 990 Evo (git-fixes).\n- nvme-pci: allocate tagset on reset if necessary (git-fixes).\n- nvme-tcp: fix link failure for TCP auth (git-fixes).\n- nvme/pci: Add APST quirk for Lenovo N60z laptop (git-fixes).\n- nvme: clear caller pointer on identify failure (git-fixes).\n- nvme: fix namespace removal list (git-fixes).\n- nvmet-rdma: fix possible bad dereference when freeing rsps (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- nvmet-tcp: fix kernel crash if commands allocation fails (git-fixes).\n- nvmet-trace: avoid dereferencing pointer too early (git-fixes).\n- nvmet: Identify-Active Namespace ID List command should reject invalid nsid (git-fixes).\n- ocfs2: cancel dqi_sync_work before freeing oinfo (git-fixes).\n- ocfs2: fix null-ptr-deref when journal load failed (git-fixes).\n- ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate (git-fixes).\n- ocfs2: remove unreasonable unlock in ocfs2_read_blocks (git-fixes).\n- pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv (stable-fixes).\n- pcmcia: Use resource_size function on resource object (stable-fixes).\n- perf annotate: Introduce global annotation_options (git-fixes).\n- perf annotate: Split branch stack cycles information out of 'struct annotation_line' (git-fixes).\n- perf annotate: Use global annotation_options (git-fixes).\n- perf arch events: Fix duplicate RISC-V SBI firmware event name (git-fixes).\n- perf intel-pt: Fix aux_watermark calculation for 64-bit size (git-fixes).\n- perf intel-pt: Fix exclude_guest setting (git-fixes).\n- perf machine thread: Remove exited threads by default (git-fixes).\n- perf maps: Move symbol maps functions to maps.c (git-fixes).\n- perf pmu: Assume sysfs events are always the same case (git-fixes).\n- perf pmus: Fixes always false when compare duplicates aliases (git-fixes).\n- perf record: Lazy load kernel symbols (git-fixes).\n- perf report: Convert to the global annotation_options (git-fixes).\n- perf report: Fix condition in sort__sym_cmp() (git-fixes).\n- perf stat: Fix the hard-coded metrics calculation on the hybrid (git-fixes).\n- perf test: Make test_arm_callgraph_fp.sh more robust (git-fixes).\n- perf tool: fix dereferencing NULL al-\u003emaps (git-fixes).\n- perf tools: Add/use PMU reverse lookup from config to name (git-fixes).\n- perf tools: Use pmus to describe type from attribute (git-fixes).\n- perf top: Convert to the global annotation_options (git-fixes).\n- perf/core: Fix missing wakeup when waiting for context reference (git-fixes).\n- perf/x86/intel/cstate: Add pkg C2 residency counter for Sierra Forest (git-fixes).\n- perf/x86/intel/cstate: Fix Alderlake/Raptorlake/Meteorlake (git-fixes).\n- perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake (git-fixes).\n- perf/x86/intel/pt: Fix a topa_entry base address calculation (git-fixes).\n- perf/x86/intel/pt: Fix pt_topa_entry_for_page() address calculation (git-fixes).\n- perf/x86/intel/pt: Fix topa_entry base length (git-fixes).\n- perf/x86/intel/uncore: Fix the bits of the CHA extended umask for SPR (git-fixes).\n- perf/x86/intel/uncore: Support HBM and CXL PMON counters (bsc#1230119).\n- perf/x86/intel: Add a distinct name for Granite Rapids (git-fixes).\n- perf/x86/intel: Factor out the initialization code for SPR (git fixes).\n- perf/x86/intel: Limit the period on Haswell (git-fixes).\n- perf/x86/intel: Use the common uarch name for the shared functions (git fixes).\n- perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (bsc#1230119).\n- perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (bsc#1230119).\n- perf/x86/uncore: Cleanup unused unit structure (bsc#1230119).\n- perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (bsc#1230119).\n- perf/x86/uncore: Save the unit control address of all units (bsc#1230119).\n- perf/x86/uncore: Support per PMU cpumask (bsc#1230119).\n- perf/x86: Fix smp_processor_id()-in-preemptible warnings (git-fixes).\n- perf/x86: Serialize set_attr_rdpmc() (git-fixes).\n- perf: Fix default aux_watermark calculation (git-fixes).\n- perf: Fix event leak upon exit (git-fixes).\n- perf: Fix perf_aux_size() for greater-than 32-bit size (git-fixes).\n- perf: Prevent passing zero nr_pages to rb_alloc_aux() (git-fixes).\n- perf: script: add raw|disasm arguments to --insn-trace option (git-fixes).\n- phy: zynqmp: Take the phy mutex in xlate (stable-fixes).\n- pinctrl: at91: make it work with current gpiolib (stable-fixes).\n- pinctrl: meteorlake: Add Arrow Lake-H/U ACPI ID (stable-fixes).\n- pinctrl: single: fix missing error code in pcs_probe() (git-fixes).\n- platform/chrome: cros_ec_lpc: MEC access can use an AML mutex (stable-fixes).\n- platform/surface: aggregator_registry: Add Support for Surface Pro 10 (stable-fixes).\n- platform/surface: aggregator_registry: Add support for Surface Laptop Go 3 (stable-fixes).\n- platform/x86: dell-smbios: Fix error path in dell_smbios_init() (git-fixes).\n- platform/x86: panasonic-laptop: Allocate 1 entry extra in the sinf array (git-fixes).\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses (git-fixes).\n- platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- power: supply: Drop use_cnt check from power_supply_property_is_writeable() (git-fixes).\n- power: supply: axp20x_battery: Remove design from min and max voltage (git-fixes).\n- power: supply: hwmon: Fix missing temp1_max_alarm attribute (git-fixes).\n- power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense (git-fixes).\n- powercap/intel_rapl: Add support for AMD family 1Ah (stable-fixes).\n- powerpc/qspinlock: Fix deadlock in MCS queue (bac#1230295 ltc#206656).\n- pwm: xilinx: Fix u32 overflow issue in 32-bit width PWM mode (stable-fixes).\n- r8152: add vendor/device ID pair for D-Link DUB-E250 (git-fixes).\n- regmap: maple: work around gcc-14.1 false-positive warning (stable-fixes).\n- regmap: spi: Fix potential off-by-one when calculating reserved size (stable-fixes).\n- regulator: Return actual error in of_regulator_bulk_get_all() (git-fixes).\n- regulator: core: Fix regulator_is_supported_voltage() kerneldoc return value (git-fixes).\n- regulator: core: Fix short description for _regulator_check_status_enabled() (git-fixes).\n- regulator: core: Stub devm_regulator_bulk_get_const() if !CONFIG_REGULATOR (git-fixes).\n- regulator: rt5120: Convert comma to semicolon (git-fixes).\n- regulator: wm831x-isink: Convert comma to semicolon (git-fixes).\n- remoteproc: imx_rproc: Correct ddr alias for i.MX8M (git-fixes).\n- remoteproc: imx_rproc: Initialize workqueue earlier (git-fixes).\n- remoteproc: k3-r5: Fix error handling when power-up failed (git-fixes).\n- reset: berlin: fix OF node leak in probe() error path (git-fixes).\n- reset: k210: fix OF node leak in probe() error path (git-fixes).\n- resource: fix region_intersects() vs add_memory_driver_managed() (git-fixes).\n- rpm/check-for-config-changes: Exclude ARCH_USING_PATCHABLE_FUNCTION_ENTRY gcc version dependent, at least on ppc\n- rtc: at91sam9: fix OF node leak in probe() error path (git-fixes).\n- s390/dasd: Fix redundant /proc/dasd* entries removal (bsc#1227694).\n- s390/dasd: Remove DMA alignment (LTC#208933 bsc#1230426 git-fixes).\n- s390/mm: Convert gmap_make_secure to use a folio (git-fixes bsc#1230562).\n- s390/mm: Convert make_page_secure to use a folio (git-fixes bsc#1230563).\n- s390: allow pte_offset_map_lock() to fail (git-fixes bsc#1230564).\n- scripts: kconfig: merge_config: config files: add a trailing newline (stable-fixes).\n- scripts: sphinx-pre-install: remove unnecessary double check for $cur_version (git-fixes).\n- scsi: ibmvfc: Add max_sectors module parameter (bsc#1216223).\n- scsi: lpfc: Change diagnostic log flag during receipt of unknown ELS cmds (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Copyright updates for 14.4.0.4 patches (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix overflow build issue (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unintentional double clearing of vmid_flag (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Fix unsolicited FLOGI kref imbalance when in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Remove redundant vport assignment when building an abort request (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update PRLO handling in direct attached topology (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Update lpfc version to 14.4.0.4 (bsc#1229429 jsc#PED-9899).\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths (bsc#1229429 jsc#PED-9899).\n- scsi: sd: Fix off-by-one error in sd_read_block_characteristics() (bsc#1223848).\n- selftests: lib: remove strscpy test (git-fixes).\n- selinux,smack: do not bypass permissions check in inode_setsecctx hook (stable-fixes).\n- soc: fsl: cpm1: tsa: Fix tsa_write8() (git-fixes).\n- soc: versatile: integrator: fix OF node leak in probe() error path (git-fixes).\n- spi: atmel-quadspi: Avoid overwriting delay register settings (git-fixes).\n- spi: atmel-quadspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: bcm63xx: Enable module autoloading (stable-fixes).\n- spi: bcm63xx: Fix module autoloading (git-fixes).\n- spi: meson-spicc: convert comma to semicolon (git-fixes).\n- spi: nxp-fspi: fix the KASAN report out-of-bounds bug (git-fixes).\n- spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ (git-fixes).\n- spi: ppc4xx: handle irq_of_parse_and_map() errors (git-fixes).\n- spi: rockchip: Resolve unbalanced runtime PM / system PM handling (git-fixes).\n- spi: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- spi: spi-fsl-lpspi: Undo runtime PM changes at driver exit time (git-fixes).\n- spi: spidev: Add an entry for elgin,jg10309-01 (stable-fixes).\n- spi: spidev: Add missing spi_device_id for jg10309-01 (git-fixes).\n- staging: iio: frequency: ad9834: Validate frequency parameter value (git-fixes).\n- supported.conf: mark adiantum and xctr crypto modules as supported (bsc#1231035)\n- thunderbolt: Fix XDomain rx_lanes_show and tx_lanes_show (git-fixes).\n- thunderbolt: Fix calculation of consumed USB3 bandwidth on a path (git-fixes).\n- thunderbolt: Fix rollback in tb_port_lane_bonding_enable() for lane 1 (git-fixes).\n- thunderbolt: There are only 5 basic router registers in pre-USB4 routers (git-fixes).\n- tomoyo: fallback to realpath if symlink's pathname does not exist (git-fixes).\n- tools/perf: Fix the string match for \"/tmp/perf-$PID.map\" files in dso__load (git-fixes).\n- tpm: Clean up TPM space after command failure (git-fixes).\n- tracing: Avoid possible softlockup in tracing_iter_reset() (git-fixes).\n- tty: rp2: Fix reset with non forgiving PCIe host bridges (git-fixes).\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (git-fixes).\n- usb: cdnsp: Fix incorrect usb_request status (git-fixes).\n- usb: dwc2: Skip clock gating on Broadcom SoCs (git-fixes).\n- usb: dwc2: drd: fix clock gating on USB role switch (git-fixes).\n- usb: dwc3: Avoid waking up gadget during startxfer (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (git-fixes).\n- usb: dwc3: core: Prevent USB core invalid event buffer address access (stable-fixes).\n- usb: dwc3: core: update LC timer as per USB Spec V3.2 (stable-fixes).\n- usb: gadget: aspeed_udc: validate endpoint index for ast udc (stable-fixes).\n- usb: typec: ucsi: Fix null pointer dereference in trace (stable-fixes).\n- usb: typec: ucsi: Wait 20ms before reading CCI after a reset (git-fixes).\n- usb: uas: set host status byte on data completion error (stable-fixes).\n- usbip: Do not submit special requests twice (stable-fixes).\n- usbnet: ipheth: add CDC NCM support (git-fixes).\n- usbnet: ipheth: do not stop RX on failing RX callback (git-fixes).\n- usbnet: ipheth: drop RX URBs with no payload (git-fixes).\n- usbnet: ipheth: fix carrier detection in modes 1 and 4 (git-fixes).\n- usbnet: ipheth: fix risk of NULL pointer deallocation (git-fixes).\n- usbnet: ipheth: race between ipheth_close and error handling (stable-fixes).\n- usbnet: ipheth: remove extraneous rx URB length check (git-fixes).\n- usbnet: ipheth: transmit URBs without trailing padding (git-fixes).\n- usbnet: modern method to get random MAC (git-fixes).\n- virtio-net: synchronize probe with ndo_set_features (git-fixes).\n- virtio_net: Fix napi_skb_cache_put warning (git-fixes).\n- virtio_net: fixing XDP for fully checksummed packets handling (git-fixes).\n- watchdog: imx_sc_wdt: Do not disable WDT in suspend (git-fixes).\n- wifi: ath11k: initialize 'ret' in ath11k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: fix BSS chan info request WMI command (git-fixes).\n- wifi: ath12k: fix firmware crash due to invalid peer nss (stable-fixes).\n- wifi: ath12k: fix invalid AMPDU factor calculation in ath12k_peer_assoc_h_he() (git-fixes).\n- wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_dp_rxdma_ring_sel_config_wcn7850() (stable-fixes).\n- wifi: ath12k: initialize 'ret' in ath12k_qmi_load_file_target_mem() (stable-fixes).\n- wifi: ath12k: match WMI BSS chan info structure with firmware definition (git-fixes).\n- wifi: ath9k: Remove error checks when creating debugfs entries (git-fixes).\n- wifi: brcmfmac: introducing fwil query functions (git-fixes).\n- wifi: brcmsmac: advertise MFP_CAPABLE to enable WPA3 (stable-fixes).\n- wifi: cfg80211: fix UBSAN noise in cfg80211_wext_siwscan() (git-fixes).\n- wifi: cfg80211: fix bug of mapping AF3x to incorrect User Priority (git-fixes).\n- wifi: cfg80211: fix two more possible UBSAN-detected off-by-one errors (git-fixes).\n- wifi: cfg80211: make hash table duplicates more survivable (stable-fixes).\n- wifi: cfg80211: restrict operation during radar detection (stable-fixes).\n- wifi: iwlwifi: clear trans-\u003estate earlier upon error (stable-fixes).\n- wifi: iwlwifi: lower message level for FW buffer destination (stable-fixes).\n- wifi: iwlwifi: mvm: do not wait for tx queues if firmware is dead (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() (stable-fixes).\n- wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation (stable-fixes).\n- wifi: iwlwifi: mvm: increase the time between ranging measurements (git-fixes).\n- wifi: iwlwifi: mvm: pause TCM when the firmware is stopped (stable-fixes).\n- wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check (stable-fixes).\n- wifi: mac80211: check ieee80211_bss_info_change_notify() against MLD (stable-fixes).\n- wifi: mac80211: do not use rate mask for offchannel TX either (git-fixes).\n- wifi: mac80211: fix the comeback long retry times (git-fixes).\n- wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() (stable-fixes).\n- wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() (git-fixes).\n- wifi: mt76: connac: fix checksum offload fields of connac3 RXD (git-fixes).\n- wifi: mt76: mt7603: fix mixed declarations and code (git-fixes).\n- wifi: mt76: mt7615: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7915: fix oops on non-dbdc mt7986 (git-fixes).\n- wifi: mt76: mt7915: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7921: Check devm_kasprintf() returned value (git-fixes).\n- wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change (stable-fixes).\n- wifi: mt76: mt7921: fix wrong UNII-4 freq range check for the channel usage (git-fixes).\n- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for clc (git-fixes).\n- wifi: mt76: mt7996: fix EHT beamforming capability check (git-fixes).\n- wifi: mt76: mt7996: fix HE and EHT beamforming capabilities (git-fixes).\n- wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he (git-fixes).\n- wifi: mt76: mt7996: fix traffic delay when switching back to working channel (git-fixes).\n- wifi: mt76: mt7996: fix uninitialized TLV data (git-fixes).\n- wifi: mt76: mt7996: fix wmm set of station interface to 3 (git-fixes).\n- wifi: mt76: mt7996: use hweight16 to get correct tx antenna (git-fixes).\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() (stable-fixes).\n- wifi: rtw88: 8822c: Fix reported RX band width (git-fixes).\n- wifi: rtw88: always wait for both firmware loading attempts (git-fixes).\n- wifi: rtw88: remove CPT execution branch never used (git-fixes).\n- wifi: rtw88: usb: schedule rx work after everything is set up (stable-fixes).\n- wifi: rtw89: ser: avoid multiple deinit on same CAM (stable-fixes).\n- wifi: rtw89: wow: prevent to send unexpected H2C during download Firmware (stable-fixes).\n- wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param (git-fixes).\n- x86/hyperv: fix kexec crash due to VP assist page corruption (git-fixes).\n- x86/kaslr: Expose and use the end of the physical memory address space (bsc#1229443).\n- x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382).\n- x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382).\n- x86/mm: Use lookup_address_in_pgd_attr() in show_fault_oops() (bsc#1221527).\n- x86/pat: Fix W^X violation false-positives when running as Xen PV guest (bsc#1221527).\n- x86/pat: Introduce lookup_address_in_pgd_attr() (bsc#1221527).\n- x86/pat: Restructure _lookup_address_cpa() (bsc#1221527).\n- xen/swiotlb: add alignment check for dma buffers (bsc#1229928).\n- xen/swiotlb: fix allocated size (git-fixes).\n- xen: add capability to remap non-RAM pages to different PFNs (bsc#1226003).\n- xen: allow mapping ACPI data using a different physical address (bsc#1226003).\n- xen: introduce generic helper checking for memory map conflicts (bsc#1226003).\n- xen: move checks for e820 conflicts further up (bsc#1226003).\n- xen: move max_pfn in xen_memory_setup() out of function scope (bsc#1226003).\n- xen: tolerate ACPI NVS memory overlapping with Xen allocated memory (bsc#1226003).\n- xen: use correct end address of kernel for conflict checking (bsc#1226003).\n- xfs: restrict when we try to align cow fork delalloc to cowextsz hints (git-fixes).\n- xhci: Set quirky xHC PCI hosts to D3 _after_ stopping and freeing them (git-fixes).\n- xz: cleanup CRC32 edits from 2018 (git-fixes).\n","status":"published","published":"2025-02-03T09:05:12Z","modified":"2026-03-23T04:48:52.78816Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"USN-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-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-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-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"},{"id":"USN-7288-1","title":"linux, linux-lowlatency vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\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  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50202, CVE-2024-50208, CVE-2024-50265, CVE-2024-41080,\nCVE-2024-50101, CVE-2024-39497, CVE-2024-50153, CVE-2024-50162,\nCVE-2024-50150, CVE-2024-50115, CVE-2024-53066, CVE-2024-50279,\nCVE-2024-50116, CVE-2024-50218, CVE-2024-53104, CVE-2024-50086,\nCVE-2024-50154, CVE-2024-50244, CVE-2024-50074, CVE-2024-50278,\nCVE-2024-50262, CVE-2024-50168, CVE-2024-50134, CVE-2024-53063,\nCVE-2024-50236, CVE-2024-50082, CVE-2024-50234, CVE-2024-50247,\nCVE-2024-50282, CVE-2024-50267, CVE-2024-40965, CVE-2024-50229,\nCVE-2024-50110, CVE-2024-35887, CVE-2024-50302, CVE-2024-50036,\nCVE-2024-50209, CVE-2024-50287, CVE-2024-50245, CVE-2024-50072,\nCVE-2024-50301, CVE-2024-50201, CVE-2024-53097, CVE-2024-40953,\nCVE-2024-50085, CVE-2024-50299, CVE-2024-50292, CVE-2024-50269,\nCVE-2024-50182, CVE-2024-50233, CVE-2024-53088, CVE-2024-50259,\nCVE-2024-50232, CVE-2024-53055, CVE-2024-50195, CVE-2024-50273,\nCVE-2024-42291, CVE-2024-50192, CVE-2024-50251, CVE-2024-50193,\nCVE-2024-50142, CVE-2024-53101, CVE-2024-50205, CVE-2024-26718,\nCVE-2024-50167, CVE-2024-50010, CVE-2024-50230, CVE-2024-41066,\nCVE-2024-50194, CVE-2024-50148, CVE-2024-50151, CVE-2024-50127,\nCVE-2024-50160, CVE-2023-52913, CVE-2024-53052, CVE-2024-50156,\nCVE-2024-50141, CVE-2024-50103, CVE-2024-50296, CVE-2024-50257,\nCVE-2024-50199, CVE-2024-50128, CVE-2024-50058, CVE-2024-50099,\nCVE-2024-50290, CVE-2024-53042, CVE-2024-50295, CVE-2024-50268,\nCVE-2024-50163, CVE-2024-53058, CVE-2024-50185, CVE-2024-50117,\nCVE-2024-50237, CVE-2024-50083, CVE-2024-50131, CVE-2024-50196,\nCVE-2024-42252, CVE-2024-50143, CVE-2024-50171, CVE-2024-50249,\nCVE-2024-53059, CVE-2024-50198, CVE-2024-53061)\n","status":"published","published":"2025-02-24T17:45:13Z","modified":"2026-10-29T20:02:44.375545195Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7288-2","title":"linux-lowlatency-hwe-5.15 vulnerabilities","description":"\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\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  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50151, CVE-2024-50195, CVE-2024-50117, CVE-2024-53104,\nCVE-2024-50171, CVE-2024-53059, CVE-2024-50160, CVE-2024-50163,\nCVE-2024-50103, CVE-2024-50245, CVE-2024-50282, CVE-2024-50233,\nCVE-2024-50218, CVE-2024-50201, CVE-2024-53058, CVE-2024-50115,\nCVE-2024-53101, CVE-2024-50268, CVE-2024-50127, CVE-2024-50182,\nCVE-2024-50148, CVE-2024-50295, CVE-2024-53061, CVE-2024-50232,\nCVE-2024-50010, CVE-2024-50273, CVE-2024-50267, CVE-2024-50198,\nCVE-2024-53097, CVE-2024-50150, CVE-2024-50278, CVE-2024-50301,\nCVE-2024-50290, CVE-2024-50185, CVE-2024-50036, CVE-2024-50296,\nCVE-2024-50082, CVE-2024-50058, CVE-2024-53063, CVE-2024-50192,\nCVE-2024-50208, CVE-2024-53052, CVE-2024-50162, CVE-2024-50247,\nCVE-2024-50302, CVE-2024-50153, CVE-2024-50143, CVE-2024-41080,\nCVE-2024-50287, CVE-2024-39497, CVE-2024-50156, CVE-2024-42252,\nCVE-2024-53055, CVE-2024-50265, CVE-2024-50230, CVE-2024-50269,\nCVE-2024-50167, CVE-2024-50237, CVE-2024-50168, CVE-2023-52913,\nCVE-2024-35887, CVE-2024-50299, CVE-2024-53088, CVE-2024-50209,\nCVE-2024-50234, CVE-2024-50131, CVE-2024-50141, CVE-2024-40965,\nCVE-2024-41066, CVE-2024-50251, CVE-2024-50292, CVE-2024-50194,\nCVE-2024-50085, CVE-2024-50154, CVE-2024-50202, CVE-2024-50074,\nCVE-2024-50199, CVE-2024-50110, CVE-2024-26718, CVE-2024-50205,\nCVE-2024-53042, CVE-2024-50279, CVE-2024-50101, CVE-2024-50116,\nCVE-2024-50236, CVE-2024-50083, CVE-2024-50262, CVE-2024-40953,\nCVE-2024-50142, CVE-2024-50128, CVE-2024-50099, CVE-2024-50086,\nCVE-2024-42291, CVE-2024-50257, CVE-2024-50229, CVE-2024-50134,\nCVE-2024-50244, CVE-2024-50249, CVE-2024-50193, CVE-2024-50072,\nCVE-2024-50259, CVE-2024-50196, CVE-2024-53066)\n","status":"published","published":"2025-02-25T11:30:39Z","modified":"2026-10-29T20:02:37.167178476Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7289-1","title":"linux-azure, linux-azure-fde, linux-gkeop, linux-nvidia, linux-oracle vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50196, CVE-2024-50199, CVE-2024-53055, CVE-2024-53101,\nCVE-2024-50160, CVE-2024-50257, CVE-2024-50148, CVE-2024-50182,\nCVE-2024-50162, CVE-2024-50249, CVE-2024-50127, CVE-2024-50115,\nCVE-2024-50192, CVE-2024-50218, CVE-2024-50086, CVE-2024-50262,\nCVE-2024-50201, CVE-2024-50082, CVE-2024-50110, CVE-2023-52913,\nCVE-2024-50290, CVE-2024-50269, CVE-2024-50208, CVE-2024-50103,\nCVE-2024-50194, CVE-2024-50237, CVE-2024-50245, CVE-2024-50128,\nCVE-2024-53052, CVE-2024-50117, CVE-2024-42252, CVE-2024-50233,\nCVE-2024-50058, CVE-2024-50229, CVE-2024-40965, CVE-2024-50265,\nCVE-2024-50143, CVE-2024-50205, CVE-2024-50131, CVE-2024-50236,\nCVE-2024-53066, CVE-2024-50268, CVE-2024-41066, CVE-2024-53088,\nCVE-2024-50209, CVE-2024-40953, CVE-2024-50168, CVE-2024-50010,\nCVE-2024-50195, CVE-2024-50171, CVE-2024-53058, CVE-2024-50267,\nCVE-2024-53061, CVE-2024-53042, CVE-2024-53104, CVE-2024-50247,\nCVE-2024-50101, CVE-2024-53063, CVE-2024-50167, CVE-2024-50273,\nCVE-2024-50163, CVE-2024-50085, CVE-2024-50154, CVE-2024-50301,\nCVE-2024-50259, CVE-2024-50292, CVE-2024-50185, CVE-2024-26718,\nCVE-2024-50116, CVE-2024-50302, CVE-2024-50083, CVE-2024-50299,\nCVE-2024-50036, CVE-2024-50251, CVE-2024-50202, CVE-2024-50099,\nCVE-2024-50279, CVE-2024-50232, CVE-2024-53059, CVE-2024-50153,\nCVE-2024-50156, CVE-2024-41080, CVE-2024-50193, CVE-2024-50287,\nCVE-2024-50141, CVE-2024-50296, CVE-2024-50230, CVE-2024-50074,\nCVE-2024-50234, CVE-2024-50142, CVE-2024-42291, CVE-2024-50151,\nCVE-2024-50295, CVE-2024-50150, CVE-2024-50282, CVE-2024-50278,\nCVE-2024-50198, CVE-2024-53097, CVE-2024-50244, CVE-2024-50134,\nCVE-2024-39497, CVE-2024-50072, CVE-2024-35887)\n","status":"published","published":"2025-02-24T18:13:51Z","modified":"2026-10-29T20:03:15.186245747Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7289-2","title":"linux-azure-5.15, linux-azure-fde-5.15, linux-oracle-5.15 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50269, CVE-2024-50208, CVE-2024-53101, CVE-2024-50257,\nCVE-2024-50110, CVE-2024-39497, CVE-2024-50116, CVE-2024-50153,\nCVE-2024-50143, CVE-2023-52913, CVE-2024-53042, CVE-2024-41066,\nCVE-2024-42252, CVE-2024-50247, CVE-2024-50131, CVE-2024-50182,\nCVE-2024-50279, CVE-2024-50209, CVE-2024-50163, CVE-2024-50265,\nCVE-2024-50010, CVE-2024-50171, CVE-2024-50295, CVE-2024-53088,\nCVE-2024-50142, CVE-2024-50058, CVE-2024-50195, CVE-2024-50232,\nCVE-2024-50141, CVE-2024-50117, CVE-2024-50229, CVE-2024-53061,\nCVE-2024-50074, CVE-2024-50282, CVE-2024-50296, CVE-2024-50218,\nCVE-2024-50259, CVE-2024-26718, CVE-2024-50134, CVE-2024-50150,\nCVE-2024-50301, CVE-2024-40953, CVE-2024-42291, CVE-2024-50086,\nCVE-2024-50198, CVE-2024-50194, CVE-2024-50168, CVE-2024-50196,\nCVE-2024-50262, CVE-2024-50290, CVE-2024-50036, CVE-2024-50156,\nCVE-2024-53066, CVE-2024-50245, CVE-2024-50278, CVE-2024-50127,\nCVE-2024-53055, CVE-2024-50287, CVE-2024-53052, CVE-2024-35887,\nCVE-2024-50199, CVE-2024-50205, CVE-2024-50273, CVE-2024-50185,\nCVE-2024-50201, CVE-2024-50072, CVE-2024-50234, CVE-2024-50101,\nCVE-2024-50103, CVE-2024-50302, CVE-2024-50251, CVE-2024-53104,\nCVE-2024-50083, CVE-2024-50292, CVE-2024-50236, CVE-2024-50230,\nCVE-2024-50085, CVE-2024-50162, CVE-2024-50193, CVE-2024-50267,\nCVE-2024-50192, CVE-2024-50148, CVE-2024-50167, CVE-2024-50249,\nCVE-2024-50268, CVE-2024-53058, CVE-2024-41080, CVE-2024-50233,\nCVE-2024-53097, CVE-2024-50244, CVE-2024-50160, CVE-2024-50299,\nCVE-2024-50115, CVE-2024-53059, CVE-2024-50099, CVE-2024-50154,\nCVE-2024-53063, CVE-2024-50237, CVE-2024-50128, CVE-2024-40965,\nCVE-2024-50151, CVE-2024-50082, CVE-2024-50202)\n","status":"published","published":"2025-02-25T11:50:00Z","modified":"2026-10-29T20:03:30.921481162Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7289-3","title":"linux-ibm vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50117, CVE-2024-50230, CVE-2024-50131, CVE-2024-50128,\nCVE-2024-50142, CVE-2024-50141, CVE-2024-50267, CVE-2024-41066,\nCVE-2024-50236, CVE-2024-50205, CVE-2024-50202, CVE-2024-50209,\nCVE-2024-50148, CVE-2024-50171, CVE-2024-50074, CVE-2024-50268,\nCVE-2024-50265, CVE-2024-50160, CVE-2024-50143, CVE-2024-50296,\nCVE-2024-50101, CVE-2024-50103, CVE-2024-39497, CVE-2024-50151,\nCVE-2024-50127, CVE-2024-50150, CVE-2024-50229, CVE-2024-50115,\nCVE-2024-50058, CVE-2024-50292, CVE-2024-50010, CVE-2024-50247,\nCVE-2024-50110, CVE-2024-53088, CVE-2024-50116, CVE-2024-26718,\nCVE-2024-53097, CVE-2024-50192, CVE-2024-50234, CVE-2024-41080,\nCVE-2024-42291, CVE-2024-50195, CVE-2024-40965, CVE-2024-50278,\nCVE-2024-50290, CVE-2024-50162, CVE-2024-53066, CVE-2024-50085,\nCVE-2024-50099, CVE-2024-50237, CVE-2024-50156, CVE-2024-50185,\nCVE-2024-50273, CVE-2024-50302, CVE-2024-50249, CVE-2024-50208,\nCVE-2024-50232, CVE-2024-50287, CVE-2024-50262, CVE-2024-50194,\nCVE-2024-40953, CVE-2024-50083, CVE-2024-50082, CVE-2024-53063,\nCVE-2024-50086, CVE-2024-50193, CVE-2024-50282, CVE-2024-50201,\nCVE-2024-50134, CVE-2024-53061, CVE-2024-50299, CVE-2024-50279,\nCVE-2024-50198, CVE-2024-53104, CVE-2024-50244, CVE-2024-50167,\nCVE-2024-53052, CVE-2024-50196, CVE-2024-50182, CVE-2024-35887,\nCVE-2024-53042, CVE-2023-52913, CVE-2024-53055, CVE-2024-50301,\nCVE-2024-42252, CVE-2024-50259, CVE-2024-50218, CVE-2024-50168,\nCVE-2024-50245, CVE-2024-50163, CVE-2024-50036, CVE-2024-50154,\nCVE-2024-53059, CVE-2024-50257, CVE-2024-53101, CVE-2024-50295,\nCVE-2024-50269, CVE-2024-53058, CVE-2024-50072, CVE-2024-50251,\nCVE-2024-50153, CVE-2024-50233, CVE-2024-50199)\n","status":"published","published":"2025-02-25T19:06:39Z","modified":"2026-10-29T20:03:13.300984105Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7289-4","title":"linux-intel-iotg, linux-intel-iotg-5.15 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50082, CVE-2024-50134, CVE-2024-50142, CVE-2023-52913,\nCVE-2024-50205, CVE-2024-50127, CVE-2024-50208, CVE-2024-50143,\nCVE-2024-50163, CVE-2024-53059, CVE-2024-50282, CVE-2024-50279,\nCVE-2024-50296, CVE-2024-50295, CVE-2024-50010, CVE-2024-53088,\nCVE-2024-50128, CVE-2024-50290, CVE-2024-50099, CVE-2024-50234,\nCVE-2024-50154, CVE-2024-53052, CVE-2024-50116, CVE-2024-50168,\nCVE-2024-50086, CVE-2024-50267, CVE-2024-50156, CVE-2024-50110,\nCVE-2024-50103, CVE-2024-50192, CVE-2024-40953, CVE-2024-50085,\nCVE-2024-50247, CVE-2024-50257, CVE-2024-50237, CVE-2024-50185,\nCVE-2024-50198, CVE-2024-50229, CVE-2024-50171, CVE-2024-50259,\nCVE-2024-50209, CVE-2024-50233, CVE-2024-35887, CVE-2024-50251,\nCVE-2024-50141, CVE-2024-53061, CVE-2024-50232, CVE-2024-50167,\nCVE-2024-50201, CVE-2024-50193, CVE-2024-50269, CVE-2024-39497,\nCVE-2024-50036, CVE-2024-50299, CVE-2024-50072, CVE-2024-53101,\nCVE-2024-50262, CVE-2024-50194, CVE-2024-50202, CVE-2024-50101,\nCVE-2024-50151, CVE-2024-41080, CVE-2024-42291, CVE-2024-50245,\nCVE-2024-50278, CVE-2024-50195, CVE-2024-50265, CVE-2024-50074,\nCVE-2024-53063, CVE-2024-50131, CVE-2024-53058, CVE-2024-50160,\nCVE-2024-50287, CVE-2024-40965, CVE-2024-50273, CVE-2024-50268,\nCVE-2024-50302, CVE-2024-50218, CVE-2024-50199, CVE-2024-50196,\nCVE-2024-50083, CVE-2024-50244, CVE-2024-50117, CVE-2024-50058,\nCVE-2024-53055, CVE-2024-50182, CVE-2024-53097, CVE-2024-50236,\nCVE-2024-50162, CVE-2024-50301, CVE-2024-50249, CVE-2024-50292,\nCVE-2024-50150, CVE-2024-50153, CVE-2024-50115, CVE-2024-26718,\nCVE-2024-53104, CVE-2024-42252, CVE-2024-53066, CVE-2024-50148,\nCVE-2024-53042, CVE-2024-50230, CVE-2024-41066)\n","status":"published","published":"2025-02-27T16:31:09Z","modified":"2026-10-29T20:02:43.41763328Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7291-1","title":"linux-gcp, linux-gcp-5.15, linux-gke vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50083, CVE-2024-50134, CVE-2024-53063, CVE-2024-50131,\nCVE-2024-53104, CVE-2024-50182, CVE-2024-50279, CVE-2024-50185,\nCVE-2024-42252, CVE-2024-50247, CVE-2024-50128, CVE-2024-53088,\nCVE-2024-50082, CVE-2024-50160, CVE-2024-50103, CVE-2024-50259,\nCVE-2024-35887, CVE-2024-50251, CVE-2024-50150, CVE-2024-53066,\nCVE-2024-50262, CVE-2024-41066, CVE-2024-50086, CVE-2024-42291,\nCVE-2024-53061, CVE-2024-50245, CVE-2024-41080, CVE-2024-50244,\nCVE-2024-50198, CVE-2024-50282, CVE-2024-50074, CVE-2024-50195,\nCVE-2024-50010, CVE-2024-50202, CVE-2024-50295, CVE-2024-50162,\nCVE-2024-50273, CVE-2024-50233, CVE-2024-50302, CVE-2024-50201,\nCVE-2024-50278, CVE-2024-50036, CVE-2024-50296, CVE-2024-53058,\nCVE-2024-50116, CVE-2024-50163, CVE-2024-50292, CVE-2024-53097,\nCVE-2024-50196, CVE-2024-50058, CVE-2024-53042, CVE-2024-53059,\nCVE-2024-50110, CVE-2024-50151, CVE-2024-26718, CVE-2024-50099,\nCVE-2024-50115, CVE-2024-50171, CVE-2024-50237, CVE-2024-50154,\nCVE-2024-50199, CVE-2024-50192, CVE-2024-50167, CVE-2024-50127,\nCVE-2024-50142, CVE-2024-50229, CVE-2024-50269, CVE-2024-53055,\nCVE-2024-40965, CVE-2024-50265, CVE-2024-50143, CVE-2024-40953,\nCVE-2024-50117, CVE-2024-50156, CVE-2024-50193, CVE-2024-50072,\nCVE-2024-50230, CVE-2024-50287, CVE-2024-50148, CVE-2024-50208,\nCVE-2024-50267, CVE-2024-50290, CVE-2024-50085, CVE-2024-50168,\nCVE-2024-50205, CVE-2024-50232, CVE-2024-50153, CVE-2024-39497,\nCVE-2024-50194, CVE-2024-50101, CVE-2024-50257, CVE-2024-50249,\nCVE-2024-50299, CVE-2024-50234, CVE-2024-50209, CVE-2024-50141,\nCVE-2023-52913, CVE-2024-50301, CVE-2024-50236, CVE-2024-53052,\nCVE-2024-53101, CVE-2024-50268, CVE-2024-50218)\n","status":"published","published":"2025-02-26T13:42:33Z","modified":"2026-10-29T20:02:54.921076297Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7293-1","title":"linux, linux-hwe-5.4 vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\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  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - TPM device driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - USB Device Class drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - BPF subsystem;\n  - Perf events;\n  - Arbitrary resource management;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Netlink;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - KVM core;\n(CVE-2024-50184, CVE-2024-47706, CVE-2024-49962, CVE-2024-35887,\nCVE-2024-53101, CVE-2024-50199, CVE-2024-47709, CVE-2024-50074,\nCVE-2024-41066, CVE-2024-42252, CVE-2024-43863, CVE-2024-47685,\nCVE-2024-47756, CVE-2024-50282, CVE-2024-50143, CVE-2024-50116,\nCVE-2024-47699, CVE-2024-47698, CVE-2024-50301, CVE-2024-47723,\nCVE-2024-50296, CVE-2024-50007, CVE-2024-49952, CVE-2024-50233,\nCVE-2023-52458, CVE-2024-53063, CVE-2024-49975, CVE-2024-50099,\nCVE-2024-47742, CVE-2024-50033, CVE-2024-50218, CVE-2024-50096,\nCVE-2024-49981, CVE-2024-40911, CVE-2024-47697, CVE-2024-49894,\nCVE-2024-49955, CVE-2024-53104, CVE-2024-49963, CVE-2024-49883,\nCVE-2024-47710, CVE-2024-49959, CVE-2024-49948, CVE-2024-50302,\nCVE-2024-49867, CVE-2024-50234, CVE-2024-49902, CVE-2024-50006,\nCVE-2024-47672, CVE-2024-50202, CVE-2024-49851, CVE-2024-35896,\nCVE-2024-50150, CVE-2024-53061, CVE-2024-46854, CVE-2024-50279,\nCVE-2024-50278, CVE-2024-50180, CVE-2024-50148, CVE-2024-50194,\nCVE-2024-50008, CVE-2024-47740, CVE-2024-49938, CVE-2024-46853,\nCVE-2024-50134, CVE-2024-44931, CVE-2024-46849, CVE-2024-49973,\nCVE-2024-50142, CVE-2024-49879, CVE-2024-50269, CVE-2024-50230,\nCVE-2024-49896, CVE-2024-49985, CVE-2024-50151, CVE-2024-40965,\nCVE-2024-50251, CVE-2024-49995, CVE-2024-47713, CVE-2023-52917,\nCVE-2024-50205, CVE-2024-49900, CVE-2024-49877, CVE-2024-47679,\nCVE-2024-50040, CVE-2024-47701, CVE-2024-50168, CVE-2024-49882,\nCVE-2024-50059, CVE-2024-49958, CVE-2024-50171, CVE-2021-47469,\nCVE-2024-50024, CVE-2024-47749, CVE-2024-50236, CVE-2024-50127,\nCVE-2024-50290, CVE-2024-47692, CVE-2024-50167, CVE-2024-49944,\nCVE-2024-50262, CVE-2024-47674, CVE-2024-49957, CVE-2024-50237,\nCVE-2024-47712, CVE-2024-49949, CVE-2024-40953, CVE-2024-50267,\nCVE-2024-53059, CVE-2024-49966, CVE-2024-47737, CVE-2024-49868,\nCVE-2024-50179, CVE-2024-50035, CVE-2024-49997, CVE-2024-50044,\nCVE-2024-49903, CVE-2024-46731, CVE-2024-49965, CVE-2024-50287,\nCVE-2024-50265, CVE-2024-47696, CVE-2024-47670, CVE-2024-47684,\nCVE-2024-41016, CVE-2024-49878, CVE-2024-49924, CVE-2024-50082,\nCVE-2024-50273, CVE-2024-38544, CVE-2024-47747, CVE-2024-50299,\nCVE-2024-50195, CVE-2024-50131, CVE-2024-50039, CVE-2024-49982,\nCVE-2024-49892, CVE-2024-50229, CVE-2024-50117, CVE-2024-49860,\nCVE-2024-47757, CVE-2024-53066, CVE-2024-47671, CVE-2024-50045)\n","status":"published","published":"2025-02-26T13:08:17Z","modified":"2026-10-29T20:03:15.899727892Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7294-1","title":"linux-azure, linux-azure-5.4, linux-bluefield, linux-gcp, linux-gcp-5.4, linux-ibm-5.4 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - TPM device driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - USB Device Class drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - BPF subsystem;\n  - Perf events;\n  - Arbitrary resource management;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Netlink;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - KVM core;\n(CVE-2024-40953, CVE-2024-50008, CVE-2024-40911, CVE-2024-47685,\nCVE-2024-49957, CVE-2024-38544, CVE-2024-49860, CVE-2024-46854,\nCVE-2024-49882, CVE-2024-44931, CVE-2024-47696, CVE-2021-47469,\nCVE-2024-41066, CVE-2024-46849, CVE-2024-47671, CVE-2024-49975,\nCVE-2024-49958, CVE-2024-50006, CVE-2024-50287, CVE-2024-50099,\nCVE-2024-50035, CVE-2024-46731, CVE-2024-49878, CVE-2024-50045,\nCVE-2023-52917, CVE-2024-47712, CVE-2024-49883, CVE-2024-50040,\nCVE-2024-50234, CVE-2024-50184, CVE-2024-50279, CVE-2024-49948,\nCVE-2024-50044, CVE-2024-50230, CVE-2024-47710, CVE-2024-50233,\nCVE-2024-49900, CVE-2024-49938, CVE-2024-50236, CVE-2024-47737,\nCVE-2024-47670, CVE-2024-41016, CVE-2024-50150, CVE-2024-50301,\nCVE-2024-50116, CVE-2024-47706, CVE-2024-40965, CVE-2024-50205,\nCVE-2024-49963, CVE-2024-47756, CVE-2024-53066, CVE-2024-49879,\nCVE-2024-53059, CVE-2024-50229, CVE-2024-50131, CVE-2024-53104,\nCVE-2024-50167, CVE-2024-47723, CVE-2024-47709, CVE-2024-42252,\nCVE-2024-50267, CVE-2024-50218, CVE-2024-47698, CVE-2024-50039,\nCVE-2024-47701, CVE-2024-50202, CVE-2024-50262, CVE-2024-50194,\nCVE-2024-46853, CVE-2024-47699, CVE-2024-47697, CVE-2024-50117,\nCVE-2024-49982, CVE-2024-47742, CVE-2024-50127, CVE-2024-50142,\nCVE-2024-49955, CVE-2024-47747, CVE-2024-49981, CVE-2024-47679,\nCVE-2024-50237, CVE-2024-43863, CVE-2024-47672, CVE-2024-50273,\nCVE-2024-49903, CVE-2024-50180, CVE-2024-50148, CVE-2024-50059,\nCVE-2024-50299, CVE-2024-47740, CVE-2024-47749, CVE-2024-49892,\nCVE-2024-50074, CVE-2024-49973, CVE-2024-50296, CVE-2024-49962,\nCVE-2024-50024, CVE-2024-49924, CVE-2024-49877, CVE-2024-49959,\nCVE-2024-49997, CVE-2024-50168, CVE-2024-47757, CVE-2024-49902,\nCVE-2024-49868, CVE-2023-52458, CVE-2024-47692, CVE-2024-49894,\nCVE-2024-50096, CVE-2024-47684, CVE-2024-50143, CVE-2024-35896,\nCVE-2024-47713, CVE-2024-50151, CVE-2024-50082, CVE-2024-50171,\nCVE-2024-53063, CVE-2024-50007, CVE-2024-49985, CVE-2024-49944,\nCVE-2024-50302, CVE-2024-49949, CVE-2024-50033, CVE-2024-49952,\nCVE-2024-49995, CVE-2024-50278, CVE-2024-53061, CVE-2024-50195,\nCVE-2024-49966, CVE-2024-50265, CVE-2024-50282, CVE-2024-35887,\nCVE-2024-49896, CVE-2024-50290, CVE-2024-53101, CVE-2024-49867,\nCVE-2024-50199, CVE-2024-49965, CVE-2024-50179, CVE-2024-47674,\nCVE-2024-50134, CVE-2024-50269, CVE-2024-49851, CVE-2024-50251)\n","status":"published","published":"2025-02-26T15:19:31Z","modified":"2026-10-29T20:04:10.783087975Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7294-2","title":"linux-aws, linux-oracle, linux-oracle-5.4 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - TPM device driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - USB Device Class drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - BPF subsystem;\n  - Perf events;\n  - Arbitrary resource management;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Netlink;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - KVM core;\n(CVE-2024-53063, CVE-2024-50236, CVE-2024-47699, CVE-2024-50044,\nCVE-2024-49877, CVE-2024-47692, CVE-2024-50116, CVE-2024-47679,\nCVE-2024-50134, CVE-2024-50045, CVE-2024-50301, CVE-2024-40965,\nCVE-2024-47684, CVE-2024-49944, CVE-2024-43863, CVE-2024-50059,\nCVE-2024-50007, CVE-2024-49973, CVE-2024-50251, CVE-2024-47674,\nCVE-2024-49982, CVE-2024-50143, CVE-2024-49883, CVE-2024-49851,\nCVE-2024-44931, CVE-2024-49949, CVE-2024-47747, CVE-2024-46853,\nCVE-2024-50233, CVE-2024-49924, CVE-2024-50033, CVE-2024-50024,\nCVE-2024-49995, CVE-2024-47737, CVE-2024-50194, CVE-2024-47712,\nCVE-2024-50273, CVE-2024-50229, CVE-2024-49896, CVE-2024-50199,\nCVE-2024-50202, CVE-2024-49868, CVE-2024-50035, CVE-2024-50184,\nCVE-2024-49882, CVE-2024-49962, CVE-2024-50299, CVE-2024-35887,\nCVE-2024-50287, CVE-2024-50265, CVE-2024-50148, CVE-2024-47757,\nCVE-2024-47742, CVE-2024-49902, CVE-2024-50302, CVE-2024-50096,\nCVE-2024-49952, CVE-2024-50099, CVE-2024-49963, CVE-2024-49900,\nCVE-2024-46731, CVE-2024-50131, CVE-2024-47723, CVE-2024-50237,\nCVE-2024-50269, CVE-2024-50142, CVE-2024-49867, CVE-2024-49985,\nCVE-2024-47670, CVE-2024-50008, CVE-2024-49938, CVE-2024-49878,\nCVE-2024-49955, CVE-2024-53104, CVE-2024-49894, CVE-2024-50039,\nCVE-2024-50279, CVE-2024-50006, CVE-2024-40953, CVE-2024-50180,\nCVE-2024-49860, CVE-2024-50117, CVE-2024-47701, CVE-2024-47698,\nCVE-2024-50171, CVE-2024-50151, CVE-2024-50082, CVE-2024-50290,\nCVE-2024-49975, CVE-2024-49903, CVE-2024-38544, CVE-2024-50218,\nCVE-2024-49948, CVE-2024-50282, CVE-2024-49965, CVE-2024-49959,\nCVE-2024-42252, CVE-2024-47749, CVE-2024-47756, CVE-2024-47672,\nCVE-2024-50127, CVE-2024-46854, CVE-2024-50230, CVE-2024-41066,\nCVE-2024-49957, CVE-2024-47713, CVE-2023-52458, CVE-2024-50167,\nCVE-2024-49997, CVE-2024-47685, CVE-2024-49879, CVE-2024-53059,\nCVE-2024-53101, CVE-2024-49958, CVE-2024-47710, CVE-2024-47706,\nCVE-2024-50074, CVE-2024-50296, CVE-2024-49892, CVE-2024-46849,\nCVE-2024-50205, CVE-2024-50168, CVE-2024-50267, CVE-2024-50262,\nCVE-2024-47709, CVE-2024-50195, CVE-2024-35896, CVE-2024-47696,\nCVE-2024-47740, CVE-2024-40911, CVE-2024-49966, CVE-2021-47469,\nCVE-2024-49981, CVE-2024-50234, CVE-2024-50179, CVE-2024-47697,\nCVE-2024-50150, CVE-2023-52917, CVE-2024-50040, CVE-2024-53061,\nCVE-2024-50278, CVE-2024-47671, CVE-2024-53066, CVE-2024-41016)\n","status":"published","published":"2025-02-27T17:37:19Z","modified":"2026-10-29T20:02:58.080696937Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7294-3","title":"linux-ibm vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - TPM device driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - USB Device Class drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - BPF subsystem;\n  - Perf events;\n  - Arbitrary resource management;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Netlink;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - KVM core;\n(CVE-2024-47698, CVE-2024-49868, CVE-2024-50006, CVE-2024-40965,\nCVE-2024-50233, CVE-2024-47671, CVE-2024-49944, CVE-2024-47684,\nCVE-2024-50134, CVE-2024-50279, CVE-2024-50302, CVE-2024-40953,\nCVE-2024-50234, CVE-2024-41066, CVE-2024-50040, CVE-2024-47701,\nCVE-2024-50033, CVE-2024-50007, CVE-2024-50143, CVE-2024-41016,\nCVE-2024-53059, CVE-2024-50195, CVE-2024-50202, CVE-2024-47749,\nCVE-2024-47685, CVE-2024-50267, CVE-2024-49965, CVE-2024-49903,\nCVE-2024-49883, CVE-2024-50035, CVE-2024-46849, CVE-2024-53061,\nCVE-2024-50151, CVE-2024-49995, CVE-2024-49867, CVE-2024-49962,\nCVE-2024-50218, CVE-2024-50039, CVE-2024-50148, CVE-2024-49900,\nCVE-2024-50287, CVE-2024-50150, CVE-2024-49879, CVE-2024-47757,\nCVE-2024-49997, CVE-2024-50045, CVE-2024-47742, CVE-2024-47679,\nCVE-2024-53063, CVE-2024-49878, CVE-2024-49860, CVE-2024-35896,\nCVE-2024-40911, CVE-2024-42252, CVE-2024-47723, CVE-2024-47674,\nCVE-2024-47737, CVE-2024-50282, CVE-2024-44931, CVE-2024-49938,\nCVE-2024-49963, CVE-2024-50290, CVE-2024-49958, CVE-2021-47469,\nCVE-2024-47670, CVE-2024-50116, CVE-2024-50262, CVE-2024-50082,\nCVE-2023-52917, CVE-2024-50117, CVE-2024-50131, CVE-2024-47699,\nCVE-2024-49896, CVE-2024-49957, CVE-2024-49952, CVE-2024-50273,\nCVE-2024-50171, CVE-2024-50237, CVE-2024-49955, CVE-2024-50230,\nCVE-2024-50194, CVE-2024-50278, CVE-2024-50127, CVE-2024-53066,\nCVE-2024-38544, CVE-2024-49902, CVE-2024-49892, CVE-2024-46854,\nCVE-2024-49966, CVE-2024-50167, CVE-2024-47697, CVE-2024-49985,\nCVE-2024-47696, CVE-2024-50024, CVE-2024-50251, CVE-2024-47740,\nCVE-2024-49882, CVE-2024-49851, CVE-2024-50059, CVE-2024-49973,\nCVE-2024-35887, CVE-2024-50296, CVE-2024-47706, CVE-2024-50044,\nCVE-2024-47712, CVE-2024-50301, CVE-2024-47709, CVE-2024-49975,\nCVE-2024-49877, CVE-2024-47710, CVE-2024-50269, CVE-2024-46731,\nCVE-2024-50099, CVE-2024-50184, CVE-2024-50299, CVE-2024-50008,\nCVE-2024-50265, CVE-2024-49948, CVE-2024-50229, CVE-2024-50168,\nCVE-2024-49894, CVE-2024-47692, CVE-2024-50074, CVE-2024-47713,\nCVE-2024-49924, CVE-2024-53104, CVE-2024-50205, CVE-2024-47672,\nCVE-2024-50096, CVE-2024-47747, CVE-2024-50199, CVE-2023-52458,\nCVE-2024-49959, CVE-2024-50236, CVE-2024-53101, CVE-2024-43863,\nCVE-2024-46853, CVE-2024-50179, CVE-2024-49981, CVE-2024-47756,\nCVE-2024-49949, CVE-2024-50142, CVE-2024-49982, CVE-2024-50180)\n","status":"published","published":"2025-02-28T10:36:14Z","modified":"2026-10-29T20:02:39.748989739Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7294-4","title":"linux-kvm vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - TPM device driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - USB Device Class drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - BPF subsystem;\n  - Perf events;\n  - Arbitrary resource management;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Netlink;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - KVM core;\n(CVE-2024-47672, CVE-2024-50273, CVE-2024-49896, CVE-2024-49962,\nCVE-2024-50007, CVE-2024-47706, CVE-2024-50302, CVE-2024-50299,\nCVE-2024-49959, CVE-2024-49973, CVE-2024-47674, CVE-2024-50143,\nCVE-2024-50278, CVE-2024-50184, CVE-2024-49892, CVE-2024-50044,\nCVE-2024-47701, CVE-2024-49860, CVE-2024-47692, CVE-2024-49948,\nCVE-2024-50039, CVE-2024-50006, CVE-2024-53066, CVE-2024-49944,\nCVE-2024-43863, CVE-2024-47756, CVE-2024-50082, CVE-2024-50237,\nCVE-2024-50262, CVE-2024-49900, CVE-2024-50059, CVE-2024-50194,\nCVE-2024-53063, CVE-2024-47697, CVE-2024-49975, CVE-2024-50033,\nCVE-2024-50148, CVE-2024-50116, CVE-2024-50168, CVE-2024-47747,\nCVE-2024-53104, CVE-2024-50218, CVE-2024-50279, CVE-2024-46853,\nCVE-2024-46854, CVE-2024-50127, CVE-2024-49995, CVE-2024-50282,\nCVE-2024-47685, CVE-2024-50296, CVE-2024-50099, CVE-2024-50199,\nCVE-2024-49879, CVE-2024-50287, CVE-2024-50265, CVE-2024-50269,\nCVE-2024-47698, CVE-2024-49868, CVE-2024-50035, CVE-2024-47709,\nCVE-2024-50024, CVE-2024-50301, CVE-2024-50142, CVE-2024-53059,\nCVE-2024-50008, CVE-2024-49997, CVE-2024-46849, CVE-2024-50290,\nCVE-2024-40953, CVE-2024-49985, CVE-2024-47737, CVE-2024-49883,\nCVE-2024-50040, CVE-2024-49958, CVE-2024-50205, CVE-2024-47723,\nCVE-2024-50180, CVE-2024-50229, CVE-2024-50131, CVE-2024-47713,\nCVE-2024-49963, CVE-2024-44931, CVE-2024-47742, CVE-2024-49903,\nCVE-2024-49949, CVE-2024-47684, CVE-2024-35896, CVE-2024-41016,\nCVE-2024-49955, CVE-2024-50134, CVE-2024-49938, CVE-2024-49877,\nCVE-2024-49981, CVE-2024-50234, CVE-2024-50096, CVE-2024-49952,\nCVE-2024-49957, CVE-2024-49982, CVE-2024-47710, CVE-2024-53061,\nCVE-2024-50267, CVE-2024-47712, CVE-2024-50195, CVE-2024-50236,\nCVE-2024-47749, CVE-2024-47757, CVE-2024-49894, CVE-2024-50179,\nCVE-2024-42252, CVE-2024-49851, CVE-2024-53101, CVE-2024-38544,\nCVE-2024-50117, CVE-2023-52917, CVE-2024-50045, CVE-2024-40911,\nCVE-2024-49882, CVE-2024-49867, CVE-2024-50202, CVE-2024-49878,\nCVE-2024-50251, CVE-2024-50151, CVE-2024-50171, CVE-2024-47740,\nCVE-2024-49965, CVE-2023-52458, CVE-2024-50233, CVE-2024-40965,\nCVE-2024-49924, CVE-2024-50167, CVE-2024-47670, CVE-2021-47469,\nCVE-2024-35887, CVE-2024-50074, CVE-2024-46731, CVE-2024-47671,\nCVE-2024-41066, CVE-2024-49966, CVE-2024-50150, CVE-2024-50230,\nCVE-2024-47696, CVE-2024-47699, CVE-2024-47679, CVE-2024-49902)\n","status":"published","published":"2025-03-03T18:44:51Z","modified":"2026-10-29T20:02:39.463543956Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7295-1","title":"linux-xilinx-zynqmp vulnerabilities","description":"Ye Zhang and Nicolas Wu discovered that the io_uring subsystem in the Linux\nkernel did not properly handle locking for rings with IOPOLL, leading to a\ndouble-free vulnerability. A local attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2023-21400)\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  - Block layer subsystem;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - TPM device driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - TTY drivers;\n  - USB Device Class drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - BPF subsystem;\n  - Perf events;\n  - Arbitrary resource management;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - Netlink;\n  - SCTP protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - KVM core;\n(CVE-2024-50116, CVE-2024-43863, CVE-2024-47757, CVE-2024-50236,\nCVE-2024-53104, CVE-2024-47701, CVE-2024-46854, CVE-2024-50024,\nCVE-2024-46849, CVE-2024-50035, CVE-2024-50262, CVE-2024-50184,\nCVE-2023-52458, CVE-2024-47696, CVE-2024-49957, CVE-2024-47692,\nCVE-2024-50007, CVE-2024-49867, CVE-2024-49900, CVE-2024-50167,\nCVE-2024-47697, CVE-2024-53164, CVE-2024-50179, CVE-2024-44931,\nCVE-2024-50301, CVE-2024-50218, CVE-2024-49995, CVE-2024-47742,\nCVE-2024-47756, CVE-2021-47469, CVE-2024-49982, CVE-2024-50229,\nCVE-2024-49851, CVE-2024-47685, CVE-2024-50265, CVE-2024-50195,\nCVE-2024-47747, CVE-2024-50273, CVE-2024-53066, CVE-2024-49924,\nCVE-2024-49963, CVE-2024-50287, CVE-2024-49948, CVE-2024-47674,\nCVE-2024-40967, CVE-2024-35887, CVE-2024-50044, CVE-2024-50099,\nCVE-2024-53059, CVE-2024-50171, CVE-2024-50082, CVE-2024-41066,\nCVE-2024-50202, CVE-2024-49868, CVE-2024-49952, CVE-2024-49965,\nCVE-2024-50296, CVE-2024-49903, CVE-2024-50194, CVE-2024-47712,\nCVE-2024-53101, CVE-2024-40953, CVE-2024-47706, CVE-2024-49958,\nCVE-2024-50059, CVE-2024-47713, CVE-2024-47737, CVE-2024-49902,\nCVE-2024-49959, CVE-2024-53103, CVE-2024-49973, CVE-2024-50045,\nCVE-2024-47710, CVE-2024-50131, CVE-2024-47671, CVE-2024-50205,\nCVE-2024-47672, CVE-2024-50234, CVE-2024-50233, CVE-2024-49860,\nCVE-2024-50127, CVE-2024-50168, CVE-2024-49962, CVE-2024-38544,\nCVE-2024-47749, CVE-2024-49949, CVE-2024-50096, CVE-2024-50033,\nCVE-2024-49955, CVE-2024-49938, CVE-2024-47698, CVE-2024-50230,\nCVE-2024-47723, CVE-2024-49877, CVE-2024-50180, CVE-2024-49879,\nCVE-2024-53061, CVE-2024-47679, CVE-2024-49892, CVE-2024-50299,\nCVE-2024-49896, CVE-2024-40911, CVE-2024-50134, CVE-2024-47740,\nCVE-2024-50039, CVE-2024-49985, CVE-2024-41016, CVE-2024-50269,\nCVE-2024-50290, CVE-2024-49882, CVE-2024-47699, CVE-2023-52917,\nCVE-2024-50267, CVE-2024-50151, CVE-2024-50251, CVE-2024-49966,\nCVE-2024-49981, CVE-2024-50008, CVE-2024-50006, CVE-2024-50117,\nCVE-2024-47670, CVE-2024-46853, CVE-2024-50282, CVE-2024-46731,\nCVE-2024-35896, CVE-2024-53141, CVE-2024-50279, CVE-2024-50040,\nCVE-2024-49883, CVE-2024-49878, CVE-2024-47684, CVE-2024-49997,\nCVE-2024-53063, CVE-2024-50302, CVE-2024-42252, CVE-2024-47709,\nCVE-2024-49894, CVE-2024-50142, CVE-2024-49944, CVE-2024-50278,\nCVE-2024-50150, CVE-2024-40965, CVE-2024-50237, CVE-2024-49975,\nCVE-2024-50074, CVE-2024-50143, CVE-2024-50199, CVE-2024-50148)\n","status":"published","published":"2025-02-26T15:14:57Z","modified":"2026-10-29T20:02:39.133836836Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7305-1","title":"linux-raspi vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50128, CVE-2024-50099, CVE-2024-50269, CVE-2024-50287,\nCVE-2024-42291, CVE-2024-50142, CVE-2024-50085, CVE-2024-50273,\nCVE-2024-26718, CVE-2024-50143, CVE-2024-50208, CVE-2024-41080,\nCVE-2024-50101, CVE-2024-50150, CVE-2024-53101, CVE-2024-50141,\nCVE-2024-50115, CVE-2024-50301, CVE-2024-53104, CVE-2024-41066,\nCVE-2024-50194, CVE-2024-50167, CVE-2024-53059, CVE-2024-50103,\nCVE-2024-50110, CVE-2024-50131, CVE-2024-50249, CVE-2024-50196,\nCVE-2024-50182, CVE-2024-50257, CVE-2024-50148, CVE-2024-50278,\nCVE-2024-50074, CVE-2024-50296, CVE-2024-50295, CVE-2024-50193,\nCVE-2024-50195, CVE-2024-42252, CVE-2024-50086, CVE-2024-50072,\nCVE-2024-50082, CVE-2024-50134, CVE-2024-50163, CVE-2024-50232,\nCVE-2024-53097, CVE-2024-50127, CVE-2024-50268, CVE-2024-39497,\nCVE-2024-50116, CVE-2024-50302, CVE-2024-50153, CVE-2024-50185,\nCVE-2023-52913, CVE-2024-40953, CVE-2024-50209, CVE-2024-53088,\nCVE-2024-50151, CVE-2024-35887, CVE-2024-53058, CVE-2024-40965,\nCVE-2024-50198, CVE-2024-50259, CVE-2024-50292, CVE-2024-50267,\nCVE-2024-50162, CVE-2024-50154, CVE-2024-50083, CVE-2024-50218,\nCVE-2024-50036, CVE-2024-53066, CVE-2024-50251, CVE-2024-53042,\nCVE-2024-50234, CVE-2024-50247, CVE-2024-50245, CVE-2024-50201,\nCVE-2024-50279, CVE-2024-50171, CVE-2024-50156, CVE-2024-50236,\nCVE-2024-53055, CVE-2024-50229, CVE-2024-50199, CVE-2024-50262,\nCVE-2024-50058, CVE-2024-53052, CVE-2024-50290, CVE-2024-50168,\nCVE-2024-50237, CVE-2024-53061, CVE-2024-50282, CVE-2024-50192,\nCVE-2024-50230, CVE-2024-50233, CVE-2024-50265, CVE-2024-50117,\nCVE-2024-50202, CVE-2024-50205, CVE-2024-50244, CVE-2024-50299,\nCVE-2024-53063, CVE-2024-50160, CVE-2024-50010)\n","status":"published","published":"2025-02-26T11:45:35Z","modified":"2026-10-29T20:02:38.421405713Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7308-1","title":"linux-aws vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - VMware vSockets driver;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50141, CVE-2024-53101, CVE-2024-50301, CVE-2024-50082,\nCVE-2024-39497, CVE-2024-50245, CVE-2024-50302, CVE-2024-35887,\nCVE-2024-50205, CVE-2024-50153, CVE-2024-50154, CVE-2024-50279,\nCVE-2024-50074, CVE-2024-50168, CVE-2024-50128, CVE-2024-53141,\nCVE-2024-50290, CVE-2024-50292, CVE-2024-50218, CVE-2024-50193,\nCVE-2024-50209, CVE-2024-53088, CVE-2024-50058, CVE-2024-50116,\nCVE-2024-50199, CVE-2024-50083, CVE-2024-50265, CVE-2024-53058,\nCVE-2024-50244, CVE-2024-50195, CVE-2024-41066, CVE-2024-50151,\nCVE-2024-50229, CVE-2024-42291, CVE-2024-40965, CVE-2024-50160,\nCVE-2024-53097, CVE-2024-50134, CVE-2024-53164, CVE-2024-50295,\nCVE-2024-50267, CVE-2024-50251, CVE-2024-50198, CVE-2024-53042,\nCVE-2024-40953, CVE-2024-50167, CVE-2024-50010, CVE-2024-42252,\nCVE-2024-53055, CVE-2024-50259, CVE-2024-50110, CVE-2024-50208,\nCVE-2024-50249, CVE-2024-50148, CVE-2024-50269, CVE-2024-50182,\nCVE-2024-50115, CVE-2024-50287, CVE-2024-50142, CVE-2024-53103,\nCVE-2024-50099, CVE-2024-50234, CVE-2024-50282, CVE-2024-50185,\nCVE-2024-50247, CVE-2024-50257, CVE-2024-50036, CVE-2024-50268,\nCVE-2024-50127, CVE-2024-50230, CVE-2024-50278, CVE-2024-50273,\nCVE-2024-26718, CVE-2024-50086, CVE-2024-50262, CVE-2024-50236,\nCVE-2024-50117, CVE-2024-50237, CVE-2024-53104, CVE-2024-50194,\nCVE-2024-50192, CVE-2024-53061, CVE-2024-53052, CVE-2024-50202,\nCVE-2024-41080, CVE-2024-50143, CVE-2023-52913, CVE-2024-50296,\nCVE-2024-50085, CVE-2024-50196, CVE-2024-50072, CVE-2024-50171,\nCVE-2024-50103, CVE-2024-50101, CVE-2024-50156, CVE-2024-50201,\nCVE-2024-50233, CVE-2024-53059, CVE-2024-53066, CVE-2024-53063,\nCVE-2024-50150, CVE-2024-50131, CVE-2024-50163, CVE-2024-50162,\nCVE-2024-50299, CVE-2024-50232)\n","status":"published","published":"2025-02-27T16:46:04Z","modified":"2026-10-29T20:02:39.331215046Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7331-1","title":"linux-hwe-5.15 vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\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  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - STMicroelectronics network drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - Direct Digital Synthesis drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Network file system (NFS) client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Timer substystem drivers;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - XFRM subsystem;\n  - Key management;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - KVM core;\n(CVE-2024-50163, CVE-2024-53104, CVE-2024-50287, CVE-2024-41066,\nCVE-2024-53066, CVE-2024-53097, CVE-2024-50229, CVE-2024-50142,\nCVE-2024-50182, CVE-2024-50156, CVE-2024-50195, CVE-2024-50232,\nCVE-2024-53063, CVE-2024-50134, CVE-2024-50103, CVE-2024-50110,\nCVE-2024-50115, CVE-2024-50233, CVE-2024-50202, CVE-2024-50268,\nCVE-2024-50171, CVE-2024-50234, CVE-2024-50083, CVE-2024-53061,\nCVE-2024-50194, CVE-2024-40953, CVE-2024-50143, CVE-2024-50278,\nCVE-2024-50257, CVE-2024-56672, CVE-2024-50141, CVE-2024-50128,\nCVE-2024-50117, CVE-2024-50292, CVE-2024-50148, CVE-2024-53055,\nCVE-2024-35887, CVE-2024-50236, CVE-2024-50249, CVE-2024-50282,\nCVE-2024-50218, CVE-2023-52913, CVE-2024-50262, CVE-2024-50269,\nCVE-2024-50010, CVE-2024-50299, CVE-2024-39497, CVE-2024-50296,\nCVE-2024-53052, CVE-2024-53058, CVE-2024-50201, CVE-2024-42291,\nCVE-2024-50036, CVE-2024-50154, CVE-2024-50196, CVE-2024-50251,\nCVE-2024-41080, CVE-2024-50074, CVE-2024-50205, CVE-2024-50131,\nCVE-2024-42252, CVE-2024-50082, CVE-2024-50273, CVE-2024-50072,\nCVE-2024-50301, CVE-2024-53088, CVE-2024-50058, CVE-2024-50085,\nCVE-2024-50167, CVE-2024-50150, CVE-2024-50185, CVE-2024-50208,\nCVE-2024-50151, CVE-2024-50086, CVE-2024-50127, CVE-2024-50153,\nCVE-2024-53042, CVE-2024-50162, CVE-2024-50237, CVE-2024-50290,\nCVE-2024-40965, CVE-2024-50193, CVE-2024-50245, CVE-2024-53059,\nCVE-2024-53101, CVE-2024-50295, CVE-2024-50259, CVE-2024-50192,\nCVE-2024-50265, CVE-2024-50279, CVE-2024-50116, CVE-2024-26718,\nCVE-2024-50101, CVE-2024-50168, CVE-2024-50267, CVE-2024-50198,\nCVE-2024-50230, CVE-2024-50199, CVE-2024-50099, CVE-2024-50247,\nCVE-2024-50302, CVE-2024-50160, CVE-2024-50209, CVE-2024-50244)\n","status":"published","published":"2025-03-05T14:27:44Z","modified":"2026-10-29T20:02:39.60289002Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7388-1","title":"linux-aws-5.15, linux-kvm vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Virtio block driver;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCPI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - Timer subsystem;\n  - VLANs driver;\n  - LAPB network protocol;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Kernel CPU control infrastructure;\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Netlink;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Key management;\n  - SELinux security module;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM core;\n(CVE-2024-56622, CVE-2024-42252, CVE-2024-53101, CVE-2025-21664,\nCVE-2024-50168, CVE-2024-53214, CVE-2024-56670, CVE-2024-53146,\nCVE-2024-50302, CVE-2024-56629, CVE-2024-53680, CVE-2024-53124,\nCVE-2024-56610, CVE-2024-50259, CVE-2024-47408, CVE-2024-53217,\nCVE-2025-21683, CVE-2024-50196, CVE-2025-21694, CVE-2024-56596,\nCVE-2024-53161, CVE-2024-53061, CVE-2024-57940, CVE-2024-41066,\nCVE-2024-53122, CVE-2024-56776, CVE-2024-50268, CVE-2024-53184,\nCVE-2024-53088, CVE-2024-56590, CVE-2024-50182, CVE-2024-56705,\nCVE-2024-50103, CVE-2024-57938, CVE-2024-53155, CVE-2024-50282,\nCVE-2024-50209, CVE-2024-53150, CVE-2024-56532, CVE-2024-57910,\nCVE-2024-56678, CVE-2024-53181, CVE-2024-50230, CVE-2024-42291,\nCVE-2024-50233, CVE-2024-53130, CVE-2024-56756, CVE-2024-53113,\nCVE-2024-56623, CVE-2024-41080, CVE-2024-53197, CVE-2024-53142,\nCVE-2024-50251, CVE-2024-50237, CVE-2024-47143, CVE-2024-56633,\nCVE-2024-57889, CVE-2024-53127, CVE-2024-46871, CVE-2024-56640,\nCVE-2024-50193, CVE-2024-53148, CVE-2025-21669, CVE-2024-53690,\nCVE-2024-50279, CVE-2024-56780, CVE-2024-56769, CVE-2024-53125,\nCVE-2024-53052, CVE-2024-56601, CVE-2024-56778, CVE-2024-50198,\nCVE-2025-21665, CVE-2024-53227, CVE-2024-40953, CVE-2024-50295,\nCVE-2024-53194, CVE-2024-56777, CVE-2024-56770, CVE-2025-21697,\nCVE-2024-57904, CVE-2024-56691, CVE-2024-56787, CVE-2024-57948,\nCVE-2024-53140, CVE-2024-50051, CVE-2025-21648, CVE-2024-56754,\nCVE-2024-50156, CVE-2024-50205, CVE-2024-57911, CVE-2024-50290,\nCVE-2024-56715, CVE-2024-56643, CVE-2024-49974, CVE-2024-50287,\nCVE-2024-50162, CVE-2024-57849, CVE-2024-50142, CVE-2024-53198,\nCVE-2024-56568, CVE-2024-56704, CVE-2024-35887, CVE-2024-57908,\nCVE-2024-56767, CVE-2024-56701, CVE-2025-21680, CVE-2024-57913,\nCVE-2024-50171, CVE-2024-56558, CVE-2024-50121, CVE-2024-50036,\nCVE-2024-53180, CVE-2024-53096, CVE-2024-57897, CVE-2024-56746,\nCVE-2024-55881, CVE-2024-57874, CVE-2024-56774, CVE-2024-57946,\nCVE-2024-56531, CVE-2024-56698, CVE-2024-56650, CVE-2025-21637,\nCVE-2024-50242, CVE-2024-49996, CVE-2024-53136, CVE-2024-56575,\nCVE-2024-56642, CVE-2024-56763, CVE-2024-57802, CVE-2024-57929,\nCVE-2024-56726, CVE-2024-56615, CVE-2024-56619, CVE-2024-50234,\nCVE-2024-50299, CVE-2024-56569, CVE-2024-57792, CVE-2024-50150,\nCVE-2024-56728, CVE-2024-53173, CVE-2024-56630, CVE-2025-21639,\nCVE-2024-53183, CVE-2024-56681, CVE-2024-46809, CVE-2024-53165,\nCVE-2024-53215, CVE-2024-50296, CVE-2024-50267, CVE-2024-53097,\nCVE-2024-56369, CVE-2024-56578, CVE-2024-56562, CVE-2025-21699,\nCVE-2024-50134, CVE-2024-56589, CVE-2024-50232, CVE-2024-53685,\nCVE-2024-50265, CVE-2024-53206, CVE-2024-50257, CVE-2024-57925,\nCVE-2024-50269, CVE-2024-56570, CVE-2024-50278, CVE-2024-56595,\nCVE-2024-56720, CVE-2024-50085, CVE-2024-50201, CVE-2024-56693,\nCVE-2023-52913, CVE-2025-21666, CVE-2024-50249, CVE-2024-50247,\nCVE-2024-47730, CVE-2024-49925, CVE-2025-21690, CVE-2024-56606,\nCVE-2024-53172, CVE-2024-53119, CVE-2024-56602, CVE-2024-50262,\nCVE-2024-50127, CVE-2024-50115, CVE-2024-57901, CVE-2024-50185,\nCVE-2024-53058, CVE-2025-21631, CVE-2024-56574, CVE-2024-56539,\nCVE-2025-21678, CVE-2024-56659, CVE-2024-56594, CVE-2024-56708,\nCVE-2024-56662, CVE-2024-55916, CVE-2024-53042, CVE-2024-50229,\nCVE-2024-56616, CVE-2024-50074, CVE-2024-57838, CVE-2024-50160,\nCVE-2024-50218, CVE-2024-56597, CVE-2024-36476, CVE-2024-49571,\nCVE-2024-53112, CVE-2024-50128, CVE-2024-53157, CVE-2024-56747,\nCVE-2024-56779, CVE-2024-50143, CVE-2024-42315, CVE-2024-56688,\nCVE-2024-57903, CVE-2024-50283, CVE-2025-21640, CVE-2024-53099,\nCVE-2024-57902, CVE-2024-57912, CVE-2024-56567, CVE-2024-56637,\nCVE-2024-50086, CVE-2024-56679, CVE-2024-56598, CVE-2024-50236,\nCVE-2024-56593, CVE-2024-50058, CVE-2024-53239, CVE-2024-57906,\nCVE-2024-43098, CVE-2024-53138, CVE-2024-50208, CVE-2024-49950,\nCVE-2024-53174, CVE-2024-50072, CVE-2024-45828, CVE-2024-56759,\nCVE-2024-56533, CVE-2024-50117, CVE-2024-53131, CVE-2024-47707,\nCVE-2025-21689, CVE-2025-21636, CVE-2024-56605, CVE-2024-57807,\nCVE-2024-56724, CVE-2024-57841, CVE-2024-53120, CVE-2024-50304,\nCVE-2024-56748, CVE-2024-58087, CVE-2024-57917, CVE-2024-44938,\nCVE-2024-57896, CVE-2024-56600, CVE-2024-57922, CVE-2024-53066,\nCVE-2024-56634, CVE-2024-53171, CVE-2024-56700, CVE-2024-57939,\nCVE-2024-53151, CVE-2024-50202, CVE-2024-56572, CVE-2024-40965,\nCVE-2024-56716, CVE-2024-46841, CVE-2024-50292, CVE-2024-57907,\nCVE-2024-53145, CVE-2024-50192, CVE-2024-53055, CVE-2025-21646,\nCVE-2024-56690, CVE-2024-57882, CVE-2024-56576, CVE-2024-50301,\nCVE-2024-53059, CVE-2024-56745, CVE-2024-57890, CVE-2024-50055,\nCVE-2024-56739, CVE-2024-50099, CVE-2024-50131, CVE-2024-50194,\nCVE-2024-57884, CVE-2024-43900, CVE-2024-52332, CVE-2024-57931,\nCVE-2024-50163, CVE-2024-53063, CVE-2024-53104, CVE-2024-57951,\nCVE-2025-21638, CVE-2024-53129, CVE-2024-56781, CVE-2024-50195,\nCVE-2024-56548, CVE-2024-56603, CVE-2024-56586, CVE-2024-50167,\nCVE-2024-56648, CVE-2024-56581, CVE-2024-53158, CVE-2024-56587,\nCVE-2024-49998, CVE-2024-50148, CVE-2024-56694, CVE-2024-50110,\nCVE-2024-50244, CVE-2024-46784, CVE-2024-50273, CVE-2024-50116,\nCVE-2024-56614, CVE-2024-50154, CVE-2024-56672, CVE-2025-21692,\nCVE-2024-56636, CVE-2024-56626, CVE-2024-50010, CVE-2024-39497,\nCVE-2024-50101, CVE-2024-50141, CVE-2024-57791, CVE-2024-50082,\nCVE-2024-53226, CVE-2024-53135, CVE-2024-50275, CVE-2024-56723,\nCVE-2024-53121, CVE-2024-50199, CVE-2024-56631, CVE-2024-50083,\nCVE-2024-50245, CVE-2025-21687, CVE-2024-50151, CVE-2022-49034,\nCVE-2024-57900, CVE-2024-53156, CVE-2024-36899, CVE-2024-50153,\nCVE-2024-53237, CVE-2024-56645, CVE-2024-26718, CVE-2024-57892,\nCVE-2025-21653, CVE-2024-56627, CVE-2024-48881, CVE-2024-56625,\nCVE-2024-57850, CVE-2024-56644, CVE-2024-56785)\n","status":"published","published":"2025-03-27T22:01:51Z","modified":"2026-10-29T20:03:00.421447553Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7389-1","title":"linux-nvidia-tegra, linux-nvidia-tegra-igx vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Virtio block driver;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCPI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - Timer subsystem;\n  - VLANs driver;\n  - LAPB network protocol;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Kernel CPU control infrastructure;\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Netlink;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Key management;\n  - SELinux security module;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM core;\n(CVE-2025-21640, CVE-2024-56625, CVE-2024-53104, CVE-2024-53055,\nCVE-2024-26718, CVE-2024-53180, CVE-2024-50257, CVE-2024-53174,\nCVE-2024-53680, CVE-2024-56670, CVE-2024-56606, CVE-2024-53156,\nCVE-2024-53112, CVE-2024-57940, CVE-2024-57807, CVE-2024-50259,\nCVE-2024-53172, CVE-2024-53214, CVE-2024-50275, CVE-2024-56770,\nCVE-2025-21666, CVE-2024-53101, CVE-2024-56630, CVE-2025-21638,\nCVE-2024-50199, CVE-2024-56705, CVE-2024-56619, CVE-2024-50115,\nCVE-2024-50209, CVE-2024-50116, CVE-2024-57908, CVE-2024-50242,\nCVE-2024-50128, CVE-2024-50247, CVE-2024-56626, CVE-2024-56693,\nCVE-2024-56648, CVE-2024-56745, CVE-2024-42252, CVE-2024-53088,\nCVE-2024-50251, CVE-2024-57889, CVE-2024-53150, CVE-2024-53066,\nCVE-2024-56569, CVE-2025-21697, CVE-2024-50185, CVE-2024-53158,\nCVE-2024-50168, CVE-2024-41066, CVE-2024-53145, CVE-2024-50171,\nCVE-2024-53135, CVE-2024-42315, CVE-2024-56615, CVE-2024-50230,\nCVE-2024-50299, CVE-2024-53140, CVE-2024-56704, CVE-2024-56533,\nCVE-2024-50121, CVE-2024-39497, CVE-2024-50282, CVE-2024-56715,\nCVE-2024-56779, CVE-2024-56769, CVE-2024-56570, CVE-2024-55916,\nCVE-2024-56637, CVE-2025-21694, CVE-2024-56691, CVE-2024-50301,\nCVE-2024-50156, CVE-2024-57903, CVE-2025-21636, CVE-2024-49974,\nCVE-2024-56532, CVE-2024-50201, CVE-2024-57929, CVE-2024-56590,\nCVE-2024-57882, CVE-2024-57925, CVE-2024-56759, CVE-2024-56726,\nCVE-2024-53215, CVE-2024-53121, CVE-2024-57912, CVE-2024-53119,\nCVE-2024-57931, CVE-2024-41080, CVE-2024-35887, CVE-2024-53173,\nCVE-2024-50245, CVE-2024-50267, CVE-2024-56627, CVE-2024-50085,\nCVE-2024-56756, CVE-2024-50232, CVE-2024-56636, CVE-2024-56581,\nCVE-2024-53194, CVE-2025-21689, CVE-2024-53226, CVE-2024-53239,\nCVE-2024-56662, CVE-2024-50205, CVE-2024-53127, CVE-2024-56586,\nCVE-2024-56603, CVE-2024-53122, CVE-2025-21699, CVE-2024-56568,\nCVE-2024-57884, CVE-2024-53113, CVE-2024-56574, CVE-2025-21669,\nCVE-2024-53125, CVE-2024-56748, CVE-2024-56575, CVE-2024-56640,\nCVE-2024-57901, CVE-2022-49034, CVE-2024-56728, CVE-2024-57910,\nCVE-2024-40965, CVE-2024-36899, CVE-2024-50131, CVE-2024-42291,\nCVE-2024-50233, CVE-2024-57791, CVE-2024-57948, CVE-2024-56633,\nCVE-2025-21653, CVE-2024-50287, CVE-2024-56724, CVE-2024-57907,\nCVE-2024-49925, CVE-2024-47730, CVE-2024-46841, CVE-2024-56716,\nCVE-2024-44938, CVE-2024-49950, CVE-2024-53131, CVE-2024-46809,\nCVE-2024-50074, CVE-2024-50167, CVE-2024-53171, CVE-2024-57911,\nCVE-2025-21680, CVE-2024-53059, CVE-2024-53161, CVE-2024-47707,\nCVE-2025-21683, CVE-2024-56597, CVE-2024-53184, CVE-2024-56562,\nCVE-2024-47143, CVE-2024-50103, CVE-2024-53138, CVE-2025-21639,\nCVE-2024-50182, CVE-2024-36476, CVE-2024-50099, CVE-2024-50194,\nCVE-2024-50163, CVE-2024-43098, CVE-2023-52913, CVE-2024-56708,\nCVE-2024-53130, CVE-2024-56587, CVE-2024-57951, CVE-2024-57938,\nCVE-2024-57917, CVE-2024-53063, CVE-2024-50148, CVE-2024-50229,\nCVE-2024-56763, CVE-2024-50101, CVE-2024-57939, CVE-2024-57874,\nCVE-2024-56778, CVE-2024-56701, CVE-2024-56672, CVE-2024-56598,\nCVE-2024-45828, CVE-2024-50208, CVE-2024-53129, CVE-2024-56754,\nCVE-2024-50141, CVE-2024-56539, CVE-2024-56720, CVE-2024-53165,\nCVE-2024-50234, CVE-2024-53120, CVE-2024-50192, CVE-2024-50283,\nCVE-2024-50160, CVE-2024-57922, CVE-2024-53052, CVE-2024-48881,\nCVE-2024-56596, CVE-2024-50202, CVE-2025-21646, CVE-2024-50082,\nCVE-2024-50278, CVE-2024-57904, CVE-2024-56602, CVE-2024-57913,\nCVE-2024-50151, CVE-2025-21690, CVE-2024-53690, CVE-2024-56739,\nCVE-2024-56594, CVE-2024-53155, CVE-2024-56694, CVE-2024-56767,\nCVE-2024-50117, CVE-2024-56634, CVE-2024-47408, CVE-2024-53124,\nCVE-2024-50292, CVE-2024-56576, CVE-2024-57841, CVE-2024-57902,\nCVE-2024-57849, CVE-2024-50196, CVE-2024-56629, CVE-2024-57792,\nCVE-2024-56605, CVE-2024-57896, CVE-2025-21664, CVE-2024-53142,\nCVE-2025-21665, CVE-2024-50249, CVE-2024-50290, CVE-2024-56688,\nCVE-2024-53096, CVE-2024-53061, CVE-2024-56622, CVE-2024-50110,\nCVE-2024-56777, CVE-2024-58087, CVE-2024-56600, CVE-2024-56601,\nCVE-2024-56645, CVE-2024-56572, CVE-2024-56723, CVE-2024-50195,\nCVE-2024-56595, CVE-2024-56698, CVE-2024-57906, CVE-2024-52332,\nCVE-2024-53099, CVE-2024-56787, CVE-2025-21687, CVE-2024-53141,\nCVE-2024-53058, CVE-2024-49998, CVE-2024-53103, CVE-2024-56642,\nCVE-2024-50058, CVE-2024-53151, CVE-2024-50162, CVE-2024-53164,\nCVE-2024-56643, CVE-2024-56610, CVE-2024-50302, CVE-2024-57900,\nCVE-2024-50083, CVE-2024-50072, CVE-2024-53227, CVE-2024-53183,\nCVE-2024-56690, CVE-2024-50142, CVE-2024-50127, CVE-2024-50134,\nCVE-2024-56700, CVE-2024-53198, CVE-2024-56781, CVE-2024-57897,\nCVE-2024-56774, CVE-2024-50269, CVE-2025-21678, CVE-2024-46784,\nCVE-2024-53685, CVE-2024-56593, CVE-2024-50051, CVE-2024-57890,\nCVE-2024-53197, CVE-2024-50198, CVE-2024-50279, CVE-2024-57802,\nCVE-2024-56578, CVE-2024-50154, CVE-2024-56623, CVE-2024-56776,\nCVE-2024-56681, CVE-2024-53157, CVE-2024-57850, CVE-2024-57946,\nCVE-2024-53148, CVE-2024-53042, CVE-2024-53181, CVE-2024-57892,\nCVE-2024-50153, CVE-2024-50265, CVE-2025-21631, CVE-2025-21692,\nCVE-2024-56558, CVE-2024-56747, CVE-2024-50304, CVE-2024-50244,\nCVE-2024-43900, CVE-2024-56746, CVE-2024-56631, CVE-2024-56644,\nCVE-2024-50262, CVE-2024-49571, CVE-2024-50296, CVE-2024-56614,\nCVE-2024-50036, CVE-2024-50273, CVE-2024-56659, CVE-2024-56650,\nCVE-2024-50236, CVE-2024-50268, CVE-2025-21637, CVE-2025-21648,\nCVE-2024-53097, CVE-2024-56678, CVE-2024-56780, CVE-2024-50010,\nCVE-2024-46871, CVE-2024-50237, CVE-2024-57838, CVE-2024-49996,\nCVE-2024-50055, CVE-2024-50143, CVE-2024-53146, CVE-2024-50150,\nCVE-2024-50193, CVE-2024-56567, CVE-2024-50086, CVE-2024-50295,\nCVE-2024-50218, CVE-2024-40953, CVE-2024-56616, CVE-2024-56548,\nCVE-2024-56531, CVE-2024-56679, CVE-2024-56785, CVE-2024-53217,\nCVE-2024-53237, CVE-2024-56369, CVE-2024-55881, CVE-2024-56589)\n","status":"published","published":"2025-03-28T12:59:33Z","modified":"2026-10-29T20:02:58.796496495Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7390-1","title":"linux-xilinx-zynqmp vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Virtio block driver;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCPI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - TTY drivers;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - Timer subsystem;\n  - VLANs driver;\n  - LAPB network protocol;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Kernel CPU control infrastructure;\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - Netlink;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Key management;\n  - SELinux security module;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM core;\n(CVE-2024-50299, CVE-2024-50304, CVE-2024-50196, CVE-2024-56548,\nCVE-2024-56531, CVE-2024-56720, CVE-2024-58087, CVE-2024-50116,\nCVE-2024-56590, CVE-2024-56589, CVE-2024-53172, CVE-2025-21687,\nCVE-2024-57925, CVE-2024-56640, CVE-2024-57896, CVE-2024-56739,\nCVE-2024-56622, CVE-2024-53173, CVE-2024-56610, CVE-2024-56787,\nCVE-2025-21690, CVE-2024-50259, CVE-2024-50278, CVE-2024-53685,\nCVE-2024-50099, CVE-2024-56616, CVE-2024-53181, CVE-2024-56643,\nCVE-2024-49950, CVE-2024-53119, CVE-2024-50257, CVE-2024-56777,\nCVE-2024-49998, CVE-2024-56629, CVE-2024-56728, CVE-2024-56601,\nCVE-2024-56776, CVE-2024-46809, CVE-2024-53061, CVE-2024-50273,\nCVE-2024-45828, CVE-2024-53161, CVE-2024-56700, CVE-2024-50103,\nCVE-2024-50156, CVE-2024-53150, CVE-2024-50237, CVE-2024-46841,\nCVE-2024-56636, CVE-2024-56572, CVE-2024-50290, CVE-2024-57913,\nCVE-2024-56698, CVE-2024-56690, CVE-2024-56568, CVE-2024-57911,\nCVE-2024-49974, CVE-2024-47707, CVE-2024-53059, CVE-2024-50244,\nCVE-2024-57874, CVE-2024-56539, CVE-2024-53145, CVE-2024-56602,\nCVE-2024-50115, CVE-2024-56726, CVE-2024-53157, CVE-2024-41080,\nCVE-2024-57938, CVE-2024-56569, CVE-2024-50171, CVE-2024-57807,\nCVE-2024-57890, CVE-2024-53122, CVE-2024-56746, CVE-2024-53135,\nCVE-2024-53063, CVE-2024-57922, CVE-2024-53130, CVE-2024-53174,\nCVE-2024-56774, CVE-2024-56606, CVE-2024-56648, CVE-2024-50160,\nCVE-2024-50262, CVE-2024-50163, CVE-2024-53112, CVE-2024-50234,\nCVE-2024-56576, CVE-2025-21664, CVE-2024-53113, CVE-2024-56625,\nCVE-2024-50154, CVE-2024-56662, CVE-2024-56645, CVE-2024-56778,\nCVE-2024-40953, CVE-2024-50055, CVE-2024-40965, CVE-2024-56627,\nCVE-2024-43900, CVE-2024-56578, CVE-2024-50202, CVE-2024-56670,\nCVE-2024-56705, CVE-2024-53103, CVE-2024-57948, CVE-2024-53197,\nCVE-2024-56704, CVE-2024-50101, CVE-2024-53180, CVE-2024-56769,\nCVE-2024-53171, CVE-2024-56558, CVE-2024-53042, CVE-2024-50051,\nCVE-2024-42291, CVE-2024-39497, CVE-2024-53183, CVE-2024-43098,\nCVE-2024-57904, CVE-2024-56615, CVE-2024-50086, CVE-2024-53239,\nCVE-2024-50127, CVE-2024-50134, CVE-2024-53148, CVE-2024-47408,\nCVE-2024-50279, CVE-2024-50292, CVE-2024-53099, CVE-2024-50121,\nCVE-2024-56567, CVE-2024-53146, CVE-2024-53052, CVE-2024-53120,\nCVE-2024-56678, CVE-2024-50282, CVE-2024-50249, CVE-2024-56623,\nCVE-2024-56701, CVE-2024-56708, CVE-2024-56763, CVE-2024-50209,\nCVE-2025-21639, CVE-2024-50230, CVE-2024-53096, CVE-2024-47730,\nCVE-2024-42252, CVE-2024-57849, CVE-2024-56587, CVE-2024-56614,\nCVE-2024-56369, CVE-2024-57838, CVE-2025-21653, CVE-2024-57792,\nCVE-2024-53140, CVE-2024-56780, CVE-2024-50218, CVE-2024-56767,\nCVE-2024-49571, CVE-2024-57910, CVE-2024-50269, CVE-2024-56630,\nCVE-2024-52332, CVE-2024-56693, CVE-2024-50148, CVE-2025-21648,\nCVE-2024-49996, CVE-2024-50085, CVE-2024-56688, CVE-2024-53125,\nCVE-2024-53129, CVE-2024-55916, CVE-2024-57900, CVE-2024-57903,\nCVE-2024-57939, CVE-2024-50010, CVE-2024-50265, CVE-2023-52913,\nCVE-2024-36476, CVE-2024-56574, CVE-2025-21636, CVE-2024-57912,\nCVE-2024-56642, CVE-2024-50287, CVE-2024-36899, CVE-2024-53131,\nCVE-2024-56595, CVE-2024-53058, CVE-2024-46871, CVE-2024-56586,\nCVE-2024-53198, CVE-2025-21699, CVE-2024-50082, CVE-2024-53194,\nCVE-2024-57901, CVE-2024-50199, CVE-2024-57802, CVE-2024-53138,\nCVE-2024-53124, CVE-2024-50167, CVE-2024-56597, CVE-2024-50233,\nCVE-2024-49925, CVE-2024-56781, CVE-2024-53127, CVE-2025-21680,\nCVE-2024-53165, CVE-2024-53227, CVE-2024-56672, CVE-2024-55881,\nCVE-2024-53184, CVE-2024-50198, CVE-2024-42315, CVE-2024-57931,\nCVE-2024-56694, CVE-2024-57951, CVE-2024-56659, CVE-2024-50247,\nCVE-2024-53690, CVE-2024-56650, CVE-2024-57889, CVE-2024-53097,\nCVE-2024-50072, CVE-2024-50267, CVE-2024-53066, CVE-2024-50153,\nCVE-2024-50194, CVE-2024-56681, CVE-2025-21692, CVE-2024-50131,\nCVE-2024-57884, CVE-2024-56748, CVE-2024-48881, CVE-2024-56593,\nCVE-2024-50162, CVE-2024-44938, CVE-2024-50128, CVE-2024-50275,\nCVE-2025-21638, CVE-2024-56634, CVE-2024-56679, CVE-2024-47143,\nCVE-2024-50251, CVE-2024-56570, CVE-2024-53156, CVE-2024-50205,\nCVE-2024-56747, CVE-2024-53121, CVE-2024-50208, CVE-2024-57841,\nCVE-2024-56575, CVE-2024-57791, CVE-2024-57897, CVE-2024-56626,\nCVE-2024-35887, CVE-2024-50302, CVE-2024-50242, CVE-2024-56756,\nCVE-2024-53217, CVE-2025-21669, CVE-2024-56603, CVE-2024-56785,\nCVE-2024-57917, CVE-2024-50058, CVE-2024-57902, CVE-2024-53215,\nCVE-2024-50229, CVE-2024-50295, CVE-2024-56633, CVE-2024-50151,\nCVE-2024-53214, CVE-2024-50232, CVE-2024-53158, CVE-2024-56715,\nCVE-2024-50182, CVE-2025-21631, CVE-2024-53104, CVE-2024-53101,\nCVE-2024-57908, CVE-2024-53055, CVE-2024-50143, CVE-2025-21646,\nCVE-2024-56605, CVE-2025-21640, CVE-2024-56779, CVE-2024-50296,\nCVE-2024-50201, CVE-2024-56691, CVE-2024-57882, CVE-2024-53141,\nCVE-2024-56600, CVE-2025-21689, CVE-2024-26718, CVE-2024-56596,\nCVE-2024-53151, CVE-2024-50083, CVE-2024-50283, CVE-2024-56532,\nCVE-2024-53226, CVE-2024-56637, CVE-2024-50193, CVE-2024-56644,\nCVE-2025-21637, CVE-2024-56716, CVE-2024-53680, CVE-2024-57907,\nCVE-2022-49034, CVE-2024-50150, CVE-2024-56723, CVE-2025-21665,\nCVE-2024-56759, CVE-2024-50301, CVE-2024-57929, CVE-2024-53164,\nCVE-2024-56754, CVE-2024-53237, CVE-2025-21694, CVE-2024-56770,\nCVE-2024-50141, CVE-2024-50192, CVE-2024-56581, CVE-2024-57892,\nCVE-2024-53142, CVE-2024-50268, CVE-2024-53088, CVE-2025-21683,\nCVE-2024-56724, CVE-2024-41066, CVE-2024-46784, CVE-2024-50074,\nCVE-2024-57906, CVE-2024-57850, CVE-2024-50036, CVE-2024-57946,\nCVE-2024-50117, CVE-2024-56594, CVE-2024-56619, CVE-2024-56598,\nCVE-2024-56533, CVE-2024-56562, CVE-2024-57940, CVE-2024-56745,\nCVE-2024-53155, CVE-2024-50236, CVE-2025-21666, CVE-2025-21697,\nCVE-2024-50185, CVE-2024-56631, CVE-2024-50195, CVE-2024-50245,\nCVE-2024-50110, CVE-2025-21678, CVE-2024-50142)\n","status":"published","published":"2025-03-28T13:08:58Z","modified":"2026-10-29T20:02:51.902460451Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7393-1","title":"linux-fips 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\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Virtio block driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCPI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - USB Device Class drivers;\n  - USB Gadget drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - File systems infrastructure;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - Timer subsystem;\n  - VLANs driver;\n  - LAPB network protocol;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - Kernel init infrastructure;\n  - BPF subsystem;\n  - Kernel CPU control infrastructure;\n  - Perf events;\n  - Arbitrary resource management;\n  - Tracing infrastructure;\n  - Closures library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Netfilter;\n  - Netlink;\n  - NET/ROM layer;\n  - Packet sockets;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Key management;\n  - SELinux security module;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - Amlogic Meson SoC drivers;\n  - USB sound devices;\n  - KVM core;\n(CVE-2024-49938, CVE-2024-41066, CVE-2024-57951, CVE-2024-56779,\nCVE-2024-50194, CVE-2024-50265, CVE-2024-56596, CVE-2024-57922,\nCVE-2024-56614, CVE-2024-57912, CVE-2024-50251, CVE-2024-56569,\nCVE-2024-56587, CVE-2024-57807, CVE-2024-50051, CVE-2024-49997,\nCVE-2024-57911, CVE-2024-50195, CVE-2024-50205, CVE-2024-35896,\nCVE-2025-21689, CVE-2024-43098, CVE-2024-47757, CVE-2025-21639,\nCVE-2024-57900, CVE-2024-56634, CVE-2024-50230, CVE-2024-57946,\nCVE-2024-53059, CVE-2024-50290, CVE-2024-49985, CVE-2024-50142,\nCVE-2024-49925, CVE-2024-50199, CVE-2024-47699, CVE-2024-53172,\nCVE-2024-53173, CVE-2024-56631, CVE-2024-57938, CVE-2024-53101,\nCVE-2024-53197, CVE-2024-49896, CVE-2024-47697, CVE-2024-56644,\nCVE-2024-50236, CVE-2024-46731, CVE-2024-47674, CVE-2024-38544,\nCVE-2024-46853, CVE-2024-47740, CVE-2024-53121, CVE-2024-50082,\nCVE-2024-53165, CVE-2024-50040, CVE-2024-57929, CVE-2024-57889,\nCVE-2024-49860, CVE-2024-50287, CVE-2022-49034, CVE-2024-56690,\nCVE-2024-50302, CVE-2024-50006, CVE-2024-49949, CVE-2024-49868,\nCVE-2024-49903, CVE-2024-47723, CVE-2024-49936, CVE-2024-49955,\nCVE-2024-50234, CVE-2024-50301, CVE-2024-47670, CVE-2024-56574,\nCVE-2024-50168, CVE-2024-57913, CVE-2024-56602, CVE-2024-56630,\nCVE-2024-53130, CVE-2024-53145, CVE-2024-56642, CVE-2024-50202,\nCVE-2024-38588, CVE-2024-56767, CVE-2024-50024, CVE-2024-53198,\nCVE-2024-56548, CVE-2024-50184, CVE-2024-47756, CVE-2024-50167,\nCVE-2025-21694, CVE-2024-53063, CVE-2024-49966, CVE-2024-50299,\nCVE-2024-50143, CVE-2024-49924, CVE-2024-53061, CVE-2024-53124,\nCVE-2024-49902, CVE-2024-56739, CVE-2024-49952, CVE-2025-21664,\nCVE-2024-49877, CVE-2024-47701, CVE-2024-52332, CVE-2024-49975,\nCVE-2024-56645, CVE-2024-53140, CVE-2024-49948, CVE-2024-56724,\nCVE-2024-49963, CVE-2025-21687, CVE-2024-47698, CVE-2024-50039,\nCVE-2024-56595, CVE-2024-50282, CVE-2023-52458, CVE-2024-56615,\nCVE-2024-40965, CVE-2024-49965, CVE-2024-53112, CVE-2024-53135,\nCVE-2024-56601, CVE-2024-56532, CVE-2024-53184, CVE-2024-47672,\nCVE-2024-53155, CVE-2024-50171, CVE-2024-50035, CVE-2024-56704,\nCVE-2024-53156, CVE-2024-47685, CVE-2024-50044, CVE-2024-47712,\nCVE-2024-47707, CVE-2024-50179, CVE-2024-56594, CVE-2024-56688,\nCVE-2024-50151, CVE-2025-21699, CVE-2024-56598, CVE-2024-47737,\nCVE-2024-57849, CVE-2024-56576, CVE-2025-21638, CVE-2024-53181,\nCVE-2024-50033, CVE-2024-49995, CVE-2024-56756, CVE-2024-49867,\nCVE-2025-21697, CVE-2024-56600, CVE-2024-56670, CVE-2024-47713,\nCVE-2024-46854, CVE-2024-47671, CVE-2024-53680, CVE-2024-49851,\nCVE-2024-49883, CVE-2024-56780, CVE-2024-56770, CVE-2024-56650,\nCVE-2024-53146, CVE-2024-50218, CVE-2024-56531, CVE-2024-47706,\nCVE-2024-56572, CVE-2024-47709, CVE-2024-49958, CVE-2024-57948,\nCVE-2024-40911, CVE-2024-57904, CVE-2024-56769, CVE-2024-35887,\nCVE-2025-21678, CVE-2024-57802, CVE-2024-56700, CVE-2024-43900,\nCVE-2024-47747, CVE-2024-50059, CVE-2024-56606, CVE-2024-53161,\nCVE-2024-50116, CVE-2024-50180, CVE-2024-50127, CVE-2024-53131,\nCVE-2024-53157, CVE-2024-50279, CVE-2024-57850, CVE-2024-56619,\nCVE-2024-49982, CVE-2024-56748, CVE-2024-53104, CVE-2024-49981,\nCVE-2024-56643, CVE-2024-49962, CVE-2024-50131, CVE-2024-56781,\nCVE-2024-50233, CVE-2024-56597, CVE-2024-56567, CVE-2024-57902,\nCVE-2024-43863, CVE-2024-56581, CVE-2024-53171, CVE-2024-56633,\nCVE-2024-50296, CVE-2024-49879, CVE-2024-56593, CVE-2024-47679,\nCVE-2024-53148, CVE-2024-50237, CVE-2024-49959, CVE-2024-50269,\nCVE-2024-53138, CVE-2024-49957, CVE-2024-50278, CVE-2024-49894,\nCVE-2024-49900, CVE-2024-56586, CVE-2024-50148, CVE-2024-50262,\nCVE-2024-56720, CVE-2024-50096, CVE-2024-57931, CVE-2024-56681,\nCVE-2021-47219, CVE-2025-21640, CVE-2024-56603, CVE-2024-50229,\nCVE-2024-53174, CVE-2024-50007, CVE-2024-49944, CVE-2024-50273,\nCVE-2024-49878, CVE-2024-56605, CVE-2024-53150, CVE-2024-44931,\nCVE-2024-53214, CVE-2024-49882, CVE-2024-53158, CVE-2024-55916,\nCVE-2024-50117, CVE-2024-56570, CVE-2024-44938, CVE-2024-53239,\nCVE-2024-53217, CVE-2024-50099, CVE-2024-50267, CVE-2024-56562,\nCVE-2024-40953, CVE-2024-57884, CVE-2024-49892, CVE-2024-56659,\nCVE-2024-56746, CVE-2024-50074, CVE-2024-41016, CVE-2024-53142,\nCVE-2024-57901, CVE-2024-56637, CVE-2024-47710, CVE-2024-46849,\nCVE-2024-57910, CVE-2024-47692, CVE-2024-48881, CVE-2024-53194,\nCVE-2024-56558, CVE-2024-56747, CVE-2024-56629, CVE-2024-47696,\nCVE-2024-56691, CVE-2024-53227, CVE-2024-57908, CVE-2024-57892,\nCVE-2024-53183, CVE-2024-56723, CVE-2024-42252, CVE-2024-57890,\nCVE-2024-50134, CVE-2024-56694, CVE-2024-57906, CVE-2024-56539,\nCVE-2024-53690, CVE-2024-53066, CVE-2024-49973, CVE-2024-47684,\nCVE-2024-50045, CVE-2024-49884, CVE-2025-21653, CVE-2024-47749,\nCVE-2024-47742, CVE-2024-50008, CVE-2024-50150, CVE-2024-53127,\nCVE-2024-49996)\n","status":"published","published":"2025-03-28T18:47:41Z","modified":"2026-10-29T20:02:49.342992859Z","updated_at":"2026-11-02T16:58:19.988474Z"}]},"sources_more":{"osv":5}}